Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
emulab-devel
emulab-devel
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 111
    • Issues 111
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • emulab
  • emulab-develemulab-devel
  • Issues
  • #313

Closed
Open
Opened Jul 06, 2017 by Mike Hibler@hibler
  • Report abuse
  • New issue
Report abuse New issue

Delay post-imaging configuration (aka, `slicefix`) until a node is assigned to an experiment.

Currently, when we re-image a node coming out of an experiment, we do the imaging, then we do the basic cluster-specific customization, and then we free the node, and it sits in PXEWAIT til allocated to an experiment.

An alternative approach is to re-image the node, then send it into PXEWAIT. When the node is then assigned to an experiment, we could first drop into an MFS, run slicefix-ng to do experiment specific customization as well as cluster specific. The specific example was to drop experiment keys (e.g. a root keypair) into the filesystem from a "trusted" environment (the MFS). We could remove the quote marks from "trusted" in the future by doing the whole TPM-based chain of trust thing like our trusted disk loading system (TDLS) did.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
criops2 status:proposed
Assign labels
  • View project labels
Reference: emulab/emulab-devel#313