date:20140805

Hi All,

I have followed the following document to install the websocket proxy on
seperate machine :-

http://www.ovirt.org/Features/noVNC_console#Setup_Websocket_Proxy_on_a_Separate_Machine

But when i try to open the VNC console it failed with the following errors
:-

Server disconnected (code: 1006)

Engine Logs :-

-
2014-08-05 15:51:22,540 INFO
 [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-5)
[6101845f] Running command: SetVmTicketCommand internal: false. Entities
affected :  ID: 6e0caf73-ae7d-493e-a51d-ecc32f507f00 Type: VM
2014-08-05 15:51:22,574 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
(ajp--127.0.0.1-8702-5) [6101845f] START, SetVmTicketVDSCommand(HostName =
Quanta, HostId = 10d7b6ea-d9fa-46af-bcd7-1d7b3c15b5ca,
vmId=6e0caf73-ae7d-493e-a51d-ecc32f507f00, ticket=5r7OgcpCeGCt,
validTime=120,m userName=admin,
userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 67f98489
2014-08-05 15:51:22,596 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
(ajp--127.0.0.1-8702-5) [6101845f] FINISH, SetVmTicketVDSCommand, log id:
67f98489
2014-08-05 15:51:22,623 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ajp--127.0.0.1-8702-5) [6101845f] Correlation ID: 6101845f, Call Stack:
null, Custom Event ID: -1, Message: user admin initiated console session
for VM test1
-

When I navigate to https://websocketproxyip:port to accept the
certificate the first time... it throws an error The connection was reset

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

[ovirt-users] service vdsmd reconfigure not working

2014-08-05 Thread Jorick Astrego


Hi,

Trying out latest 3.5 nightly vdsm (vdsm-4.16.1-4.gitb2bf270.el7.x86_64) 
and while following the guide 
(http://www.ovirt.org/Installing_VDSM_from_rpm), I run into the problem 
that service vdsmd reconfigure is not working anymore:


   # service vdsmd reconfigure
   The service command supports only basic LSB actions (start, stop,
   restart, try-restart, reload, force-reload, status). For other
   actions, please try to use systemctl.

Is this deprecated?

Kind regards,

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

Re: [ovirt-users] ovirt guest agent iso

2014-08-05 Thread Tiemen Ruiten

Hello Lev,

It seems to have been caused by Ovirt Guest tools service that was left
behind and didnt't get updated. Looks OK now.

On 4 August 2014 22:15, Tiemen Ruiten t.rui...@rdmedia.com wrote:

Hello Lev,

That's right, attach/mount the iso through the ovirt admin interface, then
open the cd drive and double click on ovirt-guest-tools-setup.exe. I'm
using Server 2012 R2 Standard. The same thing happened on all 12 servers I
installed last week, but they were cloned from the same oVirt template
though. I will try to reproduce this tomorrow with a clean install and also
double check build number.

On 4 August 2014 18:00, Lev Veyde lve...@redhat.com wrote:

Hi Tiemen,

That is quite strange behaviour...

I tried to reproduce this, but was unable to do so.
You simply double-click on the ovirt-guest-tools-setup executable file on
the CD right? Or you do something else?
If you do something different can you please explain the exact scenario
of what you do?

Can you please provide me with the exact release details of 2K12R2 that
you're using? (I used Standard, Build 9600).

Also, can you please try again installing the tools on the clean instance
of 2K12R2 ?

Just as a side note, the ovirt-guest-tools-setup.exe can be copied to any
location and run from there, as it self-contains all the necessary files.
The installer doesn't copies any files from the CD's bin directory etc.,
nor it's supposed to run any of the files included on the CD.
The sole purpose of these files on the CD is for user's convenience, to
allow i.e. manual copying and installation of oVirt Guest Agent if one
desires so.

Thanks in advance,
Lev Veyde.

- Original Message -
From: Tiemen Ruiten t.rui...@rdmedia.com
To: lve...@redhat.com, sbona...@redhat.com
Cc: users@ovirt.org
Sent: Tuesday, July 29, 2014 2:49:52 PM
Subject: Re: [ovirt-users] ovirt guest agent iso

I'm afraid I have to retract my statement: After a reboot I discovered
the files are installed to C:\Program Files (x86)\oVirt Guest Tools, but
the service is installed with a path to the CD drive
(D:\bin\OvirtGuestService.exe).

On 07/26/14 04:44, Tiemen Ruiten wrote:
I installed the newest iso 3.5_5 on my Server 2012 R2 guests and it
works nicely now.

On 23-07-14 10:41, Lev Veyde wrote:
Hi Sandro,

No, it doesn't.

But the latest release (ISO 3.5_5) should support this OS.

Thanks in advance,
Lev Veyde.

- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Tiemen Ruiten t.rui...@rdmedia.com, users@ovirt.org,
lve...@redhat.com, Simone Tiraboschi stira...@redhat.com
Sent: Wednesday, July 23, 2014 11:08:11 AM
Subject: Re: [ovirt-users] ovirt guest agent iso

Il 23/07/2014 10:02, Tiemen Ruiten ha scritto:
On 07/23/14 08:13, Sandro Bonazzola wrote:
Il 14/07/2014 10:21, Tiemen Ruiten ha scritto:
On 07/11/14 17:13, Bob Doolittle wrote:
On 07/11/2014 11:12 AM, Bob Doolittle wrote:
On 07/11/2014 10:55 AM, Tiemen Ruiten wrote:
Hello,

Is it possible/advisable to install the Windows Guest Agent
tools 3.5
ISO on a VM on a 3.4.2 oVirt cluster?
Yes. I've done just that. Works great.
Caveat - there was a bug related to not setting the Guest Agent to
autostart (at least for Windows 2008 R2). I think that's been fixed
but don't know if the fix has been pushed to the latest ISO yet.
Workaround - go into Services and change it from Manual to
Automatic.

-Bob

Unfortunately, I get 'Unsupported Windows version' on Windows Server
2012 R2.

Which release of the iso are you using?

This one:

http://resources.ovirt.org/pub/ovirt-master-snapshot-static/iso/ovirt-guest-tools/ovirt-guest-tools-3.5-2.iso

Lev, does above build include 2012 R2 support?
We're going to release a new build today as part of the 3.5.0 beta 2
release, can you re-test it once it's ready?

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

--
Tiemen Ruiten
Systems Engineer
RD Media

--
Tiemen Ruiten
Systems Engineer
RD Media
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] protocoldetector::192::vds.MultiProtocolAcceptor::(_handle_connection_read) Unrecognized protocol

2014-08-05 Thread Jorick Astrego


Hi,

When trying to add a manually installed 3.5-git vdsm on Centos 7, I get 
these messages:


   Detector thread::DEBUG::2014-08-05
   
08:07:12,445::protocoldetector::160::vds.MultiProtocolAcceptor::(_add_connection)
   Adding connection from **.***.***.***:34219
   Detector thread::DEBUG::2014-08-05
   
08:07:12,448::protocoldetector::171::vds.MultiProtocolAcceptor::(_remove_connection)
   Connection removed from **.***.***.***:34219
   Detector thread::WARNING::2014-08-05
   
08:07:12,448::protocoldetector::192::vds.MultiProtocolAcceptor::(_handle_connection_read)
   Unrecognized protocol: '\x16\x03\x00\x00c\x01\x00\x00_\x03\x00'


The engine install fails by the way, I think it's because of lvm:

   storageRefresh::DEBUG::2014-08-05
   08:06:32,292::lvm::317::Storage.OperationMutex::(_reloadpvs)
   Operation 'lvm reload operation' got the operation mutex
   storageRefresh::DEBUG::2014-08-05
   08:06:32,293::lvm::288::Storage.Misc.excCmd::(cmd) /usr/bin/sudo -n
   /usr/sbin/lvm pvs --config ' devices { preferred_names =
   [^/dev/mapper/] ignore_suspended_devices=1 write_cache_state=0
   disable_after_error_count=3 obtain_device_list_from_udev=0 filter =
   [ '\''r|.*|'\'' ] }  global {  locking_type=1
   prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0 } backup
   {  retain_min = 50  retain_days = 0 } ' --noheadings --units b
   --nosuffix --separator '|' --ignoreskippedcluster -o
   
uuid,name,size,vg_name,vg_uuid,pe_start,pe_count,pe_alloc_count,mda_count,dev_size
   (cwd None)
   storageRefresh::DEBUG::2014-08-05
   08:06:32,319::lvm::288::Storage.Misc.excCmd::(cmd) SUCCESS: err =
   '  WARNING: lvmetad is running but disabled. Restart lvmetad before
   enabling it!\n'; rc = 0
   storageRefresh::DEBUG::2014-08-05
   08:06:32,320::lvm::342::Storage.OperationMutex::(_reloadpvs)
   Operation 'lvm reload operation' released the operation mutex
   storageRefresh::DEBUG::2014-08-05
   08:06:32,320::lvm::365::Storage.OperationMutex::(_reloadvgs)
   Operation 'lvm reload operation' got the operation mutex
   storageRefresh::DEBUG::2014-08-05
   08:06:32,321::lvm::288::Storage.Misc.excCmd::(cmd) /usr/bin/sudo -n
   /usr/sbin/lvm vgs --config ' devices { preferred_names =
   [^/dev/mapper/] ignore_suspended_devices=1 write_cache_state=0
   disable_after_error_count=3 obtain_device_list_from_udev=0 filter =
   [ '\''r|.*|'\'' ] }  global {  locking_type=1
   prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0 } backup
   {  retain_min = 50  retain_days = 0 } ' --noheadings --units b
   --nosuffix --separator '|' --ignoreskippedcluster -o
   
uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name
   (cwd None)
   storageRefresh::DEBUG::2014-08-05
   08:06:32,344::lvm::288::Storage.Misc.excCmd::(cmd) SUCCESS: err =
   '  WARNING: lvmetad is running but disabled. Restart lvmetad before
   enabling it!\n  No volume groups found\n'; rc = 0
   storageRefresh::DEBUG::2014-08-05
   08:06:32,345::lvm::407::Storage.OperationMutex::(_reloadvgs)
   Operation 'lvm reload operation' released the operation mutex
   storageRefresh::DEBUG::2014-08-05
   08:06:32,345::lvm::288::Storage.Misc.excCmd::(cmd) /usr/bin/sudo -n
   /usr/sbin/lvm lvs --config ' devices { preferred_names =
   [^/dev/mapper/] ignore_suspended_devices=1 write_cache_state=0
   disable_after_error_count=3 obtain_device_list_from_udev=0 filter =
   [ '\''r|.*|'\'' ] }  global {  locking_type=1
   prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0 } backup
   {  retain_min = 50  retain_days = 0 } ' --noheadings --units b
   --nosuffix --separator '|' --ignoreskippedcluster -o
   uuid,name,vg_name,attr,size,seg_start_pe,devices,tags (cwd None)
   storageRefresh::DEBUG::2014-08-05
   08:06:32,365::lvm::288::Storage.Misc.excCmd::(cmd) SUCCESS: err =
   '  WARNING: lvmetad is running but disabled. Restart lvmetad before
   enabling it!\n  No volume groups found\n'; rc = 0
   storageRefresh::DEBUG::2014-08-05
   08:06:32,366::lvm::365::Storage.OperationMutex::(_reloadvgs)
   Operation 'lvm reload operation' got the operation mutex
   storageRefresh::DEBUG::2014-08-05
   08:06:32,366::lvm::288::Storage.Misc.excCmd::(cmd) /usr/bin/sudo -n
   /usr/sbin/lvm vgs --config ' devices { preferred_names =
   [^/dev/mapper/] ignore_suspended_devices=1 write_cache_state=0
   disable_after_error_count=3 obtain_device_list_from_udev=0 filter =
   [ '\''r|.*|'\'' ] }  global {  locking_type=1
   prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0 } backup
   {  retain_min = 50  retain_days = 0 } ' --noheadings --units b
   --nosuffix --separator '|' --ignoreskippedcluster -o
   
uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name
   (cwd None)
   storageRefresh::DEBUG::2014-08-05
   08:06:32,386::lvm::288::Storage.Misc.excCmd::(cmd) SUCCESS: err =
   '  WARNING: lvmetad is running but disabled. Restart lvmetad before

Re: [ovirt-users] service vdsmd reconfigure not working

2014-08-05 Thread Jorick Astrego



On 08/05/2014 10:02 AM, Jorick Astrego wrote:

Hi,

Trying out latest 3.5 nightly vdsm 
(vdsm-4.16.1-4.gitb2bf270.el7.x86_64) and while following the guide 
(http://www.ovirt.org/Installing_VDSM_from_rpm), I run into the 
problem that service vdsmd reconfigure is not working anymore:


# service vdsmd reconfigure
The service command supports only basic LSB actions (start, stop,
restart, try-restart, reload, force-reload, status). For other
actions, please try to use systemctl.

Is this deprecated?

Kind regards,

Jorick Astreg

Before someone else gives me this answer, I used vdsm-tool configure 
--force without problems.


Kind regards,
Jorick Astrego
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt guest agent iso

2014-08-05 Thread Lev Veyde

Hi Tiemen,

Thanks for the update, glad to see that everything works great for you.
Please feel free to contact me if you notice any issues with the oVirt WGT.

Thanks in advance,
Lev Veyde.

- Original Message -
From: Tiemen Ruiten t.rui...@rdmedia.com
To: Lev Veyde lve...@redhat.com
Cc: sbona...@redhat.com, users@ovirt.org
Sent: Tuesday, August 5, 2014 11:19:49 AM
Subject: Re: [ovirt-users] ovirt guest agent iso

Hello Lev,

It seems to have been caused by Ovirt Guest tools service that was left
behind and didnt't get updated. Looks OK now.


On 4 August 2014 22:15, Tiemen Ruiten t.rui...@rdmedia.com wrote:

 Hello Lev,

 That's right, attach/mount the iso through the ovirt admin interface, then
 open the cd drive and double click on ovirt-guest-tools-setup.exe. I'm
 using Server 2012 R2 Standard. The same thing happened on all 12 servers I
 installed last week, but they were cloned from the same oVirt template
 though. I will try to reproduce this tomorrow with a clean install and also
 double check build number.




 On 4 August 2014 18:00, Lev Veyde lve...@redhat.com wrote:

 Hi Tiemen,

 That is quite strange behaviour...

 I tried to reproduce this, but was unable to do so.
 You simply double-click on the ovirt-guest-tools-setup executable file on
 the CD right? Or you do something else?
 If you do something different can you please explain the exact scenario
 of what you do?

 Can you please provide me with the exact release details of 2K12R2 that
 you're using? (I used Standard, Build 9600).

 Also, can you please try again installing the tools on the clean instance
 of 2K12R2 ?

 Just as a side note, the ovirt-guest-tools-setup.exe can be copied to any
 location and run from there, as it self-contains all the necessary files.
 The installer doesn't copies any files from the CD's bin directory etc.,
 nor it's supposed to run any of the files included on the CD.
 The sole purpose of these files on the CD is for user's convenience, to
 allow i.e. manual copying and installation of oVirt Guest Agent if one
 desires so.

 Thanks in advance,
 Lev Veyde.

 - Original Message -
 From: Tiemen Ruiten t.rui...@rdmedia.com
 To: lve...@redhat.com, sbona...@redhat.com
 Cc: users@ovirt.org
 Sent: Tuesday, July 29, 2014 2:49:52 PM
 Subject: Re: [ovirt-users] ovirt guest agent iso

 I'm afraid I have to retract my statement: After a reboot I discovered
 the files are installed to C:\Program Files (x86)\oVirt Guest Tools, but
 the service is installed with a path to the CD drive
 (D:\bin\OvirtGuestService.exe).

 On 07/26/14 04:44, Tiemen Ruiten wrote:
  I installed the newest iso 3.5_5 on my Server 2012 R2 guests and it
  works nicely now.
 
  On 23-07-14 10:41, Lev Veyde wrote:
  Hi Sandro,
 
  No, it doesn't.
 
  But the latest release (ISO 3.5_5) should support this OS.
 
  Thanks in advance,
  Lev Veyde.
 
  - Original Message -
  From: Sandro Bonazzola sbona...@redhat.com
  To: Tiemen Ruiten t.rui...@rdmedia.com, users@ovirt.org,
 lve...@redhat.com, Simone Tiraboschi stira...@redhat.com
  Sent: Wednesday, July 23, 2014 11:08:11 AM
  Subject: Re: [ovirt-users] ovirt guest agent iso
 
  Il 23/07/2014 10:02, Tiemen Ruiten ha scritto:
  On 07/23/14 08:13, Sandro Bonazzola wrote:
  Il 14/07/2014 10:21, Tiemen Ruiten ha scritto:
  On 07/11/14 17:13, Bob Doolittle wrote:
  On 07/11/2014 11:12 AM, Bob Doolittle wrote:
  On 07/11/2014 10:55 AM, Tiemen Ruiten wrote:
  Hello,
 
  Is it possible/advisable to install the Windows Guest Agent
 tools 3.5
  ISO on a VM on a 3.4.2 oVirt cluster?
  Yes. I've done just that. Works great.
  Caveat - there was a bug related to not setting the Guest Agent to
  autostart (at least for Windows 2008 R2). I think that's been fixed
  but don't know if the fix has been pushed to the latest ISO yet.
  Workaround - go into Services and change it from Manual to
 Automatic.
 
  -Bob
 
  Unfortunately, I get 'Unsupported Windows version' on Windows Server
  2012 R2.
 
  Which release of the iso are you using?
 
 
  This one:
 
 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/iso/ovirt-guest-tools/ovirt-guest-tools-3.5-2.iso
 
  Lev, does above build include 2012 R2 support?
  We're going to release a new build today as part of the 3.5.0 beta 2
 release, can you re-test it once it's ready?
 
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users


 --
 Tiemen Ruiten
 Systems Engineer
 RD Media




 --
 Tiemen Ruiten
 Systems Engineer
 RD Media




-- 
Tiemen Ruiten
Systems Engineer
RD Media
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Standalone Websocket Proxy not working

2014-08-05 Thread Simone Tiraboschi

Hi Punit,
I'm assuming that you are using a local internal CA,
did explicit trusted it in your browser?

You can get your local CA cert from:
https://your_engine_fqdn/ca.crt

Please download it, add it into the list of your trusted CA in your browser and 
try again.

oVirt 3.5 will provide a mechanism to deploy the websocket proxy on a separate 
host via engine-setup. Also in that scenario you still have to trust the CA in 
your browser.


ciao,
Simone


- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: users@ovirt.org, Dan Kenigsberg dan...@redhat.com, aha...@redhat.com, 
Sven Kieske s.kie...@mittwald.de, Michal Skrivanek 
michal.skriva...@redhat.com, Antoni Segura Puimedon asegu...@redhat.com, 
Frantisek Kobzik fkob...@redhat.com, sabose sab...@redhat.com, Itamar 
Heim ih...@redhat.com, barum...@redhat.com
Sent: Tuesday, August 5, 2014 9:56:41 AM
Subject: [ovirt-users] Standalone Websocket Proxy not working

Hi All, 

I have followed the following document to install the websocket proxy on 
seperate machine :- 

http://www.ovirt.org/Features/noVNC_console#Setup_Websocket_Proxy_on_a_Separate_Machine
 

But when i try to open the VNC console it failed with the following errors :- 

Server disconnected (code: 1006) 

Engine Logs :- 

- 
2014-08-05 15:51:22,540 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] 
(ajp--127.0.0.1-8702-5) [6101845f] Running command: SetVmTicketCommand 
internal: false. Entities affected : ID: 6e0caf73-ae7d-493e-a51d-ecc32f507f00 
Type: VM 
2014-08-05 15:51:22,574 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-5) [6101845f] START, SetVmTicketVDSCommand(HostName = 
Quanta, HostId = 10d7b6ea-d9fa-46af-bcd7-1d7b3c15b5ca, 
vmId=6e0caf73-ae7d-493e-a51d-ecc32f507f00, ticket=5r7OgcpCeGCt, validTime=120,m 
userName=admin, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 67f98489 
2014-08-05 15:51:22,596 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-5) [6101845f] FINISH, SetVmTicketVDSCommand, log id: 
67f98489 
2014-08-05 15:51:22,623 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(ajp--127.0.0.1-8702-5) [6101845f] Correlation ID: 6101845f, Call Stack: null, 
Custom Event ID: -1, Message: user admin initiated console session for VM test1 
- 

When I navigate to https://websocketproxyip :port to accept the certificate 
the first time... it throws an error The connection was reset 

Thanks, 
Punit 




___
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: [ovirt-users] Network Question

2014-08-05 Thread Sahina Bose



On 08/04/2014 09:06 AM, Punit Dambiwal wrote:

Hi Sahina,

But when i try to add the gluster Hosts from Ovirtit doesn't 
display the FQDN to add the bricks...it display the ip address 
only...i will try to use the work around


When you add the gluster host to oVirt, you should have provided the 
FQDN in the host address field. It uses this to display the list of 
hosts from which you can add the bricks





Another question is what will be the drawbacks if i use ovirtmgmt and 
storage on the same network (i will use 10GB network here with bonding) ??



On Fri, Aug 1, 2014 at 6:14 PM, Sahina Bose sab...@redhat.com 
mailto:sab...@redhat.com wrote:



On 08/01/2014 02:51 PM, Dan Kenigsberg wrote:

On Fri, Aug 01, 2014 at 09:43:07AM +0800, Punit Dambiwal wrote:

Hi All,

Is there any update on this ??


On Thu, Jul 31, 2014 at 9:08 AM, Punit Dambiwal
hypu...@gmail.com mailto:hypu...@gmail.com wrote:

Hi Antoni,

But all the bricks and gluster in the another
subnet...I am using the
Compute and gluster storage combined on the same host

Ovirtmgmt :- 43.25.76.0/24 http://43.25.76.0/24
Gluster Storage :- 10.10.10.0/24 http://10.10.10.0/24

Did you try to follow Sahina's advice?

qemu-to-gluster communication goes on top the IP that you mount.
However, without hacks, inter-gluster communication uses FQDN
of hosts,
which most commonly resolves to the management network.



From the output of your gluster volume info , it looks like you
have used IP address (43.25...) to peer probe the hosts? If you
add the host from oVirt, for gluster to be able to use separate
network for glusterd-glusterd communication, you will need to use
FQDN while adding the host, and workaround as mentioned in
http://lists.ovirt.org/pipermail/users/2014-February/020894.html




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

Re: [ovirt-users] Convert vmware vm

2014-08-05 Thread Simone Tiraboschi

- Original Message -
 From: Michal Skrivanek michal.skriva...@redhat.com
 To: Sven Kieske s.kie...@mittwald.de
 Cc: mad196...@gmail.com, users@ovirt.org
 Sent: Monday, August 4, 2014 5:33:24 PM
 Subject: Re: [ovirt-users] Convert vmware vm

 On Aug 4, 2014, at 17:26 , Sven Kieske s.kie...@mittwald.de wrote:

  Am 03.08.2014 21:35, schrieb Itamar Heim:
  On 06/30/2014 09:50 AM, Sven Kieske wrote:
  No, as far as I know this is _not_ on the roadmap.

  actually it is.
  http://www.ovirt.org/Features/virt-v2v_Integration

  one of my comments to the feature page was it should include a file
  based conversion, not just from esxi.
  http://lists.ovirt.org/pipermail/users/2014-July/025876.html

  No, it's not:

  Offline VMware images (OVAs), not yet.  However patches are welcome.
  We quite literally have no one available to implement this.[1]

  [1]http://lists.ovirt.org/pipermail/users/2014-July/025881.html

  Or has this changed yet? This would be great news!

 well, it is in the plan to do that, so yes, it's on the roadmap
 is it done? no, not yet…
 We're hoping to get it in for 3.6 timeframe…

By the way, how are you going to copy the VM between the two system?
As far as I know scp doesn't handle really well with sparse files (and thin 
provisioned VMs are sparse files) ending up copying the fully expanded disk 
image wasting a lot of time just transferring zeroes.

Some third party utilities, like virtsync for the KVM world 
(http://www.virtsync.com/) or Veam FastSCP 
(http://www.veeam.com/vmware-esxi-fastscp.html) for the VMWare world, already 
implement some smarter copy approach (also a tar with -S option over an ssh 
pipe is indeed enough) to make it more efficient and they are quite appreciated.

Are we designing something similar?

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

Re: [ovirt-users] 答复: Error after changing IP of Node (FQDN is still the same)

2014-08-05 Thread Federico Simoncelli

What's the version of the vdsm and sanlock packages?

Can you please share the logs on the host side? We need vdsm.log
and sanlock.log containing the relevant errors (Cannot acquire host
id).

Thanks,
-- 
Federico


- Original Message -
 From: ml ml mliebher...@googlemail.com
 To: d...@redhat.com
 Cc: users@ovirt.org Users@ovirt.org
 Sent: Sunday, August 3, 2014 8:57:18 PM
 Subject: Re: [ovirt-users]答复: Error after changing IP of Node (FQDN is 
 still the same)
 
 ok, i now removed the nodes and added them again. Same FQDN. I still get
 Start SPM Task failed - result: cleanSuccess, message: VDSGenericException:
 VDSErrorException: Failed to HSMGetTaskStatusVDS, error = Cannot acquire
 host id, code = 661
 
 I also got some error.
 
 Now whats the deal with that host id?
 
 Can somone please point me to the way how to debug this instead of pressing
 some remove and add buttons?
 
 Does someone really know how ovirt works under the hood?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] SPM in oVirt 3.6

2014-08-05 Thread Federico Simoncelli

- Original Message -
 From: Nir Soffer nsof...@redhat.com
 To: Daniel Helgenberger daniel.helgenber...@m-box.de
 Cc: users@ovirt.org, Federico Simoncelli fsimo...@redhat.com
 Sent: Monday, July 28, 2014 6:43:30 PM
 Subject: Re: [ovirt-users] SPM in oVirt 3.6

 - Original Message -
  From: Daniel Helgenberger daniel.helgenber...@m-box.de
  To: users@ovirt.org
  Sent: Friday, July 25, 2014 7:51:33 PM
  Subject: [ovirt-users] SPM in oVirt 3.6

  just out of pure curiosity: In a BZ [1] Allon mentions SPM will go away
  in ovirt 3.6.

  This seems like a major change for me. I assume this will replace
  sanlock as well? What will SPM be replaced with?

 No, sanlock is not going anywhere.

 The change is that we will not have an SPM node, but any node that need to
 make meta data changes, will take a lock using sanlock while it make the
 changes.

 Federico: can you describe in more details how it is going to work?

Most of the information can be found on the feature page:

http://www.ovirt.org/Features/Decommission_Master_Domain_and_SPM

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

Re: [ovirt-users] SPM in oVirt 3.6

2014-08-05 Thread Chandrahasa S

Dear All,

Why we do not have Ovirt Forum like CentOS. Where I can see all reported / 
solved issues.

Regards,
Chandrahasa S
Tata Consultancy Services
Data Center- ( Non STPI)
2nd Pokharan Road,
Subash Nagar ,
Mumbai - 400601,Maharashtra
India
Ph:- +91 22 677-81825
Buzz:- 4221825
Mailto: chandrahas...@tcs.com
Website: http://www.tcs.com

Experience certainty.   IT Services
Business Solutions
Consulting




From:   Federico Simoncelli fsimo...@redhat.com
To: Daniel Helgenberger daniel.helgenber...@m-box.de
Cc: users@ovirt.org
Date:   08/05/2014 06:51 PM
Subject:Re: [ovirt-users] SPM in oVirt 3.6
Sent by:users-boun...@ovirt.org



- Original Message -
 From: Nir Soffer nsof...@redhat.com
 To: Daniel Helgenberger daniel.helgenber...@m-box.de
 Cc: users@ovirt.org, Federico Simoncelli fsimo...@redhat.com
 Sent: Monday, July 28, 2014 6:43:30 PM
 Subject: Re: [ovirt-users] SPM in oVirt 3.6
 
 - Original Message -
  From: Daniel Helgenberger daniel.helgenber...@m-box.de
  To: users@ovirt.org
  Sent: Friday, July 25, 2014 7:51:33 PM
  Subject: [ovirt-users] SPM in oVirt 3.6
  
  just out of pure curiosity: In a BZ [1] Allon mentions SPM will go 
away
  in ovirt 3.6.
  
  This seems like a major change for me. I assume this will replace
  sanlock as well? What will SPM be replaced with?
 
 No, sanlock is not going anywhere.
 
 The change is that we will not have an SPM node, but any node that need 
to
 make meta data changes, will take a lock using sanlock while it make the
 changes.
 
 Federico: can you describe in more details how it is going to work?

Most of the information can be found on the feature page:

http://www.ovirt.org/Features/Decommission_Master_Domain_and_SPM

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

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


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

Re: [ovirt-users] SPM in oVirt 3.6

2014-08-05 Thread Sven Kieske

I'm not 100% sure what you mean with forum
but there is the ovirt bugtracker
with all reported and solved issues:

https://bugzilla.redhat.com/buglist.cgi?list_id=2714543product=oVirt

HTH

Am 05.08.2014 16:22, schrieb Chandrahasa S:
 Dear All,
 
 Why we do not have Ovirt Forum like CentOS. Where I can see all reported / 
 solved issues.

-- 
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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 3.5.0 First Release Candidate is now, available for testing

2014-08-05 Thread Sandro Bonazzola

The oVirt team is pleased to announce that the 3.5.0 First Release Candidate is 
now
available for testing as of Aug 5th 2014.

The release candidate is available now for Fedora 19, Fedora 20 and Red Hat 
Enterprise Linux 6.5
(or similar) and allow you to use Red Hat Enterprise Linux 7 as node and run 
Hosted Engine.

Feel free to join us testing it on Tue Aug 12th third test day!

This release of oVirt includes numerous bug fixes.
See the release notes [1] for a list of the new features and bugs fixed.

The existing repository ovirt-3.5-pre has been updated for delivering this
release without the need of enabling any other repository.
If you're already using ovirt repository on EL7, please update ovirt-release3.5 
rpm,
it will provide additional repositories for it.

Please refer to release notes [1] for Installation / Upgrade instructions.
New oVirt Live, oVirt Guest Tools and oVirt Node ISO will be available soon as 
well[2].

Please note that mirrors may need a couple of days before being synchronized.
If you want to be sure to use latest rpms and don't want to wait for the 
mirrors,
you can edit /etc/yum.repos.d/ovirt-3.5.repo commenting the mirror line and
removing the comment on baseurl line.

Known issues in this RC:
- Bug 1124099 - Live Merge: Limit merge operations based on hosts' capabilities
- ovirt-optimizer has not been updated for EL6 due to dependencies issues
- vdsm for EL7 is missing a couple of patches compared to other distro due to 
building issues

[1] http://www.ovirt.org/OVirt_3.5_Release_Notes
[2] http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/

-- 
Sandro Bonazzola
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: [ovirt-users] Sharing iSCSI data stroage domain across multiple clusters in the same datacenter

2014-08-05 Thread santosh



On 08/04/2014 04:42 PM, Itamar Heim wrote:

On 08/04/2014 05:46 PM, santosh wrote:

On 08/03/2014 03:01 PM, Itamar Heim wrote:

On 07/30/2014 10:35 PM, santosh wrote:

Hi,
*
**Can we share the iSCSI data storage domain across multiple clusters in
the same datacenter?*

Following are the setup details which I tried.

  -One datacenter, Say DC1
  -in DC1, two clusters, say CL1 and CL2
  -In CL1, one host, say H1. And in CL2 one host, say H2
  -iSCSI Data Storage domain is configured where external storage
  LUNs are exported to host H1(A host in CL1 of Datacenter).


While adding H1 to CL1 is succeeded; addition of H2 in CL2 is failing
with following error in vdsm.log.

  Traceback (most recent call last):
 File /usr/share/vdsm/storage/task.py, line 873, in _run
   return fn(*args, **kargs)
 File /usr/share/vdsm/logUtils.py, line 45, in wrapper
   res = f(*args, **kwargs)
 File /usr/share/vdsm/storage/hsm.py, line 1020, in
  connectStoragePool
   spUUID, hostID, msdUUID, masterVersion, domainsMap)
 File /usr/share/vdsm/storage/hsm.py, line 1091, in
  _connectStoragePool
   res = pool.connect(hostID, msdUUID, masterVersion)
 File /usr/share/vdsm/storage/sp.py, line 630, in connect
   self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion)
 File /usr/share/vdsm/storage/sp.py, line 1153, in __rebuild
   self.setMasterDomain(msdUUID, masterVersion)
 File /usr/share/vdsm/storage/sp.py, line 1360, in setMasterDomain
   raise se.StoragePoolMasterNotFound(self.spUUID, msdUUID)
  StoragePoolMasterNotFound: Cannot find master domain:
  'spUUID=a4dfaf64-adfa-4cfa-88d5-986fbdb2b2b2,
  msdUUID=741f7913-09ad-4d96-a225-3bda6d06e042'
  Thread-13::DEBUG::2014-07-30
  15:24:49,780::task::885::TaskManager.Task::(_run)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::Task._run:
  07997682-8d6b-42fd-acb3-1360f14860d6
  ('a4dfaf64-adfa-4cfa-88d5-986fbdb2b2b2', 2,
  '741f7913-09ad-4d96-a225-3bda6d06e042', 1, None) {} failed -
  stopping task
  Thread-13::DEBUG::2014-07-30
  15:24:49,780::task::1211::TaskManager.Task::(stop)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::stopping in state
  preparing (force False)
  Thread-13::DEBUG::2014-07-30
  15:24:49,780::task::990::TaskManager.Task::(_decref)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::ref 1 aborting True
  *Thread-13::INFO::2014-07-30
  15:24:49,780::task::1168::TaskManager.Task::(prepare)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::aborting: Task is
  aborted: 'Cannot find master domain' - code 304*
  Thread-13::DEBUG::2014-07-30
  15:24:49,781::task::1173::TaskManager.Task::(prepare)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::Prepare: aborted:
  Cannot find master domain
  Thread-13::DEBUG::2014-07-30
  15:24:49,781::task::990::TaskManager.Task::(_decref)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::ref 0 aborting True
  Thread-13::DEBUG::2014-07-30
  15:24:49,781::task::925::TaskManager.Task::(_doAbort)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::Task._doAbort: force False
  Thread-13::DEBUG::2014-07-30
  15:24:49,781::resourceManager::977::ResourceManager.Owner::(cancelAll)
  Owner.cancelAll requests {}
  Thread-13::DEBUG::2014-07-30
  15:24:49,781::task::595::TaskManager.Task::(_updateState)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::moving from state
  preparing - state aborting
  Thread-13::DEBUG::2014-07-30
  15:24:49,781::task::550::TaskManager.Task::(__state_aborting)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::_aborting: recover
  policy none
  Thread-13::DEBUG::2014-07-30
  15:24:49,782::task::595::TaskManager.Task::(_updateState)
  Task=`07997682-8d6b-42fd-acb3-1360f14860d6`::moving from state
  aborting - state failed
  Thread-13::DEBUG::2014-07-30
  15:24:49,782::resourceManager::940::ResourceManager.Owner::(releaseAll)
  Owner.releaseAll requests {} resources {}
  Thread-13::DEBUG::2014-07-30
  15:24:49,782::resourceManager::977::ResourceManager.Owner::(cancelAll)
  Owner.cancelAll requests {}
  Thread-13::ERROR::2014-07-30
  15:24:49,782::dispatcher::65::Storage.Dispatcher.Protect::(run)
  {'status': {'message': Cannot find master domain:
  'spUUID=a4dfaf64-adfa-4cfa-88d5-986fbdb2b2b2,
  msdUUID=741f7913-09ad-4d96-a225-3bda6d06e042', 'code': 304}}

_*Please advise if I need to have one Storage Domain per cluster in
given datacenter.*_

Thanks, Santosh.


***Legal Disclaimer***
This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by

Re: [ovirt-users] oVirt June/July 2014 Updates

2014-08-05 Thread Sven Kieske

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 04.08.2014 21:43, Brian Proffitt wrote:
 * Kiril Nesenko educated Jenkins User Conference attendees on how
 to manage oVirt infrastructure with Jenkins 
 http://lanyrd.com/2014/jenkinsconf-israel/sdbqzc/


Any chance to get some slides/video of the talk?

thanks

Sven
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQGcBAEBAgAGBQJT4QonAAoJEAq0kGAWDrqlq0EL/1m8VmjDnNR4Jk43yVi/bJ0M
aXZZSNHasnG1+fTEzLAh+lpGZVLmBrd4tcdqSwEr2s3MLZ/m775N0tbPQtRNEVaz
/CBUJuG09zJZDVCEkxpdNPqVxIgNY1ZxrZtlXl0tvY58wsr9ed0jbQAqwGf6npaX
Apqej9CuPushdkMZt8qVO/J8I24w3Qsj91fW7s25wJ1XKA43dA+oc+j/HI+fiCeM
LVucw3uySN8FjG7fARsA8/0dTwyBYwcHaBBlhk6UpYN4wgD6hfCR44zkojXrJeZ2
KQpvGg67f+ZPq5iZRIohMkKhjuGBTCRHtn5HcOvEZXdGivjnGmiij2T+Lggk+Bem
MtcopRt30jgWgDFcansrISCCTV1GAKF9QibuTinuQLS8+MywkzuU9vDv667ZC7hf
hHvwV2zn6Z+9H2vLpcfUNZGqs9BYqf7PV1SL0zo9M/i2HRUM8rqWpHTYd/9sJck9
Wui0Gu21fj38rFsWMAvTsHKhxCcn5JQgqF6/GVNqpg==
=nrB1
-END PGP SIGNATURE-
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread ybronhei


Hey,

Just noticed something that I forgot about..
before filing new BZ, see in ovirt-host-deploy README.environment [1] 
the section:

VDSM/configOverride(bool) [True]
Override vdsm configuration file.

changing it to false will keep your vdsm.conf file as is after deploying 
the host again (what happens after node upgrade)


[1] 
https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment


please check if that what you meant..

Thanks,
Yaniv Bronhaim.

On 08/05/2014 08:12 AM, Trey Dockendorf wrote:

I'll file BZ.  As far as I can recall this has been an issue since 3.3.x as
I have been using Puppet to modify values and have had to rerun Puppet
after installing a node via GUI and when performing update from GUI.  Given
that it has occurred when VDSM version didn't change on the node it seems
likely to be something being done by Python code that bootstraps a node and
performs the other tasks.  I won't have any systems available to test with
for a few days.  New hardware specifically for our oVirt deployment is on
order so should be able to more thoroughly debug and capture logs at that
time.

Would using vdsm-reg be a better solution for adding new nodes?  I only
tried using vdsm-reg once and it went very poorly...lots of missing
dependencies not pulled in from yum install I had to install manually via
yum.  Then the node was auto added to newest cluster with no ability to
change the cluster.  Be happy to debug that too if there's some docs that
outline the expected behavior.

Using vdsm-reg or something similar seems like a better fit for puppet
deployed nodes, as opposed to requiring GUI steps to add the node.

Thanks
- Trey
On Aug 4, 2014 5:53 AM, ybronhei ybron...@redhat.com wrote:


On 07/31/2014 01:28 AM, Trey Dockendorf wrote:


I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM
installed.  I am using iSER to do iSCSI over RDMA and to make that
work I have to modify /etc/vdsm/vdsm.conf to include the following:

[irs]
iscsi_default_ifaces = iser,default

I've noticed that any time I upgrade a node from the engine web
interface that changes to vdsm.conf are wiped out.  I don't know if
this is being done by the configuration code or by the vdsm package.
Is there a more reliable way to ensure changes to vdsm.conf are NOT
removed automatically?



Hey,

vdsm.conf shouldn't wiped out and shouldn't changed at all during upgrade.
other related conf files (such as libvirtd.conf) might be overrided to keep
defaults configurations for vdsm. but vdsm.conf should persist with user's
modification. from my check, regular yum upgrade doesn't touch vdsm.conf

Douglas can you verify that with node upgrade? might be specific to that
flow..

Trey, can file a bugzilla on that and describe your steps there?

Thanks

Yaniv Bronhaim,



Thanks,
- Trey
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




--
Yaniv Bronhaim.




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

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

Hi,

Do you actually use puppet over ovirt-node?
This is unsupported.

Regards,
Alon

- Original Message -
 From: ybronhei ybron...@redhat.com
 To: Trey Dockendorf treyd...@gmail.com
 Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan 
 Kenigsberg dan...@redhat.com, Itamar
 Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon 
 Bar-Lev alo...@redhat.com
 Sent: Tuesday, August 5, 2014 8:32:04 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options
 
 Hey,
 
 Just noticed something that I forgot about..
 before filing new BZ, see in ovirt-host-deploy README.environment [1]
 the section:
 VDSM/configOverride(bool) [True]
  Override vdsm configuration file.
 
 changing it to false will keep your vdsm.conf file as is after deploying
 the host again (what happens after node upgrade)
 
 [1]
 https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment
 
 please check if that what you meant..
 
 Thanks,
 Yaniv Bronhaim.
 
 On 08/05/2014 08:12 AM, Trey Dockendorf wrote:
  I'll file BZ.  As far as I can recall this has been an issue since 3.3.x as
  I have been using Puppet to modify values and have had to rerun Puppet
  after installing a node via GUI and when performing update from GUI.  Given
  that it has occurred when VDSM version didn't change on the node it seems
  likely to be something being done by Python code that bootstraps a node and
  performs the other tasks.  I won't have any systems available to test with
  for a few days.  New hardware specifically for our oVirt deployment is on
  order so should be able to more thoroughly debug and capture logs at that
  time.
 
  Would using vdsm-reg be a better solution for adding new nodes?  I only
  tried using vdsm-reg once and it went very poorly...lots of missing
  dependencies not pulled in from yum install I had to install manually via
  yum.  Then the node was auto added to newest cluster with no ability to
  change the cluster.  Be happy to debug that too if there's some docs that
  outline the expected behavior.
 
  Using vdsm-reg or something similar seems like a better fit for puppet
  deployed nodes, as opposed to requiring GUI steps to add the node.
 
  Thanks
  - Trey
  On Aug 4, 2014 5:53 AM, ybronhei ybron...@redhat.com wrote:
 
  On 07/31/2014 01:28 AM, Trey Dockendorf wrote:
 
  I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM
  installed.  I am using iSER to do iSCSI over RDMA and to make that
  work I have to modify /etc/vdsm/vdsm.conf to include the following:
 
  [irs]
  iscsi_default_ifaces = iser,default
 
  I've noticed that any time I upgrade a node from the engine web
  interface that changes to vdsm.conf are wiped out.  I don't know if
  this is being done by the configuration code or by the vdsm package.
  Is there a more reliable way to ensure changes to vdsm.conf are NOT
  removed automatically?
 
 
  Hey,
 
  vdsm.conf shouldn't wiped out and shouldn't changed at all during upgrade.
  other related conf files (such as libvirtd.conf) might be overrided to
  keep
  defaults configurations for vdsm. but vdsm.conf should persist with user's
  modification. from my check, regular yum upgrade doesn't touch vdsm.conf
 
  Douglas can you verify that with node upgrade? might be specific to that
  flow..
 
  Trey, can file a bugzilla on that and describe your steps there?
 
  Thanks
 
  Yaniv Bronhaim,
 
 
  Thanks,
  - Trey
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
 
  --
  Yaniv Bronhaim.
 
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
 Hey,

 Just noticed something that I forgot about..
 before filing new BZ, see in ovirt-host-deploy README.environment [1] the
 section:
 VDSM/configOverride(bool) [True]
 Override vdsm configuration file.

 changing it to false will keep your vdsm.conf file as is after deploying the
 host again (what happens after node upgrade)

 [1]
 https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

 please check if that what you meant..

 Thanks,
 Yaniv Bronhaim.


I was unaware of that package.  I will check that out as that seems to
be what I am looking for.

I have not filed this in BZ and will hold off pending
ovirt-host-deploy.  If you feel a BZ is still necessary then please do
file one and I would be happy to provide input if it would help.

Right now this is my workflow.

1. Foreman provisions bare-metal server with CentOS 6.5
2. Once provisioned and system rebooted Puppet applies puppet-ovirt
[1] module that adds the necessary yum repos, and installs packages.
Part of my Puppet deployment is basic things like sudo management
(vdsm's sudo is account for), sssd configuration, and other aspects
that are needed by every system in my infrastructure.  Part of the
ovirt::node Puppet class is managing vdsm.conf, and in my case that
means ensuring iSER is enabled for iSCSI over IB.
3. Once host is online and has had the full Puppet catalog applied I
log into ovirt-engine web interface and add those host (pulling it's
data via the Foreman provider).

What I've noticed is that after step #3, after a host is added by
ovirt-engine, the vdsm.conf file is reset to default and I have to
reapply Puppet before it can be used as the one of my Data Storage
Domains requires iSER (not available over TCP).

What would be the workflow using ovirt-host-deploy?  Thus far I've had
to piece together my workflow based on the documentation and filling
in blanks where possible since I do require customizations to
vdsm.conf and the documented workflow of adding a host via web UI does
not allow for such customization.

Thanks,
- Trey

[1] - https://github.com/treydock/puppet-ovirt (README not fully
updated as still working out how to use Puppet with oVirt)


 On 08/05/2014 08:12 AM, Trey Dockendorf wrote:

 I'll file BZ.  As far as I can recall this has been an issue since 3.3.x
 as
 I have been using Puppet to modify values and have had to rerun Puppet
 after installing a node via GUI and when performing update from GUI.
 Given
 that it has occurred when VDSM version didn't change on the node it seems
 likely to be something being done by Python code that bootstraps a node
 and
 performs the other tasks.  I won't have any systems available to test with
 for a few days.  New hardware specifically for our oVirt deployment is on
 order so should be able to more thoroughly debug and capture logs at that
 time.

 Would using vdsm-reg be a better solution for adding new nodes?  I only
 tried using vdsm-reg once and it went very poorly...lots of missing
 dependencies not pulled in from yum install I had to install manually via
 yum.  Then the node was auto added to newest cluster with no ability to
 change the cluster.  Be happy to debug that too if there's some docs that
 outline the expected behavior.

 Using vdsm-reg or something similar seems like a better fit for puppet
 deployed nodes, as opposed to requiring GUI steps to add the node.

 Thanks
 - Trey
 On Aug 4, 2014 5:53 AM, ybronhei ybron...@redhat.com wrote:

 On 07/31/2014 01:28 AM, Trey Dockendorf wrote:

 I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM
 installed.  I am using iSER to do iSCSI over RDMA and to make that
 work I have to modify /etc/vdsm/vdsm.conf to include the following:

 [irs]
 iscsi_default_ifaces = iser,default

 I've noticed that any time I upgrade a node from the engine web
 interface that changes to vdsm.conf are wiped out.  I don't know if
 this is being done by the configuration code or by the vdsm package.
 Is there a more reliable way to ensure changes to vdsm.conf are NOT
 removed automatically?


 Hey,

 vdsm.conf shouldn't wiped out and shouldn't changed at all during
 upgrade.
 other related conf files (such as libvirtd.conf) might be overrided to
 keep
 defaults configurations for vdsm. but vdsm.conf should persist with
 user's
 modification. from my check, regular yum upgrade doesn't touch vdsm.conf

 Douglas can you verify that with node upgrade? might be specific to that
 flow..

 Trey, can file a bugzilla on that and describe your steps there?

 Thanks

 Yaniv Bronhaim,


 Thanks,
 - Trey
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users



 --
 Yaniv Bronhaim.



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

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

- Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: ybronhei ybron...@redhat.com
 Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan 
 Kenigsberg dan...@redhat.com, Itamar
 Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon 
 Bar-Lev alo...@redhat.com
 Sent: Tuesday, August 5, 2014 9:36:24 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
  Hey,

  Just noticed something that I forgot about..
  before filing new BZ, see in ovirt-host-deploy README.environment [1] the
  section:
  VDSM/configOverride(bool) [True]
  Override vdsm configuration file.

  changing it to false will keep your vdsm.conf file as is after deploying
  the
  host again (what happens after node upgrade)

  [1]
  https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

  please check if that what you meant..

  Thanks,
  Yaniv Bronhaim.

 I was unaware of that package.  I will check that out as that seems to
 be what I am looking for.

 I have not filed this in BZ and will hold off pending
 ovirt-host-deploy.  If you feel a BZ is still necessary then please do
 file one and I would be happy to provide input if it would help.

 Right now this is my workflow.

 1. Foreman provisions bare-metal server with CentOS 6.5
 2. Once provisioned and system rebooted Puppet applies puppet-ovirt
 [1] module that adds the necessary yum repos

and should stop here..

 , and installs packages.
 Part of my Puppet deployment is basic things like sudo management
 (vdsm's sudo is account for), sssd configuration, and other aspects
 that are needed by every system in my infrastructure.  Part of the
 ovirt::node Puppet class is managing vdsm.conf, and in my case that
 means ensuring iSER is enabled for iSCSI over IB.

you can create a file /etc/ovirt-host-deploy.conf.d/40-xxx.conf
---
VDSM_CONFIG/section/key=str:content
---

this will create a proper vdsm.conf when host-deploy is initiated.

you should now use the rest api to initiate host-deploy.

 3. Once host is online and has had the full Puppet catalog applied I
 log into ovirt-engine web interface and add those host (pulling it's
 data via the Foreman provider).

right, but you should let this process install packages and manage 
configuration.

 What I've noticed is that after step #3, after a host is added by
 ovirt-engine, the vdsm.conf file is reset to default and I have to
 reapply Puppet before it can be used as the one of my Data Storage
 Domains requires iSER (not available over TCP).

right, see above.

 What would be the workflow using ovirt-host-deploy?  Thus far I've had
 to piece together my workflow based on the documentation and filling
 in blanks where possible since I do require customizations to
 vdsm.conf and the documented workflow of adding a host via web UI does
 not allow for such customization.

 Thanks,
 - Trey

 [1] - https://github.com/treydock/puppet-ovirt (README not fully
 updated as still working out how to use Puppet with oVirt)

  On 08/05/2014 08:12 AM, Trey Dockendorf wrote:

  I'll file BZ.  As far as I can recall this has been an issue since 3.3.x
  as
  I have been using Puppet to modify values and have had to rerun Puppet
  after installing a node via GUI and when performing update from GUI.
  Given
  that it has occurred when VDSM version didn't change on the node it seems
  likely to be something being done by Python code that bootstraps a node
  and
  performs the other tasks.  I won't have any systems available to test with
  for a few days.  New hardware specifically for our oVirt deployment is on
  order so should be able to more thoroughly debug and capture logs at that
  time.

  Would using vdsm-reg be a better solution for adding new nodes?  I only
  tried using vdsm-reg once and it went very poorly...lots of missing
  dependencies not pulled in from yum install I had to install manually via
  yum.  Then the node was auto added to newest cluster with no ability to
  change the cluster.  Be happy to debug that too if there's some docs that
  outline the expected behavior.

  Using vdsm-reg or something similar seems like a better fit for puppet
  deployed nodes, as opposed to requiring GUI steps to add the node.

  Thanks
  - Trey
  On Aug 4, 2014 5:53 AM, ybronhei ybron...@redhat.com wrote:

  On 07/31/2014 01:28 AM, Trey Dockendorf wrote:

  I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM
  installed.  I am using iSER to do iSCSI over RDMA and to make that
  work I have to modify /etc/vdsm/vdsm.conf to include the following:

  [irs]
  iscsi_default_ifaces = iser,default

  I've noticed that any time I upgrade a node from the engine web
  interface that changes to vdsm.conf are wiped out.  I don't know if
  this is being done by the configuration code or by the vdsm package.
  Is there a more reliable way to ensure

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

On Tue, Aug 5, 2014 at 12:37 PM, Alon Bar-Lev alo...@redhat.com wrote:
 Hi,

 Do you actually use puppet over ovirt-node?
 This is unsupported.

 Regards,
 Alon


I use Puppet to configure everything on the system and some of those
things conflict with changes made by ovirt-engine when adding a node
so I've moved to managing those changes in an ovirt Puppet module.

When you refer to ovirt-node your refering to the pre-built ISO
images?  AFAIK the ovirt-node is not an option for me as I use
Infiniband to do all storage connections.  Currently NFS is done using
IPoIB (NFS over RDMA was crashing so I am not pursuing at the moment)
and iSCSI is done using iSER.  At some point in time I'd like to use
IB interfaces in my guests utilizing SR-IOV which my Mellanox cards
support, but I'm postponing that project till after our HPC cluster's
upgraded :)

Right now the Puppet module does the following:

* Configures firewall rules just like what is done by ovirt (with
exception of a few not supported by puppetlabs-firewall, so I override
global directive that purges unknown firewall rules)
** This is necessary as I have to add other Firewall rules, such as Zabbix
* Exports /etc/hosts entry for the node that is collected by
ovirt-engine host so that if DNS goes down ovirt-engine does not lose
access to ovirtmgmt interfaces
* Install yum repos for ovirt
* install vdsm
* ensure vdsm.conf exists
* Populates /etc/vdsm/vdsm.id (IIRC a bug in previous ovirt required this)
* Ensures vdsmd is running and will start at boot
* Ensures vdsm sudo rules are present.
* Manages default vdsm.conf configurations as a Puppet type,
vdsm_config, rather than managing file contents via template (allows
for purging unmanaged entries also)

A lot of the above is handled by ovirt already, but in the past
customizations were not possible (firewall rules, vdsm.conf entries,
etc) so if I was going to have to manage those separately I wanted
them in Puppet :)

Now that I'm aware of ovirt-host-deploy and have seen the potential
of using vdsm-reg in Puppet, I'm curious what is the right way to
automate node deployment's in oVirt. Ideally I could still use Puppet
to configure the method or fill in the gaps for customizations that
are needed (ie enabling iSER).

I'd be glad to know what the recommended method for automating ovirt
would be, and would be happy to refactor my module in hopes it would
offer other Puppet users a quick-start way to deploy oVirt while still
doing things the ovirt way.

If the right way is using the ovirt-node images then I'd like to know
what customizations are possible on those images and so on.  oVirt is
moving very rapidly and despite using ovirt for a long time I'm still
learning new things about it almost daily, so forgive any of my
assumptions above that may be wrong :).

Thanks,
- Trey

 - Original Message -
 From: ybronhei ybron...@redhat.com
 To: Trey Dockendorf treyd...@gmail.com
 Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan 
 Kenigsberg dan...@redhat.com, Itamar
 Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon 
 Bar-Lev alo...@redhat.com
 Sent: Tuesday, August 5, 2014 8:32:04 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Hey,

 Just noticed something that I forgot about..
 before filing new BZ, see in ovirt-host-deploy README.environment [1]
 the section:
 VDSM/configOverride(bool) [True]
  Override vdsm configuration file.

 changing it to false will keep your vdsm.conf file as is after deploying
 the host again (what happens after node upgrade)

 [1]
 https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

 please check if that what you meant..

 Thanks,
 Yaniv Bronhaim.

 On 08/05/2014 08:12 AM, Trey Dockendorf wrote:
  I'll file BZ.  As far as I can recall this has been an issue since 3.3.x as
  I have been using Puppet to modify values and have had to rerun Puppet
  after installing a node via GUI and when performing update from GUI.  Given
  that it has occurred when VDSM version didn't change on the node it seems
  likely to be something being done by Python code that bootstraps a node and
  performs the other tasks.  I won't have any systems available to test with
  for a few days.  New hardware specifically for our oVirt deployment is on
  order so should be able to more thoroughly debug and capture logs at that
  time.
 
  Would using vdsm-reg be a better solution for adding new nodes?  I only
  tried using vdsm-reg once and it went very poorly...lots of missing
  dependencies not pulled in from yum install I had to install manually via
  yum.  Then the node was auto added to newest cluster with no ability to
  change the cluster.  Be happy to debug that too if there's some docs that
  outline the expected behavior.
 
  Using vdsm-reg or something similar seems like a better fit for puppet
  deployed nodes, as opposed to requiring GUI steps to add the node.
 
  Thanks
  - Trey
  On

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

- Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan 
 Kenigsberg dan...@redhat.com, Itamar
 Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, 
 ybronhei ybron...@redhat.com
 Sent: Tuesday, August 5, 2014 9:50:04 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 On Tue, Aug 5, 2014 at 12:37 PM, Alon Bar-Lev alo...@redhat.com wrote:
  Hi,

  Do you actually use puppet over ovirt-node?
  This is unsupported.

  Regards,
  Alon

 I use Puppet to configure everything on the system and some of those
 things conflict with changes made by ovirt-engine when adding a node
 so I've moved to managing those changes in an ovirt Puppet module.

 When you refer to ovirt-node your refering to the pre-built ISO
 images?  AFAIK the ovirt-node is not an option for me as I use
 Infiniband to do all storage connections.  Currently NFS is done using
 IPoIB (NFS over RDMA was crashing so I am not pursuing at the moment)
 and iSCSI is done using iSER.  At some point in time I'd like to use
 IB interfaces in my guests utilizing SR-IOV which my Mellanox cards
 support, but I'm postponing that project till after our HPC cluster's
 upgraded :)

 Right now the Puppet module does the following:

 * Configures firewall rules just like what is done by ovirt (with
 exception of a few not supported by puppetlabs-firewall, so I override
 global directive that purges unknown firewall rules)

this should be done at engine side, using engine-config, seek IPTablesConfig or 
IPTablesConfigSiteCustom in 3.5.

 ** This is necessary as I have to add other Firewall rules, such as Zabbix
 * Exports /etc/hosts entry for the node that is collected by
 ovirt-engine host so that if DNS goes down ovirt-engine does not lose
 access to ovirtmgmt interfaces

why not just have a backup for dns?

 * Install yum repos for ovirt

this should not be done within ovirt-node.

 * install vdsm

this should be done by host-deploy.

 * ensure vdsm.conf exists
 * Populates /etc/vdsm/vdsm.id (IIRC a bug in previous ovirt required this)

why? you machine should have valid bios uuid.

 * Ensures vdsmd is running and will start at boot
 * Ensures vdsm sudo rules are present.
 * Manages default vdsm.conf configurations as a Puppet type,
 vdsm_config, rather than managing file contents via template (allows
 for purging unmanaged entries also)

the above should be done via host-deploy.

 A lot of the above is handled by ovirt already, but in the past
 customizations were not possible (firewall rules, vdsm.conf entries,
 etc) so if I was going to have to manage those separately I wanted
 them in Puppet :)

 Now that I'm aware of ovirt-host-deploy and have seen the potential
 of using vdsm-reg in Puppet, I'm curious what is the right way to
 automate node deployment's in oVirt. Ideally I could still use Puppet
 to configure the method or fill in the gaps for customizations that
 are needed (ie enabling iSER).

 I'd be glad to know what the recommended method for automating ovirt
 would be, and would be happy to refactor my module in hopes it would
 offer other Puppet users a quick-start way to deploy oVirt while still
 doing things the ovirt way.

 If the right way is using the ovirt-node images then I'd like to know
 what customizations are possible on those images and so on.  oVirt is
 moving very rapidly and despite using ovirt for a long time I'm still
 learning new things about it almost daily, so forgive any of my
 assumptions above that may be wrong :).

ovirt-node is not flexible as standard host, if you require sssd and misc 
packages I suggest you stick with generic host.

 Thanks,
 - Trey

  - Original Message -
  From: ybronhei ybron...@redhat.com
  To: Trey Dockendorf treyd...@gmail.com
  Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar
  Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon
  Bar-Lev alo...@redhat.com
  Sent: Tuesday, August 5, 2014 8:32:04 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options

  Hey,

  Just noticed something that I forgot about..
  before filing new BZ, see in ovirt-host-deploy README.environment [1]
  the section:
  VDSM/configOverride(bool) [True]
   Override vdsm configuration file.

  changing it to false will keep your vdsm.conf file as is after deploying
  the host again (what happens after node upgrade)

  [1]
  https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

  please check if that what you meant..

  Thanks,
  Yaniv Bronhaim.

  On 08/05/2014 08:12 AM, Trey Dockendorf wrote:
   I'll file BZ.  As far as I can recall this has been an issue since 3.3.x
   as
   I have been using Puppet to modify values and have had to rerun Puppet
   after installing a node via GUI and when

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

Ah, thank you for the input!  Just so I'm not spending time
implementing the wrong changes, let me confirm I understand your
comments.

1) Deploy host with Foreman
2) Apply Puppet catalog including ovirt Puppet module
3) Initiate host-deploy via rest API

In the ovirt module the following takes place:

2a) Add yum repos
2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf

For #2b I have a few questions

* The name of the .conf file is simply for sorting and
labeling/organization, it has not functional impact on what those
overrides apply to?
* That file is managed on the ovirt-engine server, not the actual nodes?
* Is there any way to apply overrides to specific hosts?  For example
if I have some hosts that require a config and others that don't, how
would I separate those *.conf files?  This is more theoretical as
right now my setup is common across all nodes.

For #3...the implementation of API calls from within Puppet is a
challenge and one I can't tackle yet, but definitely will make it a
goal for the future.  In the mean time, what's the manual way to
initiate host-deploy?  Is there a CLI command that would have the same
result as an API call or is the recommended way to perform the API
call manually (ie curl)?

Thanks!
- Trey

On Tue, Aug 5, 2014 at 1:45 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: ybronhei ybron...@redhat.com
 Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan 
 Kenigsberg dan...@redhat.com, Itamar
 Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon 
 Bar-Lev alo...@redhat.com
 Sent: Tuesday, August 5, 2014 9:36:24 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
  Hey,
 
  Just noticed something that I forgot about..
  before filing new BZ, see in ovirt-host-deploy README.environment [1] the
  section:
  VDSM/configOverride(bool) [True]
  Override vdsm configuration file.
 
  changing it to false will keep your vdsm.conf file as is after deploying
  the
  host again (what happens after node upgrade)
 
  [1]
  https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment
 
  please check if that what you meant..
 
  Thanks,
  Yaniv Bronhaim.
 

 I was unaware of that package.  I will check that out as that seems to
 be what I am looking for.

 I have not filed this in BZ and will hold off pending
 ovirt-host-deploy.  If you feel a BZ is still necessary then please do
 file one and I would be happy to provide input if it would help.

 Right now this is my workflow.

 1. Foreman provisions bare-metal server with CentOS 6.5
 2. Once provisioned and system rebooted Puppet applies puppet-ovirt
 [1] module that adds the necessary yum repos

 and should stop here..

 , and installs packages.
 Part of my Puppet deployment is basic things like sudo management
 (vdsm's sudo is account for), sssd configuration, and other aspects
 that are needed by every system in my infrastructure.  Part of the
 ovirt::node Puppet class is managing vdsm.conf, and in my case that
 means ensuring iSER is enabled for iSCSI over IB.

 you can create a file /etc/ovirt-host-deploy.conf.d/40-xxx.conf
 ---
 VDSM_CONFIG/section/key=str:content
 ---

 this will create a proper vdsm.conf when host-deploy is initiated.

 you should now use the rest api to initiate host-deploy.

 3. Once host is online and has had the full Puppet catalog applied I
 log into ovirt-engine web interface and add those host (pulling it's
 data via the Foreman provider).

 right, but you should let this process install packages and manage 
 configuration.

 What I've noticed is that after step #3, after a host is added by
 ovirt-engine, the vdsm.conf file is reset to default and I have to
 reapply Puppet before it can be used as the one of my Data Storage
 Domains requires iSER (not available over TCP).

 right, see above.

 What would be the workflow using ovirt-host-deploy?  Thus far I've had
 to piece together my workflow based on the documentation and filling
 in blanks where possible since I do require customizations to
 vdsm.conf and the documented workflow of adding a host via web UI does
 not allow for such customization.

 Thanks,
 - Trey

 [1] - https://github.com/treydock/puppet-ovirt (README not fully
 updated as still working out how to use Puppet with oVirt)

 
  On 08/05/2014 08:12 AM, Trey Dockendorf wrote:
 
  I'll file BZ.  As far as I can recall this has been an issue since 3.3.x
  as
  I have been using Puppet to modify values and have had to rerun Puppet
  after installing a node via GUI and when performing update from GUI.
  Given
  that it has occurred when VDSM version didn't change on the node it seems
  likely to be something being done by Python code that bootstraps a node
  and
  performs the other tasks.  I won't have any systems available to test with
  for a few days.  New

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Joop

On 5-8-2014 20:54, Alon Bar-Lev wrote:



 * ensure vdsm.conf exists
 * Populates /etc/vdsm/vdsm.id (IIRC a bug in previous ovirt required this)
 why? you machine should have valid bios uuid.

There are manufactures that don't set a unique bios uuid. Supermicro is
one of them. I had a RFE but that has been closed but I feel that it
should be reopened and implemented. The change is minimal and guarantees
that there is a unique uuid.

Regards,

Joop

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

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

- Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com
 Sent: Tuesday, August 5, 2014 10:01:14 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Ah, thank you for the input!  Just so I'm not spending time
 implementing the wrong changes, let me confirm I understand your
 comments.

 1) Deploy host with Foreman
 2) Apply Puppet catalog including ovirt Puppet module
 3) Initiate host-deploy via rest API

 In the ovirt module the following takes place:

 2a) Add yum repos
 2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf

you can have any # of files with any prefix :))

 For #2b I have a few questions

 * The name of the .conf file is simply for sorting and
 labeling/organization, it has not functional impact on what those
 overrides apply to?

right.

 * That file is managed on the ovirt-engine server, not the actual nodes?

currently on the host, in future we will provide a method to add this to engine 
database[1]

[1] http://gerrit.ovirt.org/#/c/27064/

 * Is there any way to apply overrides to specific hosts?  For example
 if I have some hosts that require a config and others that don't, how
 would I separate those *.conf files?  This is more theoretical as
 right now my setup is common across all nodes.

the poppet module can put whatever required on each host.

 For #3...the implementation of API calls from within Puppet is a
 challenge and one I can't tackle yet, but definitely will make it a
 goal for the future.  In the mean time, what's the manual way to
 initiate host-deploy?  Is there a CLI command that would have the same
 result as an API call or is the recommended way to perform the API
 call manually (ie curl)?

well, you can register host using the following protocol[1], but it is 
difficult to do this securely, what you actually need is to establish ssh trust 
for root with engine key then register.

you can also use the register command using curl by something like (I have not 
checked):
https://admin%40internal:password@engine/ovirt-engine/api/hosts
---
?xml version=1.0 encoding=UTF-8 standalone=yes?
host
  namehost1/name
  addressdns/address
  ssh
authentication_methodpublickey/authentication_method
  /ssh
  cluster id=cluster-uuid/
/host
---

you can also use the ovirt-engine-sdk-python package:
---
import ovirtsdk.api
import ovirtsdk.xml

sdk = ovirtsdk.api.API(
url='https://host/ovirt-engine/api',
username='admin@internal',
password='password',
insecure=True,
)
sdk.hosts.add(
ovirtsdk.xml.params.Host(
name='host1',
address='host1',
cluster=engine_api.clusters.get(
'cluster'
),
ssh=self._ovirtsdk_xml.params.SSH(
authentication_method='publickey',
),
)
)
---

[1] http://www.ovirt.org/Features/HostDeployProtocol

 Thanks!
 - Trey

 On Tue, Aug 5, 2014 at 1:45 PM, Alon Bar-Lev alo...@redhat.com wrote:

  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: ybronhei ybron...@redhat.com
  Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar
  Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon
  Bar-Lev alo...@redhat.com
  Sent: Tuesday, August 5, 2014 9:36:24 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options

  On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
   Hey,

   Just noticed something that I forgot about..
   before filing new BZ, see in ovirt-host-deploy README.environment [1]
   the
   section:
   VDSM/configOverride(bool) [True]
   Override vdsm configuration file.

   changing it to false will keep your vdsm.conf file as is after deploying
   the
   host again (what happens after node upgrade)

   [1]
   https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

   please check if that what you meant..

   Thanks,
   Yaniv Bronhaim.

  I was unaware of that package.  I will check that out as that seems to
  be what I am looking for.

  I have not filed this in BZ and will hold off pending
  ovirt-host-deploy.  If you feel a BZ is still necessary then please do
  file one and I would be happy to provide input if it would help.

  Right now this is my workflow.

  1. Foreman provisions bare-metal server with CentOS 6.5
  2. Once provisioned and system rebooted Puppet applies puppet-ovirt
  [1] module that adds the necessary yum repos

  and should stop here..

  , and installs packages.
  Part of my Puppet deployment is

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

Excellent, so installing 'ovirt-host-deploy' on each node then
configuring the /etc/ovirt-host-deploy.conf.d files seems very
automate-able, will see how it works in practice.

Regarding the actual host registration and getting the host added to
ovirt-engine, are there other methods besides the API and the sdk?
Would it be possible to configure the necessary
ovirt-host-deploy.conf.d files then execute ovirt-host-deploy?  I
notice that running 'ovirt-host-deploy' wants to make whatever host
executes it a ovir hypervisor but haven't yet run it all the way
through as no server to test with at this time.  There seems to be no
--help or similar command line argument.

I'm sure this will all be more clear once I attempt the steps and run
through the motions.  Will try to find a system to test on so I'm
ready once our new servers arrive.

Thanks,
- Trey

On Tue, Aug 5, 2014 at 2:23 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com
 Sent: Tuesday, August 5, 2014 10:01:14 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Ah, thank you for the input!  Just so I'm not spending time
 implementing the wrong changes, let me confirm I understand your
 comments.

 1) Deploy host with Foreman
 2) Apply Puppet catalog including ovirt Puppet module
 3) Initiate host-deploy via rest API

 In the ovirt module the following takes place:

 2a) Add yum repos
 2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf


 you can have any # of files with any prefix :))

 For #2b I have a few questions

 * The name of the .conf file is simply for sorting and
 labeling/organization, it has not functional impact on what those
 overrides apply to?

 right.

 * That file is managed on the ovirt-engine server, not the actual nodes?

 currently on the host, in future we will provide a method to add this to 
 engine database[1]

 [1] http://gerrit.ovirt.org/#/c/27064/

 * Is there any way to apply overrides to specific hosts?  For example
 if I have some hosts that require a config and others that don't, how
 would I separate those *.conf files?  This is more theoretical as
 right now my setup is common across all nodes.

 the poppet module can put whatever required on each host.

 For #3...the implementation of API calls from within Puppet is a
 challenge and one I can't tackle yet, but definitely will make it a
 goal for the future.  In the mean time, what's the manual way to
 initiate host-deploy?  Is there a CLI command that would have the same
 result as an API call or is the recommended way to perform the API
 call manually (ie curl)?

 well, you can register host using the following protocol[1], but it is 
 difficult to do this securely, what you actually need is to establish ssh 
 trust for root with engine key then register.

 you can also use the register command using curl by something like (I have 
 not checked):
 https://admin%40internal:password@engine/ovirt-engine/api/hosts
 ---
 ?xml version=1.0 encoding=UTF-8 standalone=yes?
 host
   namehost1/name
   addressdns/address
   ssh
 authentication_methodpublickey/authentication_method
   /ssh
   cluster id=cluster-uuid/
 /host
 ---

 you can also use the ovirt-engine-sdk-python package:
 ---
 import ovirtsdk.api
 import ovirtsdk.xml

 sdk = ovirtsdk.api.API(
 url='https://host/ovirt-engine/api',
 username='admin@internal',
 password='password',
 insecure=True,
 )
 sdk.hosts.add(
 ovirtsdk.xml.params.Host(
 name='host1',
 address='host1',
 cluster=engine_api.clusters.get(
 'cluster'
 ),
 ssh=self._ovirtsdk_xml.params.SSH(
 authentication_method='publickey',
 ),
 )
 )
 ---

 [1] http://www.ovirt.org/Features/HostDeployProtocol


 Thanks!
 - Trey

 On Tue, Aug 5, 2014 at 1:45 PM, Alon Bar-Lev alo...@redhat.com wrote:
 
 
  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: ybronhei ybron...@redhat.com
  Cc: users users@ovirt.org, Fabian Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar
  Heim ih...@redhat.com, Douglas Landgraf dougsl...@redhat.com, Alon
  Bar-Lev alo...@redhat.com
  Sent: Tuesday, August 5, 2014 9:36:24 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options
 
  On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:
   Hey,
  
   Just noticed something that I forgot about..
   before filing new BZ, see in ovirt-host-deploy README.environment [1]
   the
   section:

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

- Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com, Oved
 Ourfali ov...@redhat.com
 Sent: Tuesday, August 5, 2014 10:45:12 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Excellent, so installing 'ovirt-host-deploy' on each node then
 configuring the /etc/ovirt-host-deploy.conf.d files seems very
 automate-able, will see how it works in practice.

you do not need to install the ovirt-host-deploy, just create the files.

 Regarding the actual host registration and getting the host added to
 ovirt-engine, are there other methods besides the API and the sdk?
 Would it be possible to configure the necessary
 ovirt-host-deploy.conf.d files then execute ovirt-host-deploy?  I
 notice that running 'ovirt-host-deploy' wants to make whatever host
 executes it a ovir hypervisor but haven't yet run it all the way
 through as no server to test with at this time.  There seems to be no
 --help or similar command line argument.

you should not run host-deploy directly, but via the engine's process, either 
registration or add host as I replied previously.

when base system is ready, you issue add host via api of engine or via ui, the 
other alternative is to register the host host the host-deploy protocol, and 
approve the host via api of engine or via ui.

 I'm sure this will all be more clear once I attempt the steps and run
 through the motions.  Will try to find a system to test on so I'm
 ready once our new servers arrive.

 Thanks,
 - Trey

 On Tue, Aug 5, 2014 at 2:23 PM, Alon Bar-Lev alo...@redhat.com wrote:

  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: Alon Bar-Lev alo...@redhat.com
  Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian
  Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com,
  Douglas Landgraf dougsl...@redhat.com
  Sent: Tuesday, August 5, 2014 10:01:14 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options

  Ah, thank you for the input!  Just so I'm not spending time
  implementing the wrong changes, let me confirm I understand your
  comments.

  1) Deploy host with Foreman
  2) Apply Puppet catalog including ovirt Puppet module
  3) Initiate host-deploy via rest API

  In the ovirt module the following takes place:

  2a) Add yum repos
  2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf

  you can have any # of files with any prefix :))

  For #2b I have a few questions

  * The name of the .conf file is simply for sorting and
  labeling/organization, it has not functional impact on what those
  overrides apply to?

  right.

  * That file is managed on the ovirt-engine server, not the actual nodes?

  currently on the host, in future we will provide a method to add this to
  engine database[1]

  [1] http://gerrit.ovirt.org/#/c/27064/

  * Is there any way to apply overrides to specific hosts?  For example
  if I have some hosts that require a config and others that don't, how
  would I separate those *.conf files?  This is more theoretical as
  right now my setup is common across all nodes.

  the poppet module can put whatever required on each host.

  For #3...the implementation of API calls from within Puppet is a
  challenge and one I can't tackle yet, but definitely will make it a
  goal for the future.  In the mean time, what's the manual way to
  initiate host-deploy?  Is there a CLI command that would have the same
  result as an API call or is the recommended way to perform the API
  call manually (ie curl)?

  well, you can register host using the following protocol[1], but it is
  difficult to do this securely, what you actually need is to establish ssh
  trust for root with engine key then register.

  you can also use the register command using curl by something like (I have
  not checked):
  https://admin%40internal:password@engine/ovirt-engine/api/hosts
  ---
  ?xml version=1.0 encoding=UTF-8 standalone=yes?
  host
namehost1/name
addressdns/address
ssh
  authentication_methodpublickey/authentication_method
/ssh
cluster id=cluster-uuid/
  /host
  ---

  you can also use the ovirt-engine-sdk-python package:
  ---
  import ovirtsdk.api
  import ovirtsdk.xml

  sdk = ovirtsdk.api.API(
  url='https://host/ovirt-engine/api',
  username='admin@internal',
  password='password',
  insecure=True,
  )
  sdk.hosts.add(
  ovirtsdk.xml.params.Host(
  name='host1',
  address='host1',
  cluster=engine_api.clusters.get(
  'cluster'

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

Thanks for clarifying, makes sense now.

The public key trust needed for registration, is that the same key
that would be used when adding host via UI?

Any examples of how to use the HostDeployProtocol [1]?  I like the
idea of using registration but haven't the slightest idea how to
implement what's described in the docs [1].  I do recall seeing an
article posted (searching email and can't find) that had a nice
walk-through of how to use the oVirt API using browser tools.  I'm
unsure if this HostDeployProtocol would be done that way or via some
other method.

Thanks,
- Trey


[1] http://www.ovirt.org/Features/HostDeployProtocol

On Tue, Aug 5, 2014 at 3:01 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Trey Dockendorf treyd...@gmail.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian 
 Deutsch fabi...@redhat.com, Dan
 Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas 
 Landgraf dougsl...@redhat.com, Oved
 Ourfali ov...@redhat.com
 Sent: Tuesday, August 5, 2014 10:45:12 PM
 Subject: Re: [ovirt-users] Proper way to change and persist vdsm 
 configuration options

 Excellent, so installing 'ovirt-host-deploy' on each node then
 configuring the /etc/ovirt-host-deploy.conf.d files seems very
 automate-able, will see how it works in practice.

 you do not need to install the ovirt-host-deploy, just create the files.

 Regarding the actual host registration and getting the host added to
 ovirt-engine, are there other methods besides the API and the sdk?
 Would it be possible to configure the necessary
 ovirt-host-deploy.conf.d files then execute ovirt-host-deploy?  I
 notice that running 'ovirt-host-deploy' wants to make whatever host
 executes it a ovir hypervisor but haven't yet run it all the way
 through as no server to test with at this time.  There seems to be no
 --help or similar command line argument.

 you should not run host-deploy directly, but via the engine's process, either 
 registration or add host as I replied previously.

 when base system is ready, you issue add host via api of engine or via ui, 
 the other alternative is to register the host host the host-deploy protocol, 
 and approve the host via api of engine or via ui.

 I'm sure this will all be more clear once I attempt the steps and run
 through the motions.  Will try to find a system to test on so I'm
 ready once our new servers arrive.

 Thanks,
 - Trey

 On Tue, Aug 5, 2014 at 2:23 PM, Alon Bar-Lev alo...@redhat.com wrote:
 
 
  - Original Message -
  From: Trey Dockendorf treyd...@gmail.com
  To: Alon Bar-Lev alo...@redhat.com
  Cc: ybronhei ybron...@redhat.com, users users@ovirt.org, Fabian
  Deutsch fabi...@redhat.com, Dan
  Kenigsberg dan...@redhat.com, Itamar Heim ih...@redhat.com,
  Douglas Landgraf dougsl...@redhat.com
  Sent: Tuesday, August 5, 2014 10:01:14 PM
  Subject: Re: [ovirt-users] Proper way to change and persist vdsm
  configuration options
 
  Ah, thank you for the input!  Just so I'm not spending time
  implementing the wrong changes, let me confirm I understand your
  comments.
 
  1) Deploy host with Foreman
  2) Apply Puppet catalog including ovirt Puppet module
  3) Initiate host-deploy via rest API
 
  In the ovirt module the following takes place:
 
  2a) Add yum repos
  2b) Manage  /etc/ovirt-host-deploy.conf.d/40-xxx.conf
 
 
  you can have any # of files with any prefix :))
 
  For #2b I have a few questions
 
  * The name of the .conf file is simply for sorting and
  labeling/organization, it has not functional impact on what those
  overrides apply to?
 
  right.
 
  * That file is managed on the ovirt-engine server, not the actual nodes?
 
  currently on the host, in future we will provide a method to add this to
  engine database[1]
 
  [1] http://gerrit.ovirt.org/#/c/27064/
 
  * Is there any way to apply overrides to specific hosts?  For example
  if I have some hosts that require a config and others that don't, how
  would I separate those *.conf files?  This is more theoretical as
  right now my setup is common across all nodes.
 
  the poppet module can put whatever required on each host.
 
  For #3...the implementation of API calls from within Puppet is a
  challenge and one I can't tackle yet, but definitely will make it a
  goal for the future.  In the mean time, what's the manual way to
  initiate host-deploy?  Is there a CLI command that would have the same
  result as an API call or is the recommended way to perform the API
  call manually (ie curl)?
 
  well, you can register host using the following protocol[1], but it is
  difficult to do this securely, what you actually need is to establish ssh
  trust for root with engine key then register.
 
  you can also use the register command using curl by something like (I have
  not checked):
  https://admin%40internal:password@engine/ovirt-engine/api/hosts
  ---
  ?xml version=1.0 encoding=UTF-8 standalone=yes?
  host

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

2014-08-05 Thread Itamar Heim


On 08/05/2014 09:36 PM, Trey Dockendorf wrote:

On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:

Hey,

Just noticed something that I forgot about..
before filing new BZ, see in ovirt-host-deploy README.environment [1] the
section:
VDSM/configOverride(bool) [True]
 Override vdsm configuration file.

changing it to false will keep your vdsm.conf file as is after deploying the
host again (what happens after node upgrade)

[1]
https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

please check if that what you meant..

Thanks,
Yaniv Bronhaim.



I was unaware of that package.  I will check that out as that seems to
be what I am looking for.

I have not filed this in BZ and will hold off pending
ovirt-host-deploy.  If you feel a BZ is still necessary then please do
file one and I would be happy to provide input if it would help.

Right now this is my workflow.

1. Foreman provisions bare-metal server with CentOS 6.5
2. Once provisioned and system rebooted Puppet applies puppet-ovirt
[1] module that adds the necessary yum repos, and installs packages.
Part of my Puppet deployment is basic things like sudo management
(vdsm's sudo is account for), sssd configuration, and other aspects
that are needed by every system in my infrastructure.  Part of the
ovirt::node Puppet class is managing vdsm.conf, and in my case that
means ensuring iSER is enabled for iSCSI over IB.
3. Once host is online and has had the full Puppet catalog applied I
log into ovirt-engine web interface and add those host (pulling it's
data via the Foreman provider).


just wondering (and i may have missed this in the thread) - if you want 
bare metal provisioning and foreman, why not just use the new 3.5 
integration doing that:

http://www.ovirt.org/Features/AdvancedForemanIntegration

it will call foreman, do bare metal provision with the hostgroup you 
chose, then foreman will call add host in the engine on your behalf?


(doesn't limit you from either extending ovirt-host-deploy plugins, or 
using more puppet modules via the hostgroup).


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

Re: [ovirt-users] Proper way to change and persist vdsm configuration options

On Tue, Aug 5, 2014 at 3:31 PM, Itamar Heim ih...@redhat.com wrote:
 On 08/05/2014 09:36 PM, Trey Dockendorf wrote:

 On Tue, Aug 5, 2014 at 12:32 PM, ybronhei ybron...@redhat.com wrote:

 Hey,

 Just noticed something that I forgot about..
 before filing new BZ, see in ovirt-host-deploy README.environment [1] the
 section:
 VDSM/configOverride(bool) [True]
  Override vdsm configuration file.

 changing it to false will keep your vdsm.conf file as is after deploying
 the
 host again (what happens after node upgrade)

 [1]
 https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment

 please check if that what you meant..

 Thanks,
 Yaniv Bronhaim.


 I was unaware of that package.  I will check that out as that seems to
 be what I am looking for.

 I have not filed this in BZ and will hold off pending
 ovirt-host-deploy.  If you feel a BZ is still necessary then please do
 file one and I would be happy to provide input if it would help.

 Right now this is my workflow.

 1. Foreman provisions bare-metal server with CentOS 6.5
 2. Once provisioned and system rebooted Puppet applies puppet-ovirt
 [1] module that adds the necessary yum repos, and installs packages.
 Part of my Puppet deployment is basic things like sudo management
 (vdsm's sudo is account for), sssd configuration, and other aspects
 that are needed by every system in my infrastructure.  Part of the
 ovirt::node Puppet class is managing vdsm.conf, and in my case that
 means ensuring iSER is enabled for iSCSI over IB.
 3. Once host is online and has had the full Puppet catalog applied I
 log into ovirt-engine web interface and add those host (pulling it's
 data via the Foreman provider).


 just wondering (and i may have missed this in the thread) - if you want bare
 metal provisioning and foreman, why not just use the new 3.5 integration
 doing that:
 http://www.ovirt.org/Features/AdvancedForemanIntegration

 it will call foreman, do bare metal provision with the hostgroup you chose,
 then foreman will call add host in the engine on your behalf?

 (doesn't limit you from either extending ovirt-host-deploy plugins, or using
 more puppet modules via the hostgroup).


I was actually looking forward to using those features but haven't yet
had a chance to test 3.5 as I have no spare hardware at the moment.
The Foreman Integration is definitely on my radar as we rely very
heavily on Foreman.

Thanks,
- Trey
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Is there a plan to allow VM migration?

2014-08-05 Thread John Gardeniers

As per the subject, is there a plan to allow VM migration? By that I
don't mean the current idea of detaching the export storage and
attaching it to another compatible system. I mean a real migration to
something external to the system the VM is currently on.

At least in my universe, there are times when it is highly desirable or
even necessary to take an Ovirt/RHEV VM and move or copy it to another
system, such as between completely separate Ovirt/RHEV systems or to
other systems such as KVM/Qemu or VirtualBox. The nearest I can manage
right now is to use an imaging tool to make a copy of the drive and
import that into the destination machine. That's slow, cumbersome and
still requires the VMs configuration to be manually duplicated.

regards,
John

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

[ovirt-users] Is there a plan to allow VM migration?

2014-08-05 Thread R P Herrold

On Wed, 6 Aug 2014, John Gardeniers wrote:

 As per the subject, is there a plan to allow VM migration? By that I
 import that into the destination machine. That's slow, cumbersome and
 still requires the VMs configuration to be manually duplicated.

The problem we have run into when trying to implement 
automated assistance on image migrations between different 
backing store, is that the bootloader / initrd fixups are not 
deterministic and 'doable' as between grub, grub2, and other 
'first stage'

I would love a solution, but after much experimentation, I 
just don't see a good path to solving this in a general form.  
(it is not a many spokes to one common interchange format, and 
then one to new spoke transition, but rather a many to many 
problem)

Perhaps the libguestfs uplift mentioned for a few months from 
now with the RHEL 7.1 updates will help

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

Re: [ovirt-users] Standalone Websocket Proxy not working

Hi Simone,

I already trusted the CA in my browser but still has the same error..

Thanks,
Punit


On Tue, Aug 5, 2014 at 7:45 PM, Simone Tiraboschi stira...@redhat.com
wrote:

 Hi Punit,
 I'm assuming that you are using a local internal CA,
 did explicit trusted it in your browser?

 You can get your local CA cert from:
 https://your_engine_fqdn/ca.crt

 Please download it, add it into the list of your trusted CA in your
 browser and try again.

 oVirt 3.5 will provide a mechanism to deploy the websocket proxy on a
 separate host via engine-setup. Also in that scenario you still have to
 trust the CA in your browser.


 ciao,
 Simone


 - Original Message -
 From: Punit Dambiwal hypu...@gmail.com
 To: users@ovirt.org, Dan Kenigsberg dan...@redhat.com,
 aha...@redhat.com, Sven Kieske s.kie...@mittwald.de, Michal
 Skrivanek michal.skriva...@redhat.com, Antoni Segura Puimedon 
 asegu...@redhat.com, Frantisek Kobzik fkob...@redhat.com, sabose 
 sab...@redhat.com, Itamar Heim ih...@redhat.com, barum...@redhat.com
 Sent: Tuesday, August 5, 2014 9:56:41 AM
 Subject: [ovirt-users] Standalone Websocket Proxy not working

 Hi All,

 I have followed the following document to install the websocket proxy on
 seperate machine :-


 http://www.ovirt.org/Features/noVNC_console#Setup_Websocket_Proxy_on_a_Separate_Machine

 But when i try to open the VNC console it failed with the following errors
 :-

 Server disconnected (code: 1006)

 Engine Logs :-

 -
 2014-08-05 15:51:22,540 INFO
 [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-5)
 [6101845f] Running command: SetVmTicketCommand internal: false. Entities
 affected : ID: 6e0caf73-ae7d-493e-a51d-ecc32f507f00 Type: VM
 2014-08-05 15:51:22,574 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
 (ajp--127.0.0.1-8702-5) [6101845f] START, SetVmTicketVDSCommand(HostName =
 Quanta, HostId = 10d7b6ea-d9fa-46af-bcd7-1d7b3c15b5ca,
 vmId=6e0caf73-ae7d-493e-a51d-ecc32f507f00, ticket=5r7OgcpCeGCt,
 validTime=120,m userName=admin,
 userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 67f98489
 2014-08-05 15:51:22,596 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
 (ajp--127.0.0.1-8702-5) [6101845f] FINISH, SetVmTicketVDSCommand, log id:
 67f98489
 2014-08-05 15:51:22,623 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
 (ajp--127.0.0.1-8702-5) [6101845f] Correlation ID: 6101845f, Call Stack:
 null, Custom Event ID: -1, Message: user admin initiated console session
 for VM test1
 -

 When I navigate to https://websocketproxyip :port to accept the
 certificate the first time... it throws an error The connection was reset

 Thanks,
 Punit




 ___
 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: [ovirt-users] Network Question

Hi Sahina,

But Ovirt panel doesn't allow me to add with FQDN...it just display the ip
address of the hosts...

[image: Inline image 1]


On Tue, Aug 5, 2014 at 7:48 PM, Sahina Bose sab...@redhat.com wrote:


 On 08/04/2014 09:06 AM, Punit Dambiwal wrote:

  Hi Sahina,

  But when i try to add the gluster Hosts from Ovirtit doesn't display
 the FQDN to add the bricks...it display the ip address only...i will try to
 use the work around


 When you add the gluster host to oVirt, you should have provided the FQDN
 in the host address field. It uses this to display the list of hosts from
 which you can add the bricks




  Another question is what will be the drawbacks if i use ovirtmgmt and
 storage on the same network (i will use 10GB network here with bonding) ??


  On Fri, Aug 1, 2014 at 6:14 PM, Sahina Bose sab...@redhat.com wrote:


 On 08/01/2014 02:51 PM, Dan Kenigsberg wrote:

 On Fri, Aug 01, 2014 at 09:43:07AM +0800, Punit Dambiwal wrote:

 Hi All,

 Is there any update on this ??


 On Thu, Jul 31, 2014 at 9:08 AM, Punit Dambiwal hypu...@gmail.com
 wrote:

  Hi Antoni,

 But all the bricks and gluster in the another subnet...I am using the
 Compute and gluster storage combined on the same host

 Ovirtmgmt :- 43.25.76.0/24
 Gluster Storage :-  10.10.10.0/24

  Did you try to follow Sahina's advice?

 qemu-to-gluster communication goes on top the IP that you mount.
 However, without hacks, inter-gluster communication uses FQDN of hosts,
 which most commonly resolves to the management network.



  From the output of your gluster volume info , it looks like you have
 used IP address (43.25...) to peer probe the hosts? If you add the host
 from oVirt, for gluster to be able to use separate network for
 glusterd-glusterd communication, you will need to use FQDN while adding the
 host, and workaround as mentioned in
 http://lists.ovirt.org/pipermail/users/2014-February/020894.html




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

Re: [ovirt-users] Guest VM Console Creation/Access using REST API and noVNC

Hi,

I am still waiting for the updatesis there any one in the community who
can help me to resolve this issueor the Ovirt lacking this
feature.that means we can not integrate VM console to our own portal
through API ???

Thanks,
Punit


On Mon, Jul 28, 2014 at 2:40 PM, Punit Dambiwal hypu...@gmail.com wrote:

 Hi,

 Is there any one have the clue to resolve this problemit seems no one
 did this before ??

 Thanks,
 Punit


 On Fri, Jul 25, 2014 at 1:13 PM, Shanil S xielessha...@gmail.com wrote:

 Hi Bob,

 We require the VM control through our portal and our requirement is to
 give access to the console from our portal. Our portal is also will be
 doing some other vm functions like listing vm,start vm,stop vm etc and
 other operations using the REST Api that you provided.

 --
 Regards
 Shanil


 On Fri, Jul 25, 2014 at 10:15 AM, Bob Doolittle b...@doolittle.us.com
 wrote:

 You have only mentioned console access. Do you really need the
 Administrative Portal or could you live with the User Portal? Do you need
 VM control through your portal, or only consoles? What is your use scenario?

 -Bob
 On Jul 25, 2014 12:33 AM, Punit Dambiwal hypu...@gmail.com wrote:

 Hi Dan,

 We require the VM console which provide html5 console...please let me
 know can we achieve html5 with the spice..if yes how to integrate it with
 API and our own portal...??


 On Fri, Jul 25, 2014 at 6:31 AM, Itamar Heim ih...@redhat.com wrote:

 On 07/24/2014 02:43 PM, Frantisek Kobzik wrote:

 Hello Punit,

 this wouldn't be so straightforward. The data that goes from noVNC
 client to websocket proxy must be digitally signed. In engine, we use
 SignString query for that. There are 2 possibilities to create such
 signatures:
 1, Expose SignString via rest api, or


 this means its a gap we need to close in any case to allow moving the
 portals to work over the REST API?


  2, implement this signing mechanism from scratch (for that the
 signing machine would have to posses private key for signing
 ovirt-websocket-proxy tickets, which I don't like).

 This is just first idea on how we could do it. Let me think about it
 a little bit longer, I'll try to ask around and maybe we'll come up with
 something better.

 Thanks,
 Franta.

 - Original Message -
 From: Punit Dambiwal hypu...@gmail.com
 To: Shanil S xielessha...@gmail.com, Dan Kenigsberg 
 dan...@redhat.com, aha...@redhat.com, Sven Kieske 
 s.kie...@mittwald.de, Antoni Segura Puimedon asegu...@redhat.com,
 Itamar Heim ih...@redhat.com
 Cc: Michal Skrivanek michal.skriva...@redhat.com, Frantisek
 Kobzik fkob...@redhat.com, users@ovirt.org
 Sent: Thursday, July 24, 2014 6:50:02 AM
 Subject: Re: [ovirt-users] Guest VM Console Creation/Access using
 REST API and noVNC

 Hi All,

 Is there any body in the community...who can help us to resolve this
 issue...

 1. We are using Ovirt 3.4.3 and we are able to access the console
 from the
 ovirt panel.
 2. We don't want to use the ovirt engine portal for the webUI, we
 want to
 use our own portal for user interface.
 3. Webbsocket proxy Installed on the same sever where ovirt engine
 installed.
 4. We want to access the VM console from our portal,which is
 different from
 this Ovirt cluster.
 5. We already allowed our portal server Ip address in the engine as
 well as
 all the hypervisior servers.also selinux on all the servers are
 disabled mode.
 6. Display network is on the ovirtmgmt network and the same network
 we are
 using to get the VM console
 7. We are able to create the ticket and with the help of the ticket
 details,when we try to access the VM console through our portal it
 failed
 with the following error (Failed to connect to server (code: 1006)).
 8. Same time we can access the console from any vnc client,which is
 installed on my local system,but through browser with novnc it through
 error.
 9. We found that there is no direct api function to create console,
 so how
 we can create console using our own portal and how we can achieve
 this ??
 10. If it's not possible then is there any workaround for the same...

 Our whole project just stuck because of this issue...please help us
 so we
 can go ahead with Ovirt

 Thanks,
 Punit



 On Wed, Jul 23, 2014 at 1:00 PM, Shanil S xielessha...@gmail.com
 wrote:

  Hi Michal,

 We are using 3.4.3 and we are able to access the console from the
 ovirt
 panel. We don't want to use the ovirt engine portal for the webUI,
 we want
 to use our own portal for user interface. We have installed
 websocket proxy
 on the ovirt engine server and now we want to access the VM console
 from
 our portal. How we can achieve this ? it is found that there is no
 direct
 api function to create console, so how we can create console using
 our own
 portal ?


 --
 Regards
 Shanil


 On Tue, Jul 22, 2014 at 7:15 PM, Michal Skrivanek 
 michal.skriva...@redhat.com wrote:


 On Jul 22, 2014, at 13:34 , Shanil S xielessha...@gmail.com
 wrote:

  Hi Michal,

 Thanks for your

Re: [ovirt-users] Is there a plan to allow VM migration?

2014-08-05 Thread John Gardeniers

Hi Russ,

Could it be that you're over-thinking this? Why can't Ovirt simply
export VMs to a standard format, preferably of course one already used
elsewhere, such as ovf? That way it's a straight one-to-one.

regards,
John


On 06/08/14 08:57, R P Herrold wrote:
 On Wed, 6 Aug 2014, John Gardeniers wrote:

 As per the subject, is there a plan to allow VM migration? By that I
 import that into the destination machine. That's slow, cumbersome and
 still requires the VMs configuration to be manually duplicated.
 The problem we have run into when trying to implement 
 automated assistance on image migrations between different 
 backing store, is that the bootloader / initrd fixups are not 
 deterministic and 'doable' as between grub, grub2, and other 
 'first stage'

 I would love a solution, but after much experimentation, I 
 just don't see a good path to solving this in a general form.  
 (it is not a many spokes to one common interchange format, and 
 then one to new spoke transition, but rather a many to many 
 problem)

 Perhaps the libguestfs uplift mentioned for a few months from 
 now with the RHEL 7.1 updates will help

 -- Russ herrold

 __
 This email has been scanned by the Symantec Email Security.cloud service.
 For more information please visit http://www.symanteccloud.com
 __

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

Re: [ovirt-users] Standalone Websocket Proxy not working

Hi All,

It's Ok now...there was some mismatch in the country at the time of the key
generation (subject=/C=country/O=organization/CN=fqdn)...regenerate
the key with same country and organization as engine...it works...

Thanks,
Punit


On Wed, Aug 6, 2014 at 9:02 AM, Punit Dambiwal hypu...@gmail.com wrote:

 Hi Simone,

 I already trusted the CA in my browser but still has the same error..

 Thanks,
 Punit


 On Tue, Aug 5, 2014 at 7:45 PM, Simone Tiraboschi stira...@redhat.com
 wrote:

 Hi Punit,
 I'm assuming that you are using a local internal CA,
 did explicit trusted it in your browser?

 You can get your local CA cert from:
 https://your_engine_fqdn/ca.crt

 Please download it, add it into the list of your trusted CA in your
 browser and try again.

 oVirt 3.5 will provide a mechanism to deploy the websocket proxy on a
 separate host via engine-setup. Also in that scenario you still have to
 trust the CA in your browser.


 ciao,
 Simone


 - Original Message -
 From: Punit Dambiwal hypu...@gmail.com
 To: users@ovirt.org, Dan Kenigsberg dan...@redhat.com,
 aha...@redhat.com, Sven Kieske s.kie...@mittwald.de, Michal
 Skrivanek michal.skriva...@redhat.com, Antoni Segura Puimedon 
 asegu...@redhat.com, Frantisek Kobzik fkob...@redhat.com, sabose 
 sab...@redhat.com, Itamar Heim ih...@redhat.com, barum...@redhat.com
 Sent: Tuesday, August 5, 2014 9:56:41 AM
 Subject: [ovirt-users] Standalone Websocket Proxy not working

 Hi All,

 I have followed the following document to install the websocket proxy on
 seperate machine :-


 http://www.ovirt.org/Features/noVNC_console#Setup_Websocket_Proxy_on_a_Separate_Machine

 But when i try to open the VNC console it failed with the following
 errors :-

 Server disconnected (code: 1006)

 Engine Logs :-

 -
 2014-08-05 15:51:22,540 INFO
 [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-5)
 [6101845f] Running command: SetVmTicketCommand internal: false. Entities
 affected : ID: 6e0caf73-ae7d-493e-a51d-ecc32f507f00 Type: VM
 2014-08-05 15:51:22,574 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
 (ajp--127.0.0.1-8702-5) [6101845f] START, SetVmTicketVDSCommand(HostName =
 Quanta, HostId = 10d7b6ea-d9fa-46af-bcd7-1d7b3c15b5ca,
 vmId=6e0caf73-ae7d-493e-a51d-ecc32f507f00, ticket=5r7OgcpCeGCt,
 validTime=120,m userName=admin,
 userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 67f98489
 2014-08-05 15:51:22,596 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
 (ajp--127.0.0.1-8702-5) [6101845f] FINISH, SetVmTicketVDSCommand, log id:
 67f98489
 2014-08-05 15:51:22,623 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
 (ajp--127.0.0.1-8702-5) [6101845f] Correlation ID: 6101845f, Call Stack:
 null, Custom Event ID: -1, Message: user admin initiated console session
 for VM test1
 -

 When I navigate to https://websocketproxyip :port to accept the
 certificate the first time... it throws an error The connection was reset

 Thanks,
 Punit




 ___
 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

[ovirt-users] Why Ovirt do not have - User community Forum

2014-08-05 Thread Chandrahasa S

Dear All, 

Why we do not have Ovirt Forum like CentOS. Where I can see all reported / 
solved issues. 

CentOS forum is : https://www.centos.org/forums/

Regards,
Chandrahasa S
Tata Consultancy Services
Data Center- ( Non STPI)
2nd Pokharan Road,
Subash Nagar ,
Mumbai - 400601,Maharashtra
India
Ph:- +91 22 677-81825
Buzz:- 4221825
Mailto: chandrahas...@tcs.com
Website: http://www.tcs.com

Experience certainty.IT Services
   Business Solutions
   Consulting
 



From:Federico Simoncelli fsimo...@redhat.com 
To:Daniel Helgenberger daniel.helgenber...@m-box.de 
Cc:users@ovirt.org 
Date:08/05/2014 06:51 PM 
Subject:Re: [ovirt-users] SPM in oVirt 3.6 
Sent by:users-boun...@ovirt.org 




- Original Message -
 From: Nir Soffer nsof...@redhat.com
 To: Daniel Helgenberger daniel.helgenber...@m-box.de
 Cc: users@ovirt.org, Federico Simoncelli fsimo...@redhat.com
 Sent: Monday, July 28, 2014 6:43:30 PM
 Subject: Re: [ovirt-users] SPM in oVirt 3.6
 
 - Original Message -
  From: Daniel Helgenberger daniel.helgenber...@m-box.de
  To: users@ovirt.org
  Sent: Friday, July 25, 2014 7:51:33 PM
  Subject: [ovirt-users] SPM in oVirt 3.6
  
  just out of pure curiosity: In a BZ [1] Allon mentions SPM will go 
away
  in ovirt 3.6.
  
  This seems like a major change for me. I assume this will replace
  sanlock as well? What will SPM be replaced with?
 
 No, sanlock is not going anywhere.
 
 The change is that we will not have an SPM node, but any node that need 
to
 make meta data changes, will take a lock using sanlock while it make the
 changes.
 
 Federico: can you describe in more details how it is going to work?

Most of the information can be found on the feature page:

http://www.ovirt.org/Features/Decommission_Master_Domain_and_SPM

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

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


___
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: [ovirt-users] Proper way to change and persist vdsm configuration options