The content below is taken from the original (OpenStack Weekly Community Newsletter (Oct. 3 – Oct. 9)), to continue reading please visit the site. Remember to respect the Author & Copyright.
What you need to know about Astara
Henrik Rosendahl, CEO of Akanda, introduces OpenStack’s newest project, an open-source network orchestration platform built by OpenStack operators for 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 will sell out! Register NOW!
- The schedule and mobile app for the OpenStack Summit in Tokyo are now available
- If you have already downloaded an OpenStack Summit mobile app before, no need to do it again! Just refresh your existing app.
- OpenStack training sessions available in Tokyo
- Several ecosystem companies are offering training in Tokyo during the week of the Summit. Check out the sessions available and plan your travel accordingly
- The Summit maps are now available online
- Speakers, sponsors, and ATC registration codes deactivate 10/19, so register now!
Community feedback
OpenStack is always interested in feedback and community contributions, if you would like to see a new section in the OpenStack Weekly Community Newsletter or have ideas on how to present content please get in touch: community@openstack.org.
Reports from Previous Events
- None this week
Deadlines and Contributors Notifications
- Liberty Release Oct., 15, 2015
- Outreachy Mentorship Application deadline: Nov., 02, 2015, 07:00 pm UTC
- Call for papers:
- FOSDEM’16 deadline: October 30, 2015
- PyCon 2016 deadline: Jan 3, 2016
- USENIX Annual Technical Conference 2016 deadline: February 1, 2016
Superuser Awards: your vote counts
(voting closes on 10/12 at 11:59 pm PT)
- Vote for one of the four finalists: FICO, GoDaddy, Lithium Technologies, or NTT.
- The winner will be announced at the Tokyo Summit. (Vote here)
Security Advisories and Notices
Tips ‘n Tricks
- By Belmiro Moreira: Scheduling and disabling Cells
Upcoming Events
- Oct 10, 2015 OpenStack India Meetup, Pune Pune, IN
- Oct 12, 2015 OpenStack Cinder deep dive Stockholm, SE
- Oct 13, 2015 Pub Gathering Manchester, GB
- Oct 14 – 15, 2015 Monolithic to Cloud-Native Apps: Lessons Learned by HP/ Neutron with Akanda
- Oct 14, 2015 3. Istanbul Meetup: OpenStack’de Ceph Storage kullanimi Istanbul, TR
- Oct 14, 2015 教你玩東京~~東京高峰會介紹Taipei, TW
- Oct 15, 2015 OpenStack Howto part 7 – Data Processing Prague, CZ
What you need to know from the developer’s list (WIP)
Success Bot Says
- harlowja: The OpenStack Universe [1]
- krotscheck: OpenStack CI posted first package to NPM [2]
- 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.
- proton driver running with Kerberos for encryption and authentication
- Tell us yours via IRC with a message “#success [insert success]
Proposed Design Summit allocation
- Track layout is on the official schedule [3].
- PTLs or liaisons can start pushing up schedule details. The wiki [4] explains how.
- Reach out to ttx or thingee on IRC if there are any issues.
Devstack extras.d support going away M-1
- Sean Dague mentions extras.d is devstack plugins, and has existed for 10 months.
- Projects should prioritize getting to the real plugin architecture.
- Sean compiled a list of the top 25 jobs (by volume) that giving warnings of breaking [5].
Naming N and O Release Now
- Sean Dague suggests since we already have the locations for N and O summits, we should start the name polls now.
- Carol Barrett mentions that the current release naming process only allows the release to be named is announced and no sooner than the opening of development of the previous release [6].
- Consensus is made to have this changed.
- 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.
- Sean will propose this to the next group of TC members.
Requests + urllib3 + distro packages
- Problems:
- Requests python library has very very specific versions of urllib3 it works with. So specific that they aren’t always released.
- Linux vendors often unbundle urllib3 from requests and then apply what patches were needed to their urllib3 while not updating their requests package dependencies.
- We use urllib3 and requests in some places, but don’t mix them up.
- If we have a distro-alterted requests + pip installed urllib3, request usually breaks.
- Lots of places the last problem can happen; they all depend on us having a dependency on requests that is compatible with the version installed by the distro, but a urllib3 dependency that triggers an upgrade of just urllib3. When constraints are in use, the requests version has to match the distro requests version exactly, but that will happen from time to time. Examples include:
- DVSM test jobs where the base image already has python-requests installed.
- Virtualenvs where the system-site-packages are enabled.
- Solutions:
- Make sure none of our testing environments include distro requests packages.
- Monty notes we’re working hard to make this happen.
- Make our requirements be tightly matched to what requests needed to deal with unbundling.
- In progress by Matt Riedemann [7].
- Teach pip how to identify and avoid this situation by always upgrading requests.
- Get the distros to stop un-vendoring urllib3.
- Make sure none of our testing environments include distro requests packages.
[1] – http://bit.ly/1OpNcOu
[2] – http://bit.ly/1VJsrMM
[3] – http://bit.ly/1VJsubb
[4] – http://bit.ly/1VJsrMN
[5] – http://bit.ly/1OpNepG
[6] – http://bit.ly/1Se8FXO
[7] – http://bit.ly/1VJsubc