OpenStack Foundation Staffing News

The OpenStack community continues to grow, and the OpenStack Foundation has been hiring to help support many exciting new initiatives and activities as we drive cloud innovation, adoption, and interoperability. New hires in 2015 include:
  • Wes Wilson, Lead Designer, joined late January and has been working on Todd Morey’s team to help build out OpenStack.org and manage other design initiatives. You can check out his awesome work in the /enterprise and /summit sections of OpenStack.org.
  • Danny Carreno, Ecosystem Account Manager, joined Heidi Bretz’s business development team in May and is helping support our growing ecosystem. Danny is passionate about helping startups succeed, coming from his previous role where he helped build startup programs and community for Rackspace public cloud.
  • Heidi Joy Tretheway joined the team in July as Sr Manager of Marketing with a focus on branding, content campaigns and growing participation in the marketing community. She looks forward to collaborating with marketing members at companies throughout our ecosystem. She previously led marketing communications at mobile software company Urban Airship.
  • Kendall Waters recently graduated from St. Edwards University and was a part-time intern for the Foundation during the first half of 2015. She joined the team full time as a Marketing Associate in June, and is part of Claire Massey’s team focused on Summit organization and execution.
  • Jay Fankhauser, currently at Baylor University, is our newest marketing intern, and is primarily helping Allison Price with Superuser Magazine and social media / web analytics.

The bus is filling up, but we still have a few seats left! Come join us!

You can learn more about the full team at http://openstack.org/staff. And we’re still hiring! 

With Stefano Maffulli’s departure in June, the Foundation continues to seek a number of positions, including:
  • Ecosystem Manager: focused on driving the Marketplace forward and liaising with industry groups
  • Upstream Developer Advocate: coordinating and communicating upstream development activities
  • App Dev Community Coordinator: liaise with SDK and developer communities, help solicit feedback and engagement from dev community
  • Engagement Community Manager: support new companies who want to contribute, professional cert, university programs, upstream training, user groups

OpenStack Community Weekly Newsletter (July 17 – 24)

OpenStack and cloud native applications: two peas in a data center pod

OpenStack has shown the world that innovation with open technology can happen. Fast. In fact, it can happen at a pace never before seen in the history of the IT industry.

Interoperability: DefCore, Refstack and You

The OpenStack Foundation has created a set of requirements to ensure that the various products and services bearing the OpenStack marks achieve a high level of interoperability. This post from IBM OpenTech Team gives an overview of the whole machinery, how to test clouds and upload results to RefStack website.

 

IMPORTANT + TIME SENSITIVE:

The Road to Tokyo

Reports from Previous Events

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

  • None this week

Tips ‘n Tricks

Upcoming Events

Other News

OpenStack Reactions

When I hit send after writing my long email for the TC candidacy

When I hit send after writing my long email for the TC candidacy

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis.

OpenStack Community Weekly Newsletter (July 10 – 17)

What you need to know about Google joining OpenStack

In the search for the next big thing, Google has joined the OpenStack Foundation. The Mountain View, California-based colossus announced July 16 that it has become a corporate sponsor of the Foundation.

OpenStack pins down next release name: Mitaka

OpenStack’s next release will be called Mitaka (三鷹). It’s named after the town located in the Tokyo metro area, known for Inokashira park (pictured above) and the Ghibli museum, which showcases the work of the animation studio of the same name.

The Road to Tokyo

Reports from Previous Events

  • None this week

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

  • None this week

Tips ‘n Tricks

Upcoming Events

Celebrating 5 Years of OpenStack at OSCON on Wednesday, July 22nd: RSVP

Other News

OpenStack Reactions

When I stand corrected on an OpenStack mailing list

When I stand corrected on an OpenStack mailing list

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Google bringing container expertise to OpenStack

Google runs one of the world’s largest and most sophisticated automated infrastructures, pioneering new paradigms in cloud computing with containers (launching 2 billion a week), while sharing their work in the open with innovative open source projects like Kubernetes.  

That’s why I’m so excited to announce that Google is sponsoring the OpenStack Foundation, underscoring its commitment to open source and open cloud technologies.

Few companies understand cloud-native apps at scale like Google, so I expect big things as Google developers contribute to OpenStack projects like Magnum. Openstack’s Magnum project directly integrates with Kubernetes, the open source project Google introduced in June, 2014, enabling new cloud native apps to run alongside traditional enterprise workloads on a single platform. The community has also created an easy way to deploy Kubernetes on OpenStack via the Murano project and the new Community App Catalog.

I just spoke with a large enterprise user of OpenStack this week who described OpenStack as their “path to production” for containers. The value proposition for them is that OpenStack can provide a single control plane across all of their infrastructure, which will include VMware, KVM and containerized workloads. OpenStack gives them a solid platform to explore new and compelling technologies as they emerge, and I know they’ll be even more confident in that path knowing that Google has joined our mission to make OpenStack the platform for containerized workloads.

Having a company with Google’s cloud-native chops backing OpenStack is huge, and we can’t wait to see what the future of open collaboration brings to cloud computing!

Be sure to read Craig Mcluckie’s thoughts on today’s announcement on the Google Cloud Platform blog.

Mark Collier

COO, OpenStack Foundation

@sparkycollier

Technical Committee Highlights July 10, 2015

Cross-project catch-all

We merged a couple of cross-project specifications after adequate discussion and time to review. We now are enabling Python 3 for application integration tests and have changed the requirements management design, please click through to specs.openstack.org and read the details on each.

There’s a lot of discussion about a possible Stackforge retirement in order to alleviate the project github organization renaming work that happens when a project moves from the Stackforge org to the OpenStack org. We are discussing and debating the use cases for Stackforge as a provided CI workflow. So far we have observed four categories of Stackforge projects:

  • OpenStack projects using stackforge to incubate until ready
  • Projects that just wanted a place to live and don’t have enough energy to propose it to TC
  • Projects that are in the OpenStack world that expressly did not want to be under the TC’s oversight (Akanda, StackTach)
  • Dead projects

We are hoping to come up with a solution where we can still provide service to all the projects that need it, but reduce the burden on developers and system administrators involved in renaming projects. We would appreciate hearing input on those use cases and if there are any additional use cases for Stackforge, please comment on the review.

We need more cross-project chairs especially in this month, see https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Chair_rotation to sign up and talk to Thierry Carrez for how-to run one, he’s happy to provide expectations and training through email.

Healthy debate about starter kits

The last two weeks we have discussed the exact projects to get the starter-kit tag. In a series of reviews we are still debating and discussing the inclusion or exclusion of the OpenStack Networking project neutron as well as OpenStack Block Storage, project cinder.

For some background and history on networking, the nova team has in the past tried to deprecate nova-network, but hasn’t accomplished that deprecation in a few years. When creating an API, the neutron team didn’t keep a compatible set of calls with the nova API (such as how cinder implemented a v1 Volume API that was identical to the original Compute API calls). There is an upgrade path from nova-network to neutron but it is not seamless. In some configurations, since there aren’t exact analogs for the backends, it is possible now for a deployment to stay on nova-network rather than deploying neutron. However the new Networking Guide has a scenario with provider networks and Linux Bridge that is a nice starting point for many deployments. One suggestion is to add that scenario to the Install Guides to help document the starting point. So, we continue to work on the various reviews to apply those tags.

Projects in application process

Compass as a project was discussed in this week’s TC meeting. One question arises since it is a generic deployment framework and not limited to OpenStack, does it need to become an OpenStack project. There’s also an API resource name possibly causing confusion concern, and then we’ve also asked the team to be more open in meetings and communications.

Another project still in the review queue for the TC is the RPM and packaging team or teams. We are awaiting refreshed specification, more progress in discussion and meetings, a PTL (or two?) and scope definition so that we can review again. Questions such as “is this two teams or one for packaging?” still exist.

M naming quest continues

The first three names in the poll have been eliminated due to either trademark difficulty or cultural respect concerns. Stay tuned to the openstack-dev mailing list to find out the M name. We will be specific about geography in release names in the future and continue to work on the open naming processes.

Tags:

OpenStack Community Weekly Newsletter (July 3 – 10)

Seven habits of highly effective OpenStack contributors

If you want to be an awesome OpenStack contributor, there’s a formula for that. So says Adrian Otto, who should know. Otto is a distinguished architect at Rackspace, chairman of the OpenStack containers team, current project team lead (PTL) for Magnum and launched the Solum project back in 2013.

Ops Mid-Cycle Meetup in Palo Alto, Aug 18-19

We finalized the dates and location of the Ops mid-cycle meetup. Due to timing and the size of our growing event, the best option to accommodate 300 people (if needed) will be Crowne Plaza Hotel in Palo Alto, CA, August 18-19, 2015. Register now and join the brainstorming to define the agenda.

The Road to Tokyo

Reports from Previous Events

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

Tips ‘n Tricks

 

Recently Merged Specs

Subject Owner Project
Change release model to independent releases Jim Rollenhagen openstack/ironic-specs
Add service-version-number spec Dan Smith openstack/nova-specs
Cleanup tempest-library spec Ken’ichi Ohmichi openstack/qa-specs
Add simulation mode spec Ekaterina Chernova openstack/murano-specs
Make ilo drivers standalone work without swift Nisha Agarwal openstack/ironic-specs
Add spec for migrating service client to lib Ghanshyam Mann openstack/qa-specs
Database connection switching for cells melanie witt openstack/nova-specs
Add get_attr form to return all attributes Peter Razumovsky openstack/heat-specs
Add root-disable api Duk Loi openstack/trove-specs
Add REJECT into action rule of FWaaS. Toshiaki Higuchi openstack/neutron-specs
Support Keystone v3 API in openstack puppet modules Richard Megginson openstack/puppet-openstack-specs
Updated attributes in blueprint to match the code Madhusudhan Kandadai openstack/neutron-specs
Properly capitalize OpenStack Andreas Jaeger openstack/openstack-chef-specs
Support data driven test plans for role assignment testing henry-nash openstack/keystone-specs
Add a spec for in tree upgrade tests Sirushti Murugesan openstack/heat-specs
Use Templates for Scenario Tests Configuration Luigi Toscano openstack/sahara-specs
Volume migration improvement for Liberty version Vincent Hou openstack/cinder-specs
Setup Security Specs Repo Priti Desai openstack/security-specs
get-me-a-network: Really get a network Kyle Mestery openstack/neutron-specs
Added spec for add-cas Ade Lee openstack/barbican-specs
Spec for sending polled meters to notification agent Chris Dent openstack/ceilometer-specs
Integrate DNS resolution with an external DNS service Carl Baldwin openstack/neutron-specs
Fix diagram representation in rst Alexander Makarov openstack/keystone-specs
API changes for Reseller Raildo Mascena de Sousa Filho openstack/keystone-specs
Add OS::Heat::None resource spec Steven Hardy openstack/heat-specs
Remove name field from fields in dynamic UI Ekaterina Chernova openstack/murano-specs
Add heat template-function-list command Oleksii Chuprykov openstack/heat-specs
Move devstack-external-plugins spec into implemented Matthew Treinish openstack/qa-specs
Support Keystone v3 API in openstack puppet modules Richard Megginson openstack/puppet-openstack-specs
Implement server instance tagging Sergey Nikitin openstack/nova-specs
Keystone Lightweight Tokens (KLWT) Lance Bragstad openstack/keystone-specs
Use underscores instead of dashes as word separators in API resource names Dave McCowan openstack/barbican-specs
console: convert consoles code to use objects framework sahid openstack/nova-specs
Adds Hyper-V vNUMA enable spec Claudiu Belu openstack/nova-specs
Adds Hyper-V vTPM devices spec Claudiu Belu openstack/nova-specs
RPC and versionobject compatibility Thang Pham openstack/cinder-specs
Don’t put subnet pools in a scope by default Carl Baldwin openstack/neutron-specs
New ZeroMQ driver implementation details Oleksii Zamiatin openstack/oslo-specs
Add user-identity-format-flexibility for oslo.log Doug Hellmann openstack/oslo-specs
Enable optional dependencies in OpenStack projects lifeless openstack/oslo-specs
Specification for Adding Kafka Driver Komei Shimamura openstack/oslo-specs
Add flavor tables to API database Vineet Menon openstack/nova-specs
Servicegroup foundational refactoring for Control Plane Vilobh Meshram openstack/nova-specs

Upcoming Events

Celebrating 5 Years of OpenStack at OSCON on Wednesday, July 22nd: RSVP

Other News

OpenStack Reactions

Gnocchi taking care of my notifications

Gnocchi taking care of my notifications

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

OpenStack Community Weekly Newsletter (June 26 – July 3)

Writing Your First OpenStack Application

Ever thought about what it takes to write a scalable cloud application using an OpenStack SDK? Thanks to a small team’s heroic effort, there’s now a guide for that!

Dive into Zuul – Gated commit system

Zuul is software developed by the OpenStack community. It was developed as an efficient gated commit system, allowing projects to merge patches only after they pass a series of tests. It reduces the probability of breaking the master branch, for instance when unit tests or functional tests no longer pass on the tip of master. Fabien Boucher explains how Zuul works and clarifies some concepts through simple examples.

5 years of OpenStack – it’s time to celebrate the community!

OpenStack celebrates its 5th birthday July 19, and we’re celebrating with the entire OpenStack community during July! Cloud interoperability and support for developer productivity have been focuses for the OpenStack project this year, and none of it would be possible without the quickly growing OpenStack community.

The Road to Tokyo

Reports from Previous Events

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

  • None this week

Tips ‘n Tricks

Open Call for Proposals

Recently Merged Specs

Subject Owner Project
Implement server instance tagging Sergey Nikitin openstack/nova-specs
New ZeroMQ driver implementation details Oleksii Zamiatin openstack/oslo-specs
Add user-identity-format-flexibility for oslo.log Doug Hellmann openstack/oslo-specs
Enable optional dependencies in OpenStack projects lifeless openstack/oslo-specs
Specification for Adding Kafka Driver Komei Shimamura openstack/oslo-specs
Add flavor tables to API database Vineet Menon openstack/nova-specs
Servicegroup foundational refactoring for Control Plane Vilobh Meshram openstack/nova-specs
Add working items to consistent-service-method-names Ken’ichi Ohmichi openstack/qa-specs
Cleanup the specs repo Matthew Treinish openstack/qa-specs
Add devstack external plugin spec Chmouel Boudjnah openstack/qa-specs
Graduate fileutils to oslo.utils and oslo.policy Steve Martinelli openstack/oslo-specs
Move email spec to backlog Flavio Percoco openstack/zaqar-specs
Add spec for email notification Fei Long Wang openstack/zaqar-specs
Enable listing of role assignments in a project hierarchy henry-nash openstack/keystone-specs
Configure most important hadoop configs automatically Vitaly Gridnev openstack/sahara-specs
Add scheduling edp jobs in sahara lu huichun openstack/sahara-specs
Persistent transport Victoria Martinez de la Cruz openstack/zaqar-specs
Change QoS API to be consistent Eran Gampel openstack/neutron-specs
Nova API Microversions support in NovaClient Andrey Kurilin openstack/nova-specs
Propose VMware limits, reservation and shares garyk openstack/nova-specs
Spec to Add ‘macvtap’ as vif type to novas libvirt driver. Andreas Scheuring openstack/nova-specs
Add spec for more-gettext-support Peng Wu openstack/oslo-specs
Moving not implemented specs to backlog Flavio Percoco openstack/zaqar-specs
Implement force_detach for safe cleanup Scott DAngelo openstack/cinder-specs
Update to CORS specification. Michael Krotscheck openstack/openstack-specs
Add requirements management specification. lifeless openstack/openstack-specs
Enabling Python 3 for Application Integration Tests Doug Hellmann openstack/openstack-specs
Cleanup and removal of StrictABC requirement Morgan Fainberg openstack/keystone-specs
Fix resource tracking for operations that move instances between hosts Nikola Dipanov openstack/nova-specs
“Get me a network” spec Sean M. Collins openstack/neutron-specs
Add spec for tempest plugin interface Matthew Treinish openstack/qa-specs
mandatory api limits gordon chung openstack/ceilometer-specs
Moved driver interface from backlog to liberty Ajaya Agrawal openstack/keystone-specs
Adopt Oslo Guru Meditation Reports zhangtralon openstack/ceilometer-specs
Spec for DBaaS(Trove) notification consumption Rohit Jaiswal openstack/ceilometer-specs
Declarative snmp metric pollster Lianhao Lu openstack/ceilometer-specs
Add is_domain to tokens for projects acting as a domain henry-nash openstack/keystone-specs
Clean up tenant resources when one is deleted Assaf Muller openstack/neutron-specs
Fixes for generic RAID interface Devananda van der Veen openstack/ironic-specs

Upcoming Events

Celebrating 5 Years of OpenStack at OSCON on Wednesday, July 22nd: RSVP

Other News

OpenStack Reactions

Spawning up a new compute node

Spawning up a new compute node

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Writing Your First OpenStack Application

Ever thought about what it takes to write a scalable cloud application using an OpenStack SDK? Thanks to a small team’s heroic effort, there’s now a guide for that!

Christian Berendt (B1 Systems), Sean Collins (Mirantis), James Dempsey (Catalyst IT) and Tom Fifield gathered in Taipei, with Nick Chase live via video link, to produce “Writing Your First OpenStack Application” in just five days. The sprint was organised by the Application Ecosystem Working Group, with the financial support of the OpenStack Foundation.

The new work is aimed at software developers who want to build applications on OpenStack clouds and also shares some best practices for cloud application development.

Inspired by Django’s first app tutorial, where a simple polling app is used to explore the basics of working with Django, “Writing Your First OpenStack Application” uses an app that generates beautiful fractal images as a teaching tool to run through areas like:

  • Creating and destroying compute resources.
  • Scaling available resources up and down.
  • Using Object and Block storage for file and database persistence.
  • Customizing networking for better performance and segregation.
  • Making cloud-related architecture decisions such as turning functions into micro-services and modularizing them.

The guide has been written with a strong preference for the most common API calls, so it will work across a broad spectrum of OpenStack versions. In addition, the authors have paid special attention that the first few sections should work almost regardless of OpenStack cloud configuration.

A core part of the guide’s design is support for multiple SDKs. The initial version was written and tested with the libcloud SDK, but work is underway for python-openstacksdk, pkgcloud and fog which will re-use the text with new code samples.

So, check out “Writing your First OpenStack Application” for libcloud, watch the introductory presentation from the summit, or consider helping complete the samples for other languages.

 

 

 

Taipei 101 (c) James Dempsey

Taipei 101 (c) James Dempsey

Each post-it note represents an area that had to be written.

Each post-it note represents an area that had to be written.

Enjoying local Taiwanese food after a hard day's writing.

Enjoying local Taiwanese food after a hard day’s writing.

5 years of OpenStack – it’s time to celebrate the community!

OpenStack celebrates its 5th birthday July 19, and we’re celebrating with the entire OpenStack community during July! Cloud interoperability and support for developer productivity have been focuses for the OpenStack project this year, and none of it would be possible without the quickly growing OpenStack community.

There are now more than 80 global user groups and 27,300 community members, across 165 countries, spanning more than 500 organizations. Over 30 million lines of code have been written in less than five years thanks to our thriving community of developers and users around the world. This calls for a big toast to the OpenStack community members and our users.

 

5yearOpenStackBDay

 

We’ve invited all our user groups to celebrate with us. During the month of July, more than 35 OpenStack birthday parties will be thrown all over the world – celebrating the OpenStack community!  We encourage everyone to find a birthday party in your area and join your fellow community members to toast each other on another great year! If you don’t see a celebration in your area, not to worry – several more parties are to be announced soon. Don’t forget to share your pictures and memories using #OpenStack5Bday.

If you’re attending OSCON, the Foundation invites you to come celebrate the OpenStack Community on Tuesday, July 22nd at the LeftBank Annex to mingle with other community members and Foundation staff. Stay tuned – more details coming soon!

Find a local celebration in your area:

Argentina July 15

Atlanta July 18

Austin July 28

Baden-Württemberg July 15

Bangalore, India July 11

Brazil July 25

Bucharest, Romania June 30

China – ShenZhen July 11

Colorado (Denver Metro/South) July 16

Fort Collins, Colorado July 16

Greece July 1

Hong Kong July 14

Hungary July 16

Israel July 13

Italy July 14

Japan July 13

Kenya, Africa July 11

London July 21

Los Angeles July 16

Melbourne, Australia

Moscow, Russia, July 22 

Mumbai, India July 25

New Delhi, India July 11

New York July 15

North Carolina July 23

North Virginia July 7

Paris, France June 30

Philadelphia July 16

Philippines June 29

San Francisco Bay Area July 9

Seattle, July 16 

Sevilla, Spain July 1

Slovenia June 23

South Korea August 5

Stockholm/Nordic July 21

Switzerland July 17

Sydney, Australia July 15

Thailand July 17 & July 18

Tunisia July 22

Turkey July 22

Vancouver, Canada July 16

Vietnam July 4

Virginia July 9

Washington DC Metro Area July 20

OpenStack Community Weekly Newsletter (June 19 – 26)

New OpenStack component versioning

Thierry Carrez explains why the Liberty-1 milestone release has some unfamiliar version numbers for familiar projects.

Technical Committee Highlights June 25, 2015

A compute starter kit tag has been approved, it provides a place for a beginner who only wants to try to get a computing cloud use case started. New projects under the OpenStack “Big Tent”: Searchlight, OS-ansible-deployment (OSAD), Solum and Cue Message Broker service.

Forrester says: ready, set, OpenStack!

A recent report from Forrester gives a major boost to OpenStack adoption, calling its “viability and presence in the market irrefutable.” You can download the entire report for a limited time on the OpenStack.org website.

The Road to Tokyo

Reports from Previous Events

  • None this week

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

Tips ‘n Tricks

Open Call for Proposals

Recently Merged Specs

Subject Owner Project
Clean up tenant resources when one is deleted Assaf Muller openstack/neutron-specs
Fixes for generic RAID interface Devananda van der Veen openstack/ironic-specs
Add spec for reference implementation split Kyle Mestery openstack/neutron-specs
Add Spec Lifecycle Rules to readme Matthew Oliver openstack/swift-specs
Add uuid field to security-groups for server show heijlong openstack/nova-specs
Add spec to enhance PCI passthrough whitelist to support regex Moshe Levi openstack/nova-specs
Moved driver interface from backlog to liberty Ajaya Agrawal openstack/keystone-specs
Update monasca spec with version 5.0.0 Kanagaraj Manickam openstack/heat-specs
Add Zone Exists Event Spec Kiall Mac Innes openstack/designate-specs
VLAN aware VMs Erik Moe openstack/neutron-specs
Allow unaddressed port(without l3 address, subnet) and to boot VM with it Isaku Yamahata openstack/neutron-specs
Uniform Resource Signals Miguel Grinberg openstack/heat-specs
Decompose vendor plugins/drivers for neutron-*aas Doug Wiegley openstack/neutron-specs
Lbaas, use Octavia as reference implementation Doug Wiegley openstack/neutron-specs
MySQL manager refactor Alex Tomic openstack/trove-specs
Add virt-driver CPU thread pinning Stephen Finucane openstack/nova-specs
Implement external physical bridge mapping in linuxbridge Li Ma openstack/neutron-specs
Add port timestamp Zhiyuan Cai openstack/neutron-specs
Add availability_zone support IWAMOTO Toshihiro openstack/neutron-specs
PowerVM Compute Inspector Drew Thorstensen openstack/ceilometer-specs
Add rootwrap-daemon-mode blueprint Yuriy Taraday openstack/nova-specs
Add heat template-version-list command to cmd Oleksii Chuprykov openstack/heat-specs
Add a str_split intrinsic function Steven Hardy openstack/heat-specs
Add spec for more-gettext-support Peng Wu openstack/oslo-specs
trivial: Change file permissions for spec Stephen Finucane openstack/nova-specs
Action listing Tim Hinrichs openstack/congress-specs
libvirt: virtio-net multiqueue Vladik Romanovsky openstack/nova-specs
Spec for adding audit capability using CADF specification. Arun Kant openstack/barbican-specs
libvirt: set admin root password sahid openstack/nova-specs
Report host memory bandwidth as a metric in Nova Sudipta Biswas openstack/nova-specs
Adds Hyper-V Cluster spec Claudiu Belu openstack/nova-specs
Inject NMI to an instance Shiina, Hironori openstack/nova-specs
Add a Distinct Exception for Exceeding Max Retries Ed Leafe openstack/nova-specs
Fix error messages on check-flavor-type Ken’ichi Ohmichi openstack/nova-specs
Add BuildRequest object Andrew Laski openstack/nova-specs
Groups are not included in federated scoped tokens Dolph Mathews openstack/keystone-specs
Add spec for event alarm evaluator Ryota MIBU openstack/ceilometer-specs
nova.network.linux_net refactor Roman Bogorodskiy openstack/nova-specs
user_data modification Alexandre Levine openstack/nova-specs
Add support for Redis replication Peter Stachowski openstack/trove-specs
Adds spec for modeling resources using objects Jay Pipes openstack/nova-specs
Add tooz service group driver Joshua Harlow openstack/nova-specs
Add List of Group-IDs to ACL for Secrets/Containers John Wood openstack/barbican-specs
Specification for spark-jobs-for-cdh-5-3-0 added Alexander openstack/sahara-specs
Scheduler Introduce lightwieght transactional model for HostState Nikola Dipanov openstack/nova-specs
DNS resolution inside of Neutron using Nova instance name Carl Baldwin openstack/neutron-specs
Allow multiple clusters creation simultaneously Telles Mota Vidal Nóbrega openstack/sahara-specs
Update the backlog spec page John Garbutt openstack/nova-specs
Add spec for decoupling auth from API versions to backlog Morgan Fainberg openstack/keystone-specs
Let users restrict stack-update scope Ryan Brown openstack/heat-specs
Update of `support-modify-volume-image-metadata.rst` Dave Chen openstack/cinder-specs
Add ability to abandon environments Dmytro Dovbii openstack/murano-specs
Add the oslo_db enginefacade proposal Matthew Booth openstack/nova-specs
Track cinder capacity notifications XinXiaohui openstack/ceilometer-specs

Upcoming Events

Other News

OpenStack Reactions

Rushing to see if my bug was fixed in the release note

Rushing to see if my bug was fixed in the release note

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.