Skip to end of metadata
  • Created by Former user, last modified by Former user on May 08, 2017
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »


Agenda

  1. BIOS GUID was determined as the way to uniquely identify nodes, however slack dialogue indicates this might not be the best option (Switches, EMC nodes have same BIOS GUID etc)
  2. 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. 
  3. 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.
  4. Merge Guidelines do we have enough information to start process of other folks being able to merge?
    1. RackHD Merge Guidelines   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.
  5. Hound guidelines
    1. Not currently a PR gate, but are there any stylistic rules that should block PRs? 
    2. See hound violations but the step "Pass" in Jenkins : https://github.com/RackHD/RackHD/pull/703
  6. Resource allocation for rackhdci Jenkins
    1. Andre has brought up a concern regarding the number of VMs now deployed to some of the ESXi hosts for the OVA post tests.  Have we done an analysis of the resources required for each of the test and where they will be deployed?
  7. New SMI repositories
    1. What is the merge process going to be for these new repositories?
  • No labels