Like this previous PR, this one is being proposed against the feature branch for unified-agent-host-charm. Because it's against a feature branch, our rules don't strictly require reviews. However I would appreciate reviews against these smaller branches to make it simpler than reviewing one large PR at the end.
Description
We currently use the agent-charm to create a new checkout of the testflinger agent/device-connector code and install it separately for each agent in a path for each agent. This has always been useful for debugging on a real environment, but going forward, it would be much nicer to have a real dev/staging environment with real agents connected. The down side of doing it the way we’ve been doing it, is that it adds a lot of additional time required for updating ALL the agents to the latest version of testflinger code, because we need to pull the repo for each one of them. Having it in a shared location would speed up installation and updates considerably.
Resolved issues
CERTTF-376
Documentation
Updated README
Web service API changes
N/A
Tests
Integration tests added for building the charm, deploying it, and running the action. NOTE: juju must be enabled on the system where you run these tests.
Like this previous PR, this one is being proposed against the feature branch for
unified-agent-host-charm. Because it's against a feature branch, our rules don't strictly require reviews. However I would appreciate reviews against these smaller branches to make it simpler than reviewing one large PR at the end.Description
We currently use the agent-charm to create a new checkout of the testflinger agent/device-connector code and install it separately for each agent in a path for each agent. This has always been useful for debugging on a real environment, but going forward, it would be much nicer to have a real dev/staging environment with real agents connected. The down side of doing it the way we’ve been doing it, is that it adds a lot of additional time required for updating ALL the agents to the latest version of testflinger code, because we need to pull the repo for each one of them. Having it in a shared location would speed up installation and updates considerably.
Resolved issues
CERTTF-376
Documentation
Updated README
Web service API changes
N/A
Tests
Integration tests added for building the charm, deploying it, and running the action. NOTE: juju must be enabled on the system where you run these tests.