OSM Public Wiki - User contributions [en]

Openstack configuration (Release TWO)

2017-08-29T09:14:01Z

Mirabal: /* Add openstack to OSM */

__TOC__

=Configure openstack for OSM (basic)=

'''1. Guarantee that Openstack API endpoints are reachable from OSM (particularly from RO container)'''

'''2. Create a management network, with DHCP enabled, reachable from OSM (particularly from VCA container)'''

You need to create a management network, with DHCP enabled, and guarantee that this management network is reachable from OSM. The network is used by the VCA (Juju) for configuring the VNFs once they are running. It is recommended to create a provider network, isolated from Openstack. For instance, in order to create a provider network using physical interface em1 and VLAN 500 and with CIDR 10.208.0.0/24, you should run the following commands:
neutron net-create mgmt --provider:network_type=vlan --provider:physical_network=physnet_em1 --provider:segmentation_id=500 --shared
neutron subnet-create --name subnet-mgmt mgmt 10.208.0.0/24 --allocation-pool start=10.208.0.2,end=10.208.0.254

'''3. Create a valid tenant/user'''

You need to create a tenant/user with rights to create/delete flavors. The easiest way is to create a user and assign it the role "admin". Another option is to change the general flavor management policies at file ''/etc/nova/policy.json'' to allow flavor creation per user.

'''4. Upload images'''

OSM will create the needed images into openstack at deployment time, but the process takes a long time and the provided path at VNFD must be accesible by OSM. For this reason, it is recommended to upload the images of the VNFs manually at openstack, using the following command:

openstack image create --file="./cirros-0.3.4-x86_64-disk.img" --container-format=bare --disk-format=qcow2 --public cirros034

'''5. Modify default security group or create a new one'''

By default openstack apply the "default" security group that blocks any incoming traffic to the VM. However ssh access is needed by VCA. You must modify the default security group to allow TCP port 22 or; create a new security group and configure RO to use this security group when datacenter is addeed (see [[Openstack_configuration_(Release_TWO)#Add_openstack_to_OSM|Add openstack to OSM]] )

=Configure openstack for OSM (EPA)=

Besides the instructions above for any Openstack, you should do extra configuration to configure openstack for running VNFs which use SRIOV interfaces.

'''1. Provide a mechanism to connect the SR-IOV interfaces'''. As they are physical ports connected to an external switch, Neutron will not be able to connect them. You can use a physical switch programmed to interconnect the vlan tags among them (not recommened for security reasons). Another solution is to use a ML2 plugin that programs the external switch.

'''2. Configure the Neutron controller for using SR-IOV ports'''
<p>Edit /etc/neutron/plugins/ml2/ml2_conf.ini with the tag and vlan ranges used by the dataplane network</p>

[ml2_type_vlan]
network_vlan_ranges = physnet_sriov:3000:3100

'''3. Configure the compute nodes for using SR-IOV'''

On each compute node you have to associate the VFs available to each physical network. That is performed by configuring pci_passthrough_whitelist in /etc/nova/nova.conf. So, for example:

pci_passthrough_whitelist = {"vendor_id":"8086", "product_id":"10ed","physical_network":"physnet_sriov"}

=Add openstack to OSM=

There is a parameter called '''--config''' used to supply general configuration options both at datacenter creation and datacenter attachment to openmano tenant (the latter prevails).
openmano datacenter-create openstack-site http://10.10.10.11:5000/v2.0 --type openstack --description "OpenStack site" --config='{security_groups: default, keypair: mykey}'
openmano datacenter-attach openstack-site --user=admin --password=userpwd --vim-tenant-name=admin --config='{availability_zone: one}'

The following configuration can be added:

* '''security_groups''': To be used for the deployment
* '''availability_zone''': To be used for the deployment
* '''region_name''': The region where the VM must be deployed.
* '''insecure''': (By default false). When true it allows authorization over a non trusted certificate over https
* '''use_existing_flavors''': (By default false). Set to "True" to use the closer flavor with enough resources instead of creating a new flavor with the exact requirements. This option does not work for EPA (cpu pinning, huge pages, ...) where openmano still tries to create a flavor with the needed extra expects. Use this options when you do not have admin credentials (Available from future v2.0.2 version)
* '''APIversion''': (By default v2.0). Set to "v3.3" to use this openstack API version (experimental)

ADVANCED configuration:

* '''keypair''': To be added in addition to the keypair allocated on the VNF descriptor. Provide the name of a openstack keypair
* '''dataplane_physical_net''': The configured network_vlan_ranges at neutron for the SRIOV (binding direct) and passthrough (binding direct-physical) networks, e.g. 'physnet_sriov' in the above configuration
* '''use_floating_ip''': (By default false). When true a management interface of a VNFD is automatically asigned a floating_ip -if possible-. The prefered method is to use a provider network

The content of config is a yaml format text. The recomendation is to use a comma separated list between curly brackets {} and quotes, e.g.:
--config='{use_floating_ip: True, availability_zone: controller}'
--config='{use_floating_ip: True, availability_zone: [zone1, zone2]}'

Configuration of Openvim Compute Node for RHEL7.2 and CentOS7.2

2017-06-21T10:09:31Z

Mirabal:

'''This article contains specific instructions to configure a compute node, ready for NFV data plane workloads, based on a RHEL7.2 server or CentOS 7.2 Server Linux system.'''

In order to apply the configuration, you can do it automatically by using a script that performs all actions apart from BIOS configuration and user key sharing. This script is '''only for RHEL7.2 server and CentOS7.2 server'''.
wget -O install-openvim.sh "https://osm.etsi.org/gitweb/?p=osm/openvim.git;a=blob_plain;f=scripts/configure-compute-node-RHEL7.2.sh;hb=1ff6c02ecff38378a4d7366e223cefd30670602e"

chmod +x ./configure-compute-node-RHEL7.2.sh
sudo ./configure-compute-node-RHEL7.2.sh <user> <iface>

The variable <user> is the host user used by openvim to connect via ssh (libvirt admin rights will be granted to that user). The variable <iface> is the host interface where Linux bridges will be provisioned.

It is also possible to do the process manually. The [[Installation of an Openvim Compute Node|general guidelines]] fully apply to compute nodes based on RHEL7.2 or CentOS7.2 . You can follow all detailed instructions from there.

Configuration of Openvim Compute Node for RHEL7.2 and CentOS7.2

2017-06-21T10:07:56Z

Mirabal:

'''This article contains specific instructions to configure a compute node, ready for NFV data plane workloads, based on a RHEL7.2 server or CentOS 7.2 Server Linux system.'''

In order to apply the configuration, you can do it automatically by using a script that performs all actions apart from BIOS configuration and user key sharing. This script is '''only for RHEL7.2 and CentOS7.2'''.
wget -O install-openvim.sh "https://osm.etsi.org/gitweb/?p=osm/openvim.git;a=blob_plain;f=scripts/configure-compute-node-RHEL7.2.sh;hb=1ff6c02ecff38378a4d7366e223cefd30670602e"

chmod +x ./configure-compute-node-RHEL7.2.sh
sudo ./configure-compute-node-RHEL7.2.sh <user> <iface>

The variable <user> is the host user used by openvim to connect via ssh (libvirt admin rights will be granted to that user). The variable <iface> is the host interface where Linux bridges will be provisioned.

It is also possible to do the process manually. The [[Installation of an Openvim Compute Node|general guidelines]] fully apply to compute nodes based on RHEL7.2 or CentOS7.2. You can follow all detailed instructions from there.

Talk:OpenVIM installation (Release TWO)

2017-06-12T15:51:56Z

Mirabal: /* OVS controller */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim (network_type : bridge) relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Open '''openvimd.cfg''' and modify network_type:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare ovs controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Open '''openvimd.cfg''' and modify network_type:

network_type : ovs
ovs_controller_ip: <ovs_controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <ovs_controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # ovs_controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T15:51:07Z

Mirabal: /* OVS controller */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim (network_type : bridge) relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Open '''openvimd.cfg''' and modify network_type:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare ovs controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Open '''openvimd.cfg''' and modify network_type:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T15:50:58Z

Mirabal: /* DHCP server (Bridge) */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim (network_type : bridge) relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Open '''openvimd.cfg''' and modify network_type:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare ovs controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T15:49:10Z

Mirabal: /* DHCP server (Bridge) */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim (network_type : bridge) relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Modify '''openvimd.cfg''' and modify network_type:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare ovs controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T15:48:18Z

Mirabal: /* OVS controller */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim (network_type : bridge) relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare ovs controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T15:47:57Z

Mirabal: /* DHCP server (Bridge) */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim (network_type : bridge) relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T13:36:36Z

Mirabal: /* Openvim OVS controller */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T12:56:29Z

Mirabal: /* Openvim OVS controller */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== Openvim OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute ''scripts/configure-dhcp-server-UBUNTU16.0.4.sh'' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T12:55:50Z

Mirabal: /* DHCP server (Bridge) */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

For bridge type openvim relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----

== Openvim OVS controller==

For DHCP management through OVS networks, some preparation is need it before.

Execute '''scripts/configure-dhcp-server-UBUNTU16.0.4.sh''' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

OpenVIM installation (Release TWO)

2017-06-12T12:51:57Z

Mirabal: /* DHCP server */

__TOC__

=Infrastructure=
In order to run openvim in normal mode (see below the available modes) and deploy dataplane VNFs, an appropriate infrastructure is required. Below a reference architecture for an openvim-based DC deployment.

[[File:OpenvimDC.png|500px|Openvim Datacenter infrastructure]]

Openvim needs to be accessible from Resource Orchestrator (openmano).
Openvim needs:
* To make its API accesible from Resource Orchestrator (openmano). That's the purpose of the VIM mgmt network in the figure.
* To be connected to all compute servers through a network, the DC infrastructure network in the figure.
* To offer management IP addresses to VNFs for VNF configuration from CM (Juju server). That's the purpose of the Telco/VNF management network.

Compute nodes, besides being connected to the DC infrastructure network, must also be connected to two additional networks:
*Telco/VNF management network, used by Configuration Manager (Juju Server) to configure the VNFs
*Inter-DC network, optionally required to interconnect this datacenter to other datacenters (e.g. in MWC'16 demo, to interconnect the two sites).

VMs will be connected to these two networks at deployment time if requested by openmano.

=VM creation (openvim server)=
* Requirements:
** 1 vCPU (2 recommended)
** 4 GB RAM (4 GB are required to run OpenDaylight controller; if the ODL controller runs outside the VM, 2 GB RAM are enough)
** 40 GB disk
** 3 network interfaces to:
*** OSM network (to interact with RO)
*** DC intfrastructure network (to interact with the compute servers and switches)
*** Telco/VNF management network (to provide IP addresses via DHCP to the VNFs)
*Base image: ubuntu-16.04-server-amd64

=Installation=
Openvim is installed using a script:
wget -O install-openvim.sh "https://osm.etsi.org/gitweb/?p=osm/openvim.git;a=blob_plain;f=scripts/install-openvim.sh;hb=1ff6c02ecff38378a4d7366e223cefd30670602e"
chmod +x install-openvim.sh
sudo ./install-openvim.sh -q # --help for help on options
# NOTE: you can provide optionally the admin user (normally 'root') and password of the database.

Once installed, manage it with '''sudo service osm-openvim start|stop|restart'''

Logs are at '''/var/log/osm/openvim.log'''

Configuration file is at '''/etc/osm/openvimd.cfg'''

Thre is a CLI client called '''openvim'''. Type "openvim config" to see the configuration bash variables

== Openflow controller==
For normal or OF only openvim modes you will need a openflow controller. The following openflow controllers are supported:

===Floodlight version 0.90===
You can install e.g. floodlight-0.90. The script '''openvim/scripts/install-floodlight.sh''' makes this installation for you. And the script '''service-floodlight''' can be used to start/stop it in a screen with logs.
$ sudo openvim/scripts/install-floodlight.sh
$ service-floodlight start

===ONOS===
'''NOTE''': This tutorial assumes you are developing ONOS in ''DevelVM'' and deploying it on ''DeployVM'' (which is the one in which OpenVIM runs)

==== System requirements ====
* 2GB or more RAM (I personally recommend at least 4GB)
* 2 or more processors
* Ubuntu 14.04 LTS or 16.04 LTS (Checked with both distros)

==== Software requirements ====
===== Maven =====
Install Maven 3.3.9 on your Apps directory

$ cd ~
$ mkdir Apps
$ wget http://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
$ tar -zxvf apache-maven-3.3.9-bin.tar.gz -C ./Apps/

'''NOTE:''' Although ONOS has been migrated to Buck, maven was used in earlier releases.

===== Karaf =====
Install Karaf 3.0.5 on your Apps directory

$ cd ~
$ wget http://archive.apache.org/dist/karaf/3.0.5/apache-karaf-3.0.5.tar.gz
$ tar -zxvf apache-karaf-3.0.5.tar.gz -C ./Apps/

===== Java 8 =====
Install Java 8

$ sudo apt-get install software-properties-common -y
$ sudo add-apt-repository ppa:webupd8team/java -y
$ sudo apt-get update
$ sudo apt-get install oracle-java8-installer oracle-java8-set-default -y

Set your JAVA_HOME

export JAVA_HOME=/usr/lib/jvm/java-8-oracle

Verify it with the following command

$ env | grep JAVA_HOME

JAVA_HOME=/usr/lib/jvm/java-8-oracle

==== Download latest ONOS ====
$ git clone https://gerrit.onosproject.org/onos
$ cd onos
$ git checkout master

Edit ''onos/tools/dev/bash_profile'' and set the correct path for ONOS_ROOT, MAVEN and KARAF_ROOT

# Please note that I am using my absolute paths here, yours may be different
export ONOS_ROOT=${ONOS_ROOT:-~/onos}
export MAVEN=${MAVEN:-~/Apps/apache-maven-3.3.9}
export KARAF_ROOT=${KARAF_ROOT:-~/Apps/apache-karaf-$KARAF_VERSION}

Edit ''~/.bashrc'' and add the following line at the end:

#Please note that I am specifying here the absolute path of the bash_profile file in my machine, it may be different in yours
. ~/onos/tools/dev/bash_profile

Reload .bashrc or log out and log in again to apply the changes

. ~/.bashrc

==== Build and deploy ONOS ====
If you are using an stable release below 1.7, please use maven, otherwise, use Buck. Depending on which tool you use to build ONOS, the deployment procedure is also different.

===== Build with maven =====
$ mci # Alias for mvn clean install
$ op

===== Build with Buck =====
'''NOTE:''' ONOS currently uses a modified version of Buck, which has been packaged with ONOS. Please use this version until our changes have been upstreamed and released as part of an official Buck release.

$ sudo apt-get install zip unzip
$ cd $ONOS_ROOT
$ tools/build/onos-buck build onos --show-output
Updating Buck...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 43.8M 100 43.8M 0 0 172k 0 0:04:20 0:04:20 --:--:-- 230k
Archive: cache/buck-v2016.11.12.01.zip
inflating: buck
extracting: .buck_version
creating: plugins/
inflating: plugins/onos.jar
inflating: plugins/yang.jar
Successfully updated Buck in /home/alaitz/Code/onos/bin/buck to buck-v2016.11.12.01.zip

Not using buckd because watchman isn't installed.
[-] PROCESSING BUCK FILES...FINISHED 3.1s [100%] 🐳 New buck daemon
[+] DOWNLOADING... (0.00 B/S, TOTAL: 0.00 B, 0 Artifacts)
[+] BUILDING...1m47.9s [99%] (720/721 JOBS, 720 UPDATED, 720 [99.9%] CACHE MISS)
|=> IDLE
|=> IDLE
|=> IDLE
|=> //tools/package:onos-package... 9.9s (checking local cache)
|=> IDLE
|=> IDLE
|=> IDLE
|=> IDLE
The outputs are:
//tools/package:onos-package buck-out/gen/tools/package/onos-package/onos.tar.gz

'''Sources:'''
* Onos with Maven: https://wiki.onosproject.org/display/ONOS/Installing+and+Running+ONOS
* Onos with Buck: https://wiki.onosproject.org/display/ONOS/Developer+Guide

==== Run ONOS ====
$ cd $ONOS_ROOT
$ tools/build/onos-buck run onos-local -- clean debug

===OpenDayLight===
TBC

== DHCP server (Bridge)==

For bridge type openvim relays on precreated bridges at compute nodes that has L2 connectivity using e.g. a switch in trunk mode. In this mode you should provide an external DHCP server for the management network

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----
== OVS controller==

For ovs type openvim creates a ovs vxlan tunnel and launches a dhcp server in the ovs_controller. The ovs_controller can be a different or the same machine where openvim is running.

Some preparation is need it before for DHCP management through OVS networks:

Execute '''scripts/configure-dhcp-server-UBUNTU16.0.4.sh''' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_key for connecting to compute nodes

=Configuration=

- Go to openvim folder ('''/opt/openvim''') and edit openvimd.cfg. Note: by default it runs in mode: '''test''' where no real hosts neither openflow controller are needed. You can uses other modes:

{| class="wikitable"
|-
! mode
! Computes hosts
! Openflow controller
! Observations
|-
| test
| fake
| X
| No real deployment. Just for API test
|-
| normal
| needed
| needed
| Normal behavior
|-
| host only
| needed
| X
| No PT/SRIOV connections
|-
| develop
| needed
| X
| Force to cloud type deployment without EPA
|-
| OF only
| fake
| needed
| To test openflow controller without needed of compute hosts
|}

Service must be restarted
sudo service openvim restart

NOTE: the following steps (ONLY if openvim runs in test mode) are done automatically by script:
/opt/openvim/scripts/initopenvim.sh --insert-bashrc --force

- Let's configure the openvim CLI client. Needed if you have changed the /opt/openvim/openvimd.cfg file (WARNING not the ./openvim/openvimd.cfg)

openvim config # show openvim related variables
#To change variables run
export OPENVIM_HOST=<http_host of openvimd.cfg>
export OPENVIM_PORT=<http_port of openvimd.cfg>
export OPENVIM_ADMIN_PORT=<http_admin_port of openvimd.cfg>
#You can insert at .bashrc for authomatic loading at login:
echo "export OPENVIM_HOST=<...>" >> /{HOME}/.bashrc
...

==Adding compute nodes==
- Let's attach compute nodes

In '''test''' mode we need to provide fake compute nodes with all the necessary information:

openvim host-add /opt/openvim/test/hosts/host-example0.yaml
openvim host-add /opt/openvim/test/hosts/host-example1.yaml
openvim host-add /opt/openvim/test/hosts/host-example2.yaml
openvim host-add /opt/openvim/test/hosts/host-example3.yaml
openvim host-list #-v,-vv,-vvv for verbosity levels

In '''normal''' or '''host only''' mode, the process is a bit more complex. First, you need to configure appropriately the host following these [[Installation of an Openvim Compute Node|guidelines]]. The current process is manual, although we are working on an automated process. For the moment, follow these instructions:

#copy /opt/openvim/scripts/host-add.sh and run at compute host for gather all the information
./host_add.sh <user> <ip_name> >> host.yaml

#NOTE: If the host contains interfaces connected to the openflow switch for dataplane,
# the switch port where the interfaces are connected must be provided manually,
# otherwise these interfaces cannot be used. Follow one of two methods:
# 1) Fill openvim/database_utils/of_ports_pci_correspondence.sql ...
# ... and load with mysql -uvim -p vim_db < openvim/database_utils/of_ports_pci_correspondence.sql
# 2) or add manually this information at generated host.yaml with a 'switch_port: <whatever>'
# ... entry at 'host-data':'numas': 'interfaces'

# copy this generated file host.yaml to the openvim server, and add the compute host with the command:
openvim host-add host.yaml

# copy openvim ssh key to the compute node. If openvim user didn't have a ssh key generate it using ssh-keygen
ssh-copy-id <compute node user>@<IP address of the compute node>

'''Note''': It must be noted that Openvim has been tested with servers based on Xeon E5 Intel processors with Ivy Bridge architecture. No tests have been carried out with Intel Core i3, i5 and i7 families, so there are no guarantees that the integration will be seamless.

==Adding external networks==

- Let's list the external networks:

openvim net-list

- Let's create some external networks in openvim. These networks are public and can be used by any VNF. It must be noticed that these networks must be pre-provisioned in the compute nodes in order to be effectively used by the VNFs. The pre-provision will be skipped since we are in test mode. Four networks will be created:
* ''default'' -> default NAT network provided by libvirt. By creating this network, VMs will be able to connect to default network in the same host where they are deployed.
* ''macvtap:em1'' -> macvtap network associated to interface "em1". By creating this network, we allow VMs to connect to a macvtap interface of physical interface "em1" in the same host where they are deployed. If the interface naming scheme is different, use the appropriate name instead of "em1".
* ''bridge_net'' -> bridged network intended for VM-to-VM communication. The pre-provision of a Linux bridge in a compute node is described in [[Installation of an Openvim Compute Node#Pre-provision_of_Linux_bridges|this link]]. By creating this network, VMs will be able to connect to the Linux bridge "virbrMan1" in the same host where they are deployed. In that way, two VMs connected to "virbrMan1", no matter the host, will be able to talk each other.
* ''data_net'' -> external data network intended for VM-to-VM communication. By creating this network, VMs will be able to connect to a network element connected behind a physical port in the external switch.

In order to create external networks, use 'openvim net-create', specifying a file with the network information. Now we will create the 4 networks:

openvim net-create /opt/openvim/test/networks/net-example0.yaml
openvim net-create /opt/openvim/test/networks/net-example1.yaml
openvim net-create /opt/openvim/test/networks/net-example2.yaml
openvim net-create /opt/openvim/test/networks/net-example3.yaml

- Let's list the external networks:

openvim net-list
2c386a58-e2b5-11e4-a3c9-52540032c4fa data_net
35671f9e-e2b4-11e4-a3c9-52540032c4fa default
79769aa2-e2b4-11e4-a3c9-52540032c4fa macvtap:em1
8f597eb6-e2b4-11e4-a3c9-52540032c4fa bridge_net

You can build your own networks using the template 'templates/network.yaml'. Alternatively, you can use 'openvim net-create' without a file and answer the questions:

openvim net-create

You can delete a network, e.g. "macvtap:em1", using the command:

openvim net-delete macvtap:em1

==Creating a new tenant==
- Now let's create a new tenant "admin":

$ openvim tenant-create --name admin --description admin
<uuid> admin Created

- Take the uuid of the tenant and update the environment variables used by openvim client:

export OPENVIM_TENANT=<obtained uuid>
#echo "export OPENVIM_TENANT=<obtained uuid>" >> /home/${USER}/.bashrc
openvim config #show openvim env variables

Talk:OpenVIM installation (Release TWO)

2017-06-12T12:44:07Z

Mirabal: /* Openflow Controller (floodlight) */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

== DHCP server (Bridge)==

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----
== Openvim OVS controller==

For DHCP management through OVS networks, some preparation is need it before.

Execute '''scripts/configure-dhcp-server-UBUNTU16.0.4.sh''' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Talk:OpenVIM installation (Release TWO)

2017-06-12T12:30:35Z

Mirabal: /* DHCP server */

=Introduction=
Openvim is an implementation of an NFV VIM supporting EPA features and control of an underlay switching infrastructure through an OFC. Some of the EPA features included in openvim are:

*CPU pinning
*Memory pinning
*NUMA pinning
*Support of memory huge pages
*Port passthrough interfaces
*SR-IOV interfaces
*Injection of virtual PCI addresses

Openvim controller interfaces with Openvim compute nodes in the NFV Infrastructure and an Openflow controller in order to provide computing and networking capabilities and to deploy virtual machines. It offers a northbound interface, based on REST (openvim API), where enhanced cloud services are offered including the creation, deletion and management of images, flavors, instances and networks.

Next figure shows a general diagram of a datacenter controlled by openvim.

Openvim controller relies on an NFS server as image repository, an Openflow Clontroller to configure the underlay switches, and a DHCP server to provide management IP addresses to the VMs. For simplicity, these instructions will asume that these three additional modules (image repo, OFC and DHCP server will be hosted in the same machine as Openvim controller.

=Requirements=
==Openvim controller==

==Openvim compute nodes==

=Installation=

==Openvim Controller==

==NFS server==

==Openflow Controller (floodlight)==

Openvim support 2 dhcp server options, bridge or ovs

----
== DHCP server (Bridge)==

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----
== Openvim OVS controller==

For DHCP management through OVS networks, some preparation is need it before.

Execute '''scripts/configure-dhcp-server-UBUNTU16.0.4.sh''' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

=Openvim Compute Node configuration=

=Configuring openvim=
==Configure openvimd.cfg==
==Restarting openvim==
==Adding a compute node==
==Creating the management network==
==Creating a tenant==

Ovs changes

2017-06-12T12:24:42Z

Mirabal: Blanked the page

Ovs changes

2017-06-12T12:14:16Z

Mirabal: Created page with "Openvim support 2 dhcp server options, bridge or ovs ---- == DHCP server (Bridge)== Modify '''openvimd.cfg''' and add net controller connection details: network_type : b..."

Openvim support 2 dhcp server options, bridge or ovs

----
== DHCP server (Bridge)==

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : bridge

For the management network a DHCP server is needed. Install the package dhcp3-server. This package will install the actual DHCP server based on isc-dhcp-server package.

Ubuntu 14.04: sudo apt-get install dhcp3-server
Ubuntu 16.04: sudo apt install isc-dhcp-server

Configure it editing file '''/etc/default/isc-dhcp-server''' to enable DHCP server in the appropriate interface, the one attached to Telco/VNF management network (e.g. eth1).

$ sudo vi /etc/default/isc-dhcp-server
INTERFACES="eth1"

Edit file '''/etc/dhcp/dhcpd.conf''' to specify the subnet, netmask and range of IP addresses to be offered by the server.

$ sudo vi /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 86400;
max-lease-time 86400;
log-facility local7;
option subnet-mask 255.255.0.0;
option broadcast-address 10.210.255.255;
subnet 10.210.0.0 netmask 255.255.0.0 {
range 10.210.1.2 10.210.1.254;
}

Restart the service:

sudo service isc-dhcp-server restart

----
== Openvim OVS controller==

For DHCP management through OVS networks, some preparation is need it before.

Execute '''scripts/configure-dhcp-server-UBUNTU16.0.4.sh''' to prepare openvim net controller. Can be placed in the same Openvim VM or in a new one.

''$sudo ./openvim/scripts/configure-dhcp-server-UBUNTU16.0.4.sh <user-name>''

Modify '''openvimd.cfg''' and add net controller connection details:

network_type : ovs
ovs_controller_ip: <net controller ip> # dhcp controller IP address, must be change in
# order to reach computes.
ovs_controller_user: <net controller user> # User for the dchp controller for OVS networks
ovs_controller_file_path: '/var/lib/openvim' # Net controller Path for dhcp daemon
# configuration, by default '/var/lib/openvim

For automatic login from openvim controller to OVS controller computes fill the ovs_controller_keyfile path to the public ssh key must be specify in openvimd.cfg.

ovs_controller_keyfile: /path/to/ssh-key-file # ssh-access-key file to connect host
host_ssh_keyfile: /path/to/ssh-key-file # Default ssh_kye to use for connecting to compute nodes

Talk:Logs and troubleshooting (Release ONE)

2017-04-07T10:31:58Z

Mirabal:

== Update with install script ? ==

About the section [[Logs_and_troubleshooting_(Release_ONE)#Software_upgrade]]

The script linked in [[OSM_Release_ONE#Install_from_source]] is supposed to handle updates, is it stable enough to be included in the wiki ?

No, the option "--update" is not working yet. It is work in progress.

==RO upgrade==
(Propose of change once R TWO is launched)

Execute at RO container ("lxc exec RO bash" to enter into the container, "exit" to exit)

Until v1.1 execute:

service openmano stop
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v1.0.5
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
service openmano start

Upgrade from v1.x to v2.x execute:
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v2.0
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
# install some libraries need it by openvim lib
sudo apt-get install make python-pip python-paramiko libssl-dev libffi-dev python-libvirt
cd /opt
git clone https://osm.etsi.org/gerrit/osm/openvim
cd openvim/
# install openvim lib
sudo make lite
# after install openvim python library, lib-osm-openvim will be listed by "pip list" command
/usr/local/osm/openvim/database_utils/install-db-server.sh -U <db_admin_user> -P <db admin pass> -d mano_vim_db -u mano -p manopw
service openmano start

Talk:Logs and troubleshooting (Release ONE)

2017-04-07T10:31:36Z

Mirabal:

== Update with install script ? ==

About the section [[Logs_and_troubleshooting_(Release_ONE)#Software_upgrade]]

The script linked in [[OSM_Release_ONE#Install_from_source]] is supposed to handle updates, is it stable enough to be included in the wiki ?

No, the option "--update" is not working yet. It is work in progress.

==RO upgrade==
(Propose of change once R TWO is launched)

Execute at RO container ("lxc exec RO bash" to enter into the container, "exit" to exit)

Until v1.1 execute:

service openmano stop
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v1.0.5
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
service openmano start

Upgrade from v1.x to v2.x execute:
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v2.0
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
# install some libraries need it by openvim lib
sudo apt-get install make python-pip python-paramiko libssl-dev libffi-dev python-libvirt
cd /opt
git clone https://osm.etsi.org/gerrit/osm/openvim
cd openvim/
# install openvim lib
sudo make
# after install openvim python library, lib-osm-openvim will be listed by "pip list" command
/usr/local/osm/openvim/database_utils/install-db-server.sh -U <db_admin_user> -P <db admin pass> -d mano_vim_db -u mano -p manopw
service openmano start

Talk:Logs and troubleshooting (Release ONE)

2017-04-07T10:27:58Z

Mirabal:

== Update with install script ? ==

About the section [[Logs_and_troubleshooting_(Release_ONE)#Software_upgrade]]

The script linked in [[OSM_Release_ONE#Install_from_source]] is supposed to handle updates, is it stable enough to be included in the wiki ?

No, the option "--update" is not working yet. It is work in progress.

==RO upgrade==
(Propose of change once R TWO is launched)

Execute at RO container ("lxc exec RO bash" to enter into the container, "exit" to exit)

Until v1.1 execute:

service openmano stop
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v1.0.5
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
service openmano start

Upgrade from v1.x to v2.x execute:
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v2.0
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
cd /opt
git clone https://osm.etsi.org/gerrit/osm/openvim
cd openvim/
sudo make
/usr/local/osm/openvim/database_utils/install-db-server.sh -U <db_admin_user> -P <db admin pass> -d mano_vim_db -u mano -p manopw
service openmano start

Talk:Logs and troubleshooting (Release ONE)

2017-04-07T10:06:56Z

Mirabal:

== Update with install script ? ==

About the section [[Logs_and_troubleshooting_(Release_ONE)#Software_upgrade]]

The script linked in [[OSM_Release_ONE#Install_from_source]] is supposed to handle updates, is it stable enough to be included in the wiki ?

No, the option "--update" is not working yet. It is work in progress.

==RO upgrade==
(Propose of change once R TWO is launched)

Execute at RO container ("lxc exec RO bash" to enter into the container, "exit" to exit)

Until v1.1 execute:

service openmano stop
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v1.0.5
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
service openmano start

Upgrade from v1.x to v2.x execute:
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v2.0
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
cd /opt
git clone https://osm.etsi.org/gerrit/osm/openvim
cd openvim/
sudo make

/usr/local/osm/openvim/database_utils/install-db-server.sh -U <db_admin_user> -P <db admin pass> -d mano_vim_db -u mano -p manopw
service openmano start

Talk:Logs and troubleshooting (Release ONE)

2017-04-07T09:56:23Z

Mirabal:

== Update with install script ? ==

About the section [[Logs_and_troubleshooting_(Release_ONE)#Software_upgrade]]

The script linked in [[OSM_Release_ONE#Install_from_source]] is supposed to handle updates, is it stable enough to be included in the wiki ?

No, the option "--update" is not working yet. It is work in progress.

==RO upgrade==
(Propose of change once R TWO is launched)

Execute at RO container ("lxc exec RO bash" to enter into the container, "exit" to exit)

Until v1.1 execute:

service openmano stop
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v1.0.5
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
service openmano start

Upgrade from v1.x to v2.x execute:
#git -C /opt/openmano stash #required if the original config file has changed
git -C /opt/openmano pull --rebase
git -C /opt/openmano checkout tags/v2.0
#git -C /opt/openmano stash pop #required if the original file has changed
/opt/openmano/database_utils/migrate_mano_db.sh
cd /opt
git clone https://osm.etsi.org/gerrit/osm/openvim
cd openvim/
sudo make
/usr/local/osm/openvim/database_utils/install-db-server.sh -d mano_vim_db -u mano -p manopw –quiet --db-user-exist
service openmano start