{"id":7351,"date":"2015-10-09T13:51:03","date_gmt":"2015-10-09T18:51:03","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7351"},"modified":"2015-10-16T12:45:33","modified_gmt":"2015-10-16T17:45:33","slug":"openstack-weekly-community-newsletter-oct-3-oct-9","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-weekly-community-newsletter-oct-3-oct-9\/","title":{"rendered":"OpenStack Weekly Community Newsletter (Oct. 3 \u2013 Oct. 9)"},"content":{"rendered":"<h1 style=\"text-align: left;\"><strong><a href=\"http:\/\/superuser.openstack.org\/articles\/what-you-need-to-know-about-astara\">What you need to know about Astara<\/a><\/strong><\/h1>\n<p style=\"text-align: left;\" class=\"lead\">Henrik Rosendahl, CEO of Akanda, introduces OpenStack&#8217;s newest project, an open-source network orchestration platform built by OpenStack operators\u00a0for OpenStack clouds.<\/p>\n<h1 style=\"text-align: left;\"><strong><a href=\"http:\/\/superuser.openstack.org\/articles\/an-openstack-security-primer\">An OpenStack security primer<\/a><\/strong><\/h1>\n<p style=\"text-align: left;\">Meet the troubleshooters and firefighters of the OpenStack Security project and how you can get involved.<\/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<\/ul>\n<h1 style=\"text-align: left;\"><\/h1>\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:\/\/wiki.openstack.org\/wiki\/Liberty_Release_Schedule\">Liberty Release Oct., 15, 2015<\/a><\/li>\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=\"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 style=\"text-align: left;\"><a href=\"http:\/\/superuser.openstack.org\/articles\/superuser-awards-your-vote-counts\">Superuser Awards: your vote counts<\/a><\/h1>\n<h3 style=\"text-align: left;\">(voting closes on 10\/12 at 11:59 pm PT)<\/h3>\n<ul style=\"text-align: left;\">\n<li class=\"lead\">Vote for one of the four finalists:\u00a0<a href=\"http:\/\/superuser.openstack.org\/articles\/tokyo-superuser-awards-finalist-fico\">FICO<\/a>, <a href=\"http:\/\/superuser.openstack.org\/articles\/tokyo-superuser-awards-finalist-godaddy\">GoDaddy<\/a>,\u00a0<a href=\"http:\/\/superuser.openstack.org\/articles\/tokyo-superuser-awards-finalist-lithium-technologies\">Lithium Technologies<\/a>, or<a href=\"http:\/\/superuser.openstack.org\/articles\/tokyo-superuser-awards-finalist-ntt-group\">\u00a0NTT<\/a>.<\/li>\n<li class=\"lead\">The winner will be announced at the Tokyo Summit. (<a href=\"https:\/\/www.surveymonkey.com\/r\/SuperuserAwards\">Vote here<\/a>)<\/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\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-announce\/2015-October\/000683.html\">[openstack-announce] [OSSA 2015-021] Nova network security group changes are not applied to running instances (CVE-2015-7713)<\/a><\/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\u00a0Belmiro Moreira:\u00a0<a href=\"http:\/\/openstack-in-production.blogspot.com\/2015\/10\/scheduling-and-disabling-cells.html\">Scheduling and disabling Cells<\/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><\/span><\/h1>\n<h1 class=\"p6\" style=\"text-align: left;\"><\/h1>\n<ul style=\"text-align: left;\">\n<li class=\"p6\"><a href=\"http:\/\/www.meetup.com\/Indian-OpenStack-User-Group\/events\/225039190\/\">Oct 10, 2015\u00a0OpenStack India Meetup, Pune\u00a0Pune, IN<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/Indian-OpenStack-User-Group\/events\/225039190\/\">Oct 12, 2015\u00a0OpenStack Cinder deep dive\u00a0Stockholm, SE<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/Manchester-OpenStack-Meetup\/events\/224421141\/\">Oct 13, 2015\u00a0Pub Gathering\u00a0Manchester, GB<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/OpenStack-New-York-Meetup\/events\/225737696\/\">Oct 14 &#8211; 15, 2015\u00a0Monolithic to Cloud-Native Apps: Lessons Learned by HP\/ Neutron with Akanda<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/Turkey-OpenStack-Meetup\/events\/225916298\/\">Oct 14, 2015\u00a03. Istanbul Meetup: OpenStack&#8217;de Ceph Storage kullanimi\u00a0Istanbul, TR<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/OpenStack-Taiwan-User-Group\/events\/225859043\/\">Oct 14, 2015\u00a0\u6559\u4f60\u73a9\u6771\u4eac~~\u6771\u4eac\u9ad8\u5cf0\u6703\u4ecb\u7d39Taipei, TW<\/a><\/li>\n<li><a href=\"http:\/\/www.meetup.com\/OpenStack-Czech-User-Group-Meetup\/events\/222955596\/\">Oct 15, 2015\u00a0OpenStack Howto part 7 &#8211; Data Processing\u00a0Prague, CZ<\/a><\/li>\n<\/ul>\n<h1 id=\"dev-digest\" style=\"text-align: left;\">What you need to know from the developer&#8217;s list<\/h1>\n<h2 style=\"text-align: left;\"><a href=\"https:\/\/wiki.openstack.org\/wiki\/Successes\" target=\"_blank\">Success Bot Says<\/a><\/h2>\n<ul style=\"text-align: left;\">\n<li>harlowja: The OpenStack Universe [1]<\/li>\n<li>krotscheck: OpenStack CI posted first package to NPM [2]<\/li>\n<li>markvan: OpenStack Chef Cookbook team recently put in place all the pieces to allow for a running a full (devstack like) CI test against all the cookbook projects commits.<\/li>\n<li>Tell us yours via IRC with a message &#8220;#success [insert success]<\/li>\n<\/ul>\n<h2 style=\"text-align: left;\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076000.html\" target=\"_blank\">Proposed Design Summit allocation<\/a><\/h2>\n<ul style=\"text-align: left;\">\n<li>Track layout is on the official schedule [3].<\/li>\n<li>PTLs or liaisons can start pushing up schedule details. The wiki [4] explains how.<\/li>\n<li>Reach out to ttx or thingee on IRC if there are any issues.<\/li>\n<\/ul>\n<h2 style=\"text-align: left;\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076310.html\" target=\"_blank\">Devstack extras.d support going away M-1<\/a><\/h2>\n<ul style=\"text-align: left;\">\n<li>extras.d \u00a0(i.e. devstack plugins) have existed for 10 months.<\/li>\n<li>Projects should prioritize getting to the real plugin architecture.<\/li>\n<li>Sean compiled a list of the top 25 jobs (by volume) that are giving warnings of breaking [5].<\/li>\n<\/ul>\n<h2 style=\"text-align: left;\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076327.html\" target=\"_blank\">Naming N and O Release Now<\/a><\/h2>\n<ul style=\"text-align: left;\">\n<li>Sean Dague suggests since we already have the locations for N and O summits, we should start the name polls now.<\/li>\n<li>Carol Barrett mentions that the current release naming process only allows the release to be named is announced and no sooner than the\u00a0opening of development of the previous release [6].\n<ul>\n<li>Consensus is made to have this changed.<\/li>\n<li>Monty mentions this option was discussed in the past, but it was changed because we wanted to keep a sense of ownership by the people who actually worked on the release.<\/li>\n<\/ul>\n<\/li>\n<li>Sean will propose for the process to be changed to the next group of TC members.<\/li>\n<\/ul>\n<h2 id=\"dev-digest-requests\" style=\"text-align: left;\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076518.html\" target=\"_blank\">Requests + urllib3 + distro packages<\/a><\/h2>\n<ul style=\"text-align: left;\">\n<li>Problems:\n<ul>\n<li>Requests python library has very specific version of urllib3 it works with. So specific that they aren&#8217;t always released.<\/li>\n<li>Linux vendors often unbundle urllib3 from requests and then apply what patches were needed to their urllib3, while not updating their requests package dependencies.<\/li>\n<li>We use urllib3 and requests in some places, but we don&#8217;t mix them up.<\/li>\n<li>If we have a distro-alterted requests + pip installed urllib3, request usually breaks.<\/li>\n<\/ul>\n<\/li>\n<li>Lots of places the last problem can happen; they all\u00a0depend on us having a dependency on requests that is compatible with\u00a0the version installed by the distro, but a urllib3 dependency that\u00a0triggers an upgrade of just urllib3. When constraints are in use, the\u00a0requests version has to match the distro requests version exactly, but\u00a0that will happen from time to time. Examples include:\n<ul>\n<li>DVSM test jobs where the base image already has python-requests installed.<\/li>\n<li>Virtualenvs where the system-site-packages are enabled.<\/li>\n<\/ul>\n<\/li>\n<li>Solutions:\n<ul>\n<li>Make sure none of our testing environments include distro requests packages.\n<ul>\n<li>Monty notes we&#8217;re working hard to make this happen.<\/li>\n<\/ul>\n<\/li>\n<li>Make our requirements be tightly matched to what requests needed to deal with unbundling.\n<ul>\n<li>In progress by Matt Riedemann [7].<\/li>\n<\/ul>\n<\/li>\n<li>Teach pip how to identify and avoid this situation by always upgrading requests.<\/li>\n<li>Get the distros to stop un-vendoring urllib3.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2 id=\"dev-digest-scheduler\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076373.html\">Scheduler Proposal<\/a><\/h2>\n<ul>\n<li>Ed Leafe several months ago proposed an experiment [8], to see if switching the data model for the Nova scheduler to use Cassandra as the backend would be a significant improvement.\n<ul>\n<li>Due to the undertakings for Nova in Liberty, it was agreed this shouldn&#8217;t be focused on at the time, but the proposal could still be made.<\/li>\n<li>Ed finished writing up the proposal [9].<\/li>\n<\/ul>\n<\/li>\n<li>Chris Friesen mentions some points that might need further discussion:\n<ul>\n<li>Some resources (RAM) only require tracking amounts. Others resources (CPUs, PCI devices) require tracking allocation of specific host resources.<\/li>\n<li>If all of Nova&#8217;s scheduler and resource tracking was to switch to Cassandra, how do we handle pinned CPUs and PCI devices that are associated with a specific instance in the Nova database?<\/li>\n<li>To avoid races we need to:\n<ul>\n<li>Serialize the entire scheduling operation.<\/li>\n<li>Make the evaluation of filters and claiming of resources a single atomic database transaction.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Zane finds the database to use is irrelevant to the proposal, and really this is about moving the scheduling from a distributed collection python processes with ad-hoc synchronization, into the database.<\/li>\n<li>Maish notes that by adding a new database solution, we are up to three different solutions in OpenStack:\n<ul>\n<li>MySQL<\/li>\n<li>MongoDB<\/li>\n<li>Cassandra<\/li>\n<\/ul>\n<\/li>\n<li>Joshua Harlow provides a solution using a distributed lock manager:\n<ul>\n<li>Compute nodes gather information of vms, memory free, cpu usage, memory used, etc and pushes the information to be saved in a node in said DLM backend.<\/li>\n<li>All schedulers watch for pushed updates and update an in-memory cache of the information of all hypervisors.<\/li>\n<li>Besides the initial read-once on start up, this avoids reading large sets periodically.<\/li>\n<li>This information can also be used to know if a compute node is still running or not. This eliminates the need to do queries and periodic writes to the Nova database.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2 id=\"dev-digest-service-catalog\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076592.html\">Service Catalog: TNG<\/a><\/h2>\n<ul>\n<li>Last cross project meeting had good discussions with the next generation of the Keystone service catalog. Information has been recorded in an etherpad [10].<\/li>\n<li>Sean Dague suggests we need a dedicated workgroup meeting to keep things going.<\/li>\n<li>Monty provides a collection of the existing service catalogs [11].<\/li>\n<li>Adam Young suggests using DNS for the service catalog.\n<ul>\n<li>David Stanek put together an implementation [12].<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p style=\"text-align: left;\">[1] &#8211;\u00a0<a href=\"https:\/\/gist.github.com\/harlowja\/e5838f65edb0d3a9ff8a\">https:\/\/gist.github.com\/harlowja\/e5838f65edb0d3a9ff8a<\/a><\/p>\n<p style=\"text-align: left;\">[2] &#8211;\u00a0<a href=\"https:\/\/www.npmjs.com\/package\/eslint-config-openstac\">https:\/\/www.npmjs.com\/package\/eslint-config-openstac<\/a>k<\/p>\n<p style=\"text-align: left;\">[3] &#8211;\u00a0<a href=\"https:\/\/mitakadesignsummit.sched.org\/\">https:\/\/mitakadesignsummit.sched.org\/<\/a><\/p>\n<p style=\"text-align: left;\">[4] &#8211;\u00a0<a href=\"https:\/\/wiki.openstack.org\/wiki\/Design_Summit\/SchedulingForPTLs\">https:\/\/wiki.openstack.org\/wiki\/Design_Summit\/SchedulingForPTLs<\/a><\/p>\n<p style=\"text-align: left;\">[5] &#8211;\u00a0<a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076559.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-October\/076559.html<\/a><\/p>\n<p style=\"text-align: left;\">[6] &#8211;\u00a0<a href=\"http:\/\/governance.openstack.org\/reference\/release-naming.html\">http:\/\/governance.openstack.org\/reference\/release-naming.html<\/a><\/p>\n<p style=\"text-align: left;\">[7] &#8211;\u00a0<a href=\"https:\/\/review.openstack.org\/#\/c\/213310\/\">https:\/\/review.openstack.org\/#\/c\/213310\/<\/a><\/p>\n<p style=\"text-align: left;\">[8] &#8211;\u00a0<a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-July\/069593.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-July\/069593.html<\/a><\/p>\n<p style=\"text-align: left;\">[9] &#8211;\u00a0<a href=\"http:\/\/blog.leafe.com\/reimagining_scheduler\/\">http:\/\/blog.leafe.com\/reimagining_scheduler\/<\/a><\/p>\n<p style=\"text-align: left;\">[10] &#8211;\u00a0<a href=\"https:\/\/etherpad.openstack.org\/p\/mitaka-service-catalog\">https:\/\/etherpad.openstack.org\/p\/mitaka-service-catalog<\/a><\/p>\n<p style=\"text-align: left;\">[11] &#8211;\u00a0<a href=\"https:\/\/wiki.openstack.org\/wiki\/API_Working_Group\/Current_Design\/Service_Catalog\">https:\/\/wiki.openstack.org\/wiki\/API_Working_Group\/Current_Design\/Service_Catalog<\/a><\/p>\n<p style=\"text-align: left;\">[12] &#8211;\u00a0<a href=\"https:\/\/gist.github.com\/dstanek\/093f851fdea8ebfd893d\">https:\/\/gist.github.com\/dstanek\/093f851fdea8ebfd893d<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>What you need to know about Astara Henrik Rosendahl, CEO of Akanda, introduces OpenStack&#8217;s newest project, an open-source network orchestration platform built by OpenStack operators\u00a0for OpenStack clouds. An OpenStack security primer Meet the troubleshooters and firefighters of the OpenStack Security project and how you can get involved. The Road to Tokyo The OpenStack Summit Tokyo&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-weekly-community-newsletter-oct-3-oct-9\/\" class=\"more-link\" title=\"Read OpenStack Weekly Community Newsletter (Oct. 3 \u2013 Oct. 9)\">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":[13],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7351"}],"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=7351"}],"version-history":[{"count":25,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7351\/revisions"}],"predecessor-version":[{"id":7390,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7351\/revisions\/7390"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=7351"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=7351"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=7351"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}