workflow: provision after build #694

Open
hannesm opened this Issue Nov 20, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@hannesm
Member

hannesm commented Nov 20, 2016

This superseeds #631 and addresses #691 (comment)

(updated to reflect changes merged via #703)

At the very moment in master:

  • mirage configure won't call out to opam. It will configure the unikernel: generate a main.ml and a Makefile.
  • make depend will install the missing dependencies
  • make compiles the OCaml code as before
  • crunch is done during build

After XXX, we should be able to do:

  • mirage configure - same as above
  • make depend - install forgotten packages
  • make - compile
  • provision - link/add secret keys to existing unikernel image. The build host does not need to be trusted anymore!

There are still some missing pieces (how to actually do the provisioning -- easy with block devices: just provide the device during startup, but unclear how to do crunch here).

I'd be happy to use for MirageOS3 the intermediate solution, but if there are people who have strong ideas and know how to do the rest, we can also target the full provisioning workflow.

@hannesm

This comment has been minimized.

Show comment
Hide comment
@hannesm

hannesm Dec 10, 2016

Member

now that #703 is merged, I'd leave this open until we have a plan for the provisioning step (esp regarding Crunch to be applied/linked after the unikernel is built, see #489)

Member

hannesm commented Dec 10, 2016

now that #703 is merged, I'd leave this open until we have a plan for the provisioning step (esp regarding Crunch to be applied/linked after the unikernel is built, see #489)

@hannesm hannesm changed the title from workflow: configure, install dependencies, build, provision to workflow: provision after build Dec 10, 2016

@hannesm hannesm referenced this issue Dec 24, 2016

Merged

Syslog #749

@hannesm

This comment has been minimized.

Show comment
Hide comment
@hannesm

hannesm Feb 3, 2017

Member

#204 and #423 are related to this as well.. I guess we'll need a clean proposal how the MirageOS-X (for X > 3.0.0) should work (as mentioned above, I'd hope to have a configure - build - provision workflow -- currently the provision happens while building)

Member

hannesm commented Feb 3, 2017

#204 and #423 are related to this as well.. I guess we'll need a clean proposal how the MirageOS-X (for X > 3.0.0) should work (as mentioned above, I'd hope to have a configure - build - provision workflow -- currently the provision happens while building)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment