Re: Red Hat's new virtualization

[Paul Robert Marino]

I ran RHEV in production in a previous job to give you an idea its
similar to VMWare vSphere. It allows you to have a single host manage
you virtualization environment including live migrations. in addition
it can monitors the virtual machines and hardware so if vms crash
unexpectedly due to hardware failures it can relaunch them on a
different host, but it requires the management host to have access to
ILO's, DRAC's, or similar device to control the power switches of the
servers and the use of SAN or NAS storage to fully work correctly. it
can also manage Gluster storage clusters, however it assumes that the
Gluster clusters are dedicated to RHEV for use by the virtual machines
and nothing else.
there are two features vShpere has that Ovirt does not
1) last I worked with it there was no virtual switch option although I
know there is at least a plan to integrate openvswitch in the future.
2) it can not bring a VM back online in the identical running state if
the hardware crashed, VMware does this by mirroring the ram to a
ramdisk on the SAN the developers of Ovirt consider this to be an edge
case that is often misused, and I think they are right. it slows down
writes to the VM's ram significantly and eats the cache on the SAN
slowing down every thing else on it.
Ovirt is the upstream project.
there is one main difference between ovirt and RHEV, with RHEV you can
use a striped down appliance image on the servers running the VM's,
the appliance is tiny just a few hundred MB and unless its in
maintenance mode (all of the VM's have been automatically migrated off
of it and the management console has temporarily removed it from the
pool of usable servers) it runs with most of volumes mounted as
readonly including the one where it stores its configs so its
considerably hardened. in fact I've run the whole thing off a bootable
SD card slot on a motherboard before in an HP DL385 with no drives or
raid controller. I just loaded it with 8 core CPU's, lots of ram and a
high quality SD card in the slot on the motherboard and it was good to
go.
For storage I suggest using NFS, Gluster (with a minimum of 3 node for
quorum), or a SAN also keep in mind NFS is required for ISO image
storage, and data center migrations. while iSCSI is supported I don't
recommend using it because last I worked with it it had some nasty
race conditions which can stop the system from working until you dig
deep into the database to fix it. Red Hats support can not help you
with it if that happens they say just to drop the database and reload
from backups. that said I have fixed it before by manually deleting
the frozen tasks from the table and triggering the plsql command to
release the lock but it took me a an hour or two to figure it out and
the only reason I was able to is I use to be a PostgreSQL DBA and
could read and understand the PSQL procedures.
On a side note if you are looking at RHEV and Cloudforms its also a
good idea to look at cloudinit as well.


On Sat, Aug 27, 2016 at 10:01 AM, Steven Miano  wrote:
> The upstream of CloudForms is actually: http://manageiq.org/
>
> On Sat, Aug 27, 2016 at 6:16 AM, David Sommerseth
>  wrote:
>>
>> On 27/08/16 09:23, ToddAndMargo wrote:
>> > Hi All,
>> >
>> > Will we be seeing any of this?
>> >
>> >
>> > http://www.infoworld.com/article/3111908/virtualization/red-hat-virtualization-4-woos-vmware-faithful.html
>> >
>> >
>> > And does it have anything to do with qemu-kvm?
>> >
>>
>> AFAIK, Red Hat Virtualization (RHV) is building upon libvirt and
>> qemu-kvm.  The difference is that it comes with a far more powerful
>> management tool than virsh and virt-manager and the host OS is a scaled
>> down RHEL installation fine-tuned for being a virtualization host.
>>
>> Right now I've forgotten what the upstream project of RHV is named, but
>> it should exist such a project.
>>
>> You also have CloudForms, which is an even wider scoped management tool
>> capable of managing more than just libvirt/qemu-kvm virt hosts.  The
>> upstream project for this is called oVirt, IIRC.
>>
>>
>> --
>> kind regards,
>>
>> David Sommerseth
>
>
>
>
> --
> Miano, Steven M.
> http://stevenmiano.com

Re: No installation without dhcp active?

[Lamar Owen]

On 08/26/2016 06:52 PM, prmari...@gmail.com wrote:

You need to define static IP's in darcut format ‎on the kernel boot command 
line now since 7. Look at the kickstart instructions for fedora for details.
Right or wrong the idea behind it is that with IPv6 ‎coming in the future every 
one should be using DHCP every where.

Well, DHCPv6 is, ah, interesting.  Regardless, there are network 
segments and subnets here where I do not want automatic configuration.  
Period.  It shouldn't be easy for someone to plug something in to this 
particular vlan/segment/subnet and just get a usable IP config.  Those 
are my requirements.  In any case, the question was raised about the 
requirement of DHCP, and, no DHCP is NOT required.  If you pass the 
static IP information on the installer command line you won't even have 
to change that information in the installer.


In the example I present I am using the VNC installation method, mostly 
in order to grab screenshots of the installer.  If you're at the console 
or using virtualization and have the true console going in a window, you 
won't need the portions related to VNC below.


I first needed to know the interface name.  For the server I am 
installing this is 'eno1' which I found by booting the CentOS install 
DVD and running the rescue mode, then issuing an 'ifconfig' from the 
rescue shell.


Upon booting the NetInstall CD, I selected 'install' and hit the tab key 
to get to the options.  My command line (partially sanitized) was:
>vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=entOS\x207\x20x86_64 
quiet ip=10.250.130.55::10.250.130.254:24:test.pari.edu:eno1:none 
nameserver=192.168.1.3 vnc vncpasswd=nottherealone


When I connected to 10.250.130.55:1 via VNC I was greeted with the 
normal installer sequence.  The very first thing I did was check the 
network settings, and they were carried over from the command line. I 
selected the install source as a network install and http:// selected in 
the pulldown, and put the URL to the install tree there, following the 
instructions at:
http://www.if-not-true-then-false.com/2014/centos-7-netinstall-guide/?PageSpeed=noscript 
(see specifically section 3.10).


The install is now proceeding, using my http server I selected.  You do 
need to make sure the install source is set up properly; this is found 
in Red Hat's upstream documentation at:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/s1-steps-network-installs-x86.html#idp19192208
(You need to change a few obvious things for either a CentOS or SL install).

While I was writing that last paragraph, the install completed, and I 
have clicked 'reboot' and we'll see if it comes up with the same 
address yep, once the 'license' was accepted in text mode (manually, 
of course, meaning I had to manually type things in on the keyboard 
through the KVM switch) everything came up, with the correct IP address, 
and I'm successfully logged-in with ssh.


While I know that I was installing CentOS 7, the SL 7 is basically 
identical (with different branding, mostly) and should work the same way.


If you don't provide the static IP address information on the command 
line you do have the opportunity to select static (the installer uses 
the term 'Manual') addressing through the Network & Hostname spoke's 
Configure button (located in the lower right quadrant of that spoke's 
screen).  Select the interface, click configure, click the 'IPv4 
Settings' tab, and select 'Manual' from the drop-down next to Method.  
Enter your static addressing information in the appropriate blanks of 
the form, and make sure the interface is set to automatically start in 
the General tab (I didn't screencap the General tab, so it might have a 
different term in the actual dialog).


Hope that helps.

Re: Red Hat's new virtualization

[Steven Miano]

The upstream of CloudForms is actually: http://manageiq.org/

On Sat, Aug 27, 2016 at 6:16 AM, David Sommerseth <
sl+us...@lists.topphemmelig.net> wrote:

> On 27/08/16 09:23, ToddAndMargo wrote:
> > Hi All,
> >
> > Will we be seeing any of this?
> >
> > http://www.infoworld.com/article/3111908/virtualization/red-hat-
> virtualization-4-woos-vmware-faithful.html
> >
> >
> > And does it have anything to do with qemu-kvm?
> >
>
> AFAIK, Red Hat Virtualization (RHV) is building upon libvirt and
> qemu-kvm.  The difference is that it comes with a far more powerful
> management tool than virsh and virt-manager and the host OS is a scaled
> down RHEL installation fine-tuned for being a virtualization host.
>
> Right now I've forgotten what the upstream project of RHV is named, but
> it should exist such a project.
>
> You also have CloudForms, which is an even wider scoped management tool
> capable of managing more than just libvirt/qemu-kvm virt hosts.  The
> upstream project for this is called oVirt, IIRC.
>
>
> --
> kind regards,
>
> David Sommerseth
>



-- 
Miano, Steven M.
http://stevenmiano.com

Re: Red Hat's new virtualization

[Jos Vos]

On Sat, Aug 27, 2016 at 12:16:56PM +0200, David Sommerseth wrote:

> Right now I've forgotten what the upstream project of RHV is named, but
> it should exist such a project.

oVirt

-- 
--Jos Vos 
--X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204

Re: Red Hat's new virtualization

[David Sommerseth]

On 27/08/16 09:23, ToddAndMargo wrote:
> Hi All,
> 
> Will we be seeing any of this?
> 
> http://www.infoworld.com/article/3111908/virtualization/red-hat-virtualization-4-woos-vmware-faithful.html
> 
> 
> And does it have anything to do with qemu-kvm?
> 

AFAIK, Red Hat Virtualization (RHV) is building upon libvirt and
qemu-kvm.  The difference is that it comes with a far more powerful
management tool than virsh and virt-manager and the host OS is a scaled
down RHEL installation fine-tuned for being a virtualization host.

Right now I've forgotten what the upstream project of RHV is named, but
it should exist such a project.

You also have CloudForms, which is an even wider scoped management tool
capable of managing more than just libvirt/qemu-kvm virt hosts.  The
upstream project for this is called oVirt, IIRC.


-- 
kind regards,

David Sommerseth

Red Hat's new virtualization

[ToddAndMargo]

Hi All,

Will we be seeing any of this?

http://www.infoworld.com/article/3111908/virtualization/red-hat-virtualization-4-woos-vmware-faithful.html

And does it have anything to do with qemu-kvm?


Many thanks,
-T

--
~~
Computers are like air conditioners.
They malfunction when you open windows
~~