Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • emulab-devel emulab-devel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 166
    • Issues 166
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emulabemulab
  • emulab-develemulab-devel
  • Issues
  • #89
Closed
Open
Issue created May 17, 2016 by Eric Eide@eeideMaintainer

Parameterized and non-parameterized geni-lib-based profiles should be evaluated at the same times

In the PhantomNet meeting today, I learned that we have different rules about when parameterized and non-parameterized geni-lib profiles are evaluated.

In particular, it was claimed that we do not evaluate non-parameterized geni-lib profiles at every swap-in. We do evaluate parameterized geni-lib profiles at every swap-in, for somewhat obvious reasons.

My opinion is that this is inconsistent and potentially problematic, and we should change this behavior. We should evaluate non-parameterized geni-lib profiles at all the times when we evaluate parameterized profiles.

As a particular issue, consider the PhantomNet extension to geni-lib. One reason for making this extension is to allow us to update/fix bugs in the underlying PhantomNet support without requiring users to change their profiles.

For this to work, non-parameterized geni-lib profiles that use the PhantomNet extension need to be (re-)evaluated when the PhantomNet extension is updated.

(I may be wrong about when things are evaluated; if so, I apologize.)

Assignee
Assign to
Time tracking