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
afaik el6 and openssh support pkcs#8 for ages.
at least I have no issue using pkcs#8 formatted keys
with el6 hosts.
Am 21.08.2014 22:05, schrieb Alon Bar-Lev:
I hope el6 will have newer openssh with support for the PKCS8 format.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
- Original Message -
From: Sven Kieske s.kie...@mittwald.de
To: users@ovirt.org
Sent: Friday, August 22, 2014 10:32:05 AM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
afaik el6 and openssh support pkcs#8 for ages.
at least I have
well yeah, it does not generate pkcs#8 by default
but you can easily convert existing keys via openssl:
openssl pkcs8 -topk8 -v2 des3 \
-in test_rsa_key.old -passin 'pass:super secret passphrase' \
-out test_rsa_key -passout 'pass:super secret passphrase'
see this page for more details:
...@mittwald.de
To: Alon Bar-Lev alo...@redhat.com
Cc: users@ovirt.org
Sent: Friday, August 22, 2014 1:24:17 PM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
well yeah, it does not generate pkcs#8 by default
but you can easily convert existing keys via
@ovirt.org
Sent: Friday, August 22, 2014 1:24:17 PM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
well yeah, it does not generate pkcs#8 by default
but you can easily convert existing keys via openssl:
openssl pkcs8 -topk8 -v2 des3
dan...@redhat.com, Itamar Heim ih...@redhat.com, Douglas
Landgraf dougsl...@redhat.com, Oved
Ourfali ov...@redhat.com
Sent: Tuesday, August 5, 2014 11:27:45 PM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
Thanks for clarifying, makes sense now
...@redhat.com, Oved
Ourfali ov...@redhat.com
Sent: Thursday, August 21, 2014 9:41:03 PM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
Sorry, I meant the SSH public key. Is that a file or in the database?
I did a grep for the public key downloaded via
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: Thursday, August 21, 2014 9:41:03 PM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
...@redhat.com, Oved
Ourfali ov...@redhat.com
Sent: Thursday, August 21, 2014 10:55:28 PM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
Is there a method that works in EL6?
$ openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -noout
-pubkey | ssh
Cc: users users@ovirt.org
Sent: Tuesday, August 5, 2014 10:17:06 PM
Subject: Re: [ovirt-users] Proper way to change and persist vdsm
configuration options
Yep, these are Supermicro servers.
# facter serialnumber
1234567890
On Tue, Aug 5, 2014 at 2:07 PM, Joop jvdw...@xs4all.nl
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
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
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
...@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
, 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
...@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
, 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
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
...@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
, 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
...@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
...@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
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]
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
...@redhat.com, Oved
Ourfali ov...@redhat.com
Sent: Tuesday, August 5, 2014 11:27:45 PM
Subject: 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
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'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
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
please send a link to the BZ, or assign me there
I have been using Puppet to modify values and have had to rerun Puppet
after installing a node via GUI and when performing
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
30 matches
Mail list logo
