pharos:maas_getting_started_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pharos:maas_getting_started_guide [2015/10/22 15:10] Narinder Gupta |
pharos:maas_getting_started_guide [2016/01/06 17:40] (current) Iben Rodriguez |
||
|---|---|---|---|
| Line 53: | Line 53: | ||
| * apt update | * apt update | ||
| * apt upgrade | * apt upgrade | ||
| - | * apt install maas-region-controller | + | * apt install -y maas-region-controller |
| * dpkg-reconfigure maas-region-controller | * dpkg-reconfigure maas-region-controller | ||
| * create new root account | * create new root account | ||
| Line 114: | Line 114: | ||
| ====== Proposed MAAS Poc ====== | ====== Proposed MAAS Poc ====== | ||
| + | |||
| + | STATUS: the MaaS Proof of Concept is complete - now moving status to Pilot Project with expanded roll out. | ||
| + | |||
| + | Labs involved with POC: (Don't add to this list - just update and correct it. The POC is over.) | ||
| + | * Orange Pod 2 - https://wiki.opnfv.org/opnfv-orange | ||
| + | * Intel Pod 6 - https://wiki.opnfv.org/get_started/intel_hosting | ||
| + | * Spirent - https://wiki.opnfv.org/pharos/spirentvctlab | ||
| + | |||
| + | |||
| + | ====== MaaS Pilot ====== | ||
| + | |||
| + | STATUS: the MaaS Pilot Project expands on the POC. POC was completed in November 2015 before the OPNFV Summit. It was agreed to bring in more labs and refine the scope for MaaS within OPNFV labs. | ||
| + | There are two main objectives for MaaS: | ||
| + | * Obtain centralized birds eye dashboard view of all lab resources (bare metal and virtual server hardware) managed by MaaS | ||
| + | * MaaS controllers in each lab will receive requests from Jenkins jobs allowing jump hosts to be provisioned for the installer and SDN controller needed for specific developers or testers | ||
| + | |||
| + | ===== MaaS Pilot Labs ===== | ||
| + | Labs involved with Pilot: (Please update this list with your interest to participate in the Pilot Project) | ||
| + | * Orange Pod 2 - https://wiki.opnfv.org/opnfv-orange - working to resolve a configuration issue and reinstall | ||
| + | * Intel Pod 5 - https://wiki.opnfv.org/get_started/intel_hosting - eta dec 15 DavidB@Orange | ||
| + | * Intel Pod 6 - https://wiki.opnfv.org/get_started/intel_hosting - eta dec 15 DavidB@Orange | ||
| + | * Spirent - https://wiki.opnfv.org/pharos/spirentvctlab - | ||
| + | * Dell Pod 2 - https://wiki.opnfv.org/dell_hosting - TPM Mark Wenning @canonical and Vikram @Dell - too busy | ||
| + | * [[pharos:JuniperLab|Juniper Pod 1]] - [[mailto:iben@vmsec.com|Iben]] is working with Samantha Jian-Pielak <samantha.jian-pielak@canonical.com> - network issue | ||
| + | * [[pharos:JuniperLab|Juniper Pod 2]] - TBD | ||
| + | * CENGN - TBD - Nicolas@Canonical - working on a plan | ||
| + | * UTSA - TBD 2016 | ||
| + | * Huawei - TBD Prakash to inform us on status - no status - working on JOID vitual setup for ONOS Charm checked into JOID - needs documentation | ||
| + | * Ravello - OPNFV Academy for new B release users to evaluate and learn | ||
| + | * Other Pods coming - please add your info to this list | ||
| + | |||
| + | ====== Matrix ====== | ||
| + | There are 16 combinations of installers and sdn controllers being considered for OPNFV Release 2. | ||
| + | These are reflected in this matrix: | ||
| + | | Installer/SDN | OVN | ODL Helium | ODL Lithium | Contrail | ONOS | | ||
| + | | Apex | OVN | Complete | WIP | WIP | ? | | ||
| + | | Compass | OVN | Complete | ? | ? | ? | | ||
| + | | Fuel | OVN | Complete | ? | WIP | ? | | ||
| + | | JOID | OVN | Complete | WIP | Complete | WIP | | ||
| + | |||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| Line 120: | Line 164: | ||
| Above Diagram represent the End state diagram of different labs. Basic idea is to use the community lab to deploy different installer repeatedly and reliably. Which will increase the usage of individual community lab and will be true integration lab with Linux Foundation lab. | Above Diagram represent the End state diagram of different labs. Basic idea is to use the community lab to deploy different installer repeatedly and reliably. Which will increase the usage of individual community lab and will be true integration lab with Linux Foundation lab. | ||
| - | ===== Network assumption: ===== | + | ====== Network Requirements ====== |
| * MAAS regional controller will have connectivity to individual community lab where deployment will take place. | * MAAS regional controller will have connectivity to individual community lab where deployment will take place. | ||
| Line 137: | Line 181: | ||
| - When testing is complete the servers are erased and the pod is rebuilt with the new parameters | - When testing is complete the servers are erased and the pod is rebuilt with the new parameters | ||
| - | References: | + | ====== **References** ====== |
| - | MAAS demo at OPNFV slides: | + | |
| + | MAAS POC Slides OCT 12, 2015 : | ||
| + | {{:pharos:maas.pdf|}} | ||
| + | |||
| + | The original POC work on the original OPNFV Arno release (images and how to build the images) can be found here: http://people.canonical.com/~dduffey/files/OPNFV/ | ||
pharos/maas_getting_started_guide.1445526651.txt.gz · Last modified: 2015/10/22 15:10 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
