Posts Tagged ‘Alexandria’

Meet during the upcoming OpenStack Summit in Barcelona

2016/10/12

For the first time, I’ll be speaking at the OpenStack Summit during the main conference.

I’ll talk about the possibility to add Redfish support to Ironic.

I’ve already talked about Redfish, either the standard, or through our python-redfish module, even during a vBrownBag session of a previous Summit in Vancouver.

This time I’d like to detail the latest news around the standard itself, how it can be used in an Ironic context and what we’ll have to do to make it work, up to its usage for Alexandria, a CMDB as a service solution we’re also developing in conjunction with these components.

I’ll also attend most of the Ironic dev round table to organize that work, and understand better what the community is expecting from us with regards to the development, and answer to the questions around the specification. Should be a very interesting week in Barcelona (on top of the fact Barcelona is a great city I encourage you to visit !)

Advertisements

In order to meet at the OpenStack Summit in Austin, vote for us !

2016/02/12

We’ve made 3 different but related proposals for the upcoming OpenStack Summit, and as everybody, we would like to be retained in order to disclose what we’re working on and think could improve the ecossytem.

Our first proposal is “Empowering Ironic with Redfish support” which aims at describing our plans to add Redfish support to Ironic.

The second, which would benefit greatly from the work of the first, is “Alexandria: The librarian bridging OpenStack and CMDBs” which is a nascent new component to allow easily with a plugin based architecture to bridge CMDBs (starting with the great Open Source iTop one) and OpenStack features such as bare-metal deployment with Ironic, managing also automatic inventory. Amitious but pretty useful in our opinion, of course to help manage our Datacenter, but the one of any OpenStack customer as well.

Finally, We’d like to present our overall view on how OpenSTack is at the heart of a Software Defined Infrastructure with our last presentation. This one targets more architects and decision makers, while the 2 others will be more technical and cover implementation details. All will have demos.

Hopefully, you’ll agree with me to find that these topics deserve being elected !! And thus vite for them 😉

In that case, I can just wish we’ll meet over there 🙂 !

Redfish 1.0 is now out and soon used by our projects

2015/08/20

Recently the DMTF announced that the Redfish standard had reached version 1.0, the first usable for production.

If you don’t know Redfish yet, and don’t want to read the full spec, I can summarize it very roughly as a cross-manufacturer RESTful API to configure Hardware systems and recover info from them. Pretty cool in fact as this was a missing brick for a full Open Source based multi-platform Software Defined Infrasctrucute.

Now remains for us to update our python-redfish with it, and start supporting more features now it’s stable. That the first step will allow Ironic, the bare metal component of OpenStack, to have Redfish support, which is IMHO a very highly desirable feature. Not for Liberty, hopefully the spec will be ready for M and code sufficiently developed to allow us to win a slot in the Summit !

Then it will also allow us to advance on the other project we’d like to promote: Alexandria, which is a clever (of course, I’m part of the design team ;-)) way to interface CMDBs (well the one who are themselves clever enough to have a parametrized data model such as iTop) and Hardware information providers such as Redfish.

Imagine that you rack a new Refish compliant server (HP ProLiant Gen9 are among the first to provide already a subset of it), cable power and management board, integrate some info on that machine in your CMDB (iLO credntial and IP address e.g.), and ask through Alexandria that the rest is filled by Redfish calls. And kept updated as time passes. Well, that’s exactly what we try to achieve, as this is one of the need we have to maintain our Solution Center CMDB up to date as easily as possible.

Lots of good ideas, but not enough code to show for now. Hopefully, we should be able to have an Alexandria demo with somple drivers ready for the upcoming OpenStack Summit… and be able to travel to exchange our views with other OpenStacker around all this.