The OpenStack Blog

Category: OpenStack Update

Announcing the O’Reilly OpenStack Operations Guide

Er, what’s this? An O’Reilly OpenStack Operations Guide offered side-by-side with the continuously-published OpenStack Operations Guide? Yes, your eyes do not deceive you, O’Reilly has completed the production of the OpenStack Operations Guide: Set Up and Manage Your OpenStack Cloud. You can get your bits-n-bytes copy at http://docs.openstack.org/ops/ or order a dead-tree version on the O’Reilly site.

oreilly-openstack-ops-guide

This book was a complete community effort with a bit of a twist: we held a five-day book sprint back in February 2013 with the seven original authors and one book sprint facilitator, Adam Hyde. We wrote and wrote and wrote some more, then edited and glued it all together so that we had a 240 page book by Friday afternoon. The book got quite a bit of love and attention for the next year or so, and in February 2014 we held a mini-sprint with the original authors to update the book for the Havana release and to address developmental edits from our O’Reilly editors, led by Brian Anderson and first introduced by Andy Oram. In the developmental edit, we added a new architecture with RedHat using OpenStack Networking (neutron) as an alternative to Ubuntu with legacy networking, nova-network. We tested a process for upgrading from Grizzly to Havana in a new upgrades chapter. We also added a lot of network troubleshooting information. There’s a new “Havana Haunted by the Dead” tale from the crypt/cloud. We included an expanded glossary as well. Also an exciting addition to a book nerd like myself is the index.

As mentioned in the book itself, we appreciate the 50-plus contributors who support this book and the tool chains around it. Reviews, continuous builds, output, and translations are all an important part of this book’s surrounding systems.

The following people are contributors in the many methods it takes to create a book in the community: Akihiro Motoki, Alejandro Avella, Alexandra Settle, Andreas Jaeger, Andy McCallum, Benjamin Stassart, Beth Cohen, Chandan Kumar, Chris Ricker, David Cramer, David Wittman, Denny Zhang, Emilien Macchi, Gauvain Pocentek, Ignacio Barrio, James E. Blair, Jay Clark, Jeff White, Jeremy Stanley, K Jonathan Harker, KATO Tomoyuki, Lana Brindley, Laura Alves, Lee Li, Lukasz Jernas, Mario B. Codeniera, Matthew Kassawara, Michael Still, Monty Taylor, Nermina Miller, Nigel Williams, Phil Hopkins, Russell Bryant, Sahid Orentino Ferdjaoui, Sandy Walsh, Sascha Peilicke, Sean M. Collins, Sergey Lukjanov, Shilla Saebi, Stephen Gordon, Steven Deaton, Summer Long, Uwe Stuehler, Vaibhav Bhatkar, Veronica Musso, Ying Chun “Daisy” Guo, Zhengguang Ou, and ZhiQiang Fan.

We want to be sure you read this book and log bugs and perhaps even fix some yourself if you’re so inclined! You can read how to on the OpenStack wiki. We also have the OpenStack Security Guide, written in a five day book sprint in June 2013. And we won’t stop there! Plans are underway for a third book to be written with a five day book sprint to help people design OpenStack clouds for many use cases.

We’ll continue to update these books using our community tool chain. We greatly appreciate the support from the OpenStack Foundation and O’Reilly to give the OpenStack Operations Guide that professional polish it deserves.

OpenStack 2014 T-Shirt Design Winner

The 2014 T-shirt design contest is a wrap! Thank you to everyone who shared their creativity and original designs with us this year.
We are excited to reveal our winner, Jaewin Ong of Singapore! This colorful design will debut on T-Shirts at PyCon in Montreal this week, and will be distributed at upcoming events worldwide.
OpenStack T-Shirt Design
We wanted to learn more about the creative mind behind the design, so we asked Jaewin a few questions:
What was your inspiration for this design?
  • The inspiration was actually the OpenStack logo! Since the logo is already of significance, I thought it would be cool to manipulate it with bright colors and superimposing the outline with itself.
 How long have you been designing?
  • My first design was for a T-Shirt, incidentally, during my freshman year in university. The T-Shirts were printed and sold to raise funds for a committee I was involved in. And I started out with MS Paint! I’ve come a long way.
 Where are you currently working?
  • I’m currently a junior in university pursuing a degree in Electrical and Electronic Engineering.
 In what way are you involved in OpenStack?
  • I’m afraid to say that my involvement with OpenStack is minimal. Although, I had some experience with Python during my internship. Otherwise, I do find cloud computing to be rather complex and I admire people who do it.
 Do you publish any of your other work online?
  • I don’t publish my work because I’m doing this out of interest. I would be grateful when it comes to a point where I’m publishing my work for other purposes besides interest.
 Is there anything else you might like to share about yourself?
  • I constantly look for opportunities like this to improve myself. It might not be a big deal to some, but it’s a big deal to me!
Congratulations, Jaewin!
Want to see your design on a future OpenStack T-Shirt? Stay tuned on our blog as we announce upcoming design contests!

 

OpenStack Day Events April – May – June 2014

Several upcoming OpenStack Day events are taking place around the world. Please join us in spreading the word and register soon. We hope to see you there!
OpenStack Day Mexico in Mexico City – April 29
  • When: Tuesday, April 29, 2014
  • Where: World Trade Center Mexico
  • Tickets: Tickets are MXN $200.00, covering all meals, workshops and conferences. Register quickly! 
OpenStack CEE Day in Budapest – May 26
OpenStack in Action 5! in Paris – May 28
  • Attendees will be provided with the raw materials to engage with the community, become a consumer of the technology and take part in its evolution
  • When: Wednesday, May 28, 2014
  • Where: CAP 15
  • Admission is free, so register to get an overview of the OpenStack technology, projects updates, challenges, best practices and roadmap for all audiences
#1 OpenStack Day in Milan – May 30
  • When: Friday, May 30, 2014
  • Where: Via Privata Stefanardo de Vimercate
OpenStack Israel in Tel Aviv-Yafo - June 2
Hear about OpenStack’s Icehouse Release from industry thought leaders and local OpenStack users. Following the conference, attend a 3-day training course on the current OpenStack Havana Release
  • When: Monday, June 2, 2014
  • Where: Arts Hall HaBama Herzliya
  • Tickets: We’re expecting +300 OpenStack users, prospective users, ecosystem members and developers to attend, so register quickly!
With an anticipated 500+ attendees from all sectors of London’s wide and diverse tech community, an exciting line-up of speakers and exhibitors, this will be the UK’s largest OpenStack related event this year!
  • When: Wednesday, June 4, 2014
  • Where: 155 Bishopsgate
  • Tickets: The early bird rate expires on May 14th, so register quickly before prices increase!
If you are interested in organizing an OpenStack Day event in your area, please contact events@openstack.org.

 

Participate in the OpenStack User Survey by April 11!

We’re kicking off the third round of the OpenStack User Survey this month! You may remember before last November’s Summit in Hong Kong, we helped the User Committee run a survey to aggregate OpenStack deployments and share the results.

Hong Kong Survey Results

The survey received nearly twice as many answers as the previous round (822 compared to 414) and 387 deployments compared to 187.

The first User Survey in Spring 2013 provided great insight to the types of deployments and technology decisions made by the OpenStack community. We were able to catalogue 230 unique deployments – you can see the results presented by the User Committee at the last Spring Summit. Another huge benefit was the ability to uncover new users willing to talk about their OpenStack deployments, which can be found here: http://www.openstack.org/user-stories.

If you are an OpenStack user or have customers with OpenStack deployments, please take a few minutes to respond to our User Survey and pass it along to your network. The goals of the survey are to better define the OpenStack user community and requirements, facilitate engagement and communication among the user community, and uncover new use cases or OpenStack users who might be willing to tell their stories publicly.

Below you’ll find a link and instructions to complete the User Survey by April 11, 2014 at 23:00 UTC. If you already completed the survey last year, there’s no need to start from scratch. You simply need to log back in to update your Deployment Profile, as well as take the opportunity to provide any additional input.

http://www.openstack.org/user-survey

All the information provided is confidential and will only be presented in aggregate unless the user consents to making it public. Aggregate responses will be shared with the OpenStack Board, Technical Committee and community at large to help shape the roadmap and share useful information regarding operational decisions.

You can also help us by promoting the survey so we can secure as much participation as possible, for example by retweeting the OpenStack handle: @OpenStack

Remember, you can hear directly from users and see the aggregate survey findings by attending the next OpenStack Summit, May 12-16, in Atlanta.

Thank you for your support!

 

New Foundation Gold Members & Sponsors

The OpenStack Foundation is thrilled to have new additions to our ecosystem. Three new Gold Members and 18 Corporate Sponsors have recently joined the incredible list of companies who are supporting the Foundation and driving innovation on the platform.  AptiraHuawei and Hitachi won the OpenStack Board’s approval at the November board meeting and joined the Foundation as Gold members, which requires a strong, strategic commitment to the technology and community.

We’ve also seen amazing support in Corporate Sponsorship and we want to share the impressive list of recent additions.

The diversity in technologies and geographic location of these new additions to the ecosystem reflects the growth of OpenStack and its footprint worldwide.  We are looking forward to enjoying each these companies’ unique contributions going forward!

OpenStack Commitment to Interoperability

OpenStack began with the mission to produce a ubiquitous open source cloud computing platform. A key component of that mission is building not only software, but a large OpenStack ecosystem that would support its growth and add value to the core technology platform. In carrying out that mission, the Foundation has been taking key steps to define the core technology platform and advance OpenStack interoperability.

The TL;DR summary:  Now that we have tons of users, we need to make sure all (downstream) products labeled “OpenStack” have a certain set of core capabilities, and we need to verify those with automated tests just like we do upstream.  End-users should be our focus, and ensuring they get what they want and expect out of the platform once it’s running as a service is paramount.  The goal is to define the first set of tests in time for the May 2014 Summit in Atlanta. If this matters to you, get involved!

Read on to learn more about the rationale, history, future plans, and how you can get involved.

Why does interoperability matter for OpenStack?

We’ve heard from many users and operators that interoperability between OpenStack clouds and hybrid cloud scenarios are an important part of the value they are seeking. OpenStack is most useful when it provides a common platform to consistently deploy workloads between clouds without making resource intensive changes to operations tools and processes. Value is unlocked when development tools and applications have a common target across public and private OpenStack clouds.

The full potential of OpenStack will not be realized if users don’t know what they’re going to get from public cloud services or off-the-shelf distributions and appliances. Ambiguity or mistrust about the capabilities of OpenStack isn’t good for the business ecosystem or end users. It’s important that public clouds and private cloud products branded with OpenStack have a clear meaning in the market.

What is the Foundation doing?

One of the most important responsibilities we have as a Foundation is to ensure the long-term value of the OpenStack brand in the market. This has been an ongoing priority since our founding and has involved the collective effort of a great number of community members.

When we began, we implemented an OpenStack trademark policy, which allows broad use of the OpenStack logo and name for non-commercial community building efforts like user group meetups, while also creating special guidelines, technical requirements, and licenses for use by commercial products. As the community, the software, and the ecosystem have grown, so too has the need to refine these technical requirements for commercial products, by defining a core set of capabilities included in all products and services marketed as “OpenStack.”

It is indeed a large task, one that stems from the diversity of our community, the breadth of our ecosystem, and the broad application of our software. But it is one that will ensure the longevity, vitality and utility of OpenStack far into the future.

Therefore, in order to agree on a set of well-defined criteria for the core we must take special care to have a transparent and objective process. The Board of Directors and the Technical Committee have initiated a number of programs to tackle the issue.

IncUp (Early 2013)

The first step was forming the Incubation/Future of the Core (IncUp) committee, a joint effort between the OpenStack Board of Directors and Technical Committee, aimed at tackling the process for expanding the scope of OpenStack through new project incubation and promotion.

At the April 2013 board meeting, the Board of Directors approved the IncUp committee’s recommendations, including 1) The technical committee continues to manage the incubation process for new projects applying to be part of the coordinated, integrated release 2) Projects that are part of the coordinated release should be referred to as “Integrated” (but not necessarily “Core”), and 3) “Core” is a label the Board can attach to a project that is part of the regular integrated release.

The Technical Committee is following on these efforts by creating a clear set of guidelines for projects that wish to be officially incubated, as well as the attributes an incubated project should have before being approved for graduation to the integrated release. The purpose of the guidelines are to maintain a high standard of quality and cross-project integration for OpenStack.

The important outcome of the IncUp committee places the responsibility to manage the technical scope of the OpenStack project with the Technical Committee, while the Board ultimately sets the criteria for which technical capabilities should be present in (downstream) commercial products or services marketed as OpenStack. This led to the next phase in the process: considering how to define those criteria in a standard and broadly applicable manner.

Enter the “Spider” (2013)

The Board of Directors formed a new work group to tackle the task of determining how to define Core in a consistent manner that would apply to the varied set of use cases OpenStack addresses and the broad set of technology developed within the community. Early in this effort, the team, including Alan Clark and Rob Hirschfeld, drew a map on a whiteboard of dependencies and relationships that came into play when trying to define which projects were “Core OpenStack.” The drawing, which revealed some of the complexities of the task, resembled a spider mind map and inspired the nickname for the group.

Rather than jump straight into choosing specific projects that would qualify for the “Core” label, the committee focused on defining principles that would apply equally to any commonly required and deployed component of OpenStack deployments. These principles were drafted and reviewed through the summer and fall of 2013 at a series of open community meetings held online and in various locations. After several revisions, the Board of Directors approved the final principles at their November 2013 meeting.

DefCore (Ongoing)

After approving the guiding principles at the Hong Kong Summit in November 2013, the OpenStack Board of Directors created the DefCore committee, chaired by Rob Hirschfeld and Josh McKenty, to define a “core” set of capabilities which are expected to be present in all commercial products marketed as “OpenStack”, along with a set of tests to validate those capabilities.

The creation of DefCore marks a new focus on including a test-driven component to the definition of core. This route is more objective, and test-based standards better addresses our commitment to interoperability. The committee is working to determine which capabilities a commercial offering should include to make use of the OpenStack marks and is currently in the process of standardizing the tests that must be passed. The goal is to repurpose the same testing that we’ve been doing on the upstream code to apply to the products and services downstream, ensuring that they retain the fundamental building blocks of Openstack.

One of the realizations coming out of the early work of the committee was that users think in terms of “capabilities” more than “projects.”  Projects are how we organize as a development community, but in the end the capabilities delivered by an openstack-powered cloud are what really matter, and in practice many capabilities rely on multiple underlying “projects”.  This is a subtle but important distinction which is reflected in the way we think about writing tests to validate those capabilities in the downstream products licensing the OpenStack brand.

The DefCore committee is working against an aggressive timeline with a plan to the pilot must-pass tests for Havana before the OpenStack Summit in Atlanta in May. Icehouse will follow shortly thereafter, and Juno’s test will be ready to go by the Paris summit.

Being able to expose OpenStack cloud test results and provide a defined target for end users is an incredibly important effort and high priority for the Foundation this year. It is our hope that by outlining the steps we’re taking, the community will involve themselves in these efforts and track the progress of this vital endeavor. To get involved in the DefCore process, sign up for the mailing list and follow the wiki for updates.

Instant Poll:

Create your free online surveys with SurveyMonkey , the world’s leading questionnaire tool.

OpenStack T-Shirt Design Contest

It’s a new year and we’re looking for a new design to grace OpenStack’s T-Shirts. Here’s your chance to show us your creative talent and submit an original design for our 2014 OpenStack T-shirt Design Contest!

If you’d like to participate simply send a sketch of your design to events@openstack.org.

Deadline: March 15, 2014

The winning design will be showcased on T-Shirts given out at PyCon in Montreal, April 9-17, 2014 as well as future events worldwide.

T-Shirt Postcard

For some inspiration, check out last year’s winning design by Raul.  Get your pencils sharpened or fire up your design software of choice and send us your sketches! We’re excited to see what you’ll come up with!

2013 Winning T-Shirt Design

2013 Winning T-Shirt Design

Guidelines:
  • The design must be your own original, unpublished work and must not include any third-party logos or copyrighted material; by entering the competition, you agree that your submission is your own work
  • Design should be one that appeals to the majority of the OpenStack developer community
  • Deign may include line art, text, and photographs
  • Your design is for the front of the shirt and may encompass an area up to 10″ x 10″ (inches)
  • Design may use a maximum of three colors
The Fine Print:
  • One entry per person, please. And it must be original art. Content found on the internet rarely has the resolution needed for print, and it’s considered unlawful to use without permission.
  • Submissions will be screened for merit and feasibility, and we reserve the right to make changes such is image size, ink or t-shirt color before printing.
  • By submitting your design, you grant permission for your design to be used by the OpenStack Foundation including, but not limited to, the OpenStack website, the 2014 OpenStack PyCon T-shirt, and future marketing materials
  • The OpenStack Foundation reserves the right to final decision
  • The creator of the winning design will receive attribution on the T-shirt and public recognition on the OpenStack website!

Chairman’s Corner: Great 2013 to even Greater 2014

2013 was a very active year for the OpenStack board of Directors – and as a personal note, a very enjoyable year.  When the Foundation launched in September of 2012, the critics were troubled that the Foundation would be led by such a large board of 24 members.  Although 24 is large for a board, I am happy to report that the benefits have far outweighed any drawbacks. A large board has allowed many viewpoints, opinions and expertise to be shared, considered and included as part of the decision process. It has served the Foundation well because the board members are focused on the community, are very active and committed to the success of the Foundation.

Over 2013 many new board initiatives were launched. Through these efforts, you can be assured that the Foundation’s finances, trademarks and other assets are under excellent care. The benefits of which will continue to manifest themselves throughout 2014 resulting in additional qualified members, OpenStack Summit travel assistance, aligned training efforts, user experience, adoption and case studies.

As a board we are excited by the prospects that 2014 brings. There are many areas where we want to grow and improve the Foundation.  Those of high importance are the ones we gather directly from the community. A few topics that I’d like to highlight, were gathered recapped at the Breakfast with the Board at the Hong Kong Summit.

Membership Growth

2013 has demonstrated tremendous community growth. Many of the people we talked to at the Summit are fairly new members of the community. We were very pleased to hear that their community experience has thus far been positive. They are encouraged by the tone of the community and the talented people whom are engaged in the effort.  2014 is the perfect point in time to help all members discover ways to contribute their talents and to develop collaborative connections across the community.

Recognition for Contribution

We all enjoy doing something that serves a purpose. Contributing to the OpenStack project provides many ways to do something meaningful. We have a very vibrant community with people who are very dedicated and passionate about what they do.  They give it their best because they’re passionate about the project’s future impact on technology. Finding ways to highlight people for what they do, we help the project to fulfill its purpose and help provide an environment where work has meaning.

Core Definition

OpenStack is enjoying tremendous growth with the number of new projects and programs. While this makes it exciting to be part of OpenStack development, for those that are new and those looking in from outside of the community, OpenStack could begin to look unfocused or fractured. Growth demonstrates the need to convey the message that the core and integrated components are mature and stable while the new projects bring exciting innovation. In our messaging, we’ll balance new features with stability and upgradeability of the code, while ensuring diversity of and innovation around non-core projects and plugins. Throughout 2013 working together the board and TC have been tackling this topic, working toward implementation in 2014.

Individual Director Elections

Over the past year, the board has been evaluating and looking for ways to improve the Individual Director’s election process. Given the dramatic growth of the community, the desire for diverse representation and community participation, the board has been analyzing potential options to find an alternative process that is preferred by the membership and that meets the legal requirements. Community feedback from Summit attendees clearly indicates a need for additional in-depth education prior to the board taking any form of action on this topic.

When a project has experienced as much early success as OpenStack has, it can be a tempting prediction to believe the momentum will slow down. But I’m not betting on it. We at the Foundation board are committed to building on our momentum this year, and these are just a few of the many fun initiatives that the board will tackle during 2014 to do so.  OpenStack is a fun project and a great community.  2013 was a great year. 2014 is going to be even more exciting!

 

OpenStack 2014: Powered by Users

If momentum is any indication, 2014 is poised to be a defining year for OpenStack. All of our vital statistics, from community growth to code commits and tracked deployments, doubled in 2013, and all signs point to continued growth. Still, we continue to hear the questions:

Who’s really driving OpenStack?

Are there too many cooks in the kitchen?

What defines OpenStack, and do we need all of the new programs?

Where’s the voice of the user?

These points reflect the common question of how decisions are made in the OpenStack community. As we start a new year, we in the OpenStack Foundation are putting our resources behind elevating the voice of OpenStack users and tightening the feedback loop between users and developers to influence decisions such as the scope of the project, new feature priorities, interoperability requirements and operational best practices.

Balancing Voices In Software Development

Every foundational technology platform is driven by common forces: the developers who build it, users who consume it, and the ecosystem of vendors that extend it. OpenStack’s development process is unique because it is designed to allow all of these constituencies to directly influence the cloud platform.

In OpenStack, technical decisions – everything from new features to long-term roadmap – are governed by a technical meritocracy in which Program Technical Leads manage the involvement of developers and users in their programs under the oversight of a Technical Committee. The Board of Directors of the OpenStack Foundation, by comparison, focuses its attention on long-term policy, strategy and governance.

Each of these groups already includes representatives who are responsible for real-world OpenStack usage in their organizations, but we can benefit from even greater involvement from users. As we work to raise the level of user involvement, we see that some are simply not as comfortable with open source, but also that our process can be intimidating to dive in and get involved with so many people and moving parts.

The fact we often miss is that technology development is a messy process regardless of how decisions are made. Whether you’re talking about open source or proprietary software, deciding how to evolve a code base is beset by the same kinds of tradeoffs, optimizations and calculated gambles. In the end, your goal is to deliver software that solves a particular set of problems.

For OpenStack, the community chose an open process that relies on the disinfectant of transparency to maximize the chances that all points of view are heard, considered and when embraced by the community, incorporated into the code. How we make decisions in the OpenStack community is a source of strength.

Transparency Is Noisy

Of course, transparency by its very nature exposes the world at large to much more information, insight and noise than a tightly controlled process. A rapidly growing, global, diverse and passionate community of developers and users will disagree. That disagreement is often very useful even if it isn’t always going to be pretty.

But guess what? Because it’s an open process, you get to see it all and participate where you want to make an impact. Backroom and backchannel conversations are still present, to be sure, but their effect is kept in proportion. If you want to understand why particular technical decisions were made – as in the case of the networking stack, for example, with both Neutron and nova-network still present as options – it’s a relatively straightforward matter to find out. In that particular case, when you look, you’ll discover that users said they still needed features available in nova-network, so the deprecation schedule was extended to give Neutron additional time to meet their requirements.

Uncovering the decision chain in other open source projects isn’t always that simple. And with proprietary software, it’s virtually impossible, because the trail of communication from the end user goes through the sales or support organization to product management to the development team like a high stakes game of telephone. It’s a system that’s been in place for a long time, but there’s also a growing consensus that we can’t build software the way we used to.

Proprietary-vs-OpenStack

This level of transparency can be a distraction, and it sometimes makes for snarky, counterproductive and ill-informed side conversations. As we’ve seen in the past year, it can also lead to misunderstandings among the media and analyst communities covering OpenStack with regard to why decisions are made and where the project is headed. But messiness as a result of transparency is not our enemy. Our enemy is an opaque process with no accountability and responsibility to the people using the software.

Amplifying the User Voice in 2014

I have worked with many developers over nearly 20 years, and the ones who have built the best software had a passion for meeting the needs of their users. As we have ramped up the User Committee and put user input mechanisms in place, OpenStack technical leaders have been very enthusiastic about receiving this feedback. That work influenced improvements in the Havana and Icehouse development cycles, and will continue to do so in the Juno release and beyond.

Users bring valuable contributions to the project, whether they are directly contributing code, open sourcing their management tools, contributing to documentation, sharing operational best practices at user group meetups or capturing their experiences through the User Survey and Design Summit talks. In 2014, we are bringing several new initiatives to life to bring the voice of the user closer to our process to deliver the best cloud software:

  • Closing the Feedback Loop – The user and technical communities are working to close the feedback loop in the design and development process to make sure we are delivering user-driven features. Specific activities include an operator’s mini-session to gather input well before the Design Summit, beefing up the user survey with more specific feedback requests, and having more user representatives engage directly on technical mailing lists and in technical Summit sessions.
  • Ramping Up Support of Application Developers and Cloud End Users – A major focus this year will be moving beyond cloud operators to attract and support the growing community of app developers and OpenStack end users. Current projects underway include an aggregation of popular SDKs and developer resources for OpenStack clouds, as well as adding new survey questions for application developers, largely driven by community member Everett Toews. The Technical Committee is also considering how to incorporate a new program focused on user/consumer experience.
  • Establishing Baseline Interoperability Testing – The community is engaged in creating baseline interoperability testing for OpenStack products and open source distributions. Rob Hirschfeld and Joshua McKenty are leading a Board of Directors committee to drive this effort, and it’s important that we have operators and end-users engaged, especially as we work to create a consistent target a better experience for the latter.
  • Clarifying the Path to Adoption – With such a vibrant commercial ecosystem, and still many organizations who are running it themselves, one of the most common questions we hear is how to get started with OpenStack. The answer depends on many factors, including your use case and technology expertise, and this year the Foundation staff is helping users make sense of the many ways to consume OpenStack, expanding on efforts like the Training marketplace.
  • Growing Ambassador Program – Our community managers are also ramping up the global Ambassador program, which will empower more community members to get involved in these initiatives as well as through our traditional contribution channels. We now have 12 Ambassadors in eight countries.

This is of course not an exhaustive list, but they represent key activities in 2014, and now is the time to get involved, whether it’s completing a user survey, joining the interoperability testing efforts, or volunteering with the User Committee.

Pioneering a Better Way to Build Software

We in the OpenStack community are pioneering new ways to do collaborative software development at very large scale. We’re meeting our biannual release cadence, growing our base of contributors, and our testing and review process is already being emulated by other software projects. Reflecting on success is good, but there’s more work to be done.

In 2014, we are committed to bringing more users into our open and transparent process, helping them to participate directly in building great cloud software. When we balance the voices and contributors involved in all parts of OpenStack, we see the incredible power of a diverse community, focused in the same direction, driving change across our industry.

The OpenStack T-Shirt Design Contest Winner is…

In June the OpenStack Foundation launched its first T-Shirt Design Contest encouraging the community to help contribute to our collection of unique and fun shirt designs. Two months later it’s now time to announce the proud winner – Raul Chan!

Here is Raul’s design:

Winning T-shirt Design

Winning T-shirt Design

Raul is a 17-year-old student in Hong Kong, who is incredibly passionate about design. He’s been drawing, sketching and designing for a year now with the dream to become a graphic designer one day. You can check out his other designs on his Instagram account ,@d_raul.

Raul Chan

Raul Chan

When we asked what his inspiration was for the OpenStack design, he said “as I know that OpenStack is a cloud operating system which processed lots of data for many companies, I used the logo of OpenStack to form a ‘cloud’. Besides, different colors of the ‘cloud’ represent the diversification of OpenStack.” Raul isn’t very involved with OpenStack but became interested in it as it became increasingly popular in China.

Raul’s design will be featured on T-Shirts that will be given out at LinuxCon Cloud Open in New Orleans in September and at other events where OpenStack will have a presence later this year and in early 2014.

For his efforts, we’re sending him and his family several T-Shirts and a free ticket to the OpenStack Summit in Hong Kong. So say hello if you see him around!

PS: If you want to pen the next design that’ll decorate the OpenStack T-Shirts – look out for the 2014 T-Shirt Design Contest. We’ll be announcing it on the OpenStack blog and our other social media channels in the coming months.

Back to top