Merge lp:~rogpeppe/juju-core/454-1.16-maas-changes into lp:juju-core/1.16
Status: | Merged |
---|---|
Approved by: | Roger Peppe |
Approved revision: | no longer in the source branch. |
Merged at revision: | 1974 |
Proposed branch: | lp:~rogpeppe/juju-core/454-1.16-maas-changes |
Merge into: | lp:juju-core/1.16 |
Diff against target: |
935 lines (+267/-85) 10 files modified
provider/maas/config.go (+22/-2) provider/maas/config_test.go (+33/-3) provider/maas/environ.go (+4/-2) provider/maas/environ_test.go (+36/-36) provider/maas/environprovider.go (+18/-1) provider/maas/environprovider_test.go (+44/-3) provider/maas/instance_test.go (+15/-13) provider/maas/maas_test.go (+24/-2) provider/maas/storage.go (+22/-2) provider/maas/storage_test.go (+49/-21) |
To merge this branch: | bzr merge lp:~rogpeppe/juju-core/454-1.16-maas-changes |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+191413@code.launchpad.net |
Commit message
provider/maas: instance and storage uniqueness
This merges the following branches from trunk.
Fixes https:/
-------
revno: 1990 [merge]
author: Roger Peppe <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 13:12:52 +0000
message:
[r=rogpeppe] provider/maas: do not use environ-uuid
As pointed out by fwereade, it could be
confusing to have two things in the system
that both purport to be a uuid for the environ.
Also make the MAAS EnvironProvider
check that we're not changing the maas-agent-name.
https:/
-------
revno: 1989 [merge]
author: Julian Edwards <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 06:11:50 +0000
message:
[r=axwalk],[bug=1081247],[bug=1229275] Use the environment's UUID as a file prefix for all files in MAAS private storage to prevent different environments from overlapping.
-------
-------
revno: 1985 [merge]
author: Gavin Panella <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 01:56:42 +0000
message:
[r=wallyworld] Use environment-uuid when interacting with MAAS
The environment-uuid is passed - as agent_name - to MAAS when acquiring
and listing nodes. This will allow multiple Juju environments to coexist
in a single MAAS user's account.
In addition, it prevents environment-uuid from being set in
environments.
intended to stop people from inadvertently clobbering existing
environments.
It also starts cleaning up MAAS's providerSuite by dropping the environ
attribute in favour of makeEnviron(). The former was initialised to a
half-working environ that caused strange test failures.
https:/
-------
revno: 1984 [merge]
author: Gavin Panella <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Tue 2013-10-15 17:03:22 +0000
message:
[r=gz] provider/maas: Add environment UUID
We need a way to uniquely identify those machines in MAAS belonging to
a Juju environment. Until now Juju's MAAS provider has assumed that
all the machines that are allocated, are allocated to the environment
that Juju is working with. This is obviously wrong, and can be
disastrous.
This is the first part of work on the MAAS provider to use a unique
identifier for an environment. MAAS will record this identifier
(called 'agent_name' in MAAS) and allow its use for filtering.
This branch merely adds the UUID to the environment's config.
https:/
R=rogpeppe, rvb
Description of the change
provider/maas: instance and storage uniqueness
This merges the following branches from trunk.
Fixes https:/
-------
revno: 1990 [merge]
author: Roger Peppe <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 13:12:52 +0000
message:
[r=rogpeppe] provider/maas: do not use environ-uuid
As pointed out by fwereade, it could be
confusing to have two things in the system
that both purport to be a uuid for the environ.
Also make the MAAS EnvironProvider
check that we're not changing the maas-agent-name.
https:/
-------
revno: 1989 [merge]
author: Julian Edwards <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 06:11:50 +0000
message:
[r=axwalk],[bug=1081247],[bug=1229275] Use the environment's UUID as a file prefix for all files in MAAS private storage to prevent different environments from overlapping.
-------
-------
revno: 1985 [merge]
author: Gavin Panella <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 01:56:42 +0000
message:
[r=wallyworld] Use environment-uuid when interacting with MAAS
The environment-uuid is passed - as agent_name - to MAAS when acquiring
and listing nodes. This will allow multiple Juju environments to coexist
in a single MAAS user's account.
In addition, it prevents environment-uuid from being set in
environments.
intended to stop people from inadvertently clobbering existing
environments.
It also starts cleaning up MAAS's providerSuite by dropping the environ
attribute in favour of makeEnviron(). The former was initialised to a
half-working environ that caused strange test failures.
https:/
-------
revno: 1984 [merge]
author: Gavin Panella <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Tue 2013-10-15 17:03:22 +0000
message:
[r=gz] provider/maas: Add environment UUID
We need a way to uniquely identify those machines in MAAS belonging to
a Juju environment. Until now Juju's MAAS provider has assumed that
all the machines that are allocated, are allocated to the environment
that Juju is working with. This is obviously wrong, and can be
disastrous.
This is the first part of work on the MAAS provider to use a unique
identifier for an environment. MAAS will record this identifier
(called 'agent_name' in MAAS) and allow its use for filtering.
This branch merely adds the UUID to the environment's config.
https:/
R=rogpeppe, rvb
Reviewers: mp+191413_ code.launchpad. net,
Message:
Please take a look.
Description:
provider/maas: instance and storage uniqueness
This merges the following branches from trunk. /launchpad. net/bugs/ 1229275
Fixes https:/
------- ------- ------- ------- ------- ------- ------- ------- ----
revno: 1990 [merge]
author: Roger Peppe <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 13:12:52 +0000
message:
[r=rogpeppe] provider/maas: do not use environ-uuid
As pointed out by fwereade, it could be
confusing to have two things in the system
that both purport to be a uuid for the environ.
Also make the MAAS EnvironProvider .Validate
check that we're not changing the maas-agent-name.
https:/ /codereview. appspot. com/14741045/ ------- ------- ------- ------- ------- ------- ------- ----
-------
revno: 1989 [merge] ------- ------- ------- ------- ------- ------- ------- ----
author: Julian Edwards <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 06:11:50 +0000
message:
[r=axwalk],[bug=1081247],[bug=1229275] Use the environment's UUID as a
file prefix for all files in MAAS private storage to prevent different
environments from overlapping.
-------
------- ------- ------- ------- ------- ------- ------- ------- ----
revno: 1985 [merge]
author: Gavin Panella <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Wed 2013-10-16 01:56:42 +0000
message:
[r=wallyworld] Use environment-uuid when interacting with MAAS
The environment-uuid is passed - as agent_name - to MAAS when
acquiring
and listing nodes. This will allow multiple Juju environments to
coexist
in a single MAAS user's account.
In addition, it prevents environment-uuid from being set in .yaml, and returns an appropriate error message. This is
environments
intended to stop people from inadvertently clobbering existing
environments.
It also starts cleaning up MAAS's providerSuite by dropping the
environ
attribute in favour of makeEnviron(). The former was initialised to a
half-working environ that caused strange test failures.
https:/ /codereview. appspot. com/14644045/ ------- ------- ------- ------- ------- ------- ------- ----
-------
revno: 1984 [merge]
author: Gavin Panella <email address hidden>
committer: Tarmac
branch nick: juju-core
timestamp: Tue 2013-10-15 17:03:22 +0000
message:
[r=gz] provider/maas: Add environment UUID
We need a way to uniquely identify those machines in MAAS belonging to
a Juju environment. Until now Juju's MAAS provider has assumed that
all the machines that are allocated, are allocated to the environment
that Juju is working with. This is obviously wrong, and can be
disastrous.
This is the first part of work on the MAAS provider to use a unique
identifier for an environment. MAAS will record this identifier
(called 'agent_name' in MAAS) and allow its use for filtering.
This branch merely adds the UUID to the environment's config.
https:/ /codereview. appspot. com/14696043/
R=rogpeppe, rvb
https:/ /code.launchpad .net/~rogpeppe/ juju-core/ 454-1.16- maas-changes/ +merge/ 191413
(do not edit description out o...