Hi, I'm the project lead for TripleO (OpenStack on OpenStack - a disk image based approach to deploying and maintaining OpenStack clouds), and we have a tool 'diskimage-builder' which consumes upstream vendor cloud images and customises them. It would be a non-trivial nuisance if we had to expose per-cloud flavours to our users, so please consider very carefully if you go down this route: one of the major strengths of Linux is the ability to drop a filesystem image onto some hardware and have it Just Work - it's better for our users if userspace and boot tooling keep that capability, because then they don't need to respin images if they are cloudbursting across multiple providers. (Or other similar use cases). Cheers, Rob Robert Collins <rbtcollins@xxxxxx> Distinguished Technologist HP Cloud Services ________________________________________ From: cloud-bounces@xxxxxxxxxxxxxxxxxxxxxxx [cloud-bounces@xxxxxxxxxxxxxxxxxxxxxxx] on behalf of Kashyap Chamarthy [kchamart@xxxxxxxxxx] Sent: Thursday, 27 June 2013 07:04 To: Fedora Cloud SIG Subject: Should Fedora revisit the idea having "one " image to be used across the cloud providers? (Re-directing the discussion from #fedora-cloud on Freenode..) Heya, (Without trying to make it a large 'theoretical' discussion..) So, should we (Fedora) reconsider the "noble goal" (as Matthew Miller put it) of having one cloud image serve all cloud providers? Or separate images (sure, there's more work involved) that are specific Because, lately we've seen several problems where cloud-init has been breaking things in subtle ways, like output of boot messages on console.log for OpenStack/Amazon/Eucalyptus has been broken in different Garret Holmstrom and Matthew Miller (both who's been in the trenches of these issues can describe much better than I can at this midnight hour). They also discussed a couple of ideas on IRC like - configuring journald to forward to both syslog and the console e.g. (please read the issue described above) https://bugzilla.redhat.com/show_bug.cgi?id=977952 -- RFE: disable all direct writes to the console And, comparing Fedora images with Cirros -- they output a neat array of bunch of commands (I think I noted this previously on this list) that's helpful for debugging. Refer this previous thread https://lists.fedoraproject.org/pipermail/cloud/2013-April/002371.html but haven't reached a proper conclusion. Any further thoughts from other folks here on how to resolve this would be nice to hear. -- /kashyap _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
