search

canonical / multipass-blueprints

Blueprint definitions for [`multipass launch`](https://multipass.run)
GNU General Public License v3.0
66 stars 38 forks source link

Initial MAAS workflow #12

Closed sparkiegeek closed 2 years ago

sparkiegeek commented 2 years ago

Add a workflow based on https://maas.io/tutorials/build-a-maas-and-lxd-environment-in-30-minutes-with-multipass-on-ubuntu#5-launch-the-maas-and-lxd-multipass-environment

Saviq commented 2 years ago

Hi @sparkiegeek, you should be aware of #7, where @antongisli tried to do this. The problem is his solution relies on nested VMs, which are not reliable or available on all our substrates.

We'd love a MAAS workflow, but how do we make it so that it doesn't need nesting? Could MAAS drive containers? Could we spin up a couple containers and hook those up to MAAS?

Long term we want workflows to be potentially comprised of multiple nodes, so could those nodes hook up to MAAS?

sparkiegeek commented 2 years ago

Hi @sparkiegeek, you should be aware of #7, where @antongisli tried to do this. The problem is his solution relies on nested VMs, which are not reliable or available on all our substrates.

Ah, thanks for the pointer. Was "sure" that we should try this :)

We'd love a MAAS workflow, but how do we make it so that it doesn't need nesting? Could MAAS drive containers? Could we spin up a couple containers and hook those up to MAAS?

It cannot (and is not on the roadmap)

Long term we want workflows to be potentially comprised of multiple nodes, so could those nodes hook up to MAAS?

That would be amazing

antongisli commented 2 years ago

let us know @Saviq when we can describe e.g. bridge networks and a flat structure for VMs, at that point I think we can drop nested VMs and a workflow could be a possibility.