Re: [Users] Agents for Windows

[Vinzenz Feenstra]

On 12/06/2013 09:14 PM, Bob Doolittle wrote:


On 12/06/2013 06:25 AM, Vinzenz Feenstra wrote:

On 12/06/2013 05:33 AM, Blaster wrote:

I guess I'm confused as to how Red Hat can be making statements that 
Ovirt is a viable alternative to ESXi when many simple things that 
ESXi users take for granted simply don't work or are non-existent 
under Ovirt.  I'm hardly a power user of ESXi, and I've only begun 
my Ovirt journey, but I've already come across the following:

...
I understand that you're disappointed and we're trying to make our 
best to make the user experience better. You should be considering 
the age of the project and what we're actually already providing. Yes 
not everything is perfect, but we're working hard on improving it.


True but you'll note that Blaster's overall comments were about Red 
Hat's marketing of this project as a solution, given it's status. I 
agree that it's a bit premature. oVirt is maturing quickly, but it 
still has a ways to go. It will get there, as you point out, and of 
course driving demand by a little over-enthusiastic marketing may 
actually accelerate that process, which may be a goal (Machiavelli 
would approve :). It will also frustrate some users, unfortunately.


Another thing having to say about your point 4 is that you're basing 
your experience solely on Windows guests, which are a bit more 
troublesome to support the same way we do for example Linux guests.


Here I disagree. My experience is the opposite. You can get almost 
everything (that I care about anyway) for Windows by installing 
spice-guest-tools (once you find it - there are few clues on the oVirt 
Wiki). This includes drivers, better mouse/display handling, and 
copy/paste. It does not seem however to include communication of the 
IP address (nor, I suspect, clean shutdown handling).
My point was about providing our own binaries for the oVirt guest agent. 
We have not yet solved targeting Windows for the guest agent binaries 
for oVirt. My bad that it wasn't explicit enough.


It's on Linux where you have to piece together more things, and in 
fact have to build some things (e.g. vdagent) from source.


Once https://bugzilla.redhat.com/show_bug.cgi?id=1026933 is fixed 
(currently slated for 3.3.3 :( ), and assuming that a VFD will be 
included and not just an ISO, the experience will be much simpler for 
Windows than for Linux for those pieces.


If we were to build vdagent for Linux and make the RPMs for it and the 
Linux Guest Agent available in an easy way (incorporate them into an 
ISO and pre-populate ISO_DOMAIN with it?) that would be a big step 
forward for Linux guests. It's possible that you'd have to build 
vdagent from source, using some kind of automated build/install script 
on the ISO, to make it work for a variety of Linux distros. That's 
effectively what VMware has done. When building from source I find 
resolving the dependencies to be a big headache, particularly on Fedora.
Well on fedora it would be as easy as yum install spice-vdagent, no 
headaches here from my point of view.
However requiring all the devel packages just to install the agent on 
the target platform from sources is a bit overkill in my opinion.
On linux we rather should go with the default packaging ways. That's 
what we're working on at the moment as well. We have already built 
packages for Fedora, distributions using EPEL (e.g. CentOS), OpenSUSE 
and Ubuntu. Upcoming targets are SLES and Debian.


So for those it would be doable without having to build from sources. 
However besides Fedora and EPEL we don't have yet reached inclusion into 
the repositories for those packages, for Ubuntu it's on launchpad and 
for OpenSuSE on their open build infrastructure.


As I said eventually we'll get there that we'll provide binaries for that.


-Bob




--
Regards,

Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R & D
Phone: +420 532 294 625
IRC: vfeenstr or evilissimo

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt Python SDK: getting the full filenames of disk images

[Исаев Виталий Анатольевич]

Hi Dan, glad to meet you both on LOR and in this mailing list :)


Unfortunately ovirtsdk.infrastructure.brokers. classes instances miss 
information about the higher objects very often. The typical situation is 
returning of empty string when we ask something about the parent from the child 
object ("child" and "parent" in terms Red Hat Enterprise Virtualization objects 
hierarchy). Consider this Python code:



from ovirtsdk.api import API

from ovirtsdk.xml import params

...

api = API(...)

d = api.vms.list()[i].get_disks().list()[i] 
# ovirtsdk.infrastructure.brokers.VMDisk class 
instance, i – any number in range(api.vms.list().__len__())

s = d.get_storage_domains().get_storage_domain()[0] 
 # ovirtsdk.infrastructure.params.StorageDomain class instance

t = s.get_data_center() 
 # NoneType



So you can see that this approach does not work here.


Our purpose is checking the VM’s disk image integrity (I mean integrity of 
system files, stored in /boot, /bin, /sbin, /lib etc.) every time the VM 
starts. The integrity checking script is written in Python and relies on 
libguestfs and vdsm hooks. Specific vdsm hook runs our script and block the 
VM’s boot process until the correctness of the system files hash sums will be 
checked. But libguestfs requires the full path to the disk to be handled, and 
it’s not integrated with ovirt infrastructure. And here we face with a task of 
full disk image filenames definition.

Thank you,
Vitaly Isaev
Software engineer
Information security department
Fintech JSC, Moscow, Russia

From: Dan Yasny [mailto:dya...@gmail.com]
Sent: Friday, December 06, 2013 8:56 PM
To: Исаев Виталий Анатольевич
Cc: users@ovirt.org
Subject: Re: [Users] oVirt Python SDK: getting the full filenames of disk images

Probably not, but you can
- get the disk image UUID (that's the name in the filesystem or LV name),
- get the UUID of the storage domain (that will be the top level dir name or VG 
name)
- get the DC UUID (this will be the top level dir name and the mount point for 
LVM)

Then compose the path out of these. Keep in mind that the disk UUID you get is 
the latest leaf in a snapshot tree, and if you need the entire chain of images, 
you need to recursively traverse the tree starting at the leaf, using the PUUID 
tag to find the parent.

Might be a better way, but I'm not aware of it.

Moreover, if you explain why you need to touch those images manually instead of 
letting ovirt handle everything, we might be able to suggest a better way

--
D

On Wed, Dec 4, 2013 at 2:34 AM, Исаев Виталий Анатольевич 
mailto:is...@fintech.ru>> wrote:
Dear ovirt-engine users,

I will be appreciated if someone experienced in oVirt Python SDK could advice 
the method of getting the full filename of the VM’s disk images in the RHEV 
hypervisor’s file system. Can I get filename with a full file system path from 
a ovirtsdk.infrastructure.brokers.VMDisk class instance?

If Python SDK (what is preffered) can’t provide such an information, may be it 
is still possible with RHEV-M REST API?

Thank you,
Vitaly Isaev
Software engineer
Information security department
Fintech JSC, Moscow, Russia


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] How to pxeboot ovrit node into memory automatically?

[Fabian Deutsch]

Am Donnerstag, den 05.12.2013, 16:30 -0800 schrieb David Li:
> Hi Fabian,
> 
> I think the bad route is a link local route 169.254.0.0/16. I am not quite 
> sure if it's a real bug but in my case I have to remove this route.
> Also I am using ramdisk based node without a local disk. Can anything be 
> persisted? 

Hey David,

when you refer to stateless mode, then no, nothing can be persisted.
Regarding the bug - Please provide the whole cmdline you are using to
boot the node, to give me a chance to reproduce it.

- fabian

> David
> 
> 
> 
> - Original Message -
> > From: Fabian Deutsch 
> > To: David Li 
> > Cc: "users@ovirt.org" 
> > Sent: Wednesday, December 4, 2013 11:17 AM
> > Subject: Re: [Users] How to pxeboot ovrit node into memory automatically?
> > 
> > Am Montag, den 02.12.2013, 13:53 -0800 schrieb David Li:
> >>  Hi Fabian,
> >> 
> >>  Everytime the ovirt node boots up, it adds a route entry that I have to 
> > manually remove. Otherwise it messed up my routing. 
> >>   How do I modify the boot scripts to automatically remove it?
> > 
> > Hey David,
> > 
> > could you file a bug for that route problem?
> > 
> > You can try the following workaround:
> > 
> > # Create /etc/rc.d/rc.local with the commands to run
> > $ vi /etc/rc.d/rc.local
> > $ chmod a+x /etc/rc.d/rc.local
> > $ persist /etc/rc.d/rc.local
> > 
> > /etc/rc.d/rc.local should then be run on every boot.
> > 
> > - fabian
> > 
> >>  - Original Message -
> >>  > From: Fabian Deutsch 
> >>  > To: David Li 
> >>  > Cc: "users@ovirt.org" 
> >>  > Sent: Monday, October 28, 2013 7:45 AM
> >>  > Subject: Re: [Users] How to pxeboot ovrit node into memory 
> > automatically?
> >>  > 
> >>  > Am Montag, den 28.10.2013, 07:42 -0700 schrieb David Li:
> >>  >> 
> >>  >>  Hi Fabian,
> >>  >> 
> >>  >>  Yes rootpwd worked too! Thanks.
> >>  >> 
> >>  >>  Two new problems:
> >>  >> 
> >>  >>  But I found there is no networking for the stateless node.
> >>  >>  What kernel boot options are used to either use DHCP  or 
> > statically 
> >>  > configure the IP address for an interface on the node?
> >>  >> 
> >>  >>  I also need to have the sshd enabled. Is there a kernel option 
> > for that?
> >>  > 
> >>  > Hey David,
> >>  > 
> >>  > here you can find all the supported boot params in ovirt node:
> >>  > 
> > http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=blob;f=scripts/ovirt-init-functions.sh.in;h=c4280caefb89c77afc1e8bec8c925aa7f3039733;hb=HEAD#l214
> >>  > 
> >>  > Greetings
> >>  > fabian
> >>  > 
> >>  >>  David
> >>  >> 
> >>  >> 
> >>  >> 
> >>  >>  - Original Message -
> >>  >>  > From: Fabian Deutsch 
> >>  >>  > To: David Li 
> >>  >>  > Cc: "users@ovirt.org" 
> >>  >>  > Sent: Friday, October 25, 2013 9:10 AM
> >>  >>  > Subject: Re: [Users] How to pxeboot ovrit node into memory 
> >>  > automatically?
> >>  >>  > 
> >>  >>  > Am Freitag, den 25.10.2013, 08:57 -0700 schrieb David Li:
> >>  >>  >>  Hi Fabian,
> >>  >>  >> 
> >>  >>  >>  That kernel option worked for me!  The node is booted 
> > up in RAM. 
> >>  > Thanks!
> >>  >>  >> 
> >>  >>  >>  My next question is:
> >>  >>  >> How do I specify the root login and passwd as boot 
> > parameters? 
> >>  >>  > 
> >>  >>  > Hey David.
> >>  >>  > 
> >>  >>  > Nice that it worked! Were you able to register to the 
> > Engine?
> >>  >>  > 
> >>  >>  > You can use the adminpw= and rootpw= kernel arguments to set 
> > 
> >>  > passwords.
> >>  >>  > use
> >>  >>  > $ openssl passwd -salt 42
> >>  >>  > to create one or two passwords
> >>  >>  > 
> >>  >>  > Greetings
> >>  >>  > fabian
> >>  >>  > 
> >>  >>  >>  David
> >>  >>  >> 
> >>  >>  >> 
> >>  >>  >> 
> >>  >>  >> 
> >>  >>  >>  - Original Message -
> >>  >>  >>  > From: Fabian Deutsch 
> >>  >>  >>  > To: David Li 
> >>  >>  >>  > Cc: "users@ovirt.org" 
> > 
> >>  >>  >>  > Sent: Thursday, October 24, 2013 11:47 PM
> >>  >>  >>  > Subject: Re: [Users] How to pxeboot ovrit node 
> > into memory 
> >>  >>  > automatically?
> >>  >>  >>  > 
> >>  >>  >>  > Am Donnerstag, den 24.10.2013, 16:26 -0700 schrieb 
> > David Li:
> >>  >>  >>  >>  Hi,
> >>  >>  >>  >> 
> >>  >>  >>  >>  I was following the instructions at 
> >>  >>  > http://www.ovirt.org/Node_PXE. My goal 
> >>  >>  >>  > is to use pxeboot (iPXE) to boot the node entirely 
> > into RAM 
> >>  > with 
> >>  >>  > rootfs. What I 
> >>  >>  >>  > got now is an installation screen which requires a 
> > local 
> >>  > storage. My 
> >>  >>  > system has 
> >>  >>  >>  > no disk and this doesn't quite work for me. 
> >>  >>  >>  >> 
> >>  >>  >>  >>  What's are the kernel parameters I need 
> > to use to 
> >>  > boot the 
> >>  >>  > node into 
> >>  >>  >>  > RAM automatically?  I am OK as the first step with 
> > a 
> >>  > stateless node. 
> >>  >>  >>  > 
> >>  >>  >>  > Hey David,
> >>  >>  >>  > 
> >>  >>  >>  > the stateless mode is currently not completely 
> > working with 
> >>  > oVirt
> >>  >>  >>  > Engine. That means a Node needs to b

Re: [Users] Gluster Volume Info won't update

[Sahina Bose]

On 12/08/2013 01:51 PM, Andrew Lau wrote:
The defined cluster keeps showing me the option to import the 
gsx.melb.example.net  hosts into the 
cluster as hosts.


Under the Host's Network interfaces sub tab there is another issue 
I've got was it's picking up the keepalived floating IP address rather 
than the one assigned, but yes the network is listed as I managed it 
through ovirt.


Could you attach the engine.log as well as the vdsm.log from the node?



On Fri, Dec 6, 2013 at 9:22 PM, Sahina Bose > wrote:



On 12/06/2013 03:29 PM, Sahina Bose wrote:


On 12/06/2013 10:00 AM, Kanagaraj wrote:


On 12/06/2013 09:46 AM, Andrew Lau wrote:

Yup - it's ovirt cluster version 3.3 with gluster 3.4.1


what does "gluster volume info " and "gluster volume status
" say?


There's an issue where engine cannot sync the bricks, as bricks
return a different IP address than the one engine is aware of (in
this case gsx.melb.example.net 
while engine knows the host as hvx.melb.example.net
) . We need to fix this path to use
the gluster host UUID as well.

Have logged a bug to track this -
https://bugzilla.redhat.com/show_bug.cgi?id=1038988




Could you also let us know if the following network is listed
under your Host's Network Interfaces sub tab?
172.16.1.1 (gluster) gsx.melb.example.net


If it is, then even without any fix, it should have worked for you
and we need to dig further on why it did not.









On Fri, Dec 6, 2013 at 3:11 PM, Kanagaraj mailto:kmayi...@redhat.com>>wrote:


On 12/06/2013 07:55 AM, Andrew Lau wrote:

Because of a few issues I had with keepalived, I moved my
storage network to it's own VLAN but it seems to have
broken part of the ovirt gluster management.

Same scenario:
2 Hosts

1x Engine, VDSM, Gluster
1x VDSM,Gluster

So to properly split the gluster data and ovirtmgmt I
simply assigned them two host names and two IPS.

172.16.0.1 (ovirtmgmt) hvx.melb.example.net

172.16.1.1 (gluster) gsx.melb.example.net


However the oVirt engine does not seem to like this, it
would not pick up the gluster volume as "running" until I
did a restart through the UI.

The issue (possible bug) I'm seeing is the logs are being
filled with http://www.fpaste.org/59440/13862963/

Volume information isn't being pulled as it thinks the
gs01.melb.example.net  is
not within the cluster, where in fact it is but registered
under hv01.melb.example.net 



What's compatibility version of the clusters?

From 3.3 onwards, gluster-host-uuid is used to identify a
host instead of hostname.

Thanks,
Kanagaraj



Thanks,
Andrew


___
Users mailing list
Users@ovirt.org  
http://lists.ovirt.org/mailman/listinfo/users







___
Users mailing list
Users@ovirt.org  
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org  
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] 3.3.2 tested agsinst Fedora 20?

[Itamar Heim]

On 12/08/2013 03:28 PM, Antoni Segura Puimedon wrote:



- Original Message -

From: "Markus Stockhausen" 
To: users@ovirt.org
Sent: Sunday, December 8, 2013 8:49:42 AM
Subject: [Users] 3.3.2 tested agsinst Fedora 20?

Hello,

On the 3.3.2 testing page I saw that several tests where made for Fedora 20
nodes. The created bz notes suggest that they are based on the nightly
builds.


We have been testing git master on Fedora20 and backported fixes. Also recently
we performed release branch tests on Fedora 20 (Douglas did).



Is Fedora 20 really a target for 3.3.2 or are the results only posted because
we lack a 3.4 testing page?


Fedora20 is about to be released, so it will be a target.


i think its worth while testing master and 3.3.2 on fedora 20, but at 
least for engine, i don't think f20 is a target without some patching.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] What agents are needed?

[Nicholas Kesick]

 
> From: michal.skriva...@redhat.com
> Date: Tue, 3 Dec 2013 14:23:19 +0100
> To: blas...@556nato.com
> CC: users@ovirt.org
> Subject: Re: [Users] What agents are needed?
> 
> 
> On Dec 3, 2013, at 10:52 , Vinzenz Feenstra  wrote:
> 
> > On 11/30/2013 09:49 PM, Blaster wrote:
> >> There doesn't seem to be a single "tools" or "agent" install like there is 
> >> under ESXi, that's required to be installed under ovirt, instead I've seen 
> >> references to
> >> 
> >> 1) virtio drivers
> >> 2) Spice drivers
> >> 3) qemu agent
> >> 
> >> What's really needed under both Windows and Linux to get guests working 
> >> properly?
> > Well it depends on what you consider 'working properly'
> > 
> > Mainly you will need to have the VirtIO drivers, the Spice Drivers and the 
> > Spice VDAgent
> > For additional features supported by oVirt you'll also need the 
> > ovirt-guest-agent
> > The qemu agent is currently optional, however will be required together 
> > with the ovirt-guest-agent at some point to support some additional 
> > features.
> > 
> >> 
> >> Are all these agents included in Fedora?
> > Yes they are.
> 
> btw the virtio drivers are already in kernel so for a bare minimum 
> functionality you're ready to go without any additional sw on Fedora. If you 
> want copy&paste in SPICE you need vdagent, if you need detailed utilization 
> statistics, app list, guest IP reporting, SSO  you need ovirt-guest-agent. If 
> you need the new backup API and hotplug CPU in the future you'll need qemu-ga 
> as well
>  Michal, thank you for sharing this information. I am going to try and get 
> this into added to the wiki. Blaster if this helps:For Fedora, you can get 
> the guest agent and spice drivers by running "yum install ovirt-guest-agent 
> spice-vdagent" . Additional steps for the ovirt-guest-agent install here ( 
> http://www.ovirt.org/How_to_install_the_guest_agent_in_Fedora) but I wasn't 
> aware of the spice-vdagent. For Windows- you can get the VirtIO drivers by 
> downloading the iso from 
> http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/, upload it to 
> your ISO store, change the CD on the vm, and then install the drivers through 
> device manager. That will solve virtio-serial and virtio-scsi- you can get 
> the spice drivers by downloading the windows binary from 
> http://www.spice-space.org/download.html (I added this to the wiki this 
> week). Note: Win7 and lower right now.- you can get the ovirt-guest-agent by 
> following these directions: 
> http://www.ovirt.org/OVirt_Guest_Agent_For_Windows 

> Thanks,
> michal
> 
> >> 
> >> 
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> > 
> > 
> > -- 
> > Regards,
> > 
> > Vinzenz Feenstra | Senior Software Engineer
> > RedHat Engineering Virtualization R & D
> > Phone: +420 532 294 625
> > IRC: vfeenstr or evilissimo
> > 
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at redhat.com
> > 
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] avoid debug messages or explain better how to change log level

[Gianluca Cecchi]

On Sun, Dec 8, 2013 at 4:06 PM, Dan Kenigsberg wrote:
> On Sun, Dec 08, 2013 at 12:19:10AM +0100, Gianluca Cecchi wrote:
>> On Sun, Dec 8, 2013 at 1:41 AM, Douglas Schilling Landgraf  wrote:
>>
>>
>> BTW: the ERROR ones are for lines such as
>> Thread-30::ERROR::2013-12-07
>> 23:04:26,939::sdc::137::Storage.StorageDomainCache::(_findDomain)
>> looking for unfetched domain 0a8035e6-e41d-40ff-a154-e0a374f264b2
>> Thread-30::ERROR::2013-12-07
>> 23:04:26,939::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
>> looking for domain 0a8035e6-e41d-40ff-a154-e0a374f264b2
>> I don't know exactly to what they refer as I don't have an sdc disk
>> and don't know how to solve
>
> This log line indicates a serious error if that domain has an iSCSI path to 
> it, and is quite bogus if it's pure FC.
>
> We need to solve this duality in one way or another.
>
> http://gerrit.ovirt.org/#/c/21597/ for more reference.

Thanks for the info.
Actually in my case we are talking about an AIO install with local on
host datacenter and local on host storage pointing to /DATA directory
(that is under / filesystem).
I then added another local on host storage domain pointing to another
directory (/data/DATA2 where /data is another filesystem mount point)
Is it going to be addressed in 3.3.2 beta and/or final?

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] avoid debug messages or explain better how to change log level

[Dan Kenigsberg]

On Sun, Dec 08, 2013 at 12:19:10AM +0100, Gianluca Cecchi wrote:
> On Sun, Dec 8, 2013 at 1:41 AM, Douglas Schilling Landgraf  wrote:
>
>
> BTW: the ERROR ones are for lines such as
> Thread-30::ERROR::2013-12-07
> 23:04:26,939::sdc::137::Storage.StorageDomainCache::(_findDomain)
> looking for unfetched domain 0a8035e6-e41d-40ff-a154-e0a374f264b2
> Thread-30::ERROR::2013-12-07
> 23:04:26,939::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
> looking for domain 0a8035e6-e41d-40ff-a154-e0a374f264b2
> I don't know exactly to what they refer as I don't have an sdc disk
> and don't know how to solve

This log line indicates a serious error if that domain has an iSCSI path to it, 
and is quite bogus if it's pure FC.

We need to solve this duality in one way or another.

http://gerrit.ovirt.org/#/c/21597/ for more reference.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] 3.3.2 tested agsinst Fedora 20?

[Antoni Segura Puimedon]

- Original Message -
> From: "Markus Stockhausen" 
> To: users@ovirt.org
> Sent: Sunday, December 8, 2013 8:49:42 AM
> Subject: [Users] 3.3.2 tested agsinst Fedora 20?
> 
> Hello,
> 
> On the 3.3.2 testing page I saw that several tests where made for Fedora 20
> nodes. The created bz notes suggest that they are based on the nightly
> builds.

We have been testing git master on Fedora20 and backported fixes. Also recently
we performed release branch tests on Fedora 20 (Douglas did).

> 
> Is Fedora 20 really a target for 3.3.2 or are the results only posted because
> we lack a 3.4 testing page?

Fedora20 is about to be released, so it will be a target.

> 
> Thanks
> 
> Markus
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] avoid debug messages or explain better how to change log level

[Gianluca Cecchi]

On Sun, Dec 8, 2013 at 12:19 AM, Gianluca Cecchi wrote:
> On Sun, Dec 8, 2013 at 1:41 AM, Douglas Schilling Landgraf  wrote:
>
>>
>> IMO, looks reasonable. Could you please be more specific and share which
>> messages are flooding the log files? Would be nice if you open a bugzilla
>> request [1] based on component (vdsm/ovirt-engine) to get it tracked.
>>
>> https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt
>>
>> --
>> Cheers
>> Douglas
>
> Reading better, for engine now it is ok and it seems that level is
> INFO, no DEBUG messages. Good.
> But for vdsm/superdsm, my AIO server that for example today has been
> powered on without making anything else than keep an idle windows xp
> and an idle fedora 19 vm
> has these numbers


see also here as already leveraged in February for ovirt node and
persist problems
http://lists.ovirt.org/pipermail/users/2013-February/012617.html

It is only a matter of changing default values for  /etc/vdsm/logger.conf

In 3.3.1 and still in vdsm as in in 3.3.2 beta we have now

[g.cecchi@tekkaman ~]$ grep -B1 DEBUG /etc/vdsm/logger.conf
[logger_root]
level=DEBUG
--
[logger_vds]
level=DEBUG
--
[logger_Storage]
level=DEBUG
--
filters=storage.misc.TracebackRepeatFilter
level=DEBUG

Changing these lines in my environment to INFO kept off the DEBUG
messages with about one INFO message per second.
Or we could provide a page on the wiki and/or release notes where we
explain how to change logging levels and files involved if you think
that DEBUG for vdsmd is still the way to have.

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Gluster Volume Info won't update

[Andrew Lau]

The defined cluster keeps showing me the option to import the
gsx.melb.example.net hosts into the cluster as hosts.

Under the Host's Network interfaces sub tab there is another issue I've got
was it's picking up the keepalived floating IP address rather than the one
assigned, but yes the network is listed as I managed it through ovirt.

On Fri, Dec 6, 2013 at 9:22 PM, Sahina Bose  wrote:

>
> On 12/06/2013 03:29 PM, Sahina Bose wrote:
>
>
> On 12/06/2013 10:00 AM, Kanagaraj wrote:
>
>
> On 12/06/2013 09:46 AM, Andrew Lau wrote:
>
>  Yup - it's ovirt cluster version 3.3 with gluster 3.4.1
>
>
> what does "gluster volume info " and "gluster volume status "
> say?
>
>
> There's an issue where engine cannot sync the bricks, as bricks return a
> different IP address than the one engine is aware of (in this case
> gsx.melb.example.net while engine knows the host as hvx.melb.example.net)
> . We need to fix this path to use the gluster host UUID as well.
>
> Have logged a bug to track this -
> https://bugzilla.redhat.com/show_bug.cgi?id=1038988
>
>
>
> Could you also let us know if the following network is listed under your
> Host's Network Interfaces sub tab?
> 172.16.1.1 (gluster) gsx.melb.example.net
>
> If it is, then even without any fix, it should have worked for you and we
> need to dig further on why it did not.
>
>
>
>
>
>
>  On Fri, Dec 6, 2013 at 3:11 PM, Kanagaraj  wrote:
>
>>
>> On 12/06/2013 07:55 AM, Andrew Lau wrote:
>>
>>  Because of a few issues I had with keepalived, I moved my storage
>> network to it's own VLAN but it seems to have broken part of the ovirt
>> gluster management.
>>
>>  Same scenario:
>>  2 Hosts
>>
>>  1x Engine, VDSM, Gluster
>>  1x VDSM,Gluster
>>
>>  So to properly split the gluster data and ovirtmgmt I simply assigned
>> them two host names and two IPS.
>>
>>  172.16.0.1 (ovirtmgmt) hvx.melb.example.net
>> 172.16.1.1 (gluster) gsx.melb.example.net
>>
>>  However the oVirt engine does not seem to like this, it would not pick
>> up the gluster volume as "running" until I did a restart through the UI.
>>
>>  The issue (possible bug) I'm seeing is the logs are being filled with
>> http://www.fpaste.org/59440/13862963/
>>
>>  Volume information isn't being pulled as it thinks the
>> gs01.melb.example.net is not within the cluster, where in fact it is but
>> registered under hv01.melb.example.net
>>
>>
>>  What's compatibility version of the clusters?
>>
>> From 3.3 onwards, gluster-host-uuid is used to identify a host instead of
>> hostname.
>>
>> Thanks,
>> Kanagaraj
>>
>>
>>  Thanks,
>> Andrew
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users