...

• RM Core (status) (Mark S.)
  • Issues
  • UNH lab hardware approval (if needed)
  • SR-IOV continuation (if needed)
  • EPA (if needed) //deferred
  • 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
  •  None at this timeMXS: Follow up on rotating media for UNH servers
  •  MXS: Follow up on constraints precluding NVMe usage
  •  MXS: Write proposal for SRIOV language in RM (not transition plan)
• Ops
  •  None at this time
• Comp
  •  None at this time

Minutes:

• General
  • Nil
   CoreNil
  • Reviewed LNF/GSMA anti-trust policy
•  Core
  1. General discussion about UNH lap approval, Reached the following conclusions:
  2. Current PoR is 3.2TB of SSD behind a RAiD controller. ex[psed as
  3. Consensus is 3.2TB is probably too restrictive
  4. Trevor proposed we investigate supplementing the SATA SSDs with rotating media
  5. Ultimately concluded:
     1. CNTT RI to use an OSD, in snotead of hyper-converged
     2. Initially maintain homogeneous server fram forFR
     3. Investigate rotating media
     4. Investigate why NVMe i is not an option.
     5. Organization would be root volume on SDD on the host
  6. SRIOV: Aligned on creating transition plan as an appendix to the RM
  7. Mark S. took action to write a draft of the language for the RM regarding the SRIOV (not the annex or transition plan)
• Ops
  • Nil
• Comp
  • Nil