Merge lp:~allanlesage/uci-engine/coverage-retriever-juju-deployment into lp:uci-engine
Proposed by
Allan LeSage
Status: | Merged |
---|---|
Approved by: | Allan LeSage |
Approved revision: | 844 |
Merged at revision: | 847 |
Proposed branch: | lp:~allanlesage/uci-engine/coverage-retriever-juju-deployment |
Merge into: | lp:uci-engine |
Prerequisite: | lp:~allanlesage/uci-engine/coverage-retriever |
Diff against target: |
33 lines (+29/-0) 1 file modified
juju-deployer/coverage-retriever.yaml.tmpl (+29/-0) |
To merge this branch: | bzr merge lp:~allanlesage/uci-engine/coverage-retriever-juju-deployment |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Evan (community) | Needs Fixing | ||
Francis Ginther | Approve | ||
PS Jenkins bot (community) | continuous-integration | Approve | |
Review via email: mp+237318@code.launchpad.net |
Commit message
Juju deployment for coverage retriever.
Description of the change
Initial stab at a coverage-retriever juju deployment, mostly to get some tutorializing on how to do such :) . . . . Francis feel free to pass me along if I need too much instruction.
To post a comment you must log in.
This should be enough to deploy the coverage retriever. There is additional work to be done to add relations to other parts of the ci-engine deployment, but that can be done later.
This presents a small problem in that we need to be more flexible in how components are deployed. For example, the default behavior of deploy.py is to deploy everything needed for the ci-engine deployment. Does that include the coverage components or the components for some other future add on service? Just something that needs to be addressed. I think we look for ways to solve this problem at the next face to face sprint.