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.
DevNet launched a new microsite devoted to OPNFV (Open Platform for Network Function Virtualization).
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.
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: https://www.opnfv.org/software/download
For Arno release, the Documentation lists the following:
CentOS 7 (from ISO or self-installed).
libvirt or other hypervisors disabled (no kernel modules loaded).
3-4 NICs, untagged (no 802.1Q tagging), with IP addresses.
Internet access for downloading packages, with a default gateway configured.
4 GB of RAM for a bare metal deployment, 24 GB of RAM for a VM deployment.
No DHCP or TFTP server running on networks used by OPNFV.
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.
Lights out OOB network access from Jumphost with IPMI node enabled (bare metal deployment only).
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
IPMI enabled on OOB interface for power control.
BIOS boot priority should be PXE first then local hard disk.
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:
IPMI IP addresses for the nodes.
IPMI login information for the nodes (user/pass).
MAC address of admin interfaces on nodes.
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.