Merge lp:~ahasenack/landscape-charm/landscape-charm-use-trusty into lp:~landscape/landscape-charm/trunk
Status: | Merged |
---|---|
Approved by: | Andreas Hasenack |
Approved revision: | 205 |
Merged at revision: | 202 |
Proposed branch: | lp:~ahasenack/landscape-charm/landscape-charm-use-trusty |
Merge into: | lp:~landscape/landscape-charm/trunk |
Diff against target: |
72 lines (+8/-8) 3 files modified
config/landscape-deployments.yaml (+4/-4) dev/update-charm-revision-numbers (+3/-3) tests/01-begin (+1/-1) |
To merge this branch: | bzr merge lp:~ahasenack/landscape-charm/landscape-charm-use-trusty |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chris Glass (community) | Approve | ||
Adam Collard (community) | Approve | ||
Review via email: mp+231892@code.launchpad.net |
Commit message
Change the deployer file to use trusty where possible for the charms we deploy.
Description of the change
This branch switches all charms to use trusty, except haproxy, which doesn't have a trusty charm yet.
Finally, there is a small fix to the test_msg test because LDS trunk is now returning a new field, in addition to the tested ones. Since only LDS trunk does it, I chose to ignore this extra field.
I didn't add another deployer file for the trusty files, or new deployer targets, because we want to keep this simple for users. If they are confronted with dozens of deployer option, answering "which one do I use?" becomes more complicated. Still, if reviewers want it, I could change that so we get to test both precise and trusty for the time being.
I tried just running make deploy-dense-maas but immediately hit an issue https:/ /pastebin. canonical. com/115984/
The -u to deployer looks suspicious - can we remove it from this MP please?