Update bindings on deployed applications
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned |
Bug Description
Environment is Juju 2.4.3 (upgraded from Juju1), MAAS 1.9.5+bzr4599-
[Goal]
Be able to modify the network space bound to a Juju interface without needing to redeploy an application.
[Issue]
An application deployed on a host with multiple addresses (privnet, pubnet...) has a "wrong" ingress-address (and private-address). For such reason, "network-get <binding_name>" returns the "pubnet" when we want it to return the "privnet". "endpoint-bindings" shows that all bindings are "", and we want a certain binding (or all of them) to be on "privnet-space" (using the private network).
nrpe:monitors provides a public network to nagios:monitors, but nagios container only has a leg on the private network (so, routing fails).
[Use cases]
1) On upgraded Juju environments (from Juju1 to Juju2), endpoint-bindings are "", and we want to set bindings (MAAS provider is still 1.9)
2) In general, modify a binding from space-public to space-private (or any other space)
[Expectation]
1) Be able to reconfigure a binding without the need to redeploy an application
2) Once a binding is reconfigured, config-changed hook would be triggered
tags: | added: sts |
tags: | added: cpe-onsite |
tags: | added: cdo-qa foundations-engine |
Changed in juju: | |
milestone: | none → 2.7-beta1 |
importance: | Wishlist → High |
Changed in juju: | |
milestone: | 2.7-beta1 → 2.7-rc1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Thanks, this is definitely something on our roadmap todo list and we could use field requests for this during planning sprints.