6:08 a.m.
Hi all, ready for a story? (well, more of a rant, but hopefully it will be a
good UX tale, and may even be entertaining.)
Had one of the groups come to me at work this week and request a OpenStack
setup. When I sat down and discussed their needs, it turns out that they
really only need a multi-hypervisor setup where they can spin up VMs for
their research projects. The VMs should be fairly long-lived, and will have
persistent storage. Their other request is that the storage should be local
on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB drives
for VM storage on each node.) They desire this in order to keep the VM I/O
local - they do not have a SAN of any sort anyhow, and they do not care
about live migration, etc.
In any case, knowing that they did not want to afford a VMware setup (which
is what I'm used to using), I proposed using oVirt to fill their needs,
having heard and read up on it a bit (It's "open-source VMware", right?)
even though I had not used it before (I have however made single-node KVM
hypervisors for their group before, utilizing Open vSwitch, libvirt,
virt-manager etc., so I'm not completely ignorant of KVM/libvirt etc.)
In any case, I took one of their older servers which was already running
CentOS 6.5, installed the requisite packages on it, and in short order had
an engine server up and running (oVirt 3.3.2). That seems to have been the
easy part :-/ Now came the installation of a hypervisor node. I downloaded
and burned an ISO of the latest oVirt node installer
(ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso) and tried to install it on one of
their target Intel servers. On the 1st try I got to the end of the setup
TUI, invoked the Install link, and was promptly thrown an error (sorry, but
forgot what it was, something like "press X for a command prompt, or
Reboot".) No problem, I rebooted, selected booting off the CD again, waited
until the TUI came up, and when I tried to move past the first screen, it
threw me out to a login prompt. OK, enough of that (the server takes a long
time to reboot, and then boot off the CD) - I then thought I would try it on
a VMware Workstation VM (yes, I get the irony, but VMware wkstn can handle
nested virt, so it's a great testbed platform for OpenStack, etc.) because
that would install a heck of a lot faster. That went a lot better - got the
oVirt node 3.0.3 installed on the first try.
More pain was soon to follow, however. I logged in and started configuring
the node. The TUI was easy enough - much like an ESXi node ;) I set the NIC
to IPv4 static, entered in the correct IP info, registered a DNS name for
the IP I had assigned, and then tested pinging the engine, all was good. I
then moved on to the section where you define the engine. I entered in the
FQDN of the engine, verified the key fingerprint, and clicked the "Save and
Register" link at the bottom. That seemed to work, so I completed the rest
of the TUI, and then looked at the oVirt engine web UI. There was my new
node, ready for authorization. I clicked the link to authorize it, and after
a while, the UI came back with "Install Failed" status. Hmmm. So I went back
to the node's TUI, and now some of the screens said that the IP addr was
unconfigured? I went then to the Network screen, and sure enough, the NIC at
the bottom showed "Unconfigured". WTF? So I went and entered in the correct
info back in the IPv4 section, and then arrowed down to the Save link and
clicked it - and the next screen said something like "No info needing
changes, nothing to do." Whaaaa? Went back to the network setup screen, NIC
still showing "Unconfigured" even though the IPv4 info still was there. I
did a ping test at this point from the Ping link on the network setup page,
and what do you know - I could still ping IP's (the engine, the default gw,
etc.) But as I moved around the TUI, other screens still said that the
network was unconfigured. Went back to the Web UI of the engine, put the
host in Maint, then tried to Activate it, still no go - Install Failed. Even
though I had configured the node to allow remote access and set a password,
and also verified via nmap that TCP port 22 on the node was indeed
listening, when I tried to SSH into the node as admin, I immediately got a
"connection closed" message, so that failed as well. Went back to the
node's
network setup page, set the IPv4 to "Disabled", saved it, then went back and
set it back to "Static" then re-entered the IPv4 info. Clicked the Save
link, it went thru the setup again, came back with a success, verified with
ping etc. that networking was working on the node. The engine web UI still
said that it could not connect to the node however. So I put the node in
Maint, and then removed it. I went back to the node, went to the Engine
setup page, and re-did the screen to define the engine on the node. I notice
that after I did this, however, that the node screens went back to saying
that the network was unconfigured. Grrrrrr. But the node was back in the
engine's Web UI, however no joy this time either - "Install failed" again.
Well, the hell with this, said I - I removed the node again from the engine,
and went and installed Fedora 19 minimal install on the VM, so I could use
the directions found in
http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_Host and give that a
try. (At least I can see what's going on with the node's OS using F19.)
Installing F19 on the VM was a breeze, then logged in as root and did the
"yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm"
which ran fine. I then stopped firewalld, and set it not to run at boot
(which is what we typically do anyhow for internal research servers.) Then
went over to the engine UI, and manually added the node. Oh happy day - the
node seemed to install OK - it had the status of "Installing" for quite some
time, and I looked at the processes on the F19 node, and could see python
installer programs running via an SSH session from the engine. HOWEVER, at
the end of the process, the Web UI reported a status of "Non Responsive",
even though the F19 node looks OK (it had sanlock, supervdsmServer, vdsm
processes running.) So thinking that it may take an after-install reboot, I
did that, waited until the node came back up again, then clicked in the
engine web UI and executed the "Confirm 'Host has been rebooted'"
command,
but still no good - the node remains in "Non Responsive" status.
So I have no idea on how to proceed now, and what methods I can use to try
and debug the connectivity problem between the engine and node. And there's
many miles to go in setting up the whole environment. Maaaaaybe OpenStack
would be easier ;-P No, I will press on and try to get this thing
working... It seems it works for others, and looks like the right fit for
the job. Just wish it was easier to get up and running.
Oh yes, I tried reading the docs - go to
http://www.ovirt.org/Quick_Start_Guide#Install_Hosts and click on the link
for "see the oVirt Node deployment documentation." Not too helpful... (Bug
report has been opened.)
Thanks for reading, and any clues on getting a node up and running
gratefully accepted...
- Will
9:53 a.m.
've been there! :-D
I mean exactly same issuse you had on Centos, I had on Fedora 19.
Did you disable selinux on nodes? 'cause that's what is causing SSh
connection closing
My setup:
1 engine on vmware - fedora 19, up-to-date
2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 -
1.1.fc19 with nodes beig in glusterfs cluster also.....
Right now, I'm banging my head against "Operation Add-Disk failed to
complete." , message I have got after adding a new virtual machine and try
to addd its disk
On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com) <
willarddennis(a)live.com> wrote:
Hi all, ready for a story? (well, more of a rant, but hopefully it
will be
a
good UX tale, and may even be entertaining.)
Had one of the groups come to me at work this week and request a OpenStack
setup. When I sat down and discussed their needs, it turns out that they
really only need a multi-hypervisor setup where they can spin up VMs for
their research projects. The VMs should be fairly long-lived, and will have
persistent storage. Their other request is that the storage should be local
on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB
drives
for VM storage on each node.) They desire this in order to keep the VM I/O
local - they do not have a SAN of any sort anyhow, and they do not care
about live migration, etc.
In any case, knowing that they did not want to afford a VMware setup (which
is what I'm used to using), I proposed using oVirt to fill their needs,
having heard and read up on it a bit (It's "open-source VMware", right?)
even though I had not used it before (I have however made single-node KVM
hypervisors for their group before, utilizing Open vSwitch, libvirt,
virt-manager etc., so I'm not completely ignorant of KVM/libvirt etc.)
In any case, I took one of their older servers which was already running
CentOS 6.5, installed the requisite packages on it, and in short order had
an engine server up and running (oVirt 3.3.2). That seems to have been the
easy part :-/ Now came the installation of a hypervisor node. I downloaded
and burned an ISO of the latest oVirt node installer
(ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso) and tried to install it on one of
their target Intel servers. On the 1st try I got to the end of the setup
TUI, invoked the Install link, and was promptly thrown an error (sorry, but
forgot what it was, something like "press X for a command prompt, or
Reboot".) No problem, I rebooted, selected booting off the CD again, waited
until the TUI came up, and when I tried to move past the first screen, it
threw me out to a login prompt. OK, enough of that (the server takes a long
time to reboot, and then boot off the CD) - I then thought I would try it
on
a VMware Workstation VM (yes, I get the irony, but VMware wkstn can handle
nested virt, so it's a great testbed platform for OpenStack, etc.) because
that would install a heck of a lot faster. That went a lot better - got the
oVirt node 3.0.3 installed on the first try.
More pain was soon to follow, however. I logged in and started configuring
the node. The TUI was easy enough - much like an ESXi node ;) I set the
NIC
to IPv4 static, entered in the correct IP info, registered a DNS name for
the IP I had assigned, and then tested pinging the engine, all was good. I
then moved on to the section where you define the engine. I entered in the
FQDN of the engine, verified the key fingerprint, and clicked the "Save and
Register" link at the bottom. That seemed to work, so I completed the rest
of the TUI, and then looked at the oVirt engine web UI. There was my new
node, ready for authorization. I clicked the link to authorize it, and
after
a while, the UI came back with "Install Failed" status. Hmmm. So I went
back
to the node's TUI, and now some of the screens said that the IP addr was
unconfigured? I went then to the Network screen, and sure enough, the NIC
at
the bottom showed "Unconfigured". WTF? So I went and entered in the correct
info back in the IPv4 section, and then arrowed down to the Save link and
clicked it - and the next screen said something like "No info needing
changes, nothing to do." Whaaaa? Went back to the network setup screen, NIC
still showing "Unconfigured" even though the IPv4 info still was there. I
did a ping test at this point from the Ping link on the network setup page,
and what do you know - I could still ping IP's (the engine, the default gw,
etc.) But as I moved around the TUI, other screens still said that the
network was unconfigured. Went back to the Web UI of the engine, put the
host in Maint, then tried to Activate it, still no go - Install Failed.
Even
though I had configured the node to allow remote access and set a password,
and also verified via nmap that TCP port 22 on the node was indeed
listening, when I tried to SSH into the node as admin, I immediately got a
"connection closed" message, so that failed as well. Went back to the
node's
network setup page, set the IPv4 to "Disabled", saved it, then went back
and
set it back to "Static" then re-entered the IPv4 info. Clicked the Save
link, it went thru the setup again, came back with a success, verified with
ping etc. that networking was working on the node. The engine web UI still
said that it could not connect to the node however. So I put the node in
Maint, and then removed it. I went back to the node, went to the Engine
setup page, and re-did the screen to define the engine on the node. I
notice
that after I did this, however, that the node screens went back to saying
that the network was unconfigured. Grrrrrr. But the node was back in the
engine's Web UI, however no joy this time either - "Install failed" again.
Well, the hell with this, said I - I removed the node again from the
engine,
and went and installed Fedora 19 minimal install on the VM, so I could use
the directions found in
http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_Host and give that a
try. (At least I can see what's going on with the node's OS using F19.)
Installing F19 on the VM was a breeze, then logged in as root and did the
"yum localinstall
http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm"
which ran fine. I then stopped firewalld, and set it not to run at boot
(which is what we typically do anyhow for internal research servers.) Then
went over to the engine UI, and manually added the node. Oh happy day - the
node seemed to install OK - it had the status of "Installing" for quite
some
time, and I looked at the processes on the F19 node, and could see python
installer programs running via an SSH session from the engine. HOWEVER, at
the end of the process, the Web UI reported a status of "Non Responsive",
even though the F19 node looks OK (it had sanlock, supervdsmServer, vdsm
processes running.) So thinking that it may take an after-install reboot, I
did that, waited until the node came back up again, then clicked in the
engine web UI and executed the "Confirm 'Host has been rebooted'"
command,
but still no good - the node remains in "Non Responsive" status.
So I have no idea on how to proceed now, and what methods I can use to try
and debug the connectivity problem between the engine and node. And there's
many miles to go in setting up the whole environment. Maaaaaybe OpenStack
would be easier ;-P No, I will press on and try to get this thing
working... It seems it works for others, and looks like the right fit for
the job. Just wish it was easier to get up and running.
Oh yes, I tried reading the docs - go to
http://www.ovirt.org/Quick_Start_Guide#Install_Hosts and click on the link
for "see the oVirt Node deployment documentation." Not too helpful... (Bug
report has been opened.)
Thanks for reading, and any clues on getting a node up and running
gratefully accepted...
- Will
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:35 a.m.
This is a multi-part message in MIME format.
--------------090004060102060500020700
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 17-1-2014 8:53, Gabi C wrote:
've been there! :-D
I mean exactly same issuse you had on Centos, I had on Fedora 19.
Did you disable selinux on nodes? 'cause that's what is causing SSh
connection closing
My setup:
1 engine on vmware - fedora 19, up-to-date
2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 -
1.1.fc19 with nodes beig in glusterfs cluster also.....
Right now, I'm banging my head against "Operation Add-Disk failed to
complete." , message I have got after adding a new virtual machine and
try to addd its disk
On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com)
<willarddennis(a)live.com <mailto:willarddennis@live.com>> wrote:
Hi all, ready for a story? (well, more of a rant, but hopefully it
will be a
good UX tale, and may even be entertaining.)
Had one of the groups come to me at work this week and request a
OpenStack
setup. When I sat down and discussed their needs, it turns out
that they
really only need a multi-hypervisor setup where they can spin up
VMs for
their research projects. The VMs should be fairly long-lived, and
will have
persistent storage. Their other request is that the storage should
be local
on the hypervisor nodes (they plan to use Intel servers with 8-10
2TB drives
for VM storage on each node.) They desire this in order to keep
the VM I/O
local - they do not have a SAN of any sort anyhow, and they do not
care
about live migration, etc
@Will
If the installation ends, either with or without error, it will give you
a log location. Upload the log to a paste.bin and mail the link.
@Gabi,
There should be more info in either the vdsm.log on the SPM server or in
the engine.log on the engine server, see above for lettings us know what
the error is.
Having installed oVirt, probably dozens of times, I have some guidelines:
- temporarily disable firewalld/iptables (if all works, enable should
still work, scripts with rules are generated and location is given)
- make selinux permissive either via setenforce 0 (until next boot) or
via /etc/selinux/config ( survives reboots), dont disable it!
- make sure fqdn work in both directions between engine and host(s)
(either using /etc/hosts or DNS)
- make sure NetworkManager is disabled and network enabled
Joop
--------------090004060102060500020700
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 17-1-2014 8:53, Gabi C
wrote:<br>
</div>
<blockquote
cite="mid:CAJcUOahJUqi4YLJ+_G0F9_djuH2hxNS3WcenkTsWg1471ZDO2w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>'ve been there! :-D<br>
<br>
</div>
I mean exactly same issuse you had on Centos, I had on
Fedora 19.<br>
</div>
Did you disable selinux on nodes? 'cause that's what is
causing SSh connection closing<br>
<br>
</div>
<div>My setup:<br>
<br>
</div>
<div>1 engine on vmware - fedora 19, up-to-date<br>
</div>
<div><br>
<div>
<div><br>
</div>
<div>2 nodes on IBM x series 3650 - fedora 19 based -oVirt
Node - 3.0.3 - 1.1.fc19 with nodes beig in glusterfs
cluster also.....<br>
<br>
<br>
</div>
<div>Right now, I'm banging my head against "Operation
Add-Disk failed to complete." , message I have got after
adding a new virtual machine and try to addd its disk<br>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Jan 17, 2014 at 6:08 AM, Will
Dennis (Live.com) <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:willarddennis@live.com"
target="_blank">willarddennis(a)live.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,
ready for a story? (well, more of a rant, but hopefully it
will be a<br>
good UX tale, and may even be entertaining.)<br>
<br>
Had one of the groups come to me at work this week and
request a OpenStack<br>
setup. When I sat down and discussed their needs, it turns
out that they<br>
really only need a multi-hypervisor setup where they can
spin up VMs for<br>
their research projects. The VMs should be fairly
long-lived, and will have<br>
persistent storage. Their other request is that the storage
should be local<br>
on the hypervisor nodes (they plan to use Intel servers with
8-10 2TB drives<br>
for VM storage on each node.) They desire this in order to
keep the VM I/O<br>
local - they do not have a SAN of any sort anyhow, and they
do not care<br>
about live migration, etc<br>
</blockquote>
</div>
</div>
</blockquote>
@Will<br>
If the installation ends, either with or without error, it will give
you a log location. Upload the log to a paste.bin and mail the link.<br>
<br>
@Gabi,<br>
There should be more info in either the vdsm.log on the SPM server
or in the engine.log on the engine server, see above for lettings us
know what the error is.<br>
<br>
Having installed oVirt, probably dozens of times, I have some
guidelines:<br>
- temporarily disable firewalld/iptables (if all works, enable
should still work, scripts with rules are generated and location is
given)<br>
- make selinux permissive either via setenforce 0 (until next boot)
or via /etc/selinux/config ( survives reboots), dont disable it!<br>
- make sure fqdn work in both directions between engine and host(s)
(either using /etc/hosts or DNS)<br>
- make sure NetworkManager is disabled and network enabled<br>
<br>
Joop<br>
<br>
</body>
</html>
--------------090004060102060500020700--
12:06 p.m.
Hi Joop,
1. I did disabled firewalld/iptbles on both nodes and engines.
2. Disabling selinux: when setting to permissive via /etc/selinux/config
(and of course unpersist/persist them -> /config/etc........) doesn't work
( as write this I've just reboot one node with the above modification and
when I try to ssh node I get "connection closed by..." - of course selinux
is enabled; after setenforce 0 ssh is OK.The only way I manage to diasble
selinux was
mount -o.rw,remount /run/initramfs/live
edit grub.cfg and add selinux=0 to kernel line
3. one strange issue: after I reboot nodes, trying to ssh raise ssh warning
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! " so I have to remove host
entry from .ssh/.known_host in order to connect
4. I am about to check name resolution
5.I have glusterfs also on both nodes. After I put nodes on maintenace,
stop gluster volumes and rebooting nodes caused gluster volumes to
dissapear from engine web interface
Thanks
On Fri, Jan 17, 2014 at 10:35 AM, noc <noc(a)nieuwland.nl> wrote:
On 17-1-2014 8:53, Gabi C wrote:
've been there! :-D
I mean exactly same issuse you had on Centos, I had on Fedora 19.
Did you disable selinux on nodes? 'cause that's what is causing SSh
connection closing
My setup:
1 engine on vmware - fedora 19, up-to-date
2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 -
1.1.fc19 with nodes beig in glusterfs cluster also.....
Right now, I'm banging my head against "Operation Add-Disk failed to
complete." , message I have got after adding a new virtual machine and try
to addd its disk
On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com) <
willarddennis(a)live.com> wrote:
> Hi all, ready for a story? (well, more of a rant, but hopefully it will
> be a
> good UX tale, and may even be entertaining.)
>
> Had one of the groups come to me at work this week and request a OpenStack
> setup. When I sat down and discussed their needs, it turns out that they
> really only need a multi-hypervisor setup where they can spin up VMs for
> their research projects. The VMs should be fairly long-lived, and will
> have
> persistent storage. Their other request is that the storage should be
> local
> on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB
> drives
> for VM storage on each node.) They desire this in order to keep the VM I/O
> local - they do not have a SAN of any sort anyhow, and they do not care
> about live migration, etc
>
@Will
If the installation ends, either with or without error, it will give you a
log location. Upload the log to a paste.bin and mail the link.
@Gabi,
There should be more info in either the vdsm.log on the SPM server or in
the engine.log on the engine server, see above for lettings us know what
the error is.
Having installed oVirt, probably dozens of times, I have some guidelines:
- temporarily disable firewalld/iptables (if all works, enable should
still work, scripts with rules are generated and location is given)
- make selinux permissive either via setenforce 0 (until next boot) or via
/etc/selinux/config ( survives reboots), dont disable it!
- make sure fqdn work in both directions between engine and host(s)
(either using /etc/hosts or DNS)
- make sure NetworkManager is disabled and network enabled
Joop
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:04 p.m.
Hi,
my advice would be the following:
for "nodes" use either a "full"
minimal centos or fedora and install ovirt.org
repo on top of that.
then everything works.
the "node.isos" provided by ovirt are in pre-alpha
state to be honest.
sure you still have to disable selinux
(or better configure it correctly).
But you have no problems with configurations which are
not persisted and as a bonus you can install
$your_favourite_tool on the node, such as tcpdump
nmap etc. for debugging.
Again: I would strongly advise against useing
the node.isos from ovirt.org at the moment.
There is just too much stuff not working
or bugged, even simple things like network
configuration.
HTH
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
1:09 p.m.
Thanks Sven!
On Fri, Jan 17, 2014 at 1:04 PM, Sven Kieske <S.Kieske(a)mittwald.de> wrote:
Hi,
my advice would be the following:
for "nodes" use either a "full"
minimal centos or fedora and install ovirt.org
repo on top of that.
then everything works.
the "node.isos" provided by ovirt are in pre-alpha
state to be honest.
sure you still have to disable selinux
(or better configure it correctly).
But you have no problems with configurations which are
not persisted and as a bonus you can install
$your_favourite_tool on the node, such as tcpdump
nmap etc. for debugging.
Again: I would strongly advise against useing
the node.isos from ovirt.org at the moment.
There is just too much stuff not working
or bugged, even simple things like network
configuration.
HTH
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:54 p.m.
Docs should be updated with a warning then as to the "alpha" status of the
ovirt-node product... It was a huge time-sink for me.
- Will
-----Original Message-----
From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Sven Kieske
Sent: Friday, January 17, 2014 6:05 AM
To: users(a)ovirt.org; users(a)ovirt.org
Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
Hi,
my advice would be the following:
for "nodes" use either a "full"
minimal centos or fedora and install ovirt.org repo on top of that.
then everything works.
the "node.isos" provided by ovirt are in pre-alpha state to be honest.
sure you still have to disable selinux
(or better configure it correctly).
But you have no problems with configurations which are not persisted and as a bonus you
can install $your_favourite_tool on the node, such as tcpdump nmap etc. for debugging.
Again: I would strongly advise against useing the node.isos from ovirt.org at the moment.
There is just too much stuff not working or bugged, even simple things like network
configuration.
HTH
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
6:55 p.m.
------=_NextPart_000_0059_01CF137B.148269F0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thanks, Joop, for the node platform best practices. I did turn selinux from
"enforcing" to "permissive", and then when I tried to ping the engine
by
fqdn, I saw that DNS lookups were failing (even tho resolv.conf looked
correct.) Did a 'yum remove NetworkManager" and then fixed the
/etc/sysconfig/network-scripts/ifcfg-<nic>, and then after a reboot, I can
now see the info for the node in the WUI on the manager, although the status
for the node is still "Non Operational".
Where can I find the node install log (on the engine or the node, and name?)
(Sorry for noob status, but I am a quick learner ;)
Thanks,
Will
From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of
noc
Sent: Friday, January 17, 2014 3:35 AM
To: users(a)ovirt.org
Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
On 17-1-2014 8:53, Gabi C wrote:
've been there! :-D
I mean exactly same issuse you had on Centos, I had on Fedora 19.
Did you disable selinux on nodes? 'cause that's what is causing SSh
connection closing
My setup:
1 engine on vmware - fedora 19, up-to-date
2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 -
1.1.fc19 with nodes beig in glusterfs cluster also.....
Right now, I'm banging my head against "Operation Add-Disk failed to
complete." , message I have got after adding a new virtual machine and try
to addd its disk
On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com)
<willarddennis(a)live.com> wrote:
Hi all, ready for a story? (well, more of a rant, but hopefully it will be a
good UX tale, and may even be entertaining.)
Had one of the groups come to me at work this week and request a OpenStack
setup. When I sat down and discussed their needs, it turns out that they
really only need a multi-hypervisor setup where they can spin up VMs for
their research projects. The VMs should be fairly long-lived, and will have
persistent storage. Their other request is that the storage should be local
on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB drives
for VM storage on each node.) They desire this in order to keep the VM I/O
local - they do not have a SAN of any sort anyhow, and they do not care
about live migration, etc
@Will
If the installation ends, either with or without error, it will give you a
log location. Upload the log to a paste.bin and mail the link.
@Gabi,
There should be more info in either the vdsm.log on the SPM server or in the
engine.log on the engine server, see above for lettings us know what the
error is.
Having installed oVirt, probably dozens of times, I have some guidelines:
- temporarily disable firewalld/iptables (if all works, enable should still
work, scripts with rules are generated and location is given)
- make selinux permissive either via setenforce 0 (until next boot) or via
/etc/selinux/config ( survives reboots), dont disable it!
- make sure fqdn work in both directions between engine and host(s) (either
using /etc/hosts or DNS)
- make sure NetworkManager is disabled and network enabled
Joop
------=_NextPart_000_0059_01CF137B.148269F0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite
=
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks, Joop, for the node platform best practices… I did turn =
selinux from “enforcing” to “permissive”, and =
then when I tried to ping the engine by fqdn, I saw that DNS lookups =
were failing (even tho resolv.conf looked correct…) Did a =
‘yum remove NetworkManager” and then fixed the =
/etc/sysconfig/network-scripts/ifcfg-<nic>, and then after a =
reboot, I can now see the info for the node in the WUI on the manager, =
although the status for the node is still “Non =
Operational”… <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p> </o:p></span></p><p
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Where can I find the node install log (on the engine or the node, and =
name?) (Sorry for noob status, but I am a quick learner =
;)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p> </o:p></span></p><p
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,<o:p></o:p></span></p><p
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Will<o:p></o:p></span></p><p
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p> </o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] <b>On =
Behalf Of </b>noc<br><b>Sent:</b> Friday, January 17, 2014 3:35 =
AM<br><b>To:</b> users@ovirt.org<br><b>Subject:</b>
Re: [Users] New user =
to oVirt, and I haz a sad so
far...<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p> </o:p></p><div><p
class=3DMsoNormal>On =
17-1-2014 8:53, Gabi C wrote:<o:p></o:p></p></div><blockquote
=
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><div><p
=
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>'ve been there! =
:-D<o:p></o:p></p></div><p class=3DMsoNormal>I mean exactly
same issuse =
you had on Centos, I had on Fedora 19.<o:p></o:p></p></div><p
=
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Did you disable selinux =
on nodes? 'cause that's what is causing SSh connection =
closing<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>My
setup:<o:p></o:p></p></div><div><p =
class=3DMsoNormal>1 engine on vmware - fedora 19, =
up-to-date<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p> </o:p></p><div><div><p
=
class=3DMsoNormal><o:p> </o:p></p></div><div><p
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>2 nodes on IBM x series 3650 - =
fedora 19 based -oVirt Node - 3.0.3 - 1.1.fc19 with nodes beig in =
glusterfs cluster
also.....<br><br><o:p></o:p></p></div><div><p
=
class=3DMsoNormal>Right now, I'm banging my head against "Operation =
Add-Disk failed to complete." , message I have got after adding a =
new virtual machine and try to addd its =
disk<o:p></o:p></p></div></div></div></div><div><p
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p> </o:p></p><div><p
=
class=3DMsoNormal>On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis =
(Live.com) <<a href=3D"mailto:willarddennis@live.com" =
target=3D"_blank">willarddennis(a)live.com</a>&gt;
wrote:<o:p></o:p></p><p =
class=3DMsoNormal>Hi all, ready for a story? (well, more of a rant, but =
hopefully it will be a<br>good UX tale, and may even be =
entertaining.)<br><br>Had one of the groups come to me at work this week =
and request a OpenStack<br>setup. When I sat down and discussed their =
needs, it turns out that they<br>really only need a multi-hypervisor =
setup where they can spin up VMs for<br>their research projects. The VMs =
should be fairly long-lived, and will have<br>persistent storage. Their =
other request is that the storage should be local<br>on the hypervisor =
nodes (they plan to use Intel servers with 8-10 2TB drives<br>for VM =
storage on each node.) They desire this in order to keep the VM =
I/O<br>local - they do not have a SAN of any sort anyhow, and they do =
not care<br>about live migration, =
etc<o:p></o:p></p></div></div></blockquote><p
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>@Will<br>If the installation ends, either
=
with or without error, it will give you a log location. Upload the log =
to a paste.bin and mail the link.<br><br>@Gabi,<br>There should be more
=
info in either the vdsm.log on the SPM server or in the engine.log on =
the engine server, see above for lettings us know what the error =
is.<br><br>Having installed oVirt, probably dozens of times, I have some =
guidelines:<br>- temporarily disable firewalld/iptables (if all works, =
enable should still work, scripts with rules are generated and location =
is given)<br>- make selinux permissive either via setenforce 0 (until =
next boot) or via /etc/selinux/config ( survives reboots), dont disable =
it!<br>- make sure fqdn work in both directions between engine and =
host(s) (either using /etc/hosts or DNS)<br>- make sure NetworkManager =
is disabled and network =
enabled<br><br>Joop<o:p></o:p></p></div></body></html>
------=_NextPart_000_0059_01CF137B.148269F0--
6:58 p.m.
Non-operational means it's connected, but missing a cluster resource (can't
access a storage domain, or misses one of the network definitions the
cluster should have)
On Fri, Jan 17, 2014 at 9:55 AM, Will Dennis (Live.com) <
willarddennis(a)live.com> wrote:
Thanks, Joop, for the node platform best practices… I did turn
selinux
from “enforcing” to “permissive”, and then when I tried to ping the engine
by fqdn, I saw that DNS lookups were failing (even tho resolv.conf looked
correct…) Did a ‘yum remove NetworkManager” and then fixed the
/etc/sysconfig/network-scripts/ifcfg-<nic>, and then after a reboot, I can
now see the info for the node in the WUI on the manager, although the
status for the node is still “Non Operational”…
Where can I find the node install log (on the engine or the node, and
name?) (Sorry for noob status, but I am a quick learner ;)
Thanks,
Will
*From:* users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] *On
Behalf Of *noc
*Sent:* Friday, January 17, 2014 3:35 AM
*To:* users(a)ovirt.org
*Subject:* Re: [Users] New user to oVirt, and I haz a sad so far...
On 17-1-2014 8:53, Gabi C wrote:
've been there! :-D
I mean exactly same issuse you had on Centos, I had on Fedora 19.
Did you disable selinux on nodes? 'cause that's what is causing SSh
connection closing
My setup:
1 engine on vmware - fedora 19, up-to-date
2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 -
1.1.fc19 with nodes beig in glusterfs cluster also.....
Right now, I'm banging my head against "Operation Add-Disk failed to
complete." , message I have got after adding a new virtual machine and try
to addd its disk
On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com) <
willarddennis(a)live.com> wrote:
Hi all, ready for a story? (well, more of a rant, but hopefully it will be
a
good UX tale, and may even be entertaining.)
Had one of the groups come to me at work this week and request a OpenStack
setup. When I sat down and discussed their needs, it turns out that they
really only need a multi-hypervisor setup where they can spin up VMs for
their research projects. The VMs should be fairly long-lived, and will have
persistent storage. Their other request is that the storage should be local
on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB
drives
for VM storage on each node.) They desire this in order to keep the VM I/O
local - they do not have a SAN of any sort anyhow, and they do not care
about live migration, etc
@Will
If the installation ends, either with or without error, it will give you a
log location. Upload the log to a paste.bin and mail the link.
@Gabi,
There should be more info in either the vdsm.log on the SPM server or in
the engine.log on the engine server, see above for lettings us know what
the error is.
Having installed oVirt, probably dozens of times, I have some guidelines:
- temporarily disable firewalld/iptables (if all works, enable should
still work, scripts with rules are generated and location is given)
- make selinux permissive either via setenforce 0 (until next boot) or via
/etc/selinux/config ( survives reboots), dont disable it!
- make sure fqdn work in both directions between engine and host(s)
(either using /etc/hosts or DNS)
- make sure NetworkManager is disabled and network enabled
Joop
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:10 p.m.
----- Original Message -----
From: "Will Dennis (Live.com)" <willarddennis(a)live.com>
Sent: Friday, January 17, 2014 11:55:55 AM
Thanks, Joop, for the node platform best practices… I did turn selinux from
“enforcing” to “permissive”, and then when I tried to ping the engine by
fqdn, I saw that DNS lookups were failing (even tho resolv.conf looked
correct…) Did a ‘yum remove NetworkManager” and then fixed the
/etc/sysconfig/network-scripts/ifcfg-<nic>, and then after a reboot, I can
now see the info for the node in the WUI on the manager, although the status
for the node is still “Non Operational”…
In the GUI, within the "Events" sub-tab of that node, there should be an error
message detailing the reason for that node being in the Non-Operational state;
what does this message say?
Where can I find the node install log (on the engine or the node, and name?)
(Sorry for noob status, but I am a quick learner ;)
Thanks,
Will
From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of
noc
Sent: Friday, January 17, 2014 3:35 AM
To: users(a)ovirt.org
Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
On 17-1-2014 8:53, Gabi C wrote:
've been there! :-D
I mean exactly same issuse you had on Centos, I had on Fedora 19.
Did you disable selinux on nodes? 'cause that's what is causing SSh
connection closing
My setup:
1 engine on vmware - fedora 19, up-to-date
2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 - 1.1.fc19
with nodes beig in glusterfs cluster also.....
Right now, I'm banging my head against "Operation Add-Disk failed to
complete." , message I have got after adding a new virtual machine and try
to addd its disk
On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com) <
willarddennis(a)live.com > wrote:
Hi all, ready for a story? (well, more of a rant, but hopefully it will be a
good UX tale, and may even be entertaining.)
Had one of the groups come to me at work this week and request a OpenStack
setup. When I sat down and discussed their needs, it turns out that they
really only need a multi-hypervisor setup where they can spin up VMs for
their research projects. The VMs should be fairly long-lived, and will have
persistent storage. Their other request is that the storage should be local
on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB drives
for VM storage on each node.) They desire this in order to keep the VM I/O
local - they do not have a SAN of any sort anyhow, and they do not care
about live migration, etc
@Will
If the installation ends, either with or without error, it will give you a
log location. Upload the log to a paste.bin and mail the link.
@Gabi,
There should be more info in either the vdsm.log on the SPM server or in the
engine.log on the engine server, see above for lettings us know what the
error is.
Having installed oVirt, probably dozens of times, I have some guidelines:
- temporarily disable firewalld/iptables (if all works, enable should still
work, scripts with rules are generated and location is given)
- make selinux permissive either via setenforce 0 (until next boot) or via
/etc/selinux/config ( survives reboots), dont disable it!
- make sure fqdn work in both directions between engine and host(s) (either
using /etc/hosts or DNS)
- make sure NetworkManager is disabled and network enabled
Joop
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:15 p.m.
--_5b0e3953-d7c8-4a2c-b20f-5df60a985828_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Aha!
"Host <hostname> does not comply with the cluster Default networks=2C the f=
ollowing networks are missing on host: 'ovirtmgmt' "
=20
What must I do to correct this? I do not remember reading about having to d=
o something like this in the docs... Also=2C the node is on a different net=
work that the engine=2C not sure if this matters or not (the two network do=
have connectivity to each other thru a router.)
=20
Thanks=2C
Will
=20
Date: Fri=2C 17 Jan 2014 12:10:50 -0500
From: ecohen(a)redhat.com
To: willarddennis(a)live.com
CC: noc(a)nieuwland.nl=3B users(a)ovirt.org
Subject: Re: [Users] New user to oVirt=2C and I haz a sad so far...
=20
> ----- Original Message -----
> From: "Will Dennis (Live.com)" <willarddennis(a)live.com>
> Sent: Friday=2C January 17=2C 2014 11:55:55 AM
>=20
>=20
>=20
> Thanks=2C Joop=2C for the node platform best practices=85 I did turn se=
linux
from
> =93enforcing=94 to =93permissive=94=2C and then when I tried to
ping th=
e engine by
> fqdn=2C I saw that DNS lookups were failing (even tho
resolv.conf looke=
d
> correct=85) Did a =91yum remove NetworkManager=94 and then fixed
the
> /etc/sysconfig/network-scripts/ifcfg-<nic>=2C and then after a reboot=
=2C I can
> now see the info for the node in the WUI on the manager=2C
although the=
status
> for the node is still =93Non Operational=94=85
=20
In the GUI=2C within the "Events" sub-tab of that node=2C there should be=
an error=20
message detailing the reason for that node being in the
Non-Operational s=
tate=3B=20
what does this message say?
=20
>=20
>=20
>=20
> Where can I find the node install log (on the engine or the node=2C and=
name?)
> (Sorry for noob status=2C but I am a quick learner =3B)
>=20
>=20
>=20
> Thanks=2C
>=20
> Will
>=20
>=20
>=20
>=20
> From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behal=
f Of
> noc
> Sent: Friday=2C January 17=2C 2014 3:35 AM
> To: users(a)ovirt.org
> Subject: Re: [Users] New user to oVirt=2C and I haz a sad so far...
>=20
>=20
>=20
>=20
>=20
> On 17-1-2014 8:53=2C Gabi C wrote:
>=20
>=20
>=20
>=20
>=20
> 've been there! :-D
>=20
>=20
> I mean exactly same issuse you had on Centos=2C I had on Fedora 19.
>=20
>=20
> Did you disable selinux on nodes? 'cause that's what is causing SSh
> connection closing
>=20
>=20
> My setup:
>=20
>=20
> 1 engine on vmware - fedora 19=2C up-to-date
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> 2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 - 1.=
1.fc19
> with nodes beig in glusterfs cluster also.....
>=20
>=20
>=20
> Right now=2C I'm banging my head against "Operation Add-Disk failed to
> complete." =2C message I have got after adding a new virtual machine an=
d try
> to addd its disk
>=20
>=20
>=20
>=20
>=20
> On Fri=2C Jan 17=2C 2014 at 6:08 AM=2C Will Dennis (Live.com) <
> willarddennis(a)live.com > wrote:
>=20
> Hi all=2C ready for a story? (well=2C more of a rant=2C but hopefully i=
t
will be a
> good UX tale=2C and may even be entertaining.)
>=20
> Had one of the groups come to me at work this week and request a OpenSt=
ack
> setup. When I sat down and discussed their needs=2C it turns out
that t=
hey
> really only need a multi-hypervisor setup where they can spin up
VMs fo=
r
> their research projects. The VMs should be fairly long-lived=2C
and wil=
l have
> persistent storage. Their other request is that the storage
should be l=
ocal
> on the hypervisor nodes (they plan to use Intel servers with
8-10 2TB d=
rives
> for VM storage on each node.) They desire this in order to keep
the VM =
I/O
> local - they do not have a SAN of any sort anyhow=2C and they do
not ca=
re
> about live migration=2C etc
>=20
>=20
> @Will
> If the installation ends=2C either with or without error=2C it will giv=
e you
a
> log location. Upload the log to a paste.bin and mail the link.
>=20
> @Gabi=2C
> There should be more info in either the vdsm.log on the SPM server or i=
n
the
> engine.log on the engine server=2C see above for lettings us
know what =
the
> error is.
>=20
> Having installed oVirt=2C probably dozens of times=2C I have some guide=
lines:
> - temporarily disable firewalld/iptables (if all works=2C enable
should=
still
> work=2C scripts with rules are generated and location is given)
> - make selinux permissive either via setenforce 0 (until next boot) or =
via
> /etc/selinux/config ( survives reboots)=2C dont disable it!
> - make sure fqdn work in both directions between engine and host(s) (ei=
ther
> using /etc/hosts or DNS)
> - make sure NetworkManager is disabled and network enabled
>=20
> Joop
>=20
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>=20
=
--_5b0e3953-d7c8-4a2c-b20f-5df60a985828_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div
dir=3D'ltr'>Aha!<BR>"Host <=3Bhostname>=
=3B does not comply with the cluster Default networks=2C the following netw=
orks are missing on host: 'ovirtmgmt' "<BR> =3B<BR>What
must I do to co=
rrect this? I do not remember reading about having to do something like thi=
s in the docs... Also=2C the node is on =3Ba different network that the=
engine=2C not sure if this matters or not (the two network do have connect=
ivity to each other thru a
router.)<BR> =3B<BR>Thanks=2C<BR>Will<br>&nb=
sp=3B<BR><div>>=3B Date: Fri=2C 17 Jan 2014 12:10:50
-0500<br>>=3B From=
: ecohen(a)redhat.com<br>&gt=3B To: willarddennis(a)live.com<br>&gt=3B CC:
noc@=
nieuwland.nl=3B users(a)ovirt.org<br>&gt=3B Subject: Re: [Users] New user to =
oVirt=2C and I haz a sad so far...<br>>=3B <br>>=3B >=3B
----- Origin=
al Message -----<br>>=3B >=3B From: "Will Dennis (Live.com)"
<=3Bwill=
arddennis(a)live.com&gt=3B<br>&gt=3B >=3B Sent: Friday=2C January 17=2C
201=
4 11:55:55 AM<br>>=3B >=3B <br>>=3B >=3B
<br>>=3B >=3B <br>>=
=3B >=3B Thanks=2C Joop=2C for the node platform best practices=85 I did =
turn selinux from<br>>=3B >=3B =93enforcing=94 to =93permissive=94=2C
a=
nd then when I tried to ping the engine by<br>>=3B >=3B fqdn=2C I saw
t=
hat DNS lookups were failing (even tho resolv.conf looked<br>>=3B >=3B
=
correct=85) Did a =91yum remove NetworkManager=94 and then fixed the<br>>=
=3B >=3B /etc/sysconfig/network-scripts/ifcfg-<=3Bnic>=3B=2C and then=
after a reboot=2C I can<br>>=3B >=3B now see the info for the node in
=
the WUI on the manager=2C although the status<br>>=3B >=3B for the
node=
is still =93Non Operational=94=85<br>>=3B <br>>=3B In the GUI=2C
withi=
n the "Events" sub-tab of that node=2C there should be an error
<br>>=3B =
message detailing the reason for that node being in the Non-Operational sta=
te=3B <br>>=3B what does this message say?<br>>=3B
<br>>=3B >=3B <b=
r>>=3B >=3B <br>>=3B >=3B <br>>=3B >=3B
Where can I find the no=
de install log (on the engine or the node=2C and name?)<br>>=3B >=3B
(S=
orry for noob status=2C but I am a quick learner =3B)<br>>=3B >=3B
<br>=
>=3B >=3B <br>>=3B >=3B <br>>=3B >=3B
Thanks=2C<br>>=3B >=
=3B <br>>=3B >=3B Will<br>>=3B >=3B
<br>>=3B >=3B <br>>=3B &g=
t=3B <br>>=3B >=3B <br>>=3B >=3B From:
users-bounces(a)ovirt.org [mai=
lto:users-bounces@ovirt.org] On Behalf Of<br>>=3B >=3B
noc<br>>=3B &g=
t=3B Sent: Friday=2C January 17=2C 2014 3:35 AM<br>>=3B >=3B To:
users@=
ovirt.org<br>>=3B >=3B Subject: Re: [Users] New user to oVirt=2C and I
=
haz a sad so far...<br>>=3B >=3B <br>>=3B >=3B
<br>>=3B >=3B <b=
r>>=3B >=3B <br>>=3B >=3B <br>>=3B >=3B
On 17-1-2014 8:53=2C Ga=
bi C wrote:<br>>=3B >=3B <br>>=3B >=3B
<br>>=3B >=3B <br>>=3B=
>=3B <br>>=3B >=3B <br>>=3B >=3B 've been
there! :-D<br>>=3B &=
gt=3B <br>>=3B >=3B <br>>=3B >=3B I mean exactly same
issuse you ha=
d on Centos=2C I had on Fedora 19.<br>>=3B >=3B <br>>=3B
>=3B <br>&=
gt=3B >=3B Did you disable selinux on nodes? 'cause that's what is causin=
g SSh<br>>=3B >=3B connection closing<br>>=3B >=3B
<br>>=3B >=
=3B <br>>=3B >=3B My setup:<br>>=3B >=3B
<br>>=3B >=3B <br>>=
=3B >=3B 1 engine on vmware - fedora 19=2C up-to-date<br>>=3B >=3B
<b=
r>>=3B >=3B <br>>=3B >=3B <br>>=3B >=3B
<br>>=3B >=3B <br>&=
gt=3B >=3B <br>>=3B >=3B <br>>=3B >=3B
<br>>=3B >=3B 2 nodes =
on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 - 1.1.fc19<br>&g=
t=3B >=3B with nodes beig in glusterfs cluster also.....<br>>=3B
>=3B=
<br>>=3B >=3B <br>>=3B >=3B <br>>=3B
>=3B Right now=2C I'm ban=
ging my head against "Operation Add-Disk failed to<br>>=3B >=3B
complet=
e." =2C message I have got after adding a new virtual machine and
try<br>&g=
t=3B >=3B to addd its disk<br>>=3B >=3B <br>>=3B
>=3B <br>>=3B =
>=3B <br>>=3B >=3B <br>>=3B >=3B
<br>>=3B >=3B On Fri=2C Jan =
17=2C 2014 at 6:08 AM=2C Will Dennis (Live.com) <=3B<br>>=3B >=3B
wil=
larddennis(a)live.com >=3B wrote:<br>>=3B >=3B <br>>=3B
>=3B Hi all=
=2C ready for a story? (well=2C more of a rant=2C but hopefully it will be =
a<br>>=3B >=3B good UX tale=2C and may even be
entertaining.)<br>>=3B=
>=3B <br>>=3B >=3B Had one of the groups come to me at work this
wee=
k and request a OpenStack<br>>=3B >=3B setup. When I sat down and
discu=
ssed their needs=2C it turns out that they<br>>=3B >=3B really only
nee=
d a multi-hypervisor setup where they can spin up VMs for<br>>=3B >=3B
=
their research projects. The VMs should be fairly long-lived=2C and will ha=
ve<br>>=3B >=3B persistent storage. Their other request is that the
sto=
rage should be local<br>>=3B >=3B on the hypervisor nodes (they plan
to=
use Intel servers with 8-10 2TB drives<br>>=3B >=3B for VM storage on
=
each node.) They desire this in order to keep the VM I/O<br>>=3B >=3B
l=
ocal - they do not have a SAN of any sort anyhow=2C and they do not care<br=
>=3B >=3B about live migration=2C etc<br>>=3B
>=3B <br>>=3B >=
=3B <br>>=3B >=3B
@Will<br>>=3B >=3B If the installation ends=2C ei=
ther with or without error=2C it will give you a<br>>=3B >=3B log
locat=
ion. Upload the log to a paste.bin and mail the link.<br>>=3B >=3B
<br>=
>=3B >=3B @Gabi=2C<br>>=3B >=3B There should be more info in
either=
the vdsm.log on the SPM server or in the<br>>=3B >=3B engine.log on
th=
e engine server=2C see above for lettings us know what the<br>>=3B
>=3B=
error is.<br>>=3B >=3B <br>>=3B >=3B Having installed
oVirt=2C pro=
bably dozens of times=2C I have some guidelines:<br>>=3B >=3B -
tempora=
rily disable firewalld/iptables (if all works=2C enable should still<br>>=
=3B >=3B work=2C scripts with rules are generated and location is given)<=
br>>=3B >=3B - make selinux permissive either via setenforce 0 (until n=
ext boot) or via<br>>=3B >=3B /etc/selinux/config ( survives reboots)=
=2C dont disable it!<br>>=3B >=3B - make sure fqdn work in both
directi=
ons between engine and host(s) (either<br>>=3B >=3B using /etc/hosts
or=
DNS)<br>>=3B >=3B - make sure NetworkManager is disabled and network
e=
nabled<br>>=3B >=3B <br>>=3B >=3B
Joop<br>>=3B >=3B <br>>=3B =
>=3B _______________________________________________<br>>=3B >=3B
Use=
rs mailing list<br>>=3B >=3B Users(a)ovirt.org<br>&gt=3B
>=3B http://li=
sts.ovirt.org/mailman/listinfo/users<br>>=3B >=3B <br></div>
=
</div></body>
</html>=
--_5b0e3953-d7c8-4a2c-b20f-5df60a985828_--
7:18 p.m.
go to the "Network Interface" sub-tab of that node and click the "Setup
Host Networks" button.
In the dialog that has opened, attach the 'ovirtmgmt' network from the
right-hand side of the dialog to one of your node's NICs on the left-hand
side by dragging that network onto the NIC.
click OK.
after a short while, your Host should become 'Up'.
----- Original Message -----
From: "Willard Dennis" <willarddennis(a)live.com>
To: "Einav Cohen" <ecohen(a)redhat.com>
Cc: "noc" <noc(a)nieuwland.nl>, users(a)ovirt.org
Sent: Friday, January 17, 2014 12:15:22 PM
Subject: RE: [Users] New user to oVirt, and I haz a sad so far...
Aha!
"Host <hostname> does not comply with the cluster Default networks, the
following networks are missing on host: 'ovirtmgmt' "
What must I do to correct this? I do not remember reading about having to do
something like this in the docs... Also, the node is on a different network
that the engine, not sure if this matters or not (the two network do have
connectivity to each other thru a router.)
Thanks,
Will
> Date: Fri, 17 Jan 2014 12:10:50 -0500
> From: ecohen(a)redhat.com
> To: willarddennis(a)live.com
> CC: noc(a)nieuwland.nl; users(a)ovirt.org
> Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
>
> > ----- Original Message -----
> > From: "Will Dennis (Live.com)" <willarddennis(a)live.com>
> > Sent: Friday, January 17, 2014 11:55:55 AM
> >
> >
> >
> > Thanks, Joop, for the node platform best practices… I did turn selinux
> > from
> > “enforcing” to “permissive”, and then when I tried to ping the engine by
> > fqdn, I saw that DNS lookups were failing (even tho resolv.conf looked
> > correct…) Did a ‘yum remove NetworkManager” and then fixed the
> > /etc/sysconfig/network-scripts/ifcfg-<nic>, and then after a reboot, I
> > can
> > now see the info for the node in the WUI on the manager, although the
> > status
> > for the node is still “Non Operational”…
>
> In the GUI, within the "Events" sub-tab of that node, there should be an
> error
> message detailing the reason for that node being in the Non-Operational
> state;
> what does this message say?
>
> >
> >
> >
> > Where can I find the node install log (on the engine or the node, and
> > name?)
> > (Sorry for noob status, but I am a quick learner ;)
> >
> >
> >
> > Thanks,
> >
> > Will
> >
> >
> >
> >
> > From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf
> > Of
> > noc
> > Sent: Friday, January 17, 2014 3:35 AM
> > To: users(a)ovirt.org
> > Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
> >
> >
> >
> >
> >
> > On 17-1-2014 8:53, Gabi C wrote:
> >
> >
> >
> >
> >
> > 've been there! :-D
> >
> >
> > I mean exactly same issuse you had on Centos, I had on Fedora 19.
> >
> >
> > Did you disable selinux on nodes? 'cause that's what is causing SSh
> > connection closing
> >
> >
> > My setup:
> >
> >
> > 1 engine on vmware - fedora 19, up-to-date
> >
> >
> >
> >
> >
> >
> >
> >
> > 2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 -
> > 1.1.fc19
> > with nodes beig in glusterfs cluster also.....
> >
> >
> >
> > Right now, I'm banging my head against "Operation Add-Disk failed to
> > complete." , message I have got after adding a new virtual machine and
> > try
> > to addd its disk
> >
> >
> >
> >
> >
> > On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com) <
> > willarddennis(a)live.com > wrote:
> >
> > Hi all, ready for a story? (well, more of a rant, but hopefully it will
> > be a
> > good UX tale, and may even be entertaining.)
> >
> > Had one of the groups come to me at work this week and request a
> > OpenStack
> > setup. When I sat down and discussed their needs, it turns out that they
> > really only need a multi-hypervisor setup where they can spin up VMs for
> > their research projects. The VMs should be fairly long-lived, and will
> > have
> > persistent storage. Their other request is that the storage should be
> > local
> > on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB
> > drives
> > for VM storage on each node.) They desire this in order to keep the VM
> > I/O
> > local - they do not have a SAN of any sort anyhow, and they do not care
> > about live migration, etc
> >
> >
> > @Will
> > If the installation ends, either with or without error, it will give you
> > a
> > log location. Upload the log to a paste.bin and mail the link.
> >
> > @Gabi,
> > There should be more info in either the vdsm.log on the SPM server or in
> > the
> > engine.log on the engine server, see above for lettings us know what the
> > error is.
> >
> > Having installed oVirt, probably dozens of times, I have some guidelines:
> > - temporarily disable firewalld/iptables (if all works, enable should
> > still
> > work, scripts with rules are generated and location is given)
> > - make selinux permissive either via setenforce 0 (until next boot) or
> > via
> > /etc/selinux/config ( survives reboots), dont disable it!
> > - make sure fqdn work in both directions between engine and host(s)
> > (either
> > using /etc/hosts or DNS)
> > - make sure NetworkManager is disabled and network enabled
> >
> > Joop
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
7:31 p.m.
--_ce532de1-a9be-43e1-8384-883c91095919_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuup! :)
=20
Thanks for your assistance=2C Einav!
=20
Now onwards....
=20
Date: Fri=2C 17 Jan 2014 12:18:30 -0500
From: ecohen(a)redhat.com
To: willarddennis(a)live.com
CC: noc(a)nieuwland.nl=3B users(a)ovirt.org
Subject: Re: [Users] New user to oVirt=2C and I haz a sad so far...
=20
go to the "Network Interface" sub-tab of that node and click the
"Setup=20
Host Networks" button.=20
In the dialog that has opened=2C attach the 'ovirtmgmt' network from the=
=20
right-hand side of the dialog to one of your node's NICs on the
left-hand=
=20
side by dragging that network onto the NIC.
click OK.
after a short while=2C your Host should become 'Up'.
=
--_ce532de1-a9be-43e1-8384-883c91095919_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div
dir=3D'ltr'>Uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu=
uuuuuuup! =3B :)<BR> =3B<BR>Thanks for your assistance=2C
Einav!<BR=
 =3B<BR>Now
onwards....<br> =3B<BR><div>>=3B Date: Fri=2C 17 Jan=
2014 12:18:30 -0500<br>>=3B From: ecohen(a)redhat.com<br>&gt=3B
To: willar=
ddennis(a)live.com<br>&gt=3B CC: noc(a)nieuwland.nl=3B
users(a)ovirt.org<br>&gt=
=3B Subject: Re: [Users] New user to oVirt=2C and I haz a sad so far...<br>=
>=3B <br>>=3B go to the "Network Interface" sub-tab of that
node and cl=
ick the "Setup <br>>=3B Host Networks" button. <br>>=3B
In the dialog t=
hat has opened=2C attach the 'ovirtmgmt' network from the <br>>=3B
right-=
hand side of the dialog to one of your node's NICs on the left-hand
<br>>=
=3B side by dragging that network onto the NIC.<br>>=3B click
OK.<br>>=
=3B after a short while=2C your Host should become 'Up'.<br></div>
=
</div></body>
</html>=
--_ce532de1-a9be-43e1-8384-883c91095919_--
10:34 p.m.
On 01/17/2014 07:31 PM, Willard Dennis wrote:
Uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuup! :)
Thanks for your assistance, Einav!
Now onwards....
Hi Will,
this should work out of the box.
would help if you can open a bug on this not happening so it will be
verified it does work out of the box.
Thanks,
Itamar
> Date: Fri, 17 Jan 2014 12:18:30 -0500
> From: ecohen(a)redhat.com
> To: willarddennis(a)live.com
> CC: noc(a)nieuwland.nl; users(a)ovirt.org
> Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
>
> go to the "Network Interface" sub-tab of that node and click the
"Setup
> Host Networks" button.
> In the dialog that has opened, attach the 'ovirtmgmt' network from the
> right-hand side of the dialog to one of your node's NICs on the
left-hand
> side by dragging that network onto the NIC.
> click OK.
> after a short while, your Host should become 'Up'.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1 a.m.
OK, I will open a bug; trying now to bring up the node using CentOS 6.5
minimal, will keep good notes this time on what I have to do to get it
connected to the engine.
Thanks,
Will
-----Original Message-----
From: Itamar Heim [mailto:iheim@redhat.com]
Sent: Friday, January 17, 2014 3:34 PM
To: Willard Dennis; Einav Cohen
Cc: users(a)ovirt.org
Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
On 01/17/2014 07:31 PM, Willard Dennis wrote:
Uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuup! :)
Thanks for your assistance, Einav!
Now onwards....
Hi Will,
this should work out of the box.
would help if you can open a bug on this not happening so it will be
verified it does work out of the box.
Thanks,
Itamar
> Date: Fri, 17 Jan 2014 12:18:30 -0500 > From: ecohen(a)redhat.com >
To: willarddennis(a)live.com > CC: noc(a)nieuwland.nl; users(a)ovirt.org >
Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
>
> go to the "Network Interface" sub-tab of that node and click the
"Setup > Host Networks" button.
> In the dialog that has opened, attach the 'ovirtmgmt' network from
the > right-hand side of the dialog to one of your node's NICs on the
left-hand > side by dragging that network onto the NIC.
> click OK.
> after a short while, your Host should become 'Up'.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:05 p.m.
Gabi, why not share with us engine.log for your failure of adding the disk?
Yair
----- Original Message -----
From: "Gabi C" <gabicr(a)gmail.com>
To: "Will Dennis (Live.com)" <willarddennis(a)live.com>
Cc: users(a)ovirt.org
Sent: Friday, January 17, 2014 9:53:55 AM
Subject: Re: [Users] New user to oVirt, and I haz a sad so far...
've been there! :-D
I mean exactly same issuse you had on Centos, I had on Fedora 19.
Did you disable selinux on nodes? 'cause that's what is causing SSh
connection closing
My setup:
1 engine on vmware - fedora 19, up-to-date
2 nodes on IBM x series 3650 - fedora 19 based -oVirt Node - 3.0.3 -
1.1.fc19 with nodes beig in glusterfs cluster also.....
Right now, I'm banging my head against "Operation Add-Disk failed to
complete." , message I have got after adding a new virtual machine and try
to addd its disk
On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis (Live.com) <
willarddennis(a)live.com> wrote:
> Hi all, ready for a story? (well, more of a rant, but hopefully it will be
> a
> good UX tale, and may even be entertaining.)
>
> Had one of the groups come to me at work this week and request a OpenStack
> setup. When I sat down and discussed their needs, it turns out that they
> really only need a multi-hypervisor setup where they can spin up VMs for
> their research projects. The VMs should be fairly long-lived, and will have
> persistent storage. Their other request is that the storage should be local
> on the hypervisor nodes (they plan to use Intel servers with 8-10 2TB
> drives
> for VM storage on each node.) They desire this in order to keep the VM I/O
> local - they do not have a SAN of any sort anyhow, and they do not care
> about live migration, etc.
>
> In any case, knowing that they did not want to afford a VMware setup (which
> is what I'm used to using), I proposed using oVirt to fill their needs,
> having heard and read up on it a bit (It's "open-source VMware",
right?)
> even though I had not used it before (I have however made single-node KVM
> hypervisors for their group before, utilizing Open vSwitch, libvirt,
> virt-manager etc., so I'm not completely ignorant of KVM/libvirt etc.)
>
> In any case, I took one of their older servers which was already running
> CentOS 6.5, installed the requisite packages on it, and in short order had
> an engine server up and running (oVirt 3.3.2). That seems to have been the
> easy part :-/ Now came the installation of a hypervisor node. I downloaded
> and burned an ISO of the latest oVirt node installer
> (ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso) and tried to install it on one of
> their target Intel servers. On the 1st try I got to the end of the setup
> TUI, invoked the Install link, and was promptly thrown an error (sorry, but
> forgot what it was, something like "press X for a command prompt, or
> Reboot".) No problem, I rebooted, selected booting off the CD again, waited
> until the TUI came up, and when I tried to move past the first screen, it
> threw me out to a login prompt. OK, enough of that (the server takes a long
> time to reboot, and then boot off the CD) - I then thought I would try it
> on
> a VMware Workstation VM (yes, I get the irony, but VMware wkstn can handle
> nested virt, so it's a great testbed platform for OpenStack, etc.) because
> that would install a heck of a lot faster. That went a lot better - got the
> oVirt node 3.0.3 installed on the first try.
>
> More pain was soon to follow, however. I logged in and started configuring
> the node. The TUI was easy enough - much like an ESXi node ;) I set the
> NIC
> to IPv4 static, entered in the correct IP info, registered a DNS name for
> the IP I had assigned, and then tested pinging the engine, all was good. I
> then moved on to the section where you define the engine. I entered in the
> FQDN of the engine, verified the key fingerprint, and clicked the "Save and
> Register" link at the bottom. That seemed to work, so I completed the rest
> of the TUI, and then looked at the oVirt engine web UI. There was my new
> node, ready for authorization. I clicked the link to authorize it, and
> after
> a while, the UI came back with "Install Failed" status. Hmmm. So I went
> back
> to the node's TUI, and now some of the screens said that the IP addr was
> unconfigured? I went then to the Network screen, and sure enough, the NIC
> at
> the bottom showed "Unconfigured". WTF? So I went and entered in the
correct
> info back in the IPv4 section, and then arrowed down to the Save link and
> clicked it - and the next screen said something like "No info needing
> changes, nothing to do." Whaaaa? Went back to the network setup screen, NIC
> still showing "Unconfigured" even though the IPv4 info still was there. I
> did a ping test at this point from the Ping link on the network setup page,
> and what do you know - I could still ping IP's (the engine, the default gw,
> etc.) But as I moved around the TUI, other screens still said that the
> network was unconfigured. Went back to the Web UI of the engine, put the
> host in Maint, then tried to Activate it, still no go - Install Failed.
> Even
> though I had configured the node to allow remote access and set a password,
> and also verified via nmap that TCP port 22 on the node was indeed
> listening, when I tried to SSH into the node as admin, I immediately got a
> "connection closed" message, so that failed as well. Went back to the
> node's
> network setup page, set the IPv4 to "Disabled", saved it, then went back
> and
> set it back to "Static" then re-entered the IPv4 info. Clicked the Save
> link, it went thru the setup again, came back with a success, verified with
> ping etc. that networking was working on the node. The engine web UI still
> said that it could not connect to the node however. So I put the node in
> Maint, and then removed it. I went back to the node, went to the Engine
> setup page, and re-did the screen to define the engine on the node. I
> notice
> that after I did this, however, that the node screens went back to saying
> that the network was unconfigured. Grrrrrr. But the node was back in the
> engine's Web UI, however no joy this time either - "Install failed"
again.
> Well, the hell with this, said I - I removed the node again from the
> engine,
> and went and installed Fedora 19 minimal install on the VM, so I could use
> the directions found in
> http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_Host and give that a
> try. (At least I can see what's going on with the node's OS using F19.)
>
> Installing F19 on the VM was a breeze, then logged in as root and did the
> "yum localinstall
> http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm"
> which ran fine. I then stopped firewalld, and set it not to run at boot
> (which is what we typically do anyhow for internal research servers.) Then
> went over to the engine UI, and manually added the node. Oh happy day - the
> node seemed to install OK - it had the status of "Installing" for quite
> some
> time, and I looked at the processes on the F19 node, and could see python
> installer programs running via an SSH session from the engine. HOWEVER, at
> the end of the process, the Web UI reported a status of "Non Responsive",
> even though the F19 node looks OK (it had sanlock, supervdsmServer, vdsm
> processes running.) So thinking that it may take an after-install reboot, I
> did that, waited until the node came back up again, then clicked in the
> engine web UI and executed the "Confirm 'Host has been rebooted'"
command,
> but still no good - the node remains in "Non Responsive" status.
>
> So I have no idea on how to proceed now, and what methods I can use to try
> and debug the connectivity problem between the engine and node. And there's
> many miles to go in setting up the whole environment. Maaaaaybe OpenStack
> would be easier ;-P No, I will press on and try to get this thing
> working... It seems it works for others, and looks like the right fit for
> the job. Just wish it was easier to get up and running.
>
> Oh yes, I tried reading the docs - go to
> http://www.ovirt.org/Quick_Start_Guide#Install_Hosts and click on the link
> for "see the oVirt Node deployment documentation." Not too helpful...
(Bug
> report has been opened.)
>
> Thanks for reading, and any clues on getting a node up and running
> gratefully accepted...
>
> - Will
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:23 p.m.
--=-nM/9pK8xKxi01vke2fbo
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hey Will,
that was surely a bad start and we know about the state of Node.
Please take a look at this email
http://lists.ovirt.org/pipermail/node-devel/2014-January/000581.html
to see where you can find a draft image which should address some bugs.
- fabian
Am Donnerstag, den 16.01.2014, 23:08 -0500 schrieb Will Dennis
(Live.com):
In any case, I took one of their older servers which was already
running
CentOS 6.5, installed the requisite packages on it, and in short order
had
an engine server up and running (oVirt 3.3.2). That seems to have been
the
easy part :-/ Now came the installation of a hypervisor node. I
downloaded
and burned an ISO of the latest oVirt node installer
(ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso) and tried to install it on
one of
their target Intel servers. On the 1st try I got to the end of the
setup
TUI, invoked the Install link, and was promptly thrown an error
(sorry, but
forgot what it was, something like "press X for a command prompt, or
Reboot".) No problem, I rebooted, selected booting off the CD again,
waited
until the TUI came up, and when I tried to move past the first screen,
it
threw me out to a login prompt. OK, enough of that (the server takes a
long
time to reboot, and then boot off the CD) - I then thought I would try
it on
a VMware Workstation VM (yes, I get the irony, but VMware wkstn can
handle
nested virt, so it's a great testbed platform for OpenStack, etc.)
because
that would install a heck of a lot faster. That went a lot better -
got the
oVirt node 3.0.3 installed on the first try.
=20
More pain was soon to follow, however. I logged in and started
configuring
the node. The TUI was easy enough - much like an ESXi node ;) I set
the NIC
to IPv4 static, entered in the correct IP info, registered a DNS name
for
the IP I had assigned, and then tested pinging the engine, all was
good. I
then moved on to the section where you define the engine. I entered in
the
FQDN of the engine, verified the key fingerprint, and clicked the
"Save and
Register" link at the bottom. That seemed to work, so I completed the
rest
of the TUI, and then looked at the oVirt engine web UI. There was my
new
node, ready for authorization. I clicked the link to authorize it, and
after
a while, the UI came back with "Install Failed" status. Hmmm. So I
went back
to the node's TUI, and now some of the screens said that the IP addr
was
unconfigured? I went then to the Network screen, and sure enough, the
NIC at
the bottom showed "Unconfigured". WTF? So I went and entered in the
correct
info back in the IPv4 section, and then arrowed down to the Save link
and
clicked it - and the next screen said something like "No info needing
changes, nothing to do." Whaaaa? Went back to the network setup
screen, NIC
still showing "Unconfigured" even though the IPv4 info still was
there. I
did a ping test at this point from the Ping link on the network setup
page,
and what do you know - I could still ping IP's (the engine, the
default gw,
etc.) But as I moved around the TUI, other screens still said that the
network was unconfigured. Went back to the Web UI of the engine, put
the
host in Maint, then tried to Activate it, still no go - Install
Failed. Even
though I had configured the node to allow remote access and set a
password,
and also verified via nmap that TCP port 22 on the node was indeed
listening, when I tried to SSH into the node as admin, I immediately
got a
"connection closed" message, so that failed as well. Went back to the
node's
network setup page, set the IPv4 to "Disabled", saved it, then went
back and
set it back to "Static" then re-entered the IPv4 info. Clicked the
Save
link, it went thru the setup again, came back with a success, verified
with
ping etc. that networking was working on the node. The engine web UI
still
said that it could not connect to the node however. So I put the node
in
Maint, and then removed it. I went back to the node, went to the
Engine
setup page, and re-did the screen to define the engine on the node. I
notice
that after I did this, however, that the node screens went back to
saying
that the network was unconfigured. Grrrrrr. But the node was back in
the
engine's Web UI, however no joy this time either - "Install failed"
again.
Well, the hell with this, said I - I removed the node again from the
engine,
and went and installed Fedora 19 minimal install on the VM, so I could
use
the directions found in
http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_Host and give
that a
try. (At least I can see what's going on with the node's OS using
F19.)
--=-nM/9pK8xKxi01vke2fbo
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAABAgAGBQJS2RLOAAoJEC9+uOgSHVGUZsIP/Awunqq7Dyyra6n3hohyGL/W
uuAUYPPySGnbUfCJK/vtnlSPq6ypym+s33kkdJK0WSWWFO91n09uh2QfsoMFIJEM
yfLJqX5Rm/4Pq9EKqrDpRK+Zd+C1rf8ROXXUG1OcwlqGidDildVx4OGqXU1mK2oK
RRByE9gkPMdoZo+JvnHunEvQBQuRLRaXTk+b1aUEZnxKKfHUF+kVfQNdt88so/1K
d5jjXW803B219JDwytMmbV2+FuanJQF14gzud/LdDMUZFK/PUutyESaNN65AVg/d
/gbA9vu6vSWrSp7Naxz/Es4Ve8SLTP7C02m4fi6CvwXu4ssz473yHw03zFNIkiHu
Ks8WJPwJ7wux6+taF/Yp4MeDEOAG9CpFM+ftlvnZK+JzKerke6XrWva2md9LWJJT
XzZjQ7T0MMdUXYP9RTZc/m4iyn4H9XcmnTEu4MoA5CF1SjeFf39h8k1pmWq69wKL
2hMJNx+S4J3Fn3rUIsfV/An4U06onF0pbC/ju+OCsnLBIPSXyiniRqmQLOnejYmD
bZ+dqiH0XcST7YucOjCn+9hZJXV7ZoIuAJ82gL0pcYndrvJlxYJWYxM6lN45wp9q
Z8tFqhpljBpIofDBIRoqZiwbSLBbYVHolkjVf2dhr0VpPFVPLDUTVNef7MNITTwO
Fm05EWeMZn20k9DHveCH
=nvrR
-----END PGP SIGNATURE-----
--=-nM/9pK8xKxi01vke2fbo--
4:12 p.m.
Hi Will,
Great to see you on the users list! (well, not great to see the content,
but you know what I mean...)
On 01/17/2014 05:08 AM, Will Dennis (Live.com) wrote:
So I have no idea on how to proceed now, and what methods I can use
to try
and debug the connectivity problem between the engine and node. And there's
many miles to go in setting up the whole environment. Maaaaaybe OpenStack
would be easier ;-P No, I will press on and try to get this thing
working... It seems it works for others, and looks like the right fit for
the job. Just wish it was easier to get up and running.
Oh yes, I tried reading the docs - go to
http://www.ovirt.org/Quick_Start_Guide#Install_Hosts and click on the link
for "see the oVirt Node deployment documentation." Not too helpful... (Bug
report has been opened.)
Thanks for reading, and any clues on getting a node up and running
gratefully accepted...
I have had success setting up CentOS 6.5 minimal in nodes, configuring
network, and then adding the node through the management interface - the
Engine takes care of installing & configuring the nodes.
Have you tried this?
Incidentally, you can also have Node images deployed via PXE boot (this
seems orthogonal to your issue, though): http://www.ovirt.org/Node_PXE
Cheers,
Dave.
--
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
7:19 p.m.
--_41ddde3f-37ef-4727-8e84-ce6b7a26af98_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
=20
Date: Fri=2C 17 Jan 2014 15:12:20 +0100
From: dneary(a)redhat.com
To: willarddennis(a)live.com=3B users(a)ovirt.org
Subject: Re: [Users] New user to oVirt=2C and I haz a sad so far...
=20
Hi Will=2C
=20
Great to see you on the users list! (well=2C not great to see the content=
=2C
but you know what I mean...) Thanks for your help to date!
=20
On 01/17/2014 05:08 AM=2C Will Dennis (Live.com) wrote:
> Thanks for reading=2C and any clues on getting a node up and running
> gratefully accepted...
=20
I have had success setting up CentOS 6.5 minimal in nodes=2C configuring
network=2C and then adding the node through the management interface - th=
e
Engine takes care of installing & configuring the nodes.
=20
Have you tried this? No=2C I was told by someone else (in IRC I believe) =
that
only Fedora could be used as a node... I would much rather use EL6.5 (=
CentOS)... What/where is the proper RPM for this platform?
Cheers=2C
Dave.
Thanks again=2CWill
=
--_41ddde3f-37ef-4727-8e84-ce6b7a26af98_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div
dir=3D'ltr'> =3B<BR><div>>=3B Date: Fr=
i=2C 17 Jan 2014 15:12:20 +0100<br>>=3B From:
dneary(a)redhat.com<br>&gt=3B=
To: willarddennis(a)live.com=3B users(a)ovirt.org<br>&gt=3B Subject: Re: [User=
s] New user to oVirt=2C and I haz a sad so far...<br>>=3B <br>>=3B
Hi W=
ill=2C<br>>=3B <br>>=3B Great to see you on the users list!
(well=2C no=
t great to see the content=2C<br>>=3B but you know what I
mean...)</div><=
div> =3B</div><div>Thanks for your help to
date!</div><div><br>>=3B <=
br>>=3B On 01/17/2014 05:08 AM=2C Will Dennis (Live.com)
wrote:<br>>=3B=
>=3B Thanks for reading=2C and any clues on getting a node up and runnin=
g<br>>=3B >=3B gratefully accepted...<br>>=3B
<br>>=3B I have had s=
uccess setting up CentOS 6.5 minimal in nodes=2C configuring<br>>=3B netw=
ork=2C and then adding the node through the management interface - the<br>&=
gt=3B Engine takes care of installing &=3B configuring the
nodes.<br>>=
=3B <br>>=3B Have you tried
this?</div><div> =3B</div><div>No=2C I wa=
s told by someone else (in IRC I believe) that only Fedora could be used as=
a node... I would much rather use EL6.5 (CentOS)... What/where is the prop=
er RPM for this platform?</div><div><br>>=3B
Cheers=2C<br>>=3B Dave.<br=
</div><div>Thanks
again=2C</div><div>Will<br></div> </div></bod=
y>
</html>=
--_41ddde3f-37ef-4727-8e84-ce6b7a26af98_--
8:07 p.m.
Hi,
On 01/17/2014 06:19 PM, Willard Dennis wrote:
> I have had success setting up CentOS 6.5 minimal in nodes,
configuring
> network, and then adding the node through the management interface - the
> Engine takes care of installing & configuring the nodes.
>
> Have you tried this?
No, I was told by someone else (in IRC I believe) that only Fedora could
be used as a node... I would much rather use EL6.5 (CentOS)...
What/where is the proper RPM for this platform?
That was true until during the oVirt 3.2 release cycle, but we have had
an EL6 Node for a while.
oVirt Node is a stripped down OS image - installing the Node packages on
a minimal EL6 install has also worked since the 3.2 series.
Cheers,
Dave.
--
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
10:37 p.m.
On 01/17/2014 08:07 PM, Dave Neary wrote:
Hi,
On 01/17/2014 06:19 PM, Willard Dennis wrote:
>> I have had success setting up CentOS 6.5 minimal in nodes, configuring
>> network, and then adding the node through the management interface - the
>> Engine takes care of installing & configuring the nodes.
>>
>> Have you tried this?
>
> No, I was told by someone else (in IRC I believe) that only Fedora could
> be used as a node... I would much rather use EL6.5 (CentOS)...
> What/where is the proper RPM for this platform?
That was true until during the oVirt 3.2 release cycle, but we have had
an EL6 Node for a while.
oVirt Node is a stripped down OS image - installing the Node packages on
a minimal EL6 install has also worked since the 3.2 series.
just to clarify - there are two types of hosts:
- ovirt-node - stripped down, ESXi like. some workflows of deploying
and updating it are simpler as its image based
- normal linux - just configure the yum repos, and ovirt-engine should
configure everything else.
both types have fedora and .el6 support, and an ubuntu for 'normal
linux' type is making progress as well.
(and yes, it seems the ovirt-node one for 3.3 required a much needed set
of fixes)
Thanks,
Itamar
3963
days inactive
3963
days old
20 comments
11 participants
participants (11)
-
Dan Yasny -
Dave Neary -
Einav Cohen -
Fabian Deutsch -
Gabi C -
Itamar Heim -
noc -
Sven Kieske -
Will Dennis (Live.com) -
Willard Dennis
-
Yair Zaslavsky