Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Please add your name in here:

  1. Mark Shostak (AT&T)
  2. shasha guo(ChinaMobile)
  3. Kelvin Edmison (Nokia)
  4. Karine Sevilla (Orange)
  5. Beth Cohen (Verizon)
  6. Trevor Cooper (Intel)
  7. Mark Beierl (VMware)
  8. Nick Chase (Mirantis)
  9. Ahmed El Sawaf (STC)
  10. MICHAEL FIX

Special Notes:

  • Each of the three RM sections will get 20 minutes
  • Given the limited time available, we will focus on identifying issues/actions/next steps, but not solving them right now
  • Weekly RM meetings are intended to
    • Identify owners for new Issues
    • Track open Issues
    • Address technical issues that cannot be resolved online (i.e. resolve stalls)

...

  • RM Core (status) (Mark S.)
    • Issues
    • New technology principles and policy hooks
      • Differentiating underlying technology from features/functions/capabilities (e.g., SRIOV, PCI-PT, EPA, etc.)
      • Principles: Abstraction breakage and custom s/w
      • Principles: What level of h/w details can be exposed at various layers
    • Hardware discussion continuation
      • Storage configuration (10x 960GB vs. 3.2TB w/ 3x logical)
      • DIMM distribution across sockets, memory controllers and buses
      • NIC to socket mapping
      • Physical interface assignment (E/W/OpenStack/Storage, N/S, PXE, OOB LOM)
      • Hardware Objectives, Guidelines and Approach
      • Guidelines vs. Requirements
      • Objectives and Drivers for CNTT to specify h/w
      • To what granularity
      • Implications for RM Comp, RC and RI

...

  • General
    •  None at this time
  •  Core
    •  MXS: Write proposal for SRIOV language in RM (not transition plan)
  • Ops
    •  None at this time
  • Comp
    •  None at this time

...