Core Committer Weekly Interlock - September 7th 2017
Attendees
Erik Smith
Jean Pierre
Agenda
- 2.20.0 Release 9/4/17, next release 2.21.0 target 9/11/17
- Ease of use of the Vagrant based demo
- Week of 8/7 comment on the slack channel: "At this point I've given up on rackhd. If even the demo requires an old version of ubuntu to run an old version of virtualbox to get it working, I will stick with something simpler."
- priority must be on keeping it simple and easy to use
- Former user (Deleted) to create draft requirements that the team agrees upon, use that to come to consensus on the next steps
- Suggestion 1 - easier to create script to re-use the nightly built docker images + infrasim.
- disadvantage is using docker compose yml missing the network setup, linux specific demo only
- Suggestion 2 - use vagrant script to deploy rackhd (docker) + infrasim (similar to Suggestion #1, but using the vagrant script for deployment to meet an OS agnostic requirement)
- advantage - OS agnostic, virtual switch deployment can be done in a ruby script
- disadvantage - multiple vagrant versions , also thought to be an advantage as the vagrant file version can be bumped.
- Suggestion 3 - run docker in docker, leveraging existing docker images
- privileges, networking, and performance concerns with this solution
- Week of 8/7 comment on the slack channel: "At this point I've given up on rackhd. If even the demo requires an old version of ubuntu to run an old version of virtualbox to get it working, I will stick with something simpler."
- RackHD Tooling Updates
- Ubuntu to be upgraded to 16.04, 18 to be released ~ April 2018
- RackHD epic / Concourse KI to include migration of the CI environment move to Ubuntu 16.04. What has been developed to date for the Concouse env includes the 16.04 migration.
- Former user (Deleted) to provide details on what is available.
- ova scripts will need to be updated (passing a parameter) to move to 16.04
- RackHD epic / Concourse KI to include migration of the CI environment move to Ubuntu 16.04. What has been developed to date for the Concouse env includes the 16.04 migration.
- Node v6 is the current available version, RackHD is running v4.
- v4 will be EOL 4/18
- v8 releases next month
- RackHD Epic to be created to migrate from v4→ v8
- RackHD Epic to be created such that the CI env is testing the latest MongoDB version (Mongo recommending using 3.X + versions only, not supporting anything in the 2.X version family)
- Ubuntu to be upgraded to 16.04, 18 to be released ~ April 2018
Review proposal per Former user (Deleted) email on 8/29 for moving CI to container , moving CI to cloud .
- AI: CC team to review the slides, come back with feedback/answers to the questions posed in the slide deck.
- From QRB meeting notes
- Agreement at OLT that we will be going fully wsman-based and eliminate racadm from workflow support.
- Content finalized, Leo Zhang / Maglev team will work with Thomas Sullivan on generating the official KI.
Test plan: the idrac simulation tool will be used for virtualized testing (PR quality gates/MasterCI) and introduce more Dell physical hardware to the Regression-Baremetal job.
- Former user (Deleted) has downloaded the idrac simulation tool, currently under evaluation
- tool supports only read operations
- RackHD Epic to be created that introduces workflow testing to rackhd CI/CD. This will cover smi service testing, does not cover "plugin" integration tsting
- Former user (Deleted) has downloaded the idrac simulation tool, currently under evaluation
Did not get to the agenda items below:
- Plugfest demo
- Remaining stories to polish-up and merge into master (currently on a fork) have been transitioned back to Veyron, working in this current sprint as the priority for this has escalated.
- BareMetal Regression Pipeline now created/monitored.
- Plan is to monitor for a few weeks, should it then be a gate?
- BareMetal OS install on real hardware currently runs every 2 hours on the nightly docker images. Will need to kick off BareMetal at same time as CI
- Do we then continue to run BareMetal every 2 hours
- Should this be part of the Master CI pipeline, if so then we would need a modification to the Merge Freeze tool to freeze on failure of BareMetal regression tests.
- All SMI Services have been published.
- What documentation is needed, what kind of communication is needed for the open source community?
- Process change for Master CI failures - how long can a developer work on a fix for a Master CI Failure before requiring to back out the change and get back to green?
- How to add stand alone services to the Master CI/CD pipeline (ex SMI Micro Services, UCS etc) right now Master CI is strictly core RackHD
Next meeting will be Thursday September 14.