tag:blogger.com,1999:blog-88259922024-03-07T15:21:06.089-08:00Electric Duncani t a l l c o m e s d o w n t o I / O , e v e n t u a l l yUnknownnoreply@blogger.comBlogger7125tag:blogger.com,1999:blog-8825992.post-4345031384791216332013-04-23T16:55:00.000-07:002013-04-23T16:55:39.186-07:00OpenStack Developer Summit: Heat Followup<div class="separator" style="clear: both; text-align: center;">
<a href="http://2.bp.blogspot.com/-2hnHY6RH64w/UVxf7PCDPvI/AAAAAAAAAEI/F2fdJljI62g/s1600/openstack-logo52.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://2.bp.blogspot.com/-2hnHY6RH64w/UVxf7PCDPvI/AAAAAAAAAEI/F2fdJljI62g/s1600/openstack-logo52.png" height="200" width="200" /></a></div>
Folks are finally starting to recover from the OpenStack Developer Summit that was held in Portland, Oregon recently. All reports indicate that it was a truly phenomenal experience, record-breaking in many ways, and something that has inspired incredible enthusiasm within the community. And that's great news, since there's an enormous amount of work to be done this release ;-)<br />
<br />
Of particular <a href="http://technicae.cogitat.io/2013/04/autoscale-and-orchestration-heat-of.html">importance to many</a> in the community is the work around maturing the autoscaling feature in <a href="https://wiki.openstack.org/wiki/Heat">OpenStack Heat</a>. There was a fantastic session at the summit, facilitated by the bow-tied and most dapper Ken Wronkiewicz (<a href="http://www.rackspace.com/blog/the-heat-is-on-for-autoscaling-at-openstack-summit-portland/">his notes from the Summit</a> were published on the Rackspace blog). <br />
<br />
In preparation for the session, the following resources were created:<br />
<ul>
<li><a href="https://blueprints.launchpad.net/heat/+spec/heat-autoscaling">https://blueprints.launchpad.net/heat/+spec/heat-autoscaling</a></li>
<li><a href="https://etherpad.openstack.org/heat-autoscaling">https://etherpad.openstack.org/heat-autoscaling</a></li>
<li><a href="http://summit.openstack.org/cfp/details/172">http://summit.openstack.org/cfp/details/172</a> </li>
</ul>
That one in the middle is important, as it is also where notes were taken during the actual session itself (see the section entitled "ODS Session Notes"). Devs at Rackspace have started going through the notes from the session and started planning work around this -- all of which will be carried on in the open, on the OpenStack mail list (tagged with "[Heat]"), on Freenode, and on <a href="https://github.com/openstack/heat/">github</a>/<a href="https://review.openstack.org/#/q/status:open,n,z">gerrit</a>.<br />
<br />
The discussion at the Summit indicated strong interest in building a REST API for the existing autoscaling feature. Needless to say, there is a lot involved in this, touching upon significant OpenStack components like Quantum, LBaaS, and Ceilometer. Once the appropriate code is in place, a REST API will need to be created, features will need to be expanded/added, etc., and we'll be off and running :-)<br />
<br />
Lots to do, and lots of great energy and excitement around this to keep us all chugging through this cycle.<br />
<br />
On that note, we'd like to send out a special "thanks" to all the countless folks who worked so hard to make ODS happen. This event anchors us in a most excellent way, providing the insight and fuel that supports future development work so well!<br />
<br />
<br />Anonymousnoreply@blogger.com1tag:blogger.com,1999:blog-8825992.post-72150234957210582982013-04-03T10:03:00.000-07:002013-04-03T19:19:53.384-07:00Autoscale and Orchestration: the Heat of OpenStack<div class="separator" style="clear: both; text-align: center;">
<a href="http://2.bp.blogspot.com/-2hnHY6RH64w/UVxf7PCDPvI/AAAAAAAAAEE/baimMc7CxHM/s1600/openstack-logo52.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="200" src="http://2.bp.blogspot.com/-2hnHY6RH64w/UVxf7PCDPvI/AAAAAAAAAEE/baimMc7CxHM/s200/openstack-logo52.png" width="200" /></a></div>
Several months before I joined Rackspace last year, there were efforts under way to provide an Autoscaling solution for Rackspace customers. Features that we needed in OpenStack and Heat hadn't been released yet, and there were no OpenStack experts on the Autoscaling team. As such, the engineers began developing a product that met Rackspace customer needs, integrated with the<br />
existing monitoring and load-balancing infrastructure, and made calls to OpenStack Nova APIs as part of the scaling up and down process.<br />
<br />
At PyCon this year, Monty Taylor, Robert Collins, Clint Byrum, Devananda van der Veen, and I caught up and chatted about what their views were of the current status of autoscaling support in OpenStack Heat. It seems that the two pieces we need the most -- LBaas and support for external monitoring systems (perhaps via webhooks) -- are nascent and not ready for prime-time yet. Regardless, Monty and his team encouraged us to dive into Heat, contribute patches, and in general, release our work for consumption by other Stackers.<br />
<br />
Deeply encouraged by these interactions, we took this information to Rackspace management and, to quote Monty Python, <a href="http://www.youtube.com/watch?v=enSYlCEz5VI">there was much rejoicing</a>. Obviously OpenStack is huge for Rackspace. Even more, there is a lot of excitement about Heat, the existing autoscaling features in OpenStack, and getting our engineers involved and contributing to these efforts.<br />
<br />
In the course of these conversations, we discovered that Heat was getting lots of attention internally. It turns out that another internal Rackspace project had been doing something pretty cool: they were experimenting with the development of a portable syntax for application description and deployment orchestration. Their work had started to converge on some of the functionality provided by Heat, and they had a similar experience as the Autoscaling team. The timing was right to contribute what they have learned and align all of their continued efforts with adding value to Heat.<br />
<br />
Along these lines, we are building <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-April/007126.html">two new teams</a> that will focus on Heat development: one <br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://3.bp.blogspot.com/-UTNPsMlxcvY/UQBSsj_BQWI/AAAAAAAAADA/SZjwtfYECMw/s1600/RackspaceLogoMedium.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="200" src="http://3.bp.blogspot.com/-UTNPsMlxcvY/UQBSsj_BQWI/AAAAAAAAADA/SZjwtfYECMw/s200/RackspaceLogoMedium.png" width="191" /></a></div>
contributing to features related to autoscaling (not necessarily limited to Heat) and the other contributing to the ongoing conversations regarding the separation of concerns between orchestration and configuration management. Everyone -- from engineers to management -- is very excited about this new direction in which our teams are moving. Not only will it bring new developers to OpenStack, but it is aligning our teams with Rackspace's OpenStack roots and the company's vision for supporting the growing cloud community.<br />
<br />
Simply put: we're pretty damned pumped and looking forward to more good times with OpenStack :-)<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
Anonymousnoreply@blogger.com0tag:blogger.com,1999:blog-8825992.post-1344094677348473332012-05-14T23:00:00.000-07:002012-05-15T12:05:32.334-07:00CERN, OpenStack Keep Resonance Cascades at Bay<table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjljJ4dZlMqFZFYQfiLDBqhwW6MNfquz0FgbZePMEAMWVc4cZ9Oya2ROkVPnoCsVMvsz3bwdq6MuuhFWtsl3sf_8lgWzGzhCxjoezkp612vCY_UeMyX-kTmjF4n6mr87gdJ1zsm/s1600/Gordonfreeman.jpg" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjljJ4dZlMqFZFYQfiLDBqhwW6MNfquz0FgbZePMEAMWVc4cZ9Oya2ROkVPnoCsVMvsz3bwdq6MuuhFWtsl3sf_8lgWzGzhCxjoezkp612vCY_UeMyX-kTmjF4n6mr87gdJ1zsm/s200/Gordonfreeman.jpg" width="156" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Tim Bell preparing to get his <br />
OpenStack on</td></tr>
</tbody></table>
<span style="font-family: inherit;">As <a href="http://cogitat.io/2012/04/new-life-openstack-devops-community.html" target="_blank">previously mentioned</a>, there's a growing momentum around ops-oriented participation in the <a href="http://openstack.org/" target="_blank">OpenStack</a> community. <a href="http://dreamhost.github.com/" target="_blank">DreamHost</a> is deeply invested in DevOps, seeing how that's where we're going to be living in a few months! As <a href="http://www.linkedin.com/in/simonanderson" target="_blank">Simon Anderson</a>, CEO of DreamHost, recently said:</span><br />
<blockquote class="tr_bq">
<span style="font-size: large;">"When we're running a complex fabric of apps on over 5,000 servers across three data centers, we need a lean and nimble approach to software development and operational implementation. Without a DevOps approach, we wouldn't be able to push code into production as fast or as efficiently as we do, and our customers would not be happy! Today's
developers demand up-to-the-hour security and performance updates to Internet infrastructure, so we aim to deliver just that with DevOps."</span></blockquote>
<span style="font-family: inherit;">Though expressed in the context of our work, the import of DevOps that Simon's comment generally highlights is going to be increasingly important for nearly anyone running cloud services. </span><br />
<br />
<span style="font-family: inherit;">In particular, I've been following the work of the intrepid folks at CERN. As such, this post is not about DreamHost; rather, it's a mad tale of OpenStack, DevOps, and averting alien invasion.</span><br />
<div>
<br /></div>
<div>
<span style="font-family: inherit;">After countless long-distance phone conversations, a flight to Switzerland, and spending several days buying pints for a security guard in the know (referred to from now on as "Barney"), I've uncovered some profound truths -- Mulder-style -- and have confirmed that the impact of OpenStack at CERN is huge. </span></div>
<div>
<span style="font-family: inherit;"><br /></span></div>
<div>
<span style="font-family: inherit;">Superficial examinations turn up the usual: CERN's planning </span><a href="http://cern.ch/go/Php8" style="font-family: inherit;" target="_blank">slides</a><span style="font-family: inherit;">, nice quotes, discussions of features and savings in time and money. For </span>instance<span style="font-family: inherit;">, i</span><span style="font-family: inherit;">n a recent email conversation with Tim "Gordon Freeman" Bell at CERN, I learned that </span></div>
<blockquote class="tr_bq">
<span style="font-family: inherit; font-size: large;">"The <span class="il">CERN</span> Agile Infrastructure project aims to develop <span class="il">CERN</span>'s computing resources and processes to support the expanding needs of LHC physicists and the <span class="il">CERN</span> organisation."</span></blockquote>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_M52z45R21PNUDaKd6KNJ_mbeDDCBwr8i3zhRAuZY56IsfK3WKN8wN8rA9Q1Jhc1f_cKvhqhQ0k8xzuQA_nVbdxifNvIDXEAoMFXiz3HeuAEqrmcPGS0mMf3yT__KnKxFkX-l/s1600/Gordon%252BFreeman%252BSpotted%252BAt%252BCERN%252BOpenStack.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_M52z45R21PNUDaKd6KNJ_mbeDDCBwr8i3zhRAuZY56IsfK3WKN8wN8rA9Q1Jhc1f_cKvhqhQ0k8xzuQA_nVbdxifNvIDXEAoMFXiz3HeuAEqrmcPGS0mMf3yT__KnKxFkX-l/s320/Gordon%252BFreeman%252BSpotted%252BAt%252BCERN%252BOpenStack.jpg" width="320" /></a></div>
<div>
I think these guys have been hanging out with Simon! But once you slip behind the scenes, peek at some of the whiteboards in unattended rooms, or rifle through notes lying about, you see that things are not what they appear. I've included a shot of Mr. OpenStack-at-CERN himself; this was my first clue.</div>
<div>
<br /></div>
<div>
Publicly, he's been working with other teams at CERN to:</div>
<div>
<ul>
<li>modernise the data centre configuration tools and automating operations procedures</li>
<li>exploit wide scale use of virtualisation, improving flexibility and efficiency</li>
<li>enhance monitoring such that the usage of the infrastructure can be fully understood and tuned to maximise the resources available</li>
</ul>
</div>
<div>
But privately, it seems that he and his team have been doing much, much more. This was alluded to in a statement made by team member Jan van Eldik: "We expect the number of requests to insert non-standard specimens into the scanning beam of the Anti-Mass Spectrometer to significantly decrease, once automation is in place and everyone is using the standard infrastructure we are setting up."<br />
<br />
That isn't to say there haven't been incidents...</div>
<div>
<br /></div>
<div>
Innocuously enough, the current toolchains are based around:<br />
<ul>
<li><span style="font-family: inherit;">OpenStack as a single Infrastructure-as-a-Service providing physics </span><span style="font-family: inherit;">experiment services, developer boxes, applications servers as well as the </span><span style="font-family: inherit;">large batch farm</span></li>
<li><span style="font-family: inherit;">Puppet for configuration management</span></li>
<li><span style="font-family: inherit;">Scientific Linux </span><span class="il" style="font-family: inherit;">CERN</span><span style="font-family: inherit;"> as the dominant operating system with sizeable chunk </span><span style="font-family: inherit;">of Windows installs</span></li>
</ul>
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkYIooD1tXichvxC1Y7Pk5hbuKSfqy8wYYiEa_2vPEO6CAfeuLKwtM_f7-Y-JSSkYJoQJwKrCpWFFyS3X-izyTD_4vRlKLpKV72fk3bfchJXxUCv7I0lomqHV2GWkeOtW1BO-m/s1600/crowbar.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="150" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkYIooD1tXichvxC1Y7Pk5hbuKSfqy8wYYiEa_2vPEO6CAfeuLKwtM_f7-Y-JSSkYJoQJwKrCpWFFyS3X-izyTD_4vRlKLpKV72fk3bfchJXxUCv7I0lomqHV2GWkeOtW1BO-m/s200/crowbar.jpg" width="200" /></a></div>
<div>
But that second bullet caught my eye, and one of Barney's pub mates confirmed a rumor that we'd heard: the Puppet instances are actually trained <a href="http://en.wikipedia.org/wiki/Headcrab" target="_blank">headcrabs</a>. The primary training tool? You guessed it, a crowbar. Barney said that the folks from Dell took inspiration from this and developed it further for <a href="http://content.dell.com/us/en/gen/d/cloud-computing/crowbar-software-framework" target="_blank">their OpenStack deployment framework</a> after an extended visit to CERN.<br />
<br />
<span style="font-family: inherit;">Although Barney hadn't seen any evidence of resonance cascades, there have been minor cross-dimensional disturbances as a result of some "cowboy" activity and folks not following DevOps best practices. This has been kept quiet for obvious reasons, but </span>has led to a small pest problem in some of CERN's <a href="http://www.cernlove.org/blog/2009/10/underground-cern-its-half-life/" target="_blank">older tunnel complexes</a>.<span style="font-family: inherit;"> As rouge elements are discovered, CERN has been educating transgressors </span>aggressively.<span style="font-family: inherit;"> (Sometimes they go as far as sending employees to <a href="http://half-life.wikia.com/wiki/Xen" target="_blank">Xen</a> training... or was it <a href="http://en.wikipedia.org/wiki/Xen" target="_blank">Xen</a> training?)</span><br />
<br /></div>
<div>
<table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: right; margin-left: 1em; text-align: right;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_pKnHM6PidordDoozCS0lDgNsSFvnnG1TtJyesLE7QE-RsyvkaGyU4H64jr4poWscg1W4eUK7Rbp9o9XyqnvHXMtnZ20TbafAIJFqKV6_fakf94vj7In0RKajhBqFWTMM2W63/s1600/2008-04-02-hadron-gordon-freeman.jpg" imageanchor="1" style="clear: right; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" height="213" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_pKnHM6PidordDoozCS0lDgNsSFvnnG1TtJyesLE7QE-RsyvkaGyU4H64jr4poWscg1W4eUK7Rbp9o9XyqnvHXMtnZ20TbafAIJFqKV6_fakf94vj7In0RKajhBqFWTMM2W63/s320/2008-04-02-hadron-gordon-freeman.jpg" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">One artist's conception of what success will<br />
look like for OpenStack at CERN</td></tr>
</tbody></table>
<span style="font-family: inherit;">Despite the minor </span>hiccoughs<span style="font-family: inherit;"> along the way, CERN is aiming for success. (Given the lack of Combine</span> and forced relocation programs, they're already doing better than Black Mesa's Anomalous Materials team.) <span style="font-family: inherit;">Plans are in place for an initial </span>pre-production service, <span style="font-family: inherit;">OpenStack deployment this year. Following that, they will be moving towards 300,000 virtual machines on 15,000 hosts spread across two data centres by 2015.</span><br />
<br />
<span style="font-family: inherit;">The OpenStack community is supporting them in their efforts with fantastic new features, high-quality discussions on the mail lists, and real-time interaction on the IRC channels. </span><span style="font-family: inherit;">In an act of reciprocity and community spirit, operators at CERN have volunteered to contribute back to the OpenStack community with regard to operations best practices, reference </span>architecture<span style="font-family: inherit;"> documentation, and support on the operators' mail list.</span><br />
<br />
To see how other institutions were taking this news, I spent several days waiting on hold. In particular, Aperture Science could not be reached for comment. However, Ops team member <span class="gI">Belmiro Rodrigues Moreira</span> did say that there's an audio file being circulated at CERN of Cave Johnson threatening to "burn down OpenStack" ... with lemons. Given Aperture Science's failure record with time machine development, it's generally assumed to be a prank audio reconstruction. CloudStack developers are considered to be the prime suspects, seeing how much time they have on their hands while waiting for ant to finish compiling the latest Java contributions.<br />
<br />
When asked what advice he could give to shops deploying OpenStack, Tim said simply: "Remember, the cake is a lie. Don't get distracted and don't stop. Just keep hacking."<br />
<br />
<table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: right; margin-left: 1em; text-align: right;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjsI1DVcYCXNB63mpp0oSy527cdC7cFyp6pJhX5s9G8_32QDrhOmU2hZQA4z0qX0uuMZWIU8kcQFdESPUNdLbMxLCSHvkemLQWk87Ibo_4NOmVLDpS5fgNcW2a16168LePWdDOO/s1600/20090111171621!Eli-alyx-vance.jpg" imageanchor="1" style="clear: right; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" height="213" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjsI1DVcYCXNB63mpp0oSy527cdC7cFyp6pJhX5s9G8_32QDrhOmU2hZQA4z0qX0uuMZWIU8kcQFdESPUNdLbMxLCSHvkemLQWk87Ibo_4NOmVLDpS5fgNcW2a16168LePWdDOO/s320/20090111171621!Eli-alyx-vance.jpg" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Alyx, explaining to her dad why she loves DreamHost</td></tr>
</tbody></table>
Couldn't have said it better myself.<br />
<br />
In closing, and interestingly enough, one of DreamHost's employees has an uncle who works at the Black Mesa Research Facility. Though his teleportation research team was too busy for an extended interview, <a href="http://half-life.wikia.com/wiki/Alyx_Vance" target="_blank">his daughter</a> did mention that she is a DreamHost customer and can't wait to use OpenStack while interning at CERN next summer. After all, that's what she uses to auto-scale her WordPress blog (she's in our private beta program). <br />
<br />
It's a small world.<br />
<br />
And, thanks to Tim and the rest at CERN, a safer one, too.<br />
<br />
<br /></div>Unknownnoreply@blogger.com6tag:blogger.com,1999:blog-8825992.post-34163492862185188622012-04-25T12:47:00.000-07:002012-04-25T12:47:40.656-07:00New Life: The OpenStack DevOps Community<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjK2uRAg3lTvYGXTTFienU6fX7zz-cG5oqeH2KcZNb0wS7I0IfCDIXVMzwP27sUnpOW9xhoqt5oMblsNZ-aWTswO0GWpBn-K47yHVUJO3gOkV1z6bGYolasLtWGwn2xFB2tgPqD/s1600/openstack-logo512.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjK2uRAg3lTvYGXTTFienU6fX7zz-cG5oqeH2KcZNb0wS7I0IfCDIXVMzwP27sUnpOW9xhoqt5oMblsNZ-aWTswO0GWpBn-K47yHVUJO3gOkV1z6bGYolasLtWGwn2xFB2tgPqD/s200/openstack-logo512.png" width="200" /></a></div>
Last week's OpenStack Design Summit and Conference were pretty fantastic events. Lots of great technical discussions, some good initial planning on large tasks, incredible numbers of conversations -- all of high quality! Looking back, though, I'd have to say that the high point of the event for me was what turned into the <a href="http://folsomdesignsummit2012.sched.org/event/e176414e81687b80e00b91a7fbcdf0a6" target="_blank">DevOps community brainstorm session</a> (<a href="http://etherpad.openstack.org/FolsomDevOpsTeam" target="_blank">etherpad link</a>) at the Design Summit (all etherpads are <a href="http://wiki.openstack.org/FolsomSummitEtherpads" target="_blank">here</a>).<br />
<br />
The session was approved with the title of "OpenStack and Operations: Getting Real" with a major goal of deciding whether we needed to create a new top-level project for DevOps. So it was really "New DevOps Team?" However, all that changed once we got started, and there was some amazing feedback and enthusiasm in that room. By the end of it, we were all pretty pumped up and ready to jump in with all our hands and feet!<br />
<br />
The highest-level summary for me was this: The DevOps folks in the OpenStack community really need a point to rally around. Someplace they can not only talk to each other, share stories, get advice, etc., but also where they can have their voices heard by the predominantly developer-oriented OpenStack community. Jay Pipes suggested that a new section be added to the weekly IRC team leader meetings, and as <a href="https://launchpad.net/~nova-operations" target="_blank">Nova Ops subteam</a> lead (<a href="http://wiki.openstack.org/Teams" target="_blank">teams list</a>), I volunteered to collect top issues from the DevOps (sub-)community and give these some air-time in the meetings.<br />
<br />
Some other highlights from the session:<br />
<br />
<ul>
<li><a href="http://trystack.org/">trystack.org</a> needs volunteer admins -- a great opportunity for improving the dev <-> ops interface</li>
<li><a href="http://public.web.cern.ch/public/" target="_blank">CERN</a> is deeply invested in DevOps, and wants to share data and possibly help with defining reference architectures</li>
<li>The same goes for the <a href="http://www.unimelb.edu.au/" target="_blank">University of Melbourne</a>!</li>
<li>There was a good corporate presences in the session too, rallying around a new and improved DevOps community: HP, Yahoo, AT&T, Canonical, Rackspace, DreamHost, and more (sorry if I forgot you!) </li>
</ul>
<br />
There is a tremendous amount of information that we collected, but in written form (etherpads) as well as conversations during last week's event. As this is collected, we'll be reaching out to folks via the <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">operators mail list</a>, <a href="http://planet.openstack.org/" target="_blank">blog posts</a>, <a href="https://twitter.com/#!/search/%23openstack%20AND%20%23devops" target="_blank">tweets</a>, and <a href="https://plus.google.com/s/%23openstack%20AND%20%23devops" target="_blank">Google+</a> messages. Be sure to do the same! If you've got concerns, bring them up on the mail list, we'll get some bugs filed and blueprints put together, and come up with plans for addressing these.<br />
<br />
Thanks again, everyone!<br />
<br />
<br />Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-8825992.post-14157027293855973762012-04-04T21:55:00.002-07:002012-04-05T08:14:10.181-07:00Recent Stackiness<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjK2uRAg3lTvYGXTTFienU6fX7zz-cG5oqeH2KcZNb0wS7I0IfCDIXVMzwP27sUnpOW9xhoqt5oMblsNZ-aWTswO0GWpBn-K47yHVUJO3gOkV1z6bGYolasLtWGwn2xFB2tgPqD/s1600/openstack-logo512.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjK2uRAg3lTvYGXTTFienU6fX7zz-cG5oqeH2KcZNb0wS7I0IfCDIXVMzwP27sUnpOW9xhoqt5oMblsNZ-aWTswO0GWpBn-K47yHVUJO3gOkV1z6bGYolasLtWGwn2xFB2tgPqD/s200/openstack-logo512.png" width="200" /></a></div>
<span style="font-size: large;"><b>Meetup</b></span><br />
<br />
Tomorrow is OpenStack Atlanta's second event (the first being a <a href="http://oubiwann.blogspot.com/2012/03/successful-hack-in-01-mar-2012.html">HackIn</a>). Ken Pepple is going to be talking about deploying OpenStack, something he should feel very comfortable doing, given <a href="http://shop.oreilly.com/product/0636920021674.do">his book</a> as well as <a href="http://www.networkworld.com/news/2011/102811-openstack-internap-252517.html">Internap's latest announcement</a> :-)<br />
<br />
There's more info about tomorrow's event at the <a href="http://www.meetup.com/openstack-atlanta/events/54612622/">Meetup page</a>.<br />
<br />
<span style="font-size: large;"><b>OpenStack Design Summit</b></span><br />
<br />
In a couple weeks, a bunch of us from <a href="http://dreamhost.com/">DreamHost</a> are going to be heading to the <a href="http://openstack.org/conference/san-francisco-2012/">OpenStack Summit and Conference</a> in San Francisco. There's a lot of buzz about it both inside the company, in the offices of our fellow OpenStack collaborators, and in the wider open source community. With Citrix's recent announcement, Internap's deployment, Eucalyptus' approval by Amazon, there's plenty of Cloud Drama to go around. Fortunately, the focus of the Summit and Conference is on the important positives: how to improve an extraordinary piece of software and disseminating expertise. Can't wait!<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuhCcqPNXB7ZzIDStOG0EBzi7LhzLa3Aw0HgkNXS_teh3jzrCfxz-EayvtJmmRQQkAOsDaxrP-U5UbmLmxiDj4Di5bvc-Rvyh7gnkQ9ZPDnIl5Qg8y8v80Sq_aNubDkLfQ75Cu/s1600/github-logo-2x120.gif" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuhCcqPNXB7ZzIDStOG0EBzi7LhzLa3Aw0HgkNXS_teh3jzrCfxz-EayvtJmmRQQkAOsDaxrP-U5UbmLmxiDj4Di5bvc-Rvyh7gnkQ9ZPDnIl5Qg8y8v80Sq_aNubDkLfQ75Cu/s1600/github-logo-2x120.gif" /></a></div>
<span style="font-size: large;"><b>GitHub Love</b></span><br />
<br />
Last but not least, the Dev team at DreamHost has been using <a href="https://github.com/dreamhost">Github</a> in conjunction with <a href="https://launchpad.net/">Launchpad</a> in a manner similar to how the OpenStack project does it. The increased interest in open source software in our offices is starting to make its way out to our customers, and we've got a <a href="http://dreamhost.github.com/">new web presence</a> that is the first step in supporting this new direction. We're cooking up a bunch more stuff, so be sure to check in on our repos from time to time :-)<br />
<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8825992.post-7166057004438126072012-03-12T14:07:00.000-07:002012-03-26T07:26:53.130-07:00OpenStack at PyCon 2012 Sprints!This is just a short post to give a shout out to some folks who are sprinting for OpenStack this year at PyCon. It's a small group, since the <a href="http://wiki.openstack.org/Summit/Folsom">Folsom Design Summit and Conference</a> is coming up in a few weeks. <br />
<br />
One big surprise came last night when I got an email about <a href="http://wiki.openstack.org/quantum-l3">Cisco's recent work with Layer 3</a> (<a href="https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api">blueprint</a>) support in Quantum, and there were two Cisco folks here this morning to chat about that. Mark McClain (DreamHost) is digging deep into their work right now.<br />
<br />
Yahoo! is remote-sprinting today, and they hope to be in the house tomorrow, to continue working on current improvements in <a href="https://github.com/yahoo/Openstack-DevstackPy">DevstackPy</a>. Mike Pittaro (La Honda Research), Jonathan LaCour and Doug Hellmann (DreamHost) are working with Yahoo! on that.<br />
<br />
Mike Perez (DreamHost) is hacking on some additional improvements in Horizon for different storage backend representations. We've also chatted a bit about the latest efforts in Horizon for Quantum support (Michael Fork's work). Perez is also helping out tracking some bugs down in DevstackPy.<br />
<br />
Special thanks to Mike Pittaro for improving the <a href="http://wiki.openstack.org/Sprints/PyCon2012">sprinting pages</a> on the OpenStack wiki with links to previous work and discussions!<br />
<br />
If you're keen on OpenStack and would like to dive in with some fellow hackers into the deep ends of Nova, Quantum, or Horizon, be sure to come by or pop in at #openstack-pycon on Freenode :-)<br />
<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8825992.post-75252408511358951042012-03-01T17:51:00.000-08:002012-03-01T17:53:03.458-08:00Successful Hack-In, 01 Mar 2012!DreamHost has a new core set of cloud developers now based in Atlanta, and a <a href="https://lists.launchpad.net/openstack/msg08090.html">new Meetup group</a> to go with that :-) Today there was a <a href="http://www.openstack.org/blog/2012/02/essex-openstack-global-hack-in/">global OpenStack Hack-In</a>, and I just posted a summary to our Meetup discussion page, but since I desperately need to do some blogging, I'm republishing here :-) (with some minor tweaks...)<br />
<br />
We had fun in person, there was good chatter on IRC with the Colorado
and San Francisco teams, and we had a great time digging into OpenStack
some more.<br />
<br />
Technical highlights include:<br />
<ul>
<li>testing out development deployments of OpenStack using Vagrant (some successes, some blockers)</li>
<li>testing out dev deployments of OpenStack using VirtualBox directly</li>
<li>filed some bugs for issues in horizon regarding error feedback to users and how the documentation is generated</li>
<li>dug into issues with logging and inconsistencies in datestamps</li>
<li>uncovered
some weirdness with the usage of gnu screen and hanging
services/partial devstack installs due to sudo assumptions (devstack
assumes a passwordless sudo, and will label an install as failed if it
gets hung up on the apache log tail, waiting for a password, even if the
install was successful and all the services started correctly)</li>
<li>Doug Hellmann made his <a href="https://review.openstack.org/#change,4771" target="_blank">first commit</a> upstream to OpenStack</li>
</ul>
On the non-technical, fun side:<br />
<ul>
<li>Thanks for <a href="http://www.zenoss.com/" target="_blank">Zenoss</a> for the fun swag today <img alt="smile" border="0" src="http://img1.meetupstatic.com/img/smileys/smile.gif" /> (the Zebras are still staring at me... I think they're going to be making an appearance in ToyStory 5)</li>
<li>Even more thanks to Zenoss for the offer to become an OpenStack Atlanta Sponsor (food, drinks, and swag)!</li>
<li>Thanks to <a href="http://dreamhost.com/" target="_blank">DreamHost</a> for the AMAZING coffee and danishes from <a href="http://www.germanrestaurant.com/" target="_blank">The Village Corner Restaurant/Basket Bakery</a>. Seriously. That was the best coffee I have ever had. In. My. <i>Life</i>.</li>
<li>Also, thanks DreamHost for the <a href="http://www.yelp.com/biz/cioffis-original-italian-eatery-stone-mountain" target="_blank">pizza</a> and the <a href="http://www.sweetpotatocafe.net/" target="_blank">sweet potato pies</a>!</li>
</ul>
<br />
<br />
We
took a couple snapshots of the event, and I'll be posting those soon on
the Meetup page, but for the super-impatient, they're up on Flickr
right now <img alt="smile" border="0" src="http://img1.meetupstatic.com/img/smileys/smile.gif" /><br />
<br />
<a href="http://www.flickr.com/photos/oubiwann/sets/72157629127676628/" target="_blank">http://www.flickr.com...</a><img alt="" class="brImage" src="http://img1.meetupstatic.com/img/clear.gif" width="0" /><br />
<br />
<br />Unknownnoreply@blogger.com0