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.