Re: [ovirt-users] trunk port for vm guest

2017-09-21 Thread Charles Kozler
So I tried to set this up. I configured an untagged network and attached it
to all of my hosts. I setup a VM and correctly setup a trunk port but no
traffic is passed

Can anyone assist?

On Wed, Sep 20, 2017 at 9:09 AM, Charles Kozler 
wrote:

> Hello,
>
> I have seen mixed results for this search on this list so I'd like to
> clear it up
>
> I have a VM that I need to configure with a trunk port so that all of my
> VLANs can be configured on it but not as separate NICs (eth0, eth1, eth2,
> etc)
>
> I have seen on this list about a year ago someone said to setup a network
> and leave it untagged and ovirt will pass all tagged and untagged packets
> there. Then attach this to the guest VM and configure the trunk port inside
> the VM (eth0:)
>
> However, I saw also about 6 months ago someone suggest something like VLAN
> tag 4095 so wondering if the support came in for this...or I should use
> untagged VM network
>
> So - how can I configure a trunk port for a guest VM?
>
> Thanks
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Where can we get emergency support for oVirt ?

2017-09-21 Thread Charles Kozler
https://www.ovirt.org/community/user-stories/users-and-providers/

BobCares is based out of India, so know that. They seemed responsive and
helpful and eager for business and generally knowledgeable in initial talks

I'd recommend you check out CornerStone. They are states local (I think NC
or SC) and Gary is a great guy (I am not affiliated with them). The link is
broken on that page so use https://cornerstonets.net/

On Thu, Sep 21, 2017 at 4:33 PM, netad  wrote:

> We have been unable to find anyone who can help fix an urgent problem.
>
> Please advise.
>
> 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


[ovirt-users] Where can we get emergency support for oVirt ?

2017-09-21 Thread netad
We have been unable to find anyone who can help fix an urgent problem.

Please advise.

Thank you/




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


Re: [ovirt-users] VM won't start if a Cinder disk is attached

2017-09-21 Thread Luca 'remix_tj' Lorenzetto
Hi,

can you attach vdsm.log?

Which version are you running? IIRC in the past booting from Ceph was not
possible, but should be possible since 4.1.

Luca

On Thu, Sep 21, 2017 at 3:42 PM, Maxence SARTIAUX 
wrote:

> Hello
>
> I have a ovirt 4.1.5.2-1 ovirt cluster with a ceph luminous & openstack
> ocata cinder.
>
> I can create / remove / attach cinder disks with ovirt but when i attach a
> disk to a VM, the VM stay in "starting mode" (double up arrow grey) and
> never goes up, ovirt try every available hypervisors and end to detach the
> disk and stay in "starting up" state
>
> All i see in the libvirt logs are "connection timeout" nothing more, the
> hypervisors can contact the ceph cluster
>
> Nothing related in the ovirt logs & cinder
>
> Any ideas ?
>
> Thank you !
>
>
>
> Maxence Sartiaux | System & Network Engineer
> Boulevard Initialis, 28 - 7000 Mons
> Tel : +32 (0)65 84 23 85 <+32%2065%2084%2023%2085> (ext: 6016)
> Fax : +32 (0)65 84 66 76 <+32%2065%2084%2066%2076> www.it-optics.com
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
lorenzetto.l...@gmail.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Cannot change resolution on Ubuntu 16 LTS, using spice

2017-09-21 Thread Филипп Панин
Hey, i have problem setting resolution higher than 1024x768 on guest using
spice
xserver-xorg-video - installed
spice-vdagent - installed
ovirt-guest-agent - installed

/var/log/syslog:

Sep 21 13:16:48 admin-oVirt-Node kernel: [ 1548.537892] qxl :00:02.0:
object_init failed for (8302592, 0x0002)
Sep 21 13:16:48 admin-oVirt-Node kernel: [ 1548.537901]
[drm:qxl_gem_object_create [qxl]] *ERROR* Failed to allocate GEM object
(8302080, 2, 4096, -12)
Sep 21 13:16:48 admin-oVirt-Node kernel: [ 1548.537905]
[drm:qxl_alloc_surf_ioctl [qxl]] *ERROR* qxl_alloc_surf_ioctl: failed to
create gem ret=-12
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] VM won't start if a Cinder disk is attached

2017-09-21 Thread Maxence SARTIAUX


Hello 



I have a ovirt 4.1.5.2-1 ovirt cluster with a ceph luminous & openstack ocata 
cinder. 


I can create / remove / attach cinder disks with ovirt but when i attach a disk 
to a VM, the VM stay in "starting mode" (double up arrow grey) and never goes 
up, ovirt try every available hypervisors and end to detach the disk and stay 
in "starting up" state 


All i see in the libvirt logs are "connection timeout" nothing more, the 
hypervisors can contact the ceph cluster 


Nothing related in the ovirt logs & cinder 


Any ideas ? 


Thank you ! 







Maxence Sartiaux | System & Network Engineer 
Boulevard Initialis, 28 - 7000 Mons 
Tel :   +32 (0)65 84 23 85 (ext: 6016) 
Fax :   +32 (0)65 84 66 76 www.it-optics.com 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt repo errors..

2017-09-21 Thread Alexander Witte
Disregard, figured it out- system clock was wrong.  Sorry!

Alex Witte


On Sep 21, 2017, at 2:20 PM, Alexander Witte 
> wrote:

I seem to get this error with multiple oVirt repos (4.0, 4.1).  I’m just trying 
to install the hosted engine on a fresh Centos 7.4 server...

Can someone please point me in the direction of what I am doing wrong?


[root@localhost ~]# yum install ovirt-hosted-engine-setup
Loaded plugins: fastestmirror
base

 | 3.6 kB  00:00:00
centos-opstools-release 

 | 2.9 kB  00:00:00
extras  

 | 3.4 kB  00:00:00
ovirt-4.1   

 | 3.0 kB  00:00:00
ovirt-4.1-centos-gluster38  

 | 2.9 kB  00:00:00


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

 5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify 
its path and try again
[root@localhost ~]#

[root@localhost ~]# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)
[root@localhost ~]#

Sorry if I’m dumb.

Alex

___
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] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-21 Thread Piotr Kliczewski
Neil,

It seems that your engine certificate(s) is/are not ok. I would
suggest to enable ssl debug in the engine by:
- add '-Djavax.net.debug=all' to ovirt-engine.py file here [1].
- restart your engine
- check your server.log and check what is the issue.

Hopefully we will be able to understand what happened in your setup.

Thanks,
Piotr

[1] 
https://github.com/oVirt/ovirt-engine/blob/master/packaging/services/ovirt-engine/ovirt-engine.py#L341

On Thu, Sep 21, 2017 at 4:42 PM, Neil  wrote:
> Further to the logs sent, on the nodes I'm also seeing the following error
> under /var/log/messages...
>
> Sep 20 03:43:12 node01 vdsm root ERROR invalid client certificate with
> subject "/C=US/O=UKDM/CN=engine01.mydomain.za"^C
> Sep 20 03:43:12 node01 vdsm vds ERROR xml-rpc handler exception#012Traceback
> (most recent call last):#012  File "/usr/share/vdsm/BindingXMLRPC.py", line
> 80, in threaded_start#012self.server.handle_request()#012  File
> "/usr/lib64/python2.6/SocketServer.py", line 278, in handle_request#012
> self._handle_request_noblock()#012  File
> "/usr/lib64/python2.6/SocketServer.py", line 288, in
> _handle_request_noblock#012request, client_address =
> self.get_request()#012  File "/usr/lib64/python2.6/SocketServer.py", line
> 456, in get_request#012return self.socket.accept()#012  File
> "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 136,
> in accept#012raise SSL.SSLError("%s, client %s" % (e,
> address[0]))#012SSLError: no certificate returned, client 10.251.193.5
>
> Not sure if this is any further help in diagnosing the issue?
>
> Thanks, any assistance is appreciated.
>
> Regards.
>
> Neil Wilson.
>
>
> On Thu, Sep 21, 2017 at 4:31 PM, Neil  wrote:
>>
>> Hi Piotr,
>>
>> Thank you for the reply. After sending the email I did go and check the
>> engine one too
>>
>> [root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/ca.pem -enddate
>> -noout
>> notAfter=Oct 13 16:26:46 2022 GMT
>>
>> I'm not sure if this one below is meant to verify or if this output is
>> expected?
>>
>> [root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/private/ca.pem
>> -enddate -noout
>> unable to load certificate
>> 140642165552968:error:0906D06C:PEM routines:PEM_read_bio:no start
>> line:pem_lib.c:703:Expecting: TRUSTED CERTIFICATE
>>
>> My date is correct too Thu Sep 21 16:30:15 SAST 2017
>>
>> Any ideas?
>>
>> Googling surprisingly doesn't come up with much.
>>
>> Thank you.
>>
>> Regards.
>>
>> Neil Wilson.
>>
>> On Thu, Sep 21, 2017 at 4:16 PM, Piotr Kliczewski
>>  wrote:
>>>
>>> Neil,
>>>
>>> You checked both nodes what about the engine? Can you check engine certs?
>>> You can find more info where they are located here [1].
>>>
>>> Thanks,
>>> Piotr
>>>
>>> [1]
>>> https://www.ovirt.org/develop/release-management/features/infra/pki/#ovirt-engine
>>>
>>> On Thu, Sep 21, 2017 at 3:26 PM, Neil  wrote:
>>> > Hi guys,
>>> >
>>> > Please could someone assist, my cluster is down and I can't access my
>>> > vm's
>>> > to switch some of them back on.
>>> >
>>> > I'm seeing the following error in the engine.log however I've checked
>>> > my
>>> > certs on my hosts (as some of the goolge results said to check), but
>>> > the
>>> > certs haven't expired...
>>> >
>>> >
>>> > 2017-09-21 15:09:45,077 ERROR
>>> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>>> > (DefaultQuartzScheduler_Worker-4) Command
>>> > GetCapabilitiesVDSCommand(HostName
>>> > = node02.mydomain.za, HostId = d2debdfe-76e7-40cf-a7fd-78a0f50f14d4,
>>> > vds=Host[node02.mydomain.za]) execution failed. Exception:
>>> > VDSNetworkException: javax.net.ssl.SSLHandshakeException: Received
>>> > fatal
>>> > alert: certificate_expired
>>> > 2017-09-21 15:09:45,086 ERROR
>>> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>>> > (DefaultQuartzScheduler_Worker-10) Command
>>> > GetCapabilitiesVDSCommand(HostName = node01.mydomain.za, HostId =
>>> > b108549c-1700-11e2-b936-9f5243b8ce13, vds=Host[node01.mydomain.za])
>>> > execution failed. Exception: VDSNetworkException:
>>> > javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>> > certificate_expired
>>> > 2017-09-21 15:09:48,173 ERROR
>>> >
>>> > My engine and host info is below...
>>> >
>>> > [root@engine01 ovirt-engine]# rpm -qa | grep -i ovirt
>>> > ovirt-engine-lib-3.4.0-1.el6.noarch
>>> > ovirt-engine-restapi-3.4.0-1.el6.noarch
>>> > ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch
>>> > ovirt-engine-3.4.0-1.el6.noarch
>>> > ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch
>>> > ovirt-host-deploy-java-1.2.0-1.el6.noarch
>>> > ovirt-engine-setup-3.4.0-1.el6.noarch
>>> > ovirt-host-deploy-1.2.0-1.el6.noarch
>>> > ovirt-engine-backend-3.4.0-1.el6.noarch
>>> > ovirt-image-uploader-3.4.0-1.el6.noarch
>>> > ovirt-engine-tools-3.4.0-1.el6.noarch
>>> > ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch

Re: [ovirt-users] oVirt's VM backup

2017-09-21 Thread Niyazi Elvan
Hi,

Can you share the log files under scripts/logs directory ?


On Sep 21, 2017 8:59 PM, "Nathanaël Blanchet"  wrote:

> Yes seems to be good, the UI is very nice, but I didn't manage to make one
> backup though the connection to the API is okay. I followed the README but
> Nothing happens when lauching the backup processus...
>
> Le 21/09/2017 à 19:34, Niyazi Elvan a écrit :
>
> Hi,
>
> You may check my project Bacchus at https://github.com/openbacchus/bacchus
>
>
>
>
>
> On Sep 21, 2017 19:54, "Bernardo Juanicó"  wrote:
>
> I didnt know that, we may adapt it in the future, but at first we will
> probably just write a basic set of scripts for minimal backup functionally
> since our dev time is limited.
>
> Ill keep you in mind when looking into it.
>
> Regards,
>
> Bernardo
>
> PGP Key 
> Skype: mattraken
>
> 2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet :
>
>> Hi Bernardo,
>>
>> Thanks, I knew this tool, but it is based on sdk3 which will be removed
>> in the next version 4.2, so I'm looking at sdk4 project.
>>
>> You may want to adapt it?
>>
>> Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :
>>
>> Hi Nathanael,
>>
>> You may want to take a look at this too:
>>
>> https://github.com/bjuanico/oVirtBackup
>>
>> Regards,
>>
>> Bernardo
>>
>> PGP Key 
>> Skype: mattraken
>>
>> 2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet :
>>
>>> Hello Victor,
>>>
>>> I have some questions about your script
>>>
>>> Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :
>>>
>>> Hello everyone, i created a python tool to backup and restore oVirt's
>>> VMs.
>>>
>>> Also i created a little "how to" on my blog:
>>> http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>>>
>>>
>>>- Backup step is okay, and I get a usable qcow2 image of the
>>>snapshot vm in the backup vm. It seems to be compliant with the official
>>>backup API, except on the step 2.
>>>
>>>
>>>1. *Take a snapshot of the virtual machine to be backed up -
>>>(existing oVirt REST API operation)*
>>>2. *Back up the virtual machine configuration at the time of the
>>>snapshot (the disk configuration can be backed up as well if needed) -
>>>(added capability to oVirt as part of the Backup API)*
>>>
>>> I can't see any vm configuration anywhere but only the qcow2 disk itself
>>>
>>>1. *Attach the disk snapshots that were created in (1) to the
>>>virtual appliance for data backup - (added capability to oVirt as part of
>>>the Backup API)*
>>>2.
>>> 3. *Detach the disk snapshots that were attached in (4) from the
>>>virtual appliance - (added capability to oVirt as part of the Backup 
>>> API)*
>>>
>>> An other case is when the vm to backup has more than one disk. After I
>>> tested it, I found that only one qcow2 disk is saved on the backup vm. This
>>> is really a matter when the original vm has many disks part of lvm, it
>>> makes the vm restoration unusable.
>>>
>>>- About vm restoration, it seems that you are using the upload_disk
>>>api, so the disk is uploaded to the pre-defined storage domain, so it is
>>>not a real vm restoration.
>>>
>>> Do you plan to backup and restore a full VM (disks + vm definition) in a
>>> next release?
>>>
>>>
>>> I hope it help someone else
>>>
>>> Regards
>>>
>>> Victor Acosta
>>>
>>>
>>>
>>>
>>> ___
>>> Users mailing 
>>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>> --
>>> Nathanaël Blanchet
>>>
>>> Supervision réseau
>>> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
>>> 
>>> 34193 MONTPELLIER CEDEX 5   
>>> Tél. 33 (0)4 67 54 84 55
>>> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
>> 
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
> 
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
___
Users mailing list
Users@ovirt.org

[ovirt-users] oVirt repo errors..

2017-09-21 Thread Alexander Witte
I seem to get this error with multiple oVirt repos (4.0, 4.1).  I’m just trying 
to install the hosted engine on a fresh Centos 7.4 server...

Can someone please point me in the direction of what I am doing wrong?


[root@localhost ~]# yum install ovirt-hosted-engine-setup
Loaded plugins: fastestmirror
base

 | 3.6 kB  00:00:00
centos-opstools-release 

 | 2.9 kB  00:00:00
extras  

 | 3.4 kB  00:00:00
ovirt-4.1   

 | 3.0 kB  00:00:00
ovirt-4.1-centos-gluster38  

 | 2.9 kB  00:00:00


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

 5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify 
its path and try again
[root@localhost ~]#

[root@localhost ~]# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)
[root@localhost ~]#

Sorry if I’m dumb.

Alex

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


[ovirt-users] Hosts will not activate Master Data Store while in Maintenance Mode

2017-09-21 Thread netad
The Data Domain is in Maintenance Mode.  

The Data Domain will not activate because we have no active hosts.

The hosts will not activate -- they always have a status of connecting or not 
responding.

A sample of the VDSM log errors is copied below (about 500 lines of the VDSM 
log is attached)

Storage.HSM:connectStorageServer) Could not connect to storageServer

{'status': {'message': "Wrong Master domain or its version: 
u'SD=e6b9c52e-a528-4ae9-884a-4831967f24dc, 
pool=6ff24c27-9227-4f7c-abf3-263950cf5d35'", 'code': 324}}
dDomain) looking for unfetched domain 673b27d3-862b-42d2-bdfb-3ee6267270cc
Thread-13::ERROR::2017-09-21 
11:13:02,957::sdc::157::Storage.StorageDomainCache:_findUnfetchedDomain) 
looking for domain 673b27d3-862b-42d2-bdfb-3ee6267270cc
Thread-13::ERROR::2017-09-21 
11:13:03,068::sdc::146::Storage.StorageDomainCache:_findDomain) domain 
673b27d3-862b-42d2-bdfb-3ee6267270cc not found
Thread-13::ERROR::2017-09-21 
11:13:03,069::monitor::328::Storage.Monitor:_setupLoop) Setting up monitor for 
673b27d3-862b-42d2-bdfb-3ee6267270cc failed
Thread-14::ERROR::2017-09-21 
11:13:03,078::sdc::140::Storage.StorageDomainCache:_findDomain) looking for 
unfetched domain caa44e02-6ff2-46df-a156-3a74ae26e910
Thread-14::ERROR::2017-09-21 
11:13:03,078::sdc::157::Storage.StorageDomainCache::

Thanks, 

Netad






vdsm.log
Description: Binary data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt's VM backup

2017-09-21 Thread FERNANDO FREDIANI

Is it just me just finds strange the way oVirt/RHEV does backup ?

At the present you have to snapshot the VM (fine by that), but them you 
have to clone AND export it to an Export Domain, then delete the cloned 
VM. That means three copies of the same VM somewhere.


Wouldn't it be more logical to take a snapshot, get the then read-only 
disk and export it directly from any host that can read it, and finally 
remove the snapshot ?


Why the need to clone AND export ? What is the limitation to pull this 
VM directlly from host decreasing the time it takes the overall process 
and mainly the amount of storage necessary to do this job.
Ohh and before I forget by this workflow the disks are hammered a lot 
more decreasing their lifetime and may causing performance issues mainly 
during the clone process.


Fernando


On 21/09/2017 14:59, Nathanaël Blanchet wrote:


Yes seems to be good, the UI is very nice, but I didn't manage to make 
one backup though the connection to the API is okay. I followed the 
README but Nothing happens when lauching the backup processus...



Le 21/09/2017 à 19:34, Niyazi Elvan a écrit :

Hi,

You may check my project Bacchus at 
https://github.com/openbacchus/bacchus





On Sep 21, 2017 19:54, "Bernardo Juanicó" > wrote:


I didnt know that, we may adapt it in the future, but at first we
will probably just write a basic set of scripts for minimal
backup functionally since our dev time is limited.

Ill keep you in mind when looking into it.

Regards,

Bernardo

PGP Key

Skype: mattraken

2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet >:

Hi Bernardo,

Thanks, I knew this tool, but it is based on sdk3 which will
be removed in the next version 4.2, so I'm looking at sdk4
project.

You may want to adapt it?


Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :

Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup


Regards,

Bernardo

PGP Key

Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet
>:

Hello Victor,

I have some questions about your script


Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a
écrit :

Hello everyone, i created a python tool to backup and
restore oVirt's VMs.

Also i created a little "how to" on my blog:
http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/



  * Backup step is okay, and I get a usable qcow2 image
of the snapshot vm in the backup vm. It seems to be
compliant with the official backup API, except on
the step 2.

 1. /Take a snapshot of the virtual machine to be backed
up - (existing oVirt REST API operation)/
 2. /Back up the virtual machine configuration at the
time of the snapshot (the disk configuration can be
backed up as well if needed) - (added capability to
oVirt as part of the Backup API)/

I can't see any vm configuration anywhere but only the
qcow2 disk itself

 1. /Attach the disk snapshots that were created in (1)
to the virtual appliance for data backup - (added
capability to oVirt as part of the Backup API)/
 2. /
/
 3. /Detach the disk snapshots that were attached in (4)
from the virtual appliance - (added capability to
oVirt as part of the Backup API)/

An other case is when the vm to backup has more than one
disk. After I tested it, I found that only one qcow2
disk is saved on the backup vm. This is really a matter
when the original vm has many disks part of lvm, it
makes the vm restoration unusable.

  * About vm restoration, it seems that you are using
the upload_disk api, so the disk is uploaded to the
pre-defined storage domain, so it is not a real vm
restoration.

Do you plan to backup and restore a full VM (disks + vm
definition) in a next release?



I hope it help someone else

Regards

Victor Acosta




___
Users mailing list
Users@ovirt.org 

[ovirt-users] Hosts will not activate Master Data Store while in Maintenance Mode

2017-09-21 Thread netad
The Data Domain is in Maintenance Mode.  

The Data Domain will not activate because we have no active hosts.

The hosts will not activate -- they always have a status of connecting or not 
responding.

A sample of the VDSM log errors is copied below (about 500 lines of the VDSM 
log is attached)

Storage.HSM:connectStorageServer) Could not connect to storageServer

{'status': {'message': "Wrong Master domain or its version: 
u'SD=e6b9c52e-a528-4ae9-884a-4831967f24dc, 
pool=6ff24c27-9227-4f7c-abf3-263950cf5d35'", 'code': 324}}
dDomain) looking for unfetched domain 673b27d3-862b-42d2-bdfb-3ee6267270cc
Thread-13::ERROR::2017-09-21 
11:13:02,957::sdc::157::Storage.StorageDomainCache:_findUnfetchedDomain) 
looking for domain 673b27d3-862b-42d2-bdfb-3ee6267270cc
Thread-13::ERROR::2017-09-21 
11:13:03,068::sdc::146::Storage.StorageDomainCache:_findDomain) domain 
673b27d3-862b-42d2-bdfb-3ee6267270cc not found
Thread-13::ERROR::2017-09-21 
11:13:03,069::monitor::328::Storage.Monitor:_setupLoop) Setting up monitor for 
673b27d3-862b-42d2-bdfb-3ee6267270cc failed
Thread-14::ERROR::2017-09-21 
11:13:03,078::sdc::140::Storage.StorageDomainCache:_findDomain) looking for 
unfetched domain caa44e02-6ff2-46df-a156-3a74ae26e910
Thread-14::ERROR::2017-09-21 
11:13:03,078::sdc::157::Storage.StorageDomainCache::

Thanks, 

Netad






vdsm.log
Description: Binary data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt's VM backup

2017-09-21 Thread Nathanaël Blanchet

Thanks for your work


Le 21/09/2017 à 18:53, Bernardo Juanicó a écrit :
I didnt know that, we may adapt it in the future, but at first we will 
probably just write a basic set of scripts for minimal backup 
functionally since our dev time is limited.


Ill keep you in mind when looking into it.

Regards,

Bernardo

PGP Key 
Skype: mattraken

2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet >:


Hi Bernardo,

Thanks, I knew this tool, but it is based on sdk3 which will be
removed in the next version 4.2, so I'm looking at sdk4 project.

You may want to adapt it?


Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :

Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup


Regards,

Bernardo

PGP Key

Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet >:

Hello Victor,

I have some questions about your script


Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :

Hello everyone, i created a python tool to backup and
restore oVirt's VMs.

Also i created a little "how to" on my blog:
http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/



  * Backup step is okay, and I get a usable qcow2 image of
the snapshot vm in the backup vm. It seems to be
compliant with the official backup API, except on the step 2.

 1. /Take a snapshot of the virtual machine to be backed up -
(existing oVirt REST API operation)/
 2. /Back up the virtual machine configuration at the time of
the snapshot (the disk configuration can be backed up as
well if needed) - (added capability to oVirt as part of
the Backup API)/

I can't see any vm configuration anywhere but only the qcow2
disk itself

 1. /Attach the disk snapshots that were created in (1) to
the virtual appliance for data backup - (added capability
to oVirt as part of the Backup API)/
 2. /
/
 3. /Detach the disk snapshots that were attached in (4) from
the virtual appliance - (added capability to oVirt as
part of the Backup API)/

An other case is when the vm to backup has more than one
disk. After I tested it, I found that only one qcow2 disk is
saved on the backup vm. This is really a matter when the
original vm has many disks part of lvm, it makes the vm
restoration unusable.

  * About vm restoration, it seems that you are using the
upload_disk api, so the disk is uploaded to the
pre-defined storage domain, so it is not a real vm
restoration.

Do you plan to backup and restore a full VM (disks + vm
definition) in a next release?



I hope it help someone else

Regards

Victor Acosta




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



-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala


34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr   



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





-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala


34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr   





--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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


Re: [ovirt-users] oVirt's VM backup

2017-09-21 Thread Nathanaël Blanchet
Yes seems to be good, the UI is very nice, but I didn't manage to make 
one backup though the connection to the API is okay. I followed the 
README but Nothing happens when lauching the backup processus...



Le 21/09/2017 à 19:34, Niyazi Elvan a écrit :

Hi,

You may check my project Bacchus at 
https://github.com/openbacchus/bacchus





On Sep 21, 2017 19:54, "Bernardo Juanicó" > wrote:


I didnt know that, we may adapt it in the future, but at first we
will probably just write a basic set of scripts for minimal backup
functionally since our dev time is limited.

Ill keep you in mind when looking into it.

Regards,

Bernardo

PGP Key

Skype: mattraken

2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet >:

Hi Bernardo,

Thanks, I knew this tool, but it is based on sdk3 which will
be removed in the next version 4.2, so I'm looking at sdk4
project.

You may want to adapt it?


Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :

Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup


Regards,

Bernardo

PGP Key

Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet
>:

Hello Victor,

I have some questions about your script


Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :

Hello everyone, i created a python tool to backup and
restore oVirt's VMs.

Also i created a little "how to" on my blog:
http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/



  * Backup step is okay, and I get a usable qcow2 image
of the snapshot vm in the backup vm. It seems to be
compliant with the official backup API, except on the
step 2.

 1. /Take a snapshot of the virtual machine to be backed
up - (existing oVirt REST API operation)/
 2. /Back up the virtual machine configuration at the
time of the snapshot (the disk configuration can be
backed up as well if needed) - (added capability to
oVirt as part of the Backup API)/

I can't see any vm configuration anywhere but only the
qcow2 disk itself

 1. /Attach the disk snapshots that were created in (1)
to the virtual appliance for data backup - (added
capability to oVirt as part of the Backup API)/
 2. /
/
 3. /Detach the disk snapshots that were attached in (4)
from the virtual appliance - (added capability to
oVirt as part of the Backup API)/

An other case is when the vm to backup has more than one
disk. After I tested it, I found that only one qcow2 disk
is saved on the backup vm. This is really a matter when
the original vm has many disks part of lvm, it makes the
vm restoration unusable.

  * About vm restoration, it seems that you are using the
upload_disk api, so the disk is uploaded to the
pre-defined storage domain, so it is not a real vm
restoration.

Do you plan to backup and restore a full VM (disks + vm
definition) in a next release?



I hope it help someone else

Regards

Victor Acosta




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



-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala


34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr   



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





-- 
Nathanaël Blanchet


Supervision réseau
Pôle 

Re: [ovirt-users] oVirt's VM backup

2017-09-21 Thread Niyazi Elvan
Hi,

You may check my project Bacchus at https://github.com/openbacchus/bacchus




On Sep 21, 2017 19:54, "Bernardo Juanicó"  wrote:

I didnt know that, we may adapt it in the future, but at first we will
probably just write a basic set of scripts for minimal backup functionally
since our dev time is limited.

Ill keep you in mind when looking into it.

Regards,

Bernardo

PGP Key 
Skype: mattraken

2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet :

> Hi Bernardo,
>
> Thanks, I knew this tool, but it is based on sdk3 which will be removed in
> the next version 4.2, so I'm looking at sdk4 project.
>
> You may want to adapt it?
>
> Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :
>
> Hi Nathanael,
>
> You may want to take a look at this too:
>
> https://github.com/bjuanico/oVirtBackup
>
> Regards,
>
> Bernardo
>
> PGP Key 
> Skype: mattraken
>
> 2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet :
>
>> Hello Victor,
>>
>> I have some questions about your script
>>
>> Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :
>>
>> Hello everyone, i created a python tool to backup and restore oVirt's VMs.
>>
>> Also i created a little "how to" on my blog:
>> http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>>
>>
>>- Backup step is okay, and I get a usable qcow2 image of the snapshot
>>vm in the backup vm. It seems to be compliant with the official backup 
>> API,
>>except on the step 2.
>>
>>
>>1. *Take a snapshot of the virtual machine to be backed up -
>>(existing oVirt REST API operation)*
>>2. *Back up the virtual machine configuration at the time of the
>>snapshot (the disk configuration can be backed up as well if needed) -
>>(added capability to oVirt as part of the Backup API)*
>>
>> I can't see any vm configuration anywhere but only the qcow2 disk itself
>>
>>1. *Attach the disk snapshots that were created in (1) to the virtual
>>appliance for data backup - (added capability to oVirt as part of the
>>Backup API)*
>>2.
>> 3. *Detach the disk snapshots that were attached in (4) from the virtual
>>appliance - (added capability to oVirt as part of the Backup API)*
>>
>> An other case is when the vm to backup has more than one disk. After I
>> tested it, I found that only one qcow2 disk is saved on the backup vm. This
>> is really a matter when the original vm has many disks part of lvm, it
>> makes the vm restoration unusable.
>>
>>- About vm restoration, it seems that you are using the upload_disk
>>api, so the disk is uploaded to the pre-defined storage domain, so it is
>>not a real vm restoration.
>>
>> Do you plan to backup and restore a full VM (disks + vm definition) in a
>> next release?
>>
>>
>> I hope it help someone else
>>
>> Regards
>>
>> Victor Acosta
>>
>>
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
>> 
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
> 
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>

___
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] oVirt's VM backup

2017-09-21 Thread Bernardo Juanicó
I didnt know that, we may adapt it in the future, but at first we will
probably just write a basic set of scripts for minimal backup functionally
since our dev time is limited.

Ill keep you in mind when looking into it.

Regards,

Bernardo

PGP Key 
Skype: mattraken

2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet :

> Hi Bernardo,
>
> Thanks, I knew this tool, but it is based on sdk3 which will be removed in
> the next version 4.2, so I'm looking at sdk4 project.
>
> You may want to adapt it?
>
> Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :
>
> Hi Nathanael,
>
> You may want to take a look at this too:
>
> https://github.com/bjuanico/oVirtBackup
>
> Regards,
>
> Bernardo
>
> PGP Key 
> Skype: mattraken
>
> 2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet :
>
>> Hello Victor,
>>
>> I have some questions about your script
>>
>> Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :
>>
>> Hello everyone, i created a python tool to backup and restore oVirt's VMs.
>>
>> Also i created a little "how to" on my blog:
>> http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>>
>>
>>- Backup step is okay, and I get a usable qcow2 image of the snapshot
>>vm in the backup vm. It seems to be compliant with the official backup 
>> API,
>>except on the step 2.
>>
>>
>>1. *Take a snapshot of the virtual machine to be backed up -
>>(existing oVirt REST API operation)*
>>2. *Back up the virtual machine configuration at the time of the
>>snapshot (the disk configuration can be backed up as well if needed) -
>>(added capability to oVirt as part of the Backup API)*
>>
>> I can't see any vm configuration anywhere but only the qcow2 disk itself
>>
>>1. *Attach the disk snapshots that were created in (1) to the virtual
>>appliance for data backup - (added capability to oVirt as part of the
>>Backup API)*
>>2.
>> 3. *Detach the disk snapshots that were attached in (4) from the virtual
>>appliance - (added capability to oVirt as part of the Backup API)*
>>
>> An other case is when the vm to backup has more than one disk. After I
>> tested it, I found that only one qcow2 disk is saved on the backup vm. This
>> is really a matter when the original vm has many disks part of lvm, it
>> makes the vm restoration unusable.
>>
>>- About vm restoration, it seems that you are using the upload_disk
>>api, so the disk is uploaded to the pre-defined storage domain, so it is
>>not a real vm restoration.
>>
>> Do you plan to backup and restore a full VM (disks + vm definition) in a
>> next release?
>>
>>
>> I hope it help someone else
>>
>> Regards
>>
>> Victor Acosta
>>
>>
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
>> 
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
> 
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt's VM backup

2017-09-21 Thread Nathanaël Blanchet

Hi Bernardo,

Thanks, I knew this tool, but it is based on sdk3 which will be removed 
in the next version 4.2, so I'm looking at sdk4 project.


You may want to adapt it?


Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :

Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup 



Regards,

Bernardo

PGP Key 
Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet >:


Hello Victor,

I have some questions about your script


Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :

Hello everyone, i created a python tool to backup and restore
oVirt's VMs.

Also i created a little "how to" on my blog:
http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/



  * Backup step is okay, and I get a usable qcow2 image of the
snapshot vm in the backup vm. It seems to be compliant with
the official backup API, except on the step 2.

 1. /Take a snapshot of the virtual machine to be backed up -
(existing oVirt REST API operation)/
 2. /Back up the virtual machine configuration at the time of the
snapshot (the disk configuration can be backed up as well if
needed) - (added capability to oVirt as part of the Backup API)/

I can't see any vm configuration anywhere but only the qcow2 disk
itself

 1. /Attach the disk snapshots that were created in (1) to the
virtual appliance for data backup - (added capability to oVirt
as part of the Backup API)/
 2. /
/
 3. /Detach the disk snapshots that were attached in (4) from the
virtual appliance - (added capability to oVirt as part of the
Backup API)/

An other case is when the vm to backup has more than one disk.
After I tested it, I found that only one qcow2 disk is saved on
the backup vm. This is really a matter when the original vm has
many disks part of lvm, it makes the vm restoration unusable.

  * About vm restoration, it seems that you are using the
upload_disk api, so the disk is uploaded to the pre-defined
storage domain, so it is not a real vm restoration.

Do you plan to backup and restore a full VM (disks + vm
definition) in a next release?



I hope it help someone else

Regards

Victor Acosta




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



-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr   



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





--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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


Re: [ovirt-users] oVirt's VM backup

2017-09-21 Thread Bernardo Juanicó
Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup

Regards,

Bernardo

PGP Key 
Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet :

> Hello Victor,
>
> I have some questions about your script
>
> Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :
>
> Hello everyone, i created a python tool to backup and restore oVirt's VMs.
>
> Also i created a little "how to" on my blog:
> http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>
>
>- Backup step is okay, and I get a usable qcow2 image of the snapshot
>vm in the backup vm. It seems to be compliant with the official backup API,
>except on the step 2.
>
>
>1. *Take a snapshot of the virtual machine to be backed up - (existing
>oVirt REST API operation)*
>2. *Back up the virtual machine configuration at the time of the
>snapshot (the disk configuration can be backed up as well if needed) -
>(added capability to oVirt as part of the Backup API)*
>
> I can't see any vm configuration anywhere but only the qcow2 disk itself
>
>1. *Attach the disk snapshots that were created in (1) to the virtual
>appliance for data backup - (added capability to oVirt as part of the
>Backup API)*
>2.
> 3. *Detach the disk snapshots that were attached in (4) from the virtual
>appliance - (added capability to oVirt as part of the Backup API)*
>
> An other case is when the vm to backup has more than one disk. After I
> tested it, I found that only one qcow2 disk is saved on the backup vm. This
> is really a matter when the original vm has many disks part of lvm, it
> makes the vm restoration unusable.
>
>- About vm restoration, it seems that you are using the upload_disk
>api, so the disk is uploaded to the pre-defined storage domain, so it is
>not a real vm restoration.
>
> Do you plan to backup and restore a full VM (disks + vm definition) in a
> next release?
>
>
> I hope it help someone else
>
> Regards
>
> Victor Acosta
>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
> ___
> 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] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-21 Thread Neil
Further to the logs sent, on the nodes I'm also seeing the following error
under /var/log/messages...

Sep 20 03:43:12 node01 vdsm root ERROR invalid client certificate with
subject "/C=US/O=UKDM/CN=engine01.mydomain.za"^C
Sep 20 03:43:12 node01 vdsm vds ERROR xml-rpc handler
exception#012Traceback (most recent call last):#012  File
"/usr/share/vdsm/BindingXMLRPC.py", line 80, in threaded_start#012
 self.server.handle_request()#012  File
"/usr/lib64/python2.6/SocketServer.py", line 278, in handle_request#012
 self._handle_request_noblock()#012  File
"/usr/lib64/python2.6/SocketServer.py", line 288, in
_handle_request_noblock#012request, client_address =
self.get_request()#012  File "/usr/lib64/python2.6/SocketServer.py", line
456, in get_request#012return self.socket.accept()#012  File
"/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 136,
in accept#012raise SSL.SSLError("%s, client %s" % (e,
address[0]))#012SSLError: no certificate returned, client 10.251.193.5

Not sure if this is any further help in diagnosing the issue?

Thanks, any assistance is appreciated.

Regards.

Neil Wilson.


On Thu, Sep 21, 2017 at 4:31 PM, Neil  wrote:

> Hi Piotr,
>
> Thank you for the reply. After sending the email I did go and check the
> engine one too
>
> [root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/ca.pem -enddate
> -noout
> notAfter=Oct 13 16:26:46 2022 GMT
>
> I'm not sure if this one below is meant to verify or if this output is
> expected?
>
> [root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/private/ca.pem
> -enddate -noout
> unable to load certificate
> 140642165552968:error:0906D06C:PEM routines:PEM_read_bio:no start
> line:pem_lib.c:703:Expecting: TRUSTED CERTIFICATE
>
> My date is correct too Thu Sep 21 16:30:15 SAST 2017
>
> Any ideas?
>
> Googling surprisingly doesn't come up with much.
>
> Thank you.
>
> Regards.
>
> Neil Wilson.
>
> On Thu, Sep 21, 2017 at 4:16 PM, Piotr Kliczewski <
> piotr.kliczew...@gmail.com> wrote:
>
>> Neil,
>>
>> You checked both nodes what about the engine? Can you check engine certs?
>> You can find more info where they are located here [1].
>>
>> Thanks,
>> Piotr
>>
>> [1] https://www.ovirt.org/develop/release-management/features/in
>> fra/pki/#ovirt-engine
>>
>> On Thu, Sep 21, 2017 at 3:26 PM, Neil  wrote:
>> > Hi guys,
>> >
>> > Please could someone assist, my cluster is down and I can't access my
>> vm's
>> > to switch some of them back on.
>> >
>> > I'm seeing the following error in the engine.log however I've checked my
>> > certs on my hosts (as some of the goolge results said to check), but the
>> > certs haven't expired...
>> >
>> >
>> > 2017-09-21 15:09:45,077 ERROR
>> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>> > (DefaultQuartzScheduler_Worker-4) Command
>> GetCapabilitiesVDSCommand(HostName
>> > = node02.mydomain.za, HostId = d2debdfe-76e7-40cf-a7fd-78a0f50f14d4,
>> > vds=Host[node02.mydomain.za]) execution failed. Exception:
>> > VDSNetworkException: javax.net.ssl.SSLHandshakeException: Received
>> fatal
>> > alert: certificate_expired
>> > 2017-09-21 15:09:45,086 ERROR
>> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>> > (DefaultQuartzScheduler_Worker-10) Command
>> > GetCapabilitiesVDSCommand(HostName = node01.mydomain.za, HostId =
>> > b108549c-1700-11e2-b936-9f5243b8ce13, vds=Host[node01.mydomain.za])
>> > execution failed. Exception: VDSNetworkException:
>> > javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> > certificate_expired
>> > 2017-09-21 15:09:48,173 ERROR
>> >
>> > My engine and host info is below...
>> >
>> > [root@engine01 ovirt-engine]# rpm -qa | grep -i ovirt
>> > ovirt-engine-lib-3.4.0-1.el6.noarch
>> > ovirt-engine-restapi-3.4.0-1.el6.noarch
>> > ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch
>> > ovirt-engine-3.4.0-1.el6.noarch
>> > ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch
>> > ovirt-host-deploy-java-1.2.0-1.el6.noarch
>> > ovirt-engine-setup-3.4.0-1.el6.noarch
>> > ovirt-host-deploy-1.2.0-1.el6.noarch
>> > ovirt-engine-backend-3.4.0-1.el6.noarch
>> > ovirt-image-uploader-3.4.0-1.el6.noarch
>> > ovirt-engine-tools-3.4.0-1.el6.noarch
>> > ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch
>> > ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch
>> > ovirt-engine-cli-3.4.0.5-1.el6.noarch
>> > ovirt-engine-setup-base-3.4.0-1.el6.noarch
>> > ovirt-iso-uploader-3.4.0-1.el6.noarch
>> > ovirt-engine-userportal-3.4.0-1.el6.noarch
>> > ovirt-log-collector-3.4.1-1.el6.noarch
>> > ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch
>> > ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch
>> > ovirt-engine-dbscripts-3.4.0-1.el6.noarch
>> > [root@engine01 ovirt-engine]# cat /etc/redhat-release
>> > CentOS release 6.5 (Final)
>> >
>> >
>> > [root@node02 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem
>> -enddate
>> > -noout ; date
>> > notAfter=May 27 

Re: [ovirt-users] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-21 Thread Neil
Hi Piotr,

Thank you for the reply. After sending the email I did go and check the
engine one too

[root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/ca.pem -enddate
-noout
notAfter=Oct 13 16:26:46 2022 GMT

I'm not sure if this one below is meant to verify or if this output is
expected?

[root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/private/ca.pem
-enddate -noout
unable to load certificate
140642165552968:error:0906D06C:PEM routines:PEM_read_bio:no start
line:pem_lib.c:703:Expecting: TRUSTED CERTIFICATE

My date is correct too Thu Sep 21 16:30:15 SAST 2017

Any ideas?

Googling surprisingly doesn't come up with much.

Thank you.

Regards.

Neil Wilson.

On Thu, Sep 21, 2017 at 4:16 PM, Piotr Kliczewski <
piotr.kliczew...@gmail.com> wrote:

> Neil,
>
> You checked both nodes what about the engine? Can you check engine certs?
> You can find more info where they are located here [1].
>
> Thanks,
> Piotr
>
> [1] https://www.ovirt.org/develop/release-management/features/
> infra/pki/#ovirt-engine
>
> On Thu, Sep 21, 2017 at 3:26 PM, Neil  wrote:
> > Hi guys,
> >
> > Please could someone assist, my cluster is down and I can't access my
> vm's
> > to switch some of them back on.
> >
> > I'm seeing the following error in the engine.log however I've checked my
> > certs on my hosts (as some of the goolge results said to check), but the
> > certs haven't expired...
> >
> >
> > 2017-09-21 15:09:45,077 ERROR
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> > (DefaultQuartzScheduler_Worker-4) Command GetCapabilitiesVDSCommand(
> HostName
> > = node02.mydomain.za, HostId = d2debdfe-76e7-40cf-a7fd-78a0f50f14d4,
> > vds=Host[node02.mydomain.za]) execution failed. Exception:
> > VDSNetworkException: javax.net.ssl.SSLHandshakeException: Received fatal
> > alert: certificate_expired
> > 2017-09-21 15:09:45,086 ERROR
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> > (DefaultQuartzScheduler_Worker-10) Command
> > GetCapabilitiesVDSCommand(HostName = node01.mydomain.za, HostId =
> > b108549c-1700-11e2-b936-9f5243b8ce13, vds=Host[node01.mydomain.za])
> > execution failed. Exception: VDSNetworkException:
> > javax.net.ssl.SSLHandshakeException: Received fatal alert:
> > certificate_expired
> > 2017-09-21 15:09:48,173 ERROR
> >
> > My engine and host info is below...
> >
> > [root@engine01 ovirt-engine]# rpm -qa | grep -i ovirt
> > ovirt-engine-lib-3.4.0-1.el6.noarch
> > ovirt-engine-restapi-3.4.0-1.el6.noarch
> > ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch
> > ovirt-engine-3.4.0-1.el6.noarch
> > ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch
> > ovirt-host-deploy-java-1.2.0-1.el6.noarch
> > ovirt-engine-setup-3.4.0-1.el6.noarch
> > ovirt-host-deploy-1.2.0-1.el6.noarch
> > ovirt-engine-backend-3.4.0-1.el6.noarch
> > ovirt-image-uploader-3.4.0-1.el6.noarch
> > ovirt-engine-tools-3.4.0-1.el6.noarch
> > ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch
> > ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch
> > ovirt-engine-cli-3.4.0.5-1.el6.noarch
> > ovirt-engine-setup-base-3.4.0-1.el6.noarch
> > ovirt-iso-uploader-3.4.0-1.el6.noarch
> > ovirt-engine-userportal-3.4.0-1.el6.noarch
> > ovirt-log-collector-3.4.1-1.el6.noarch
> > ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch
> > ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch
> > ovirt-engine-dbscripts-3.4.0-1.el6.noarch
> > [root@engine01 ovirt-engine]# cat /etc/redhat-release
> > CentOS release 6.5 (Final)
> >
> >
> > [root@node02 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem
> -enddate
> > -noout ; date
> > notAfter=May 27 08:36:17 2019 GMT
> > Thu Sep 21 15:18:22 SAST 2017
> > CentOS release 6.5 (Final)
> > [root@node02 ~]# rpm -qa | grep vdsm
> > vdsm-4.14.6-0.el6.x86_64
> > vdsm-python-4.14.6-0.el6.x86_64
> > vdsm-cli-4.14.6-0.el6.noarch
> > vdsm-xmlrpc-4.14.6-0.el6.noarch
> > vdsm-python-zombiereaper-4.14.6-0.el6.noarch
> >
> >
> > [root@node01 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem
> -enddate
> > -noout ; date
> > notAfter=Jun 13 16:09:41 2018 GMT
> > Thu Sep 21 15:18:52 SAST 2017
> > CentOS release 6.5 (Final)
> > [root@node01 ~]# rpm -qa | grep -i vdsm
> > vdsm-4.14.6-0.el6.x86_64
> > vdsm-xmlrpc-4.14.6-0.el6.noarch
> > vdsm-cli-4.14.6-0.el6.noarch
> > vdsm-python-zombiereaper-4.14.6-0.el6.noarch
> > vdsm-python-4.14.6-0.el6.x86_64
> >
> > Please could I have some assistance, I'm rater desperate.
> >
> > Thank you.
> >
> > Regards.
> >
> > Neil Wilson
> >
> >
> >
> > ___
> > 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] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-21 Thread Piotr Kliczewski
Neil,

You checked both nodes what about the engine? Can you check engine certs?
You can find more info where they are located here [1].

Thanks,
Piotr

[1] 
https://www.ovirt.org/develop/release-management/features/infra/pki/#ovirt-engine

On Thu, Sep 21, 2017 at 3:26 PM, Neil  wrote:
> Hi guys,
>
> Please could someone assist, my cluster is down and I can't access my vm's
> to switch some of them back on.
>
> I'm seeing the following error in the engine.log however I've checked my
> certs on my hosts (as some of the goolge results said to check), but the
> certs haven't expired...
>
>
> 2017-09-21 15:09:45,077 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-4) Command GetCapabilitiesVDSCommand(HostName
> = node02.mydomain.za, HostId = d2debdfe-76e7-40cf-a7fd-78a0f50f14d4,
> vds=Host[node02.mydomain.za]) execution failed. Exception:
> VDSNetworkException: javax.net.ssl.SSLHandshakeException: Received fatal
> alert: certificate_expired
> 2017-09-21 15:09:45,086 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-10) Command
> GetCapabilitiesVDSCommand(HostName = node01.mydomain.za, HostId =
> b108549c-1700-11e2-b936-9f5243b8ce13, vds=Host[node01.mydomain.za])
> execution failed. Exception: VDSNetworkException:
> javax.net.ssl.SSLHandshakeException: Received fatal alert:
> certificate_expired
> 2017-09-21 15:09:48,173 ERROR
>
> My engine and host info is below...
>
> [root@engine01 ovirt-engine]# rpm -qa | grep -i ovirt
> ovirt-engine-lib-3.4.0-1.el6.noarch
> ovirt-engine-restapi-3.4.0-1.el6.noarch
> ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch
> ovirt-engine-3.4.0-1.el6.noarch
> ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch
> ovirt-host-deploy-java-1.2.0-1.el6.noarch
> ovirt-engine-setup-3.4.0-1.el6.noarch
> ovirt-host-deploy-1.2.0-1.el6.noarch
> ovirt-engine-backend-3.4.0-1.el6.noarch
> ovirt-image-uploader-3.4.0-1.el6.noarch
> ovirt-engine-tools-3.4.0-1.el6.noarch
> ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch
> ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch
> ovirt-engine-cli-3.4.0.5-1.el6.noarch
> ovirt-engine-setup-base-3.4.0-1.el6.noarch
> ovirt-iso-uploader-3.4.0-1.el6.noarch
> ovirt-engine-userportal-3.4.0-1.el6.noarch
> ovirt-log-collector-3.4.1-1.el6.noarch
> ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch
> ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch
> ovirt-engine-dbscripts-3.4.0-1.el6.noarch
> [root@engine01 ovirt-engine]# cat /etc/redhat-release
> CentOS release 6.5 (Final)
>
>
> [root@node02 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -enddate
> -noout ; date
> notAfter=May 27 08:36:17 2019 GMT
> Thu Sep 21 15:18:22 SAST 2017
> CentOS release 6.5 (Final)
> [root@node02 ~]# rpm -qa | grep vdsm
> vdsm-4.14.6-0.el6.x86_64
> vdsm-python-4.14.6-0.el6.x86_64
> vdsm-cli-4.14.6-0.el6.noarch
> vdsm-xmlrpc-4.14.6-0.el6.noarch
> vdsm-python-zombiereaper-4.14.6-0.el6.noarch
>
>
> [root@node01 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -enddate
> -noout ; date
> notAfter=Jun 13 16:09:41 2018 GMT
> Thu Sep 21 15:18:52 SAST 2017
> CentOS release 6.5 (Final)
> [root@node01 ~]# rpm -qa | grep -i vdsm
> vdsm-4.14.6-0.el6.x86_64
> vdsm-xmlrpc-4.14.6-0.el6.noarch
> vdsm-cli-4.14.6-0.el6.noarch
> vdsm-python-zombiereaper-4.14.6-0.el6.noarch
> vdsm-python-4.14.6-0.el6.x86_64
>
> Please could I have some assistance, I'm rater desperate.
>
> Thank you.
>
> Regards.
>
> Neil Wilson
>
>
>
> ___
> 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] oVirt's VM backup

2017-09-21 Thread Nathanaël Blanchet

Hello Victor,

I have some questions about your script


Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :

Hello everyone, i created a python tool to backup and restore oVirt's VMs.

Also i created a little "how to" on my blog:
http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/


 * Backup step is okay, and I get a usable qcow2 image of the snapshot
   vm in the backup vm. It seems to be compliant with the official
   backup API, except on the step 2.

1. /Take a snapshot of the virtual machine to be backed up - (existing
   oVirt REST API operation)/
2. /Back up the virtual machine configuration at the time of the
   snapshot (the disk configuration can be backed up as well if needed)
   - (added capability to oVirt as part of the Backup API)/

I can't see any vm configuration anywhere but only the qcow2 disk itself

1. /Attach the disk snapshots that were created in (1) to the virtual
   appliance for data backup - (added capability to oVirt as part of
   the Backup API)/
2. /
   /
3. /Detach the disk snapshots that were attached in (4) from the
   virtual appliance - (added capability to oVirt as part of the Backup
   API)/

An other case is when the vm to backup has more than one disk. After I 
tested it, I found that only one qcow2 disk is saved on the backup vm. 
This is really a matter when the original vm has many disks part of lvm, 
it makes the vm restoration unusable.


 * About vm restoration, it seems that you are using the upload_disk
   api, so the disk is uploaded to the pre-defined storage domain, so
   it is not a real vm restoration.

Do you plan to backup and restore a full VM (disks + vm definition) in a 
next release?




I hope it help someone else

Regards

Victor Acosta




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


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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


[ovirt-users] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-21 Thread Neil
Hi guys,

Please could someone assist, my cluster is down and I can't access my vm's
to switch some of them back on.

I'm seeing the following error in the engine.log however I've checked my
certs on my hosts (as some of the goolge results said to check), but the
certs haven't expired...


2017-09-21 15:09:45,077 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler_Worker-4) Command
GetCapabilitiesVDSCommand(HostName = node02.mydomain.za, HostId =
d2debdfe-76e7-40cf-a7fd-78a0f50f14d4, vds=Host[node02.mydomain.za])
execution failed. Exception: VDSNetworkException:
javax.net.ssl.SSLHandshakeException: Received fatal alert:
certificate_expired
2017-09-21 15:09:45,086 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler_Worker-10) Command
GetCapabilitiesVDSCommand(HostName = node01.mydomain.za, HostId =
b108549c-1700-11e2-b936-9f5243b8ce13, vds=Host[node01.mydomain.za])
execution failed. Exception: VDSNetworkException:
javax.net.ssl.SSLHandshakeException: Received fatal alert:
certificate_expired
2017-09-21 15:09:48,173 ERROR

My engine and host info is below...

[root@engine01 ovirt-engine]# rpm -qa | grep -i ovirt
ovirt-engine-lib-3.4.0-1.el6.noarch
ovirt-engine-restapi-3.4.0-1.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch
ovirt-engine-3.4.0-1.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch
ovirt-host-deploy-java-1.2.0-1.el6.noarch
ovirt-engine-setup-3.4.0-1.el6.noarch
ovirt-host-deploy-1.2.0-1.el6.noarch
ovirt-engine-backend-3.4.0-1.el6.noarch
ovirt-image-uploader-3.4.0-1.el6.noarch
ovirt-engine-tools-3.4.0-1.el6.noarch
ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch
ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch
ovirt-engine-cli-3.4.0.5-1.el6.noarch
ovirt-engine-setup-base-3.4.0-1.el6.noarch
ovirt-iso-uploader-3.4.0-1.el6.noarch
ovirt-engine-userportal-3.4.0-1.el6.noarch
ovirt-log-collector-3.4.1-1.el6.noarch
ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch
ovirt-engine-dbscripts-3.4.0-1.el6.noarch
[root@engine01 ovirt-engine]# cat /etc/redhat-release
CentOS release 6.5 (Final)


[root@node02 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -enddate
-noout ; date
notAfter=May 27 08:36:17 2019 GMT
Thu Sep 21 15:18:22 SAST 2017
CentOS release 6.5 (Final)
[root@node02 ~]# rpm -qa | grep vdsm
vdsm-4.14.6-0.el6.x86_64
vdsm-python-4.14.6-0.el6.x86_64
vdsm-cli-4.14.6-0.el6.noarch
vdsm-xmlrpc-4.14.6-0.el6.noarch
vdsm-python-zombiereaper-4.14.6-0.el6.noarch


[root@node01 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -enddate
-noout ; date
notAfter=Jun 13 16:09:41 2018 GMT
Thu Sep 21 15:18:52 SAST 2017
CentOS release 6.5 (Final)
[root@node01 ~]# rpm -qa | grep -i vdsm
vdsm-4.14.6-0.el6.x86_64
vdsm-xmlrpc-4.14.6-0.el6.noarch
vdsm-cli-4.14.6-0.el6.noarch
vdsm-python-zombiereaper-4.14.6-0.el6.noarch
vdsm-python-4.14.6-0.el6.x86_64

Please could I have some assistance, I'm rater desperate.

Thank you.

Regards.

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


Re: [ovirt-users] Restrict a single storage domain for users/roles

2017-09-21 Thread Sandro Bonazzola
2017-09-19 14:29 GMT+02:00 Marco Paolone :

> Hello,
> this is my first message on ML.
>

Welcome aboard!


>
> First off, a short recap: I'm setting up an oVirt test environment based
> on version 4.1.5.2. Once in production, I'm planning to let users access
> the dashboard with a custom role for basic operations (like startup,
> shutdown or creation of  VMs).
>
> For storage domains I'm using both NFS and Cinder, and I'd like to know
> if there's a way to limit, for users, creation of new volumes only on
> Cinder.
>
>
Allon?


>
> Best regards,
> Marco
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

TRIED. TESTED. TRUSTED. 

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


Re: [ovirt-users] CentOS 7.4, qemu 2.9 -> Gluster 3.xx?

2017-09-21 Thread Sandro Bonazzola
2017-09-21 9:19 GMT+02:00 Markus Stockhausen :

> Hi,
>
> given the fact that a current yum update will bring Centos 7.4 and qemu 2.9
> to the nodes I wonder if a gluster update thorugh Ovirt repos is already
> close
> to release? Not only is 3.8 EOL but also I like to minimize the update
> steps to
> a new stable package level.
>

We are planning an upgrade to GlusterFS 3.10 with oVirt 4.2.0.

Sahina, according to
https://www.spinics.net/lists/gluster-users/msg31875.html 3.8 is becoming
EOL since august, any plan to anticipate the move to 3.10 before 4.2.0?



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


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

TRIED. TESTED. TRUSTED. 

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


Re: [ovirt-users] Odp: Re: How to upgrade self-hosted engine?

2017-09-21 Thread Karli Sjöberg
On tor, 2017-09-21 at 13:41 +0200, gabriel_skup...@o2.pl wrote:
> 
> Dnia 21 września 2017 13:20 Johan Bernhardsson 
> napisał(a):
> 2017-09-21 13:08 skrev gabriel_skup...@o2.pl:
> Dnia 20 września 2017 15:54 Kasturi Narra 
> napisał(a):
> 
> Hi,
> 
> upgrade HE (Hosted Engine ) by doing the steps below.
> 
> 1) Move HE to global maintenance by running the command
> 'hosted-engine --set-maintenance --mode=global'
> 
> 2) Add the required repos which has higher package versions.
> 
> 3) Run 'yum update ovirt\*setup\*'
> 
> What if we upgrade all packages by 'yum update'?
> 
> 
> That will break the engine most probably. Since engine-setup does
> more
> than just installing the package. To ensure a safe upgrade follow
> these
> steps.
> 
> Clear.

Well, that´s not entirely true.

It´s like this: engine-setup versionlocks the packages that it wants to
install and keeps them as they are. Updating them is only possible
through engine-setup.

All of the other packages you update like usual with yum
up(date|grade). So by only running engine-setup, you'll leave a lot of
other packages "behind".

So before, or after engine-setup, you also need to yum up(date|grade),
as well. Sh$t may go wrong if you do, then again, sh$t may go wrong if
you don´t :) Best you can do is ask.

/K

> 
> G.
> 
> 
> /Johan
> 
> --
> Security all the way ...
> 
> Linux/CMS/Network/Print/Virtualisation/VoIP Consultant
> 
> Kafit AB
> Orgnr:  556792-5945
> Mobile: +46705111751
> Sweden: +46101993005
> Seychelles: +2486478105
> Uk: +448701821792
> Email:  jo...@kafit.se
> Web:    http://www.kafit.se
> 
> Connect with me on LinkedIn: http://www.linkedin.com/in/smallone
> 
> About me: http://about.me/smallone/bio
> ___
> 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] Odp: Re: How to upgrade self-hosted engine?

2017-09-21 Thread gabriel_skupien
Dnia 21 września 2017 13:20 Johan Bernhardsson jo...@kafit.se 
napisał(a):  2017-09-21 13:08 skrev gabriel_skup...@o2.pl:  Dnia 20 września 
2017 15:54 Kasturi Narra kna...@redhat.com  napisał(a):   Hi,   upgrade 
HE (Hosted Engine ) by doing the steps below.   1) Move HE to global 
maintenance by running the command  hosted-engine --set-maintenance 
--mode=global   2) Add the required repos which has higher package 
versions.   3) Run yum update ovirt\*setup\*   What if we upgrade all 
packages by yum update?That will break the engine most probably. 
Since engine-setup does more  than just installing the package. To ensure a 
safe upgrade follow these  steps.   Clear.   G./Johan   --  Security all 
the way ...   Linux/CMS/Network/Print/Virtua Consultant   Kafit AB  Orgnr:  
556792-5945  Mobile: +46705111751  Sweden: +46101993005  Seychelles: 
+2486478105  Uk: +448701821792  Email:  jo...@kafit.se  Web:     www.kafit.se 
www.kafit.se   Connect with me on LinkedIn:  www.linkedin.com www.linkedin.com  
 About me:  about.me about.me
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Odp: Re: How to upgrade self-hosted engine?

2017-09-21 Thread Johan Bernhardsson

2017-09-21 13:08 skrev gabriel_skup...@o2.pl:

Dnia 20 września 2017 15:54 Kasturi Narra 
napisał(a):


Hi,

upgrade HE (Hosted Engine ) by doing the steps below.

1) Move HE to global maintenance by running the command
'hosted-engine --set-maintenance --mode=global'

2) Add the required repos which has higher package versions.

3) Run 'yum update ovirt\*setup\*'


What if we upgrade all packages by 'yum update'?



That will break the engine most probably. Since engine-setup does more 
than just installing the package. To ensure a safe upgrade follow these 
steps.


/Johan

--
Security all the way ...

Linux/CMS/Network/Print/Virtualisation/VoIP Consultant

Kafit AB
Orgnr:  556792-5945
Mobile: +46705111751
Sweden: +46101993005
Seychelles: +2486478105
Uk: +448701821792
Email:  jo...@kafit.se
Web:http://www.kafit.se

Connect with me on LinkedIn: http://www.linkedin.com/in/smallone

About me: http://about.me/smallone/bio
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Odp: Re: How to upgrade self-hosted engine?

2017-09-21 Thread gabriel_skupien
Dnia 20 września 2017 15:54 Kasturi Narra kna...@redhat.com napisał(a): 
 Hi,      upgrade HE (Hosted Engine ) by doing the steps below.   1) Move HE to 
global maintenance by running the command hosted-engine --set-maintenance 
--mode=global  2) Add the required repos which has higher package 
versions.  3) Run yum update ovirt\*setup\*   What if we upgrade all 
packages by yum update?   4) engine-setup  5) Once the setup is done 
successfully please move HE out of global maintenance mode by running the 
command hosted-engine --set-maintenance --mode=none   For upgrade 
node you can do the steps below:   1) If there is an upgrade link present in 
the General tab of the UI, (if ovirt node) click upgrade from UI 
which will move the host to maintenance and run upgrade on the system, reboots 
and brings it back up to Normal state.   2) If you do not see the upgrade link, 
then add the repos to which you would want to update the node.   3) Run 
yum update   4) Reboot the system.   5) make sure that you are on the 
latest image by running imgbase w if it is a ovirt node.   
6)otherwise just make sure that you are on the latest kernel once your upgrade 
finishes.   THANK YOU!Hope this helps    Thanks  kasturi   On Wed, Sep 
20, 2017 at 6:34 PM,gabriel_skup...@o2.pl  gabriel_skup...@o2.pl 
  wrote:  To be honest, I dont see consistency regarding all that 
upgrade procedures. Have a look here:  www.ovirt.org www.ovirt.org 
documentation/upgrade-guide/ chap-Updating_the_oVirt_ Environment/  It asks to 
update the system too :)   I will appreciate if somebody clearly explains:  -to 
upgrade the Node - please do this and this  -to upgrade the Hosted-Engine - 
please do this and this.   G.   Dnia 20 września 2017 14:52 Johan Bernhardsson 
   jo...@kafit.se  napisał(a):  If you follow that guide it will update 
everything on the virtual server  running the engine. You should not run yum to 
upgrade the packages  (correct me anyone if i am wrong about this)   The 
engine-setup will download and install the packages for you.   And on the nodes 
 upgrade first via the web interface and after that you  can upgrade with yum 
on the nodes. Dont forget to have the node in  maintence mode when you run 
yum update   /Johan  2017-09-20 14:39 skrevgabriel_skup...@o2.pl :  Thanks. 
What about the system itself?   Is yum update enough?   Dnia 20 września 2017 
13:25 Johan Bernhardssonjo...@kafit.se   napisał(a):   Follow this 
guide if it is between minor releaseswww.ovirt.org www.ovirt.org 
documentation/upgrade-guide/ chap-Updates_between_Minor_ Releases/Dont 
forget to send the hosted-engine to global maintenance   /Johan   On September 
20, 2017 13:11:41gabriel_skup...@o2.pl  wrote:   In oVirt Engine Web 
Administration portal I can see option to  upgrade the nodes but cant see 
any option to upgrade  hosted-engine itself?   What is the recommended 
procedure for it?   __ _  Users 
mailing listUsers@ovirt.org  lists.ovirt.org lists.ovirt.org 
mailman/listinfo/users   --  Security all the way ...   
Linux/CMS/Network/Print/ Virtualisation/VoIP Consultant   Kafit AB  Orgnr:  
556792-5945  Mobile: +46705111751  Sweden: +46101993005  Seychelles: 
+2486478105  Uk: +448701821792  Email:     jo...@kafit.se  Web:     
www.kafit.se www.kafit.se   Connect with me on LinkedIn:  www.linkedin.com 
www.linkedin.com smallone   About me:  about.me about.me   
__ _   Users mailing list  
Users@ovirt.orglists.ovirt.org lists.ovirt.org mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] [ANN] oVirt 4.1.7 First Release Candidate is now available

2017-09-21 Thread Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the First
Release Candidate of oVirt 4.1.7, as of September 21st, 2017

This update is the seventh in a series of stabilization updates to the 4.1
series.

Starting from 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a
real performance boost for ovirt when using GlusterFS .
Due  to a known issue [6], using this will break live storage migration.
This is expected to be fixed soon. If you do not use live storage
migration you can give it a try. Use [7] for more details on how to  enable
it.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available[4]
- oVirt Node is already available[4]

Additional Resources:
* Read more about the oVirt 4.1.7 release highlights:
http://www.ovirt.org/release/4.1.7/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1.7/
[4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
[5]
http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/libgfapi/
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562
[7]
http://www.ovirt.org/develop/release-management/features/storage/glusterfs-storage-domain/




-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

TRIED. TESTED. TRUSTED. 

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


[ovirt-users] CentOS 7.4, qemu 2.9 -> Gluster 3.xx?

2017-09-21 Thread Markus Stockhausen
Hi,

given the fact that a current yum update will bring Centos 7.4 and qemu 2.9
to the nodes I wonder if a gluster update thorugh Ovirt repos is already close 
to release? Not only is 3.8 EOL but also I like to minimize the update steps to 
a new stable package level.

Best regards.

Markus

 
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

Über das Internet versandte E-Mails können unter fremden Namen erstellt oder
manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine
rechtsverbindliche Willenserklärung.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 Köln

Vorstand:
Kadir Akin
Dr. Michael Höhnerbach

Vorsitzender des Aufsichtsrates:
Hans Kristian Langva

Registergericht: Amtsgericht Köln
Registernummer: HRB 52 497

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

e-mails sent over the internet may have been written under a wrong name or
been manipulated. That is why this message sent as an e-mail is not a
legally binding declaration of intention.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 Köln

executive board:
Kadir Akin
Dr. Michael Höhnerbach

President of the supervisory board:
Hans Kristian Langva

Registry office: district court Cologne
Register number: HRB 52 497


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