Created by Gustavo Niemeyer and last modified
Get this branch:
bzr branch lp:pyjuju
Members of Juju Engineering can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Juju Engineering

Recent revisions

624. By Kapil Thangavelu

merge env-safety-belt

623. By Martin Packman

Merge up latest changes from 0.7 branch

622. By Kapil Thangavelu

merge managed-client, updates for tests and txzk 0.9.8

621. By Kapil Thangavelu

merge upgrade-adds-peers, add new peer rels when upgrading

620. By Kapil Thangavelu

juju home support for config and keys

618. By Kapil Thangavelu

Properly encode maas tags in urls.

Hopefully the last in the sordid history of maas tag support. Revno 616 reverted
attempts to string serialize tags for urls, but which had broken constraint
comparisions. Those string serialization had been attempt in revno 597 and 598
to encode maas tags properly for maas client usage. This branch properly
captures the raw tags string for use by the client, while preserving the
constraint comparisons restored in revno 616.


617. By Martin Packman

Fix os-scheduler-hints constraint to pass correct json layout [r=hazmat,jameinel]

616. By Kapil Thangavelu

Fix broken maas-tags constraint.

The maas tags wasn't properly converting values for comparision
and was not previously testing tag constraint comparisons.

615. By Kapil Thangavelu

Unit process multiple relations in defined order.

Previously when unit agents were being notified of multiple relations, typicaly
at startup, they would process them in essentially random order. This would
complicate things for applications that would have peer relations as well, for
ha or replication, as they couldn't tell if they were being run standalone or
in a cluster/quorum. Instead when a unit has multiple relations, we process
peer relations first followed by client/server relations.


Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.