{"id":7386,"date":"2015-10-16T16:14:43","date_gmt":"2015-10-16T21:14:43","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7386"},"modified":"2015-10-19T16:51:12","modified_gmt":"2015-10-19T21:51:12","slug":"openstack-weekly-community-newsletter-oct-10-16","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-weekly-community-newsletter-oct-10-16\/","title":{"rendered":"OpenStack Weekly Community Newsletter (Oct.,10-16)"},"content":{"rendered":"<h1 class=\"p1\" style=\"text-align: left\"><span class=\"s1\"><a href=\"https:\/\/www.openstack.org\/software\/liberty\/\">Liberty, the 12th release of OpenStack, came out yesterday<\/a><\/span><\/h1>\n<p class=\"p1\" style=\"text-align: left\" class=\"lead\">With 1,933 individual contributors and 164 organizations contributing to the release, Liberty offers finer-grained management controls, performance enhancements for large deployments and more powerful tools for managing new technologies such as containers in production environments:\u00a0<a href=\"http:\/\/superuser.openstack.org\/articles\/openstack-liberty-a-primer-on-what-s-new\">Learn what&#8217;s new<\/a><\/p>\n<h1 class=\"p1\" style=\"text-align: left\"><a href=\"http:\/\/superuser.openstack.org\/articles\/break-down-those-silos-openstack\">Break down those silos, OpenStack<\/a><\/h1>\n<p style=\"text-align: left\">&#8220;The projects need to come together to develop consistent formats, approaches and messaging,&#8221; says Rochelle Grober, senior software architect at Huawei Technologies and active member of the OpenStack community.<\/p>\n<h1 style=\"text-align: left\">The Road to Tokyo<\/h1>\n<ul style=\"text-align: left\">\n<li class=\"p4\"><a href=\"https:\/\/www.eventbrite.com\/e\/openstack-summit-october-2015-tokyo-tickets-17356780598\">The OpenStack Summit Tokyo will sell out! Register NOW!<\/a><\/li>\n<li class=\"p4\"><a href=\"https:\/\/www.openstack.org\/summit\/tokyo-2015\/schedule\/\">The schedule and mobile app for the OpenStack Summit in Tokyo are now available<\/a>\n<ul>\n<li class=\"p4\">If you have already downloaded an OpenStack Summit mobile app before, no need to do it again! Just refresh your existing app.<\/li>\n<\/ul>\n<\/li>\n<li class=\"p4\"><a href=\"https:\/\/www.openstack.org\/blog\/2015\/10\/openstack-training-sessions-available-in-tokyo\/\">OpenStack training sessions available in Tokyo<\/a>\n<ul>\n<li class=\"p4\">Several ecosystem companies are offering training in Tokyo\u00a0during the week of the Summit. Check out the sessions available and plan your travel accordingly<\/li>\n<\/ul>\n<\/li>\n<li class=\"p4\"><a href=\"https:\/\/www.openstack.org\/summit\/tokyo-2015\/campus-maps\">The Summit maps are now available online<\/a><\/li>\n<li class=\"p4\">Speakers, sponsors, and ATC registration codes deactivate\u00a0<strong>10\/19<\/strong>, so <a href=\"https:\/\/www.eventbrite.com\/e\/openstack-summit-october-2015-tokyo-tickets-17356780598\">register now<\/a>!<\/li>\n<li class=\"p4\"><span class=\"s2\">If the OpenStack Summit Tokyo is going to be your first summit, check out these helpful tips and info:\u00a0<a href=\"https:\/\/www.openstack.org\/summit\/tokyo-2015\/new-to-the-summit\/\"><span class=\"s3\">https:\/\/www.openstack.org\/summit\/tokyo-2015\/new-to-the-summit\/<\/span><\/a>\u00a0<\/span><\/li>\n<li class=\"p4\"><span class=\"s2\">We have created\u00a0<a href=\"https:\/\/www.openstack.org\/summit\/tokyo-2015\/tokyo-and-travel\/#hotels\"><span class=\"s3\">videos and PDF downloads<\/span><\/a>\u00a0to help you navigate from either of the Tokyo airports to the Summit venue.<\/span><\/li>\n<\/ul>\n<h1 style=\"text-align: left\">Community feedback<\/h1>\n<p style=\"text-align: left\">OpenStack is always interested in feedback and community contributions, if you would like to see a new section in the\u00a0OpenStack Weekly Community Newsletter\u00a0or have ideas on how to present content please get in touch:\u00a0<span class=\"s1\"><a href=\"mailto:community@openstack.org\">community@openstack.org<\/a>.<\/span><\/p>\n<h1 class=\"p4\" style=\"text-align: left\"><span class=\"s1\">Reports from Previous Events\u00a0<\/span><\/h1>\n<ul class=\"ul1\" style=\"text-align: left\">\n<li class=\"li5\">None this week<\/li>\n<\/ul>\n<h1 class=\"p4\" style=\"text-align: left\"><span class=\"s1\">Deadlines and Contributors Notifications<\/span><\/h1>\n<ul class=\"ul1\" style=\"text-align: left\">\n<li class=\"li5\"><a href=\"https:\/\/www.gnome.org\/outreachy\/\">Outreachy Mentorship Application deadline: Nov., 02, 2015, 07:00 pm UTC<\/a><\/li>\n<li class=\"li5\">Call for papers:\n<ul>\n<li><a href=\"https:\/\/fosdem.org\/2016\/news\/2015-09-24-call-for-participation\/\">FOSDEM\u201916<\/a> deadline: October 30, 2015<\/li>\n<li><a href=\"http:\/\/conferences.oreilly.com\/oscon\/open-source\/public\/cfp\/423\">OSCON<\/a> 2016 deadline: November 24, 2015<\/li>\n<li><a href=\"http:\/\/continuouslifecycle.london\/call-for-papers\/\">Continuous Lifecycle London<\/a> Deadline: December 1, 2015<\/li>\n<li><a href=\"https:\/\/us.pycon.org\/2016\/speaking\/\">PyCon 2016<\/a> deadline<strong>: <\/strong>Jan 3, 2016<\/li>\n<li><a href=\"https:\/\/www.usenix.org\/conference\/atc16\/call-for-papers\">USENIX Annual Technical Conference 2016<\/a> deadline: February 1, 2016<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1 class=\"p4\" style=\"text-align: left\"><span class=\"s1\">Security Advisories and Notices\u00a0<\/span><\/h1>\n<ul class=\"ul1\" style=\"text-align: left\">\n<li class=\"li5\">None this week<\/li>\n<\/ul>\n<h1 class=\"p4\" style=\"text-align: left\"><span class=\"s1\">Tips \u2018n Tricks\u00a0<\/span><\/h1>\n<ul class=\"ul1\" style=\"text-align: left\">\n<li class=\"li5\">By Nir Yechiel\u00a0and\u00a0Jiri Benc: <a href=\"http:\/\/redhatstackblog.redhat.com\/2015\/10\/15\/troubleshooting-networking-with-rhel-openstack-platform-meet-plotnetcfg\/\">Troubleshooting Networking with RHEL OpenStack Platform: meet\u00a0\u2018plotnetcfg\u2019<\/a><\/li>\n<\/ul>\n<h1 class=\"p6\" style=\"text-align: left\"><span class=\"s2\"><a href=\"https:\/\/www.openstack.org\/community\/events\">Upcoming Events<\/a>\u00a0<\/span><\/h1>\n<ul style=\"text-align: left\">\n<li><a href=\"http:\/\/www.meetup.com\/China-OpenStack-User-Group\/events\/225801881\/\">Oct 17, 2015\u00a0OpenStack\u4e2d\u7684SaaS\u00a0Beijing, CN<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/Minnesota-OpenStack-Meetup\/events\/224638648\/\">Oct 19 &#8211; 20, 2015\u00a0OpenStack Octoberfest!\u00a0Minneapolis, MN, US<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/Triangle-OpenStack-Meetup\/events\/226055043\/\">Oct 19 &#8211; 20, 2015\u00a0OpenStack BoF at All Things Open!\u00a0Raleigh, NC, US<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/Triangle-OpenStack-Meetup\/events\/226055043\/\">Oct 20, 2015\u00a0Easy OpenStack: SolidFire+Platform9\u00a0Sunnyvale, California, US<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/OpenStack-GDL\/events\/225875446\/\">Oct 20, 2015\u00a0Stateless OS: From an OpenStack Perspective &amp; Creacion de Plugins para Tempest\u00a0Guadalajara, MX<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/OpenStack-Hungary-Meetup-Group\/events\/225260922\/\">Oct 21, 2015\u00a0OpenStack 2015 October<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/OpenStackDC\/events\/224954102\/\">Oct 21 &#8211; 22, 2015\u00a0Bi-modal IT &amp; OpenStack (#26) Washington D.C., DC, US<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/OpenStack-STL\/events\/225819101\/\">Oct 22 &#8211; 23, 2015\u00a0October monthly meetup\u00a0Chesterfield, MO, US<\/a><\/li>\n<\/ul>\n<h1 class=\"p6\" style=\"text-align: left\">What You Need to Know From the Developer&#8217;s List<\/h1>\n<div class=\"left-event\" style=\"text-align: left\"><\/div>\n<h2 style=\"text-align: left\"><a href=\"https:\/\/wiki.openstack.org\/wiki\/Successes\"><span style=\"font-weight: 400\">Success Bot Says<\/span><\/a><\/h2>\n<ul style=\"text-align: left\">\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">ttx: Another OpenStack Release!<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">With help of <\/span><span style=\"font-weight: 400\">jesusaurus, the infra team has deployed Kibana 3. First steps in upgrading elastic search cluster.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">shamail: Product Working Group wiki fully updated [1]<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">tristanC: 6 new TC members have been elected[2]<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">AJaeger: OpenStack API Quick Start converted to RST [3], and translated to German [4] and Japanese [5].<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">reed: section 2 and 3 of the OpenStack Shade tutorial merged. Now work on section [6].<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">sirushti: Heat just announced support for Python 3.4 [7].<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">AJaegar: All Documentation manuals have been updated with content for Liberty [8].<\/span><\/li>\n<\/ul>\n<h2 style=\"text-align: left\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076962.html\"><span style=\"font-weight: 400\">Upgrade to Gerrit 2.11<\/span><\/a><\/h2>\n<ul style=\"text-align: left\">\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">The OpenStack Infra team would like to upgrade from Gerrit 2.8 to 2.11.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Proposing to do the upgrade shortly after the Mitaka summit.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Motivation: Take advantage of some of the new REST API, ssh commands, and stream events features.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">There is a big UI change in 2.11, in which 2.8 includes both the old and new style.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Preview 2.11 [9].<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">If you don\u2019t like Gerrit 2.11, give Gertty [10] a try.<\/span><\/li>\n<\/ul>\n<h2 style=\"text-align: left\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076592.html\"><span style=\"font-weight: 400\">Service Catalog: The Next Generation (Cont.)<\/span><\/a><\/h2>\n<ul style=\"text-align: left\">\n<li style=\"font-weight: 400\"><a href=\"http:\/\/www.openstack.org\/blog\/2015\/10\/openstack-weekly-community-newsletter-oct-3-oct-9\/#dev-digest-service-catalog\"><span style=\"font-weight: 400\">Continuing from last week summary\u2026<\/span><\/a><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Sean Dague realizes that while people want to go in much more radical directions here, we should be careful. This is not a blank slate, as there are enough users using it that we must do careful shifts that enable a new thing similar to the old thing.<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Moving away from REST is too much, at least in the next 6 to 12 months.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Getting a service catalog over REST without auth, or tenant IDs gets us somewhere to figure out a DNS representation.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2 style=\"text-align: left\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/077033.html\"><span style=\"font-weight: 400\">Establishing Release Liaisons for Mitaka<\/span><\/a><\/h2>\n<ul style=\"text-align: left\">\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Doug Hellmann writes that the release management team relies on liaisons from each project to be available for coordination for work across all teams.<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Responsibilities of release liaisons [11].<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Signup [12].<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2 style=\"text-align: left\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/077033.html\"><span style=\"font-weight: 400\">Release Communication During Mitaka<\/span><\/a><\/h2>\n<ul style=\"text-align: left\">\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Doug Hellmann begins one of many emails describing difference in the way we handle release management for the Mitaka cycle.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">In the past, we\u2019ve had communication issues where project team leads didn\u2019t see or pay attention to release related announcements.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">This email was sent to the list and individual project team leads, to improve the odds that all will see it.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">\u201c[release]\u201d topic tag on the openstack-dev mailing list will be used.<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">All project team leads and release liaison should configuring their email client to ensure the messages are visible.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2 style=\"text-align: left\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076518.html\"><span style=\"font-weight: 400\">Requests + urllib3 + distro package (cont.)<\/span><\/a><\/h2>\n<ul style=\"text-align: left\">\n<li style=\"font-weight: 400\"><a href=\"http:\/\/www.openstack.org\/blog\/2015\/10\/openstack-weekly-community-newsletter-oct-3-oct-9\/#dev-digest-requests\"><span style=\"font-weight: 400\">Continuing discussions from last week\u2026<\/span><\/a><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Robert Collins comments a trivial workaround is to always use virtualenvs and not system-site-packages.<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Has OpenStack infra team considered using system-site-packages?<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Yes, but we take advantage of the python ecosystem uploading new releases to PyPI. We can then pretty instantly test compatibility of our software with new releases of dependencies.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">A way forward is:<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Get distros to fix their requests python dependencies<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ubuntu [13]<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Fedora [14][15][16]<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Fix existing known bugs in pip where such dependencies are violated by some operations.<\/span><\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Stop using vendorized version of requests and fork the project to use dependencies it should from the start.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Convince upstream to stop vendorizing urllib3.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Always use distro packages of requests, never from virtual environments.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2 style=\"text-align: left\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076373.html\"><span style=\"font-weight: 400\">Scheduler Proposal (cont.)<\/span><\/a><\/h2>\n<ul style=\"text-align: left\">\n<li style=\"font-weight: 400\"><a href=\"http:\/\/www.openstack.org\/blog\/2015\/10\/openstack-weekly-community-newsletter-oct-3-oct-9\/#dev-digest-scheduler\"><span style=\"font-weight: 400\">Continuing from last week\u2019s summary&#8230;<\/span><\/a><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Ed notes that Josh Harlow\u2019s solution isn\u2019t too different than the current design of hosts sending their state to the scheduler.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">The reason for Cassandra proposal was to eliminate the duplication and have resources being scheduler and the scheduler itself all working with the same data.<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">This is the intent of the current design. The data can never be perfect, so work with what you have and hope the rest of the system deals with your mistakes and gracefully retry. (e.g. scheduled compute node no longer has resources to accommodate a request.)<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">To make this solution possible for downstream distributions and\/or OpenStack users) you have to solve:<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Cassandra developers upstream should start caring about OpenJDK.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Or Oracle should make its JVM free software.<\/span><\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Clint notes that Cassandra does not recommend OpenJDK [17].<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Thomas adds:<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Upstream does not test against OpenJDK.<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">They close bugs without fixing them when it only affects OpenJDK.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Thierry is generally negative about Java solutions as this being one of the reasons [18]. The free software JVM is not on par with the non-free JVM. We then indirectly force our users to use a non-free dependency. When the java solution is the only solution for a problem space, that might still be a good trade-off versus reinventing the wheel. However, for distributed locks and sharing state, there are some other good options out there.<\/span>\n<ul>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Clint mentions that Zookeeper is different from Cassandra. He has had success with OpenJDK. It\u2019s also available on Debian\/Ubuntu making access for developers much easier.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[1] &#8211; <\/span><a href=\"https:\/\/wiki.openstack.org\/wiki\/ProductTeam\"><span style=\"font-weight: 400\">https:\/\/wiki.openstack.org\/wiki\/ProductTeam<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[2] &#8211; <\/span><a href=\"https:\/\/wiki.openstack.org\/wiki\/TC_Elections_September\/October_2015#Results\"><span style=\"font-weight: 400\">https:\/\/wiki.openstack.org\/wiki\/TC_Elections_September\/October_2015#Results<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[3] &#8211; <\/span><a href=\"http:\/\/developer.openstack.org\/api-guide\/quick-start\/\"><span style=\"font-weight: 400\">http:\/\/developer.openstack.org\/api-guide\/quick-start\/<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[4] &#8211; <\/span><a href=\"http:\/\/developer.openstack.org\/de\/api-guide\/quick-start\/\"><span style=\"font-weight: 400\">http:\/\/developer.openstack.org\/de\/api-guide\/quick-start\/<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[5] &#8211; <\/span><a href=\"http:\/\/developer.openstack.org\/api-guide\/quick-start\/\"><span style=\"font-weight: 400\">http:\/\/developer.openstack.org\/api-guide\/quick-start\/<\/span><span style=\"font-weight: 400\"><br \/>\n<\/span><\/a><span style=\"font-weight: 400\">[6] &#8211; <\/span><a href=\"https:\/\/review.openstack.org\/#\/c\/232810\/\"><span style=\"font-weight: 400\">https:\/\/review.openstack.org\/#\/c\/232810\/<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[7] &#8211; <\/span><a href=\"https:\/\/review.openstack.org\/231557\"><span style=\"font-weight: 400\">https:\/\/review.openstack.org\/231557<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[8] &#8211; <\/span><a href=\"http:\/\/docs.openstack.org\/liberty\/\"><span style=\"font-weight: 400\">http:\/\/docs.openstack.org\/liberty\/<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[9] &#8211; <\/span><a href=\"http:\/\/review-dev.openstack.org\"><span style=\"font-weight: 400\">http:\/\/review-dev.openstack.org<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[10] &#8211; <\/span><a href=\"https:\/\/pypi.python.org\/pypi\/gertty\"><span style=\"font-weight: 400\">https:\/\/pypi.python.org\/pypi\/gertty<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[11] &#8211; <\/span><a href=\"http:\/\/docs.openstack.org\/project-team-guide\/release-management.html#release-liaisons\"><span style=\"font-weight: 400\">http:\/\/docs.openstack.org\/project-team-guide\/release-management.html#release-liaisons<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[12] &#8211; <\/span><a href=\"https:\/\/wiki.openstack.org\/wiki\/CrossProjectLiaisons#Release_management\"><span style=\"font-weight: 400\">https:\/\/wiki.openstack.org\/wiki\/CrossProjectLiaisons#Release_management<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[13] &#8211; <\/span><a href=\"https:\/\/bugs.launchpad.net\/ubuntu\/+source\/python-requests\/+bug\/1505038\"><span style=\"font-weight: 400\">https:\/\/bugs.launchpad.net\/ubuntu\/+source\/python-requests\/+bug\/1505038<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[14] &#8211; <\/span><a href=\"https:\/\/bodhi.fedoraproject.org\/updates\/FEDORA-2015-20de3774f4\"><span style=\"font-weight: 400\">https:\/\/bodhi.fedoraproject.org\/updates\/FEDORA-2015-20de3774f4<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[15] &#8211; <\/span><a href=\"https:\/\/bodhi.fedoraproject.org\/updates\/FEDORA-2015-1f580ccfa4\"><span style=\"font-weight: 400\">https:\/\/bodhi.fedoraproject.org\/updates\/FEDORA-2015-1f580ccfa4<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[16] &#8211; <\/span><a href=\"https:\/\/bodhi.fedoraproject.org\/updates\/FEDORA-2015-d7c710a812\"><span style=\"font-weight: 400\">https:\/\/bodhi.fedoraproject.org\/updates\/FEDORA-2015-d7c710a812<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[17] &#8211; <\/span><a href=\"https:\/\/github.com\/apache\/cassandra\/blob\/trunk\/src\/java\/org\/apache\/cassandra\/service\/StartupChecks.java#L153-L155\"><span style=\"font-weight: 400\">https:\/\/github.com\/apache\/cassandra\/blob\/trunk\/src\/java\/org\/apache\/cassandra\/service\/StartupChecks.java#L153-L155<\/span><\/a><\/p>\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">[18] &#8211; <\/span><a href=\"https:\/\/twitter.com\/mipsytipsy\/status\/596697501991702528\"><span style=\"font-weight: 400\">https:\/\/twitter.com\/mipsytipsy\/status\/596697501991702528<\/span><\/a><\/p>\n<h1 style=\"text-align: left\">OpenStack Reactions<\/h1>\n<div style=\"width: 580px;\" class=\"wp-video\"><!--[if lt IE 9]><script>document.createElement('video');<\/script><![endif]-->\n<video class=\"wp-video-shortcode\" id=\"video-7386-1\" width=\"580\" height=\"325\" preload=\"metadata\" controls=\"controls\"><source type=\"video\/webm\" src=\"https:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2015\/10\/reaction.webm?_=1\" \/><a href=\"https:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2015\/10\/reaction.webm\">https:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2015\/10\/reaction.webm<\/a><\/video><\/div>\n<p class=\"entry-title\">plug keystone\u2019s authtoken middleware into a service &#8220;so graceful&#8221;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Liberty, the 12th release of OpenStack, came out yesterday With 1,933 individual contributors and 164 organizations contributing to the release, Liberty offers finer-grained management controls, performance enhancements for large deployments and more powerful tools for managing new technologies such as containers in production environments:\u00a0Learn what&#8217;s new Break down those silos, OpenStack &#8220;The projects need to&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-weekly-community-newsletter-oct-10-16\/\" class=\"more-link\" title=\"Read OpenStack Weekly Community Newsletter (Oct.,10-16)\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":81,"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\/7386"}],"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\/81"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=7386"}],"version-history":[{"count":19,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7386\/revisions"}],"predecessor-version":[{"id":7413,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7386\/revisions\/7413"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=7386"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=7386"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=7386"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}