{"id":7643,"date":"2016-02-20T10:31:19","date_gmt":"2016-02-20T16:31:19","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7643"},"modified":"2016-02-20T10:59:52","modified_gmt":"2016-02-20T16:59:52","slug":"openstack-developer-mailing-list-digest-20160219","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160219\/","title":{"rendered":"OpenStack Developer Mailing List Digest Feb 13-19"},"content":{"rendered":"<h1>OpenStack Operators<\/h1>\n<ul>\n<li>Takeaways from the OpenStack Mid-Cycle Ops Meetup: first time\u2019s the charm [1]<\/li>\n<li>OpenStack Upgrading Tutorial: 11 pitfalls and solutions [2]<\/li>\n<\/ul>\n<h1>\u201cNo Open Core\u201d in 2016 (continuing)<\/h1>\n<ul>\n<li>Continuing with discussions on Poppy in particular, Doug Hellmann raises that the Poppy team has done everything we&#8217;ve asked. The governance currently emphasizes on the social aspects of the project and community interactions. Tell the Poppy team they \u201care not OpenStack\u201d even though they followed things is distressing.<\/li>\n<li>Sean Dague mentions that solutions like Neutron have an open source solution. It may needed some work, but at least there was one open source solution for testing.<\/li>\n<li>Dean Troyer brings up how we have things like Cinder with commerical products as storage drivers. Even without those storage drivers though, Cinder is still useful.<\/li>\n<li>Poppy&#8217;s open source implementation option, OpenCDN is currently an abandoned project.<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/085855.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/085855.html<\/a><\/li>\n<\/ul>\n<h1>Upgrade Implications of Lots of Content in paste.ini<\/h1>\n<ul>\n<li>A set of Cross-origin resource sharing (CORS) patches came out recently [3], that adds a ton of content to paste.ini.<\/li>\n<li>Paste.ini is a config that operators can change.\n<ul>\n<li>Large amounts of complicated things in there which may change in future releases is really problematic.<\/li>\n<li>Deprecating content also is a challenge.<\/li>\n<li>Why aren&#8217;t these options just the defaults of the CORS middlware?\n<ul>\n<li>Some projects like Ironic did request to not have headers prescribed, for eample, if Ironic is using something other than Keystone, different allowed headers would be required.<\/li>\n<li>However, Keystone is defcore, so the default should be useful there first. Then be flexible to other auth options can go on top.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Where do we go from here?\n<ul>\n<li>Option 1: Implement as is, keep things consistent, fix them in Newton.\n<ul>\n<li>This is not fixable in Newton as it requires deprecating out for the next three releases.<\/li>\n<\/ul>\n<\/li>\n<li>Option 2: Try to fix it in Mitaka 2 of CORS middleware setting defaults and projects having the ability to override [4].\n<ul>\n<li>This will require patches against a bunch of projects [5]. Who can help?<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086746.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086746.html<\/a><\/li>\n<\/ul>\n<p class=\"lead\">&nbsp;<\/p>\n<p>[1] &#8211; <a href=\"http:\/\/superuser.openstack.org\/articles\/takeaways-from-the-openstack-mid-cycle-ops-meetup-first-time-s-the-charm\">http:\/\/superuser.openstack.org\/articles\/takeaways-from-the-openstack-mid-cycle-ops-meetup-first-time-s-the-charm<\/a><\/p>\n<p>[2] &#8211; <a href=\"http:\/\/superuser.openstack.org\/articles\/openstack-upgrading-tutorial-11-pitfalls-and-solutions\">http:\/\/superuser.openstack.org\/articles\/openstack-upgrading-tutorial-11-pitfalls-and-solutions<\/a><\/p>\n<p>[3] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/265415\/1\">https:\/\/review.openstack.org\/#\/c\/265415\/1<\/a><\/p>\n<p>[4] &#8211; <a href=\"http:\/\/docs.openstack.org\/developer\/oslo.config\/generator.html#modifying-defaults-from-other-namespaces\">http:\/\/docs.openstack.org\/developer\/oslo.config\/generator.html#modifying-defaults-from-other-namespaces<\/a><\/p>\n<p>[5] &#8211; <a href=\"http:\/\/governance.openstack.org\/reference\/projects\/index.html\">http:\/\/governance.openstack.org\/reference\/projects\/index.html<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>OpenStack Operators Takeaways from the OpenStack Mid-Cycle Ops Meetup: first time\u2019s the charm [1] OpenStack Upgrading Tutorial: 11 pitfalls and solutions [2] \u201cNo Open Core\u201d in 2016 (continuing) Continuing with discussions on Poppy in particular, Doug Hellmann raises that the Poppy team has done everything we&#8217;ve asked. The governance currently emphasizes on the social aspects&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160219\/\" class=\"more-link\" title=\"Read OpenStack Developer Mailing List Digest Feb 13-19\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":82,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7643"}],"collection":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/users\/82"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=7643"}],"version-history":[{"count":2,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7643\/revisions"}],"predecessor-version":[{"id":7645,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7643\/revisions\/7645"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=7643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=7643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=7643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}