[Users] Problem Creating "oVirt Engine" - Stuck on FQDN

[Richie@HIP]

I agree.  The "oVirt Node" part will not be a VM since as you said, it would be a VM within a VM - my mistake in expressing what i'm preparing.

Regarding the "single machine" (Engine and Node) "live iso" that you mention.  Where can I find it…?

Regards;

Richie

José E ("Richie") Piovanetti, MD, MS 
M: 787-615-4884 | richiepiovanetti at healthcareinfopartners.com






On Jun 5, 2013, at 3:28 AM, Joop <jvdwege at xs4all.nl> wrote:

> Richie at HIP wrote:
>> 
>> hi oVirt Community.
>> 
>> This will be my first posting for help to the oVirt community, so please bear with me I'f I'm not to the etiquette standards you might have already.
>> 
>> I'm trying to test oVirt as a FOSS Virtualization solution for small- to medium-sized healthcare organizations implementing various health information technology solutions (HIT) that the new health care reform is requiring.  As a Clinical informatist, I'm very concerned about health care costs, hence I'm pushing for open source to take a wider stance in U.S. health care to reduce costs where possible and divert moneys to patient care.  Now enough with my altruistic desires, and let go into the deep.
>> 
>> I'm trying to create "virtual machines" (using VirtualBox, Parallels and/or VMWare Workstation); mainly one for "oVirt Engine"; ind later a the second one for "oVirt Nodes".  This way, these VM's files can be copier to any hardware and underlying OS, so at least the "Virt Engine" is easily installed and brought-up to facilitate managing oVirt Nodes.  I considered creating ".iso" images of each component (Engine and Nodes) but I'm afraid this will hit the wall for linux novices when installing the ".iso" images in different hardware platforms (with different processors, number of cores, RAM, chipsets, etc.)
>> 
> If I understand you correctly you want to make VMs for both engine and node so that you'll only need those images to setup a virtualisation infrastructure?
> If so that is only partly going to work. The engine VM will work but the node not since that would imply nested virtualisation. That can work but not for every combination and probably not for the above mentioned products.
> Node needs to run on the bare metal since it provides the same functions as VirtualBox/Parallels/VMWare, its Fedora18 as its operating system + kvm as its virtualiser.
> 
> Concerning you dns problems, to make it short, you'll need to come up with a naming scheme and implement that either using a full dns server or through /etc/hosts.
> You might also have a look at the all-in-one plugin which turns a single machine into both engine and node or if you want to play around have a look at the live iso.
> 
> Regards,
> 
> Joop
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130605/f266ab6b/attachment.html>