The OpenStack Blog

OpenStack Technical Committee Update (July 1)

The last TC update discussed the DefCore effort being led by the OpenStack Foundation Board. The DefCore subcommittee had made some requests for input from the TC. This week we held a special meeting entirely focused on clarifying some points around DefCore and providing some responses to the questions given to us.

It’s also worth noting that prior to the meeting, Jonathan Bryce posted a very comprehensive review of the existing framework that governs OpenStack trademark usage. This thread is absolutely worth reading for a good understanding of this topic.

Scope of DefCore

The first point on the agenda was to clarify the scope of DefCore. Specifically, we wanted to clarify which uses of the trademark this effort was applicable to. There were some important points of clarification reached during the meeting on this topic. DefCore is only about the commercial uses of the trademark. Currently, this only includes the “Powered by OpenStack” trademark license program. We also understand that the board has left open the option of an “OpenStack Compatible” trademark program in the future that may have a different set of requirements than what we are discussing right now.

Jonathan clarified this very well during the meeting (at 20:25:56):

The license agreement in question is called OpenStack Powered and is intended for use with products and services that are built using OpenStack software. for instance a public cloud “FooTron Compute Powered By OpenStack”, an appliance “FooTron Appliance Powered by OpenStack”, a distribution “FooTron OpenStack”. All of those different products would be held to the same standard. in other words, they would all be required to expose the same capabilities (testable over the APIs) and include the same actual community-developed software bits (designated sections).

DefCore Capabilities

The DefCore subcommittee has been working to define a set of capabilities with associated tests that would be used as a part of the process to determine if a given OpenStack product or service was allowed to use the OpenStack mark under the “Powered by OpenStack” trademark program. They have been using a scoring system to determine which capabilities should be required. Part of the input into this scoring is “technical direction”. They do not want to include a required capability that the technical community does not view as something we want to keep around long term. The TC was asked to provide input on some capabilities where the future was unclear. We have been working on clarifying all of these points in two reviews to the OpenStack technical governance repository. We are close to reaching a final conclusion on these points.

DefCore capabilities are currently defined in a JSON file as a mapping to a set of tests. One recommendation that the TC provided was that a 1 or 2 sentence description for each capability would help provide easier understanding of the intended coverage of a capability. Otherwise, interested parties must go read each test to understand exactly what it’s attempting to verify. While this would be helpful, we all agreed that this does not actually block progress. It would just make things easier.

The final point discussed in this section of the meeting was the intersection of capabilities and designated sections of code. Generally you have to implement designated section code and deliver core capabilities, but it was clarified that designated sections of code would only be required if there is a corresponding capability that is deemed required. If a project has no required capabilities, then the use or distribution of that project is not required.

Designated Sections

This was the most controversial part of the meeting. The DefCore committee had requested that the TC provide a proposed set of designated sections of code. This input would then be used as the basis for what code is required under the “Powered by OpenStack” trademark license program. After much discussion, the TC was able to reach consensus on this topic and a response was provided in this meeting.

One of the primary responsibilities of the TC is to define the OpenStack integrated release which is released every 6 months. This is the set of things that we vouch for. We have a defined process with a set of requirements projects must satisfy to apply for incubation and potentially eventually graduate to be a part of this integrated release. Defining a subset of the integrated release would make the TC appear to endorse or encourage replacing part of their work with proprietary alternatives. The TC is an elected representation of the contributors to the project and as such it does not feel it should declare a subset of the integrated release less important than the rest.

We do value that the Apache license provides the option of replacing part of the code with alternative solutions, and we respect that it’s the board prerogatives to determine trademark use policy. So we would like to clearly recognize that it’s the board’s right to define the subset of the integrated release required by commercial trademark license agreements (such as the “OpenStack Powered” trademark program), and therefore they should have final say on “designated sections”. A process to achieve that was suggested by Mark McLoughlin on the Defcore list, where the Board would propose designated sections and ask the wider community for comments on it, then make the final calls based on that feedback.

Category: Governance

OpenStack – A Global Perspective: Five Things we Learned at OpenStack Events Across Europe and Israel

We say the words “global community” and “collaboration” so often they can start to lose their meaning. It’s easy to lose sight of the bigger picture, and the scale of our community far beyond name-brand users from the US or the number of Summit attendees. A few weeks ago, members of the OpenStack community organized a series of events across Europe and Israel, including Budapest, Paris, Milan, Tel-Aviv and London.I was fortunate enough to attend several events, and my goals were two-fold: to do some learning as we prepare for the November Summit in Paris, including getting a pulse on the issues and topics resonating most in the region and identifying new users we could feature; and second, of course, to start promoting the Paris Summit (shameless plug, happening November 3-7) by getting sponsors, press and potential attendees on board.

Jonathan

But what I really took away from the trip was a reminder that our greatest strength truly is the diversity and size of our global community. They aren’t just words that we throw around, but the hundreds of people we met and stories we heard in just a few short days. Reflecting on my conversations and a few interviews with the user group leaders, I wanted to pass along my five takeaways from the trip:

Businesses everywhere just want to move faster. Full disclosure, my original plan for this blog post was to interview the user group leader at each event and ask about the unique drivers in their region for OpenStack (or cloud and general). I suppose I shouldn’t have been surprised when they gave me essentially the same answers. The themes we discussed at the Atlanta Summit, including the Software-Defined Economy and needing to move faster than emerging competitors, resonated with everyone (unprompted!). Sure, there may be different regulatory environments or more financial services organizations in the UK and startups in Budapest, but at the end of the day they still want the same thing: the speed and agility to compete. The beauty of OpenStack is that there are many different ways to consume it, whether you’re a small business in Italy using Enter’s public cloud services, or building scale-out infrastructure for researchers to store and analyze data at CERN in Switzerland.

One of those user group leaders was Mariano Cunetti of Enter IT, based in Milan. According to Mariano, “the idea of team and company is changing. It has not been a painless process, but moving to the cloud is not only a matter of infrastructure. It’s not just a matter of how you develop your tools, it’s changing your processes. It’s being more agile and quick. In the next few years, the difference between companies adopting cloud compared to the ones who are not adopting cloud will be the difference of surviving and not.  Time to market will be so fast, that you need to keep the pace. You choose the pace you want to run to.”

London

Data sovereignty and national services create a different landscape in Europe, especially in industries like telco. I am familiar with the concept of data sovereignty and implications for our users, but one interesting thing we learned on the trip is that likely this year an update is coming to the EU-wide Data Protection Act Directive established in 1995. The new regulation, called the General Data Protection Regulation, is expected to take into account globalization and technological developments like cloud computing. As I mentioned, we’ve been talking about data sovereignty for some time — and it’s been a pretty significant driver of adoption among mid-size service providers across Europe and Australia — but debate and discussion around the new EU regulations, as well as court cases like Microsoft’s Dublin datacenter will be very timely for the OpenStack Summit in Paris, where we expect to discuss such issues with leading telcos, enterprises and technology vendors.

LivePerson

We’ve moved from “what” to “how.” Attending many of these same events a year ago, what really struck me is how the conversation has changed in tone. We’ve moved beyond the question of “what is OpenStack?” or “why OpenStack” to how it’s being used and more advanced topics. Attendees seemed eager for more technical deep dives and workshops. At the Paris event, Andrew Mitry from Comcast presented their user story, and had the most engagement and questions from audience members who were planning or operating their own deployments. In a short video interview, Nati Shalom, CTO of GigaSpaces and organizer of the OpenStack Israel Day, said: “When they were getting started, there was a lot of questions about whether OpenStack was the right thing. Is it going to happen? Is it going to be successful? Is it something that I should bet on? Even until last year that was the main discussion, but this year it’s more about how do I get started, how do I actually implement things, and how do I move fast with OpenStack.”

Budapest Check-in_2

Márton Kiss, who co-organized OpenStack CEE Day in Budapest, told me, “the major driving force behind this interest is that people started to trust the open source technology. The startups are definitive end-users of cloud technology, they know and use agile development, continuous integration / deployment, the entire devops culture, and OpenStack fits here as an alternative platform to Amazon. Larger enterprises here still have a conservative attitude, but telecom and financial sector are doing pilot projects. The structure of enterprises is a bit different in this Eastern European region, because most companies don’t have HQs here, but there are a lot of software development / technology center located here.”

Shuttleworth

Contribution pays off. One of the most exciting things to see is the companies who have been contributing — both code and community activities like organizing these events — have been making a name for themselves, and building their brand as OpenStack experts in the global community. They’ve gained knowledge and relationships that are translating into real business opportunities. We met some very large users who are choosing to work with smaller, focused companies in the OpenStack ecosystem because they know contributions equate to knowledge and influence. Companies who are consistently contributing are also openly attracting talent, because many of the OpenStack experts want to work in an environment where they know their efforts are going to have a broader impact. As one example, I was going to report on how impressive it has been to see eNovance grow and expand globally, because we had the chance to tour their new — OpenStack themed! — offices in Paris, but they’ve since been acquired!

Thierry

Need more focus on operations and end users. This isn’t so much a lesson learned on this trip, as it was reinforced by these events. The makeup of attendees has evolved from primarily vendors looking to productize OpenStack and contributing developers to infrastructure teams within larger enterprises and research organizations who are using the software. The content has also evolved, but there’s more we can do to focus on cloud operators and app developers. One thought is for the Foundation to help recruit and sponsor more users like Andrew Mitry to travel and speak at these events, because hearing case studies and having the chance to ask/answer questions first hand is incredibly valuable.Please feel free to weigh in, whether or not you attended the events, I’d love to get your perspective.

Thank you to all of the organizers who put significant time into these events: Márton Kiss and Gergely Szalay in Budapest; Annie Potvin and the eNovance (now Red Hat) team in Paris; Martina Casani, Mariano Cunietti and the Enter team in Milan; Avner Algom, Nati Shalom, Sharone Zitzman and the GigaSpaces team in Tel-Aviv; and Mark Baker, Cezzaine Zaher and the Canonical team in London.

I’m energized as we head to Paris in November, and hope to see you there.

Category: community, Event, Newsletter, Uncategorized

OpenStack Global Community: Interviews from OpenStack Days in Italy & Israel

Mariano Cunietti & Martina Casani, Enter IT

We recently had a chance to catch up with OpenStack community members Mariano Cunietti, CTO, and Martina Casani, Marketing Manager, at Enter IT.  Mariano got involved in OpenStack around the Folsom release and first attended the San Diego Summit in October 2012. He helped establish the Italy OpenStack User Group upon return from San Diego, which has since grown to more than 300 participants. They hosted the first OpenStack Day Italy at their offices in Milan, Italy, May 30th.Enter’s office space in Milan is truly unique. As part of the company’s process and culture transformation, and after touring several co-working spaces in the San Francisco / Bay Area, they decided last year to turn their own offices into a co-working space. Mariano explains in the video how co-working spaces are a great representation of cloud infrastructure physically, a true multi-tenant environment with shared infrastructure for the different teams and people they host. What you aren’t able to see in the video is that the office is entirely configurable and made of low-cost materials where possible. All of the desks are on wheels, and even the hanging outlets can be swung along tracks to different locations. They were easily able to clear out a large meeting space where they hosted more than 125 attendees for the OpenStack Day. And more important than the physical setup, the biggest benefit to them has been the exchange of ideas, meeting new and interesting people with which they are now collaborating, for example companies working in security, communications, drones and 3D printers.

Enter is an ISP funded in 1996 with expertise is datacenter services and connectivity. When it came to OpenStack, they were searching for a technology to bring their virtual private server product to market. Mariano says VPS is popular in the Italian market because 95% of companies are small businesses who don’t need large, scale-out architectures. Now with OpenStack, they have a real public cloud, Enter Cloud Suite, and are also actively pursuing hybrid cloud services so users can run OpenStack in house and then scale on the public service as they need. OpenStack is core to Enter’s infrastructure, and they are continuing to build a suite of services around it, such as hadoop, CDN and email.

Mariano says that engaging with the global OpenStack community dramatically changed the way Enter approaches work.  Where they used to wear suits, they are now more casual, and they’ve traded in tools like Microsoft Exchange for new ones. They have changed their internal processes, and are much smarter and more efficient than they were.  According to Mariano, “the idea of team and company is changing. It has not been a painless process, but moving to the cloud is not only a matter of infrastructure. It’s not just how you develop your tools, it’s changing your processes. It’s being more agile and quick. In the next year, the difference between companies adopting cloud compared to the ones who are not adopting cloud will be the difference of surviving and not.  Ttime to market will be so fast, that you need to keep the pace. You choose the pace you want to run to.”

###
Nati Shalom, CTO & Founder of GigaSpaces

Nati Shalom, CTO & Founder at GigaSpaces, got involved with OpenStack when the community was just being formed. He has since been instrumental in building the OpenStack user group in Israel, and we caught up with him at the 5th OpenStack Day Israel, June 2nd.  It was the biggest and most successful event the group has hosted yet with more than 500 attendees. The crowd is a mix of major users like LivePerson, technologists from global IT companies with R&D offices in Tel-Aviv and startups who are building web scale applications or products around OpenStack.

Over the past few years, Nati has seen a significant shift in the conversation at these events. Even last year, there were still questions about about whether OpenStack was the right thing. “Is it going to happen? Is it going to be successful? Is it something that I should bet on?” This year he’s seen it tip over to questions like “How do I get started? How do I actually implement things? How do I move faster with OpenStack?” That shift was also evident to him at the latest Summit in Atlanta. People are no longer standing at the fence and looking at how OpenStack is shaping up. They are moving to execution and sharing their user stories and best practices. It reminds Nati of the Java community 10 years ago, where a big, revolutionary shift in technology brings together business people, users and developers in a very collaborative fashion.

In this quick interview, Nati discusses the unique business landscape in Israel with an atmosphere of entrepreneurship. He calls Israel a startup nation. One reason being that Israel is small and there are not many natural resources, so the ability to export ideas and innovation is very important. There is a strong tech startup and R&D community that is always working on the next big thing, so emerging technologies are very well received. OpenStack plays well into the scene, and we met many Israeli companies like GigaSpaces, Mellanox, LivePerson and Cloudyn that are actively involved in the community.

One thing that Nati values highly is the transparency and availability of information from the community. We did not discuss it in this video, but during his presentation at the event, Nati talked about the differences between working in an open source community and with a proprietary software platform in terms of transparency and ability to influence the roadmap. He gave an example of the user survey conducted by the user committee every six months, the results of which are shared broadly with our technical community and ecosystem. The ability to have real data and insight into user adoption and tools being used has a huge impact on his product strategy. Proprietary vendors might push their partners in one direction based on their roadmap and plans, but they rarely expose the raw data required to make your own analysis.

Category: Uncategorized

Call for Speakers now OPEN – November Summit in Paris

Screen Shot 2014-07-01 at 9.23.02 AM

 

 

 

The Call for Speakers is OPEN for the November OpenStack Summit in Paris! 

Submit your talks here: https://www.openstack.org/summit/openstack-paris-summit-2014/call-for-speakers/.

There are a few new speaking tracks in the Summit lineup this year so please review the below list before you submit a talk.

Don’t wait! The Call for Speakers will close on July 28 at 11:59pm CDT.

The Summit will take place in Paris at Le Palais des Congrès, November 3-7. The main conference and expo will run Monday – Wednesday and the design summit will run Tuesday – Friday.

If you have any Summit related questions please contact events@openstack.org.

Continue to visit openstack.org/summit for information including:
• Event format
• Registration
• Hotel room blocks
• Visa invitation letters
• Venue maps
Speaking Tracks for the OpenStack Summit in Paris:

• Enterprise IT Strategies
Enterprise IT leaders building their cloud business case are facing unique requirements to manage legacy applications, new software development and shadow IT within industry regulations and business constraints. In this track, we’ll discuss how OpenStack is meeting enterprise IT technical requirements and cover topics relevant to planning your cloud strategy, including culture change, cost management, vendor strategy and recruiting.

• Telco Strategies
Telecommunications companies are one of the largest areas of growth for OpenStack around the world. In this track, we’ll feature content relevant to these users, addressing the evolution of the network and emerging NFV architecture, the global IaaS market and role of telcos, industry regulation and data sovereignty, and industry cooperation around interoperability and federation.

• How to Contribute
The How to Contribute track is for new community members and companies interested in contributing to the open source code, with a focus on OpenStack community processes, tools, culture and best practices.

• Planning Your OpenStack Project
If you are new to OpenStack or just getting started planning your cloud strategy, this track will cover the basics for you to evaluate the technology, understand the different ways to consume OpenStack, review popular use cases and determine your path forward.

• Products, Tools & Services
OpenStack’s vibrant ecosystem and the different ways to consume it are among it’s greatest strengths. In this track, you’ll hear about the latest products, tools and services from the OpenStack ecosystem.

• User Stories
Sharing knowledge is a core value for the OpenStack community. In the user stories track, you’ll hear directly from enterprises, service providers and application developers who are using OpenStack to address their business problems. Learn best practices, challenges and recommendations directly from your industry peers.

• Community Building
OpenStack is a large, diverse community with more than 75 user groups around the world. In the community building track, user group leaders will share their experiences growing and maturing their local groups, community leaders will discuss new tools and metrics, and we’ll shine a spotlight on end user and contributing organizations who have experienced a significant internal culture change as participants of the OpenStack community.

• Related OSS Projects
There is a rich ecosystem of open source projects that sit on top of, plug into or support the OpenStack cloud software. In this track, we’ll demonstrate the capabilities and preview the roadmaps for open source projects relevant to OpenStack. This presentation track is separate from the open source project working sessions, which allow the contributors to those projects to gather and discuss features and requirements relevant to their integration with OpenStack. A separate application for those working sessions will be announced.

• Operations
The Operations track is 100% focused on what it takes to run a production OpenStack cloud. Every presenter has put endless coffee-fueled hours into making services scale robustly, never go down, and automating, automating, automating. The track will cover efficient use of existing tools, managing upgrades and staying up-to-date with one of the world’s fastest-moving code bases and “Architecture show and tell,” where established clouds will lead a discussion around their architecture. If you’re already running a cloud, you should also join us in the Ops Summit for some serious working sessions (no basic intros here) on making the OpenStack software and ops tools for it better.

• Cloud Security
The Security track will feature technical presentations, design and implementation disussions relevant to cloud security and OpenStack.

• Compute
Computing is a broad topic, but this track will offer technical presentations, use cases, and design and implementation specific to the OpenStack Compute project. Topics will include new features, integration with tools and technologies and configuration as well as hypervisors, HA, schedulers, bare metal computing and databases.

• Cloud Storage
The Storage track will feature technical presentations, use cases, design and implementation discussions relevant to cloud storage and OpenStack.

• Cloud Networking
The Networking track will feature technical presentations, use cases, design and implementation discussions relevant to cloud networking, specifically topics like SDN, scale, IPv6, policies, HA and performance.

• Public & hybrid clouds
The public and hybrid clouds track will cover issues and considerations unique to organizations who are making use of public or hybrid cloud infrastrucutre, or are considering this approach.

• Hands-On Labs (90 minutes)
Hands-on Labs offers a window into OpenStack training for operators and application developers. Sessions are typically 90 minutes and set classroom style for interaction. Bring your laptop and walk away with OpenStack skills.

• Targeting Apps for OpenStack Clouds
A large community of application developers and ecosystem of development tools is growing around OpenStack. This track will be for users who are building and deploying applications on OpenStack clouds, and cover topics like automating and managing application deployment, application software configuration, SDKs, tools, PaaS and big data.

Category: Event, Summit, Uncategorized

OpenStack Turns 4 – It’s Time to Celebrate the Community!

OpenStack celebrates its 4th birthday July 19, and we’re celebrating with the entire OpenStack community during July!  User maturity, software maturity and a focus on cloud software operations are rapidly emerging for OpenStack and none of it would be possible without the quickly growing OpenStack community. There are now more than 70 global user groups and 17,000 community members across 139 countries, spanning more than 370 organizations. This calls for a big toast to the OpenStack community members and our users.

Within our community, we are also celebrating our users in our online publication, Superuser. Check out birthday-themed features during July and keep an eye out for our infographic that will showcase user growth metrics and deployments.

4th Birthday Sticker

We’ve invited all our user groups to celebrate with us. During the month of July, more than 50 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! Don’t forget to share your pictures and memories using #OpenStack4Bday.

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


Find a local celebration in your area:
Atlanta – July 17
Austin - July 10
Bangalore, India – July 13
Berlin, Germany – July 29
Beijing, China – July 19
Boston - July 10
Brazil – July 26
Brisbane – July 24
China  - July 19
Colorado – July 15
Connecticut – July 15
Ecuador – July 24
Egypt - July 19
Florida – July 11
Frankfurt, Germany – July 28
Greece – July 9
Hong Kong – July 4
Hungary – July 10
Indonesia – July 1
Iran – July 14
Ireland – July 18
Israel – July 3
Italy – July 10
Japan – July 10
Kentucky – July 17
Korea – July 16
London – July 15
Los Angeles – July 31
Minnesota – July 21
Mumbai, India – July 20
Munich, Germany – July 23
Nairobi – July 29
Netherlands – July 17
New York City – July 16
Paris, France – July 2
Philadelphia – July 17
Philippines – July 4
Portland – July 22
Russia – July 19
San Francisco - July 30
Seattle – July 24
Slovenia – July 10
Switzerland – July 17
Sydney – July 10
Taiwan – July 11
Thailand – July 21 – 23
Toulouse, France – July 9
Venezuela - July 19
Washington DC – July 9

 

 

Category: Uncategorized

OpenStack Community Weekly Newsletter (June 20 – 27)

OpenStack Technical Committee Update (June 25)

The TC is busy discussing OpenStack Glance‘s mission, evolving from cataloging and serving Nova disk images to cataloging and serving other artifacts consumed by other OpenStack services, like for example Heat templates. This scope evolution has been under discussion at the last two meetings. Read the other things that keep the TC busy on OpenStack blog.

A Path Towards Contributing (via Commits) in Open Stack

Matt Fischer set himself a goal to contribute 12 patches to OpenStack during 2014: he reached the goal and shared how he did it.

On bug reporting…

Speaking of contributing, sending bug reports is a good way to contribute to OpenStack (together with doing code reviews). Kashyap Chamarthy has a very good guide on how to file a useful bug report.

Engage in technical discussions keeping in mind the OpenStack promise

There is a conversation about what is Cinder itself and what’s the role of its drivers. It’s a highly technical debate and a very important one, where I think this promise needs to be reminded: There will be no “Enterprise Edition”. John Griffith and Ken Hui have a lot of interesting things to say about this and I suggest you to read their posts and read the conversation on this proposed specification. Then we may want to have a wider conversation about Software Defined Storage (SDS) and Cinder.

Reports from Previous Events

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Constanze Kratel Harry Rybacki
TaoBai David Pineau
Kevin McCarthy Angus Lees
Angus Lees Michael Turek
yalei wang IBM xCAT CI
Craig Bryant Clayton O’Neill
Ben Roble Tomáš Nováčik
pritesh Randy Bertram
Vishal kumar mahajan Kevin Fox
Tomoki Sekiyama Aaron Sahlin
Jyotsna yalei wang
sridhar basam
Tomoki Sekiyama
Matthew J Black
Anthony Lee
Jason Rouault
James Kremer
Craig Bryant

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

When your patch has passed half the tempest tests at the gate, and the other half is still running.

With sound

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.

Category: Communication, community, Newsletter

OpenStack Technical Committee Update (June 25)

Two weeks ago, Russell Bryant inaugurated a series of blogposts about what the Technical Committee (“TC”) is working on. We will regularly post about the outcomes of the TC meetings, and rotate writers to give all TC members a chance to participate and describe what happens in their own words. This post will focus on what happened during the last two meetings.

The TC has several missions, and the topics we cover in TC meetings generally fall into one of them.

Mission #1: Integrated release contents

One of the missions of the TC is to determine what is part of the OpenStack “integrated release” that we collectively produce every 6 months. We manage the “incubation” process, through which selected projects can become part of the integrated release. We also keep an eye on already-integrated projects in case their scope evolves.

That’s the case currently for Glance, whose mission is evolving from cataloging and serving Nova disk images to cataloging and serving other artifacts consumed by other OpenStack services, like for example Heat templates. This scope evolution has been under discussion at the last two meetings. The principle of expanding Glance’s scope is pretty much accepted at this point, but the precise words to describe the new scope are still under discussion.

In order to set clear base expectations for projects in the incubation/integration process track, last cycle the TC came up with a reference document listing all the requirements for incubation, integration and the first integrated cycle that are consensual across TC members. This document is constantly revisited as we continue to raise the quality and convergence bar between integrated projects.

Last two meetings we have been discussing adding a translation support requirement for projects wishing to graduate from incubation. The main objection to it at this point is the lack of automated testing of the translated strings (which resulted in undetected I18N problems in the past). It looks like when this is addressed, this requirement will probably make it to the reference document.

Raising requirements for new entrants is one thing, but sometimes existing integrated projects do not fill those new requirements. This creates a gap that we need to address. During this cycle we reviewed most existing integrated projects (Heat and Swift are still pending). When a gap was raised, PTLs responded with a proposed “gap coverage plan” to address it.

The last project to go through that exercise was Glance, where a single gap around testing coverage was raised. Mark Washenberger (Glance PTL) created a gap coverage plan to address it and that plan was blessed by the TC at the last meeting.

Having plans is a good thing, but we also need to check that projects meet the deadlines that they set in such plans. Last week, after the juno-1 development milestone, we reviewed the progress on gap coverage plans. Ceilometer plan is on track, still targeting the juno-2 milestone for fully covering the gap. Horizon plan is mostly on track. Neutron has an ambitious gap coverage plan, and work on all gaps has started; gap 4 is a bit late (was planned to be completed by juno-1), but it’s also been determined to just be one API call. Trove plan is on track, and work started on all items.

Finally, having responsibility over the integrated release also means making sure we use terminology across integrated projects consistently. An issue was raised about the use of “certified” terminology to qualify CI testing on some projects. After open discussion on the -dev mailing-list and at the TC meeting, there was agreement that “certified” terminology was too loaded and should be phased out in favor of some variation around “tested”.

Mission #2: Representation of technical contributors

The TC is a directly-elected body representing all the technical contributors to the project. It is the final decision-making entity over technical matters in OpenStack as a whole. Some issues that can’t be solved at a lower level are sometimes escalated to the TC for final resolution, and the TC is also a convenient conduit for other OpenStack governance bodies to ask for general technical input.

Two issues were brought to the TC recently. The first one is about expected election behavior for our technical elections (PTLs and TC members). Our current election procedure doesn’t clearly describe expected behavior, and a proposal was raised to cover that. While everyone agrees on what is acceptable behavior and what is not, there are two ways of addressing issues if they arise. One is to piggy-back on the Community Code of Conduct, which clearly states that you should respect the election process. The other is to call out out-of-line behavior and trust the voters to make their own judgment about it. Both options are and will stay available, but we are still discussing which of those options (if any) we should encourage by making it part of the TC resolution. This discussion is on-going and will continue in a future meeting.

The other issue being brought to the TC were requests from the Foundation Board of Directors “Defcore” subcommittee for technical input to use as part of their work on trademark rules. There are two types of requested inputs. One is to provide for each project “designated sections” of code that you need to run in order to use the “OpenStack” trademark. The other is to give precise scoring for “core capabilities”: for each capability, indicate whether it’s part of the TC future direction or if it’s on its way to be deprecated.

While those inputs are technical (and we even voted on guidelines to help coming up with answers), some TC members expressed clearly their discomfort. Asking the representation of OpenStack contributors to designate parts of OpenStack that may just be replaced by proprietary alternatives (while still being called “OpenStack”) just crosses the line as to what they consider acceptable. Our “technical” answer might be read as an endorsement, or collaboration toward a behavior we don’t really want to encourage.

This tension has been surfacing every time Defcore was discussed at the TC meeting, and it’s difficult to address it between two topics in a one-hour online meeting. We have therefore scheduled a Defcore-specific TC meeting for July 1st (20:00 UTC in #openstack-meeting on Freenode IRC), and will try to clearly list concerns beforehand to ensure meeting clarity.

Category: Communication, community, Governance

OpenStack Community Weekly Newsletter (June 13 – 20)

Summer Speaking Sessions and Call for Papers

Summer is in full swing and there are some great industry events coming up on the OpenStack Marketing calendar, as well as Call for Proposals deadlines!

Marconi to AMQP: See you later

In the last couple of weeks, Marconi’s team has been doing lots of research around AMQP and the possibility of supporting traditional queuing systems. Flavio Percoco, believed with others that this capability would be useful. However, after digging more into what’s needed and what supporting traditional brokers means for Marconi, the community changed its mind and now believes supporting such systems doesn’t make much sense anymore. This post explains why.

Tracking multiple OpenStack projects using StoryBoard

StoryBoard is a new task tracking system which is aimed at the systems where projects are closely related, and OpenStack is definitely a good example of that. In inter-related systems like OpenStack, a feature or a bug usually affects more than one project, so it should be tracked simultaneously across those projects. The proof-of-concept was presented in the Havana release cycle by OpenStack release manager Thierry Carrez, and active development started during the Icehouse development cycle. The project is now driven by three major contributor companies: the OpenStack Foundation, Mirantis, and HP.

Breaking news:OpenStack Object Storage ‘Storage policies’ merge today

The series of patches that will eventually lead to Swift 2.0 merged today. Many Swift contributors have been working on storage policies for quite some time now. It’s a huge feature and improvement to Swift that enables a ton of new use cases. Storage policies allow deployers to configure multiple object rings and expose them to end users on a per-container basis. Deployers can create policies based on hardware performance, regions, or other criteria and independently choose different replication factors on them. A policy is set on a Swift container at container creation time and cannot be changed. Full docs and more details about the roadmap in this message by John Dickinson.

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

peng fei wang Renjie Sun
Doug Wiegley Vishal kumar mahajan
Stephen Jahl Nikunj Aggarwal
joanne Lennart Regebro
Richard Hagarty João Cravo
Flavio Fernandes Anna Eilering
yingjun Vivek Jain
Tom Cammann Susanne Balle
Julie Gravel Stephen Balukoff
Rikimaru Honjo Shayne Burgess
Diana Whitten Nathan Manville
Max Grishkin
German Eichberger
Dustin Lundquist
Doug Wiegley
Yi Sun
Przemyslaw Czesnowicz
FrazyLee
Ying Zuo
Julie Gravel
Jorge Chai
Bradley Klein

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

its-friday

When I see the OpenStack newsletter in my mailbox

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.

Category: Communication, community, Newsletter

Summer Speaking Sessions and Call for Papers

Summer is in full swing and there are some great industry events coming up on the calendar, as well as Call for Proposals deadlines!

The Global Events Calendar is the primary resource to know what events are approaching. It is fully editable, so you can update the following criteria:

  • If your organization is attending, sponsoring or exhibiting (COLUMN G)
  • Provide feedback or ideas on events (COLUMN H)
  • Add vendor-independent industry events to the calendar (complete ALL criteria)

Here are the upcoming industry events planned for July:

OSCON: July 20 – 24, Portland OR

  • No charge Expo Plus registration using OPENSTACKEHO.  Or 25% discount on any other conference pass using OPENSTACK25.  Pass these on!
  • Open Cloud Day: July 21, featuring Chris Launey from The Walt Disney Company, OpenStack user, Thierry Carrez from the OpenStack Foundation, and Rob Hirschfeld, OpenStack Board Director.  Open to all registrants, including Expo Plus.
  • If you’re attending, be sure to attend the OpenStack birthday party Tuesday, July 22nd at Union/Pine. Details coming soon!

EuroPython: July 21 – 27, Berlin, Germany
PyCon AU: August 1 – 5, Brisbane Australia – There will be an OpenStack miniconf on Friday, August 1, a full day event with several community speakers
CloudOpen NA: August 20 – 22, Chicago  - Looking for a well-known speaker and community volunteers

Here are the approaching CFP deadlines:

DEVIEW 2014: June 30
LinuxCon/CloudOpen Europe: July 11
Software Defined Enterprise World Forum: No deadline listed
FSOSS: No deadline listed

If you have any questions, or you would like to plan a regional OpenStack Day, please contact events@openstack.org

Category: community, Event, Uncategorized

OpenStack Community Weekly Newsletter (June 6 – 13)

Moving forward as a User Experience Team in the OpenStack Juno release cycle

The OpenStack Juno Summit in Atlanta was a major turning point for User Experience professionals working on OpenStack. There were 3 specific design sessions around UX work and 1 talk on the persona work, all with great attendance, and the whole team committed taking a number of actions to take over the course of the Juno development cycle. Liz Blanchard summarized them quite nicely.

OpenStack Technical Committee Update

The OpenStack Technical Committee (TC) meets weekly and recently decided to publish regular updates about the TC to the OpenStack blog. The first post has news about the graduation process, Glance and Designate.

Calling on Security Engineers / Developers / Architects – Time to share your toys

Lets work together and openly on security review and threat analysis for OpenStack. There are currently scores of security reviews taking place on OpenStack architecture, projects and implementations. Robert Clark sent a call for action to OpenStack developers: “All the big players in OpenStack are conducting their own security reviews, we are all finding things that should be addressed in the community and that we are all missing things that others have found too.” Robert’s call is for all the security people out there in the community to come together and share expertise on Threat Modelling/Analysis in OpenStack.

Reports from Past Events

Tips ‘n Tricks

Security Notes and Advisories

Upcoming Events

Other News

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Welcome New Reviewers and Developers

Petersingh Anburaj mark collier
Ellen Hui Rey Aram Alcantara
Pierre Rognant Patrick Crews
ajay Angela Smith
Rui Zang Zu Qiang
Rahul Verma Vladimir Eremin
Christoph Arnold Praveen Yalagandula
Amit Prakash Pandey
Ton Ngo
Tom Cammann
Sam Leong
Paul Montgomery
James Chapman
Gal Sagie

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

tumblr_inline_n1h25lbMTa1raprkq

Giving +2 out of fear

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.

Category: Communication, community, Newsletter

Back to top