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": "mark.atwood@hp.com-tenant1"
}
},

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 mark.atwood@hp.com

..m

The Havana design summit was held mid-April.  Since then the Nova team has been documenting the Havana roadmap and going full speed ahead on development of these features.  The list of features that developers have committed to completing for the Havana release is tracked using blueprints on Launchpad. At the time of writing, there are 74 blueprints listed that cover a wide range of development efforts. Russell Bryant, Nova Tech Lead, highlights some of them.

Stacker Voices: Thierry Carrez, OpenStack Foundation

Thierry Carrez handles release management for the OpenStack Foundation and is chair of the project’s Technical Committee. Thierry was involved with the earliest incarnations of OpenStack while at Rackspace. Cloudscaling’s team caught up with him at the OpenStack Summit in Portland to get Thierry’s insights into the release cycle, governance and his wish list for the project.

Swiftsync – A way to synchronize two swift clusters

Enovance was asked to migrate and synchronize two swift clusters in order to provide a customer a way to handle a swift migration easily. For that they started a project called swiftsync hosted in github.

Tips ‘n Tricks

• By Ceph: Incremental Snapshots with RBD
• By eNovance: Swiftsync – A way to synchronize two swift clusters
• By Loïc Dachary: Disaster recovery on host failure in OpenStack

Security Issues

• Nova fails to verify image virtual size (CVE-2013-2096)

OpenStack In The Wild

A new section of the weekly newsletter dedicated to users of OpenStack. If you want to showcase how OpenStack helps you (or you know somebody that uses OpenStack) please let us know: email, twitter, reddit or avian carrier will do).

• Canadian Web Hosting to Launch Public Cloud Built on OpenStack Software

Upcoming Events

• OpenStack Dublin Meetup May 22, 2013 – Dublin, Ireland Details
• 3rd London OpenStack Meetup May 23, 2013 – London, UK Details
• OpenStack DACH Day May 24, 2013 – Berlin Fairgrounds Details
• OpenStack India Meetup May 26, 2013 – Bangalore, India at Anuta Network Details
• OpenStack Israel May 27, 2013 – Tel-Aviv, Israel Details
• Australian OpenStack User Group tri-city Meetup May 27, 2013 – Australia Details
• OpenStack at CeBit Australia May 28 – 30, 2013 – Sidney, Australia Booth in Hall 4
• OpenStack CEE Day May 29, 2013 – Budapest, Hungary Details
• Building an OpenStack Cloud May 30, 2013 – Chicago, IL Details
• OpenStack meeting in Munich Jun 11, 2013 – Munich, Germany Details
• DatacenterDynamics Converged Jun 11, 2013 – Paris, France Details
• GigaOM Structure Jun 19 – 20, 2013 – San Francisco, CA Details
• OpenStack DevCamp Essen Jun 21 – 23, 2013 – Essen, Germany Details
• PyCon Australia – OpenStack Miniconf Jul 05, 2013 – Hobart, Australia Details
• OSCON 2013 Jul 22 – 26, 2013 – Portland, OR Details

Other News

• Crowbar cuts OpenStack Grizzly (“pebbles”) branch & seeks community testing
• OpenStack Grizzly Webinar Preview: Availability Zones vs. Host Aggregates
• Nested Virtualization — KVM, Intel, with VMCS Shadowing
• OpenStack Upstream University training
• A new (configurable) cgroups layout for libvirt with QEMU, KVM & LXC
• How to guarantee success of the I Design Summit in HK
• OpenStack Project Meeting:Summary and full logs.

Welcome New Developers

• Hugh Saunders
• Bruno Semperlotti
• YAMAMOTO Takashi, VALinux
• Fujioka Yuuichi, NEC

Got answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

• Trying to run pki_setup for keystone however the command doesn’t exist
• Authentication credentials are being ignored
• Instance failed to start “qemu-img: Could not open…No such file or directory”
• How to attach volume for instance (iso) on /dev/hda
• Can Openstack Choose the physical resources to boot a VM?
• What causes “cloud-init-nonet gave up waiting for a network device”?

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

2013.1.1 release, the latest in the series of stable releases. These releases are bugfix updates to Grizzly and are intended to be relatively risk free with no intentional regressions or API changes. A total of 85 bugs have been fixed in this release.

OpenStack Grizzly documentation released

We have released a version of the OpenStack official documentation for grizzly and it is now available at http://docs.openstack.org/grizzly. We continue to update docs through our continuous publishing process so feedback is always welcome. If you have questions about how OpenStack documentation is maintained or would like to get involved, see http://wiki.openstack.org/Documentation/HowTo. We had nearly 80 contributors to the documentation for the Grizzly release. Thanks to everyone who helped create and maintain accurate information for OpenStack.

Guidelines for answering question on Ask

It’s time we start collecting guidelines for the moderators so we keep having a very informative tool, with consistently good questions and answers. This wiki page hosts the draft of the Guidelines for Moderators https://wiki.openstack.org/wiki/Community/AskModerators. Comments welcome before they’re moved to their natural home on Ask OpenStack.

Discussions at Breakfast with the Board – OpenStack April 2013 Summit

The summary written by OpenStack Foundation’s Board of Directors of the things discussed during the Breakfast with the Bard in Portland, ranging from marketing to wifi, transparency to elections to what makes a contribution. A must read.

Use existing RBD images and put it into Glance

What if Glance, the OpenStack Image Service, was capable of converting images within its store, say from QCOW2 image to a RAW? Waiting for this capability to be added, Sébastien Han plays with a scenario where you have a KVM cluster backed by a Ceph Cluster and your CTO wants you to migrate the whole environment to OpenStack. Science fiction in action.

Security Issues

• Nova uses insecure keystone middleware tmpdir by default (CVE-2013-2030)
• Keystone tokens not immediately invalidated when user is deleted (CVE-2013-2059)

OpenStack In The Wild

A new section of the weekly newsletter dedicated to users of OpenStack. If you want to showcase how OpenStack helps you (or you know somebody that uses OpenStack) please let us know: email, twitter, reddit or avian carrier will do). More content from Portland Summit:

• Using OpenStack In A Traditional Hosting Environment by EIG/Bluehost

Upcoming Events

• OpenStack Atlanta Meetup May 16, 2013 – Atlanta, USA Details
• OpenStack Dublin Meetup May 22, 2013 – Dublin, Ireland Details
• 3rd London OpenStack Meetup May 23, 2013 – London, UK Details
• OpenStack DACH Day May 24, 2013 – Berlin Fairgrounds Details
• OpenStack India Meetup May 26, 2013 – Bangalore, India at Anuta Network Details
• OpenStack Israel May 27, 2013 – Tel-Aviv, Israel Details
• Australian OpenStack User Group tri-city Meetup May 27, 2013 – Australia Details
• OpenStack at CeBit Australia May 28 – 30, 2013 – Sidney, Australia Booth in Hall 4
• OpenStack CEE Day May 29, 2013 – Budapest, Hungary Details
• Building an OpenStack Cloud May 30, 2013 – Chicago, IL Details
• OpenStack meeting in Munich Jun 11, 2013 – Munich, Germany Details
• GigaOM Structure Jun 19 – 20, 2013 – San Francisco, CA Details
• OpenStack DevCamp Essen Jun 21 – 23, 2013 – Essen, Germany Details
• PyCon Australia – OpenStack Miniconf Jul 05, 2013 – Hobart, Australia Details
• OSCON 2013 Jul 22 – 26, 2013 – Portland, OR Details

Other News

• Rant about Github pull-request workflow implementation
• Open Marketing Meeting – May 15
• Fixes and upgrades to Search on OpenStack Activity Board
• OpenStack Project Meeting: Summary and full logs.

Welcome New Developers

• Matt Wagner, Redhat

Got answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

• Can I still use nova-network in Grizzly?
• VM stops boot right after initializing tun
• Why do I get “Could not find token” error using Swift with s3 API?
• How do I effectively disable/enable a tenant using the API?
• How do I debug Nova service with eclipse and pydev
• What causes error “service n-net is not running” when running stack.sh?
• How to list Server Id using python-novaclient Python API?
• Is it possible to modify a network while in use?
• How to set up metadata service on a flat network?
• Keystone remove_user command removing ALL users not just the specified ones
• How do I debug Nova service with eclipse and pydev
• ENABLE_TENANT_TUNNELS, OVS Version check in Compute fails
• How to make openstack_auth the default authentication backend for django admin?

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Tuesday morning during the Summit, we continued the tradition of Breakfast With The Board (BwtB).  We wish to thank all who participated.  As board members we very much appreciated your comments of support, feedback and ideas.  We heard many positive and encouraging comments  and participated in many lively discussions.

Through this writeup we would like to share what we heard.   There was a wide variety of topics discussed, including:

Summit Design Session Growing Pains
Despite a variety of changes tested and introduced over the past Summits, accommodating all who wish to participate in the Summit design sessions continue to exhibit growing pains.  The design sessions are “intended to be small, focused developer working sessions where the roadmap is set by active contributors on the project.”  With such a description it is easy to see why so many business persons, users, and developers want to participate or listen in. Yet the fear is that a varied large audience will decrease session output.

Many ideas were voiced at the BwtB as to how to address the issue, including room moderators, attendee prioritization, seating arrangements and session segregation.

“Scotty we need more power er WIFI”
While the conference survey will prioritize on  what items will be most relevant to improve for the next Summit, one of the vocal suggestion at the BwtB was the never ending need for more WIFI.  We techies live on WIFI.

Who the heck is…
Leading the list for reasons to attend the Summit is to simply meet people we work with on IRC and other community channels.  A simple suggestion was made that we add IRC nicks in a nice big font to the front and back of the conference badges. 50% of the time you see the back of someone’s badge and don’t know who they are.

Traveling to the Fall Summit
For those traveling to the fall Summit from the North America, concerns over prohibitive travel costs was raised.  Determining a Summit location is made up of many different factors.  Cost of travel being one.    A Summit location effects attendance, whether it be in Portland or Hong Kong.  Balancing that cost can be tricky.   The planning committee investigations concluded that attendees will find that the travel rates will not be the feared prohibitive if they do some research and book early.

Driving Priorities
Several discussions evolved around the idea of how customer priorities are injected into each projects focus and features. Typically in a corporate development model such interests are captured and formulated into the development model through Product Owners (PO) or Product Managers (PM).  How does this map to the OpenStack model?  Which is easily generalized to how does this map to the open source world?

At the BwtB, several of the discussions converged on the notion of contribution.  Contribution either in the form of code, leadership or voice.  One company simply cannot pretend to make choices for resources in another company. At most you can find other resources from a  company which share a problem you are helping describe and therefore solve.

A familiar saying in the open source world is “scratch the itch”.  It is this saying which has driven open source developers for years.  If you find a need that nothing out there can meet, write a solution yourself or better yet voice the need to help find those who share in the need and write a solution together contributing in ways that leverage your experience and expertise or providing support to those who can contribute for you.

Big Vision
Also discussed at the BwtB was the notion of having the TC play more of a role across the various projects, for things like security and API versioning, aligning and setting direction across the groups. Citing the need for the TC (or someone at least) to give more cross project consideration for:
API compatibility and consistency
architectural consistency
security
Input from Users to guide our path

Align the Doc
Opinions voiced concerns that the documentation lags the implementations.  So how do we  make the OpenStack documentation more up-to-date and improve quality and timelines?  That was the question raised by attendees at the BwtB.  Offered suggestions included a requirement for documentation changes to be checked in concurrent with the code, rather than just setting a flag that the doc’s might be effected.

What comprises OpenStack?
A couple of tables discussed the current progress around the current Core/Integrated/Incubated framework with input on moving forward; people seem to prefer the kernel/drivers analogy. There is confusion regarding the new approach to core-integrated-incubation,  what the differences are, who gets seats on the TC, etc.  Early and continued discussions at Technical Committee and Board on this are important for next phases of the effort. It is important  to ensure that the TC and Board sign off on all steps with formal statements by the foundation when we arrive at any and all conclusions.

Interoperability
There is a lot of interop interest. Folks at the BwtB seemed to be mostly happy with the refstack approach. They voiced opinions about whether API-based interop or same-codebase interop is appropriate in various projects and for having verification teams for plug-ins.

Marketing OpenStack
Where does OpenStack as the data center operating system model go?  How to support that?  Marketing discussions ranged across several of the tables.  Including a conversation at one of the tables  on how to best explain OpenStack to CIO/IT Directors. Participants in the discussion felt that the video overviews available on the OpenStack website as well as the user stories presented at the Summit Keynotes were of great help.

Others pondered why FUD is generated by open source competition with a  lack of sense of those for who their competition really should be (proprietary software).

And others voiced concern over perceptions around OpenStack.  These perceptions include, complexity, talent shortages, security gaps and that it takes too many people to run OpenStack.  Such perceptions create a barrier to adoption.

Transparency
The Board at its February meeting, launch a committee to improve transparency and foster collaboration between the foundation members and members of the board, technical committee, user committee and other committees.  Members of the committee took the opportunity to discuss, at their tables, the committee ideas and efforts.  Everyone is all for transparency and seeking a balance between transparency and compromising the strategic position of the project was accepted as an important consideration. The ombudsman and staggered release were seen as valid solutions.

Attendees also voiced the importance for direct participation within project processes.  It is important that the TC and board to listen to what the project have to say.

Elections
The Board at its February meeting also launched an effort to improve the Individual member election process.  The board members engaged in this effort took the opportunity to gather feedback at the BwtB on the ideas and efforts underway.  Many were pleased that a schedule for implementation of changes is being set and were pleased with the efforts so far.

Conclusion
As you can see there was a wide range of topics raised and discussed.  Each of which could be worthy of a full writeup on its own. As a board we appreciate the input.  We will delve into the issues further and will use this input to guide the prioritization of our efforts.  So again thank you for your participation. We look forward to the next BwtB at the fall Summit.

Regards,

OpenStack Board of Directors

In response to growing demand for deploying and running Windows based applications on OpenStack cloud, the team at Mirantis started Murano: a native OpenStack component that enables fast provisioning and operation of Windows Environments on demand.

Who Wrote OpenStack Grizzly Docs?

Sneaking a peek at the numbers for documentation along with the code should show us pointers about docs keeping up with code. Anne Gentle dives into the documentation with data and insights.

“I” release cycle naming

The next OpenStack summit will happen in Hong Kong. That creates a pretty challenging naming problem, since there is no word starting with “i’ in classic transliteration of Chinese words. So the Technical Committee is willing to bend the rules a little to extend the range of candidates… Feel free to add suggestions to the list on the wiki.

Stacker Voices: Monty Taylor, HP

Cloudscaling Engineering talked with Monty Taylor of HP (reaching rockstar status also with a wired.com profile this week) at the OpenStack Summit in Portland. Monty leads the CI (continuous innovation) project for OpenStack. In that role, he and his group have built testing systems that have made it possible for the OpenStack project to scale from a few dozen contributors for the Bexar release to more than 700 developers now pushing hundreds of patches daily to OpenStack. Watch the video on YouTube.

A little tracing hack

Timothy Daly at Yahoo! added metrics and tracing for OpenStack and released tomograph: a tool to see what and how OpenStack is doing behind the curtains.

Contribute to OpenStack Activity Board

We’ve released the complete documentation for OpenStack Insights, with binaries and source code downloadable from Sourceforge while the OpenStack Dash tools are the vanilla MetricsGrimoire set hosted on github. The code is free as in freedom so you’re welcome to play with it.

How to run pylint with few false positives

Testing your python code can get complex and with pylint, you will see false positives, meaning it will complain some lines as bugs that are actually correct. lintstack is designed to address this problem: reduce false positives from pylint as much as possible without sacrificing accuracy. Yun Mao describes how lintstack works.

Report from Previous Events

• By Alessio Ababilov: OpenStack Summit April 2013: a First Experience
• By Amar Kapadia: Coming of Age of Swift .

Tips and Tricks

• By Adam Young: Kerberizing PostgreSQL with FreeIPA for Keystone
• By Giulio Fidente: OpenStack Cinder – Add more volume nodes
• By Flavio Percoco: Dynamic TTL Collection in Mongodb for Marconi

OpenStack In The Wild

A new section of the weekly newsletter dedicated to users of OpenStack. If you want to showcase how OpenStack helps you (or you know somebody that uses OpenStack) please let us know: email, twitter, reddit or avian carrier will do). Meanwhile watch the keynotes from Portland Summit:

• Bloomberg User Spotlight
• Keynote: Comcast User Spotlight
• Keynote: Best Buy User Spotlight
• Keynote: Clouds in High Energy Physics
• Keynote: OpenStack at the National Security Agency (NSA)

Upcoming Events

• OpenStack meeting in Cologne May 04, 2013 – Cologne, Germany Details
• OpenStack Atlanta Meetup May 16, 2013 – Atlanta, USA Details
• OpenStack Dublin Meetup May 22, 2013 – Dublin, Ireland Details
• OpenStack DACH Day May 24, 2013 – Berlin Fairgrounds Details
• OpenStack India Meetup May 26, 2013 – Bangalore, India at Anuta Network Details
• OpenStack Israel May 27, 2013 – Tel-Aviv, Israel Details
• OpenStack CEE Day May 29, 2013 – Budapest Details
• Building an OpenStack Cloud May 30, 2013 – Chicago, IL Details
• OpenStack meeting in Munich Jun 11, 2013 – Munich, Germany Details
• GigaOM Structure Jun 19 – 20, 2013 – San Francisco, CA Details
• OSCON 2013 Jul 22 – 26, 2013 – Portland, OR Details

Other News

• A brief introduction to Keystone and PKI Tokens
• Glance wants to go public: the future of OpenStack Image Service
• OpenStack Common Vulnerability Database
• OpenStack Project Meeting: Summary and full logs
  • HELP: please participate to the thread that Gabriel started on API version discovery

Welcome New Developers

• Shawn Hartsock, VMwware
• David Martin, redbrick health

Got answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

• openstack tries to use cache=none when using glusterfs, when it should be writethrough
• Ceilometer BinApiTestCase fails with 503 error connecting to localhost
• Why do I get “Could not find token” error using Swift with s3 API?
• What p2v (physical to Virtual) capabilities does OpenStack have?
• Why isn’t OpenStack Swift sending metrics to Statsd server?
• “Package ‘openstack-keystone’ isn’t signed with proper key” installing OpenStack on CentOS 6.4

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Help us spread the word, and we hope to see you there!

Berlin, Germany – Friday, May 24

OpenStack DACH Day 2013 will provide attendees with first­hand insights from OpenStack developers and enterprises that are successfully using OpenStack in production environments for both private and public clouds. The lineup includes speakers from industry leaders including:

• Jonathan Bryce, OpenStack Foundation
• Kurt Garloff, Deutsche Telekom AG
• Monty Taylor, HP
• Bernhard Wiedemann & Sascha Peilicke, SUSE
• Muharem Hrnjadovic, Rackspace Cloud
• Dr. Wolfgang Schulze, Inktank
• Tobias Riedel, Netways
• Dr. Udo Seidel, Amadeus Data Processing

Register to Attend:

• When: Friday, May 24, 2013
• Where: Berlin Fairgrounds (Messegelände unter dem Funkturm), Hall 7, as part of LinuxTag
• Tickets: Registration is free, and there 200 tickets available at http://openstackdach2013.eventbrite.com

Tel Aviv, Israel – Monday, May 27

Join the OpenStack community for the third OpenStack Israel event, co-organized by OpenStack community supporters IGTCloud and GigaSpaces. The event is sponsored by the OpenStack Foundation and includes speakers from across the OpenStack community. Hear about OpenStack’s newest Grizzly release from the source, deep-dive into the Quantum network, learn about the new Cinder storage, hear what others are doing with OpenStack technology with real-life case studies from Intel, Liveperson and Alcatel, and meet the top industry leaders from IBM, HP, Rackspace, RedHat, GigaSpaces, DreamHost, Radware, Ravello, Mirantis, Cloudsoft and Hastexo.

Register to Attend:

• When: Monday, May 27, 2013
• Where: Herzilya Arts Center at 15 Jabotinsky Street in Herzilya, Israel
• Tickets: Registration is free, but there are only 300 tickets available, so register quickly! http://www.openstack-israel.org

Budapest, Hungary – Wednesday, May 29

Join us for OpenStack CEE Day – a large-scale one day user conference for the Central & Eastern European region. Attendees will get insights to OpenStack from industry-leading keynote speakers, as well as user case studies, workshops and deep dive sessions. The OpenStack CEE Day welcomes users, prospective users, ecosystem members, partners, developers and everyone who is excited about OpenStack’s open source cloud innovation.

Register to Attend:

• When: Wednesday, May 29
• Where: The Boscolo Hotel,1073 Budapest, Erzsébet körút 9-11
• Tickets: Registration is now open – http://openstackceeday.eventbrite.com

####

Check out the latest hastexo blog post about each of these events – It’s May. It must be OpenStack Month! 

Follow @OpenStack on Twitter for the latest news.

Following up on the long session hosted during the  Summit in Portland and 1-on-1 discussions, I’ve created a new topic on the Development mailing list.  You can join the conversations about OpenStack metrics and the Activity Board  avoiding the high volume traffic on the Development list by subscribing only to the Metrics topic. You’ll receive only messages that have the words [metrics] or [activity] in the subject and nothing else.  Go to http://lists.openstack.org/cgi-bin/mailman/options/openstack-dev to subscribe and pick “Metrics” among the topic categories you would like to subscribe to.

If you want to know how the OpenStack Activity Board can help you understand your team’s activities in the project, build reports, integrate data from different sources, join the webinar we’re hosting on May 9th. We’ll keep ironing out the known issues while we think about the future of the platform.

• OpenStack Design Summit Havana, from a Ceilometer point of view by Julien Danjou
• Havana Design Summit: Swift API Discussions by SwiftStack Team
• OpenStack Summit Portland Aftermath by Kyle Mestery
• OpenStack Developer Summit: Heat Followup by Duncan McGreggor
• Havana! By OpenStack Security Blog
• Portland OpenStack Summit by John Bresnahan
• Dan’s Partial Summary of the Nova Track by Dan Smith
• The Rocket Ship to Havana – OpenStack Summit Spring 2013 by Clint Byrum
• Women of OpenStack at the Portland Summit by Anne Gentle
• Michael’s surprisingly unreliable predictions for the Havana Nova release by Michael Still
• Havana Design Summit: Extending ACLs and Metadata by SwiftStack Team
• Design Summit in Portland: Day 1,Day 2, Day 3, Day 4 by eNovance
• Havana Design Summit: Swift Extensions Talk by SwiftStack Team
• Havana Design Summit: Extending ACLs and Metadata by SwiftStack Team
• OpenStack Design Summit days 1-2, days 3-4 by Elizabeth Krumbach
• “Stack Shop” cover of Macklemore’s Thrift Shop by Rob Hirschfeld and others
• The Making of Cloud of USB Sticks by eglute

OpenStack docs and tooling in 20 minutes

Howto get started with all the tooling and setup needed to build, review, and contribute to OpenStack Documentation. By Joe Heck.

How It’s Made: the OpenStack API Reference Page

The site at http://api.openstack.org is a collection of HTML pages, and one page has an especially interesting story about how it is built. Anne Gentle reveals the secret.

Storage != Transfer

John Bresnahan argues that concepts of data transfer and data storage should not be conflated into a single solution.  He believes that OpenStack can benefit from a new component that offloads the burden of optimally transferring images from existing components like nova-compute and swift.

Report from Previous Events

• 3rd Swiss OpenStack User Group Meetup

Tips and Tricks

• By Sébastien Han: Ceph and Cinder multi-backend
• By Chmouel Boudjnah :: Howto revoke a token with keystone and PKI (v2.0 API)
• By Running PostgreSQL and Mysql Unit tests in Keystone
• By SwiftStack Team: Havana Design Summit: Benchmarking Swift
• By Giulio Fidente: Deploy OpenStack Heat on RHEL (and derivates)

Upcoming Events

• OpenStack meeting in Cologne May 04, 2013 – Cologne, Germany Details
• OpenStack DACH Day May 24, 2013 – Berlin Fairgrounds Details
• OpenStack Israel May 27, 2013 – Tel-Aviv, Israel Details
• OpenStack CEE Day May 29, 2013 – Budapest Details
• Building an OpenStack Cloud May 30, 2013 – Chicago, IL Details
• OpenStack meeting in Munich Jun 11, 2013 – Munich, Germany Details
• GigaOM Structure Jun 19 – 20, 2013 – San Francisco, CA Details
• OSCON 2013 Jul 22 – 26, 2013 – Portland, OR Details

Other News

• OpenStack Project Technical Lead Interview Series #1: Mark McClain, OpenStack Networking Project 
• Crowbar and our Pivot (or, how we slipped and shipped Grizzly)
• Project Savanna Moves Ahead: Red Hat and Hortonworks are on board
• OpenStack Project Meeting: Summary and full logs

Welcome New Developers

• Tilottama Gaat, Rackspace
• Zang MingJie, None
• Jason Dunsmore, Rackspace
• James Slagle, None

Got answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

• Why is the quantum linuxbridge plugin getting sudo errors?
• How to do automated deployment of a new node?
• Is it safe to use WMI python library to manage HyperV driver from a Linux host?
• Why do I see “Unable to find authentication token in headers” using swift with staticweb?
• What’s causing permission error with Vmware Vcenter/ESX 4.1.0 on Grizzly?
• Why is the quantum linuxbridge plugin getting sudo errors?

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

• Red Hat: for extra tasty on-demand pizza as a service
• SwiNG: for a great selection of beverages
• University of Bern: for the facilities

Once we kicked off, there were five presentations, 3 which were more detailed and 2 that were more lightning talks in nature. The presentations in there running order were:

• OpenStack Quantum SDN with Open vSwitch, Redhat, Thomas Graf.
• OpenStack on SmartOS, ICCLab, Daniele Stroppa.
• Packstack, Systemx, Sandro Mathys
• OpenStack in Hepia, University of Applied Sciences Western Switzerland, Dimitri Racordon
• Impressions from the Summit in Portland, Rackspace, Muharem Hrnjadovic

Upcoming

There are other upcoming Swiss events that will include much talk of OpenStack. Of note are:

• Academic Cloud Computing Experience, April 29th.
• OpenStack DACH at LinuxTag, 24th May.
• Swiss Open Systems User Group, Open Cloud Day 2013, June 11th.

Also the Swiss Informatics Society have started a cloud computing special interest group, where all folk active in cloud are welcomed to join. More details can be found at their site.

Swiss OpenStack User Group Channels

• General Info
• Meetup site
• CHOSUG Wiki
• LinkedIn
• Mailing List
• Twitter @OpenStackCH

 Original post: ICCLab

Over 70 women attended the networking breakfast hosted by the OpenStack Foundation and lead by community leader, Anne Gentle.  During the breakfast Anne was surprised to be recognized by the Foundation with the creation of the Anne Gentle Travel Scholarship for Women named in her honor. The scholarship will continue to fund travel for women to attend future OpenStack Summits. The initial use supported three OpenStack interns who attended the Portland Summit – Laura Alves and Victoria Martinez de la Cruz from Argentina and Anita Kuno from Canada. Learn more about the Outreach Program for Women here.

To watch a glimpse of the Women of OpenStack who attended the Summit, check out this video, Getting More Women Involved in OpenStack, filmed by Rackspace Videographer, Jacob Forbis.

To get involved yourself – join the Women of OpenStack group on LinkedIn today!

Group Shot of those who attended the Breakfast for Women

Anne Gentle is recognized with a Travel Scholarship for Women named in her honor

GNOME Interns:
Laura Alves
Anita Kuno
Victoria Martínez de la Cruz

Red hoodies given out at the Summit were specifically designed for women – based on feedback from the previous Summit