Skip to end of metadata
  • Created by Former user (Deleted) , last modified on Mar 20, 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 2 Next »

Date

Attendees

Proposed Agenda

  • Review AIs
    • Maithri - add footprint data for microservices (AI)
  • Questions regarding Dell Server Team interlock
  • Collateral status and review - next steps
  • Discussion - WFEaaS - standalone workflow engine
    • On-going effort for removing dependence on on-http
    • on-taskgraph (optional) - subset of 2.0 APIs built into WFE
    • use of gRPC
    • Today, still depends on MongoDB - will be challenging
      • Abstraction "store" that exists - may be able to create another "store" using local FS
      • "store" does not abstract MongoDB semantics
      • Almost all state is stored in MongoDB, except for poller state
    • Feature branch that is holding RESTful and gRPC, test coverage needs work PR exists (modularity branch)
    • Lex - consume MS as JAR, today Lex is a OVA
  • DHCP/TFTP - tightly coupled to workflows, OS install, discovery, cataloing, etc. 
    • Today's OS install WF boot the installer (iPXE bootloader, chainload iPXE script) leverages DHCP/TFTP/HTTP proxy
    • in some extreme cases (static IP on host), could remove 
  • Dell PE servers have iDRAC with virtual media
    • OS deployment microservice exists, mounts virtual media, can do everything, only need workflow, need NFS share with install media
    • tell iDRAC location of share, no need for TFTP, Lex uses static IP (no need for DHCP)
    • RackHD would need to "coordinate" the workflow, take user prompts, create ISO, take results into next REST call to microservice
    • Lex may be able to use microservice by itself, if Lex 

Action items

  •  
  • No labels