Category: openstack

Highlights of Newton OpenStack Summit Austin

Day 0

It’s been a long time to write this post after the Austin OpenStack Summit, but I hope to keep all memories of this trip.  It’s my third OpenStack Summit, this time the Summit happened at Austin Texas on April 25 to April 29, 2016 . This is my second time been to the US and first time been to Austin Texas.

I arrived Austin at Sunday (April 24) afternoon, dropped my bags at hotel and went to the convention center to pick up my badge and T-shirt before many people come in the Monday morning. Met my colleague Craige at  the convention center.

My third OpenStack Summit badge

iphone6Sd_20160515 296

Then I got a time taking a quick tourist of Austin around the convention center, walk at the Colorado riverside and visit the Capital of Texas State.

riversideiphone6Sd_20160515 249

I am very happen to meet my old colleague Dan and have dinner with him at the iron cactus mexican restaurant, try grill and margarita.

iphone6Sd_20160515 317 iphone6Sd_20160515 316

Day 1

The first day began with the live music from the band Soul Track Mind. This is first time OpenStack Summit start with the live music show, it’s fun.

iphone6Sd_20160515 322

Jonathan Bryce, Todd Morey and Lauren Sell of the OpenStack Foundation opened the conference and gave a tour of numbers. The first OpenStack summit was held in Austin just under six years ago with 75 people and they were proud to announce that this summit had over 7,500 people registered. In Jonathan’s keynote we were able to get into the real users of OpenStack, with highlights including the fact that 65% of respondents to the recent OpenStack User Survey are using OpenStack in production and that half of the Fortune 100 companies are using OpenStack. The video from his keynote is here: Embracing Datacenter Diversity.

The first day keynote session by AT&T, Mirants, SAP, Redhat and Volkswagen Group. The most interested for me is from Volkswagen Group(Driving the Future of IT Infrastructure at Volkswagen Group). Also announced the superuser awards to AT&T, the keynote sessions concluded with the announcement of the 2017 OpenStack Summit locations: Boston and Sydney!

After the keynote sessions, I joined the session of OpenStack-Health Dashboard and Dealing with Data from the Gate by Matthew Treinish, he talked about the openstack-health dashboard, how it works, it’s current limitations, and the future of the project. It’ll also cover some related tools that are available and how they all fit together, and how you can use everything together to take a more data driven approach to analyze and test OpenStack with the gate.

iphone6Sd_20160515 370

After lunch, I went to the talk “OpenStack Stable: What It Actually Means to Maintain Stable Branches” by Matt Riedemann, Matthew Treinish and Ihar Hrachyshka in the Upstream Development track of the conference. The goal of this talk was to inform members of the community what exactly is involved in management of stable releases, which has a lot more moving pieces than most people tend to expect. Video from the session up here.  Next is “OpenAPI as a Standard – A New Way Forward for API Documentation, Design and Tool” by Ken’ichi Ohmichi, Motohiro Otsuka, Anne Gentle and Alex Xu, this talk provides the overview of Swagger, how to apply Swagger to each project, and merit for clients. Video of this session here.

Next I joined is “Hunting for Purple Squirrels: Hiring OpenStack Contributors in the Wild” by Colette Alexander, She talked about the tips and tricks for screening and interviewing so you can get the best candidates for your team. She also talked about the traits and skills that are the best indicators for success for someone new to the OpenStack community, and what red flags to watch out for in interviews. The hiring process is daunting, but you’ll leave this talk re-charged and ready to go find some purple squirrels!

 

The last session joined in a series of great Lightning Talks. Elizabeth K. Joseph gave a tour of status.openstack.org. Continued with talks by Paul Belanger on Grafyaml, James E. Blair on Gertty and Andreas Jaeger on the steps for adding a project to OpenStack. Video of all the lightning talks here.

The last part today is the happy hour at the Market place, food, beer and music, visit sponsor’s booth for T-shirt and gifts.

iphone6Sd_20160515 390

Day 2 

Day two of the summit also began with live music. Mark Collier of the OpenStack Foundation kicked off by talking about to manage the increased  billions of devices infrastructure, new tools and patterns will be required which can handle bare metal, virtual machines, and containers, The opportunity is massive, but it will require collaboration across many open source communities, always mindful of what our users want and need, because it’s collaborate or die in the billion device, billion core era. videohere.

iphone6Sd_20160515 393

The highlights of the keynotes today included a talk about Building a SmartCity with IoT. Video of the presentation here. Improving user experience(UX) with OpenStackClient by Dean Troyer, The video from the talk is here. And OVH presented its high-performance and large-scale OpenStack-based cloud that efficiently combines dedicated and shared resources. And also Lew Tucker, Cisco’s CTO of Cloud Computing, will address Cisco’s continued commitment to OpenStack and discuss how the technology is evolving to usher in a new era of developer-driven, software-defined applications and services.

After these keynote sessions, I began my first Design Summit sessions. Tuesday is for the cross-project sessions.

ods-n_design_summit_sign

I joined following cross-project sessions:

  • Cross Project workshops: Deployment tools discussion
  • How to improve the situation around global requirements
  • Stable Branch End of Life Policy
  • The future of baremetal networking

There is another session related split event I didn’t join, copy the content from my colleague’s blog post:

“Brainstorm format for design summit split event” session that talked a lot about dates. As a starting point, Thierry Carrez wrote a couple blog posts about the proposal to split the design summit from the user summit:

With these insightful blog posts in mind, the discussion moved forward on the assumption that the events would be split and how to handle that timing-wise. When in the cycle would each event happen for maximum benefit for our entire community? In the first blog post he had a graphic that had a proposed timeline, which the discussions mostly stuck to, but dove deeper into discussing what is going on during each release cycle week and what the best time would be for developers to gather together to start planning the next release. While there was good discussion on the topic, it was clear that there continues to be apprehension around travel for some contributors. There are fears that they would struggle to attend multiple events funding-wise, especially when questions arose around whether mid-cycle events would still be needed. Change is tough, but I’m on board with the plan to split out these events. 

Tuesday’s evening I joined the StackCity Community Party.  Instead of individual companies throwing big, expensive parties, a street was rented out and companies were able to sponsor the bars and eateries in order to throw their branded events in them. But I didn’t get any thing to eat as most of the party is beer, I stay here about 1 hours and went with my colleague for another delicious dinner.

iphone6Sd_20160515 416      iphone6Sd_20160515 420

 

Day 3

Design Summit day of Infrastructure and QA

ods-n_design_summit_sign

All the Wednesday, I joined the Design Summit of Infrastructure and QA sessions. Today’s first session was discussing the Community Task Tracking. A status update on Storyboard and Maniphest, and the road ahead for OpenStack community task, bug and incident tracking. Copied of the pros and cons of Storyboard and Maniphest:

Pros Cons
Storyboard Strong influence over direction, already running and being used in our infra, good API We need to invest in development ourselves, little support for design/UI folks (though we could run a standalone Pholio)
Maniphest Investment is made by a large exiting development team, feature rich with pluggable components like Pholio for design folks Little influence over direction (like with Gerrit), still have to stand up and migrate to, weak API

The session didn’t end with any selection, Session etherpad here.

Next session I joined was the QA track about the devstack roadmap, Quick update on the progress of the Neutron refactor, discuss some of the issues discovered while doing the refactor, and plans to finish the refactor. Session etherpad here.

Next one also the QA track about How to accelerate to apply tempest.lib to each project? What’s necessary for a tempest plugin? Etherpad: here

The last one in the morning was Infrastructure: Landing Page for Contributors. The current pages were on the wiki, like the Main page and the How To Contribute wiki aren’t the most welcoming of pages. This session talked through a lot of the tooling that could be used to make a more inviting, approachable page. Session etherpad here.

In the afternoon, I just joined one QA session about OpenStack Health lead by Matthew Treinish, to discuss the current needs for the project and how to address outstanding issues like bringing in check queue data, how to handle DB scaling, etc. Session etherpad here

After that I have a great conversion and coffee with Vicky (Our US team manager), talked about the team status, work, presentation, Vicky suggested a great idea about present at LCA 2017 about Open Source projects contributions for none english native person.

Today’s evening I had a chance to join the core reviewers dinner sponsored by HPE each summit as the greeting  guys with my boss Allison. The dinner was at the very beautiful place and had chance to talk with many core reviewers.

iphone6Sd_20160515 435iphone6Sd_20160515 441

Conclude today with Austin’s beautiful night view

iphone6Sd_20160515 450

 

Day 4

Started in Thursday, I joined a session about “Application CI/CD on OpenStack – Building a Solution Using Jenkins and OpenStack Solum”, Continuous integration and continuous delivery are important aspects in today’s agile and iterative application development methods. Systems such as Jenkins have become pillars of the continuous integration movement providing a general framework to run application-specific tests. On the other hand, continuous delivery has always remained as a challenge. This is especially true if the deployment target is an OpenStack environment which involves several moving parts. In this talk we will present a CI/CD solution that we have built using Jenkins for CI and OpenStack Solum for CD for testing and deploying applications to OpenStack clouds.

iphone6Sd_20160515 466

Then back to the Design Summit for Infrastructure was a fishbowl session about OpenID/SSO for Community Systems. The OpenStack Foundation invested in the development of OpenStackID when few other options that fit our need were mature in this space. Today we have the option of using ipsilon, which has a bigger development community and is already in use by another major open source project (Fedora). The session outlined the benefits of consuming an upstream tool instead, including their development model, security considerations and general resources that have been spent to roll our own solution. The session also outlined exactly what our needs are to move all of our authentication away from Launchpad hosted by Canonical. Session etherpad here.

Next session was QA: DefCore and Interoperability Testing, The DefCore Working Group is formalizing the requirements for what an interoperable test is. With the successful history of collaboration between the QA and DefCore teams, this working session is targeted towards building that relationship and planning for working on short and long term test issues. This includes identifying work items for currently flagged tests, planning for the refactoring of existing tests to meet DefCore test requirements (including removing unnecessary admin privileges where possible), and long term planning for the augmentation of existing tests and creation of new tests for verifying cloud interoperability.”

The last one I joined today was QA: Newton cycle priorities, this session is to discuss, evaluate, and agree up the list of work item priorities for the Newton cycle. Etherpad: here

 

Day 5

The last day was the day for team work session gatherings. Jeremy Stanley (fungi) kicked the day off by outlining topics for Infra and QA that we may find valuable to work on together while we were in the room.

Infra etherpad and QA etherpad

I also got chance to meet with the jenkins-job-builder cores Wayne, Thanh and Khai, to talk about the jjb planning and jjb-2.0. Also in Austin Summit, I first time to meet Jeblair and Monty.

I concluded my Austin Summit with the special bar in Austin airport.

iphone6Sd_20160515 571

NOTE: Infrastructure PTL Jeremy Stanley has also written summaries of sessions here:Newton Summit Infra Sessions Recap

Mitaka OpenStack Summit at Tokyo

Day 1

It’s been more than a year to attend Mitaka OpenStack Summit at Tokyo, it’s my second OpenStack Summit, it’s my first travel after join the new team and it’s my first time to visit Tokyo. For Mitaka, the OpenStack Summit is only 4 days long, lasting from Tuesday through Friday. I arrived Tokyo Haneda Airport at the Monday afternoon (2015.10.26) with 3 hours flight from Beijing, then took the keikyu line railway to arrive Shinagawa Station, after about 10 mins walking got to my hotel and OpenStack Summit venue. (Grand Prince Hotel New Takanawa)Grand Prince Hotel New Takanawa

After a little rest, I walked over to the HP employee party at a nearby restaurant where I saw my boss first time.

Tuesday was the actual start of the summit. There about 5,000 attendees from 56 countries attend this summit, which makes it the biggest non-North American summit. I attended the keynotes today (all of which are in the video here: OpenStack Tokyo Summit Full Keynote). It continues to be inspiring to watch such diverse companies embracing not only the usage of open source and OpenStack, but the contributions back to the community. Jonathan Bryce also talked about the cool new feature on the OpenStack website that takes various metrics and creates a table tracking age, maturity and adoption to help operators evaluate each component, it can be found at: http://www.openstack.org/software/project-navigator. He also announced an OpenStack certification that was built and developed with some of the training partners and will start being available to take in 2016.

keynote

The rest of this day i attended many OpenStack sessions related Infrastructure.

Day2

The opening keynotes on Wednesday had a pretty common theme: Neutron. Mark Collier shared that in the Liberty cycle, for the first time Neutron was the most active project in OpenStack. This is really inspiring news for the community, as just two years ago there was concern about the commitment to the project and adoption statistics. Mark went on to share that 89% of respondents to the latest OpenStack User Survey said they’re using Neutron in production. Keynotes continued with former Neutron PTL Kyle Mestery who gave a quick history of Neutron, spoke about design goals and new Kuryr project, which focuses on networking for containers. Full video of the keynotes here.keynote

Today I also join the QA session about the new health dashboard to track problems and failures in our CI system so they can be checked by anyone when a disruption occurs. An initial prototype has been launched, so the discussion centered around the future of scaling the dashboard so it can be introduced to the wider community. This included concerns like backups and bottlenecks like subunit2sql performance fixes. Read-only link to the Etherpad from the session here.

The official evening party was hold by HP, Scality, Cisco and Bit-isle and took place at the beautiful Happo-En park. It was a shuttle ride or a 10 minute walk from the venue. The event had several indoor spaces with refreshments and entertainment. It also had a beautiful outdoor space, with a park to walk through, water features, bridges, and a whole fleet of bonsai trees, one of which was 520 years old.

party

Day3 and Day4
I spent the Thursday and Friday focus on the Design Summit and Team meetup. This is my first time to join the design summit.
Also sent a postcard with the Japanese character at the HP lounge.
iphone5_20151103 146
For lunch I met up with my HP colleagues as we secured two tables in the hot buffet lunch area, It’s my first time to meet the whole team and put the IRC nick to a face in several cases.
Friday was contributor meetup day! I would like to join the Infrastructure session but full house.
That’s all my Mikata OpenStack Summit!

Contribute to OpenStack

This August, I transferred to a new team as an upstream contributor on the OpenStack Infrastructure team. I started my new journal in the OpenStack world, I have been focusing on the jenkins-job-builder, OpenStack CI and OpenStack QA projects. I had my first OpenStack patch merged on August 11, 2015, I would like to write and share my experience about contribute to OpenStack projects.

  • What to contribute?                                                                                            

My first patch is a bug fix for openstack documentation, documentation is the easiest start for the first patch, also you can ask for help from your colleagues to find out where to contribute, If you don’t have a buddy to make recommendations, just pop into the #openstack-infra #openstack-qa and #openstack-doc channel in IRC and just ask for suggestions.

  • Setup your dev environment                                                                OpenStack has done an excellent job of documenting the steps for new developers and I recommend following those instructions.
    1. Account Setup                                                                                   First, You’ll need a Launchpad account, since this is how the Web interface for the Gerrit Code Review system will identify you. Also to contribute to any OpenStack project, you’ll need to create a community account and sign the agreement. Make sure the email you provide for your OpenStack email address matches your Ubuntu Single Sign On email address! Also make sure to update your contact information on Gerrit.You’ll also want to upload an SSH key to Gerrit at review.openstack.org while you’re at it, so that you’ll be able to commit changes for review later. This is different from adding a key to Launchpad. Ensure that you have run these steps to let git know about your email address: 
      git config --global user.name "Firstname Lastname"
git config --global user.email "your_email@youremail.com"
git config --global http.proxy http://web-proxy.cce.hp.com:8088 (optional for env under firewall)
git config --global https.proxy http://web-proxy.cce.hp.com:8088 (optional for env under firewall)
    2. Install git-review 
      apt-get install git-review
git config --global gitreview.scheme https
git config --global gitreview.port 443
git config --global gitreview.username yourgerritusername
    3. Working on a projectClone a repository in the usual way, for example: 
      git clone https://git.openstack.org/openstack/<projectname>.git
debug: nc review.openstack.org 29418
debug: ssh -p 29418 larainema@review.openstack.org gerrit version
    4. If you didn’t work under the Great China firewall, the envroument will works, but the port 29418 is blocked by the firewall, so ssh didn’t work in China, you need to access Gerrit by HTTPS.Keep in mind that you will need to generate an HTTP password in Gerrit to use this connection. You should run the following command before “git review -s”: 
      git remote add gerrit https://<username>:<password>@review.openstack.org/<umbrella repository name>/<repository name>.git
    5. Obtain commit-msg 
      $ scp -p -P 29418 <your username>@<your Gerrit review server>:hooks/commit-msg <local path to your git>/.git/hooks/ 
$ curl -Lo <local path to your git>/.git/hooks/commit-msg <your Gerrit http URL>/tools/hooks/commit-msg
    6. In general you should be using a local Python rather than a system Python. You know if you’re using system Python if you have to type “sudo” anytime you want to do anything beyond running a program (like pip). Virtualenv makes doing this really easy. My colleagoue have a great blog about how to use virtualenv

 

  • Run the tests                                                                                                      Once you’ve cloned the git repository, follow the instructions in the README at the parent level to do any necessary local setup. It will likely involve installing a bunch of python dependencies. See the section above for my recommendation involving using virtualenv for this.After configuring and installing, before touching anything else, I highly recommend running the tests to make sure everything works on your system. It’s incredibly hard to troubleshoot when you’re not sure if your patch broke something or if it was a setup issue that’s causing test failures. To run the tests you’ll need to set up tox if you haven’t already. It’s really straightforward (pip install tox), see the OpenStack Python Developer Docs if you’re not sure how.

 

  • Make the changes
  • git checkout -b TOPIC-BRANCH
git commit -a
git review

Git commit messages should start with a short 50 character or less summary in a single paragraph. The following paragraph(s) should explain the change in more detail.

  • Update the changes
  • git commit -a --amend
git review
  • Get your patch reviewed                                                                                          Once the test have passed, you’ll need to get your change accepted by 2 core members in order to get it merged. If your patch has been reviewed and says “Needs Workflow” it means another core needs to approve it before it can be merged.
    To find out who the core members are that can +2 or approve your patch, visit the project’s page in review.openstack.org. Click on “Access” at the top of the screen and then click on any of the project-core links to see a list of people. You can add names as Reviewers to your change from your change’s url or you can ask in #openstack-infra if those individuals could review your change.
    Once your patch has been approved, it will be automatically merged!

 

  • You can watch your progress as an OpenStack contributor at Stackalytics!

 

Useful Links