> I think the obstacle is that most folk are not prepared to give up their languages
s/languages/frameworks, and I agree. One step at a time -- this work is a foundational block that we're building on, not the ultimate solution.
s/languages/frameworks, and I agree. One step at a time -- this work is a foundational block that we're building on, not the ultimate solution.
It looks like the place to make the change would be in Diego in the Executor[0][1] component, which currently implements behaviour in terms of containers (using Linux-Garden as the container system).
So long as you can conceptually fit into the Receptor Actions API[2] it looks as though unikernels would be a plausible addition to Executor. Once you have that, you can either wire into Lattice[3] or a full Cloud Foundry installation as a first-class citizen.
Disclaimer: I'm not as familiar with Diego as other CFers are, so it's possible I'm just making stuff up.
[0] https://github.com/cloudfoundry-incubator/executor
[1] https://github.com/cloudfoundry-incubator/diego-design-notes
[2] https://github.com/cloudfoundry-incubator/receptor/blob/mast...
In any case, we started the Lattice effort last year to make it easier for people to play with Diego without having to stand up a whole Cloud Foundry installation.
My only Lattice-related claim to fame is not knowing what is was: https://github.com/pivotal-cf-experimental/lattice-app/issue...