2017-02-15 RackHD Architecture Forum Meeting notes
Date
Attendees
- Former user (Deleted)
- Former user (Deleted)
- James King
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
Proposed Agenda
Did not get to the items in blue below.
- Review AIs - DONE
- Discuss and finalize Guiding Principles
- #9 Stateless microservices
- stateless = state not held in the code
- #5 non-disruptive upgrades
- is this referring to the services or the managed systems or both? Clarify this: AI
- #3A secure external interfaces
- was read as the security was "optional". Clarify AI
- #9 Stateless microservices
- Proposed near term discussion topics
- Footprint reduction
- With an expectation of maintained performance
- There is a relationship to scaling
- A footprint relative to scale
- Unified Data Model
- RackHD native (based on IPMI and microkernel catalog)
- Advance PE Service (based on WS-MAN catalog)
- Voyager
- graph-based topology database
- Grooming - Update based on changes, removal of stale information
- Cache coherency - maintaining consistent "views" into the data from all consumers of the data
- Brownfield vs. Greenfield deployment (non-intrusive vs. intrusive)
- Advanced PE Services
- Service Now (TaaS/Iaas)
- Dell Server team
- Scaling
- Scale "up" - within a neighborhood (single RackHD instance / L2 broadcast domain)
- Scale "out" - between neighborhoods (aggregation of RackHD instances)
- Jon Haas vision - 10Ks to 100Ks nodes
- Workflow Engine As A Service (WFEaaS)
- CoprHD, Project-C, others?
- Footprint reduction
- Discuss plan for presentation to Dell server team - updated architecture, plans to support their use case
- Maithri to provide some background to help frame use case
Action items
- @jgolio Clarify Guiding Principle #5
- @jgolio Clarify Guiding Principle #3A
- @jgolio Clarify Guiding Principle #9