[Libosinfo] [PATCH 7/7] data: added lxc install script for suse

[Daniel P. Berrange]

On Mon, Apr 14, 2014 at 06:11:50PM +0200, Cedric Bosdonnat wrote:
> On Mon, 2014-04-14 at 15:39 +0100, Zeeshan Ali (Khattak) wrote:
> > On Mon, Apr 14, 2014 at 3:09 PM, Cédric Bosdonnat <cbosdonnat at suse.com> wrote:
> > > ---
> > 
> > Finally, someone adding script for openSUSE. \o/ Some comments:
> > 
> > 1. Is this a complete unattended installation script or it only
> > creates the rootfs? If its former, are you sure the name has to be
> > 'create-rootfs.sh'? If its latter, I think we'd rather want a script
> > that can do a complete installation as thats what the applications
> > will expect from these scripts.
> 
> This script just creates the rootfs: the rest is supposed to be done by
> the containerization.
> 
> > 2. The injection-method method isn't the most important feature of
> > this patch so I don't think it deserves to be mentioned in the
> > shortlog at least. Having said that, would be nice to have some more
> > info in the commit log details section.
> 
> Well... the attempt with a special injection method (whatever we call it
> in the end) it to help filter the install scripts that will apply to
> create rootfs for containers. We can either filter by name and assuming
> all rootfs creation script will have the same name across distros, or we
> can filter on a special injection method.
> 
> Depending on what you prefer, I can even drop that new (fake) injection
> method.

If its only creating the filesystem I don't think that is particularly
useful. The install scripts facility is really more about automating the
provisioning of the operating system, akin to kickstart.

An app doing provisioning knows it should create the filesystem really
so we don't need metadata / script todo that IMHO. At the very most we
could have a metadata element which records the preferred filesystem
type (ext3, ext4, whatever) and the app can just run that mkfs binary.

I wonder what "install scripts" means in the context of container based
virt. With machine virt this is about running the full operating system
installer (eg anaconda with Fedora/RHEL) from the install media / tree,
along with an "answer file" to automate its action.

We do have information about install media / trees, but AFAIK, no current
operating system is able to run its regular installer in a container. At
leastt you can use the install media / tree URL / file as an repository
for invoking an apt/yum/etc command. We don't exactly need install
scripts for that though - we could just tag the install media / tree
info we have with the type of repository (apt/yum/etc), and then mgmt
apps could just invoke apt/yum to boot strap the installation.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|