pyjuju

lp:~fwereade/pyjuju/shadow-trunk-1204

Created by William Reade and last modified
Get this branch:
bzr branch lp:~fwereade/pyjuju/shadow-trunk-1204
Only William Reade can upload to this branch. If you are William Reade please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
William Reade
Project:
pyjuju
Status:
Merged

Recent revisions

516. By William Reade

merge trunk

515. By William Reade

All actions which require remote environment state now sync it

add-unit had lost it somewhere in the pipeline due to expectation of syncing
being retired; terminate-machine never had it; deploy and
[gs]et-constraints' tests slightly improved.

R=hazmat
CC=
https://codereview.appspot.com/5957044

514. By William Reade

ConstraintSet.parse now logs on ignored constraints

R=hazmat
CC=
https://codereview.appspot.com/5956044

513. By William Reade

Block set-constraints, and deploy --constraints, in legacy deployments

R=hazmat
CC=
https://codereview.appspot.com/5952045

512. By William Reade

Implement environment constraints

In user-visible terms:

* bootstrap now accepts --constraints;
* set-constraints now works without --service;
* get-constraints now accepts empty args and outputs env constraints.

In developer terms:

* EnvironmentStateManager has new methods for get/set constraints;
* A new /constraints node is used to store environment constraints (if you
  can think of a better way to do this, bearing in mind that we can't create
  /environment until we've got data for the PA in there, please tell me);
* MachineProvider.bootstrap now requires a Constraints;
* CloudInit now needs a Constraints when setting up a master;
* juju-admin initialize now accept --constraints-data;
* get-constraints and set-constraints take an apparent long way round to
  construct their constraints (they sync environents.yaml so that a provider
  can be created from it by EnvironmentStateManager -- but ESM is used
  internally in a number of places, and the fact that we have a provider
  already available at the juju.control level is not so helpful);
* an awful lot of the diff is tedious test fixing in juju.providers.

R=hazmat
CC=
https://codereview.appspot.com/5957043

511. By William Reade

Small fixes:

* Private EC2 clouds no longer expose constraints
* deploy/add-unit no longer pointlessly warn about legacy keys which remain
  necessary in legacy environments

R=hazmat
CC=
https://codereview.appspot.com/5933058

510. By William Reade

Implement maas-name constraint

Descended from lp:~julian-edwards/juju/name-constraints; but uses new-style
constraints registration.

Also uses a custom ubuntu-series constraint to forbid use of charms written
for systems we can't yet provision with MAAS.

R=allenap, hazmat
CC=
https://codereview.appspot.com/5938050

509. By William Reade

Add get-constraints command

Takes any number of machine names, service names, and unit names; outputs
yaml-formatted dict of name:constraints (showing the full computed
constraints dict for each entity).

R=hazmat
CC=
https://codereview.appspot.com/5935047

508. By William Reade

Providers are now directly responsible for their own constraints

This is really just a rearrangement of code; nothing fundamental has
actually changed, except that Constraints.from_strs is entirely gone; and
trying to construct Constraints(None, data) will no longer produce a viable
specimen.

R=hazmat
CC=
https://codereview.appspot.com/5939046

507. By William Reade

Remove most remaining direct uses of Constraints

The contents of constraint_test will soon scatter amongst the providers;
leaving them in as verification for now.

R=hazmat
CC=
https://codereview.appspot.com/5933050

Branch metadata

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

Subscribers