Core Commiter Weekly Interlock - May 1, 2017

Agenda

Expanded the meeting to a larger audience and time slot. Intent is to cover things like architecture, build/break status, etc. Plan is to move to 1.5 hours starting at 7:30 CST/830 EST. Due to conflicts with other meetings it will be difficult to move to 90. Plan is to leave it regular schedule.
When to start weekly sprints? AI Former user (Deleted) are we ready to go to weekly releases? If so plan is to start weekly sprints on May 8th.
During the RackHD Redfish Interlock with Jon Hass , it was discussed that nodes are being redundantly created for PXE booted nodes that are discovered by WSMAN (or vice versa where nodes are discovered via WSMAN and then PXE booted). Need to determine how to best manage the co-existence of PXE and WSMAN based discovery. Also to include poller management (WSMAN is starting it's own set of pollers). Will forward meeting to Jon Hass, Former user (Deleted) and Former user (Deleted) to attend and support the discussion.
1. update - Use BIOS-GUID as the unique ID (works across all vendors). AI Former user (Deleted) to open up a RAC-Issue for resolution. Tracked in this issue: RAC-4976 - Getting issue details... STATUS
Should Ansible Playbooks be supported/delivered as part of RackHD?
1. Came up as a solution to retrieve Symphony driver versions. Code was developed a long time ago, not kept up to date. Efforts to bring it up to date and add it to RackHD deployment would be required.
2. Including Kranti Uppala and Former user (Deleted) to the discussion
  1. Update Add an RI for this effort AI Amy Mullins to lead this effort.
Requirements on resources on RackHD OVA (memory, disk, cpu)
1. Again, came up in the context of Symphony. Current OVA is generated with 1 GB RAM and POST test includes only 3 nodes and ~ 12 pollers. Simple Symphony dev/test config has 4-5 nodes (~16-20 pollers) with some switches (not an exact number available, but will increase the poller (and therefore resources required))
2. Previously articulated min RAM requirement was 4G .
  1. https://github.com/RackHD/RackHD/blob/master/example/Vagrantfile#L13:L15
3. Tracked in this issue: RAC-4954 - Getting issue details... STATUS
  1. Update - need to lock down specific requirements for CPU/Memory etc. Do we need to go to 8 GB in near future? Any metrics available to indicate the need? AI Leo Zhang are you aware of any metrics? Current plan is to go to 4 GB as stated in the above mentioned PR.
Merge Guidelines do we have enough information to start process of other folks being able to merge?
1. RackHD Code Review and Merge Process AI All to review and have updates by next CC meeting. Each team has a CC that is responsible for training and overlooking the process for each team. AI Amy Mullins to provide guidelines from Symphony. Need to communicate the process of how to dub someone ready to be CC.