Deliver puppet modules on slave nodes using packages
Bug #1493568 reported by
Vladimir Kozhukalov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Toolbox | ||
| Mitaka |
Won't Fix
|
Medium
|
Fuel Toolbox | ||
| Newton |
Confirmed
|
Medium
|
Fuel Toolbox | ||
Bug Description
Currently, we install fuel-libraryX.Y package(s) on the master node and then right before starting actual deployment we rsync [1] puppet modules (one of installed versions) from the master node to slave nodes. Such a flow makes things much more complicated than they could be if we installed puppet modules on slave nodes as rpm/deb packages. Deployment itself is parameterized by repo urls (upstream + mos) and this pre-deployment task could be nothing more than just installing fuel-library package from mos repo defined for a cluster. We would not have several versions of fuel-library on the master node, we would not need that complicated upgrade stuff like we currently have for puppet modules.
| tags: | added: feature |
| tags: |
added: need-bp removed: feature |
| tags: | added: area-python |
| tags: | added: fuel-build |
| Changed in fuel: | |
| assignee: | Vladimir Kozhukalov (kozhukalov) → Fuel Enhancements (fuel-enhancements-team) |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #1 |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
Revision history for this message
| Vitaly Parakhin (vparakhin) wrote | #2 |
| tags: | removed: fuel-build need-bp |
To post a comment you must log in.
We passed SCF for 8.0. Moving bug to 9.0