Machines should know their provider type
Bug #854230 reported by
Kapil Thangavelu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Undecided
|
Kapil Thangavelu | ||
Bug Description
We need to distinguish provider type for deployment of units.
This branch modifies the add_machine_state to take a mandatory
argument of the provider type.
Related branches
lp:~hazmat/pyjuju/machine-with-type
- Gustavo Niemeyer: Approve
- Jim Baker: Pending requested
-
Diff: 490 lines (+106/-33)23 files modifiedjuju/control/add_unit.py (+2/-6)
juju/control/deploy.py (+1/-3)
juju/control/initialize.py (+7/-1)
juju/control/tests/test_initialize.py (+4/-2)
juju/providers/common/cloudinit.py (+10/-4)
juju/providers/common/tests/data/cloud_init_bootstrap (+1/-1)
juju/providers/common/tests/data/cloud_init_bootstrap_zookeepers (+1/-1)
juju/providers/dummy.py (+4/-0)
juju/providers/ec2/__init__.py (+4/-0)
juju/providers/ec2/launch.py (+0/-1)
juju/providers/ec2/tests/data/bootstrap_cloud_init (+1/-1)
juju/providers/ec2/tests/test_provider.py (+1/-0)
juju/providers/orchestra/__init__.py (+4/-0)
juju/providers/orchestra/tests/data/bootstrap_user_data (+1/-1)
juju/providers/tests/test_dummy.py (+3/-0)
juju/state/environment.py (+6/-0)
juju/state/initialize.py (+15/-1)
juju/state/machine.py (+3/-2)
juju/state/placement.py (+20/-2)
juju/state/tests/test_environment.py (+7/-0)
juju/state/tests/test_initialize.py (+5/-1)
juju/state/tests/test_machine.py (+2/-2)
juju/state/tests/test_placement.py (+4/-4)
| Changed in juju: | |
| assignee: | nobody → Kapil Thangavelu (hazmat) |
| milestone: | none → eureka |
| status: | New → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
