Release ONE Installation: Difference between revisions
From OSM Public Wiki
Garciadeblas (talk | contribs) No edit summary |
Garciadeblas (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
Once you have prepared a server or VM with the requirements specified [[Release 1 Minimal infrastructure|here]], and you have [[LXD configuration for OSM release 1|configured LXD on it]], all you need to do is: | Once you have prepared a server or VM with the requirements specified [[Release 1 Minimal infrastructure|here]], and you have [[LXD configuration for OSM release 1|configured LXD on it]], all you need to do is: | ||
wget https://osm-download.etsi.org/ftp/osm-1.0-one/install_from_source | wget https://osm-download.etsi.org/ftp/osm-1.0-one/install_from_source.sh | ||
chmod +x install_from_source | chmod +x install_from_source.sh | ||
./install_from_source | ./install_from_source.sh | ||
After some time, you will get a fresh OSM Release One installation. You can access to the UI in the following URL: | After some time, you will get a fresh OSM Release One installation. You can access to the UI in the following URL: |
Revision as of 15:06, 5 October 2016
Once you have prepared a server or VM with the requirements specified here, and you have configured LXD on it, all you need to do is:
wget https://osm-download.etsi.org/ftp/osm-1.0-one/install_from_source.sh chmod +x install_from_source.sh ./install_from_source.sh
After some time, you will get a fresh OSM Release One installation. You can access to the UI in the following URL:
https://your_local_ip:8443
Next steps after the installation are:
- the addition of datacenters in order to be able to deploy NS
- the addition of VNF and NS to the catalog
- the deployment of NS.
Check the HowTo guide to know how to proceed with those tasks.
Further details on the result of the installation
As a result of the installation, three LXD containers will be created in your machine:
* SO-ub, hosting the Service Orchestrator and the User Interface * RO (Resource Orchestrator) * VCA (VNF Configuration and Abstraction)
If required, you could get access to each container from the host by running:
lxc exec <CONTAINER> bash