The OpenStack Blog

Category: Partner

New Foundation Gold Members & Corporate Sponsors

The OpenStack Foundation was thrilled to add two new Gold Members and 13 corporate sponsors so far this year to the already impressive list of companies who are supporting the Foundation and driving innovation on the platform.    Ericsson and Juniper Networks won the OpenStack Board’s approval at the April board meeting and joined the Foundation as Gold members.  To learn more about these companies and their OpenStack initiatives please visit www.ericsson.com and www.juniper.net

We’ve also seen amazing support in Corporate Sponsorship and we want to share the impressive list of recent additions.

The diversity in technologies and geographic location of these new additions to the ecosystem reflects the growth of OpenStack and its footprint worldwide.  We are looking forward to enjoying each these companies’ unique contributions going forward!

An introductory tour of OpenStack Cloud Messaging as a Service

Post by Mark Atwood, Director of OpenSource Engineering for HP Cloud

5.23.13-Cloud-Messaging

The need for well understood intra-application messaging was one of the signs that new application design patterns beyond just the LAMP stack were needed.

The need for an OpenStack Messaging Service was recognized by the San Diego Grizzly Summit, and in an unconference track design meeting on the last day, a crowd of interested people met, talked out some requirements, and from that the OpenStack Message Bus project was born. It was codenamed “Marconi”, in honor of Guglielmo Marconi, the inventor of wireless messaging. The Marconi team collaborates on Launchpad.

At the same time, HP was looking for a way to make it’s already under development application messaging service available to users of the HP Cloud. When the Marconi project appeared, HP decided that instead of splitting the developer community in a pointless API standards war, it made more sense to clone and track the public Marconi API, and then contribute to open source Marconi project itself.

As part of the development process, HP is running the messaging service in “developer preview”, meaning that you have to ask to be enrolled in the preview program to access it, and neither the service nor the API are stable. Oh, and right now it is free of charge.

Log into your HP Cloud account, and then go to the URL https://account.hpcloud.com/services and look for “Beta Services” and then “Request Access” to “Messaging”. Your request will be reviewed, and then activated. This can potentially take a couple of days, because there are human beings in this decision loop.

All parts of OpenStack and HP Cloud are controlled via RESTful APIs, and Messaging is no exception. We will access the raw API with the cURL command line tool. Using a specialized client tool can be simpler to use, and such tools are under development. However, walking this process step by step the first time helps build an understand of how all the parts work.

First thing we need is the API credentials to your HP Cloud account.

After logging into your HP Cloud account, go to the URL https://account.hpcloud.com/account/api_keys and look for following information:

  • “Project ID”, something like “58345815996918″
  • “Access Key #1″, something like “2DJ3Z58RZB5JJ7V2JKS3″
  • “Show Secret Key”. When you click on it, it will reveal something like “bPH13haenb/DlvR1th+u4Uj5ehvYKsF7ApYact6i”
  • The URL for “Identity” “region-a.geo-1″. It will be something like https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/
  • The URL for “Messaging” “region-a.geo-1″. It will be something like https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918

Now open a text editor, and construct a file named keystone-req.json with JSON contents like the following, only with your own access key, secret key, and tenant id (aka “project id”).

{
"auth": {
"apiAccessKeyCredentials": {
"accessKey": "2DJ3Z58RZB5JJ7V2JKS3",
"secretKey": "bPH13haenb/DlvR1th+u4Uj5ehvYKsF7ApYact6i"
},
"tenantId": "58345815996918"
}
}

Now, at the command prompt, run the following cURL command. Notice that the URL is the one for “Identity” “region-a.geo-1″ we looked up earlier, with the path part “/tokens” appended to it.

curl -X POST -H "Content-Type: application/json" \
https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/tokens \
-d @keystone-req.json \
| python -mjson.tool > keystone-rsp.json
Notice that we pipe the output through "python -mjson.tool". This is a useful trick for prettyprinting JSON to make it more readable.

Open up the resulting file keystone-rsp.json in a text editor, and take a look.

Search down for the string “token”, and you should see something lilke

"token": {
"expires": "2013-05-21T12:38:16.962Z",
"id": "HPAuth10_3e1c44e527f0e64387ff0705e1b09d0ca3ef47c47a6c6afe1738d77f896b4f20",
"tenant": {
"id": "58345815996918",
"name": "[email protected]"
}
},

The important part is the “access.token.id” value. We are going to paste that string into the HTTP X-Auth header for the next few cURL commands.

Now search the file for the string “hpext:messaging”, and you will find a block of JSON that looks like this:

{
"endpoints": [
{
"publicURL": "https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918",
"publicURL2": "",
"region": "region-a.geo-1",
"tenantId": "58345815996918",
"versionId": "1.1",
"versionInfo": "https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1",
"versionList": "https://region-a.geo-1.messaging.hpcloudsvc.com"
}
],
"name": "Messaging",
"type": "hpext:messaging"
},

The “publicURL” is the URL we can use to issue REST commands to the Messaging service. Here is how we list all the queues we can use. Notice that we pass the keystone authentication token in on the X-Auth-Token header.

curl -X GET -H "Content-Type: application/json" \
-H "X-Auth-Token: HPAuth10_3e1c44e527f0e64387ff0705e1b09d0ca3ef47c47a6c6afe1738d77f896b4f20" \
https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918/queues \
| python -mjson.tool

We will probably see

{
"queues": []
}

which means, logically enough, no queues have been created.

Let’s create one. We change the method to PUT and append queues/foo to create a queue named “foo”. There is no need to use the JSON prettyprinter, because no request body will be returned.

curl -X PUT -H "Content-Type: application/json" \
-H "X-Auth-Token: HPAuth10_3e1c44e527f0e64387ff0705e1b09d0ca3ef47c47a6c6afe1738d77f896b4f20" \

https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918/queues/foo

And then let’s again list all the queues.

curl -X GET -H "Content-Type: application/json" \
-H "X-Auth-Token: HPAuth10_3e1c44e527f0e64387ff0705e1b09d0ca3ef47c47a6c6afe1738d77f896b4f20" \
https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918/queues \
| python -mjson.tool

which returns

{
"queues": [
{
"name": "foo"
}
]
}

Look at that that! A queue named foo.

Now let’s put something on that foo queue. We do that by POSTing some JSON to the queue URL with the path part “/messages” appended, like so:

curl -X POST -H "Content-Type: application/json" \
-H "X-Auth-Token: HPAuth10_3e1c44e527f0e64387ff0705e1b09d0ca3ef47c47a6c6afe1738d77f896b4f20" \
https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918/queues/foo/messages \
-d '{ "body": "Hello World!" }'

And then read it back.

curl -X GET -H "Content-Type: application/json" \
-H "X-Auth-Token: HPAuth10_3e1c44e527f0e64387ff0705e1b09d0ca3ef47c47a6c6afe1738d77f896b4f20" \

https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918/queues/foo/messages

which will remove the item and display

{"id":"b41ea44e-3962-4010-80ad-4f87dcd6ba8d","body":"Hello World!"}
And then let’s delete the queue

curl -X DELETE \
-H "X-Auth-Token: HPAuth10_3e1c44e527f0e64387ff0705e1b09d0ca3ef47c47a6c6afe1738d77f896b4f20" \

https://region-a.geo-1.messaging.hpcloudsvc.com/v1.1/58345815996918/queues/foo

As always, if you have any questions, send us an email. You can contact me directly at [email protected]

..m

Here is what happens inside Nova when you provision a VM

At the Essex conference summit this past month, we presented a session on  OpenStack Essex architecture. As a part of that workshop we visually demonstrated the request flow for provisioning a VM and went over Essex arthicture. There was a lot of interest in this material; it’s now posted in Slideshare:

In fact, we’ve packaged up the architecture survey/overview as part of our 2-day Bootcamp for OpenStack. The next session is scheduled 14-15 June. This time around will carry out the training at the Santa Clara CA offices of our friends at Nexenta. Last course was delivered at our Mountain View office right before the OpenStack summit in April to a sold out crowd. You can find more information about the course at www.mirantis.com/training

I hear the Essex Train a-coming

With Essex train in the wilds of testing, and the Essex release intended date less than 10 days away, we are pretty excited about everyone descending on San Francisco — practically our home town — for the Design Summit and Conference.

Here at Mirantis, the company famous across OpenStack community for distributing vodka bottles at OpenStack meetups, we are gearing up in a big way for the summit and conference. If you haven’t seen the agenda, here’s what we’ve got teed up:

(1) We’ll start the frenzy with Just-in-time-Training: we have a few seats left at our 2-day OpenStack Boot Camp, crammed into the weekend of April 14-15, right before the summit and conference. REGISTER HERE and come to the event fully prepared to torment speakers and presenters with insidious technical questions about OpenStack technology and its future.

(2) Our team will participate in / moderate a few exciting sessions during the conference: OpenStack and Block Storage, OpenStack and High Performance Computing, Expanding the Community. Please be sure to pay us a visit.

(3) …and just to show how happy we are to have you here, we invite everyone at the conference to join Mirantis Summit Kick-Off Party. This is how we party at Mirantis! Vodka bottles and fun times in the best traditions of all our events are guaranteed. Be sure not to miss.

Looking forward to receiving everyone at the 2012 OpenStack Design Summit and Conference.

OpenStack in Production – Event Highlights

As a matter of tradition at this point, we offer a photo report, covering OpenStack event series that Mirantis hosts. Our December 14th event focused on sharing experience around running OpenStack in production. I moderated a panel consisting of Ken Pepple – director of cloud development at Internap, Ray O’Brian – CTO of IT at NASA and Rodrigo Benzaquen – R&D director at MercadoLibre.

This time we went all out and even recorded the video of the event: http://vimeo.com/33982906

For those that are not in the mood to watch this 50 minute panel video, here is a quick photo report:


We served wine and beer with pizza, salad and deserts…


…While people ate, drank, and mingled…


…and then they drank some more…


We started the panel with myself saying smart stuff about OpenStack. After the intro we kicked off with questions to the panel.


The panelists talked…


…and talked…


…and then talked some more.


Meanwhile, the audience listened…


…and listened.


Everyone in our US team was sporting these OpenStack shirts.


At the end we gave out 5 signed copies of “Deploying OpenStack” books, written by one of our panelists – Ken Pepple. Roman (pictured above) did not get a copy.

Great Turnout at the first Austin OpenStack Meetup

.

Last Thursday, a number of us Austin OpenStack fans decided to get together and talk OpenStack, Diablo, Crowbar, and more.

We had a fantastic turnout of almost SEVENTY people who came out that night – almost at near capacity for our venue, Tech Ranch Austin.  A number of startups where represented, as well as a number of notable OpenStack partners like Rackspace, Canonical, and Dell (the company I work for), who sponsored this first OpenStack meet up in Austin.

This meetup coincided with the Rackspace Cloud Builders OpenStack training, being held at the Dell campus that entire week, so a number of OpenStack students from that class, many who had flown in for class from out of town / state, were able to make it as well.

It was a great pleasure for us here at Dell to sponsor the first Austin meetup for OpenStack, and I look forward to our community growing as other partners help us sponsor future meet ups.

You can get more details on what was discussed at the meetup at Rob’s blog – www.RobHirschfeld.com.

If you’re in the Austin area, and are interested in joining the OpenStack Austin meetup group, join us at www.meetup.com/OpenStack-Austin.

Rackspace Running OpenStack Compute Today for Select Customers, Discusses Broader Rollout Plans

Lew Moorman, President of the Rackspace Cloud, recently discussed the state of Rackspace’s OpenStack plans in a blog post.

In addition to running OpenStack Object Storage (code named Swift) for over a year to power their cloud, Rackspace is now running OpenStack Compute (code named Nova) for select customers. Head over to the Rackspace Cloud blog to learn more.

They also recently announced dates for training classes on OpenStack, and will be in full attendance at the OpenStack Conference in Boston next month.

HP Announces Private Beta Program for OpenStack Cloud

Today HP announced the private beta program for HP Cloud Services.  Our initial cloud services are HP Cloud Compute and HP Cloud Object Storage, both based on HP’s world-class hardware and software combined with OpenStack ™ technology.   I  want to personally invite you to sign up for our free private beta to develop, test and run your applications. To register, simply visit www.hpcloud.com. We are accepting only a limited number of private beta applicants—so register early.

As we announced in July, HP is taking an active role in the community and we are looking forward to seeing many of you at the upcoming OpenStack Design Summit and OpenStack Conference.

Read the blog entry!

OpenStack Conference – Call for Speakers

On behalf of the OpenStack Conference Program Committee, I am pleased to initiate the Call for Speakers for the Fall 2011 OpenStack Conference in Boston, MA from October 5-7.  This gathering of OpenStack developers, users, eco-system partners, open source enthusiasts, and cloud computing technologists presents speakers with the opportunity to actively participate in the shaping of the future of the OpenStack project. I look forward to joining with the community in Boston for an amazing 3 days of OpenStack goodness.

PROCESS
The Program Committee has listed a series of suggested topics for the overall agenda of the conference. Please review these topics and submit your talk under the various topic(s). Of course, if you have an idea for a topic not listed, please send your information as the Program Committee is always open to new ideas.

To submit your request to be a speaker please send an email to [email protected] with the Subject Line: OPENSTACK CONFERENCE SPEAKER SUBMISSION. In the email be sure to include your contact information as well as the topic you are interested in speaking on. Should you submit a new topic, please provide details on that topic.

TOPICS
The topics suggested by the Program Committee fit under two umbrella categories:  technical or business. Each session is currently planned for 30 minutes.

Technical
Project Overview – NOVA
Project Overview -  SWIFT
Project Overview – GLANCE
Community Developer Tools
OpenStack in the Data Center
OpenStack Deployments
DevOps
Project Introductions – Information on the various eco-system projects not yet core in OpenStack

Business
Economics of OpenStack
OpenStack Case Study
Project Overview – NOVA
Project Overview -  SWIFT
Project Overview – GLANCE
Building an OpenStack Practice (Solution Providers)
OpenStack Case Study
Public Cloud Hosting Best Practices
Private Clouds Hosting Best Practices

The Program Committee anxiously awaits your speaker submission as we assemble the final OpenStack Conference Agenda. The deadline to submit your request is September 6, 2011 so that we can release the final agenda on September 14, 2011. All speakers selected will receive a complementary pass to the event via a special registration code. If you have any further questions, please contact me.

Some OpenStack Pictures from OSCON

Here are a few shots of the OpenStack booth at OSCON being supported by our amazing ecosystem partners during a slow time when I could get away from the crowds to take a shot. I also took a picture of the great OpenStack cake from our birthday with the tasty cupcakes.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Back to top