Page Comparison

...

1. Ease of use of the Vagrant based demo
   1. 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."
      1. Requirements agreed to  by the team:   
         
         1. The demo should be simple, convenient, easy to use / bring up and debug
         2. The environments should be workable across different versions or latest versions. Such as mongodb, docker/virtualbox, 
         3. Host OS independent, Can run on Windows, Linux, or MacOS host system.
         4. Has no impact / dependency of the host network.
         5. utilizes existing nightly RackHD images, does not require building / testing of additional new images
         6.  Uses infrasim for vmbc nodes
         7. can run discovery workflows
         8. can run OS install workflows
         9. can run FIT smoke test suite
         10. The demo solution could support running in cloud (ex: IaaS, PaaS) technically
         11. to include the smi microservice containers  
      2. Review POC from Former user (Deleted)
         1. Ran 2 scripts (1 to get rackhd services up, 1 to get infrasim started)
         2. RackHD code up to date as of the prior sprint release, Infrasim version locked down.
         3. look in to ways for re-using the existing config.json file
         4. https://github.com/RackHD/RackHD/pull/889
      3. Review POC from Former user (Deleted)n
         
         1. https://github.com/RackHD/RackHD/pull/857
         2. RackHD and Infrasim run from source inside a single docker container
      4. AI for the team:  review both POC, next meeting we will identify which one we move forward with
2. RackHD Tooling Updates
   1. Ubuntu to be upgraded to 16.04, 18 to be released ~ April 2018
      1. 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.
         1. Former user (Deleted) to provide details on what is available.
      2. ova scripts will need to be updated (passing a parameter) to move to 16.04
   2. Node v6 is the current available version, RackHD is running v4.
      1. v4 will be EOL 4/18
      2. v8 releases next month 
      3. RackHD Epic to be created to migrate from v4→ v8
         1. Needs to be assigned.  Former user (Deleted)/Maglev team to help create the epic.
   3. 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)
      1. Do we want to support this in Jenkins, Concourse, or both.  Will be part of the Concourse env.
      2. Jenkins side, seems to be a trivial effort to support.  May bring out issues in RackHD and if previous issues have since been resolved.
         1. Plan to try testing with the latest, see what the issues are.  If trivial set of isues, move to the latest.  If many issues encountered, hold off.
         2. Maglev team to create the story and target next sprint.
3. 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?
   1. have your 1 working day to resolve the issue (ie, up to the next MasterCI run at 6:31pm EST) 
   2. if not resolved, code is backed out, the MasterCI job is re-run to ensure that pipeline is returned to Green.
   3. If thought to be resolved, MasterCI to be re-run to ensure the pipeline returns to green

...