get_started_juju_deploy
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
get_started_juju_deploy [2015/11/11 17:08] Narinder Gupta |
get_started_juju_deploy [2015/11/11 18:19] (current) Narinder Gupta [Openstack Details] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Integrate you lab with Joid ====== | ||
| - | |||
| - | ''git clone https://gerrit.opnfv.org/gerrit/p/joid.git'' | ||
| - | ''cd joid/ci'' | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Enable MAAS ===== | ||
| - | |||
| - | * Create a directory in maas/<company name>/<pod number>/ for example | ||
| - | ''mkdir maas/intel/pod7/'' | ||
| - | |||
| - | * copy files from pod5 to pod7 | ||
| - | ''cp maas/intel/pod5/* maas/intel/pod7/* '' | ||
| - | |||
| - | 4 files will get copied: | ||
| - | deployment.yaml environments.yaml interfaces.host lxc-add-more-interfaces | ||
| - | |||
| - | ==== modify deployment.yaml file ==== | ||
| - | |||
| - | This file has been used to configure your maas and bootstrap node in a VM. Comments in the file are self explanatory and we expect fill up the information according to match lab infrastructure information. | ||
| - | |||
| - | ==== modify interfaces.host file ==== | ||
| - | |||
| - | This file will be used to configure your network interfaces on the rest of the nodes deployed through MAAS. | ||
| - | I would suggest to list interface you want to bring up after the deployment of the Operating System. JUJU will do that using this file. | ||
| - | |||
| - | ==== modify lxc-add-more-interfaces file ==== | ||
| - | |||
| - | This File will be used as network template to create the network in containers.\ | ||
| - | |||
| - | |||
| - | |||
| - | |||
| ====== Juju Build and Install instructions ====== | ====== Juju Build and Install instructions ====== | ||
| Line 38: | Line 4: | ||
| [[juju_release| Juju Release ]] | [[juju_release| Juju Release ]] | ||
| - | Single node | + | ===== Single node ===== |
| ----------- | ----------- | ||
| Line 51: | Line 18: | ||
| Hard disk: 250 GB | Hard disk: 250 GB | ||
| - | download the code | + | ==== download the code ==== |
| + | |||
| ----------------- | ----------------- | ||
| - | Scripts are hosted in Bazar branch | + | Scripts are hosted in OPNFV gerrit |
| + | |||
| + | ''$ sudo apt-get install git'' | ||
| - | ''$ sudo apt-get install bzr'' | + | ''$ git clone http://gerrit.opnfc.org/gerrit/joid.git'' |
| - | ''$ bzr branch lp:~sdn-charmers/+junk/odl-deployer'' | ||
| + | ==== Checkout charms ==== | ||
| - | Checkout charms | ||
| --------------- | --------------- | ||
| Line 67: | Line 36: | ||
| Follow these steps to checkout code: | Follow these steps to checkout code: | ||
| - | ''$ cd odl-deployer'' | + | ''$ cd joid/ci/odl/'' |
| ''$ ./fetch-charms.sh'' | ''$ ./fetch-charms.sh'' | ||
| Line 73: | Line 42: | ||
| This will checkout the relevant charms into 'src' and create any Juju symlinks | This will checkout the relevant charms into 'src' and create any Juju symlinks | ||
| in 'charms'. | in 'charms'. | ||
| + | |||
| + | ===== Deploy with cloud-sh-odl on single node ===== | ||
| - | Deploy with cloud-sh-odl on single node | ||
| --------------------------------------- | --------------------------------------- | ||
| Line 126: | Line 96: | ||
| - | Deploy with Juju Deployer for multiple node with MAAS | + | ===== Deploy with JOID for multiple node with MAAS ===== |
| ----------------------------------------------------- | ----------------------------------------------------- | ||
| Line 133: | Line 104: | ||
| Scripts are hosted in Bazar branch | Scripts are hosted in Bazar branch | ||
| - | ''$ sudo apt-get install bzr'' | + | ''$ sudo apt-get install git'' |
| - | ''$ bzr branch lp:~sdn-charmers/+junk/odl-deployer'' | + | ''$ git clone http://gerrit.opnfc.org/gerrit/joid.git'' |
| Pre Requisite: | Pre Requisite: | ||
| - | 1. have a single node install with MAAS and configure the MAAS environment. | + | 1. have a single node install with Ubuntu OS 14.04 LTS |
| - | 2. Have a JUJU environment connect to MAAS as per MAAS/JUJU documentation. | + | 2. Minimum four nodes exist and should have been preconfigured and integrated with JOID please have look into this wiki page https://wiki.opnfv.org/joid/get_started |
| - | 3. Run JUJU bootstrap either on a physical node or on a VM. | + | ==== Deploy MAAS: ==== |
| - | 4. Run juju deployer as below with old bundle. | + | '' $ ./02-maasdeploy.sh <lab and pod name i.e. intelpod5> '' |
| - | Juju Deployer can deploy a preset configuration of charms given a yaml | + | ==== Deploy OPNFV: ==== |
| - | configuration file. There is a configuration file in 'juju-deployer/odl.yaml'. | + | |
| - | ''$ sudo apt-get install juju-deployer'' | + | For kilo openstack, ODL SDN, HA mode in intel pod5 |
| - | ''$ cd juju-deployer'' | + | '' $ ./deploy.sh -o kilo -s odl -t ha -l intelpod5 '' |
| - | ''$ juju-deployer -c odl.yaml -d trusty-icehouse-odl'' | + | ==== Openstack Details ==== |
| + | Details of openstack deployment can be found below: | ||
| - | Juju Deployer will branch its own copy of the remote charms. | + | * Openstack dashboard http:<ip> |
| - | + | * Admin credentials will be admin/openstack. | |
| - | Horizon will be located on the machine 'juju status openstack-dashboard' - | + | * ODL will be located on the machine juju status old-controller |
| - | + | * http:<ip>:8181/dlux/index.html | |
| - | http://<ip>/horizon. | + | * credentials will be admin/admin |
| - | + | ||
| - | Admin credentials will be written to cloud/admin-openrc. | + | |
| - | + | ||
| - | ODL will be located on the machine 'juju status old-controller' | + | |
| - | + | ||
| - | http:<ip>:8181/dlux/index.html | + | |
| - | + | ||
| - | credentials will be admin/admin | + | |
get_started_juju_deploy.1447261724.txt.gz · Last modified: 2015/11/11 17:08 by Narinder Gupta
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
