Merge lp:~free.ekanayaka/landscape-client/juju-machine-registration into lp:~landscape/landscape-client/trunk
Status: | Merged |
---|---|
Approved by: | Free Ekanayaka |
Approved revision: | 789 |
Merged at revision: | 784 |
Proposed branch: | lp:~free.ekanayaka/landscape-client/juju-machine-registration |
Merge into: | lp:~landscape/landscape-client/trunk |
Diff against target: |
476 lines (+105/-71) 9 files modified
landscape/__init__.py (+3/-1) landscape/broker/registration.py (+16/-7) landscape/broker/tests/test_exchange.py (+4/-4) landscape/broker/tests/test_registration.py (+38/-18) landscape/broker/tests/test_store.py (+3/-4) landscape/manager/tests/test_customgraph.py (+8/-10) landscape/manager/tests/test_shutdownmanager.py (+2/-3) landscape/message_schemas.py (+29/-21) landscape/monitor/tests/test_activeprocessinfo.py (+2/-3) |
To merge this branch: | bzr merge lp:~free.ekanayaka/landscape-client/juju-machine-registration |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Adam Collard (community) | Approve | ||
Alberto Donato (community) | Approve | ||
Review via email: mp+232531@code.launchpad.net |
Commit message
This branch:
- Bumps the server API to 3.3: this will let us introduce a new schema
for the juju-info registration field, since we have released clients
out there that could potentially send the old juju-info schema (although
they'd need to be deployed with an older version of the client charm,
so it's more a theoretical situation than one that can happen in practice).
A server branch has been pushed to bump the server to API 3.3. as well.
- Include the machine ID information in the registration message if the server
is capable of handling it.
Description of the change
This branch:
- Bumps the server API to 3.3: this will let us introduce a new schema for the juju-info registration field, since we have released clients out there that could potentially send the old juju-info schema (although they'd need to be deployed with an older version of the client charm, so it's more a theoretical situation than one that can happen in practice). A server branch has been pushed to bump the server to API 3.3. as well. See:
https:/
- Include the machine ID information in the registration message if the server is capable of handling it.
Just to be clear, after the server-side branch lands too what happen will be that new clients will send a 3.3 registration message with the new juju info schema, which the server knows how to handle. In case old clients send the old juju-info field, the server will just ignore it.
Looks good, +1
A few comments inline.