stoney orchestra: Roadmap: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== backlog == | |||
=== unsorted === | |||
These might be rather epic and need breaking down until they are sensible user-stories. | |||
* investigate, document and implement hooks and git-scripts needed for continuous-(integration|development|.*) | |||
* evaluate and decide between puppet-librarian, r10k or byoc solution for applying Puppetfile/Modulefile | |||
* develop and establish "frontend" tooling like git-* scripts or puppet-rake tasks for devs and admins | |||
* use mcollective for orchestration when provisioning new services thru puppet | |||
* early bootstrap of puppet master during stoney cloud install | |||
== links == | |||
* Architecture | * Architecture | ||
** [[Gentoo_Infrastructure#Puppet_proposal]] | |||
** [http://www.craigdunn.org/2012/05/239/ Craig Dunn's Blog: Designing Puppet – Roles and Profiles] | ** [http://www.craigdunn.org/2012/05/239/ Craig Dunn's Blog: Designing Puppet – Roles and Profiles] | ||
* Puppet Modules | * Puppet Modules | ||
Latest revision as of 22:24, 2 February 2014
backlog
unsorted
These might be rather epic and need breaking down until they are sensible user-stories.
- investigate, document and implement hooks and git-scripts needed for continuous-(integration|development|.*)
- evaluate and decide between puppet-librarian, r10k or byoc solution for applying Puppetfile/Modulefile
- develop and establish "frontend" tooling like git-* scripts or puppet-rake tasks for devs and admins
- use mcollective for orchestration when provisioning new services thru puppet
- early bootstrap of puppet master during stoney cloud install