Technical Committee Highlights June 5, 2015

Welcome to this week’s highlights from the Technical Committee. Just like every other week, this has been quite a busy one for the community and the efforts to enhance our governance model keep moving forward.

The tc-approved-release tag has been approved

The tc-approved-release tag was mentioned in the last edition of these highlights. The discussions has moved a step forward and the first, basic, version of this tag has been approved. You can read the full version here. Initially, all projects that have the tag-integrated-release tag also get the tc-approved-release tag.

Compute kernel tag

A good part of the last meeting – from 20:07 to 20:38 – was spent discussing this tag and we’ll do the same in this post. Lets start by describing what this tag is trying to achieve.

The tag aims to define the minimum set of required projects to have a running OpenStack Compute deployment. The motivation behind this tag comes from the Kilo mid-cycle OPs meetup where some of the participants suggested that this is something the community should dictate. Although there’s no disagreement on how important and valuable this information is for the community, there seem to be different opinions about who should provide this information and how it should be provided. This means there are 2 questions that need to be answered in order to reach consensus on this matter:

Should the TC have an opinion on start here for this use case today?
If yes, How should this opinion be expressed/represented?

There were 2 versions of question number one. The previous version didn’t include the use case bit, which turned out being a deal breaker for several members of the technical committee. The use case clause indicates that the TC could express an opinion on starting points for different scenarios, such as compute, object-storage, or bare metal, instead of providing a single starting point for a specific use case. Some of the current opinions are:

The information provided by this tag has nothing to do with the governance
The TC should know how to answer questions like: “What’s the minimum required set to get OpenStack running?” If the TC can’t, who else is going to do it?
The TC could have an opinion on different starting points but it should not dictate a one-and-only entry point.

The TC voted on the first question and the results were in favor for the TC having an opinion on this matter. Question number 2, however, remains open and it’ll likely be discussed in future meetings. If you have an opinion on how these starting points should be communicated, please do provide them on this review.

i18n is now an OpenStack Project Team

The group behind i18n has taken a step forward in their organization and they are now an OpenStack Project Team. The TC and the community are excited to have an official i18n team. Their mission is “To make OpenStack ubiquitously accessible to people of all language backgrounds” and we fully support them.

Consideration of the Packaging team proposal

The TC also discussed a proposal adding distribution packaging to OpenStack. We decided that the packaging team proposal should be set to Work In Progress until the plan is more fully described with infrastructure considerations. There’s a lot of activity on the mailing list so please join in if you’re interested in the outcome.

Potential release cycle overhaul

Please take a look at the mailing list discussions for changing the release cycles for certain projects such as Ironic.

In closing, for a bit of fun take a look at the M names proposed for the next release cycle including Japanese characters inline. We’re looking forward to the vote.

OpenStack Community Weekly Newsletter (May 29 – June 5)

Containers and OpenStack: here’s what you need to know

Interview with Adrian Otto, a principal architect at Rackspace, is the project technical lead (PTL) for Magnum, an API service developed by the OpenStack containers team for OpenStack to make container management tools such as Docker and Kubernetes available as first-class resources in OpenStack. Magnum officially joined the OpenStack project list upon approval by a unanimous vote by the Technical Committee in March 2015.

What building Legos can teach you about open source

If you want to build a gas station next to a children’s playground, fireworks are pretty much guaranteed. That not-in-my-neighborhood face-off was one of the issues hashed out in a recent OpenStack Upstream Training session where about 50 participants split into teams building Lego sets.

Travel grants bring global community members to OpenStack Summit

Turns out there’s nothing like working together in person to push a cloud project forward. To help make that valuable face time happen, the OpenStack Foundation funded the travel and hotel accommodations for 21 men and 7 women who are key contributors to attend the OpenStack Summit Vancouver.

Neutron RFE Process

Starting with the development of the Juno release, the Neutron project moved to using a specs repository similar to how other projects were using them. Kyle Mestery, Neutron’s PTL, reflects on the fact that the process at best, lengthened the pipeline we had in place to gate the incoming feature fire-hose. At worst, it turned off potential committers. Neutron’s team is implementing a new process meant to allow users to express their desires for new features using Launchpad.

More Post-Vancouver Summaries

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

  • None

Tips ‘n Tricks

Open Call for Proposals

Recently Merged Specs

Subject Owner Project
fix wrong title for OS-INHERIT Extension spec Guojian Shao openstack/keystone-specs
Introduce flavor framework for services mark mcclain openstack/neutron-specs
Use os-brick library Walter A. Boring IV (hemna) openstack/nova-specs
Federated domain identified by “id“ not “name“ Marek Denis openstack/keystone-specs
Removing JobExecutionArgument Table Ethan Gafford openstack/sahara-specs
Spec for pre-signed URLs Flavio Percoco openstack/zaqar-specs
Add support for missing features in zaqarclient v1.1 Doraly Navarro openstack/zaqar-specs
Tests refactoring spec Thomas Herve openstack/zaqar-specs
Remove Liberty Placeholder Kiall Mac Innes openstack/designate-specs
Add a backlog folder Flavio Percoco openstack/zaqar-specs
Fix references syntax for correct conversion into html Oleksii Zamiatin openstack/oslo-specs
MongoDB database management commands Matthew Van Dijk openstack/trove-specs
Configuration Groups for Cassandra Petr Malik openstack/trove-specs
Add backup and restore to the Redis datastore Peter Stachowski openstack/trove-specs
Update Ironic spec URL refs to specs.openstack.org Naohiro Tamura openstack/ironic-specs
Spec for graduating reports Davanum Srinivas (dims) openstack/oslo-specs
Neutron QoS API Extension Sean M. Collins openstack/neutron-specs
Explain how to adopt a backlog spec Joe Gordon openstack/nova-specs
Add new boot interface in Ironic Ramakrishnan G openstack/ironic-specs
Add spec approval rules to readme Michael Still openstack/nova-specs
Property Group Kanagaraj Manickam openstack/heat-specs
Drop incubating theme from docs Joe Gordon openstack/barbican-specs
Add open-iscsi transport support to brick Anish Bhatt openstack/cinder-specs
Adopt oslo guru meditation report to cinder wanghao openstack/cinder-specs
Backup and Restore for Cassandra Petr Malik openstack/trove-specs

 

Upcoming Events

Other News

OpenStack Reactions

Unexpected hiccup before the release

Unexpected hiccup before the release

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 (May 8 – 29)

OpenStack users share how their deployments stack up

Some of OpenStack’s founding projects — including Nova, Keystone, Glance, Horizon and Cinder — continue to be the most popular. That may be changing, however. For starters, the inclusion of bare-metal provisioning project Ironic in the integrated release led to an increase across all deployment stages, including production, test and running a proof-of-concept (POC). Other projects, including Heat, Ceilometer, Swift and Trove, are also gaining in adoption, according to the recent User Survey.

OpenStack application developers share insights

Application developers working with OpenStack know what they want. Most are looking for clear, accurate documentation with emphasis on detailed working examples so they can get their jobs done. That’s one of key takeaways from the fifth consecutive survey conducted by the User Committee.

How to get more women involved in tech? Communication, leadership and mentors

Whether the women considering the problem were developers, engineers or marketers, they all pinpointed that communication, leadership and mentorship were fundamental to getting more women involved.

Think FICO is a credit scoring company? Nope: it’s about large-scale analytics

Americans have been counting on FICO to measure their credit worthiness since the 1980s, but the San Jose, California-based company has much a farther reach.

Post-Vancouver Summaries

Relevant Conversations

Deadlines and Development Priorities

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

OpenStack Reactions

Life of an OpenStack contributor in Animated GIF the summit session (Vancouver 2015) will make you laugh out loud

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.

Technical Committee Highlights May 29, 2015

Welcome back from the summit. A huge part of OpenStack’s community gathered together in Vancouver for a week full of brainstorms, problem solving and planning for the next 6 months. So did the Technical Committee and here are the highlights of last week and this week’s meeting.

Design Summit

 

Joint Board and TC meeting

We held a joint Board and TC meeting Sunday afternoon. The DefCore definition has been updated and it now includes the Kilo release, YAY! With the changes, interoperability testing includes:

  • Auth operations within the Identity API; however identity management operations will not be considered designated sections because they are controlled by policies.
  • Management operations for floating IPs through the Compute API.

The testing means that we have concrete evidence of interoperability for OpenStack clouds.

As a community, we have to make a decision about nova-network or neutron API calls and compatibility for interop in the coming six months. Lots of great discussion happened at the Summit, and one way forward is through documenting how to keep floating IP call compatibility by showing how to use ports in the Neutron API to be equivalent to elastic floating IP lists. Stay tuned as we write up more details in a doc near you.

Diversity working group approved to go and set up a mission. This is uncharted territory but we want to chart it as other cloud organizations and open source groups look to us to pave the way.

Tags, tagging, tagification

As part of completing the list of base tags for OpenStack, the TC often has to discuss whether some of them make sense or not. The tags currently under discussion are: tc-approved release and kernel:compute.

Tag (rather confusingly) named tc-approved-release
This tag mostly exists to suffice one of the requirements imposed by the Foundation bylaws. It serves to indicate that the Technical Committee has included a project in the “OpenStack TC Approved Release”, which indicates projects that are suitable to be included in the “Trademark Designated OpenStack Software”. Although the name might be confusing and not sexy, it serves the sole purpose of sufficing the bylaws requirements.Check the proposed change for more info.
Tags named kernel:compute (exciting?) or use-case:basic-compute (boring?)
This tag is meant to indicate the set of services that are required to have a minimum compute deployment. We’re having long discussions around this tag with community members and each other on the TC. The discussions go from whether it is useful at all, what the scopes and limits of this tag are and whether it sends the right message or not. You can follow some of these discussions on the review itself.

Cross-project sessions

The Technical Committee whittled down the list of proposed cross-project sessions to 14 sessions, and we want to report back on these sessions.

The single network stack session has a part two as well, where the discussion came up with the priority to test Linux Bridge on DevStack as well as document the port reuse example that gives more compatible floating IP features. Floating IP quotas will not apply to this situation so people will be able to burn as many public IPs as their port quota allows, but it seems like this documentation is sorely missed right now.

Stable releases have been available with a tag, such as 2015.1, since the project’s inception. But at a cross project session we decided that the current tagged releases are not more stable or tested than any other, and the stable branches are actually the ones we would like deployers to use as reference. We are dedicated to stability and trust of those branches. Please read more and reply on http://lists.openstack.org/pipermail/openstack-dev/2015-May/065144.html with any questions.

We had good forward progress on the service catalog and CORS support in OpenStack. The wiki page has all the Etherpads from sessions if you want to deep dive on those sessions.

Latest news from last TC meeting

We voted to give Scott Moser, maintainer of Cirros, Active Technical Contributor (ATC) status for his work on the lightweight image and operating system we use consistently for launching and testing VMs.

The chef project was proposed as an OpenStack project and the TC voted it in. We still want to see evidence of being an OpenStack project, but moving their open design discussions to the OpenStack-dev mailing list is the right step.

We also passed a resolution to use UTC always. Now, some of us felt this was heavy-handed, but once we learned of the risk of having to restart an election (or a candidate missing a deadline due to confusion on the time or date of election deadlines), we agreed to pass it as a resolution.

Also we have a process for gathering potential release names that start with M and are near the summit location. Monty Taylor is the name coordinator, so look for the list of potential names on Monday, June 1. The next release is less than five months away, October 15, 2015.

A subteam from the TC is working on the OpenStack Project Team Guide June 18-19 in a remote work session and all are welcome to help.

The TC is also looking to provide deep-dive into troublesome issues with teams and help with resolutions. We’re also looking into starting a basic design tenants team as well as cross-project team to improve activity around cross-project specs and the cross-project meeting.

Tags:

Deadline For New Cinder Volume Drivers in Liberty

[Guest post from Mike Perez, Cinder Project Team Lead]

The Cinder team has met this week to begin discussions on the deadline for new volume drivers in the Liberty release. The proposed deadline for volume drivers to be merged by is June 19th 2015. However, we will be finalizing the deadline at the Cinder sprints at the summit on Friday May 15th.

Requirements for a volume driver to be merged:

  • Your blueprint for your volume driver is submitted and approved (mark your blueprint as pending approval to get PTL’s attention)
  • Your volume driver code is posted to gerrit and passing gate tests
  • Your volume driver code gerrit review page has results posted from your CI, and is passing. Keep in mind that your CI must continue running in order to stay in the release. This also includes future releases
  • Your volume driver fulfills minimum features
  • You meet all of the above at least by June 12th. This is to discourage late code submissions. Reviews can take time. Merges can also be very difficult late in the milestone due to the OpenStack Gate testing being very full. In the past we have seen gate wait times take a whole day. Do yourself a favor and don’t wait.

To be clear:

  • Your volume driver submission must meet all the items before we review your code. If not, you’ll have to submit your volume driver in the M release
  • If your volume driver is submitted after Liberty-1, expect me to reference this email and we’ll request the volume driver to be submitted in the M release
  • Even if you meet all of the above requirements by June 12th, it is not guanranteed that your volume driver will be merged by June 19th You still need to address all review comments in a timely manner and allow time for gating testing to finish
  • This does not include backup drivers
  • This does not include connector drivers in os-brick. This will be a separate discussion.

To help speed up the review process, please review the How to Contribute a driver to Cinder documentation.

Tags:

Technical Committee Highlights May 13, 2015

Based on multiple inputs from the openstack-dev mailing list, we’ve discovered we, the TC, need to level up our communications. We have identified two TC members to take on the communications plan, Anne Gentle (that’s me!) and Flavio Percoco. See below for details of the plan, and thanks for reading the first post in the revitalized series.

Welcome and thanks

After the TC elections were complete and validated, we said goodbye to Vish Ishaya, Devanandra van der Veen and Michael Still, and we welcomed new TC members Robert Collins, Jay Pipes, Dean Troyer and Flavio Percoco. The TC voted for Theirry Carrez to continue as TC chair for running the meetings and keeping the TC patch backlog reviewed and organized.

Summit preparation and cross-project track

A subteam worked through the 28 proposals for the cross-project track at the summit to fit into 14 available fishbowl rooms. Doug Hellman then presented it to the TC and we approved it for him to then apply his “note-cards-on-the-floor schedule resolution algorithm” to fit them into available time slots. Those have been pushed to sched at libertydesignsummit.sched.org.

Communication plan

Our goals for communicating about TC activity are to inform both the electorate and the wider community about decisions made, directions pointed, or guidance given through the OpenStack Technical Committee. We’ll use regular posts to the OpenStack Blog, pointers to the post in the weekly Community mailing list, and the feed to http://planet.openstack.org to issue regular communications.

We’ll continue to listen on the openstack-dev mailing list for any issues that come up, and use patches to the governance repo to shape the agenda each week. The final decisions are published to http://governance.openstack.org. Let us know if you envision any additional channels posting to the openstack-dev mailing list. While we did also consider a Twitter account for the TC, we won’t use a common account to avoid splitting attention across too many channels.

New project team guide

In the spirit of replacing aging wiki pages and oral tradition, a small team is tackling writing a project team guide. When we say “be an OpenStack team” we need to be specific about the meaning, processes, releases, and be able to point to documentation that defines our culture and expectations. Jim Blair, Flavio Percoco, Doug Hellman, and Thierry Carrez have agreed to start this effort.

Repository patches policy

Recently the TC decided to keep the repo list tidy by allowing the TC chair to push through basic listing changes proposed by a Project Team Lead (PTL) to their own projects. The agreement is to skip discussing repo additions in the Tuesday TC meeting and instead, let the patches be viewed for at least one week. Then, as long as there is no -1 from a TC member that may need discussion, the TC chair can approve them if the changes have PTL +1 and no TC member -1 by then.

Agenda timing

The process for getting an item considered for the TC meeting agenda had been documented as being proposed “at least 4 business days before meeting,” but now that items are proposed to Gerrit, Thierry proposed changing the agenda schedule to better match the way we work now. We all agreed we can consider a change TC meeting material if posted before 0800 UTC Friday.

Tags, tagging, and marking

We managed to time-box large, expansive discussions about reviews for tags to help define a “tc-approved-release” tag as well as a “compute-kernel” tag. We didn’t go into the discussions expecting resolution, and with the Summit coming up next week, we just wanted to hear more from each other on each topic in real-time, outside of the patch review itself. For the “tc-approved-release” tag, it is meant to embody the Technical Committees responsibility under the bylaws of the OpenStack Foundation. The “compute-kernel” tag is intended to indicate which projects are essential to a basic compute use case. In fact, we even discussed changing the tag name to include use-case. At this point, it’s probably best to read the logs from the meeting and follow along the reviews, as we made no conclusions.

We’re all looking forward to a great week in Vancouver. Thanks for the ongoing input, and keep it coming.

Tags:

OpenStack Community Weekly Newsletter (May 1 – 8)

Snapshot of the OpenStack community behind Kilo

The OpenStack community that helped create the Kilo release has done some seriously heavy lifting. For the 11th release, there were more contributors, more companies involved and more work across time zones than ever before.

Heat SoftwareConfig resources – primer/overview.

Steve Hardy provides an overview of Heat’s Software Configuration resources, as a preface to digging in more detail into the structure of TripleO heat templates, which leverage SoftwareConfig functionality to install and configure the deployed OpenStack cloud.

Ceph vs Swift – An Architect’s Perspective

A description of architectural details and differences between Ceph and Swift by Christian Huebner. A useful preview of his talk on the same topic at the OpenStack Summit in Vancouver.

The Road to Vancouver

Relevant Conversations

Deadlines and Development Priorities

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

New Specs This Week

OpenStack Reactions

Saying hello for the first time at the summit to someone we know on IRC

Saying hello for the first time at the summit to someone we know on IRC

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 Trainings and Certifications Available in Vancouver

It’s almost here! The OpenStack Summit in Vancouver is just around the corner, and we wanted to update you on some upcoming OpenStack Training and Certification classes that will take place in Vancouver around the Summit dates (May 18-22). For those of you traveling, you might want to take advantage of these offers and make the most of your visit.
 
Training Offerings:
Mirantis Training for OpenStack Bootcamp I (OS100) 
Ubuntu OpenStack Fundamentals Training
 
Certification Exams:
Free Red Hat OpenStack Exams: Red Hat Certified System Administrator in Red Hat OpenStack exam
  • Date: Sunday, May 17
  • Times: 9:00 a.m. – 12:00 p.m. PDT or 1:00 p.m. – 4:00 p.m. PDT.
  • Location: Suite 1, Pan Pacific Vancouver Hotel, 300-999 Canada Place, Vancouver BC, V6C 3B5 (near the convention center.)
  • Register herehttps://engage.redhat.com/free-exam-seat-e-201505010215
Mirantis Training OpenStack Administrator Certification – Professional Level (MCA200) 
If you have any questions regarding the above Training and Certifications, please contact the member companies directly for more information.
See you in Vancouver!

OpenStack Community Weekly Newsletter (Apr 24 – May 1)

Kilo Logo

Superuser Awards final faceoff: your vote counts

Four great finalists, but only one can win: it’s a close call as the voting deadline approaches for this edition of the Superuser Awards.

Snapshot of the OpenStack community behind Kilo

The OpenStack community that helped create the Kilo release has done some seriously heavy lifting. For the 11th release, there were more contributors, more companies involved and more work across time zones than ever before.

The Road to Vancouver

Relevant Conversations

Deadlines and Development Priorities

  • Relax for a day :)

Reports from Previous Events

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

OpenStack Israel CFP Voting is Open

PyCon-AU Openstack miniconf CFP closes May 8th

Other News

OpenStack Reactions

    Kilo released. Going to the next one.

Kilo released. Another smooth ride to the next one.

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 (Apr 17 – 24)

Why you should attend an OpenStack Summit

OpenStack Summits don’t miss a beat – with a schedule full of diverse breakout sessions, captivating speakers, off-the-wall evening events and the occasional surprise, it’s the twice-yearly event you simply cannot miss. What would you add to the list of 10 most memorable summit moments to date?

Gnocchi 1.0: storing metrics and resources at scale

Gnocchi provides a scalable way to store and retrieve data and metrics from instances, volumes, networks and all the things that make an OpenStack cloud. Gnocchi also provides a REST API that allows the user to manipulate resources (CRUD) and their attributes, while preserving the history of those resources and their attributes. The Gnocchi team takes great pride in the quality of their documentation too, fully available online.

The Road to Vancouver

Relevant Conversations

Deadlines and Development Priorities

Reports from Previous Events

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

OpenStack Israel CFP Voting is Open

PyCon-AU Openstack miniconf CFP open

Other News

OpenStack Reactions

 

Having to look for an error into a devstack log

Having to look for an error into a devstack log

 

 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.