Remove upstream repo dependency
Presently the repo-clone-mirror play is responsible for cloning the upstream repository that Rackspace maintains into the repo containers. While this process is simple enough it does bring with it a reliance on an upstream deployer/vendor. OSAD already has the ability to build its own python packages which is the process used to do all gate check testing so it should also be the default means to deploy an OSAD environment.
Blueprint information
- Status:
- Complete
- Approver:
- Jesse Pretorius
- Priority:
- Medium
- Drafter:
- Kevin Carter
- Direction:
- Approved
- Assignee:
- Kevin Carter
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
- Implemented
- Milestone target:
- liberty-3
- Started by
- Jesse Pretorius
- Completed by
- Jesse Pretorius
Related branches
Related bugs
Sprints
Whiteboard
spec: https:/
Gerrit topic: https:/
Addressed by: https:/
Remove upstream repo dependency
Addressed by: https:/
Removed rpc-repo upstream pip deps
Work Items
Dependency tree
* Blueprints in grey have been implemented.