Skip to end of metadata
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 5 Next »

Agenda

  1. Expanded the meeting to a larger audience.   Intent is to cover things like architecture, build/break status, etc.  Plan is to move to 1.5 hours starting at 7:30 EST.
  2. When to start weekly sprints?
  3. 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 HassFormer user (Deleted) and Former user (Deleted) to attend and support the discussion. 
  4. 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
  5. 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  
  • No labels