Archive for the ‘OpenStack’ Category

New Gerrit and Jenkins styles are live

Март 21st, 2012
After a bit of tweaking and improvements following feedback from various people the new changes to Jenkins and Gerrit are now live. The changes will also be rolled out onto Stackforge in the next 24 hours.

I've had a lot of great feedback in the few hours the changes have been live, many love it and some have suggestions for improvements. This is great, we know the look could use a bit of refining here and there. What makes this truly awesome is that the styles are kept in an OpenStack project with which anyone can file bugs or send patches up to Gerrit.

To modify the styles simply grab the openstack-ci-puppet repo and look in the Gerrit and Jenkins modules for the files. If you wish to file a bug, please do so in the OpenStack CI bugs page.

Thanks again for the great feedback so far. Hopefully this has made the lives of many of you that little bit easier (or at least stop your eyes bleeding).

PlanetMySQL Voting: Vote UP / Vote DOWN

High Availability in OpenStack

Март 21st, 2012

A few thoughts on high availability features (or the current absence thereof) in OpenStack.

I've just proposed a session for the OpenStack Folsom design summit which Jay Pipes was nice enough to invite me to (thanks!), and I thought I'd write up a few thoughts of mine ahead of time to get the discussion started.

read more


PlanetMySQL Voting: Vote UP / Vote DOWN

The real way to start hacking on OpenStack

Март 15th, 2012
I've seen recent attempts at blog posts to show how to get started at hacking on an OpenStack project.  Unfortunately they seem to have over-complicated the issue for new users.  As part of the Core Infrastructure team it is my job to make submitting, reviewing and merging code easier for developers.  This includes documenting that process, so here goes :)

  1. You need a Launchpad account and need to be joined to the Openstack team.  You can also join the team of one of the many subprojects if you want to.  Make sure Launchpad has your SSH key, Gerrit (the code review system) uses this.
  2. Sign the CLA as outlined in section 3 of the How To Contribute wiki page
  3. Tell git your details:
    git config --global user.name "Firstname Lastname"
    git config --global user.email "your_email@youremail.com"
  4. Install git-review. This tool takes a lot of the pain out of remembering commands to push code up to Gerrit for review and to pull it back down to edit it. It is installed using:
    pip install git-review
    Several Linux distributions (notably Fedora 16 and Ubuntu 12.04) are also starting to include git-review in their repositories so it can also be installed using the standard package manager.
  5. Grab a tree to hack on, for example for Nova you would do:
    git clone git://github.com/openstack/nova.git
  6. Checkout a new branch to hack on:
    git checkout -b TOPIC-BRANCH
  7. Start hacking
  8. Run the test suite locally to make sure nothing broke
  9. Commit your work using:
    git commit -a
    or you can use the following to edit a previous commit:
    git commit -a --amend
  10. Push the commit up for code review using:
    git review
    That is the awesome tool we installed earlier that does a lot of hard work for you
  11. Watch your email or review site, it will automatically send your code for a battery of tests on our Jenkins setup and the core team for the project will review your code. If there is any changes that should be made they will let you know.
  12. When all is good the review site will automatically merge your code
Obviously nearly half of that list are tasks you will only need to perform once. So as you can see it is pretty darn simple to get started. If anyone gets stuck they are welcome to shout out in the #openstack-dev IRC channel or the OpenStack mailing list. For more information on developer work flow please see the Gerrit Workflow page, I'm not ashamed to say I still have it as a pinned tab :)

PlanetMySQL Voting: Vote UP / Vote DOWN

Changes coming to Gerrit’s style

Март 13th, 2012
Gerrit is a fantastic tool for performing code reviews and automating many of the tasks which can become quite complex. Unfortunately its default style is not the most attractive thing to look at all day. Yesterday I was tasked with skinning Gerrit to make it more in-line with Openstack. This was not as easy a task as I first anticipated, mostly down to not having the ability to edit the HTML layout very much without editing Gerrit's source.

The result isn't perfect but hopefully a notable improvement which will be coming to an Openstack review site near you soon.  Here is the before and after shots:

PlanetMySQL Voting: Vote UP / Vote DOWN

A Change in Direction

Январь 18th, 2012
In 2008 my career took a sudden unexpected turn into the world of MySQL when I was offered a job at Sun.  Since then MySQL and it's forks have been a big part of my life.  The whole community (I mean the people, not the companies) around MySQL are part of what really drove me.

Unfortunately to me something has changed.  I am not exactly sure what it is, but I am sure it is not just me because others have expressed it in conversation too.  I wasn't enjoying things as much as I used to and for several reasons, some related to this, I have been quite ill.

Recently I was approached by HP's new cloud division who wanted me to work on OpenStack.  It seemed the perfect opportunity to start something new inside a new vibrant community.  That is not to say I have anything against my previous employer, SkySQL.  They are doing a fantastic job with a great vision and I wish them well in the future.

So, I have been working on OpenStack's Core Infrastructure team for a week and a half now and so far I am loving it.  The community is very welcoming and it is refreshing to see a development model similar to the one used in Drizzle so widely adopted.  I look forward to diving deeper into the OpenStack world and blogging about it as I go.

PlanetMySQL Voting: Vote UP / Vote DOWN

451 CAOS Links 2011.10.07

Октябрь 7th, 2011

OpenStack Foundation. New Pentaho CEO. And more.

# Rackspace announced its intention to form an independent OpenStack Foundation.

# HP has chosen Ubuntu as the lead host and guest operating system for its Public Cloud.

# Pentaho appointed Quentin Gallivan as its new CEO.

# Hortonworks continued the discussion about contributions to Apache Hadoop.

# Bob Bickel explained why CloudBees is not, itself, open source.

# Google announced the limited preview release of Google Cloud SQL.

# Eucalyptus Systems, Nebula and Virtual Bridges joined the Linux Foundation.

# Dave Neary discussed the different types of community in relation to the Tizen project.

# Akamai joined the OpenStack community.

# Daniel Abadi provided his perspective on Oracle’s NoSQL Database.

# One more thing…
Apple’s relationship with open source may be somewhat tenuous – Paul Rooney provides some background – but given the impact Steve Jobs has made on the industry as a whole it seems wrong not to mark his passing in some way. We’ll leave the words to the company he created.


PlanetMySQL Voting: Vote UP / Vote DOWN

CAOS Theory Podcast 2011.09.30

Сентябрь 30th, 2011

Topics for this podcast:

*Cloud M&A potential around OpenStack
*Oracle’s commercial extensions for MySQL
*Puppet Labs rolls out Enterprise 2.0, hosts PuppetConf
*Basho bolsters Riak distributed data store in NoSQL race
*Our latest special CAOS report, ‘The Changing Linux Landscape’

iTunes or direct download (25:59, 4.4MB)


PlanetMySQL Voting: Vote UP / Vote DOWN

451 CAOS Links 2011.09.07

Сентябрь 7th, 2011

HP builds Cloud Services on OpenStack. Linux on Github. And more.

# HP announced the private beta program of its OpenStack-based HP Cloud Services.

# Linus Torvalds made Linux 3.1 available on Github, albeit temporarily.

# The National Security Agency proposed a new database, Accumulo, to the Apache Foundation for incubation.

# Nominations for the Document Foundation board elections are now open.

# Fouriertransform invested $3m in automotive infotainment application developer Pelagicore AB.

# LibreOffice and OpenOffice.org are drifting apart.

# Luis Villa explained license compatibility in the context of MPL 2.0.

# The Swiss Parliament’s control committee for the Federal Court is allowing the publication as open source software of Open Justitia.


PlanetMySQL Voting: Vote UP / Vote DOWN

451 CAOS Links 2011.09.07

Сентябрь 7th, 2011

HP builds Cloud Services on OpenStack. Linux on Github. And more.

# HP announced the private beta program of its OpenStack-based HP Cloud Services.

# Linus Torvalds made Linux 3.1 available on Github, albeit temporarily.

# The National Security Agency proposed a new database, Accumulo, to the Apache Foundation for incubation.

# Nominations for the Document Foundation board elections are now open.

# Fouriertransform invested $3m in automotive infotainment application developer Pelagicore AB.

# LibreOffice and OpenOffice.org are drifting apart.

# Luis Villa explained license compatibility in the context of MPL 2.0.

# The Swiss Parliament’s control committee for the Federal Court is allowing the publication as open source software of Open Justitia.


PlanetMySQL Voting: Vote UP / Vote DOWN

What VMware’s Cloud Foundry announcement is about

Апрель 13th, 2011

I chatted today about VMware's Cloud Foundry with Roger Bodamer, the EVP of products and technology at 10Gen. 10Gen's MongoDB is one of three back-ends (along with MySQL and Redis) supported from the start by Cloud Foundry.

If I understand Cloud Foundry and VMware's declared "Open PaaS" strategy, it should fill a gap in services. Suppose you are a developer who wants to loosen the bonds between your programs and the hardware they run on, for the sake of flexibility, fast ramp-up, or cost savings. Your choices are:

  • An IaaS (Infrastructure as a Service) product, which hands you an emulation of bare metal where you run an appliance (which you may need to build up yourself) combining an operating system, application, and related services such as DNS, firewall, and a database.

    You can implement IaaS on your own hardware using a virtualization solution such as VMware's products, Azure, Eucalyptus, or RPM. Alternatively, you can rent space on a service such as Amazon's EC2 or Rackspace.

  • A PaaS (Platform as a Service) product, which operates at a much higher level. A vendor such as handles all the back-end services and just exposes an API to which you program.

By now, the popular APIs for IaaS have been satisfactorily emulated so that you can move your application fairly easily from one vendor to another. Some APIs, notably OpenStack, were designed explicitly to eliminate the friction of moving an app and increase the competition in the IaaS space.

Until now, the PaaS situation was much more closed. VMware claims to do for PaaS what Eucalyptus and OpenStack want to do for IaaS. Vmware has a conventional cloud service called Cloud Foundry, but will offer the code under an open source license. Right Scale has already announced that you can use it to run a Cloud Foundry application on EC2. And a large site could run Cloud Foundry on its own hardware, just as it runs VMware.

Cloud Foundry is aggressively open middleware, offering a flexible way to administer applications with a variety of options on the top and bottom. As mentioned already, you can interact with MongoDB, MySQL, or Redis as your storage. (However, you have to use the particular API offered by each back-end; there is no common Cloud Foundry interface that can be translated to the chosen back end.) You can use Spring, Rails, or Node.js as your programming environment.

So open source Cloud Foundry may prove to be a step toward more openness in the cloud arena, as many people call for and I analyzed in a series of articles last year. VMware will, if the gamble pays off, gain more customers by hedging against lock-in and will sell its tools to those who host PaaS on their own servers. The success of the effort will depend on the robustness of the solution, ease of management, and the rate of adoption by programmers and sites.


PlanetMySQL Voting: Vote UP / Vote DOWN