On 07/26/2011 09:16 AM, Joey Boggs wrote:
On 07/26/2011 08:15 AM, Bruno Wolff III wrote:
> On Tue, Jul 19, 2011 at 15:44:56 -0400,
> Joey Boggs<jboggs(a)redhat.com> wrote:
>> There seems to have been positive support for this spin so far, can we
>> get an official ACK from the Spins SIG to continue the process? Fedora
>> Design team has acked it and I'm just waiting on an offical ack from QA.
>> Once we have the three groups we can be accepted.
> I looked briefly at the ks file for the ovirt spin and it is a lot
> different
> then the live images included in the past. Typically spins SIG only
> reviewed live spins, which ovirt doesn't appear to be.
>
> I think it might be better to consider this spin as outside the scope
> of Spins SIG, as we would need to rewrite policy to be able to cover
> ovirt, and I don't think that is going to happen in a timely fashion.
This specific spin can actually cover multiple use cases. It can boot
and run directly from the cd or be installed to a machine. Then add any
type ofstorage for libvirt and create vm's. It's original form was to
boot up and grab a configuration from a management server which gave out
storage and networking configurations as needed and provision templated
vm's from a web interface. That server framework was been released for
adoption as RHEV-M becomes open source it will replace it. When
installed to a machine and run it provides persistent storage for any
configuration files. The actual image itself stays in the same form as
it would in the iso, only storage for a volume group and grub
configuration are wrapped around it.
There may be multiple methods of running this spin but it will still run
from a cd/iso file just like any other spin.
Right. oVirt Node is no different from any of the other Live spins in
that regard. It can both be run Live/stateless or installed to disk.
We just highlight the 'install to disk' presently functionality because
it maps to the current use case for RHEVH/RHEVM product that Red Hat has.
Other use cases may not require the 'install to disk' functionality.
For example, standalone usage via the virt-manager-tui or integration
with the Condor Cloud feature.
Besides, don't the other spins provide an option to install to hard disk?
Perry