The OpenStack Blog

Author Archive

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.

Welcome new Gold Members Aptira, Hitachi, and Huawei!

The OpenStack Board of Directors approved Aptira, Hitachi and Huawei as Gold Members of the OpenStack Foundation. The companies are based in Australia/India, Japan and China respectively, and range from a startup to established, multinational corporations.

The timing couldn’t be better in my view, given that we are having our first ever Summit in Asia this week with attendees from 50 countries, including many from Australia, Japan, India, and China. As OpenStack adoption continues to accelerate around the globe, I am excited to welcome these new companies to the Gold Member ranks.

Some Background on the new members:

Aptira is a services business that focuses primarily on consulting, integration and training for OpenStack. Aptira has been instrumental in building the OpenStack community in Australia and India by organizing user groups, promotional activities and offering training courses. The company open sourced much of its training material and is collaborating across the community on broader education efforts.

Hitachi’s JP1 systems management solution supports OpenStack, and they’ve contributed support for their Hitachi Unified Storage platform for OpenStack Block Storage. The company also sponsors community building efforts in Japan, including an OpenStack event happening in Tokyo, February 2014.

Huawei is a top 20 OpenStack contributor that has contributed a Block Storage driver to support Huawei storage solutions, as well as made broader contributions to OpenStack documentation and testing systems. Huawei has supported community building efforts in China, including organizing meet ups and conferences, publishing whitepapers and blogs, and sponsoring and promoting the Summit this week.

Now let’s give each of the contributors from these companies a proper stacker welcome in Hong Kong this week!

@sparkycollier

 

OpenStack Summit Survey Results

As we gear up for the next OpenStack Summit in Hong Kong, and look forward to two more Summits in 2014, it’s a good time to take a look at the feedback from the April 2013 Summit in Portland.

We surveyed all Portland attendees, and almost 400 people responded. In this post I’ll break down some of the key findings and highlight a few changes we’re implementing in Hong Kong and beyond.

TL; DR Key Findings:

  • Overall: 96% of people rating the overall Summit as Good or Excellent. 
  • Top areas to improve:  Clearly the Network and the Session Rooms (size, acoustics, equipment) were unacceptable.
  • Format: Stackers favored keeping the Design Summit co-located with the rest of the Summit sessions by a margin of 4:1 over breaking it out separately

Ratings:

ChartExport

Regarding the “Session rooms” (size, acoustics, equipment), I attribute most of this to crowding issues, but there were also some technical glitches with the presentation equipment.

The Format Question:

ChartExport (1)

Among Active Technical Contributors (ATCs), who make up the majority of Design Summit attendees, the results were similar, but with more interest in making some change to the format. That said, keeping the overall event together was still preferred 2.5:1 over breaking it out completely:

ChartExport (2)

 

While the current format is the clear “winner” in the survey, there is always room for improvement.  Over the past 6 summits, we’ve had the most success when making incremental changes rather than completely overhauling the format.  Given the results of the survey, including the 96% rating of “Good or Excellent” I think this approach continues to make the most sense.

There were two free form questions, so I picked a few choice quotes:

“What did you find most valuable about the Summit?”

  • “The ability to get a large amount of information on OpenStack projects, progress, ideas, walkthroughs, and case studies, in a relatively short amount of time. Much better than web-based because it gets folks out of the office and thinking more constructively and creatively about OpenStack, and more passionate about it. This was my first summit, and attending it truly invigorated and greatly amplified my interest and enthusiasm in OpenStack in general.
  • “People, from all different backgrounds – both “world”-wise and Openstack-wise.”
  • “It was my first, so I was just racing from one talk to the next trying to soak up as much knowledge and personal connections as I could.”
  • “Workshops I attended & being able to speak with others who are right in the mix of OpenStack…”
  • “Hands-on labs and real world implementation strategies in the operations summit.”
  • “The fact that customers are now starting to show up at this summit is exciting.”
  • “To be able to finally meet people who I met on IRC and participate in design sessions. To be able to talk to customers.”

“What is the biggest area of improvement you see for the next Summit?”

  • “I think some logistics could improve; better wi-fi or even wired touchdown spots would be nice, since many of us need to keep working even as we’re enjoying the conference, and better sizing of the rooms to the presentations. Also the bag check idea I think would be excellent since the conference was not co-located with hotel. But overall a very well-run conference with lots of great content!”
  • “Removing barrier for non-native English speaker. They can do tremendous jobs in spite of their poor English.”
  • “Make sure participants can continue to ‘mingle’ while the number of attendees continues to grow…”
  • “1. Provide breakfast again :) 2. One evening event that accommodates all summit attendees 3. Better communication around the design sessions so they are not packed with non-ATCs.”
  • “- IRC nicks on badges – Better wifi, maybe have an on-site etherpad server since chunks of session time was lost to etherpad connection issues – Cold drinks available on site all day – don’t mind paying but never have time to go far – Conference being away from the hotel meant jetlag hurt more since going for a short nap was difficult”
  • “More seating!”

Planned actions for Hong Kong:

  • Network: We participated in a debrief with the networking company and are planning to evaluate additional vendors for Hong Kong, as well as engage with other organizations who have hosted conferences at Asia World Expo to learn more about their experience and any unique requirements we should be prepared for.
  • ATC Designation: We’re planning to make the ATC designation more clear and recognizable on the badges and include IRC nicknames. We’re also communicating that ATCs should register for the Summit with the email tied to their Gerrit ID in order to receive ATC designation on the badge.
  • Capacity & Crowding: In Hong Kong we are limiting “Full Access” passes – people who can attend the breakout sessions and Design Summit all four days — to a reasonable capacity based on room sizes, and offering a “General Session & Expo” pass with one track running Tuesday & Wednesday to better manage our growing base of attendees. Also, the “curtained off” area for the Design Summit received positive feedback in Portland and is a model we’ll pursue again for Hong Kong.
  • Design Summit Productivity & Scheduling: It has been proposed to move the PTL “project update” sessions to a series of webinars post-Summit, so they won’t conflict with Design Summit sessions, PTLs will have a chance to gather thoughts/feedback from the Summit and more people will have the opportunity to participate and ask questions online. ATCs were fairly split on having an additional moderator participate in the Design Summit sessions to help manage the room, slightly favoring bringing on the moderator.  Both of the topics are still under discussion. Regardless, we can take steps to more clearly identify “Design Summit” sessions within the online schedule and help educate Design Summit session leaders and attendees with best practices for a productive session.
  • Food & Drinks:  We will not be able to provide breakfast at the event in Hong Kong, but many of the hotel room blocks and budget-friendly recommendations offer free breakfasts. We are requesting healthier snacks for the developer’s lounge, per feedback from several developers, and we’re also planning to offer larger, reusable water bottles instead of the small plastic cups.

For 2014 Summits, we would like to continue evaluating the format, and considering the possibility of starting the Design Summit a day early (or ending a day later) relative to the other content, to reduce the scheduling conflicts for ATCs.   The data doesn’t scream out for this change, but I don’t want to dismiss it yet either for 2014.

Please keep the feedback coming! And start making plans for Hong Kong now!

@sparkycollier

 

Welcome Heidi, Margie, Jeremy, and Tom to the OpenStack Foundation team!

Since the Foundation launched last September, we’ve continued to build out a diverse team. This has been a big focus to keep up with the incredible growth in the OpenStack community with another new software release (Grizzly), the Portland Summit with over 2600 people (double San Diego!), and the start of the work to organize the first international Summit in Hong Kong (expecting over 4,000 people).

To keep up with such amazing growth, we expanded the team with new roles to drive adoption of the software, support the development process and grow the OpenStack ecosystem. Heidi Bretz joined as Director of Business Development, Margie Callard as Marketing Manager, Jeremy Stanley as Infrastructure Engineer and Tom Fifield as User Community Manager.

Heidi joined prior to the Summit in Portland and has been quickly getting to know the companies in our ecosystem, so many of you may have already met her. She comes from Amazon Web Services, where she worked to build a successful ecosystem around Mechanical Turk. She has vast experience building relationships with partners while working for AWS, Microsoft, Netscape, and Red Herring.

Margie is covering a wide range of marketing activities for the Foundation, including analyst relations and content development, driving many of the OpenStack user stories found at openstack.org/user-stories. She joined the Foundation from Internap, where she was first became involved in the OpenStack community marketing their cloud products.

Jeremy is supporting the continuous integration systems and infrastructure for the OpenStack developer community as a core member of the Infrastructure Team, assisting with security vulnerability management for the OpenStack  project. You can find him on IRC #openstack-infra, his nickname is fungi.

Tom Fifield is the most recent to join as User Community Manager, focused on helping users be successful with OpenStack, working closely with our other community manager Stefano Maffulli who many of you already know. Tom is a known name in the community as he’s one of the authors of the OpenStack Operations guide and the architect of one of the earliest (and largest!) OpenStack implementations. He currently lives in Australia, speaks Mandarin and has familiarity with Japanese. He and Stefano will split the tasks necessary to keep fueling the OpenStack community’s growth from the perspective of adoption and development of the product. With 100 user groups around the world, hundreds of individual developers and companies contributing to OpenStack there is lots that needs to be done. Please hang out on IRC #openstack-community to say hello to Tom: his nickname is fifieldt.

I hope to see all of you at the Summit in Hong Kong this November!  Next week we’ll begin accepting speaking submissions, as well as selling tickets and sponsorships.

@sparkycollier

OpenStack Grizzly

Today OpenStack’s 7th release, called “Grizzly”, will be released. and I just want to thank the over 500 stackers who contributed and the many more who participated in the OpenStack Summit last October where this release was planned.  This release, more than any before it, was driven by users who have been running OpenStack in production for the past year (or more) and have asked for broader support for the compute, storage, and networking technologies they trust and even greater scale and ease of operations.

On the compute side, we saw innovations for those operating at massive scale like “Cells” to manage distributed clusters and “NoDB” to reduce reliance on central databases, as well as big improvements in virtualization management with full support for ESX, KVM, XEN, and Hyper-V.

In the storage world, quotas were added to the object storage system as well as Cross-origin resource sharing (CORS) to enable browsers to talk directly to back-end storage environments.  And in block storage land, 10 new drivers were added including Ceph/RBD, Coraid, EMC, Hewlett-Packard, Huawei, IBM, NetApp, Red Hat/Gluster, SolidFire and Zadara, while the system itself became much more sophisticated with an intelligent scheduler for allocating the right class of storage for each workload, such as for performance, cost or efficiency.

Networking is an area everyone is talking about (and investing in), and with Grizzly their was a focus on achieving greater scale and higher availability by distributing L3/L4 and dynamic host configuration protocol (DHCP) services across multiple servers. A new load-balancing-as-a-service (LBaaS) framework and API will bring another wave of investment and innovation in the coming months.  To deliver on the choice users are demanding,  we saw new plugins from Big Switch, Hyper-V, PlumGrid, Brocade and Midonet in addition to the existing support for Open vSwitch, Cisco UCS/Nexus, Linux Bridge, Nicira, Ryu OpenFlow, and NEC OpenFlow.  And many others are releasing plug ins now, including Arista, Extreme Networks, Ruijie, and Mellanox. Exciting time as we explore the final frontier of the software defined datacenter!

Since the Dashboard is all about UX, I recorded a short demo in place of a write up:

Some other helpful links:

  • Thierry posted to the openstack-announce mailing list with additional info and links here.
  • You can read more about the new features on this new Grizzly page.
  • Read the Grizzly Release Notes
  • Blog Post from Aaron Rosen:  Building a multi-tier application with openstack (highlights some exciting new features like LBaaS)
  • The folks at Bitergia once again did some great work analyzing the contributions and blogged about it today.

If you’re already a user, don’t forget to make your voice heard by taking this user survey and by attending our next OpenStack Summit in Portland April 15th-18th.  We fight for the users!

@sparkycollier

 

 

 

October 2013 Summit: Where should we have it?

As we announced at the October 2012 Summit, we will be holding the October 2013 Summit outside of the U.S. for the first time, either in Europe or Asia.

The OpenStack Foundation seeks site proposals for the October 2013 Summit.  The deadline to submit is January 25th, 2013.

Following the announcement in October, we were contacted by officials from the Paris region, who have been extremely helpful in providing guidance and are making a strong case for holding the event in the region.

We would love to hear from anyone else who has a strong interest in bringing this important event to their region, whether from a government economic development office, or a private company with significant resources in the region.  Open source in general, and OpenStack in particular, are powerful forces for economic development and job creation, with hundreds of job openings related to OpenStack right now, and start ups getting funded on a regular basis.

Keys to include in any proposal:  1)  Venue options that can accomodate our requirements (see below), 2) Any potential economic help to offset event production costs 3) Identify local sponsors that are likely to bring additional resources as we get close to the event 4) Anything and everything that’s unique about your city or region, making it the perfect fit for our community.

Event Overview:

  • 4 day event (Monday-Thursday)
  • Dates:  First choice is October 14 – 17, second choice is October 21-24 (we’ll also need access to the venue a few days before and after the event for load in/out)
  • Expected Attendance:  1500-2000
  • Network Connectivity: Access to reliable Internet connectivity is required. If infrastructure is prepared for high speed, upgrade can be accomplished. Desired speed is 50Mb down, 5Mb up.
  • Food & Beverage: Need to be able to serve breakfast & lunch for 1500 – 2000 people.

Space & Room Requirements:

  • City Preference:  Near a major international airport with direct flights from major hubs.
  • General Session: One room to seat 2000 theater style with space for stage with rear projection
  • Breakout Sessions | Four rooms: Each rooms should seat 250 theater style with room for smaller stage and screen (no rear projection)
  • Design Summit | Five rooms (can be separated from the rest of the space): Each room should seat 100-150 semi-circle theater style, square rooms are better, will have screens and projector but no stage
  • Developer’s Lounge: Desired size is 2,000 sq. ft. to 2,500 sq. ft space, approximately 185m2 to 235m2 to accommodate lounge area (Cushioned Chairs, Couches, etc.)
  • Dining Area: Should seat 750 round tables of 10, with buffet and refreshment space
  • Sponsorship Area: Desired size is 10,000sq feet, approximately 930m2 to accommodate. The dining and sponsorship areas can be in the same space.
  • Special Event Room: Should fit 30-40 people classroom-style with a projector
  • 8-10 Meeting Rooms: Should fit 10-12 people in a boardroom-style setting

Please send proposals to [email protected]The deadline is January 25th, 2013.

Mark Collier
COO, OpenStack Foundation
@sparkycollier

OpenStack At Cloud Expo 2012 West

The OpenStack Foundation is the proud Diamond Sponsor of Cloud Expo 2012 West! If you’re in California for the event this week, please join the Foundation and the many members of the  OpenStack Community in attendance. If you can’t make it, follow the developments via twitter and of course follow openstack on twitter for general OpenStack information.

Already this morning, we’ve seen some big OpenStack news, including two announcements from RightScale regarding their sponsorship of the OpenStack Foundation and their partnership with Rackspace, and the acquisition of OpenStack supporter Vyatta by another recent OpenStack supporter (and Foundation Sponsor), Brocade. We also have some big OpenStack users speaking at the Summit this week, including Cisco WebEx, eBay and PayPal.  As the conference continues, I’m sure there will be other interesting developments.

Below you’ll find a list of OpenStack sessions to attend, and don’t forget to visit the OpenStack booth to learn how your organization can plan and implement successful, effective cloud environments.

You can also visit openstack.org/start to get started down your own OpenStack path today, and openstack.org/join to join the Foundation.

Monday, November 5

Opening Keynote: Open Cloud – Place Your Bets!

  • Jonathan Bryce, Executive Director, OpenStack Foundation 12:30-1:15pm, General Session Room – Ballroom A-H

Case Study Session: Open Cloud at PayPal

  • Saran Mandair, Sr. Director, and Anand Palanisamy, Architect/Technical Lead, Infrastructure Engineering, PayPal 2:10-2:55pm, General Session Room – Ballroom A-H

Conversation, demo and information

  • OpenStack and Community representatives
Welcome reception, Expo Hall, OpenStack Booth #603; 10:00am-12:30pm and 3:00-6:00pm

Tuesday, November 6

OpenStack Folsom demo

  • Jonathan Bryce, Executive Director, OpenStack Foundation Demo theater, Expo Hall booth #853; 11:00-11:20am

Conversation, demo and information

  • OpenStack and Community representatives
Expo Hall, OpenStack Booth #603; 10:00am-12:30pm and 3:00-6:00pm

Wednesday, November 7

General Session: Powered by OpenStack User Panel

  • Panelists from Cisco WebEx, eBay and PayPal, moderated by Chris C. Kemp, CEO, Nebula 11:45am-12:30pm, General Session Room – Ballroom A-H

Breakout Session: Making Money in the OpenStack Ecosystem

  • Boris Renski, Co-founder and COO, Mirantis 2:10-2:55pm, Room M1

Conversation, demo and information

  • OpenStack and Community representatives
 Expo Hall, OpenStack Booth #603; 10:00am-12:30pm and 3:00-6:00pm

Thursday, November 8

Conversation, demo and information

  • OpenStack and Community representatives
Expo Hall, OpenStack Booth #603; 10:00am-12:00pm and 2:30-5:00pm

OpenStack Community At Cloud Expo 2012 West

Please attend these sessions from the OpenStack Community!

Sessions by OpenStack members, sponsors and supporters Akamai, AT&T, Broadcom, ComputeNext, Dell, enStratus, HP, Intel, New Relic, Nimbula, OW2, Red Hat, SoftLayer, SUSE, UShareSoft, VMware, and Vyatta are also scheduled.

Keynote: The Ever Changing Cloud

Lew Tucker, Cisco; Thursday November 8, 9:05-9:50, General Session room

How Private PaaS Can Take You From Code To Cloud In 45 Minutes

Diane Mueller, ActiveState; Wednesday November 7, 2:10-2:55pm, Lafayette room (Hyatt)

Elastic Cloud Infrastructure: Why the Enterprise Wants It

Troy Angrignon, Cloudscaling; Thursday November 8, 1:40-2:25pm, Room M2

OpenStack Momentum: Adopters Speak Up

Mike Fountaine, Dell and Bennett Bauer, DreamHost; Wednesday November 7, 2:10-2:55pm, Stevens Creek room (Hyatt)

CEO Power Panel: There’s No Business Like the Cloud & Big Data Business!

Chris C. Kemp, Nebula, Inc.; Tuesday November 6, 7:00-7:30pm, General Session room Interacting with a Cloud

Gabriel Hurley, Nebula, Inc.; Tuesday November 6, 6:10-6:55pm, Room M1

Beyond the Hype: Understanding Cloud Security for Your Application
Bryan D. Payne, Nebula, Inc.; Wednesday November 7, 5:10-5:55pm, General Session room

Cloud Application Black Magic

Wayne Walls, Rackspace; Monday November 5, 2:10-2:55pm, Lafayette room (Hyatt)

This is Your Career. This is Your Career on OpenStack

Niki Acosta, Rackspace; Monday November 5, 4:25-5:05pm, Room M1

Scaling the Cloud

Brian Jawalka, Rackspace, Monday November 5, 5:10-5:55pm, Lafayette room (Hyatt)

Keynote: An Open Cloud Discussion

John Engates, Rackspace; Tuesday November 6, 9:05-9:50am, General Session room

Network Virtualization – Amplifying the Power of Cloud Computing

James Meredith, Rackspace; Tuesday November 6, 2:10-2:55pm, Room M2

General Session: The IT Talent Shift – Preparing Your Enterprise IT Talent for the Cloud

Lisa Larson, Rackspace; Wednesday November 7, 9:55-10:40am, General Session room

Storage Performance in the Cloud

Nelson Nahum, Zadara Storage; Monday November 5, 5:10-5:55pm, Room M3

OpenStack In The Expo Hall

Please visit the following booths for more information on how the Community supports OpenStack software:

Platinum and Gold Members

AT&T 921

HP 421

Rackspace 301/309

Red Hat 509

SUSE 715

DreamHost 926

VMware 209

Supporters

ActiveState 1020

Akamai 514

Cloud Cruiser 829

Cloudscaling 922

New Relic 415

OW2 915

SoftLayer 201

Vyatta 609

Zadara Storage 732

 

Mark Collier

COO, OpenStack Foundation

@sparkycollier

Join The OpenStack Foundation

We’re excited to announce that we’ve reached a huge milestone in the process to establish the OpenStack Foundation.  Individual Members can now join and begin making important contributions like nominating board members: http://openstack.org/join  (It’s free!)

Thanks to the hard work of the drafting committee (led by the amazing Alice King), we now have a complete set of legal documents. Our Bylaws, with appendices, and Member agreements are now posted online on http://www.openstack.org/legal/.

As a community we’ve really pulled together, made some tough decisions, and I couldn’t be prouder of the result.  It’s hard to believe, but OpenStack just started 2 years ago (with the first release of software, the “Austin” release, in October 2010).  OpenStack seems to have struck a chord, and I think the core values of our community have everything to do with it.  We’ve taken great care to preserve and promote those core values.  Everyone should be extremely proud!

On Tuesday the fine folks at OSCON put on an amazing “OpenStack Day”, and last night those who were lucky to be attending OSCON gathered together to discuss the Foundation progress and start signing up as individual members.  It was quite an amazing feeling to see so many familiar faces, but also meet so many new people interested in OpenStack.

Individual contributors, here are steps you can now take to secure representation in the OpenStack Foundation:

  1. Join as an Individual Member: OpenStack.org/join by August 15
  2. Nominate an Individual for the Board of Directors: Send nominations to [email protected] by August 6 (candidates require 10 nominations to appear on the ballot)
  3. Vote for Individuals to be on the Board of Directors: Elections take place August 20-24

To provide more context, the following is a full list of key dates and milestones through the formation of the Foundation:

  • July 18 – Initial Platinum, Gold & Individual membership sign up period opens
  • July 18 – Nomination period for Individual member board directors opens
  • August 6 – Nomination period for Individual member board directors closes
  • August 15 – Initial Platinum, Gold & Individual membership sign up period closes
  • August 20-24 – Gold & Individual Board director elections
  • August 27 – Initial Board meeting via teleconference – operational setup
  • October 15 – First regular quarterly Board meeting at OpenStack Summit

Thank you so much to everyone who helped us reach this milestone!

Mark Collier

@sparkycollier

OpenStack Summit Fall 2012: Tickets & Sponsorships now available

The OpenStack Summit is coming to San Diego October 15th-18th at the Manchester Grand Hyatt . Check out the new Summit website to learn more, buy tickets, or to become a sponsor.

This time we’ve set aside 4 days (Monday-Thursday) with “Design Summit” tracks running in parallel with other presentations and discussions, and have a single registration system.  On Friday, we are organizing a volunteer day to benefit a local charity (details TBD) so try to stick around through Friday and give something back to our host city.

The early bird price for tickets is $400 until August 31st, then it goes up to $600, so please buy your ticket now!  Sponsorships are also selling out quickly, so review the options here and contact [email protected] with any questions.

Also please take advantage of the discounted room rate of $199 before the room block is sold out by booking with this link: http://bit.ly/sandiegohyatt

The Hyatt is going to be a great venue for our event.  See you in San Diego!

 

 

OpenStack Foundation Update

We’ve come a long way since announcing in October in Boston that we planned to create an OpenStack Foundation in 2012. We set out to solicit as much feedback as possible (and on the second day, there was a town hall) and to participate in as many open forums as possible (mailing lists, webinars, meetups, and in person meetings).

At the start of the process, Jonathan Bryce and I spent the first couple of months learning as much as we could about successful open source foundations, like the ASF, Eclipse, and the Linux Foundation, reading foundation meeting minutes into the wee hours of the morning. We also talked to a lot of lawyers to get advice on legal structures, and received feedback from many of the folks in the community. We entered 2012 with a heck of a lot more knowledge and a good sense of what proposals to put forward (borrowing heavily from these amazing trailblazers before us!) that would best fit the “OpenStack Way.”

Since then we’ve had active mailing list discussions, held several webinars, meetups, and published a ton of stuff on the wiki, culminating in a Mission, Structure, and Funding Model that stay true to our values as a community, including:

  • An open development process that is driven by technical meritocracy
  • Making significant investments in community building and driving awareness and adoption
  • Encouraging the development of a healthy and profitable ecosystem of companies powered by OpenStack

Last month, as that framework started coming into focus, we published a “Framework Acknowledgement Letter” and asked companies to sign it if they agreed with the approach and were intent on joining as Gold or Platinum members once formed. Today are are very excited to announce that nineteen companies have signed the letter:

  • Platinum: AT&T, Canonical, HP, IBM, Nebula, Rackspace, Red Hat, SUSE
  • Gold: Cisco, ClearPath, Cloudscaling, Dell, DreamHost, ITRI, Mirantis, Morphlabs, NetApp, Piston Cloud Computing, Yahoo!

What’s Next?
We are now forming a Drafting Committee, to take the framework and turn it into legal documents, with the help of legal resources from the above companies. The Drafting Committee process and timeline is outlined on the wiki, and they will be publishing drafts for community review & input, with a goal of getting to a final draft in Q3. The committee will not be making decisions in a vacuum, they will be putting the framework into long form legalese for all of us to review and comment.

I don’t think it’s a stretch to suggest that cloud computing will one day power our global economy, and that means there is a lot at stake. Seeing the caliber of companies putting serious resources into making OpenStack successful, who all believe deeply in the open development model, I am more optimistic than ever it will be an open future, powered by OpenStack.

Here are a few related posts about today’s announcement from participating companies

In closing, I’ll leave you with the mission we are excited to pursue when the foundation is formed later this year:

The Foundation Mission: The OpenStack Foundation is an independent body providing shared resources to help achieve the OpenStack Mission by Protecting, Empowering, and Promoting OpenStack software and the community around it, including users, developers and the entire ecosystem.

Mark Collier

@sparkycollier

Back to top