Difference between revisions of "Chef/Contributing/NewCookbook"
< Chef | Contributing
(Add page for create new stackforge cookbook) |
|||
(4 intermediate revisions by 2 users not shown) | |||
Line 4: | Line 4: | ||
=How to create a new Stackforge OpenStack cookbook= | =How to create a new Stackforge OpenStack cookbook= | ||
− | + | Please visit this [http://docs.openstack.org/infra/manual/creators.html page] and go through the steps suggested. | |
== Blueprint == | == Blueprint == | ||
Line 11: | Line 11: | ||
** include general view of recipe functions, any platform issues (we support ubuntu, redhat, suse), basic use cases to be covered | ** include general view of recipe functions, any platform issues (we support ubuntu, redhat, suse), basic use cases to be covered | ||
** Attend meetings and chat on ML to get spec approved and assigned to a release | ** Attend meetings and chat on ML to get spec approved and assigned to a release | ||
+ | ** Example: https://review.openstack.org/#/c/140983/ | ||
== Stackforge Project == | == Stackforge Project == | ||
Line 16: | Line 17: | ||
* create a stackforge project https://github.com/stackforge | * create a stackforge project https://github.com/stackforge | ||
* assign the "chef-manager-core" gerrit group to the project | * assign the "chef-manager-core" gerrit group to the project | ||
− | * create a patch with the basic cookbook files for getting thru first gate | + | * create a patch with the basic cookbook files for getting thru first gate example: https://review.openstack.org/#/c/145120/ |
** .gitignore | ** .gitignore | ||
** .gitreview | ** .gitreview | ||
Line 28: | Line 29: | ||
** TESTING.md | ** TESTING.md | ||
** /spec/spec_helper.rb | ** /spec/spec_helper.rb | ||
+ | * create patche(s) to every other OpenStack cookbook that depends upon this directly or in directly with a new Berksfile entry for it. For example, in the bare-metal case, it was added as a new dependency under Compute, so need patch for Compute Berksfile. And since Telemetry also depends upon Compute, it also need Berksfile update. | ||
== Infra Integration == | == Infra Integration == | ||
* create a infra patch https://github.com/openstack-infra/project-config | * create a infra patch https://github.com/openstack-infra/project-config | ||
− | ** | + | ** https://review.openstack.org/#/c/143800/ |
back to contributing page: https://wiki.openstack.org/w/index.php?title=Chef/Contributing | back to contributing page: https://wiki.openstack.org/w/index.php?title=Chef/Contributing |
Latest revision as of 19:44, 16 March 2015
<under construction>
Contents
How to create a new Stackforge OpenStack cookbook
Please visit this page and go through the steps suggested.
Blueprint
- create a spec/blueprint to cover the basic scope of this cookbook https://github.com/stackforge/openstack-chef-specs
- include general view of recipe functions, any platform issues (we support ubuntu, redhat, suse), basic use cases to be covered
- Attend meetings and chat on ML to get spec approved and assigned to a release
- Example: https://review.openstack.org/#/c/140983/
Stackforge Project
- create a stackforge project https://github.com/stackforge
- assign the "chef-manager-core" gerrit group to the project
- create a patch with the basic cookbook files for getting thru first gate example: https://review.openstack.org/#/c/145120/
- .gitignore
- .gitreview
- .rubocop.yml
- Berksfile
- CONTRIBUTING.md
- Gemfile
- metadata.md
- Rakefile
- README.md
- TESTING.md
- /spec/spec_helper.rb
- create patche(s) to every other OpenStack cookbook that depends upon this directly or in directly with a new Berksfile entry for it. For example, in the bare-metal case, it was added as a new dependency under Compute, so need patch for Compute Berksfile. And since Telemetry also depends upon Compute, it also need Berksfile update.
Infra Integration
- create a infra patch https://github.com/openstack-infra/project-config
back to contributing page: https://wiki.openstack.org/w/index.php?title=Chef/Contributing