Superuser TV <http://superuser.openstack.org/articles/section/superuser-tv>
Introduced at the Tokyo Summit, Superuser TV offers community and industry
insights, plus educational topics to support the OpenStack community. With
content ranging from deployments to diversity, from emerging technologies to
cloud strategy, Superuser TV is aiming to provide the community with access to
a variety of perspectives and knowledge
October 2015 user survey highlights increasing maturity of OpenStack
deployments
<http://superuser.openstack.org/articles/october-2015-user-survey-highlights-increasing-maturity-of-openstack-deployments>
60 percent of deployments in production and high rates of adoption of
OpenStack’s core services are key findings from the report released by the User
Committee. The full report can be downloaded here: openstack.org/user-survey
<https://www.openstack.org/surveys/landing?BackURL=%2Fsurveys%2Fcurrent>
Eliminating “Not-Invented-Here” Syndrome
<http://superuser.openstack.org/articles/eliminating-not-invented-here-syndrome>
Why embracing this notion is the key to unlock an open data center
infrastructure, according to Boris Renski, the co-founder and CMO of Mirantis.
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:
[email protected] <mailto:[email protected]>.
Reports from Previous Events
OpenStack Summit Tokyo – Final Summary
<http://redhatstackblog.redhat.com/2015/11/05/openstack-summit-tokyo-final-summary/>
Why OpenStack Neutron just grabbed center stage
<http://superuser.openstack.org/articles/why-openstack-neutron-just-grabbed-center-stage>
Finding your way around OpenStack: professional certification and the project
navigator
<http://superuser.openstack.org/articles/finding-your-way-around-openstack-professional-certification-and-the-project-navigator>
Your OpenStack questions answered, a block storage battle and mobile eats the
world
<http://superuser.openstack.org/articles/your-openstack-questions-answered-a-block-storage-battle-and-mobile-eats-the-world>
Domo arigato Japan!
<https://www.blueboxcloud.com/insight/blog-article/domo-arigato-japan>
Deadlines and Contributors Notifications
Call for papers:
OSCON <http://conferences.oreilly.com/oscon/open-source/public/cfp/423> 2016
deadline: November 24, 2015
Continuous Lifecycle London
<http://continuouslifecycle.london/call-for-papers/> Deadline: December 1, 2015
PyCon 2016 <https://us.pycon.org/2016/speaking/> deadline: Jan 3, 2016
USENIX Annual Technical Conference 2016
<https://www.usenix.org/conference/atc16/call-for-papers> deadline: February 1,
2016
Security Advisories and Notices
None this week
Tips ‘n Tricks
By Russell Bryant <https://twitter.com/russellbryant>: Open Virtual Network
tutorial <http://superuser.openstack.org/articles/open-virtual-network-tutorial>
By Gal Sagie: What you need to know about Dragonflow for the OpenStack Liberty
release
<http://superuser.openstack.org/articles/what-you-need-to-know-about-dragonflow-for-the-openstack-liberty-release>
Upcoming Events <https://www.openstack.org/community/events>
Nov 07, 2015 OSATH – FOSSCOMM 2015 Aigaleo, GR
<http://www.meetup.com/Athens-OpenStack-User-Group/events/226479917/>
Nov 11, 2015 whereis instance_ha + OpenStack Tokyo Summit Recap
<http://www.meetup.com/Australian-OpenStack-User-Group/events/220202353/>
Nov 12, 2015 8. Meetup, Konu: OpenStack Plugin Development 101 Ankara, TR
<http://www.meetup.com/Turkey-OpenStack-Meetup/events/225419513/>
What you need to know from the developer’s list
Success Bot Says <https://wiki.openstack.org/wiki/Successes>
calebb: Shade now supports volume snapshots
pleia2: Launched code search [1].
sdague: grenade-multinode live upgrade tests now running on nova non voting
AJaeger: Contributors guide is published [2].
Tell us yours via IRC with a message “#success [insert success]”
Upgrading Elastic Search Cluster Monday
<http://lists.openstack.org/pipermail/openstack-dev/2015-November/078314.html>
November 9th 1700UTC
Requires a cluster restart, in which people won’t be able to do searches during
that time.
New features from upgrade:
Aggregations
Rolling upgrades within a major release
Should improve performance
Release Team Communication Changes
<http://lists.openstack.org/pipermail/openstack-dev/2015-November/078277.html>
IRC channel change from #openstack-relmgr-office to #openstack-release
“Office hours” are being dropped.
Just drop by the channel or on the dev list with subject containing “[release]”
anytime you need something.
Deprecation for Untagged Code
<http://lists.openstack.org/pipermail/openstack-dev/2015-November/078336.html>
Ironic tries to keep master backwards compatible. There are deployers doing
continuous deployments of Ironic off of master.
Based on the deprecation tag policy [3], it only covers released and tagged
code, but not unreleased code or features introduced in an intermediate release.
A proposal [4] by Jim:
Three month deprecation period is needed for features that were never released.
A feature that was introduced in a intermediate release needs to be deprecated
in the next intermediate release or coordinated release, and supported until
the next release and 3 months.
Outcome of Distributed Lock Manager Discussion @ the Summit
<http://lists.openstack.org/pipermail/openstack-dev/2015-November/078214.html>
There was a two part session at the summit [5]
Previously, there was an unwritten policy that DLMs should be optional, which
led to writing poor DLM-like things backed by databases.
Continuing our existing pattern of usage like databases and message-queues,
we’ll use an oslo abstraction layer: tooz [6].
Current OpenStack project requirements that surfaced in discussion for DLMs,
it’s likely that Consul, Etcd and Zoo Keeper will be fine to use via Tooz. No
project required a fair locking implementation in the DLM.
We want to avoid the situation of unmaintained drivers. We adopted a similar
requirement from oslo.messaging driver requirements [7]:
Two developers responsible for it
Gating functional tests that use dsvm
Test drivers in-tree need to be clearly referenced as a test driver in the
module name.
Davanum brings in Devstack ZooKeeper support [8].
An etcd driver is in review for Tooz [9].
A Consul driver in Tooz is also planned [10].
Concerns raised about the default DLM driver being ZooKeeper:
It’s a new platform for operators to understand
We don’t know how well ZooKeeper will work with openjvm as oppose to Oracle’s
JVM.
Troubleshooting Cross-Project Communication
<http://lists.openstack.org/pipermail/openstack-dev/2015-November/078138.html>
Evolve the current cross-project meeting to an “as needed” rotation, held at
any time on Tuesdays or Wednesdays.
Based on feedback [11] it’s difficult to have meetings at different times on
Tuesday and Wednesdays.
There was consensus that the meeting can be “as needed” on Tuesday, and that
most announcements will happen in the mailing list, and sometimes show up in
this weekly Dev List Summary.
API For Getting Only Status of Resources
<http://lists.openstack.org/pipermail/openstack-dev/2015-November/078318.html>
Projects like Heat,Tempest, Rally, and other projects that work with resources
are polling for updates on asynchronous operations.
Boris proposes having API’s expose the ability to just get the status by UUID,
instead of fetching all data on a resource.
Clint suggests instead of optimizing for polling, we should revisit the
proposal for a pub/sub model, so users can subscribe to updates for resources.
Sean suggests near term work around is to actually use Searchlight, which today
monitors the notification bus for Nova.
Searchlight is hitting the Nova API more than ideal, but at least it’s one
service.
Longer term we need a dedicated event service in OpenStack. Everyone wants web
sockets, but anticipating 10,000+ open web sockets, this isn’t just a bit of
python code, but a highly optimized server underneath.
[1] – http://codesearch.openstack.org/ <http://codesearch.openstack.org/>
[2] – http://docs.openstack.org/contributor-guide
<http://docs.openstack.org/contributor-guide>
[3] – https://review.openstack.org/#/c/242117/1
<https://review.openstack.org/#/c/242117/1>
[4] – https://review.openstack.org/#/c/242117/1
<https://review.openstack.org/#/c/242117/1>
[5] – https://etherpad.openstack.org/p/mitaka-cross-project-dlm
<https://etherpad.openstack.org/p/mitaka-cross-project-dlm>
[6] – https://pypi.python.org/pypi/tooz <https://pypi.python.org/pypi/tooz>
[7] – https://review.openstack.org/#/c/240645/
<https://review.openstack.org/#/c/240645/>
[8] – https://review.openstack.org/#/c/241040/
<https://review.openstack.org/#/c/241040/>
[9] – https://review.openstack.org/#/c/151463/
<https://review.openstack.org/#/c/151463/>
[10] – https://blueprints.launchpad.net/python-tooz/+spec/add-consul-driver
<https://blueprints.launchpad.net/python-tooz/+spec/add-consul-driver>
[11] –
http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-11-03-21.01.log.html
<http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-11-03-21.01.log.html>
_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
