Deployment tests for Puppet OpenStack
fuel-library uses many modules from Puppet OpenStack project via puppet-librarian. Currently we use pinned version of modules, with versions hardcoded in Puppetfile. To simplify the process of updating to new upstream versions and to provide an early feedback to upstream we'd like to setup the CI, similar to fuel-library tests, which will test master of upstream puppet modules against stable Fuel code.
Blueprint information
- Status:
- Complete
- Approver:
- Bogdan Dobrelya
- Priority:
- High
- Drafter:
- Aleksandra Fedorova
- Direction:
- Approved
- Assignee:
- Igor Belikov
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
9.0
- Started by
- Dmitry Borodaenko
- Completed by
- Dmitry Borodaenko
Related branches
Related bugs
Sprints
Whiteboard
Related links:
* https:/
* https:/
* offline build support https:/
@mwhahaha:
> we support providing a module tarball that we can use
> so we can prepackage all of the modules based on what we need and provide it to the fuel-library build process
> it was added in for offline build support, https:/
> basically as part of the build process today it'll go fetch all the upstream modules and their versions based on a Puppetfile using puppet-
> so for the upstream usage, we could run puppet-
> then tar up the modules and provide it to the fuel-library build process which will then skip rerunning librarian and use the provided module tarball
@EmilienM:
script crinkle wrote is able to take your puppetfile and clone modules with zuul-cloner
https:/
Gerrit topic: https:/
Addressed by: https:/
Fuel CI for Puppet OpenStack modules
Work Items
Work items:
Setup periodic noop test on current merged master: DONE
Setup periodic deployment test on current merged master: DONE
Setup non-voting tests on patchset created: DONE
Switch to voting mode: DONE
Dependency tree
* Blueprints in grey have been implemented.
