Re: [openstack-dev] Proposal for new Program: OpenStack Deployment
Any thoughts on these questions? Thanks, Anne On Wed, Jul 10, 2013 at 9:47 AM, Anne Gentle annegen...@justwriteclick.comwrote: Hi Robert, What's your plan for documenting the efforts so that others can do this in their environments? Is there any documentation currently for which you can send links? The Doc team is especially interested in configuration docs and installation docs as those are the toughest to produce in a timely, accurate manner now. We have a blueprint for automatically generating docs from configuration options in the code. We are trying to determine a good path for install docs for meeting the release deliverable -- much discussion at http://lists.openstack.org/pipermail/openstack-docs/2013-July/002114.html. Your input welcomed. Thanks, Anne On Wed, Jul 10, 2013 at 3:40 AM, Robert Collins robe...@robertcollins.net wrote: On 10 July 2013 20:01, Thierry Carrez thie...@openstack.org wrote: Robert Collins wrote: Official Title: OpenStack Deployment PTL: Robert Collins robe...@robertcollins.net mailto:robe...@robertcollins.net Mission Statement: Develop and maintain tooling and infrastructure able to deploy OpenStack in production, using OpenStack itself wherever possible. I believe everyone is familiar with us, but just in case, here is some background: we're working on deploying OpenStack to bare metal using OpenStack components and cloud deployment strategies - such as Heat for service orchestration, Nova for machine provisioning Neutron for network configuration, golden images for rapid deployment... etc etc. So far we have straight forward deployment of bare metal clouds both without Heat (so that we can bootstrap from nothing), and with Heat (for the bootstrapped layer), and are working on the KVM cloud layer at the moment. Could you provide the other pieces of information mentioned at: https://wiki.openstack.org/wiki/Governance/NewPrograms ack: * Detailed mission statement (including why their effort is essential to the completion of the OpenStack mission) I think this is covered. In case its not obvious: if you can't install OpenStack easily, it becomes a lot harder to deliver to users. So deployment is essential (and at the moment the market is assessing the cost of deploying OpenStack at ~ 60K - so we need to make it a lot cheaper). * Expected deliverables and repositories We'll deliver and maintain working instructions and templates for deploying OpenStack. Repositories that are 'owned' by Deployment today diskimage-builder tripleo-image-elements triple-heat-templates os-apply-config os-collect-config os-refresh-config toci [triple-o-CI][this is something we're discussing with infra about where it should live... and mordred and jeblair disagree with each other :)]. tripleo-incubator [we're still deciding if we'll have an actual CLI tool or just point folk at the other bits, and in the interim stuff lives here]. * How 'contribution' is measured within the program (by default, commits to the repositories associated to the program) Same as rest of OpenStack : commits to any of these repositories, and we need some way of recognising non-code contributions like extensive docs/bug management etc, but we don't have a canned answer for the non-code aspects. * Main team members Is this the initial review team, or something else? If its the review team, then me/Clint/Chris Jones/Devananda. If something else then I propose we start with those who have commits in the last 6 months, namely [from a quick git check, this may be imperfect]: Me Clint Byrum Chris Jones Ghe Rivero Chris Krelle Devananda van der Veen Derek Higgins Cody Somerville Arata Notsu Dan Prince Elizabeth Krumbach Joe Gordon Lucas Alvares Gomes Steve Baker Tim Miller Proposed initial program lead (PTL) I think yours truely makes as much sense as anything :). -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Cloud Services ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Anne Gentle annegen...@justwriteclick.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Proposal for new Program: OpenStack Deployment
Excerpts from Anne Gentle's message of 2013-07-10 07:47:19 -0700: Hi Robert, What's your plan for documenting the efforts so that others can do this in their environments? Is there any documentation currently for which you can send links? We've been documenting the bootstrap procedure in this file: https://github.com/tripleo/incubator/blob/master/devtest.md This is intended as much as a how to get started as it is how does this actually work?. We intend to have a much leaner set of instructions that will have many of these steps scripted. Also elements have their own README.md which is intended to inform deployers what to do with each piece: https://github.com/stackforge/tripleo-image-elements/tree/master/elements/neutron-openvswitch-agent https://github.com/stackforge/tripleo-image-elements/tree/master/elements/keystone Long term I see us assembling those into a holistic deployment guide, and mapping the configurations and relationships defined in the Heat templates and elements to the corresponding parts of each project's manual. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Proposal for new Program: OpenStack Deployment
On 11 July 2013 02:47, Anne Gentle annegen...@justwriteclick.com wrote: Hi Robert, What's your plan for documenting the efforts so that others can do this in their environments? Is there any documentation currently for which you can send links? Sorry for the slow reply to this; the thread got lost in my inbox, then the weekend... bah! Anyhow, Clint has sent through current docs. The plan we have is to get the thing working end to end (which we are mostly there on) and then decide what should be instructions, and what should be automation. E.g. exactly what the UI for tripleo's native bits are (whatever they may be). The Doc team is especially interested in configuration docs and installation docs as those are the toughest to produce in a timely, accurate manner now. We have a blueprint for automatically generating docs from configuration options in the code. We are trying to determine a good path for install docs for meeting the release deliverable -- much discussion at http://lists.openstack.org/pipermail/openstack-docs/2013-July/002114.html. Your input welcomed. A few random thoughts: http://lists.openstack.org/pipermail/openstack-docs/2013-July/002131.html is an interesting perspective... Certainly we consider documentation a primary part of what we're doing : got to teach people how to use the tooling. So I guess I disagree with that post - if you can't install a product, you can't use it. I don't think we need to cover all the options and possibilities - we should be covering the 95% of use cases: small/ medium / big profiles; reference network setup, reference DB etc. I would like to get TripleO into the official manuals of course... I think as we mature we'll start moving docs from our trees into the reference manuals. I expect TripleO/OpenStack Deployment docs to be updated continually (even if/when we add support for released versions) - because the environment folk deploy in doesn't stand still. -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Cloud Services ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Proposal for new Program: OpenStack Deployment
Robert Collins wrote: Official Title: OpenStack Deployment PTL: Robert Collins robe...@robertcollins.net mailto:robe...@robertcollins.net Mission Statement: Develop and maintain tooling and infrastructure able to deploy OpenStack in production, using OpenStack itself wherever possible. I believe everyone is familiar with us, but just in case, here is some background: we're working on deploying OpenStack to bare metal using OpenStack components and cloud deployment strategies - such as Heat for service orchestration, Nova for machine provisioning Neutron for network configuration, golden images for rapid deployment... etc etc. So far we have straight forward deployment of bare metal clouds both without Heat (so that we can bootstrap from nothing), and with Heat (for the bootstrapped layer), and are working on the KVM cloud layer at the moment. Could you provide the other pieces of information mentioned at: https://wiki.openstack.org/wiki/Governance/NewPrograms Also if you want it discussed at the next TC meeting, please send a heads-up (pointing to the -dev thread) to openstack-tc ML. Thanks! -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Proposal for new Program: OpenStack Deployment
On 10 July 2013 20:01, Thierry Carrez thie...@openstack.org wrote: Robert Collins wrote: Official Title: OpenStack Deployment PTL: Robert Collins robe...@robertcollins.net mailto:robe...@robertcollins.net Mission Statement: Develop and maintain tooling and infrastructure able to deploy OpenStack in production, using OpenStack itself wherever possible. I believe everyone is familiar with us, but just in case, here is some background: we're working on deploying OpenStack to bare metal using OpenStack components and cloud deployment strategies - such as Heat for service orchestration, Nova for machine provisioning Neutron for network configuration, golden images for rapid deployment... etc etc. So far we have straight forward deployment of bare metal clouds both without Heat (so that we can bootstrap from nothing), and with Heat (for the bootstrapped layer), and are working on the KVM cloud layer at the moment. Could you provide the other pieces of information mentioned at: https://wiki.openstack.org/wiki/Governance/NewPrograms ack: * Detailed mission statement (including why their effort is essential to the completion of the OpenStack mission) I think this is covered. In case its not obvious: if you can't install OpenStack easily, it becomes a lot harder to deliver to users. So deployment is essential (and at the moment the market is assessing the cost of deploying OpenStack at ~ 60K - so we need to make it a lot cheaper). * Expected deliverables and repositories We'll deliver and maintain working instructions and templates for deploying OpenStack. Repositories that are 'owned' by Deployment today diskimage-builder tripleo-image-elements triple-heat-templates os-apply-config os-collect-config os-refresh-config toci [triple-o-CI][this is something we're discussing with infra about where it should live... and mordred and jeblair disagree with each other :)]. tripleo-incubator [we're still deciding if we'll have an actual CLI tool or just point folk at the other bits, and in the interim stuff lives here]. * How 'contribution' is measured within the program (by default, commits to the repositories associated to the program) Same as rest of OpenStack : commits to any of these repositories, and we need some way of recognising non-code contributions like extensive docs/bug management etc, but we don't have a canned answer for the non-code aspects. * Main team members Is this the initial review team, or something else? If its the review team, then me/Clint/Chris Jones/Devananda. If something else then I propose we start with those who have commits in the last 6 months, namely [from a quick git check, this may be imperfect]: Me Clint Byrum Chris Jones Ghe Rivero Chris Krelle Devananda van der Veen Derek Higgins Cody Somerville Arata Notsu Dan Prince Elizabeth Krumbach Joe Gordon Lucas Alvares Gomes Steve Baker Tim Miller Proposed initial program lead (PTL) I think yours truely makes as much sense as anything :). -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Cloud Services ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Proposal for new Program: OpenStack Deployment
Hi Robert, What's your plan for documenting the efforts so that others can do this in their environments? Is there any documentation currently for which you can send links? The Doc team is especially interested in configuration docs and installation docs as those are the toughest to produce in a timely, accurate manner now. We have a blueprint for automatically generating docs from configuration options in the code. We are trying to determine a good path for install docs for meeting the release deliverable -- much discussion at http://lists.openstack.org/pipermail/openstack-docs/2013-July/002114.html. Your input welcomed. Thanks, Anne On Wed, Jul 10, 2013 at 3:40 AM, Robert Collins robe...@robertcollins.netwrote: On 10 July 2013 20:01, Thierry Carrez thie...@openstack.org wrote: Robert Collins wrote: Official Title: OpenStack Deployment PTL: Robert Collins robe...@robertcollins.net mailto:robe...@robertcollins.net Mission Statement: Develop and maintain tooling and infrastructure able to deploy OpenStack in production, using OpenStack itself wherever possible. I believe everyone is familiar with us, but just in case, here is some background: we're working on deploying OpenStack to bare metal using OpenStack components and cloud deployment strategies - such as Heat for service orchestration, Nova for machine provisioning Neutron for network configuration, golden images for rapid deployment... etc etc. So far we have straight forward deployment of bare metal clouds both without Heat (so that we can bootstrap from nothing), and with Heat (for the bootstrapped layer), and are working on the KVM cloud layer at the moment. Could you provide the other pieces of information mentioned at: https://wiki.openstack.org/wiki/Governance/NewPrograms ack: * Detailed mission statement (including why their effort is essential to the completion of the OpenStack mission) I think this is covered. In case its not obvious: if you can't install OpenStack easily, it becomes a lot harder to deliver to users. So deployment is essential (and at the moment the market is assessing the cost of deploying OpenStack at ~ 60K - so we need to make it a lot cheaper). * Expected deliverables and repositories We'll deliver and maintain working instructions and templates for deploying OpenStack. Repositories that are 'owned' by Deployment today diskimage-builder tripleo-image-elements triple-heat-templates os-apply-config os-collect-config os-refresh-config toci [triple-o-CI][this is something we're discussing with infra about where it should live... and mordred and jeblair disagree with each other :)]. tripleo-incubator [we're still deciding if we'll have an actual CLI tool or just point folk at the other bits, and in the interim stuff lives here]. * How 'contribution' is measured within the program (by default, commits to the repositories associated to the program) Same as rest of OpenStack : commits to any of these repositories, and we need some way of recognising non-code contributions like extensive docs/bug management etc, but we don't have a canned answer for the non-code aspects. * Main team members Is this the initial review team, or something else? If its the review team, then me/Clint/Chris Jones/Devananda. If something else then I propose we start with those who have commits in the last 6 months, namely [from a quick git check, this may be imperfect]: Me Clint Byrum Chris Jones Ghe Rivero Chris Krelle Devananda van der Veen Derek Higgins Cody Somerville Arata Notsu Dan Prince Elizabeth Krumbach Joe Gordon Lucas Alvares Gomes Steve Baker Tim Miller Proposed initial program lead (PTL) I think yours truely makes as much sense as anything :). -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Cloud Services ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Anne Gentle annegen...@justwriteclick.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
