Release 0 installation: Difference between revisions
Garciadeblas (talk | contribs) No edit summary |
Garciadeblas (talk | contribs) No edit summary |
||
| Line 17: | Line 17: | ||
Next figure shows the minimal infrastructure setup. The type and number and interfaces are only an example. | Next figure shows the minimal infrastructure setup. The type and number and interfaces are only an example. | ||
[[File:OSM_Rel0_DCinfra1.jpg|700px|OSM Release 0 Minimal infrastructure]] | |||
A zoom on the servers show how the OSM components interact each other, with the infrastructure (computes and switches) and with the VNFs: | |||
[[File:OSM_Rel0_DCinfra2.jpg|700px|OSM Release 0 Minimal infrastructure (zoom)]] | |||
The previous figures show the infrastructure and logical networks for a reduced setup for testing purposes. For an appropriate setup involving several datacenters, a different infrastructure is required. The main difference resides on the infrastructure for each datacenter. In the figure below, 2 datacenters are shown (based on OpenVIM and OpenStack respectively), and both are controlled from the OSM server. | The previous figures show the infrastructure and logical networks for a reduced setup for testing purposes. For an appropriate setup involving several datacenters, a different infrastructure is required. The main difference resides on the infrastructure for each datacenter. In the figure below, 2 datacenters are shown (based on OpenVIM and OpenStack respectively), and both are controlled from the OSM server. | ||
Revision as of 10:26, 10 May 2016
Infrastructure
The minimal infrastructure requirements for installing and running OSM Release 0 are 2 servers and 1 switch:
- The first server will run 5 VMs:
- RO (OpenMANO)
- NSO (Riftware)
- CM (Juju Server)
- An additional virtual machine (AVM) for operation support (containing an openmano CLI client and a Juju CLI client)
- A 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)
- Datacenter 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)
Next figure shows the minimal infrastructure setup. The type and number and interfaces are only an example. OSM Release 0 Minimal infrastructure
A zoom on the servers show how the OSM components interact each other, with the infrastructure (computes and switches) and with the VNFs: OSM Release 0 Minimal infrastructure (zoom)
The previous figures show the infrastructure and logical networks for a reduced setup for testing purposes. For an appropriate setup involving several datacenters, a different infrastructure is required. The main difference resides on the infrastructure for each datacenter. In the figure below, 2 datacenters are shown (based on OpenVIM and OpenStack respectively), and both are controlled from the OSM server.
*** IMAGE3 ***
Installing Release 0 modules and external references
In order to install release 0, you need to install and configure 3 virtual machines for hosting the 3 components. Details are provided in the links below:
- RO - Resource Orchestrator (Openmano)
- CM - Configuration Manager (Juju Server)
- NSO - Network Service Orchestrator (RiftWare)
In addition, it is recommended to have an additional virtual machine for operation support, whose installation procedure is detailed below:
Finally, compute nodes and VIMs are required. Right now, Openstack and OpenVIM are the VIMs supported in the RO. Below links on how to install and configure both VIMs: