Documentation for Rebuilding Repositories
While there are standard ways to do this depending on the OS, we need documentation on the steps we expect for a user to rebuild their repository. This is a frequent ask for customers who need to add packages for monitoring, scripts, or other tools they plan on using within their Fuel deployed OpenStack environment.
This is specifically meant for after deployment, not adding packages to the ISO. Customers have a need to add packages such as upgraded versions of [package-name] when there is a vulnerability.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Michael Petersen
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
for CentOS:
1) login to fuel-master
2) Download needed RPMs, then set chmod all downloaded RPMs for 0444 and copy new RPMs into /var/www/
3) rebuild rpm metadata
# createrepo -g /var/www/
4) then run
# /usr/bin/yum clean all
