Mondoescue 3.2.1 is now available … with effort and pain !


Believe it or not, it has been one of the most challenging version to produce ! And one which was really awaited by lots of people.

First all those of you who had problems restoring big files with 3.2.0 which had issues with that. Now that’s solved (was already with the beta previously).

Then those of you who had a RHEL 5 system. 3.2.0 wasn’t working, and 3.2.1 should be much better. Similarly for the people using RHEL 7. This is the real first version working for RHEL 7 available of MondoRescue. I’ve made most of my tests with a RHEL 7 VM in order to track all the errors which were remaining for that env (also some smaller but annoying ones). The root cause is that I had a customer wanting to move to that version for RHEL 7, and I wanted them to be happy with the result. Doesn’t mean they won’t encounter issues, despite what I did, but I’m much more comfortable to handle the cases in their support contract (Yes this is a paying customer).

And finally those of you who were trying to have a working environment for a UEFI based machine with RHEL 6. UEFI wasn’t working at all with 3.2.0 (and previous versions) even if EFI was working on Itanium systems. So this time I used a real system to make again lots of different tests, and solving again lots of issues linked to the support of UEFI, and now I’m happy with the result. The media made is recognized by the UEFI shell or the HP ProLiant guided boot menu. And a full backup / restore works also on it. So that other customer (an HP one, but not a paying one from a MondoRescue perspective… yet) should as well be happy and be able to use MondoRescue to perform its clones and installs correctly.

Could it be better ? Of course. RHEL 7 + UEFI are not yet friends. That will be for 3.2.2, as I want to keep my job ;-). Few bugs in trac have been addressed during these last 8 months, sorry for that. But a lot not mentioned there have been solved, and that was most of the work. And a lot of work has been put (commit hours are real !) into solving the customers needs and deliver that version on time. That’s probably why I hate time based releases, as it forces you to deliver (which is always good), but not with the serenity which should be part of an OpenSource development. Of course, that’s my fault ! I should have anticipated these requests (UEFI and RHEL 7 are there since a long time). But hey, this is still not my day job at HP. So I can only do my best as time permits. And I have a lot of other hobbies that I’ll be back to now so they can also know some progress. That’s also why I do not make more regular releases. But patches are always welcome.

Anyway, pain is over, a new version is here. Test it, report feedback, try to not break it too much, and remember to do regular backups whatever the tools you use.

Download at

Redfish 1.0 is now out and soon used by our projects


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.

Some personal news around OpenStack


I’m trying to be more and more involved around OpenStack, as much as my time allows me of course.

So some recent news about that:

1/ I’m now a member of the Franch OpenStack Association Board and really proud to be listed alongside real long time contributors and advocates of the project.

2/ I’ve become an ATC during the Liberty cycle due to a modest contribution on Ironic. But it gives me the possibility to attend the Tokyo Summit !

3/ I’ve contributed to 3 proposals of talks for the upcoming Tokyo OpenStack Summit: the first one on the work we do to add support for Redfish in Ironic. The second is on a new project called Alexandria which we would like to see becoming an OpenStack project in the future and which is a CMDBaaS solution. Early stage but pretty neat ! And finally, we want to expose our view around a Software Defined Infrastructure with OpenStack.

If you think that any of these 3 presentations is worth listening during the upcoming Tokyo Summit, then vote for us before the 30th of July !!

I’d like to share other thoughts on the big tent and the community, but that will be for a next article.

Back to RMLL 5 years after !


I like that event which is organized by different teams each year and gather thousands of enthusiasts during one week in one city to celebrate Open Source and Free Software.

This year, for the first time since 2010, I have no conflict attending it and also attending the Academy of sacred Music in Etampes, the week after, as I do since the first one.

So this year I’ll give a status of where we are with the MondoRescue project for my tenth anniversary of project leadership and after the last presentation I did 5 years ago.

And as you can’t be in the mood without docker, I’ll deliver a session on docker and project-builder to demonstrate its particular value IMHO in this domain of continuous packaging and also I’ll animate a Lab session on docker to help discover this tool and understand the challenge of containerizing an application such as owncloud. Come prepared with at least a Linux VM or better a Linux laptop to enjoy the tour :-) And start by downloading the Lab document based on Ubuntu 14.04 !

And don’t hesitate to come and talk of whatever topic I’d be able to cover such as AFUL, Mageia, OpenStack, Redfish and Ironic or the beauty of Jean Mouton’s music during the reign of François the first (not our current pope ;-))

Time to meet again at HP ExpertOne Technology & Solutions Summit !


For those of you working for an HP value added reseller (VAR) and attending the HP ExpertOne Technology & Solutions Summit in Dublin from the 16thth to the 19th of June, feel free to meet during one of the session I’ll (co-)deliver:

  • UEFI: what, why, when, how and the rest Breakout 49 – Tuesday 16th of June 2015 – 5:45PM-6:35PM
  • HP Helion OpenStack in action – Breakout 175 – Wednesday 17th of June 2015 – 8:30AM-9:20AM
  • UEFI Hands-On Labs (François Donzé) – Lab 4 – Wednesday 17th of June 2015 – 11:00AM-12:50AM
  • HP ProLiant Gen9 value add on Linux (Hands-on Lab) – Lab 16 – Thursday 18th of June 2015 – 2:00PM-3:50PM
  • HP REST API for iLO Lab (François Donzé) – Lab 6 – Thursday 18th of June 2015 – 4:30PM-6:20PM
  • HP ProLiant Gen9 value add on Linux – Breakout 48 – Friday 19th of June 2015 – 12:00AM-12:50AM

And you should be able to meet the Geeks on Wednesday afternoon, myself included.

For those of you wondering why and MondoRescue versions are not published more regularly, that gives you a hint ;-) Even if I made some progresses recently I also need to document !

See you there to talk of these subjects or something else as you see fit. I’m around the whole week.

Représentation HP à une table ronde du congrès Curie


J’ai été invité à parler à la table ronde du congrès CURIE modérée par Eric Horlait

Son thème est: “CLA, un mode de coopération original pour animer une communauté du logiciel propriétaire” (sic). J’y aborderai pour ma part la manière dont HP gère son engagement auprès de communautés du logiciel libre et le gestion des contributions.

Je ne suis pas encore bien sûr de comment cela va s’articuler, mais si vous êtes curieux comme moi, rendez-vous demain à Pau pour le savoir !

Software Defined Compute: Redfish and Ironic at the next OpenStack Summit


The future is already here !

In fact here ! This is a new specification which is gaining traction to allow hardware configuration of systems through a RESTful interface. All new HP ProLiant Gen9 servers from HP are providing a first version of what is not yet the standard, but looks very near to it, and provide already a rich interface.

This is pretty exciting, as it will allow people like me working on Disaster Recovery e.g., or people like Devananda van der Veen who is the Ironic PTL (OpenSTack bare metal deployment component) or many others to have, when it’s ready, a single interface to configure the servers from different manufacturers following the Redfish Specification (as of now HP, Dell, Emerson, Intel). And it’s much more feature rich than IPMI, so you would be able to go well farer with it and reach a real Software Defined Compute node.

In order to make it usable for Ironic we’ve started to work on a low level python library (python-redfish) on which we’ll be able to build the Ironic driver for Redfish later on. This is work for Liberty and after of course. And as Ironic can be also use alone, I’m more and more thinking of using it as a way to provide MondoRescue images for bare metal deployment as an additional feature over media boot. Especially if there are plans to have a standalone web interface for Ironic !

If you want to learn more on the HP implementation of the RESTful API, there is a webinar organized Wednesday, April 29, 2015 from 10:00 am CDT to 11:00 am CDT. Register from

And if you want to learn a bit more of where we are on this, read the code (easy for now) or come at Vancouver for the upcoming OpenStack Summit to discover it.

Lettre ouverte aux représentants de la nation


Cette lettre se veut un lancement d’alerte auprès de nos représentants démocratiquement élus de tout bord concernant l’examen en cours par le parlement de la “loi sur le renseignement”

Je réagis en tant qu’amateur du logiciel libre et de données ouvertes à titre privé, membre de l’AFUL, comme de l’APRIL, aussi bien que comme professionnel, en tant que citoyen que l’on va priver d’un de ses droits fondamentaux, en tant qu’électeur qui refuse de se reconnaître dans le premier vote effectué et demande instamment à tous nos représentants de se documenter avant de voter juste comme on leur a dit de voter.

Un certain nombre d’articles décrivent très bien les dérives vers lesquelles vont nous entraîner un vote en l’état de cette loi. Celui de Laurent Chemla sur Mediapart par exemple, ou celui de la Quadrature du Net vont donneront assez de matière pour réfléchir, et comprendre l’appauvrissement numérique qui gagne la France avec tous ces services associatifs et professionnels qui vont quitter le pays.

De plus, qui peut vraiment souhaiter vouloir qu’une boite noire en dehors de tout contrôle juridique amasse la plus grande collection de données possible pour la traiter selon le bon vouloir du gouvernement du moment. Comme nous ne savons pas lequel sortira des urnes en 2017, c’est donner un blanc-seing potentiellement à des partis dont on ne souhaite pas qu’ils aient une vue complète sur tout ce que vous échangez.

Va-t-il falloir tout crypter (chiffrer pour les puristes), du simple message de coucou, à ceux échangés autour de la musique renaissance (qui permet de faire des concerts sans droits d’auteur mais cela déplaira à la Sacem qui demandera à un ami un accès aux boites noires pour voir ce que je complote, ce que personne ne pourra contrôler du reste), ceux échangés au sein des conseils d’administration auxquels je contribue (le gouvernement saura ainsi que j’ai voté oui pour que l’AFUL se positionne contre cette loi), ceux que j’envoie à ma banque pour faire une opération, les sites que je consulte et ceux que je ne consulte pas, … On n’a pas besoin d’être terroriste pour vouloir faire respecter un niveau de confidentialité de son activité numérique.

A-t-on envisagé l’impact sur les sociétés ayant des sièges à l’étranger sur leur volonté de communiquer avec leur filiales potentiellement espionnées en France ? A-t-on mesuré l’impact sur les ONG et le travail qu’elles font partout dans le monde, quand elles réaliseront que tout ce qu’elle font (et elles dépendent complètement de l’Internet aujourd’hui pour fonctionner comme les précédentes et les suivantes) est potentiellement espionable ? Et les associations loi de 1901 ? Et les partis politiques, les syndicats, les juges, les avocats, les journalistes ? La CFTC Metallurgie 91 par exemple est hébergée chez Free par exemple. La confidentialité d’adhésion va du coup est sérieusement mise à mal non ? Et ce n’est qu’un des nombreux aspects où la surveillance de masse (puisque faite en coeur de réseau chez les opérateurs de l’Internet systématiquement, elle est donc de masse) aveugle pose problème.

Pourquoi ne pas simplement déjà appliquer la loi telle qu’elle est ? Elle a permis de mettre sur écoute les personnes qui allaient plus tard commettre des attentats (malheureusement pour les victimes, la surveillance légale et contrôlée a été arrêtée trop tôt) sans que cela soit une atteinte à la liberté des 65 autres millions de français ? Les lois actuelles, même si elles ne sont pas parfaites, ont permis à notre société de grandir et croître jusqu’ici. Il suffit de continuer à demander l’autorisation d’un juge pour mettre une personne sur écoute Internet. Au moins, il y aura des traces des raisons pour lesquelles cela est fait.

Messieurs et Mesdames les députés et sénateurs, cette frénésie pour légiférer n’est pas une preuve d’action. Par le simple fait qu’un ministre dise dans l’assemblée que la vie privée n’est pas une liberté vous devriez sérieusement prendre du temps pour examiner le projet, reconsidérer les amendements proposés et agir non en suivant la consigne de groupe, mais votre propre choix car sur un tel texte, on n’est pas de droite ou de gauche, on est pour la liberté individuelle et la vie privée (comme dans la constitution européenne) ou contre. Nous, citoyens, aurons le nom de tous ceux qui n’auront pas eu le courage de voter en leur âme et conscience pour léguer un Internet ouvert et respectueux des libertés de chacun à nos enfants.

En attendant, je vais leur apprendre les principes de bases des clés publiques et privées, et faire quelques essais sur le cryptage (aka chiffrement) systématique de nos communications. Cela contribuera au réchauffement climatique car nos ordinateurs, comme ceux qui tentent d’analyser les contenus, auront beaucoup plus de travail à faire (donc plus de consommation d’énergie pour y arriver).

Et n’oubliez pas que vous êtes des citoyens comme les autres de ce point de vue, et que donc vos informations bancaires, d’impots, d’opinions, … seront elles aussi stockées dans ces merveilleuses boites noires d’où l’on pourra extraire ce que l’on voudra. Finalement, on y gagnera sur l’automatisation de la déclaration de votre patrimoine en ligne qui sera grandement simplifiée, … et nécessairement juste. Mais ce ne sera qu’un petit pas pour la démocratie finalement non ?

Dans l’attente de consulter vos votes prochains sur ce projet de loi, et en espérant que vous éviterez à la France d’être à l’avenir comparée à la Corée du Nord, je vous souhaite une bonne lecture des références mentionnées plus haut pour vous forger une opinion par vous-même.

Attending HP Helion MVP next week in Sunnyvale


I’ve been recently awarded as an HP Helion MVP. And immediately after, invited to participate to the first HP Helion MVP Event in Sunnyvale on March 18th thru 20th, 2015. Looking at the mmebers and the presenters, that will be a great event, and I’m sure I’ll learn a lot through the discussions and presentations we’ll have.

On my way to the US, I’ll go through Seattle to meet with some HP colleagues arriving Monday night, and departing to Sunnyvale on Tuesday evening.

All that is a short trip, just before our big HP internal EMEA Event the week after, but I’m sure it will be worth the effort. And if you’re around as well, and want to talk about Open Source @HP, disaster recovery or cloning with MondoRescue, continuous packaging with or Helion OpenStack of course, feel free to drop me a mail so we can meet and talk.

MondoRescue 3.2.1 is definitively looking better but will for sure with your help !


Since a couple of days, I’ve passed quite some time to deal with the various reports that were made on the mondo mailing list with regards to bugs found by users on version 3.2.0. Of course, as every .0 version, not everything was tested, and the help of the community is as usual key to find these cases left appart, and of course find bugs in them !

What has been fixed is available here:

The other BRs I’d like to address before releasing 3.2.1 are:

  • glibc detect an invalid pointer (#766)
  • Smartarray b120i closed drivers not working (#751)

and the older, but really annoying one:

  • Fail to Restore from External Hard Disk (#628)

While I think I can deal with the 2 first one pretty easily, the last one requires more time and will probably end up in 3.2.2 instead, as it’s difficult to delay more 3.2.1 now that the most annoying issues have been solved.

In the mean time, please test the beta of 3.2.1 at (lots of distros available). That will clearly help me finalizing that version. Hopefully you’ll mostly report successes, but I really need your help to make it much better than 3.2.0.

With the latest devs made on mindi to support again correctly older distributions such as RHEL5 (which wasn’t working anymore in 3.2.0), I think I’ll also being able to make the promised 3.0.5 soon, for those wanting to avoid the risk of using a mondoarchive very different in code with lots of dynamically allocated memory. That will pretty surely be the last one in that serie. The focus is really now on the 3.2 branch.

Thanks for your continuous support on this project !


Get every new post delivered to your Inbox.

Join 124 other followers