Core Commiter Weekly Interlock - Feb 27th,2017

Agenda items that need to be discussed at upcoming core committer meeting.

Please list below anything you feel needs to be discussed. For higher priority items please place at the top of the queue.

Communicate Plan to Community of the new release naming (2.0.x) API changes warrant this release naming change AI Former user (Deleted)
Go/No Go for 1.3.0
1. Any open issues?
  1. As of 2/24/17 morning timeframe, the only one to be discussed is RAC-4356 - Getting issue details... STATUS and usability requirements PR has been submitted and needs approval https://github.com/RackHD/RackHD/pull/650
  2. As of 2/27/17 possible OVA build issue AI Amy Mullins to take deeper dive
  3. As of 2/27/17 delay no/go no by 1 day due to build issues per Peter Pan email
  4. Build Status :
    Weekend Issues are resolved. It’s expected restored green tonight.
    
    RAC-4372
    Fixed
    RAC-4374
    Fixed
    RAC-4383
    Workaround so far.
When debugging this issue : RAC-4125 - Getting issue details... STATUS Anitha found this to be a compatibility issue with mongodb version 2.6.10. She was able to reproduce this error when upgrading my mongodb from 2.4.9 to 2.6.10. Current recommended workaround is to stay at 2.4.9. Our scripts currently pull the latest version of Mongodb. Should we be considering locking down the mongodb version?Document which version of the package was tested with. All external dependencies needs to be documented and controlled (what did we test with?). Every release needs to document all external dependencies with what we tested against. Make sure nightly regression testing is against the latest external dependencies. 1.3.0 release notes need to state that Mongo should stay at 2.4.9 due to this issue. Amy Mullins to look into how to capture what we are pulling down for regression testing to be put into the release notes Thomas Sullivan and Former user (Deleted)
Bug Triage from QRB team how to assign and prioritize AI Thomas Sullivan to communicate process via email.
PR process Do we verify submitter has appropriate test cases in place?
Best practice for designing URIs for micro services REST APIs. API should be semantic versioned, version reported through swagger. MicroService will have its own namespace decoupled from the API
Defects -
- Deleting node doesn't delete workflows related to the node. SMI-4 (design decision was to cancel workflows and delete independent of deleting the node) Enhancement request to verify delete of node and delete the active workflows. What happens to catalog on a delete? Former user (Deleted) to create RAC enhancement request
- RackHD should block rediscovering the same node more than once. SMI-10 Former user (Deleted) to create RAC issue possibly resolved with RAC-490
- RackHD Doc - Id shows catalog identifier not identifier for node, http://rackhd.readthedocs.io/en/latest/rackhd/nodes.html Former user (Deleted) create RAC issue for documentation
Update the git submodules of RackHD repo per release. Felix? Should be updated automatically AI Former user (Deleted) to look into with Former user (Deleted)

RAC-4372	Fixed
RAC-4374	Fixed
RAC-4383	Workaround so far.