Announcement:Help us improve your community experience


5 posts

In this video I am trying to show basic steps to troubleshoot when something went wrong with deployment. I am using Virtual devnet sandbox on which deployment failed with the problem to find NTP server.

Here is the link to video:

Basic troubleshooting of fuel deployer - YouTube

After successful deploy of arno fuel image on master branch I connected to the Openstack where I was trying to spawn 2 VMs and was trying to ping each other to prove basic functionality.

Here is the link to video:

basic VNF functionality - YouTube


OPNFV deployment using Fuel

Posted by pbandzi Feb 8, 2016

Here is a video showing Fuel Arno release deployment.


The overall process should be same also for Brahmaputra release, however templates (dea.yaml, dha.yaml) need to be modified accordingly.


Before start your own deployment it is recommended to look at latest documentation available at:



Other good source of info:   (search for fuel)


There is also community on irc channels available for help.


New OPNFV microsite goes LIVE

Posted by eckelcu Jan 22, 2016

DevNet launched a new microsite devoted to OPNFV (Open Platform for Network Function Virtualization).


Screen Shot 2016-01-22 at 11.43.48 AM.png

For Cisco, OPNFV is a perfect complement to Cisco’s NFVI solution. OPNFV provides a great foundation by putting in place infrastructure that allows for continuous integration, test, and enhancement of NFV infrastructure components as an automated system. OPNFV continuously and automatically retrieves a set of components from upstream projects, integrates them, installs the system reference hardware, and runs automated test suites against this reference deployment.


With the OPNFV microsite, you can quickly and easily grasp what OPNFV is all about, Cisco's role in the OPNFV community, and Cisco products and platforms that enable you to start building your own solutions on top of a carrier grade platform for NFV. Instructional videos help you install your own OPNFV environment, and slides and recordings from previous presentations by OPNFV experts at Cisco. Better still, we have a full lineup of OPNFV related content on tap for CiscoLive Berlin, February 15-19.


Screen Shot 2016-01-22 at 11.16.04 AM.pngInsightful OPNFV sessions include:

* Requires full conference pass

You can also count on hands on demos in the DevNet Zone that showcase OPNFV solutions and give you access to OPNFV experts on site.

Register today! Multiple registration options are available. The Explorer Pass gives you access to the DevNet Zone the entire week.

OpenStack can be very challenging to install. The procedures and documentation have improved over time, but there is still a lot to do. Configuring OpenStack to work appropriately with OpenDaylight and other components of the OPNFV architecture can be even more challenging. Thanks to Peter Bandzi, we have a couple videos that can help. But before jumping into the videos, let's provide some background.


For OPNFV deployment, proper network preparation is key. Most requirements are covered in the Installation Guide. This can be found in the Documentation section at:


For Arno release, the Documentation lists the following:


Jumphost Requirements
  1. CentOS 7 (from ISO or self-installed).
  2. Root access.
  3. libvirt or other hypervisors disabled (no kernel modules loaded).
  4. 3-4 NICs, untagged (no 802.1Q tagging), with IP addresses.
  5. Internet access for downloading packages, with a default gateway configured.
  6. 4 GB of RAM for a bare metal deployment, 24 GB of RAM for a VM deployment.


Network Requirements
  1. No DHCP or TFTP server running on networks used by OPNFV.
  2. 3-4 separate VLANs (untagged) with connectivity between Jumphost and nodes (bare metal deployment only). These make up the admin, private, public and optional storage networks.
  3. Lights out OOB network access from Jumphost with IPMI node enabled (bare metal deployment only).
  4. Admin or public network has Internet access, meaning a gateway and DNS availability.

Note: Storage network will be consolidated to the private network if only 3 networks are used.


Bare Metal Node Requirements
  1. IPMI enabled on OOB interface for power control.
  2. BIOS boot priority should be PXE first then local hard disk.
  3. BIOS PXE interface should include admin network mentioned above.


Execution Requirements (Bare Metal Only)

In order to execute a deployment, one must gather the following information:

  1. IPMI IP addresses for the nodes.
  2. IPMI login information for the nodes (user/pass).
  3. MAC address of admin interfaces on nodes.
  4. MAC address of private interfaces on 3 nodes that will be controllers



Foreman/Quickstack is one of the two deployment tools offered as part of OPNFV Release 1.


Before you try to deploy, make sure you look at the wiki:

The latest installation instructions can be found:


Deploy scripts are cloned as follows:

git clone


This approach installs everything from public repositories. This might be an issue when you use it behind a proxy.

Here is a little patch which modifies some parts of deploy script in order to make it work behind a proxy. This however works only for virtual deploy:


The following two videos help walk you through the requirements and installation of your OPNFV deployment.



Screen Shot 2015-10-20 at 12.21.17 PM.png



Screen Shot 2015-10-20 at 12.17.39 PM.png


Good luck!  Let us know how it goes. Please share any suggestions you have for improvements.