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

2015/04/24

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 https://h71044.www7.hp.com/campaigns/2013/events/linkandcoordinate/index.php

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

2015/04/21

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

2015/03/11

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 Project-Builder.org 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 !

2015/03/06

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:
http://trac.mondorescue.org/query?status=closed&group=resolution&milestone=3.2.1

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 ftp://ftp.mondorescue.org/test/ (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 !

Time to Meet at HP ExpertOne Technology & Solutions Summit !

2015/01/21

For those of you working for an HP value added reseller (VAR) and attending the HP ExpertOne Technology & Solutions Summit on Barcelona from the 2nd to the 6th of February, feel free to meet during one of the session I’ll (co-)deliver:

  • UEFI: what, why, when, how and the rest Breakout 101 – Wed 2014-02-04 9:30-10:20 AM
  • HP Helion OpenStack in action – Breakout 124 – Wed 2014-02-04 2:00-2:50PM
  • HP ProLiant Gen9 value add on Linux – Breakout 99 – Thu 2014-02-05 9:30-10:20 AM
  • HP ProLiant Gen9 value add on Linux (Hands-on Lab) – Lab 16 – Thu 2014-02-05 2:00-3:50 PM
  • UEFI Hands-On Labs – Lab 19 – Thu 2014-02-05 4:30-6:20 PM
  • Running Enterprise Linux distributions on HP ProLiant Gen9 – Breakout 100 – Fri 2014-02-06 9:30-10:20 AM

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

For those of you wondering why project-builder.org and MondoRescue versions are not published more regularly, that gives you a hint ;-) Not speaking of the next event in March, TES, where I’m part of the Event team this time.

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

MondoRescue packages available for new distributions

2015/01/20

As asked on our trac instance, new packages have now been build for the latest MondoRescue version 3.2.0 for OpenSUSE 13.2, Fedora 21 and SLES 12 in addition to the 150+ other distros already supported.

SLES was as expected the most difficult to deal with as it doesn’t provide newt packages, so I had to also build them from sources with the dependencies and they are all in the repository as well so you shouldn’t had issues trying to use them.

As usual please report issues either with the tool itself or the packaging following the guidelines.

Tout à voir

2015/01/08

Je pensais que ce billet n’avait pour une fois rien à voir avec ce dont je parle habituellement: l’informatique libre et la musique ancienne. Mais en fait si.

Parler de ce qui s’est passé est impossible. Se taire serait intolérable.

Faire du logiciel libre, c’est promouvoir une forme de liberté. Liberté de contrôler son environnement numérique, de penser le logiciel d’une certaine manière, d’échanger facilement avec d’autres qui ne font pas comme vous car on respecte des chartes d’interopérabilité comme des constitutions.

Faire de la musique ancienne, c’est promouvoir une forme rare et profonde de culture qui montre la continuité par delà les époques, qui promeut par la chanson parisienne de de Janequin par exemple une forme complexe mais subtile si représentative pour moi de l’esprit français, c’est faire partager par l’émotion suscitée l’amour de la différence et du beau.

Aujourd’hui on a tenté de détruire deux des socles fondamentaux de notre démocratie à la française, la liberté et la culture.

Je n’aimais pas vraiment l’humour de Charlie Hebdo. J’ai le droit de le penser. Et alors ! tout le monde se fiche de ce que je pense, du moment qu’eux ont le droit de s’exprimer et de d’échanger autour de leurs idées, comme je peux moi échanger autour des miennes mentionnées plus haut. Comme ne l’a pas dit Voltaire: « Je ne suis pas d’accord avec ce que vous dites, mais je me battrai pour que vous ayez le droit de le dire »

Alors ce soir, moi aussi comme l’immense majorité des démocrates de tous les pays, je suis Charlie.

Finalement, parler est possible. Revenons en à notre devise:

Liberté de la presse et de la pensée
Egalité dans la laïcité et notre capacité de croire en ce que nous voulons,
Fraternité envers les victimes et leurs familles

Merry Christmas, MondoRescue 3.2.0 is out !

2014/12/24

My previous post was to announce I wanted to publish that long overdue 3.2.0 version of MondoRescue beofre Christmas, so here we are !

I finally found the issue I had restoring RHEL7 with 3.2.0. This was due to a cumul of problems:

  • XFS labelling was broken. I fixed it by calling appropriately xfs_admin in label-partitions-as-necessary
  • RHEL7 uses a UUID for / in the grub2 configuration, which is not mentioned in /etc/fstab; so mindi wasn’t recreating that UUID correctly. So now mindi will store in the mountlist.txt the UUID of each partition, if no other LABEL or UUID was explicitely given in /etc/fstab in order to be able to use it at restore time, and label-partitions-as-necessary was also updated to take that in account

And I was with these modifications able to restore fully automatically a RHEL7 VM. So as I had alrady a working RHEL6 and Fedora 20 env, and as no big regression is expected on other supported distros (Mageia, SLES, OpenSuSE, Debian, Ubuntu mainly) I thought it was time to deliver it officially and give you a toy to play with for Christmas ! Am I not a nice guy ;-) ?

A lot as changed with regards to 3.0.4. If you want to have all the details, look at the Changelogs available in the trac announce, or read my previous posts about the 3.2 branch development, which started back in October 2013 (or even before in fact).

Is it the end of the 3.0 branch ? No. As I announced it earlier already, I want to at least publish a 3.0.5 with most mindi modifications backported in it (SVN already has such a branch in fact) in order for those of you who don’t like major updates, to stay with a more stable branch for some months, before jumping into 3.2.x. Because 3.2.x is the future, and most of my development time will happen here.

Hopefully that 3.0.5 branch will also work fine with systemd and /usr only based distros as the modifications to support that have all been done in mindi.

As for the 3.2.x branch, please report your findings ! I know I’m far from answering all mails, or answer all bug reports, but I do rad all of these, and as time permit, I try to make the code evolve (typically adding more perl functions) to have a more flexible way of incorporating your requests. Slower, but I have an installed base to maintain, I’m not like Fedora, which will always be followed, I need to keep my sysadmin as happy as possible with the state of the tool, while maintaing as much compatibility as I can with the previous versions.

But all that won’t happen before early January, as I’ll pass time with my kids and my wife to celebrate Christmas, an enjoy being together, which is now not as often as the previous years (yes kids grow up and move sometimes far from home :-), and that’s good !)

As I write packages are still being delivered to the master ftp server. Try it after the 25th !

MondoRescue 3.2.0: last beta before publishing

2014/12/07

I’m probably far from being a good project leader. The lack of time is one of the reason, but I think I could do better anyway, as I was particularly quiet these 2 last months. So I use that time, where I’m waiting before driving to the airport to give a status.

I was quiet, but still working on it as time permitted, and willing to solve the Fedora 18-20 support issues I had for a very long time now. And it seems that with the latest patches pushed this week, I’m good on that side. I’ve been able to do a full backup/restore of my Fedora 20 VM in automatic mode without issue ! That’s the first time, and was particularly happy that after 9 months of development around 3.2, I could achieve that. The other good news, is that it is still working fine for RHEL 6 e.g. as I also did a full cycle this week.

Ok, so life is nice. Well, as you know, nothing’s perfect ;-) So I still have an issue with RHEL 7. In fully automatic mode, eveything works fine, except that the restored VM doesn’t start due to an issue on the UUID in the initramfs.

I’ll test by recreating that initramfs after restore, and hopfully, dracut will do the job for me. But as I’ll be travelling in the US all next week, I thought it was good to publish a last beta before leaving, so that the community could also test and report what happens on other distros or on other configurations.

Note that very few other bugs have been fixed. I’m more interested for this first 3.2 version to have it work finally on all new systemd distros as much as I can, even if some features are still not fully working (see trac for details).

Compared to my last post on the subject, some points have been improved:

  • the network stack is now launched as long as a network backup has been done originally, even if you boot from the ISO image directly, and not through PXE. You may still choose from where to restore afterwards, but at least network is up
  • solve some /bin vs /usr/bin issues for pre-fedora 18 and systemd distros which were not working anymore (Cf: #741)
  • fix for a lack of keyboard discovery
  • fix some perl issues in some cases (Cf: #755)
  • force LV creation which on RHEL7 now asks a question in case something was already there before (Cf: #753)
  • Optimize modules list computation between mindi and restore init script and do not load modules list twice anymore
  • Force generation of hardlinks for busybox to avoid package build problem on some distro with inexistant links at build time (recent SLES)
  • Fix busybox 1.21.1 to support back old distributions such as RHEL3 and RHEL4 or SLES9 by avoiding usage of the struct tpacket_auxdata
  • Fix isolinux.bin and ldlinux.c32 locations for recent Debian distro

So maybe even more has been fixed than I considered initially in fact. Anyway, I’ll try to avoid to stay so long without publishing new versions to test. It’s a promise, but will be difficult to keep so don’t hold your breath !

I’d appreciate that you provide feedback on the MondRescue mailing list, create trac entries (even if I know there are already a lot that would need to be solved sooner than later).

The goal is to publish 3.2.0 final before Christmas, and to work on a hopefully final 3.0.5 version backporting some of the previously mentionned fixes coded in 3.2 for those of you who prefer to stay on that branch, which will be maintained a bit in parallel as long as 3.2 is not tested more. I think that you’ve been patient with me, so I also have to be patient myself before more users adopt the new stable branch.

Hopefully you’ll get a new blog article for the announce in less than a month !

Fifth OpenStack Meetup for Rhône Alpes

2014/11/18

The fifth meetup for the OpenStack regional group will be organized in Lyon at the ENS the 4th of December 2014.

We will have various presentations which are not yet finalized, and indeed you’re even invited to propose a talk if you’re a speaker, or soon to vote to choose the presentations you’d like to see.

Refer to http://www.meetup.com/OpenStack-Rhone-Alpes/ (in french) for more details and registration for those of you around.


Follow

Get every new post delivered to your Inbox.

Join 124 other followers