In an environment deployed on MaaS 1.9 and juju < 1.25, we have some applications that were not deployed with spaces. During the lxc->lxd process, the configs of each lxc are properly converted so we maintain the same network configurations pre-post juju 1->2 upgrade. When adding new units of an application with complex networking to a lxd container, we end up missing the non-default space bindings in the containers.
I would like to propose a method to inject fresh space bindings into the upgraded juju model, perhaps as a yaml definition, and then a way to tag currently up interfaces as having a link to the space while not relying on upstream MaaS provider for the currently deployed machines.
In an environment deployed on MaaS 1.9 and juju < 1.25, we have some applications that were not deployed with spaces. During the lxc->lxd process, the configs of each lxc are properly converted so we maintain the same network configurations pre-post juju 1->2 upgrade. When adding new units of an application with complex networking to a lxd container, we end up missing the non-default space bindings in the containers.
I would like to propose a method to inject fresh space bindings into the upgraded juju model, perhaps as a yaml definition, and then a way to tag currently up interfaces as having a link to the space while not relying on upstream MaaS provider for the currently deployed machines.