OpenStack Community Weekly Newsletter (Aug., 22 – 28)

IMPORTANT + TIME SENSITIVE:

Mastering containers with OpenStack: a white paper

As containers gain major ground, a new white paper from the OpenStack Foundation highlights how to succeed with them.

Dive in deep with a new book dedicated to Trove

Ahead of Trove Day, the authors of the first book on OpenStack’s database-as-a-service talk about common errors and getting started with contributions.

The Road to Tokyo 

Reports from Previous Events 

Deadlines and Contributors Notifications 

Security Advisories and Notices 

Tips ‘n Tricks 

Upcoming Events 

Other News 

The weekly newsletter is a way for the community to learn about all the various activities in the OpenStack world.

OpenStack Community Weekly Newsletter (Aug., 15 – 21)

Make your cloud sing with OpenStack’s Community App Catalog 

The Catalog can get you rocking with containers in just a few clicks – how it’s evolving and how your feedback can shape its future.

The Road to Tokyo 

Reports from Previous Events 

Deadlines and Contributors Notifications 

Security Advisories and Notices 

  • None this week

Tips ‘n Tricks 

Upcoming Events 

Other News 

The weekly newsletter is a way for the community to learn about all the various activities in the OpenStack world.

OpenStack Community Weekly Newsletter (Aug., 8 – 14)

OpenStack continues to strengthen its commitment to interoperability

The latest on interoperability, Neutron, RefStack and how you can shape what’s next.

Jumpstart your OpenStack know-how with Upstream Training

Join experts for this free, fast-track course that combines work with play.

The Road to Tokyo

Reports from Previous Events

  • None this week

Deadlines and Contributors Notifications

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

The weekly newsletter is a way for the community to learn about all the various activities in the OpenStack world. 

Technical Committee Highlights August 11, 2015

This week, the Technical Committee will not hold the regular Tuesday meeting. Here’s a round up of the discussions and decisions from the last week or so. Let us know how these posts are working for you by emailing, tweeting, commenting, or finding us on IRC.

Midway focus points for the TC

“Technical discussions are like lasagna. You need to layer ML threads and IRC discussions to reach consensus.” – Thierry Carrez

Thierry challenged us to think about the “hard problems” we mean to solve this release as a technical community leadership body, so we discussed for a half hour this past week. The service catalog specifically came up and we also talked about cross-project specifications generally. It’s difficult to get exact assignees for cross-project specs, and we also discussed the communication channels we have for cross-project work. Currently it’s the mailing list, IRC, and the weekly cross-project meeting along with a special summit track just for cross-project work.

Should we, could we move the day/time of the cross-project meeting for better communications? Originally it was set up after the TC meeting as a convenience for chairs and attendees alike, but it seems like we could get a wider attendance rate by moving it earlier in the day. I know that moving to earlier does not help our New Zealand or Australian members, but comments from both the East coast US and Europe mention they currently find it tough to attend regularly.

Current tags under discussion

In the big tent, projects may be at a different pace of development. As a result, projects have different priorities that cause tradeoffs in speed or innovation. The pace and priorities can cause deprecation of a configuration option or API feature or other capability within a project.

Deprecation policy tags under review intend to communicate assertions that projects commit to whether they would purposely deprecate user-visible features and APIs and if they would deprecate, under which predictable conditions. Providing this tag should help determine how to mitigate any risk factors for adoption as it provides a key factor in assessing a given project maturity.

Different teams are trying out different approaches to the release process, and these also are tags under review for release tagging, and size of the team indicators.

All these tags intend to provide essential bits of information to give users and deployers evaluation criteria while also giving projects an idea of what measures are applied to their work.

Stackforge and renames of overarching organization

The passing of the Stackforge namespace retirement means no projects will be added to the stackforge namespace. Look for more specific communications and how-tos from the Infrastructure team about what this means for current projects in the stackforge namespace. They are working hard to ensure transition plans are in place.

Debian packaging team

The Debian packaging team led by Thomas Goirand continues to focus its mission to have the packaging Git repositories for Debian hosted in the /openstack git namespace.

 

OpenStack Community Weekly Newsletter (Aug., 1 – 7)

Inside the hive: the latest OpenStack Community Activity Report

From April to June 2015, there’s been an uptick in active core reviewers.

The Road to Tokyo

Reports from Previous Events

  • None this week

Deadlines and Contributors Notifications

Security Advisories and Notices

  • None this week

Tips ‘n Tricks

Upcoming Events

Other News

 

The weekly newsletter is a way for the community to learn about all the various activities in the OpenStack world. 

OpenStack Community Weekly Newsletter (July 24 – 31)

OpenStack: the platform for VMs, containers, and the next big thing

Jonathan Bryce, OpenStack Foundation executive director, on the state of the stack heading into OpenStack Silicon Valley, August 26-27.

25 Years of OpenStack—Looking Back From the Future

Well, here we are again. It’s 2035, and it’s time for another OpenStack anniversary post. Can you believe it’s really been 25 years since OpenStack began? Back then OpenStack wasn’t the ubiquitous juggernaut it is now, of course. There were even people who questioned whether it would ever catch on at all!

The Road to Tokyo

Reports from Previous Events

Deadlines and Contributors Notifications

Security Advisories and Notices

Tips ‘n Tricks

Upcoming Events

Other News

OpenStack Reactions

    starting to write a long spec for an OpenStack project

starting to write a long spec for an OpenStack project

The weekly newsletter is a way for the community to learn about the various activities in the OpenStack world.

Technical Committee Highlights July 24, 2015

Welcoming a common project for improving OpenStack user experience

We accepted a proposal for a new UX Program whose mission is to support and facilitate cross-project efforts to improve the overall user experience of OpenStack. I personally find this as exciting an effort and innovative as cross-project documentation in open source. Congratulations to this team and welcome! We look forward to great collaborative and open efforts across multiple projects.

Starter kit suggestions change

With much discussion the TC decided to change the compute starter kit tag applications slightly by adding the neutron project as the networking solution and removing the cinder project as a block storage solution since starter clouds could have ephemeral storage and then add block storage later.

New team for RPM packaging

A new team has been approved to manage all packaging git repos for RPM-based distributions in the /openstack git namespace. This team will enable gate testing and reviewing of changes
to the packaging close to the actual OpenStack development. The co-Project Team Leads are Dirk Mueller and Haikel Guemar. This team offers packaging for SUSE, openSUSE, Fedora Linux, Red Hat Enterprise Linux, or CentOS.

Stackforge resolution

Proceeding from our discussions about retiring Stackforge, we have continued to revise the resolution while still wanting to find a way to alleviate the extra work of organization renaming. The current proposal is instead of retiring the Stackforge project, we simply move all Stackforge projects into the “openstack/” namespace and create new projects there as well. Then as projects become official OpenStack projects, no repository renames are necessary.  Essentially, this means the “openstack/” namespace will no longer hold only official OpenStack projects, but also any project being developed in our community-driven shared development environment.  This should be a lot less disruptive to developers, users, and system administrators.

M naming quest resolved

The M release is Mitaka, say it three times fast! Mitaka, mitaka, mitaka. And if you can write the second character in the name, 三鷹, color me impressed!

Service names and project names

In an insane quest for consistency and ability to write about each service in a sensible way, TC member and documentarian Anne Gentle has proposed a set of guidelines for projects and services names, even for those services that have been around a few years. After consulting with the legal team and technical editors alike, please review the proposed guidelines and take a look at examples of possible new names with the new guidelines applied:

  • Object Storage -> Object storage
  • Block Storage -> Block storage
  • Image service-> Image
  • Database service -> Database
  • Bare metal service -> Bare metal
  • Key-Value Store as a Service -> Key value storage
  • Message Broker Service -> Message broker

Please take a look and comment on the reviews so we can discuss and look at various examples.

Introducing deliverables defined across repositories

We have discovered during testing across projects that often deliverables we produce
as a single “thing” may be represented by multiple code repositories. For example, a Networking release from the neutron team is actually made of openstack/neutron and openstack/neutron-lbaas and other gatherings from neutron-*aas. A release from the “sahara” team for the Data processing service  is actually made of openstack/sahara, openstack/sahara-extra and openstack/sahara-image-elements. Those repositories are all released at the same time with the same version number, and published together as a single “deliverable”. We want to ensure that the projects.yaml file indicates
the collection. It makes also sense to apply the “tags” we define at that user-visible layer, rather than at the (technical) git repository layer.

Tags:

OpenStack Foundation Staffing News

The OpenStack community continues to grow, and the OpenStack Foundation has been hiring to help support many exciting new initiatives and activities as we drive cloud innovation, adoption, and interoperability. New hires in 2015 include:
  • Wes Wilson, Lead Designer, joined late January and has been working on Todd Morey’s team to help build out OpenStack.org and manage other design initiatives. You can check out his awesome work in the /enterprise and /summit sections of OpenStack.org.
  • Danny Carreno, Ecosystem Account Manager, joined Heidi Bretz’s business development team in May and is helping support our growing ecosystem. Danny is passionate about helping startups succeed, coming from his previous role where he helped build startup programs and community for Rackspace public cloud.
  • Heidi Joy Tretheway joined the team in July as Sr Manager of Marketing with a focus on branding, content campaigns and growing participation in the marketing community. She looks forward to collaborating with marketing members at companies throughout our ecosystem. She previously led marketing communications at mobile software company Urban Airship.
  • Kendall Waters recently graduated from St. Edwards University and was a part-time intern for the Foundation during the first half of 2015. She joined the team full time as a Marketing Associate in June, and is part of Claire Massey’s team focused on Summit organization and execution.
  • Jay Fankhauser, currently at Baylor University, is our newest marketing intern, and is primarily helping Allison Price with Superuser Magazine and social media / web analytics.

The bus is filling up, but we still have a few seats left! Come join us!

You can learn more about the full team at http://openstack.org/staff. And we’re still hiring! 

With Stefano Maffulli’s departure in June, the Foundation continues to seek a number of positions, including:
  • Ecosystem Manager: focused on driving the Marketplace forward and liaising with industry groups
  • Upstream Developer Advocate: coordinating and communicating upstream development activities
  • App Dev Community Coordinator: liaise with SDK and developer communities, help solicit feedback and engagement from dev community
  • Engagement Community Manager: support new companies who want to contribute, professional cert, university programs, upstream training, user groups

OpenStack Community Weekly Newsletter (July 17 – 24)

OpenStack and cloud native applications: two peas in a data center pod

OpenStack has shown the world that innovation with open technology can happen. Fast. In fact, it can happen at a pace never before seen in the history of the IT industry.

Interoperability: DefCore, Refstack and You

The OpenStack Foundation has created a set of requirements to ensure that the various products and services bearing the OpenStack marks achieve a high level of interoperability. This post from IBM OpenTech Team gives an overview of the whole machinery, how to test clouds and upload results to RefStack website.

 

IMPORTANT + TIME SENSITIVE:

The Road to Tokyo

Reports from Previous Events

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

  • None this week

Tips ‘n Tricks

Upcoming Events

Other News

OpenStack Reactions

When I hit send after writing my long email for the TC candidacy

When I hit send after writing my long email for the TC candidacy

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis.

OpenStack Community Weekly Newsletter (July 10 – 17)

What you need to know about Google joining OpenStack

In the search for the next big thing, Google has joined the OpenStack Foundation. The Mountain View, California-based colossus announced July 16 that it has become a corporate sponsor of the Foundation.

OpenStack pins down next release name: Mitaka

OpenStack’s next release will be called Mitaka (三鷹). It’s named after the town located in the Tokyo metro area, known for Inokashira park (pictured above) and the Ghibli museum, which showcases the work of the animation studio of the same name.

The Road to Tokyo

Reports from Previous Events

  • None this week

Relevant Conversations

Deadlines and Contributors Notifications

Security Advisories and Notices

  • None this week

Tips ‘n Tricks

Upcoming Events

Celebrating 5 Years of OpenStack at OSCON on Wednesday, July 22nd: RSVP

Other News

OpenStack Reactions

When I stand corrected on an OpenStack mailing list

When I stand corrected on an OpenStack mailing list

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.