Updates to MAAS machine data propogated to Juju

Bug #1669729 reported by Peter Sabaini on 2017-03-03
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

I'd like to update metadata on a machine deployed by MAAS, eg. correct tags and AZ.

I can update this in MAAS, but the change is not propagated to Juju.

It would be beneficial to have this updated automatically, or alternatively have a command to sync this data from MAAS to Juju.

Anastasia (anastasia-macmood) wrote :

Re-targeting to "juju" project for tracking for Juju 2.x. Putting it on wishlist.

no longer affects: juju-core
Changed in juju:
status: New → Triaged
importance: Undecided → Wishlist
summary: - Cannot update machine data
+ Updates to MAAS machine data propogated to Juju
Arif Ali (arif-ali) wrote :

This has come up with a customer

2 use cases based on the conversation with the customer


At deployment time some of the AZs were not defined correctly in MAAS, and hence juju had the wrong AZs. They were able to change the AZs in MAAS, but this was then not reflected in juju itself. It would be nice to either have the capability to sync down, like suggested in the original comment, or do be able to change the AZ via the juju CLI.


At certain points a customer may need to move pieces of HW from one rack to another. Typically, with customers, racks are defined for AZs, and therefore in this instance the AZ would change. With various workloads on a cloud or system, it would not be trivial to re-deploy the unit and/or application so that juju shows the correct AZs. So again, the customer can change it in MAAS, and therefore will not propagate to juju, and again as point 1, either automatic propagation or via CLI would be very helpful


AZs are used by customers for support mechanisms to understand (via juju) where the machines may be located and juju is a nice way to show that.

tags: added: community-feedback field-feedback
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers