OpenStack Community Weekly Newsletter (Dec 6 – 13)

OpenStack DefCore Enters Execution Phase. Help!

OpenStack DefCore Committee has established the principles and first artifacts required for vendors using the OpenStack trademark. Over the next release cycle, we will be applying these to the Icehouse and Juno releases. Rob will be doing two sessions about DefCore next week (will be recorded): Tues Dec 16 at 9:45 am PST- OpenStack Podcast #14 with Jeff Dickey and Thurs Dec 18 at 9:00 am PST – Online Meetup about DefCore with Rafael Knuth.

Keeping up to date with OpenStack Blueprints

OpenStack is a living product – and because it is community driven – changes are being proposed almost constantly. The specifications approved in each project are published on http://specs.openstack.org as html pages and RSS feeds. Maish Saidel-Keesing compiled an OPML file with all the current projects that you can add to your favorite RSS reader.

Korea User Group got “The community of the Year” award

Great news for the whole OpenStack community: OpenStack Korea User Group received “The community of the Year” award from Korea Open Source Software Association. Congratulations to all for the amazing work you’ve been doing all these years. The Korean user group doesn’t rest on their laurels and they’re busy organizing the OpenStack Day Korea 2015: check the sponsorship opportunities.

Ask OpenStack passes 10,000 questions

Recently, our Q&A site, Ask OpenStack passed an important milestone – more than 10,000 questions. Since it was launched by community manager Stefano Maffulli with the help of our tame AskBot developer Evgeny Fadeev early last year, we’ve had great support from our entire community – users and vendor support staff alike getting on there and helping each other out. Everybody can give answers: read how to give answers and head out to answer questions on Ask OpenStack.

Relevant Conversations

Deadlines and Development Priorities

Security Advisories and Notices

Tips ‘n Tricks

Reports from Previous Events

Upcoming Events

Other News

Got Answers?

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

Welcome New Reviewers and Developers

Chris Gacsal Ankur Rishi
Babu Shanmugam Alger Wang
Abhishek G M Tom Pollard
Bogun Dmitriy Dan Ritchie
Cosmin Poieana
wangtianfa
Roman Dobosz
Park
Moshe Levi
Matt Borland
Toshiaki Higuchi
Dexter Fryar
Chris Gacsal
Hironori Shiina

OpenStack Reactions

waiting-for-reviews

waiting for reviews on my spec

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.

Ask OpenStack passes 10,000 questions

Recently, our Q&A site, Ask OpenStack passed an important milestone – more than 10,000 questions. Since it was launched by community manager Stefano Maffulli with the help of our tame AskBot developer Evgeny Fadeev early last year, we’ve had great support from our entire community – users and vendor support staff alike getting on there and helping each other out.

At points like this one, it is wise to reflect on whether the endeavour has been successful. Anecdotally, we hear good things, and there seems to be a reasonably self-sustaining community around the site.

We have pulled the data to compare the proportion of questions that were asked to those that were answered, and compared it to other forums to gauge where we stand. Although there were some fluctuations that occurred during some periods, the volunteer team was able to diagnose the problem and move forward.

During some months of this year – luckily unseen by most – we suffered from a serious spam problem. This is an example of something that can seriously turn members away, though the moderation tools and volunteer team was able to keep it in check. A potential problem as serious as a spam infestation is if user’s questions don’t get answered. So we did some quick math and googling to try and quantify how we’re doing.

There are about 1,700 unanswered questions out of over 10,000 in total. Based on the rough conclusions for similar sized/typed communities – we’re essentially in a best-of-field position. Now, let’s look at if we’re keeping it there.

This time series has been tracking our unanswered questions for 494 days. We started with 150 unanswered questions, and on average over this period we add 3.12 questions per day. This is already good, because it means that if we can push just 25 people to answer an extra question every week we’ll start going in the other direction.

Now, to look at whether the trend is going up. Dividing the space into two 247 day segments, we can calculate the relative average over these two chunks of time (basically 2/3rds of a year each). In the first chunk, from Jul 2013 to Mar 2014 the average is 2.6 new unanswered questions per day. In the second chunk it’s an average of 3.5 new unanswered questions per day.

So, the trend is increasing by about 23% over this 2/3rd of a year chunk. If it increases to 4/day, which will take about a year at the current rate of increase, that means that rather than getting 25 new people involved, we’d need to have 30+. Still not so bad.

Of course, this analysis doesn’t take into account that some of the unanswered questions are just unanswerable – but in theory the moderation team should be weeding those out.

 

Question posted Screen Shot 2014-12-02 at 11.55.17 AM

Final idea – which might put us firmly in the “best practice” bucket. What about a global 24 hour Ask OpenStack Question Answering day? Do you think such a thing would work? Everybody can give answers: read how to give answers and head out to answer questions on Ask OpenStack.

Tags:

OpenStack Community Weekly Newsletter (Nov 28 – Dec 6)

December 2014 OpenStack Infrastructure User Manual Sprint

During this week the Infrastructure team released a significant milestone for the Infrastructure User Manual. The manual consolidates documentation for Developers, Core Reviewers and Project Drivers, which was spread across wiki pages, project-specific documentation files and general institutional knowledge. The manual is starting to look great and a lot of wiki pages have been declared obsolete meanwhile.

Third-party CI account creation is now self-serve

This means that new third-party account will need to follow a new, leaner process. There are some changes for existing accounts. Read the full announcement.

My Key Learning from Paris

Matt Fischer “learned a bunch of things in Paris: French food is amazing, always upgrade OVS” and “All operators have the same problems.” The result of his and others’ realization is the beginnings of an Operations Project.

Relevant Conversations

Deadlines and Development Priorities

Stable Release

Tips ‘n Tricks

Reports from Previous Events

Upcoming Events

Other News

Got Answers?

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

Welcome New Reviewers and Developers

Kai Qiang Wu Midun Kumar
Jing Zeng Jukka Lehtniemi
Marco Fargetta Sunil Kumar
Sam Yaple chenglch
Qi Zhang Yoni
Richard Hedlind Kyle Rockman
Hironori Shiina qiaomin032
yoan desbordes Stefano Canepa
Surojit Pathak Sam Yaple
Rohit Jaiswal Chris Cannon

OpenStack Reactions

rev

Starting a VM on my newly deployed OpenStack cloud

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.

Tags:

Studying Midcycle Sprints and Meetings

Hard to believe that we gathered in Paris just a month ago for the Design Summit. I’m still snacking on the chocolate and cheese from that fine place.

Since the Summit we’ve had questions and posts about midcycle meeting planning, so I started gathering information from the various teams and we discussed at a recent cross-project meeting. Here are the findings about patterns, guidelines, and pitfalls for midcycle meetings. I’ve posted these to the OpenStack wiki also so we can continue to evolve and refine as our teams self-organize.

Patterns we’re seeing for current midcycle meetings:

  • About 10-30 people attend.
  • Feedback by attendees is positive; midcycle meetings are generally considered productive events.
  • Only a handful of groups tend to hold them; for this cycle we’re seeing some teams choose not to. Often subteams form around a specific tasks to complete.
  • Meeting space is donated by companies, so often location is based on available free spaces and dates are then partial to the location availability.
  • Travel costs are the responsibility of the individual attending (their employer most likely).
  • Sometimes companies will host meals (not often).

Guidelines we want teams to stick to:

  • Highest return on investment is in early days of joining or forming the team, when social bonds and trust need to be established.
  • Best quality meetings tend to be sprint-oriented with real work getting done and a specific outcome in mind; hence the mid-cycle sprint name.
  • Organization responsibility lands on PTL or a designated delegate.
  • Multiple sprints can be co-hosted. However, productivity also lies in the small, quiet environment, and social bonding is easier in smaller groups.
  • Unless there are good cross-pollination opportunities between co-hosted teams, teams should favor separate sprints.
  • The Design Summit should be the first choice for gathering the whole team for decisions and roadmap alignment.

Known risks to be aware of:

  • Pitfall can be a feeling of “required” attendance (social or actual) causing hard feelings; also some types of contributors will be marginalized despite best efforts, such as those without a corporate sponsor, family caretakers, and people who need Visas to travel.
  • Often there’s a choice implied in choosing what an individual travels to; adding a midcycle sprint means a choice has to be made.
  • Virtual aspects of a midcycle require additional support such as open source tooling, or if using non-open source tooling, you must get agreement from participants.

From my own experience, the docs team had a boot camp over a year ago where we had a great time focusing on our team, but since then we haven’t needed to meet separately from the Design Summit. Here’s Michael Still giving his “I love you” sign at our docs team meetup.
Doc boot camp

If you have any questions about midcycle sprints, please ask Stefano Maffulli. To get a list of upcoming sprints, both in person and virtual, go to the Sprints wiki page.

OpenStack Community Weekly Newsletter (Nov 21 – 28)

Notice of meeting to elect Individual Directors

The Annual Meeting of the Individual Members to elect directors for the Board of the OpenStack Foundation shall be held from January 12, 2015 to January 16, 2015, commencing at 00:01 UTC on January 12 and ending at 17:00 UTC on January 16. The meeting will be held by remote communication. While technically a “meeting” according to our bylaws, all of the voting will take place online. If you are an eligible voter, you will receive an email with a link that will allow you to complete your ballot during the time that the election occurs.

In the meantime, nominate OpenStack Foundation Individual Members as candidates for election. The requirements for nominating any individual to run for the Board must be completed and received by the OpenStack Foundation on or prior to 23:00 UTC on December 12, 2014. Nominations Close: 23:00 UTC, December 12, 2014. Polls Open: 00:01 UTC, January 12, 2015. Polls Close: 17:00 UTC, January 16, 2015.

The Foundation Board of Directors is also considering three potential changes to the OpenStack Foundation Bylaws, as a result of the work during the DefCore Committee’s activities. If the proposed amendments are passed at the Board meeting on December 2, they will each be on the ballot in the upcoming election January 12-16, 2015. Read an explanation of the three amendments and the proposed language.

Seeing Murano Actions in action

Murano is an OpenStack project that enables application developers and cloud developers to publish applications in a browsable catalog. With the catalog, users can create complex multi-tier application environments with the push of a button using published applications as building blocks.

reBot – using Lego for bare metal deployments on Intel NUC

Cloudbase uses a lot of Intel Next Unit of Computing (NUC) for internal testing and development work. NUCs lack the ability to power them on and off remotely, like higher grade servers do with technologies likeIPMI, AMT, iLO. In pure hacker spirit, Cloudbase invented their own to have some fun. Spoiler alert: it involves Lego.

Fedora Atomic, OpenStack, and Kubernetes (oh my)

Lars Kellogg-Stedman has embarked in a fascinating journey: follow his thoughts among the most recent, bleeding edge technologies.

Relevant Conversations

Deadlines and Development Priorities

Tips ‘n Tricks

Reports from Previous Events

Upcoming Events

Other News

Got Answers?

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

Welcome New Reviewers, Developers and Core Reviewers

yoan desbordes 刘军卫
Cedric Dos Santos ZhangYang
Praveen Kumar Bharat Kumar Kobagana
Bharat Kumar Kobagana zhu.rong
Einst Crazy
Danny Wilson
kulafenghen
ice.yao
Maxime Leroy
Kai Qiang Wu
Ikuo Kumagai
Naohiro Tamura
coding1314
Dingyx
xhzhf
Jan Kundrát

OpenStack Reactions

Running devstack when family is eating turkey

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.

OpenStack Community Weekly Newsletter (Nov 14 – 21)

OpenStack User Survey Insights: November 2014

This is the fourth consecutive survey conducted by the User Committee prior to each Summit starting in April 2013 and the previous survey in Atlanta, May 2014. The goals of the survey are to generate insights based on a representative sample of OpenStack users, in order to better understand their organizational profiles, use cases and technology choices across different deployment stages and sizes. These insights are intended to provide feedback to the broader community, and to arm technical leaders and contributors with better data to make decisions.

Wrapping up the Travel Support Program – Kilo

The OpenStack Foundation brought 20 people to Paris for the Summit earlier this month, thanks to the grants offered by the Travel Support Program. We had 22 people accepted in the program from 11 different countries, spanning five continents. Four people traveled from Brazil, four from India, three from Europe and the rest were from South America, North America and South-east Asia. Of the selected recipients, two were unable to attend due to VISA timing issues, but we were excited to welcome the 20 attendees that were able to make the trip. Stay tuned for when we announce the applications for the Travel Support Applications for the May Summit in Vancouver.

A mascot for Ironic

The idea about what the mascot would be was easy because the RAX guys put “bear metal” in their presentation and that totally rocks! So Lucas Alvares Gomes drew a bear.

Relevant Conversations

Deadlines

Tips ‘n Tricks

Security Advisories and Notices

Reports from Previous Events

Upcoming Events

Other News

Got Answers?

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

Welcome New Reviewers, Developers and Core Reviewers

Welcome Michael McCune and Sergey Reshetniak to sahara-core, Steve Heyman, Juan Antonio Osorio Robles and Steve Heyman for barbican-core.

Xiao Xi LIU Ai Jie Niu
Naohiro Tamura jiangfei
Danny Wilson Dave Chen
yatin rajiv
Richard H juigil kishore
Pawel Palucki Richard Hedlind
Park Lucas Dutra Nunes
jmurax Nicolas T
Swati Shukla Michael Hagedorn
Guillaume Giamarchi keshava
Seb Hughes
sailajay

OpenStack Reactions

Helping new contributor

Finding a great bug to solve and giving it to new contributors (and helping them)

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.

Wrapping up the Travel Support Program – Kilo

The OpenStack Foundation brought 20 people to Paris for the Summit earlier this month, thanks to the grants offered by the Travel Support Program. The Travel Support Program is based on the promise of Open Design and its aim is to facilitate participation of key contributors to the OpenStack Design Summit. The program aims at covering costs for travel and accommodation for key contributors to the OpenStack project to join the community at the Summits.

Travel Support Program

We had 22 people accepted in the program from 11 different countries, spanning five continents. Four people traveled from Brazil, four
 from India, three from Europe and the rest were from South America, North America and South-east Asia. Of the selected recipients, two were unable to attend due to VISA timing issues, but we were excited to welcome the 20 attendees that were able to make the trip. 

The Foundation spent $28,400 on flights and $24,000 on hotels for a total cost for the Foundation of more than $54,000 USD, including the cost of four full access passes granted to non-ATCs. 

Stay tuned for when we announce the applications for the Travel Support Applications for the May Summit in Vancouver. The Travel Support Program will also be a sponsorship opportunity for the upcoming Summit in Vancouver. Details will be shared in the sponsorship prospectus that will be published soon.  

OpenStack Community Weekly Newsletter (Post Paris)

How Operators Can Get Involved in Kilo #OpenStackSummit

Maish Saidel-Keesing participated in the Ops Summit: How to get involved in Kilo, and shared his notes from those sessions.

Development Reports from Summit

Relevant Conversations

Tips ‘n Tricks

Security Advisories and Notices

Upcoming Events

Other News

Got Answers?

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

Welcome New Reviewers, Developers and Core Reviewers

jiangfei Cserey Szilard
ZongKai LI Ran Ziv
Swati Shukla Accela Zhao
Guillaume Giamarchi yatin
Seb Hughes François Bureau
Vadim Rutkovsky habuka036
Mark McDonagh Zengfa Gao
Craige McWhirter Jorge Munoz
juigil kishore Jobin Raju
Trung Trinh John Belamaric
Scott Lowe Seb Hughes
Roozbeh Shafiee David Caro
Mike Mason Craige McWhirter
Tan Lin Jan-Erik Mångs
David Caro Adolfo Duarte
Konstantinos Papadopoulos Tan Lin
Matteo Panella hossein zabolzadeh
Lena Vinod Pandarinathan
Michael Hagedorn Pieter
Major Hayden Lan Qi song
Magnus Lundin Vidyut
Arun S A G Inessa Vasilevskaya
Pratik Mallya Gil Meir
Brian Saville Dimitri Korsch
Chris Grivas Ian Adams
Marcin Karkocha Pratik Mallya
Yash Bathia
Wei Xiaoli
Mike Mason
Anton Arefiev
Yury Konovalov
Shang Yong

OpenStack Reactions

show-the-light

When a large company join the OpenStack foundation after ignoring it for a while

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.

 

OpenStack Upstream Training in Japan

While we’re completing the training sessions in Paris, I’m glad to share the results of the Upstream Training in Japan on Oct.10-11 in Tokyo. The training session was organized by the Japanese user group with 19 people attending from 11 different Japanese companies and organizations and 7 mentors helping them. There are a lot more developers interested in becoming contributors to OpenStack so the Japanese community is organizing more sessions. The next one will be in February, co-located with OpenStack Days Tokyo. Trainees chose bugs from Launchpad and engaged with mentors two weeks before the live, in-person sessions.

The Japanese community has shared lots more pictures, showing impressive work on the collaborative LEGO building role playing game. Congratulations to the Japanese community for being the first to bring home the practice of OpenStack Upstream Training.

The Lego building role playing game

The Lego building role playing game

Full learning mode

Full learning mode

 

2014 Summer of Interns at OpenStack

OpenStack has been a regular participant in community-led internship programs, such as the FOSS Outreach Program and for the
first time this year, the Google Summer of Code. Our wonderful mentors and coordinators have made it possible for OpenStack to have some great interns over the (northern hemisphere) summer. Julie Pichon has helped collect thoughts from the interns. Here is what they have to say about their experience:

Artem Shepelev worked on a scheduler solution based on the non-compute metrics: Working as a part of Google Summer of Code program was very interesting and useful for me. I liked the experience of working with a real project with all its difficulty, size and people involved with it. (Mentors: Yathiraj Udupi, Debojyoti Dutta)

Tzanetos Balitsaris worked on measuring the performance of the deployed Virtual Machines on OpenStack: The experience was really good. Of course one has to sacrifice some things over the summer, but at the end of the day, you have the feeling that it was worth it. (Mentors: Boris Pavlovic and Mikhail Dubov).

Rishabh Kumar: I worked on improving the benchmarking context mechanism in the Rally project. It was a really awesome experience to be part of such a vibrant and diverse community. Getting to know people from all sorts of geographies and the amazing things they are doing humbled me a lot. The code reviews were particularly good with so many people giving their reviews which made me a better programmer. (Mentors: Boris Pavlovic and Mikhail Dubov).

Prashanth Raghu: GSoC was a great opportunity for me to get started with learning about contributing to open source. During my project I was greatly backed by the community which helped me a lot in finally getting my project successfully shipped into the OpenStack Zaqar repository. It was great fun interacting with the team and I would like to thank all those who supported me in this wonderful experience. (Mentor: Alejandro Cabrera).

Ana: I am very grateful for being given the chance to participate in OPW. I had a really positive experience thanks to an amazing mentor, Eoghan Glynn, who explained everything clearly and was enthusiastic about the project and was patient with my many mistakes. I was working on Gnocchi, a new API for Ceilometer; my project was to add moving statistics to the available aggregation functionality. (Mentor: Eoghan Glynn).

Victoria: During my GSoC internship in OpenStack I researched the feasibility of adding AMQP 1.0 as a storage backend for the Messaging and Notifications Service (Zaqar). Since this was not possible, I changed the direction of my research to the transport layer and worked
on creating a POC for it. (Mentor: Flavio Percoco).

Masaru: Awesome experience which is more than I expected at the beginning of my project about VmWare API! Also, great and considerate hackers there, I’m grateful to have participated in GSoC 2014  as one of the students from the OpenStack Foundation. (Mentor: Mr. Arnaud Legendre).

Nataliia: It was a fascinating opportunity. During the internship I worked with the Zaqar team, mainly on Python 3 support, but also with developing api-v1.1. Professionally I learnt a lot, about Python 3 of course, but also from reading and participating in discussions of other interns: about Redis and AMPQ and how to do proper benchmarking. Socially-wise: There was no feeling of being “an intern”. The team considers all interns as teammates and treats them equally as any other developer. Anyone could (and actually can — why not?) actively participate in discussions and in making decisions. After finishing it, I helped with other tasks, in particular api-v1.1-response-document-changes. (Mentor: Flavio Percoco, Kurth Griffiths).

OpenStack doesn’t plan on stopping there and is already preparing for the next round of the FOSS Outreach Program, this time scheduled during the southern hemisphere summer round starting this December. Stay tuned for more announcements.