The OpenStack Blog

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!

Category: OpenStack Update, Uncategorized

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.

Category: OpenStack Update, Uncategorized

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!

Category: Contest, Newsletter, OpenStack Update

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!

 

Category: community, Newsletter, OpenStack Update

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.

Category: community, Newsletter, OpenStack Update

OpenStack Community Weekly Newsletter (Jan 17 – 24)

Icehouse-2 development milestone available

The second milestone of the Icehouse development cycle, “icehouse-2″ is now available for Keystone, Glance, Nova, Horizon, Neutron, Cinder, Ceilometer, Heat, and Trove. Including the oslo libraries, “only” 50 blueprints were implemented and about 650 bugs were fixed during this milestone, which is slightly less than our usual velocity at that point in the cycle. This is mostly due to the recent issues in gating and the end-of-year holiday season. The next development milestone, icehouse-3, is scheduled for March 6th.

Organizing a Gate Blocking Bug Fix Day – Mon Jan 27th

Developers may have noticed issues with our gate and in order to improve the situation Sean Dague proposed a Gate Blocking Bug Fix Day on Jan 27th. All developers are encouraged to focus on fixing bugs on the OpenStack CI infrastructure.

OpenStack Swift as backend for Git

The fine folks at Enovance have written about the advantages of using Swift as backend for Git. In a recent blog post they gave also some details about what happens in Git (server side) when a client pushes or fetches objects. They’ve now shared more operational details on how to handle Swift as a backend to store repositories.

Tips ‘n Tricks

By Andreas Jaeger: Python Virtualenv awesomeness – and developing openstack-doc-tools and Setting up gating in the OpenStack intrastructure

Upcoming Events

Security Advisories and Security Notes

Reports from Previous 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

Is your affiliation correct? Check your profile in the OpenStack Foundation Members Database!

Xav Paice Tapan
Donald Stufft Ralf Haferkamp
Zhang Yang Ken Pepple
Eli Klein Jerry Johnson
Gregory Haynes Gregory Haynes
Aaron Weitekamp Eric Brown
JiaHao Li Balazs Gibizer
tinytmy Trevor McKay
LeileiZhou Svetlana Dobogoeva
Joel Friedly Paul Nelson
Enol Fernández Mike Spreitzer
Maxim Kulkin John Speidel
Dima Shulyak IWAMOTO Toshihiro
lizheming Evgeny Fedoruk
Andrew Lazarev
Yuanhui Liu
Kaitlin Farr
Ronelle Landy
Matthew Fischer
Dieter P

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

polite

Jenkins giving me a -1 on my change

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

Open Mic Spotlight: James Slagle

slagleOpenMicThis post is part of the OpenStack Open Mic series to spotlight the people who have helped make OpenStack successful. Each week, a new contributor will step up to the mic and answer five questions about OpenStack, cloud, careers and what they do for fun. 

James Slagle lives in Boone, NC with his wife and 7 month old son. He enjoys outdoor activities like hiking, trail running, camping, and canoeing. He’s a Senior Software Engineer at Red Hat where he works primarily on the TripleO project for OpenStack. Follow him on twitter @slagle

1. Where is your happy place? Favorite place to visit, vacation, decompress?

The mountains of NC. We were lucky enough to be able to move there a couple years ago. The scenery, outdoor activities, colder climate, and rural area are just a few of the reasons we like it here. Some might say don’t move to where you like to vacation, because then it won’t be special anymore. But, we still feel like we’re on vacation every time we come home. Plus, I’m fortunate enough to be able to work from home. The view out of my office beats a parking lot any day.

2. If you couldn’t be a developer, what would your dream job be?

Can I only pick one dream job? :) I’d like to own my beer brewery someday. I enjoy spending time and working outdoors, so maybe a forest ranger. I like building things with my hands too, so maybe a wood worker. I also wouldn’t mind if my only job was to be a professional runner, so I could train competitively for the marathon or longer trail races. The good news is that, on a smaller scale, all of those jobs are my everyday hobbies. And, I love being a developer too, so in a lot of ways I already have my dream job.

3. What behavior has helped get you the furthest as a developer?

I think being fairly self-sufficient and not being afraid to dive into the code to figure out how something works or how to fix a bug. That is one of the main reasons that attracted me to open source software to begin with. Going right along with that is having the knowledge to know when the right time is to ask for help, so that you don’t get stuck or in way over your head.

4. What do you think is the coolest thing that’s happened with OpenStack over the past three years?

It’s growth and sustained momentum. As more people and companies contribute and remain participants, they’re learning for themselves what Openstack is and has to offer. That’s helping OpenStack to stand on its own merits since it’s the contributors and users who are helping spread the word. That reputation attracts even more new growth. The ease with which you can have an impact in the community, and learn for yourself what you can do with OpenStack, is much more valuable than simply reading someone else’s opinion on the matter.

5. How did you first get involved in OpenStack? 

I believe it was a patch to Horizon or Keystone, I can’t remember. I found that an easy way to get involved was to set up a development environment and find something you don’t like, a bug, or something you think can be improved. From there, I looked for a few bugs to fix on Launchpad. Once I had dabbled in OpenStack a bit, I knew it was something I wanted to work on full time.

Category: Open Mic

OpenStack Community Weekly Newsletter (Jan 10 – 17)

Election Results for Individual and Gold Directors

Each January two of the Foundation member classes hold elections to determine their Board representatives for 2014. The Gold Members held their election on January 6th-7th while Individual Members elected their Directors between Jan 12th-17th.

Today the 2014 election of Individual Directors has closed and the official results are in. The elected and appointed directors will be seated at the next board meeting, at 12:00pm PST on January 30th. Thank you to everyone who participated in this year’s Individual Director election and congratulations to our new and returning directors. The composition of the board is on OpenStack blog.

Atlanta Summit – Call for Speakers Open + Sponsor & Registration Info

Marching rapidly to our next big gathering: the OpenStack Summit will be held in Atlanta, Georgia May 12-16, 2014. The official page for Atlanta contains the latest announcements. The Summit is a five-day conference for OpenStack contributors, enterprise users, service providers, application developers and ecosystem members.  Attendees can expect visionary keynote speakers, 200+ breakout sessions, hands-on workshops, collaborative design sessions and lots of networking. Keynote sessions will take place Monday and Tuesday, the main conference will run Monday – Thursday. The Design Summit, a special track for active technical contributors to plan the next software release, will run Tuesday – Friday.

Where to ask question and find help OPW Experience with OpenStack Part 1

One of our awesome intern from the Outreach Program for Women (OPW) shares her experience towards solving a problem while getting stared with OpenStack.

Organizing a Gate Blocking Bug Fix Day – Mon Jan 27th

Developers may have noticed issues with our gate and in order to improve the situation Sean Dague proposed a Gate Blocking Bug Fix Day on Jan 27th. All developers are encouraged to focus on fixing bugs on the OpenStack CI infrastructure.

Tips ‘n Tricks

Upcoming Events

Security Advisories

Reports from Previous 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

Is your affiliation correct? Check your profile in the OpenStack Foundation Members Database!

Don Domingo Travis Tripp
Xiaolin Zhang RonenKat
Jorge L. Williams Guido Günther
Vahid Hashemian Eugeniya Kudryashova
Michael Krotscheck Ya Hong Du
Jerry Cai Thai Tran
Alexander Ignatov Khyati Sheth
Roman Rader Justin Pomeroy
Jeffrey J. Walls Doug Fish
Aditya Patawari lintan
Joris Roovers Sergey Reshetnyak
Guido Günther Cindy Lu
João Vale songqianxia
Roman Rader
Lance Bragstad
Khanh-Toan TRAN
Maithem
Dmitry Borodaenko
Nassim Babaci
Thiago da Silva
David Charles Kennedy

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

not_a_single_f.gif.pagespeed.ce.CRScJl-DfZ

Keep hitting “recheck no bug” in reviews

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

Election Results for Individual and Gold Directors

Each January two of the Foundation member classes hold elections to determine their Board representatives for 2014. The Gold Members held their election on January 6th-7th while Individual Members elected their Directors between Jan 12th-17th.

Today the 2014 election of Individual Directors has closed and the official results are in. The elected and appointed directors will be seated at the next board meeting, at 12:00pm PST on January 30th. Thank you to everyone who participated in this year’s Individual Director election and congratulations to our new and returning directors. The composition of the board will be as follows:

Individual Directors

  • Tim Bell
  • Yujie Du
  • Alex Freedland
  • Rob Hirschfeld
  • Vishvananda Ishaya
  • Mark McLoughlin
  • Monty Taylor
  • Troy Toman

Gold Directors

  • Simon Anderson
  • Randy Bias
  • Tristan Goode
  • Joshua McKenty
  • Boris Renski
  • Sean Roberts
  • Imad Sousou
  • Lew Tucker

Platinum Directors

  • Alan Clark
  • Eileen Evans
  • Toby Ford
  • Chris Kemp
  • Van Lindberg
  • Todd Moore
  • Brian Stevens
  • John Zannos

Category: Communication, community, Governance

Open Mic Spotlight: Jay Lau

JayThis post is part of the OpenStack Open Mic series to spotlight the people who have helped make OpenStack successful. Each week, a new contributor will step up to the mic and answer five questions about OpenStack, cloud, careers and what they do for fun. 

Jay Lau (Guang Ya Liu) is an Advisory Software Engineer at IBM CSTL. He is the Technical Leader of the IBM Platform Resource Scheduler project. He has 5+ years of experience in large scale distributed system, SOA and Cloud Computing. He joined the OpenStack community in 2013. Now, he mainly focus on OpenStack compute, storage and application management. You can follow him on Twitter at @jaylau513.

 

1. What behavior has helped get you the furthest as a developer?

I want to say it is interest and passion. OpenStack is really an amazing project and it makes me want to work for it anywhere, at any time, with any device that can access Gerrit ;-)

2. What is your favorite project that you’ve contributed code to?

Hmm, may I say I love all projects? ;-) To be honest, my current focus is nova, but also extending to cinder and heat.

3. How did you learn to code? Are you self-taught or did you learn in college? On-the-job?

If I want to lean code for a product, I will first get familiar with the key features of the product, and then think how the code will be written and then start to read and debug code. For OpenStack, you also need strong system technologies if you want to understand the code.

4. How did you first get involved in OpenStack?

When I first get involved in OpenStack for some research work in 2011, I set up a demo environment with StackOps and found that scheduler is very simple and weak in OpenStack. My company has a very good product named PRS (Platform Resource Scheduler) which is very good at resource scheduling. Hmm, you know how I start my journey on OpenStack then.

5. Define what “open source” means to you.

IMHO, “open source” means contribution and collaboration. Worldwide engineers from different companies collaborate together to contribute to create the best software. As a software engineer, “open source” can make us grow quickly in community.

Category: Open Mic

Back to top