Thank you, Yedidyah for fast reply.
As a minimum, install 'ovirt-hosted-engine-setup' and
run 'hosted-engine --deploy'.
*These are my repositories from your docs.*
*[root@master02 ~]# ls -ls /etc/yumyum/ yum.conf
yum.repos.d/ [root@master02 ~]# ls -ls
Il 13/11/2013 09:29, Pavel Gandalipov ha scritto:
Thank you, Yedidyah for fast reply.
As a minimum, install 'ovirt-hosted-engine-setup' and
run 'hosted-engine --deploy'.
*These are my repositories from your docs.*
/[root@master02 ~]# ls -ls /etc/yum
yum/ yum.conf
yum --enablerepo=ovirt-nightly
On Wed, Nov 13, 2013 at 9:29 AM, Pavel Gandalipov pgandali...@gmail.com wrote:
Thank you, Yedidyah for fast reply.
As a minimum, install 'ovirt-hosted-engine-setup' and
run 'hosted-engine --deploy'.
These are my repositories from your docs.
[root@master02
Hi,
afaik the rhel 5 kernel series just has not the necessary drivers for
all virtio stuff, so it's not supported and does not work, unless
you want to patch your own kernel.
Am 13.11.2013 06:44, schrieb Paul Jansen:
I have just set up an Ovirt 3.3.0 install and have done a test install of
Hi,
- Original Message -
From: Pavel Gandalipov pgandali...@gmail.com
To: Yedidyah Bar David d...@redhat.com
Cc: users@ovirt.org
Sent: Wednesday, November 13, 2013 10:29:32 AM
Subject: Re: [Users] Installation of self hosted engine
Thank you, Yedidyah for fast reply.
As a
According to https://access.redhat.com/site/solutions/20511 virtio
work on rhel5.3.
You have to edit /etc/modprobe.conf and generate a new initrd.
On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske s.kie...@mittwald.de wrote:
Hi,
afaik the rhel 5 kernel series just has not the necessary drivers
Hi,
can someone elaborate on this fix?
Is something broken with the ballooning-rules in the current
vdsm? If yes, what is it, and can it be circumvented until
a new vdsm stable release hits the ovirt.org repo?
Thanks in advance!
Am 12.11.2013 21:51, schrieb Douglas Schilling Landgraf:
-
On Wed, 2013-11-13 at 09:41 +0100, Sander Grendelman wrote:
According to https://access.redhat.com/site/solutions/20511 virtio
work on rhel5.3.
You have to edit /etc/modprobe.conf and generate a new initrd.
If you're installing the OS on a VirtIO disk this is done automatically
by
Hi Rene.
I specifically need the scsi support (virtio-scsi).
I do know about the virtio-block support, which results in /dev/vd* devices as
you say.
From what I read even EL6 earlier than 6.3 does not support virtio-scsi
Alternatively, does oVirt support an emulated scsi adapter of a different
Thank you all, Yedidya, Sandro,Sander. Your advices helped me to go farther
in my project.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
I specifically need the scsi support (virtio-scsi).
I do know about the virtio-block support, which results in /dev/vd*
devices as you say.
From what I read even EL6 earlier than 6.3 does not support
virtio-scsi
Sorry, I did read your email to fast as it seems.
You're right you need at
On Wed, Nov 13, 2013 at 9:58 AM, Paul Jansen wrote:
Hi Rene.
I specifically need the scsi support (virtio-scsi).
I do know about the virtio-block support, which results in /dev/vd* devices
as you say.
From what I read even EL6 earlier than 6.3 does not support virtio-scsi
Alternatively,
Hi Uche,
Thanks for the tip, looks a lot like proxmox and I can use it for some tasks
probably.
I read through the information and the reason OpenNode can run on Amazon is
because they use the OpenVZ support. Amazon has enabled OpenVZ a couple of
months ago.
As oVirt doesn't support OpenVZ
This time it failed earlier. Looks like the PCA webservice2 was not
listening on 8443 port. Have you replaced the port 8443 with 8442 in server
side ($TOMCAT_HOME/conf/server.xml) but not change it in client side
(/usr/share/oat-client/script/OAT_client.sh)? Or the 8443 port is occupied
by another
Hi,
There are 2 features I can maybe add to existing projects of mine
(check_rhev3 and Monitoring UI-Plugin), but it would be good to know
what users require to decide if this can be done via an external
(ui)plugin or if this needs to be integrated into oVirt itself.
* gluster: Monitoring (UI
Il 08/11/2013 10:47, Sandro Bonazzola ha scritto:
Hi,
Looking at bugzilla, there are 366 bugs without a target release.
Some of them are in POST state but I'm pretty sure they should be in ON_QA or
CLOSED state.
A lot of them haven't a whiteboard set.
Please review the bug list and help
Hi,
I am using port 8443, since no other process -- as far as I know -- is
using it;
below you will find all of the requested configuration files:
Contents of /etc/oat_client/*:
log4j.properties: http://pastebin.com/MQLM68vs
OAT.properties: http://pastebin.com/LwHihxah
* other: Zabbix monitoring
Monitoring the oVirt environment should work with my check_rhev3 plugin
by adding it as an external check to Zabbix. I'll test this and if it's
working I'll provide a short guide on how to do it.
Displaying data/triggers in oVirt isn't possible yet with my
On 11/13/2013 09:27 AM, René Koch (ovido) wrote:
Hi,
There are 2 features I can maybe add to existing projects of mine
(check_rhev3 and Monitoring UI-Plugin), but it would be good to know
what users require to decide if this can be done via an external
(ui)plugin or if this needs to be
On Wed, 2013-11-13 at 15:46 +0100, Sander Grendelman wrote:
* other: Zabbix monitoring
Monitoring the oVirt environment should work with my check_rhev3 plugin
by adding it as an external check to Zabbix. I'll test this and if it's
working I'll provide a short guide on how to do it.
On 11/13/2013 08:20 PM, Itamar Heim wrote:
On 11/13/2013 09:27 AM, René Koch (ovido) wrote:
Hi,
There are 2 features I can maybe add to existing projects of mine
(check_rhev3 and Monitoring UI-Plugin), but it would be good to know
what users require to decide if this can be done via an
On 11/13/2013 10:20 AM, Sahina Bose wrote:
On 11/13/2013 08:20 PM, Itamar Heim wrote:
On 11/13/2013 09:27 AM, René Koch (ovido) wrote:
Hi,
There are 2 features I can maybe add to existing projects of mine
(check_rhev3 and Monitoring UI-Plugin), but it would be good to know
what users require
On 11/13/2013 08:53 PM, Itamar Heim wrote:
On 11/13/2013 10:20 AM, Sahina Bose wrote:
On 11/13/2013 08:20 PM, Itamar Heim wrote:
On 11/13/2013 09:27 AM, René Koch (ovido) wrote:
Hi,
There are 2 features I can maybe add to existing projects of mine
(check_rhev3 and Monitoring UI-Plugin),
Hi René,
On 11/13/2013 04:16 PM, René Koch (ovido) wrote:
[snip]
The plugin is a Nagios monitoring plugin, but as mentioned above you
should be able to use it with Zabbix when defining it as an external
check.
Download and documentation can be found here:
https://github.com/ovido/check_rhev3
I am running oVirt Engine Version:
3.4.0-0.2.master.20131107144332.git214186b.fc18. I am having an issue
adding new hosts. I do a fresh install of fc18 on the host and then try
to add it into my cluster. The controller installs all packages and it
looks like it's all good, but at the end I
Patrick Lists schreef op 13-11-2013 16:37:
Hi René,
On 11/13/2013 04:16 PM, René Koch (ovido) wrote:
[snip]
The plugin is a Nagios monitoring plugin, but as mentioned above you
should be able to use it with Zabbix when defining it as an external
check.
Download and documentation can be
On 11/13/2013 05:16 PM, Martijn Grendelman wrote:
Patrick Lists schreef op 13-11-2013 16:37:
Hi René,
On 11/13/2013 04:16 PM, René Koch (ovido) wrote:
[snip]
The plugin is a Nagios monitoring plugin, but as mentioned above you
should be able to use it with Zabbix when defining it as an
Please attach vdsm.log and supervdsm.log after you get the Failed to configure
management network on the host error.
- Original Message -
From: Rob Abshear rabsh...@citytwist.net
To: users@ovirt.org
Sent: Wednesday, November 13, 2013 6:12:57 PM
Subject: [Users] Failed to configure
On Wed, 2013-11-13 at 17:16 +0100, Martijn Grendelman wrote:
Patrick Lists schreef op 13-11-2013 16:37:
Hi René,
On 11/13/2013 04:16 PM, René Koch (ovido) wrote:
[snip]
The plugin is a Nagios monitoring plugin, but as mentioned above you
should be able to use it with Zabbix when
And you need to copy files from server to client before you try to run
provisioner.sh every time you run OAT_configure.sh again.
Jimmy
-Original Message-
From: Wei, Gang
Sent: Thursday, November 14, 2013 11:26 AM
To: Nicolae Paladi
Cc: Doron Fediuck; users@ovirt.org; Wei, Gang
Hi Itamar,
Thanks for the update.
Is the POC for Cinder driver is ready? Are there any resources pointing towards
this?
Regards,
Udaya Kiran
On Thursday, 14 November 2013 1:19 AM, Itamar Heim ih...@redhat.com wrote:
On 11/12/2013 01:38 AM, Udaya Kiran P wrote:
Hi everyone,
Does
- Original Message -
Please attach vdsm.log and supervdsm.log after you get the Failed to
configure management network on the host error.
Also a relevant segment from the engine.log file from the failure might be
helpful.
- Original Message -
From: Rob Abshear
Hi Paul,
First of all, thanks for the detailed answer, it really helps.
See comments inline.
- Original Message -
Hello Itamar.
The specific use case is a particular propriety filesystem that needs to see
a scsi device. It will do scsi inquiry conmmands to verify suitability.
In
Adding Stefan with the correct email this time.
- Original Message -
Hi Paul,
First of all, thanks for the detailed answer, it really helps.
See comments inline.
- Original Message -
Hello Itamar.
The specific use case is a particular propriety filesystem that needs to
On 11/14/2013 12:10 AM, Udaya Kiran P wrote:
Hi Itamar,
Thanks for the update.
Is the POC for Cinder driver is ready? Are there any resources pointing
towards this?
still need to get to it, but we'd welcome help...
Regards,
Udaya Kiran
On Thursday, 14 November 2013 1:19 AM, Itamar Heim
Hi,
yes it is, but that's not that simple at all, looking at our use case:
We want to automate this as much as possible via REST-API and scripts,
so we would need to e.g. put an ascending number in the path to avoid
this bug, but on the other hand this makes debugging via scripts
difficult as
36 matches
Mail list logo
