Merge ~pwlars/testflinger/+git/testflinger-charm-reactive-layer:testflinger-reactive-charm into ~canonical-hw-cert/testflinger/+git/testflinger-charm-reactive-layer:master
Proposed by
Paul Larson
| Status: | Merged |
|---|---|
| Approved by: | Paul Larson |
| Approved revision: | e9bfc0cf2f2af52f17bf243c3469a869b5bca015 |
| Merged at revision: | e9bfc0cf2f2af52f17bf243c3469a869b5bca015 |
| Proposed branch: | ~pwlars/testflinger/+git/testflinger-charm-reactive-layer:testflinger-reactive-charm |
| Merge into: | ~canonical-hw-cert/testflinger/+git/testflinger-charm-reactive-layer:master |
| Diff against target: |
282 lines (+216/-0) 11 files modified
README (+31/-0) config.yaml (+9/-0) layer.yaml (+5/-0) metadata.yaml (+14/-0) reactive/testflinger.py (+94/-0) templates/testflinger-vhost.conf (+8/-0) templates/testflinger.conf (+3/-0) templates/testflinger.service (+10/-0) testflinger.yaml (+6/-0) tests/00-setup (+5/-0) tests/10-deploy (+31/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Paul Larson | Approve | ||
|
Review via email:
|
|||
Description of the change
This is the reactive charm itself. I'll create a separate branch to store the built version, for convenient deployment, as you can't deploy this one without running charm build -s xenial on it. If you do want to try building it and deploying it, you'll need to run the above command, and also deploy it with a redis instance. From there, you can do juju add-relation redis:db testflinger:db to make the connection, then curl the ip for testflinger on port 80 to interact with the API.
To post a comment you must log in.
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
self-approving