get_started:lflab_maaspoc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
get_started:lflab_maaspoc [2015/09/30 22:03] Iben Rodriguez |
get_started:lflab_maaspoc [2015/10/20 01:50] (current) Narinder Gupta [MaaS Workflow Idea] |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Proposed MAAS Poc ====== | ====== Proposed MAAS Poc ====== | ||
| + | this page docs the POC proposed in Sept 2015 - see details of how to get started with MaaS here: https://wiki.opnfv.org/pharos/maas_getting_started_guide | ||
| {{:pharos:maas_poc_lab.png?600|}} | {{:pharos:maas_poc_lab.png?600|}} | ||
| Line 9: | Line 10: | ||
| ===== Network assumption: ===== | ===== Network assumption: ===== | ||
| - | * MAAS regional controller will have connectivity to individual community lab where deployment will take place. | + | * MAAS regional controller and cluster controller will have connectivity to community lab where deployment will take place. |
| - | * Each community data centre expected to have cluster controller on interface (say eth4) which is connected to different pods jump hosts within data centre at eth4 only. | + | * Each community data centre expected to have regional and cluster controller on interface (say eth4) which is connected to different pods jump hosts within data centre at eth4 only. |
| * Jump hosts and other deployment nodes needs to configure the PXE boot first with eth0 first then eth4 in sequence then to hard disk. | * Jump hosts and other deployment nodes needs to configure the PXE boot first with eth0 first then eth4 in sequence then to hard disk. | ||
| * Cluster controller will run DHCP/DNS/TFTP/PXE on eth4 interface network to control the jump host. | * Cluster controller will run DHCP/DNS/TFTP/PXE on eth4 interface network to control the jump host. | ||
| ====== MaaS Workflow Idea ====== | ====== MaaS Workflow Idea ====== | ||
| + | - Acquire a individual node or group of nodes of deployment through MAAS REST API depend on which community lab needs to use. | ||
| - jenkins server kicks off maas workflow job to initiate pod build out in a lab | - jenkins server kicks off maas workflow job to initiate pod build out in a lab | ||
| - maas regional controller receives job and sends task to cluster controller for the lab | - maas regional controller receives job and sends task to cluster controller for the lab | ||
| - | - cluster controller builds the jump box for OPNFV installer of choice: Fuel, Foreman, RDO, APEX, JOID, COMPASS, etc... | + | - The cluster controller builds the jump box for OPNFV installer of choice: Fuel, Foreman, RDO, APEX, JOID, COMPASS, etc... |
| - | - jumpbox build out OPNFV for the compute nodes of the pod with correct OS and SDN controller: Ubuntu, CentOS, Daylight, Contrail, Midonet, etc | + | - The jumpbox builds out an OPNFV for the compute nodes of the pod with correct OS and SDN controller: Ubuntu, CentOS, Daylight, Contrail, Midonet, etc |
| - FUNCTEST jobs run to validate the environment | - FUNCTEST jobs run to validate the environment | ||
| - A quick QTIP benchmark is run to provide a performance score | - A quick QTIP benchmark is run to provide a performance score | ||
| - More in depth tests can be run as desired: vsperf, storage, yardstick, etc | - More in depth tests can be run as desired: vsperf, storage, yardstick, etc | ||
| - 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 | ||
| - | |||
get_started/lflab_maaspoc.1443650612.txt.gz · Last modified: 2015/09/30 22:03 by Iben Rodriguez
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
