Skip to content

Q&A

Jump to bottom
Gerardo García edited this page Nov 28, 2016 · 10 revisions

This page is obsolete.

The project OpenMANO has been contributed to the open source community project Open Source MANO (OSM), hosted by ETSI.

Go to the URL osm.etsi.org to know more about OSM.

#Table of Contents#

Can I use compute nodes with Core i3, i5 or i7 processors or AMD processors?

Host addition is managed by openvim module using the command "openvim host-add [file]":

  • Automatic host addition. If you don't include a file, you should answer the questions and then openvim will try to add the host automatically, getting the parameters directly from the host.
  • Manual host addition. If the file is included, the file describes the internal architecture of the host and the appropriate parameters. You could follow the examples provided with the code.

Manual host addition should work with any processor as long as the host file is appropriately written.

Automatic host addition has been tested with servers based on Xeon E5 Intel processors with Ivy Bridge architecture. No tests have been carried out with Intel Core i3, i5 and i7 families or AMD processors, so there are no guarantees that the automatic host addition will be seamless.

When I try deploying a network scenario, I get the following message: "No room at data center for allocating the server" What's the meaning?

This means that there are not enough resources in the hosts to allocate all the VMs of a network scenario. The error can also appear in 'test mode'. Although in test mode VMs are not deployed in the hosts, the resource orchestration is still done, so enough room is needed in any case. The error can be one of the following issues:

  1. There are no hosts (check openvim host-list). Or the hosts are occupied (check allocated VMs with openvim vm-list). In test mode, you should have 'fake' hosts, like the ones provided as examples in the Getting Started guide:

     ./openvim host-add test/hosts/host-example0.json # repeat with host-example1, ...2, ...3

  2. There is not enough memory in the hosts. Ensure that hosts contain enough HUGEPAGES of Gibabytes. (See 'openvim host-list -vvv'. Total memory appears at 'host:numas:memory', and hugepages memory at 'host:numas:hugepages')

  3. There are not enough isolated cores in the host. Ensure that hosts contain enough isolated cores (See 'openvim host-list -vvv'. Cores appear at 'host:numas:cores', those isolated are the ones without 'status: noteligible')

  4. There are no dataplane interfaces in the host WITH SWITCH PORT INFORMATION. Apart from having 10Gbit/s cards, openvim needs to know where they are connected to the switch port (regardless of using “host only” or “test” mode). It is needed to provide the switch port name where this interface is connected. In “test” or “host only” mode this switch port name can be a fake name. See 'openvim host-list -vvv', at 'host:numas:interfaces'. If empty, try to add the host following these steps

How do I configure the environment in order to use dataplane interfaces? How do I deal with the following message from openvim "Error 00:01:02:03:04:05:06:08 not present in controller"?

Once you are familiar with the test mode, if you plan to deploy VMs with dataplane interfaces (passthrogh or SR-IOV), you have 2 options:

  1. If you have an Openflow switch and you want to use it, you must use the normal mode. You need to have the floodlight controller running and you need to make the Openflow switch connects to the Floodlight controller. Once you have the Openflow switch connected to the floodlight controller, you can get the list of switches connected to the Floodlight controller with the following instruction:

     curl http://localhost:7070/wm/core/controller/switches/json

    You can get the dpid from there and configure it in openvimd.cfg. If the switch is not available, openvimd will not be able to run.

  2. The other option, only recommended if you don’t want to use an Openflow switch, is to use the “host only” mode. In that mode, the openflow controller is not needed, but all the dataplane connections must be done manually. This means that you will need first to deploy the VM, then obtain the physical interfaces that were assigned to that VM, and finally plug the cable to the appropriate physical interface based on the previous information. In order to know the physical interfaces assigned to a VM, use the following commands:

     openmano instance-scenario-list <instance>         #read the VIM ID of the VM
 openvim vm-list <vim_vm_id> -vvv                   #read the source under extended > numas > interfaces

Prior to that, we advise you to create a diagram of the physical interfaces of your host, with its name and the PCI address associated to each port. For that purpose, use the following commands:

ethtool –p <iface>            # makes a physical port blink
ethtool -i <iface>            # to get the PCI address of the interface.
Clone this wiki locally