Core Commiter Weekly Interlock - April 24,2017

Owned by Former user (Deleted)
Last updated: Apr 24, 2017
2 min read

Rod Frost

Jeanne Ohren

Amy Mullins

Andrew Hou

Felix Yuan

Rahman Muhammad

Brian Parry

Geoff Reid

Peter Pan

Tim Larson

Michael Hepfer


Agenda

  • How do we handle external commits/PR's for testing?  Do they follow our FIT process?   If it fails FIT do we have enough info to tell them what has failed?  Or do we have to handle the failures as a RackHD team? 
    • External mirror is cumbersome - Thursday meeting to discuss how to make this easier for Open Source
    • Any documentation to help with Unit/FIT testing? AI Rod to find Erika FIT documentation and make it public.
    • We will have to support the community with lots of support why PR may fail/.
    • make it easy for folks to use vagrant infrasim for testing on their laptops.
    • Coverage needs to be the same as we have today for the community.   
    • UT Students are running out of time and can't submit any PR's right now due to PE work can't be put in yet.  Their work is dependent on PE work.  Mustang team to work with UT team to get their unit tests in as well as any FIT tests.  Mustang will own this work from UT going forward.   Mustang to pull in UT code into their code/branch.   It will be merged to master with PE code at a later time.  
  • Proposing Event Processing Service - EPS for RackHD hardware/process events 
  • Nightly Build and Release details per rackhdcc slack channel Post:
        P1 issue opened:
    https://rackhd.atlassian.net/browse/RAC-4915
    • The SprintTag failure tracked in RAC-4915. it's fixed and SprintTag is re-running.
    • Master CI also fails due to slave disk full. tracked in  RAC-4921(fixed). let's re-run MasterCI after SprintRelease done.
  • Setting Test criteria for new services 
    •  Do all services need to be integrated in to production test (FIT)?, pr quality gates?
    • UCS-Service is part of production level test, do new services need to be tested/packaged/deployed as part of RackHD ?
    • Image Service
    • PE Service
    •    PE will be docker containers deployments and thus will have its own testing before pushed, still do FIT testing for full integration testing.  AI Amy to create guidelines/criteria for services.
  • Discuss version bumping
    1. https://hardware.corp.emc.com/pages/viewpage.action?pageId=99942703
    2. Update Option F fully automated with only 1 regression run (not 10).   If fail we fix and re-run with a new minor version.