)]}'
{"reference/charter.rst":[{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":25,"context_line":"necessary to achieve their goals."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"The work of project teams is performed under the oversight of the TC."},{"line_number":28,"context_line":"Contributing to their work grants you ATC status (see below). Current"},{"line_number":29,"context_line":"groups or teams which want to join the OpenStack project should file a"},{"line_number":30,"context_line":"motion with the TC by modifying ``teams.yaml`` in the"},{"line_number":31,"context_line":":repo:`openstack/governance` git repository.  The TC has ultimate"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_bf743168","line":28,"updated":"2014-10-28 17:33:56.000000000","message":"Careful here. I think this implies that filing a bug now grants ATC status for example?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"e5586b02b82c966d5c93aec31f96ebe51357ae3c","unresolved":false,"context_lines":[{"line_number":33,"context_line":""},{"line_number":34,"context_line":".. seealso::"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"   * `Official List of OpenStack Teams`_"},{"line_number":37,"context_line":"   * :doc:`official-projects`"},{"line_number":38,"context_line":"   * :doc:`new-team-requirements`"},{"line_number":39,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_322337a8","line":36,"updated":"2014-10-27 18:39:46.000000000","message":"Shouldn\u0027t this be OpenStack Project Teams?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"0314e55f4eb303d37bf2955053e9965a39125c87","unresolved":false,"context_lines":[{"line_number":33,"context_line":""},{"line_number":34,"context_line":".. seealso::"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"   * `Official List of OpenStack Teams`_"},{"line_number":37,"context_line":"   * :doc:`official-projects`"},{"line_number":38,"context_line":"   * :doc:`new-team-requirements`"},{"line_number":39,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_72adbfe8","line":36,"in_reply_to":"9aa7fdbe_322337a8","updated":"2014-10-27 18:44:00.000000000","message":"I\u0027m not sure why? It\u0027s the title of a link to a document that contains the teams we\u0027ve designated as official so far. That seems accurate.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":".. _Official List of OpenStack Teams: http://git.openstack.org/cgit/openstack/governance/tree/reference/teams.yaml"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":".. _PTL:"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Project Team Leads"},{"line_number":45,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_7fdc8946","line":42,"updated":"2014-10-28 17:33:56.000000000","message":"If we are going to rework this section, then I\u0027d like to see it include discussion of whether we expect a project team to have more than one sub team. I\u0027ve certainly had conversations where it has been suggested that a project team would correlate to a single core team for example, which isn\u0027t clear to me from the words above.\n\nSo, for example, can the Compute Project Team and a hypervisor project (nova) and a containers project, both with different core teams? I don\u0027t see a reason why not, but perhaps that\u0027s a thing we want to exclude for some reason?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"}],"reference/integrated-release.rst":[{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":" The OpenStack Integrated Release"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The OpenStack Integrated Release is a subset of the official OpenStack"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_bf97d146","line":2,"updated":"2014-10-28 17:33:56.000000000","message":"I feel we should be dropping the term \"integrated release\" if we\u0027re moving to something layers-like.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"28d9a59b5a453db178ea2c280b83280f90c55e4e","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":" The OpenStack Integrated Release"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The OpenStack Integrated Release is a subset of the official OpenStack"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_dfc1f580","line":2,"updated":"2014-10-28 17:12:08.000000000","message":"Reposting my comment from the split review:\n\nI think we need to stop calling that \"the integrated release\". \"Integrated release\" is an overloaded term which, being the ultimate Grail of our project structure, means different things depending on the stakeholder you talk to. Changing what it means but keeping the same terminology is IMHO a recipe for more confusion down the road.\n\nIn particular, \"integrated release\" currently means \"valuable thing\" for almost all stakeholders, so anything thrown out of it will resist the change.\n\nI like to think of this \"thing\" as a production artifact. It\u0027s an arbitrary set of projects (defined based on an opinionated use case), but they are (1) highly interdependent, (2) all fine with stronger alignment and TC direction/oversight, (3) all current horizontal teams seem fine supporting them, and (4) unlikely to dramatically increase in size, so sustainable for those said horizontal teams. So it\u0027s a group of projects and horizontal teams that are fine working together, under increased control of the TC. It\u0027s not a statement of value, it\u0027s just a production structure.\n\nIt\u0027s perfectly fine to me if another group of OpenStack projects decide to have shared services (other horizontal teams) and call themselves \"Ring B\".\n\nIn summary, using \"integrated release\" to describe the arbitrary compute ring makes it unique and valuable. It\u0027s just a set of projects submitting themselves to increased constraints, and a number of people lined up to support that same set. Nothing more. Making it artificially valuable won\u0027t give us anything.\n\nI would replace this by a definition of the new \"Compute Base Ring\" concept. You can keep most of the words.. just don\u0027t call it \"The Integrated Release\" ?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"6e76e54707e1c6cf29f1eed6864d550bb36c952a","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Compute Base Layer"},{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The Integrated Release is built on the \"Compute Base Layer\", a"},{"line_number":13,"context_line":"collection of tightly integrated foundation projects for managing"},{"line_number":14,"context_line":"compute resources. The Compute Base Layer is the minimal set of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_cb277fc8","line":11,"updated":"2014-10-28 15:51:15.000000000","message":"I\u0027m not completely sure the Base Layer should be labeled \"Compute\" - we build clouds and clouds can be compute or storage focused. \n\nI want more discussion around both the label and the layer definition. Some thoughts here:\n\nCross-Project Layer\ninfra, docs, quality, release management, common libraries\n\nBasic Layer\ncompute, images, identity\n\nAdded Services Layer\nstorage(object,block,files), networking (include load balancing), data (include databases, dns)\n\nUser Services Layer\nuser interface, messages, orchestration, encryption, SDKs\n\nOps Services Layer\nmetering, monitoring, deploying\n\nThen each Layer would have a set of expectations as an OpenStack layer, and a map can be drawn for required integration points that are tested and documented.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"e986cf405384f5e1c119cfa18ee08b094ce6be56","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Compute Base Layer"},{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The Integrated Release is built on the \"Compute Base Layer\", a"},{"line_number":13,"context_line":"collection of tightly integrated foundation projects for managing"},{"line_number":14,"context_line":"compute resources. The Compute Base Layer is the minimal set of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_3c4e7d97","line":11,"in_reply_to":"5a890539_4d82b9c9","updated":"2014-11-18 19:32:15.000000000","message":"Completely agree with Zane here. This is partly why I don\u0027t see value in using anything other than a set of structured (and target-audience-focused) tags to describe code that lives in the openstack/ code namespace. It inevitably will devolve into yet another discussion of \"But is it *core* OpenStack?\"","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"50b9c1db7deb80d37b32356b705960b54e48ab26","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Compute Base Layer"},{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The Integrated Release is built on the \"Compute Base Layer\", a"},{"line_number":13,"context_line":"collection of tightly integrated foundation projects for managing"},{"line_number":14,"context_line":"compute resources. The Compute Base Layer is the minimal set of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_4d82b9c9","line":11,"in_reply_to":"9aa7fdbe_cb277fc8","updated":"2014-11-18 17:20:24.000000000","message":"\u003e we build clouds and clouds can be compute or storage focused.\n\nIn theory, clouds could also be messaging-focused.\n\nI don\u0027t think this layering approach is ever going to yield interesting results, because the use-case are not linear combinations of layers. For example, you said that clouds can be storage-focused rather than compute-focused, yet to build one you\u0027d have to take only 1/3 of the \"Basic\" layer and combine it with 1/3 of 1/3 of the \"Added Services\" layer.\n\nRemember how in the TC-Board meeting it took less than 10 minutes for a board member to declare the Compute Base layer the new Core? That\u0027s inevitably how all this will be perceived.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Compute Base Layer"},{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The Integrated Release is built on the \"Compute Base Layer\", a"},{"line_number":13,"context_line":"collection of tightly integrated foundation projects for managing"},{"line_number":14,"context_line":"compute resources. The Compute Base Layer is the minimal set of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_bf7ef116","line":11,"in_reply_to":"9aa7fdbe_cb277fc8","updated":"2014-10-28 17:33:56.000000000","message":"Agreed. I prefer the term \"foundational services\", and I think swift should be included in that list.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"5818e408244b0ad148295cee7e9931f3dc739b73","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Compute Base Layer"},{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The Integrated Release is built on the \"Compute Base Layer\", a"},{"line_number":13,"context_line":"collection of tightly integrated foundation projects for managing"},{"line_number":14,"context_line":"compute resources. The Compute Base Layer is the minimal set of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_01d79aee","line":11,"in_reply_to":"9aa7fdbe_cb277fc8","updated":"2014-11-18 18:58:11.000000000","message":"I briefly mentioned a proposal to have the \u0027base layer\u0027 be infrastructure (Compute, Networking and Storage) but that didn\u0027t seem like a good option when I presented it.  I\u0027d be curious to get some documented input here, also bringing it up again just as a result of Anne\u0027s comment, which by the way I agree with.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"68e15fb06b309eaa6e0af03ca3fef5352223c808","unresolved":false,"context_lines":[{"line_number":12,"context_line":"The Integrated Release is built on the \"Compute Base Layer\", a"},{"line_number":13,"context_line":"collection of tightly integrated foundation projects for managing"},{"line_number":14,"context_line":"compute resources. The Compute Base Layer is the minimal set of"},{"line_number":15,"context_line":"services \"needed to start a virtual machine,\" and is an instance of a"},{"line_number":16,"context_line":":ref:`strictly co-dependent project group"},{"line_number":17,"context_line":"\u003cco-dependent-project-groups\u003e`. The group includes:"},{"line_number":18,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_edb8b2e7","line":15,"updated":"2014-10-29 17:20:46.000000000","message":"So where does this stand with the recent extensions in the mandates of some of these compute base layer projects?\n\ne.g. glance expanding into a generalized artifact catalog (acting a repo for non-image data such as Heat templates) or keystone getting into audit (as opposed to being a pure identity service)\n\nShould these mandate expansions now be split off into separate projects?\n\nAnd conversely, does this blessing of the ring0 act as a perverse incentive to add new stuff to existing ever-more monolithic projects?\n\n(as opposed to spinning up an entirely new project, or splitting off something from an existing ring0 project that isn\u0027t fully core to the project\u0027s mission)","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2889,"name":"Aeva Black","email":"aeva.online@gmail.com","username":"tenbrae"},"change_message_id":"27494ae49789e0754d2128947ef55992a9814008","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"The Integrated Release is made up of projects that have integration"},{"line_number":29,"context_line":"test gate jobs shared with one or more Compute Base Layer *and* follow"},{"line_number":30,"context_line":"the policies described here. Some projects may co-gate without"},{"line_number":31,"context_line":"following the other policies and opt out of the Integrated Release."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Integrated Release Members"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a8c0949_86fc5e40","line":30,"updated":"2014-10-31 08:35:42.000000000","message":"\"may depend on or co-gate with other projects, without\"","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":51,"context_line":"Scope and Dependencies"},{"line_number":52,"context_line":"----------------------"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":".. Suggestion 2: Make Layer #1 assume the rest of Layer #1 will always be there"},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"* Projects may assume that members of the Compute Base Layer are"},{"line_number":57,"context_line":"  present in any deployment."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_9fe92db9","line":54,"updated":"2014-10-28 17:33:56.000000000","message":"I feel like this line should go. Its weird to be quoting a blog post here.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"5818e408244b0ad148295cee7e9931f3dc739b73","unresolved":false,"context_lines":[{"line_number":54,"context_line":".. Suggestion 2: Make Layer #1 assume the rest of Layer #1 will always be there"},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"* Projects may assume that members of the Compute Base Layer are"},{"line_number":57,"context_line":"  present in any deployment."},{"line_number":58,"context_line":"* Projects should leverage existing functionality in other Integrated"},{"line_number":59,"context_line":"  Release projects as much as possible."},{"line_number":60,"context_line":"* Projects must not have hard dependencies on projects outside of the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_215f3677","line":57,"updated":"2014-11-18 18:58:11.000000000","message":"Would it be useful at all to modify this to say:\nProjects *should* assume the presence of projects defined as Base Layer being present in any deployment.  \n\nIdea being that we should write code based on the premise but that it isn\u0027t actually a real world fact.\n\nAlso I left the whole \"Compute is the base layer\" thing out of it intentionally.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":59,"context_line":"  Release projects as much as possible."},{"line_number":60,"context_line":"* Projects must not have hard dependencies on projects outside of the"},{"line_number":61,"context_line":"  Integrated Release, but may have optional dependencies on them"},{"line_number":62,"context_line":"  through pluggable components such as drivers."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"API"},{"line_number":65,"context_line":"---"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_5f0a658a","line":62,"updated":"2014-10-28 17:33:56.000000000","message":"I like all of this, because it simplifies our configuration handling.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"5818e408244b0ad148295cee7e9931f3dc739b73","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"Upgrades"},{"line_number":111,"context_line":"--------"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Seamless upgradability of OpenStack components remains the most"},{"line_number":114,"context_line":"requested feature by deployers and operators. Once a deployer of"},{"line_number":115,"context_line":"OpenStack has installed a cloud, there is an implicit expectation that"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_2162d616","line":112,"updated":"2014-11-18 18:58:11.000000000","message":"Honestly I like this whole section, but the other thing that we try and ignore (and I don\u0027t think we should) is the whole deployment side of it.\n\nI realize this is extremely unpopular as most large contributors provide their value add via distro/installer, but I do think the fact that we sort of ignore this aspect is part of what makes upgradability a challenge in many cases.\n\nI also realize it\u0027s a difficult problem that nobody wants to touch in terms of \"picking winners and losers\", but maybe it would be worth taking a look at what open source install tool currently has the most traction, consider the winner picked by the Operator Community already and focus on it?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"e986cf405384f5e1c119cfa18ee08b094ce6be56","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"Upgrades"},{"line_number":111,"context_line":"--------"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Seamless upgradability of OpenStack components remains the most"},{"line_number":114,"context_line":"requested feature by deployers and operators. Once a deployer of"},{"line_number":115,"context_line":"OpenStack has installed a cloud, there is an implicit expectation that"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_c763e2db","line":112,"in_reply_to":"5a890539_2162d616","updated":"2014-11-18 19:32:15.000000000","message":"Well, there just isn\u0027t one that would be picked, frankly. Tell a Chef shop to start using Ansible and they\u0027ll look at you funny. Tell a CD shop that\u0027s using image-based deployments to start using configuration-management-based deployments, and they\u0027ll yell at you for messing with their flows. In the end, deployers and operators will pick a tool (or set of tools) that matches their own worldviews, their own tolerances for instability, and their own infrastructure preferences. There will never be a one-size-fits-all deployment tool I\u0027m afraid, because there\u0027s not one-size-fits-all deployers.\n\nThis is partly why I\u0027ve been pushing the TC to consider letting multiple overlapping or competing projects exist in the openstack/ code namespace and let development naturally produce winners and losers (or winners and winners -- it\u0027s not a zero-sum game).","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":114,"context_line":"requested feature by deployers and operators. Once a deployer of"},{"line_number":115,"context_line":"OpenStack has installed a cloud, there is an implicit expectation that"},{"line_number":116,"context_line":"it can be upgraded in place on the existing hardware without creating"},{"line_number":117,"context_line":"downtime for any of the active resources that the cloud manages."},{"line_number":118,"context_line":""},{"line_number":119,"context_line":"As such, we expect projects to have a path for inplace upgrading from:"},{"line_number":120,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_9f0e8d8a","line":117,"updated":"2014-10-28 17:33:56.000000000","message":"So, moving this here implies to me that we only care about this for integrated release projects. I don\u0027t think that\u0027s necessarily true? Don\u0027t we want it for more than that?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"18efbef6142c0e34e35631eee87c8ba0d6b307df","unresolved":false,"context_lines":[{"line_number":116,"context_line":"it can be upgraded in place on the existing hardware without creating"},{"line_number":117,"context_line":"downtime for any of the active resources that the cloud manages."},{"line_number":118,"context_line":""},{"line_number":119,"context_line":"As such, we expect projects to have a path for inplace upgrading from:"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"* one stable release to the next stable release (i.e. stable/havana \u003d\u003e"},{"line_number":122,"context_line":"  stable/icehouse)"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_2801086a","line":119,"range":{"start_line":119,"start_character":47,"end_line":119,"end_character":54},"updated":"2014-10-27 20:36:09.000000000","message":"Should be \"in place\" or \"in-place\" ?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"a7db66af0fd306112a0bc026f7af8a0d1e6995de","unresolved":false,"context_lines":[{"line_number":116,"context_line":"it can be upgraded in place on the existing hardware without creating"},{"line_number":117,"context_line":"downtime for any of the active resources that the cloud manages."},{"line_number":118,"context_line":""},{"line_number":119,"context_line":"As such, we expect projects to have a path for inplace upgrading from:"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"* one stable release to the next stable release (i.e. stable/havana \u003d\u003e"},{"line_number":122,"context_line":"  stable/icehouse)"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_8b33cef4","line":119,"in_reply_to":"9aa7fdbe_2801086a","updated":"2014-10-27 20:54:06.000000000","message":"Yes, probably in-place. I\u0027ll update that with the next patch set.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"6e76e54707e1c6cf29f1eed6864d550bb36c952a","unresolved":false,"context_lines":[{"line_number":141,"context_line":""},{"line_number":142,"context_line":"Cross-Team Coordination"},{"line_number":143,"context_line":"-----------------------"},{"line_number":144,"context_line":""},{"line_number":145,"context_line":".. based on http://lists.openstack.org/pipermail/openstack-dev/2014-August/043812.html"},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"Teams participating in the Integrated Release are integrated at the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_eba0c391","line":144,"updated":"2014-10-28 15:51:15.000000000","message":"As this is the biggest source of pain and a problem to solve, I\u0027d like to see this at the top, even before defining layers. \n\nAlso I need some \"think time\" about what picking and choosing integration points means for docs, but that doesn\u0027t need to be codified here. I just think that the placement indicates emphasis and we should reverse it.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":155,"context_line":"- Oslo liaison"},{"line_number":156,"context_line":"- Documentation liaison"},{"line_number":157,"context_line":"- Security/vulnerability"},{"line_number":158,"context_line":"- Stable branch support"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_1f1a9dc5","line":158,"updated":"2014-10-28 17:33:56.000000000","message":"We should provide guidance on how to select people to fill these roles, even if its \"these roles are appointed at the discretion of the PTL for the period of one release\".","commit_id":"34e9ff9b7882675d3038092688669a061500a485"}],"reference/official-projects.rst":[{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"28d9a59b5a453db178ea2c280b83280f90c55e4e","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Project Teams who place themselves under the oversight of the"},{"line_number":6,"context_line":"Technical Committee and meet the requirements (see"},{"line_number":7,"context_line":":doc:`new-team-requirements`) may be granted official status as part"},{"line_number":8,"context_line":"of the OpenStack project. Official status comes with some benefits in"},{"line_number":9,"context_line":"terms of expectations of support from the other OpenStack projects."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":".. Suggestion 7: User interface tools should be aggressive in talking to anything we release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_9fadad9d","line":8,"updated":"2014-10-28 17:12:08.000000000","message":"I think this is redundant with what\u0027s already said of official project teams @ new-team-requirements.rst and charter.rst. Is there value in reiterating this for a 3rd time ?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":8,"context_line":"of the OpenStack project. Official status comes with some benefits in"},{"line_number":9,"context_line":"terms of expectations of support from the other OpenStack projects."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":".. Suggestion 7: User interface tools should be aggressive in talking to anything we release."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Client and UI tool projects are encouraged to actively support all"},{"line_number":14,"context_line":"  official projects."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_3f63e142","line":11,"updated":"2014-10-28 17:33:56.000000000","message":"Again I find the blog quoting unnecessary.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"}],"reference/project-release-schedules.rst":[{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":68,"context_line":"at the end of the development cycle. It is recommended that they follow a"},{"line_number":69,"context_line":"Compatible Release Cycle."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":".. Suggestion 10: End user tools should adopt a rolling release model"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Teams working on projects intended to interact with OpenStack"},{"line_number":74,"context_line":"services, such as client libraries and user interfaces, are encouraged"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_5ff4255a","line":71,"updated":"2014-10-28 17:33:56.000000000","message":"Ditto","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":71,"context_line":".. Suggestion 10: End user tools should adopt a rolling release model"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Teams working on projects intended to interact with OpenStack"},{"line_number":74,"context_line":"services, such as client libraries and user interfaces, are encouraged"},{"line_number":75,"context_line":"to adopt a Free Release Cycle. Releasing a new version of a project"},{"line_number":76,"context_line":"when the code is stable gives end users immediate access to new features"},{"line_number":77,"context_line":"and bug fixes, which makes using OpenStack deployments easier."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_5f9b4517","line":74,"updated":"2014-10-28 17:33:56.000000000","message":"Wait, so we don\u0027t think Horizon should use the standard release cycle?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"50b9c1db7deb80d37b32356b705960b54e48ab26","unresolved":false,"context_lines":[{"line_number":71,"context_line":".. Suggestion 10: End user tools should adopt a rolling release model"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Teams working on projects intended to interact with OpenStack"},{"line_number":74,"context_line":"services, such as client libraries and user interfaces, are encouraged"},{"line_number":75,"context_line":"to adopt a Free Release Cycle. Releasing a new version of a project"},{"line_number":76,"context_line":"when the code is stable gives end users immediate access to new features"},{"line_number":77,"context_line":"and bug fixes, which makes using OpenStack deployments easier."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_0d49918e","line":74,"in_reply_to":"9aa7fdbe_5f9b4517","updated":"2014-11-18 17:20:24.000000000","message":"I think Monty thinks that.\n\nHorizon is both a user interface and a Server project though, so I don\u0027t think this is going to offer any real clear guidance.","commit_id":"34e9ff9b7882675d3038092688669a061500a485"}],"reference/project-testing-policies.rst":[{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"f23f91262d90ced1124f6cb212f2ebb512f8c5f7","unresolved":false,"context_lines":[{"line_number":25,"context_line":".. Suggestion 6: EVERYTHING participates in a single install-only devstack gate"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Projects must be included in devstack\u0027s global installation"},{"line_number":28,"context_line":"integration test job."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Optional Inter-Project Dependencies"},{"line_number":31,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_9ab69bf7","line":28,"updated":"2014-10-28 17:33:56.000000000","message":"Whatfore is an installation integration test?","commit_id":"34e9ff9b7882675d3038092688669a061500a485"},{"author":{"_account_id":2889,"name":"Aeva Black","email":"aeva.online@gmail.com","username":"tenbrae"},"change_message_id":"27494ae49789e0754d2128947ef55992a9814008","unresolved":false,"context_lines":[{"line_number":25,"context_line":".. Suggestion 6: EVERYTHING participates in a single install-only devstack gate"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Projects must be included in devstack\u0027s global installation"},{"line_number":28,"context_line":"integration test job."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Optional Inter-Project Dependencies"},{"line_number":31,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a8c0949_66ff7235","line":28,"updated":"2014-10-31 08:35:42.000000000","message":"enforcing that installation dependencies don\u0027t conflict across projects","commit_id":"34e9ff9b7882675d3038092688669a061500a485"}]}