| Summary: | ansible playbook needed to deploy/upgrade the service | ||
|---|---|---|---|
| Product: | [Community] rpm-test-trigger | Reporter: | Roman Joost <rjoost> |
| Component: | general | Assignee: | beaker-dev-list |
| Status: | POST --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unreleased | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Roman Joost
2016-10-26 04:43:06 UTC
What it needs to do: * need a role which sets up an rpm-test-trigger repository * ensures that the rpm-test-trigger rpm is present * enables the rpm-test-trigger as a service with systemd Additionally create a Jenkins "driftcheck" job to notice if the staging systems configuration deviates. Just as a notice as well that this has moved from being RHEL7 which was originally discussed but now onto F25 for our staging environment, due to rpm-test-trigger now requiring python 3.5 which isn't currently available within RHEL 7 Another requirement follow on that has changed since this ticket was created was the legacy broker which needs to be added which is a part of 1388265 which is moving us to python 3 (as noted above). Which is a temporary bridge between python2 and python-qpid which doesn't support python 3 and our application which we moved to, to get better async functionality. This means that'll be a separate rpm as seen within https://gerrit.beaker-project.org/#/c/5529/ Which also is another service to configure within the role. We also will need the rpms to be built and to update the role once we get the proper repo location for the playbook. |