On 06/27/2013 12:53 AM, Collins, Robert (HPCS) wrote:
Hi, I'm the project lead for TripleO (OpenStack on OpenStack -
Hi Robert, yes, I've just noticed this project a week or so ago.
While I have your attention, probably too late now, I wonder was Oz ever considered for
disk-image-building? (I've read the README of diskimage-builder briefly)
Oz has been in development (& has an amicable upstream) for a couple of years,
JEOS (just enough OS) targeting multiple operating systems including Windows. It's not
RPM specific either. There's Debian packaging notes:
All apologies if this discussion happened elsewhere, please point me to it.
a disk image based approach to deploying and maintaining OpenStack
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).
Understood. Thanks for bringing it up.
From: cloud-bounces(a)lists.fedoraproject.org [cloud-bounces(a)lists.fedoraproject.org] on
behalf of Kashyap Chamarthy [kchamart(a)redhat.com]
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..)
(Without trying to make it a large 'theoretical' discussion..)
So, should we (Fedora) reconsider the "noble goal" (as Matthew Miller put it)
one cloud image serve all cloud providers? Or separate images (sure, there's more
involved) that are specific
Because, lately we've seen several problems where cloud-init has been breaking
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
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)
-- RFE: disable all direct writes
And, comparing Fedora images with Cirros -- they output a neat array of bunch of
(I think I noted this previously on this list) that's helpful for debugging. Refer
but haven't reached a proper conclusion.
Any further thoughts from other folks here on how to resolve this would be nice to hear.