Difference between revisions of "TripleO"

Latest revision as of 13:39, 10 January 2020

TripleO (OpenStack On OpenStack) is a program aimed at installing, upgrading and operating OpenStack clouds using OpenStack's own cloud facilities as the foundations - building on nova, neutron and heat to automate fleet management at datacentre scale.

All documentation including development and deployment can be found at the TripleO Documentation.

Blueprints

All tripleo blueprints. When creating new blueprints please ensure you put 'tripleo' in the short name.

Review team

A handy way to see all the reviews that need action: TripleoO Inbox Dashboard from https://github.com/stackforge/gerrit-dash-creator/

Anyone can do reviews, but only the 'tripleo-core' team can approve them to land. We operate with the OpenStack standard two x +2's except in well, exceptional circumstances. Where multiple people collaborate on a single patch, one of the +2's must come from someone that isn't an author of the patch.

Please don't send requests for reviews to the mailing list. Try IRC or direct email instead. http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html

As a guideline, we follow the standard Review Checklist. We also have an expedited approval process for changes where there is general consensus and only minor implementation changes are needed. Details can be found in the Expedited Approvals Policy.

For specs, we have some additional guidelines Spec Review Policy

The review team should look for reviews in all the following projects:

For completeness, the following URL will show you reviews from the above projects that are open:

All TripleO Reviews

If you prefer to see an organized report of Gerrit reviews ordered by Launchpad ticket priority you can use the TripleO ReviewDay

Bug Triage

Triage for us consists of:

assigning an importance
putting any obvious tags (e.g. 'baremetal') on it (see also: bug tagging policy)
setting status to 'triaged'.

(If you're a TripleO contributor and you're filing your own bug, you can skip 'confirm' and go straight to triaged - unless you believe the bug isn't real, in which case why are you filing it? :)

The bug triage team for TripleO is https://launchpad.net/~tripleo.

We're mostly using the process described at https://wiki.openstack.org/wiki/BugTriage, with two key differences:

we don't use wishlist: things we'd like to do and things that we do wrong are both defects; except for regressions the priority of the work is not affect by whether we've delivered the the thing or not, and using wishlist just serves to flatten all the priority of all unimplemented things into one bucket: not helpful.
we use triaged, not just 'confirmed'.

@@ Line 1: / Line 1: @@
-=TripleO - Openstack on Openstack=
+TripleO (OpenStack On OpenStack) is a program aimed at installing, upgrading and operating OpenStack clouds using OpenStack's own cloud facilities as the foundations - building on nova, neutron and heat to automate fleet management at datacentre scale.
-TripleO is a program aimed at installing, upgrading and operating OpenStack clouds using OpenStack's own cloud facilities as the foundations - building on nova, quantum and heat to automate fleet management at datacentre scale (and scaling down to as few as 2 machines).
+All documentation including development and deployment can be found at the [https://docs.openstack.org/developer/tripleo-docs/ TripleO Documentation].
-We gave a [https://www.openstack.org/summit/portland-2013/session-videos/presentation/openstack-on-openstack-overview presentation] at the portland 2013 summit about TripleO.
+=== Blueprints ===
+[https://blueprints.launchpad.net/openstack?searchtext=tripleo All tripleo blueprints]. '''When creating new blueprints please ensure you put 'tripleo' in the short name.'''
-TripleO is raw but usable today - see our [https://github.com/openstack/tripleo-incubator tripleo-incubator] for deployment instructions.
+=== Review team ===
+A handy way to see all the reviews that need action: [https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Ftripleo%2Dincubator+OR%0Aproject%3Aopenstack%2Ftripleo%2Dimage%2Delements+OR%0Aproject%3Aopenstack%2Ftripleo%2Dheat%2Dtemplates+OR%0Aproject%3Aopenstack%2Ftripleo%2Dpuppet%2Delements+OR%0Aproject%3Aopenstack%2Ftripleo%2Dspecs+OR%0Aproject%3Aopenstack%2Ftripleo%2Dcommon+OR%0Aproject%3Aopenstack%2Fos%2Dapply%2Dconfig+OR%0Aproject%3Aopenstack%2Fos%2Dcollect%2Dconfig+OR%0Aproject%3Aopenstack%2Fos%2Drefresh%2Dconfig+OR%0Aproject%3Aopenstack%2Fos%2Dcloud%2Dconfig+OR%0Aproject%3Aopenstack%2Fdiskimage%2Dbuilder+OR%0Aproject%3Aopenstack%2Fdib%2Dutils+OR%0Aproject%3Aopenstack%2Dinfra%2Ftripleo%2Dci+OR%0Aproject%3Aopenstack%2Ftripleo%2Dui+OR%0Aproject%3Aopenstack%2Fpython%2Dtripleoclient+OR%0Aproject%3Aopenstack%2Fos%2Dnet%2Dconfig+OR%0Aproject%3Aopenstack%2Finstack+OR%0Aproject%3Aopenstack%2Finstack%2Dundercloud+OR%0Aproject%3Aopenstack%2Fpython%2Dtripleoclient+OR%0Aproject%3Aopenstack%2Ftripleo%2Ddocs%29+status%3Aopen+NOT+label%3AWorkflow%3C%3D%2D1+NOT+label%3ACode%2DReview%3C%3D%2D2&title=TripleO+Inbox&My+Patches+Requiring+Attention=owner%3Aself+%28label%3AVerified%2D1%2Cjenkins+OR+label%3ACode%2DReview%2D1%29&TripleO+Specs=NOT+owner%3Aself+project%3Aopenstack%2Ftripleo%2Dspecs&Needs+Approval=label%3AVerified%3E%3D1%2Cjenkins+NOT+owner%3Aself+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%2D1&5+Days+Without+Feedback=label%3AVerified%3E%3D1%2Cjenkins+NOT+owner%3Aself+NOT+project%3Aopenstack%2Ftripleo%2Dspecs+NOT+label%3ACode%2DReview%3C%3D2+age%3A5d&No+Negative+Feedback=label%3AVerified%3E%3D1%2Cjenkins+NOT+owner%3Aself+NOT+project%3Aopenstack%2Ftripleo%2Dspecs+NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D2+limit%3A50&Other=label%3AVerified%3E%3D1%2Cjenkins+NOT+owner%3Aself+NOT+project%3Aopenstack%2Ftripleo%2Dspecs+label%3ACode%2DReview%2D1+limit%3A20 TripleoO Inbox Dashboard] from https://github.com/stackforge/gerrit-dash-creator/
-Folk working on TripleO are contributing to Nova, OpenStack Networking, Heat and [[Baremetal|Ironic]] to ensure they have the facilities needed to deploy to baremetal at scale. We also have a small number of projects we're shepards for ourselves:
+Anyone can do reviews, but only the 'tripleo-core' team can approve them to land. We operate with the OpenStack standard two x +2's  except in well, exceptional circumstances. Where multiple people collaborate on a single patch, one of the +2's must come from someone that isn't an author of the patch.
-* [https://github.com/stackforge/os-config-applier os-apply-config] - small templating layer for writing out config files.
-* [https://github.com/stackforge/os-refresh-config-applier os-refresh-config] - react to heat metadata changes and send heat events
-* [https://github.com/stackforge/diskimage-builder diskimage-builder] - build golden disk images
-* [https://github.com/stackforge/tripleo-image-elements tripleo-image-elements] - rules for diskimage-builder for OpenStack golden images.
-* [https://github.com/stackforge/tripleo-heat-templates tripleo-heat-templates] Heat templates for deploying OpenStack
-=Design=
+Please don't send requests for reviews to the mailing list.  Try IRC or direct email instead.  http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
-Our overall story is to invest in robust solid automation such that we can do continuous integration and deployment testing of a cloud at the bare metal layer, then deploy the very same tested images to production clouds using nova baremetal (now ironic), rather than any separate management stack, leading to shared expertise in both deployments in the cloud, and of the cloud. Finally, because we can setup OpenStack in a fully HA environment, we can host the baremetal cloud used to deploy OpenStack in itself, and have a fully self sustaining HA cluster. On top of that we intend to build out a solid operations story - baseline monitoring autoconfigured as the overcloud - the cloud we deploy on top of the bare-metal "under" cloud scales up.
-=Interoperability=
+As a guideline, we follow the standard  [http://docs.openstack.org/infra/manual/developers.html#peer-review Review Checklist].  We also have an expedited approval process for changes where there is general consensus and only minor implementation changes are needed.  Details can be found in the [https://specs.openstack.org/openstack/tripleo-specs/specs/policy/expedited-approvals.html Expedited Approvals Policy].
-A key goal of ours is to play nice with folk that already have deep investment in operational areas - such as automation via Chef/Puppet/Salt, or monitoring via icinga/assimilator etc. We're ensuring we have clean interfaces that alternative implementations can be plugged into [e.g. you can use Chef/Puppet/Salt to do the in-instance configuration of a golden TripleO disk image].
+For specs, we have some additional guidelines [https://specs.openstack.org/openstack/tripleo-specs/specs/policy/spec-review.html Spec Review Policy]
+The review team should look for reviews in all the following projects:
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-specs,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-incubator,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-ui,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack-infra/tripleo-ci,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/os-apply-config,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/os-collect-config,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/os-refresh-config,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/os-cloud-config,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/os-net-config,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-heat-templates,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-image-elements,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-puppet-elements,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/diskimage-builder,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/dib-utils,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-common,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/instack,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/instack-undercloud,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-docs,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/python-tripleoclient,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/puppet-tripleo,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-ansible,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-quickstart,n,z
+* https://review.openstack.org/#/q/status:open+project:openstack/tripleo-quickstart-extras,n,z
+For completeness, the following URL will show you reviews from the above projects that are open:
+* [https://review.openstack.org/#/q/status:open+%28project:openstack/tripleo-incubator+OR+project:openstack-infra/tripleo-ci+OR+project:openstack/tripleo-ui+OR+project:openstack/os-apply-config+OR+project:openstack/os-collect-config+OR+project:openstack/os-net-config+OR+project:openstack/os-refresh-config+OR+project:openstack/tripleo-image-elements+OR+project:openstack/tripleo-heat-templates+OR+project:openstack/diskimage-builder+OR+project:openstack/os-cloud-config+OR+project:openstack/dib-utils+OR+project:openstack/tripleo-common+OR+project:openstack/tripleo-puppet-elements+OR+project:stackforge/puppet-tripleo+OR+project:openstack/instack+OR+project:openstack/instack-undercloud+OR+project:openstack/tripleo-docs+OR+project:openstack/python-tripleoclient+OR+project:openstack/puppet-tripleo+OR+project:openstack/tripleo-ansible+OR+project:openstack/tripleo-quickstart+OR+project:openstack/tripleo-quickstart-extras+OR+project:openstack/tripleo-specs%29,n,z All TripleO Reviews]
+If you prefer to see an organized report of Gerrit reviews ordered by Launchpad ticket priority you can use the [http://tripleo.org/reviews.html TripleO ReviewDay]
+=== Bug Triage ===
+Triage for us consists of:
+* assigning an importance
+* putting any obvious tags (e.g. 'baremetal') on it (see also: [http://specs.openstack.org/openstack/tripleo-specs/specs/policy/bug-tagging.html bug tagging policy])
+* setting status to 'triaged'.
+(If you're a TripleO contributor and you're filing your own bug,
+you can skip 'confirm' and go straight to triaged - unless you
+believe the bug isn't real, in which case why are you filing it? :)
+The bug triage team for TripleO is https://launchpad.net/~tripleo.
+We're mostly using the process described at https://wiki.openstack.org/wiki/BugTriage,
+with two key differences:
+* we don't use wishlist: things we'd like to do and things that we do wrong are both defects; except for regressions the priority of the work is not affect by whether we've delivered the the thing or not, and using wishlist just serves to flatten all the priority of all unimplemented things into one bucket: not helpful.
+* we use triaged, not just 'confirmed'.