Register a new Point of Presence (PoP)

The Virtualised Infrastructure Manager (Vim) is the functional block, responsible for controlling and managing the NFVI compute, storage and network resources within a Point of Presence (PoP).

In order to instantiate resources on a PoP, the NFVO must be aware of it. Assuming that you already installed the proper VIM driver, you need to register a new PoP. For doing that you can write a JSON file containing the details of your PoP, meaning how to reach via remote APIs the VIM responsible for that particular PoP. Here you have an example:

{  
   "name":"vim-instance-name",
   "authUrl":"http://127.0.0.1:5000/v2.0",
   "tenant":"tenant-name",
   "username":"username",
   "password":"password",
   "keyPair":"keypair",
   "securityGroups":[  
      "default"
   ],
   "type":"vim-driver-type",
   "location":{  
      "name":"Berlin",
      "latitude":"52.525876",
      "longitude":"13.314400"
   }
}

Most of the parameters are based on the OpenStack VIM type, since OpenStack represents the standard de-facto VIM in the ETSI NFV specification. However, there are additional VIM drivers provided, therefore refer to the actual VIM driver you are using for more details about what to fill in the JSON file:

Once you have prepared your JSON file, you need to upload it on the NFVO either via the dashboard (described below) or via the CLI.

Register the PoP using the GUI

In order to make use of your PoP described within your JSON file, you need to upload the JSON file to the NFVO. You can use the dashboard available at localhost:8080 for this purpose. Under the menu Manage PoPs you can see the PoP instances. Click on the Register a new PoP button and upload your JSON file (from the File input section). The following picture shows the dashboard:

register a new PoP

Once the VIM instance is registered, it will appear on the list of available PoPs, filled with the information regarding the available images, networks and flavors. At this point, you are ready to use this new PoP in any NSDs and VNFDs.

Please note that the name chosen must be unique inside the project and will be used to refer to the VimInstance.

For more information about the dashboard see: OpenBaton Dashboard