This year has been super packed with conferences and travel. I’ve done 13 talks across 3 continents and have several more coming up in the next few months. I’ve also been squeezing in the hosting of Ubuntu Hours each month.
Aside from all this, life-wise things have been pretty mellow due to my abdominal pain (sick of hearing about it yet?). I’ve been watching a lot of TV because of how exhausted the pain is making me. Exercise has totally taken a back seat, this compounds the tiredness and means I’ve put on some weight that I’m not at all happy about. Once I’m better I plan on starting Couch to 5K again and may also join a new gym to get back into shape.
The gallbladder removal surgery itself is on Thursday and I’m terribly nervous about it. Jet lag combined with surgery nervousness means I haven’t been sleeping exceptionally well either. I’m not looking forward to the recovery, it should be relatively fast (a couple of weeks), but I’m a terrible patient and get bored easily when I’m not doing things. It will take a lot of effort to not put too much stress on my system too quickly. I’ll be so happy when this is all over.
I did take some time to do a few things though. On June 29th our friend Danita was still in town and we got to check out the Pride parade, which is always a lot of fun, even if I did get a bit too much sun.
Lots more photos from the parade here: https://www.flickr.com/photos/pleia2/sets/72157645439712155/
MJ and I also took a Sunday to drive north a couple weeks ago to visit Tiburon for some brunch. It was a beautiful day for it, and always nice to further explore the beautiful places around where we live, I hope we can make more time for it.
Finally, I’m happy to report that after a couple months, I’ve gotten a painting back from Chandler Fine Art who was working with a restoration artist to clean it up and to have it framed. Not much can be done about the cracks without a significant amount of work (the nature of oil paintings!) but they were able to fix a dent in the canvas and clean up some stains, I can’t even tell where the defects were now.
It may not strictly match the decor of our home, but it was a favorite of my father’s growing up and it’s nice to have such a nice memory from my childhood hanging here now.
This past spring I had the great opportunity to work with Matthew Helmke, José Antonio Rey and Debra Williams of Pearson on the 8th edition of The Official Ubuntu Book.
In addition to the obvious task of updating content, one of our most important tasks was working to “future proof” the book more by doing rewrites in a way that would make sure the content of the book was going to be useful until the next Long Term Support release, in 2016. This meant a fair amount of content refactoring, less specifics when it came to members of teams and lots of goodies for folks looking to become power users of Unity.
Quoting the product page from Pearson:
The Official Ubuntu Book, Eighth Edition, has been extensively updated with a single goal: to make running today’s Ubuntu even more pleasant and productive for you. It’s the ideal one-stop knowledge source for Ubuntu novices, those upgrading from older versions or other Linux distributions, and anyone moving toward power-user status.
Its expert authors focus on what you need to know most about installation, applications, media, administration, software applications, and much more. You’ll discover powerful Unity desktop improvements that make Ubuntu even friendlier and more convenient. You’ll also connect with the amazing Ubuntu community and the incredible resources it offers you.
Huge thanks to all my collaborators on this project. It was a lot of fun to work them and I already have plans to work with all three of them on other projects in the future.
So go pick up a copy! As my first published book, I’d be thrilled to sign it for you if you bring it to an event I’m at, upcoming events include:
- August 9, Philadelphia: Fosscon
- August 27-31, Portland, OR: Debconf 14
- September 11-13, Orlando: Fossetcon
- September 23, San Francisco: PuppetConf
- October 22-23, Raleigh: All Things Open
And of course, monthly Ubuntu Hours and Debian Dinners in San Francisco.
This past week I was in Germany! I’ve gone through Frankfurt many times over the years, but this was the first time I actually left the airport via ground transportation.
Upon arrival I found the bus stop for the shuttle to Darmstadt and after a 20 minute ride was at Hauptbahnhof (main transit station) in Darmstadt and a very short walk took me to the Maritim Konferenzhotel Darmstadt where I’d be staying for the week.
The hotel was great, particularly for a European hotel. The rooms were roomy, the shower was amazing, and all the food I had was good.
Our timing on the sprint was pretty exceptional, with most of us arriving on Sunday just in time to spend the evening watching the World Cup final, which Germany was in! Unfortunately for us the beer gardens in the city required reservations and we didn’t have any, so we ended up camping out in the hotel bar and enjoying the game there, along with some beers and good conversations. In spite of my current gallbladder situation, I made an exception to my abstinence from alcohol that night and had a couple of beers to commemorate the World Cup and my first proper time in Germany.
Unfortunately I wasn’t so lucky gallbladder-wise the rest of the week. I’m not sure if I was having some psychosomatic reaction to knowing the removal surgery is so close, but it definitely felt like I was in more pain this week. This kept me pretty close to the hotel and I sadly had to skip most of the evenings out with my co-workers at beer gardens because I was too tired, in pain and couldn’t have beer anyway.
I did make it out on Wednesday night, since I couldn’t resist a visit to Darmstädter Ratskeller, even if I did only have apple juice. This evening brought me into Darmstadt center where I got to take all my tourist photos, and also gave me an opportunity to visit the beer garden and chat with everyone.
Plus, I managed to avoid pork by ordering Goulash – a dish I hadn’t had the opportunity to enjoy since my childhood.
I wish I had felt up to more adventuring. Had I felt better I probably would have spent a few extra days in Frankfurt proper giving myself a mini-vacation to explore. Next time.
All photos from my adventure that night in Darmstadt center (and planes and food and things!) here: https://www.flickr.com/photos/pleia2/sets/72157645839688233/
I spent this week at the QA/Infrastructure Meetup in Darmstadt, Germany.
Our host was Marc Koderer of Deutsche Telekom who sorted out all logistics for having our event at their office in Darmstadt. Aside from the summer heat (the conference room lacked air conditioning) it all worked out very well, we had a lot of space to work, the food was great, we had plenty of water. It was also nice that the hotel most of us stayed at was an easy walk away.
The first day kicked off with an introduction by Deutsche Telekom that covered what they’re using OpenStack for in their company. Since they’re a network provider, networking support was a huge component, but they use other components as well to build an infrastructure as they plan to have a quicker software development cycle that’s less tied to the hardware lifetime. We also got a quick tour of one of their data centers and a demo of some of the running prototypes for quicker provisioning and changing of service levels for their customers.
Monday afternoon was spent with an on-boarding tutorial for newcomers to OpenStack when it comes to contributing, and on Tuesday we transitioned into an overview of the OpenStack Infrastructure and QA systems that we’d be working on for the rest of the week. Beyond the overview of the infrastructure presented by James E. Blair, key topics included in the infrastructure included jeepyb presented by Jeremy Stanley, devstack-gate and Grenade presented by Sean Dague, Tempest presented by Matthew Treinish (including the very useful Tempest Field Guide) and our Elasticsearch, Logstash and Kibana (ELK) stack presented by Clark Boylan.
Wednesday we began the hacking/sprint portion of the event, where we moved to another conference room and moved tables around so we could get into our respective working groups. Anita Kuno presented the Infrastructure User Manual which we’re looking to flesh out, and gave attendees a task of helping to write a section to help guide users of our CI system. This ended up being a great thing for newcomers to get their feet wet with, and I hope to have a kind of entry level task at every infrastructure sprint moving forward. Some folks worked on getting support for uploading log files to Swift, some on getting multinode testing architected, and others worked on Tempest. In the early afternoon we had some discussions covering recheck language, next steps I’d be taking when it comes to the evaluation of translations tools, a “Gerrit wishlist” for items that developers are looking for as Khai Do prepares to attend a Gerrit hack event and more. I also took time on Wednesday to dive into some documentation I noticed needed some updating after the tutorial day the day before.
Thursday the work continued, I did some reviews, helped out a couple of new contributors and wrote my own patch for the Infra Manual. It was also great to learn and collaborate on some of the aspects of the systems we use that I’m less familiar with and explain portions to others that I was familiar with.
Friday was a full day of discussions, which were great but a bit overwhelming (might have been nice to have had more on Thursday). Discussions kicked off with strategies for handling the continued publishing of OpenStack Documentation, which is currently just being published to a proprietary web platform donated by one of the project sponsors.
A very long discussion was then had about managing the gate runtime growth. Managing developer and user expectations for our gating system (thorough, accurate testing) while balancing the human and compute resources that we have available on the project is a tough thing to do. Some technical solutions to ease the pain on some failures were floated and may end up being used, but the key takeaway I had from this discussion was that we’d really like the community to be more engaged with us and each other (particularly when patches impact projects or functionality that you might not feel is central to your patch). We also want to stress that the infrastructure is a living entity that evolves and we accept input as to ideas and solutions to problems that we’re encountering, since right now the team is quite small for what we’re doing. Finally, there were some comments about how we run tests in the process of reviewing, and how scalable the growth of tests is over time and how we might lighten that load (start doing some “traditional CI” post merge jobs? having some periodic jobs? leverage experimental jobs more?).
The discussion I was most keen on was around the refactoring of our infrastructure to make it more easily consumable by 3rd parties. Our vision early on was that we were an open source project ourselves, but that all of our customizations were a kind of example for others to use, not that they’d want to use them directly, so we hard coded a lot into our special openstack_projects module. As the project has grown and more organizations are starting to use the infrastructure, we’ve discovered that many want to use one largely identical to ours and that making this easier is important to them. To this end, we’re developing a Specification to outline the key steps we need to go through to achieve this goal, including splitting out our puppet modules, developing a separate infra system repo (what you need to run an infrastructure) and project stuff repo (data we load into our infrastructure) and then finally looking toward a way to “productize” the infrastructure to make it as easily consumable by others as possible.
The afternoon finished up with discussions about vetting and signing of release artifacts, ideas for possible adjustment of the job definition language and how teams can effectively manage their current patch queues now that the auto-abandon feature has been turned off.
And with that – our sprint concluded! And given the rise in temperature on Friday and how worn out we all were from discussions and work, it was well-timed.
Huge thanks to Deutsche Telekom for hosting this event, being able to meet like this is really valuable to the work we’re all doing in the infrastructure and QA for OpenStack.
Full (read-only) notes from our time spent throughout the week available here: https://etherpad.openstack.org/p/r.OsxMMUDUOYJFKgkE
Today the OpenStack Infrastructure team hosted our first bug day of the cycle.
The steps we have for running a bug day can be a bit tedious, but it’s not hard, here’s the rundown:
- I create our etherpad: cibugreview-july2014 (see etherpad from past bug days on the wiki at: InfraTeam#Bugs)
- I run my simple infra_bugday.py script and populate the etherpad.
- Grab the bug stats from launchpad and copy them into the pad so we (hopefully) have inspiring statistics at the end of the day.
- Then comes the real work. I open up the old etherpad and go through all the bugs, copying over comments from the old etherpad where applicable and making my own comments as necessary about obvious updates I see (and updating my own bugs).
- Let the rest of the team dive in on the etherpad and bugs!
Throughout the day we chat in #openstack-infra about bug statuses, whether we should continue pursuing certain strategies outlined in bugs, reaching out to folks who have outstanding bugs in the tracker that we’d like to see movement on but haven’t in a while. Plus, we get to triage a whole pile of New bugs and close others we may have lost track of.
As we wrap up, here are the stats from today:
Bug day start total open bugs: 281
- 64 New bugs
- 41 In-progress bugs
- 5 Critical bugs
- 22 High importance bugs
- 2 Incomplete bugs
Bug day end total open bugs: 231
- 0 New bugs
- 33 In-progress bugs
- 4 Critical bugs
- 16 High importance bugs
- 10 Incomplete bugs
Thanks again everyone!