White Papers

Understanding OPNFV

Issue link: https://read.uberflip.com/i/1344850

Contents of this Issue

Navigation

Page 102 of 144

Understanding OPNFV 102 (RDO is a project that takes OpenStack packages originally developed for Ubuntu and ports them to CentOS, Fedora and Red Hat Enterprise Linux.) Triple-O uses an interesting philosophy of OpenStack on OpenStack. It first installs a light-weight OpenStack "undercloud". An OpenStack "overcloud", the one that will actually be used by workloads, is deployed by the undercloud using Heat templates. Apex provides flexibility, but at the cost of numerous manual steps. JOID JOID stands for Juju OPNFV Infrastructure Deployer. JOID uses two open source projects that came out of Canonical: MAAS and Juju. Both are general purpose technologies, as opposed to purpose-built. Sample JOID Juju Screenshot MAAS (metal as a service) is a tool for provisioning bare metal servers. MAAS has functionality such as OS provisioning, inventory management, IPAM (IP address manager) and PXE/IPMI integration with a convenient GUI, CLI, or API access. Juju is a service orchestration tool that is used for deploying OpenStack on a MAAS environment. If Juju sounds familiar, it's because we discussed it in Chapter 4 in the context of being a VNFM for multiple MANO projects. Juju uses descriptors called Charms that are a template file to define a service. Charms support languages such as Chef, Puppet, Ansible and so on, and allow for the easy addition of new functionality such as SDN controllers or MANO.

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV