Core Committer Weekly Interlock - November 29th 2017

Agenda

1. What is considered a 3rd party service? and what are testing / continuous testing requirements for these 3rd party services?
   1. What is a core RackHD Service, what is a 3rd party service?  
      1. Definition of 3rd party service: services developed outside of Dell EMC org. (ie  mongodb)
      2. Definition of non-core services: services developed by Dell EMC orgs, not released with RackHD (ie UCS and SMI services).  
         1. Continuous functional testing for these non-core services is not required by the RackHD CI/CD process.  They should be tested by their "owners".  
         2. Continuous integration test is required
            1. previous discussions had SMI integration testing with RackHD, currently a WIP migrating to Concourse
            2. Needs to be done for UCS
            3. No requirement at this time where the physical resources are for CI.
         3. Separate release pipeline is required 
            1. SMI services currently has a release pipeline, to be migrated to Concourse
            2. Needs to be done for UCS
2. Bintray publication

   1. limiting to 6 months of sprint releases and 1 week of per-merge builds.

   2. Efforts include cleaning up what we have published today and maintaining that clean-up policy going forward.

   3. Before deleting the older sprint releases from binary, we should copy them to a local store in case someone comes looking (as has happened in the past).

3. Concourse Based Sprint release status
   1.  Still on track for the December 1st sprint Release.
      1. Currently in test.  Concourse "version" file will be merged as a record of the version number.  Will bump version automatically. 
      2. Will plan to stop running Jenkins for Fridays' release, only run Concourse. 
         1. Expect release to take longer to run, now running on physical hardware on both dell and quanta stacks
      3. Sprint Release notes will be part of  Concourse and update the main release page with release notes (starting with Release 2.34.0) : RackHD Release Page 
4. RackHD metrics collection status
   1. feedback from last weeks demo addressed, one more action item to be addressed (have total failures/success releases in a single stat, in progress by the Felouka team )
   2. Plan to demo at CC/QRB meeting next week.
5. Should Force merge to master be allowed in the new CD model
   1. Team agreed this should be disabled.  Did this happen?  Yes (thanks Former user (Deleted)!).  Needs to be updated for on-network, on-topology, smi, ...)
6. Is there a concept of merge freeze in CI/CD (rod)
   1. suggestion to revert -  did not get to finish this discussion.  Will seed through email and finish at the next CC meeting.