User Tools

Site Tools


projects:armband:armbandlab

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
projects:armband:armbandlab [2016/01/08 16:21]
Bob Monkman
projects:armband:armbandlab [2016/01/08 16:38] (current)
Bob Monkman
Line 45: Line 45:
  
 a. Creating an initial arm64-based bootstrap image that is served to bare metal servers that boot on a Fuel Master’s admin network ​ a. Creating an initial arm64-based bootstrap image that is served to bare metal servers that boot on a Fuel Master’s admin network ​
 +     Short Description:​ Build a Fuel Bootstrap Linux Image to enable the discovery of bare metal servers
 + Status:  ​
 +     This has been built for Fuel 6.1 and has been successfully used on the ARM servers in the Enea Pharos Lab (Cavium, Applied Micro, and SoftIron/​AMD) We are currently building this again for Fuel 7 (and soon for Fuel 8).
 +     This is in good shape. It will be included in the Fuel “ISO” for arm64, in similar fashion to the bootstrap image included for x86.
  
 b. Providing a set of repositories,​ both standard upstream Ubuntu (or Centos) repos as well as MOS (Mirantis Open Stack) repos, that contain arm64-based packages for all necessary target configurations (controller,​ compute, ODL, HA, etc) that can provide for both the base target image that is booted on deployed targets and for the puppet-based installation/​configuration that occurs after the initial target images are booted on controller and compute nodes. ​ b. Providing a set of repositories,​ both standard upstream Ubuntu (or Centos) repos as well as MOS (Mirantis Open Stack) repos, that contain arm64-based packages for all necessary target configurations (controller,​ compute, ODL, HA, etc) that can provide for both the base target image that is booted on deployed targets and for the puppet-based installation/​configuration that occurs after the initial target images are booted on controller and compute nodes. ​
 +
 +   Short Description:​ Preparing arm64 repositories for all the layers of packages, from standard Ubuntu to MOS to specials for OPNFV
 +   ​Status: ​
 +   We have assembled these packages by hand (pointing at an ubuntu repo and building the MOS packages) for a combo of public and private repos.
 +   We will rebuild the arm64 packages (particularly those in the MOS repo) and put them in a public mirror hosted by Enea for the time being (until Mirantis consumes and supports this repo in their upstream MOS repo for Fuel).
 +   We are currently setting this up, and targeting building the repo for the Fuel 7 and soon Fuel 8 versions of the MOS repo.
 +
  
 c. Porting the Fuel business-logic code that creates initial target distros and drives the installation/​configuration of the various Openstack/​ODL/​OPNFV parts when Fuel does the install. ​ c. Porting the Fuel business-logic code that creates initial target distros and drives the installation/​configuration of the various Openstack/​ODL/​OPNFV parts when Fuel does the install. ​
 +
 +        Short Description:​ This is the machinery that does what Fuel does – we change the “x86” or “amd64” specifiers for packages to also support “arm64”.
 + Status: ​
 + We have done this for Fuel 6.1 (what’s in Arno SR1) in an exploratory manner (I.e. Not necessarily optimized to push upstream). We are starting this arm64 porting exercise for Fuel 7 (and eventually 8) and will be doing it in a fashion more suited to upstream.
  
 d. Overall Status: ​ d. Overall Status: ​
  
 + i. We have deployed Arno SR1 using Fuel on both a 2-node Cavium server environment and a 2-node Applied Micro (APM) server environment.
  
- ​2. Porting Functest to arm64 + ii. We have deployed Arno SR1 with ODL using Fuel on a 2-node APM environment. 
 + 
 + iii. We have not yet deployed Arno SR1 with HA controllers on a 5-node arm64 server environment  
 + 
 + iv. We are putting 4 nodes together to do a 3-controller in HA configuration with 1 compute to test HA controllers on arm64. This started today and will continue tomorrow and into early next week. 
 + 
 + v. We are currently bringing up Fuel 7 and are putting in place a public mirror to host arm64 repos for things like MOS that are not already available publicly for ARM. Note: the MOS (Mirantis OpenStack) is just deviations/​patches applied to Openstack and its components by Mirantis to “improve” Openstack. This is done currently (for Arno as well as Brahmaputra) when using the Fuel installer. 
 + 
 +  ​2. Porting Functest to arm64 
  
 -a. We have run a number of functest tests against an “opnfv-like” install (I.e. Not installed by an installer) of Openstack and ODL in our dev lab. -a. We have run a number of functest tests against an “opnfv-like” install (I.e. Not installed by an installer) of Openstack and ODL in our dev lab.
Line 74: Line 98:
 ---- ----
 ===== Other Hardware Approaches ===== ===== Other Hardware Approaches =====
- 
- 
----- 
-Latest Lab Status 
-Report as of Jan 6 
- 
-2. Creating an initial arm64-based bootstrap image that is served to bare metal servers that boot on a Fuel Master’s admin network ​ 
- Short Description:​ Build a Fuel Bootstrap Linux Image to enable the discovery of bare metal servers 
- Status:  ​ 
- This has been built for Fuel 6.1 and has been successfully used on the ARM servers in the Enea Pharos Lab (Cavium, Applied Micro, and SoftIron/​AMD) 
- We are currently building this again for Fuel 7 (and soon for Fuel 8). 
- This is in good shape. 
- It will be included in the Fuel “ISO” for arm64, in similar fashion to the bootstrap image included for x86. 
-2. Providing a set of repositories,​ both standard upstream Ubuntu (or Centos) repos as well as MOS (Mirantis Open Stack) repos, that contain arm64-based packages for all necessary target configurations (controller,​ compute, ODL, HA, etc) that can provide for both the base target image that is booted on deployed targets and for the puppet-based installation/​configuration that occurs after the initial target images are booted on controller and compute nodes. ​ 
- Short Description:​ Preparing arm64 repositories for all the layers of packages, from standard Ubuntu to MOS to specials for OPNFV 
- Status: ​ 
- We have assembled these packages by hand (pointing at an ubuntu repo and building the MOS packages) for a combo of public and private repos. 
- We will rebuild the arm64 packages (particularly those in the MOS repo) and put them in a public mirror hosted by Enea for the time being (until Mirantis consumes and supports this repo in their upstream MOS repo for Fuel). 
- We are currently setting this up, and targeting building the repo for the Fuel 7 and soon Fuel 8 versions of the MOS repo. 
- 
-3. Porting the Fuel business-logic code that creates initial target distros and drives the installation/​configuration of the various Openstack/​ODL/​OPNFV parts when Fuel does the install. ​ 
- Short Description:​ This is the machinery that does what Fuel does – we change the “x86” or “amd64” specifiers for packages to also support “arm64”. 
- Status: ​ 
- We have done this for Fuel 6.1 (what’s in Arno SR1) in an exploratory manner (I.e. Not necessarily optimized to push upstream) 
- We are starting this arm64 porting exercise for Fuel 7 (and eventually 8) and will be doing it in a fashion more suited to upstream. 
- Overall Status:  ​ 
- We have deployed Arno SR1 using Fuel on both a 2-node Cavium server environment and a 2-node Applied Micro (APM) server environment. 
- We have deployed Arno SR1 with ODL using Fuel on a 2-node APM environment. 
- We have not yet deployed Arno SR1 with HA controllers on a 5-node arm64 server environment ​ 
- We are putting 4 nodes together to do a 3-controller in HA configuration with 1 compute to test HA controllers on arm64. 
- This started today and will continue tomorrow and into early next week. 
- We are currently bringing up Fuel 7 and are putting in place a public mirror to host arm64 repos for things like MOS that are not already available publicly for ARM. Note: the MOS (Mirantis OpenStack) is just deviations/​patches applied to Openstack and its components by Mirantis to “improve” Openstack. This is done currently (for Arno as well as Brahmaputra) when using the Fuel installer. 
- 
-4. Porting Functest to arm64  
-1. We have run a number of functest tests against an “opnfv-like” install (I.e. Not installed by an installer) of Openstack and ODL in our dev lab. 
-2. We will next run functest against our 4-node HA pharos environment (installed by Fuel 6.1) when we have it running. 
-3. We will also run functest against a 2-node non-HA with ODL pharos environment. 
-4. Portability issues here are so far mainly related to the test image that is launched, which is by default a small x86-based image called “cirros”. ​ We are replacing this with a similar small arm64-based image. 
-5. The status for the Functest effort is not as detailed as for Fuel.  We’ve been practicing with Functest both on x86-based deployments and on non-Fuel-installed (I.e. “by hand”) arm64 deployments. 
-  Once we have the two functions above (Fuel for arm64 and Functest for arm64), the Pharos Lab should be ready for Jenkins integration. ​ It’s possible we can start on that effort earlier, but I think I’ve gotten the feedback that we should start the integration after Fuel/​Functest are ready. ​ If that’s not the case, we are up for trying to start Jenkins integration sooner. 
- 
- 
  
 Here is a low-cost ARMv8 platform described at 96boards.com at this link: https://​www.96boards.org/​products/​ce/​dragonboard410c/​ Here is a low-cost ARMv8 platform described at 96boards.com at this link: https://​www.96boards.org/​products/​ce/​dragonboard410c/​
  
 We [at Enea] have powered this up (it comes with Android) and installed Ubuntu. ​ It's certainly a challenging form-factor,​ as there'​s no built-in Ethernet, but it has wifi and we have added a 100mb USB enet dongle. ​ This isn't awesome, but it's much closer to an OPNFV-capable ARMv8 SoC than BBBrC or rPi.  One blocker with this device is that getting KVM running on it is not simple due to some bootstrap challenges. ​ Anyone with interest or experience, please comment as well!  We [at Enea] have powered this up (it comes with Android) and installed Ubuntu. ​ It's certainly a challenging form-factor,​ as there'​s no built-in Ethernet, but it has wifi and we have added a 100mb USB enet dongle. ​ This isn't awesome, but it's much closer to an OPNFV-capable ARMv8 SoC than BBBrC or rPi.  One blocker with this device is that getting KVM running on it is not simple due to some bootstrap challenges. ​ Anyone with interest or experience, please comment as well! 
projects/armband/armbandlab.1452270070.txt.gz · Last modified: 2016/01/08 16:21 by Bob Monkman