Create config-download developer documentation
Bug #1852798 reported by
Luke Short
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
In Progress
|
Medium
|
Luke Short | ||
Bug Description
Currently there is a lack of developer documentation about the magic that happens in the background with config-download. For new and existing contributors to TripleO, it would be ideal to have that information written down and explained. This should also help to promote more cross-team development work on the Ansible side of TripleO.
Some fundamental questions to be answered in this documentation:
Where is the Ansible content stored (hint: it's not all in tripleo-ansible!)?
How is it generated?
How is it executed?
How can new Ansible content be added?
What tips and tricks are there for developers to quickly get started with config-download development?
https:/
| Changed in tripleo: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Luke Short (ekultails) |
| milestone: | none → ussuri-1 |
| tags: | added: config-download |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to tripleo-docs (master) | #1 |
| Changed in tripleo: | |
| status: | Triaged → In Progress |
| Changed in tripleo: | |
| milestone: | ussuri-1 → ussuri-2 |
| Changed in tripleo: | |
| milestone: | ussuri-2 → ussuri-3 |
| Changed in tripleo: | |
| milestone: | ussuri-3 → ussuri-rc3 |
| Changed in tripleo: | |
| milestone: | ussuri-rc3 → victoria-1 |
| Changed in tripleo: | |
| milestone: | victoria-1 → victoria-3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/