Release 0 minimal infrastructure

From OSM Public Wiki
Jump to: navigation, search

Minimal Infrastructure

The minimal infrastructure requirements for installing and running OSM Release 0 is a single server running the following components in 3 VM:

  • RO (OpenMANO)
  • SO (Riftware)
  • CM (Juju Server)

In addition, a datacenter will be required to be controlled by OSM. This datacenter must consist at least of 2 servers and a switch:

  • The first server will act as the Virtualized Infrastructure Manager (VIM).
  • The second server will act as a compute node controlled from the VIM.
  • The switch is intended to handle simultaneously different networks:
    • Datacenter infrastructure network (used by the VIM to talk to the compute nodes)
    • Telco/VNF management network (equivalent to a traditional telco management network, used by the CM to configure the VNFs)
    • Data plane networks (networks between VMs that use interfaces based on SR-IOV or Physical Port pass-through)
    • Other virtual networks (networks between VMs that use Linux bridges, virtual switches like OVS, etc. when the VMs are located in different compute nodes)
    • VIM management network (used by RO to talk to the VIMs)

Next figure shows the minimal infrastructure setup. The number of data-plane interfaces are only an example. The figure shows that OSM controller is connected to the same switch, bus this is not really required as long as there is L3 connectivity from OSM controller to the VIM mgmt network and to the Telco/VNF mgmt network.

OSM Release 0 Minimal infrastructure

A zoom on the OSM controller shows how the OSM components interact and to which networks they should be connected:

OSM Release 0 Controller

A zoom on the rest of servers shows also how OSM works together with a VIM and the infrastructure controlled by the VIM:

OSM Release 0 Minimal infrastructure (zoom)

Multi-datacenter infrastructure

The previous section showed the infrastructure and logical networks for a reduced setup for testing purposes. For an appropriate setup involving several datacenters, a different setup might be required. In the figure below, 2 datacenters are shown (based on OpenVIM and OpenStack respectively), and both are controlled from the OSM server that might be placed in a remote location. Both datacenters require connectivity to the OSM components:

  • The VIMs need to be accesible by the RO component
  • The VNFs need to be accesible by the CM component

OSM Release 0 Multi-datacenter infrastructure

Optionally, if it is desired to interconnect both datacenters, an inter-datacenter network is required (shown in purple in the figure). The inter-datacenter connectivity must be manually pre-provisioned in each datacenter. In Openstack, this means creating a provider network, while in OpenVIM this means creating a network associated to a specific port in the switching infrastructure.

Your feedback is most welcome!
You can send us your comments and questions to OSM_TECH@list.etsi.org
Or join the OpenSourceMANO Slack Workplace
See hereafter some best practices to report issues on OSM