[ovirt-users] API Snapshot removal ending event

2017-09-24 Thread Lionel Caignec 
Hi,

For snap creation i use a loop like this to know when task is finished:
> snap = snapshots_service.add(types.Snapshot(description=description,
   persist_memorystate=False))
> snap_service = snapshots_service.snapshot_service(snap.id)
>while snap.snapshot_status != types.SnapshotStatus.OK:


is it possible to do the same think for snap deletion? i did not find anything 
in api doc.


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

Re: [ovirt-users] Restoring from backup

2017-09-24 Thread Yedidyah Bar David 
On Sun, Sep 24, 2017 at 10:46 PM, Tyson Landon
 wrote:
> The final setup in restoring a backup has you run engine-setup. When I try
> to run engine-setup I get "[ ERROR ] Failed to execute stage 'Setup
> validation': Hosted Engine setup detected, but Global Maintenance is not
> set."

Which version? This should not happen in 4.1. If earlier, perhaps consider
upgrading? Also check recent thread in this list 'Engine
Backup/Restore Question'.

> I am in Global Maintenance mode however.

You should be in Global maintenance during backup.
During restore, the error you get is based on a test against the
db contents only, not actual processes.

> If I exit Global Maintenance
> the hosted engine reboots every few minutes and it fails liveliness checks.

Right.

> Is there a service i have to stop so that the setup wont think HA is
> running?

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

Re: [ovirt-users] Engine migration and host import

2017-09-24 Thread Ben Bradley 

On 23/09/17 00:27, Ben Bradley wrote:

On 20/09/17 15:41, Simone Tiraboschi wrote:


On Wed, Sep 20, 2017 at 12:30 AM, Ben Bradley > wrote:


Hi All

I've been running a single-host ovirt setup for several months,
having previously used a basic QEMU/KVM for a few years in lab
environments.

I currently have the ovirt engine running at the bare-metal level,
with the box also acting as the single host. I am also running this
with local storage.

I now have an extra host I can use and would like to migrate to a
hosted engine. The following documentation appears to be perfect and
pretty clear about the steps involved:

https://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/ 


 


and

https://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment 


 



However I'd like to try and get a bit more of an understanding of
the process that happens behind the scenes during the cut-over from
one engine to a new/hosted engine.

As an experiment I attempted the following:
- created a new VM within my current environment (bare-metal engine)
- creating an engine-backup
- stopped the bare-metal engine
- restored the backup into the new VM
- ran engine-setup within the new VM
The new engine started up ok and I was able to connect and login to
the web UI. However my host was "unresponsive" and I was unable to
manage it in any way from the VM. I shut the VM down and started the
bare-metal ovirt-engine again on the host and everything worked as
before. I didn't try very hard to make it work however.

The magic missing from the basic process I tried is the
synchronising and importing of the existing host, which is what the
hosted-engine utility does.


No magic up to now: the host are simply in the DB you restored.
If the VM has network connectivity and the same host-name of the old 
machine you shouldn't see any issue.
If you changed the host-name moving to the VM, you should simply run 
engine-rename after the restore.


Thank you for the reply.
I tried this again this evening - again it failed.

The host is present within the new engine but I am unable to manage it.
Host is marked as down but Activate is greyed out. I can get get into 
the "Edit" screen for the host and on right-click I get the following 
options:

- Maintenance
- Confirm Host has been Rebooted
- SSH Management: Restart and Stop both available
The VMs are still running and accessible but are not listed as running 
under the web interface. This time however I did lose access to the 
ovirtmgmt bridge and the web interface, running VMs and host SSH session 
were unavailable until I rebooted.
Luckily I left ovirt-engine service enabled to restart on boot so 
everything came back up.


The engine URL is a CNAME so I just re-pointed to the hostname of the VM 
just before running engine-setup after the restore.


This time though I have kept the new engine VM so I can power it up 
again and try and debug.


I am going to try a few times over the weekend and I have setup serial 
console access so I can do a bit more debugging.


What ovirt logs could I check on the host to see if the new engine VM is 
able to connect and sync to the host properly?


Thanks, Ben


So I tried again to migrate my bare-metal host to a hosted VM but no 
luck. The host remained in unresponsive state in the engine web UI and I 
was unable to manage the host in anyway. Although all VMs continued to run.


I did capture some logs though.
From the new engine VM... engine.log
https://p.bsd-unix.net/view/raw/666839d1

From the host...
mom.log  https://p.bsd-unix.net/view/raw/ac9379f0
supervdsm.log  https://p.bsd-unix.net/view/raw/f9018dec
vdsm.log  https://p.bsd-unix.net/view/raw/bcdcdb13

The engine VM is complaining about being unable to connect to the host, 
though I can see from tcpdump communication is fine. I believe this is 
backed up by the pings seen in mom.log


Though I can see the following in vdsm.log... [vds] recovery: waiting 
for storage pool to go up (clientIF:569)

So I wonder if this is blocking the engine bringing the host up.

The host is running local storage, which I believe is a pretty recent 
addition to ovirt. So I could see how trying to run an engine VM on a 
host's local storage might cause weird issues.


I realise that there won't be HA with this setup, until I create my 
second host and configure HA on the VM.


If I am unable to migrate from bare-metal -> engine VM then it doesn't 
give me any confidence that I would be able to restore a setup from a 
backup onto a bare-metal host and recover host state.


So is the only supported meth

[ovirt-users] Restoring from backup

2017-09-24 Thread Tyson Landon 
The final setup in restoring a backup has you run engine-setup. When I try to 
run engine-setup I get "[ ERROR ] Failed to execute stage 'Setup validation': 
Hosted Engine setup detected, but Global Maintenance is not set." I am in 
Global Maintenance mode however. If I exit Global Maintenance the hosted engine 
reboots every few minutes and it fails liveliness checks. Is there a service i 
have to stop so that the setup wont think HA is running?

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

Re: [ovirt-users] oVirt Node update question

2017-09-24 Thread Yuval Turgeman 
Hi Matthias,

Basically, ovirt-node-ng is shipped as an image, and imgbased then syncs
some files to the new lv so the user will get a new working image without
breaking his configuration.  It could be that some files were sync'ed
across wrong, can you please attache /tmp/imgbased.log ?  Also, which
version are you using now ?

Thanks,
Yuval.


On Fri, Sep 22, 2017 at 4:33 PM, Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:

> Hi Yuval,
>
> i updated my nodes from 4.1.3 to 4.1.6 today and noticed that the
>
> > /etc/yum.repos.d/ovirt-4.1-pre-dependencies.repo
> > /etc/yum.repos.d/ovirt-4.1-pre.repo
>
> files i moved away previously reappeared after rebooting, so i'm getting
> updates to 4.1.7-0.1.rc1.20170919143904.git0c14f08 proposed again.
> obviously i haven't fully understood this "layer" concept of imgbased. the
> practical question for me is: how do i get _permanently_ rid of these files
> in path "/etc/yum.repos.d/"?
>
> thanks
> matthias
>
> Am 2017-08-31 um 16:24 schrieb Yuval Turgeman:
>
>> Yes that would do it, thanks for the update :)
>>
>> On Thu, Aug 31, 2017 at 5:21 PM, Matthias Leopold <
>> matthias.leop...@meduniwien.ac.at > iwien.ac.at>> wrote:
>>
>> Hi,
>>
>> all of the nodes that already made updates in the past have
>>
>> /etc/yum.repos.d/ovirt-4.1-pre-dependencies.repo
>> /etc/yum.repos.d/ovirt-4.1-pre.repo
>>
>> i went through the logs in /var/log/ovirt-engine/host-deploy/ and my
>> own notes and discovered/remembered that this being presented with
>> RC versions started on 20170707 when i updated my nodes from 4.1.2
>> to 4.1.3-0.3.rc3.20170622082156.git47b4302 (!). probably there was a
>> short timespan when you erroneously published a RC version in the
>> wrong repo, my nodes "caught" it and dragged this along until today
>> when i finally cared ;-) I moved the
>> /etc/yum.repos.d/ovirt-4.1-pre*.repo files away and now everything
>> seems fine
>>
>> Regards
>> Matthias
>>
>> Am 2017-08-31 um 15:25 schrieb Yuval Turgeman:
>>
>> Hi,
>>
>> Don't quite understand how you got to that 4.1.6 rc, it's only
>> available in the pre release repo, can you paste the yum repos
>> that are enabled on your system ?
>>
>> Thanks,
>> Yuval.
>>
>> On Thu, Aug 31, 2017 at 4:19 PM, Matthias Leopold
>> > 
>> > >> wrote:
>>
>>  Hi,
>>
>>  thanks a lot.
>>
>>  So i understand everything is fine with my nodes and i'll
>> wait until
>>  the update GUI shows the right version to update (4.1.5 at
>> the moment).
>>
>>  Regards
>>  Matthias
>>
>>
>>  Am 2017-08-31 um 14:56 schrieb Yuval Turgeman:
>>
>>  Hi,
>>
>>  oVirt node ng is shipped with a placeholder rpm
>> preinstalled.
>>  The image-update rpms obsolete the placeholder rpm, so
>> once a
>>  new image-update rpm is published, yum update will pull
>> those
>>  packages.  So you have 1 system that was a fresh
>> install and the
>>  others were upgrades.
>>  Next, the post install script for those image-update
>> rpms will
>>  install --justdb the image-update rpms to the new image
>> (so
>>  running yum update in the new image won't try to pull
>> again the
>>  same version).
>>
>>  Regarding the 4.1.6 it's very strange, we'll need to
>> check the
>>  repos to see why it was published.
>>
>>  As for nodectl, if there are no changes, it won't be
>> updated and
>>  you'll see an "old" version or a version that doesn't
>> seem to be
>>  matching the current image, but it is ok, we are
>> thinking of
>>  changing its name to make it less confusing.
>>
>>  Hope this helps,
>>  Yuval.
>>
>>
>>  On Thu, Aug 31, 2017 at 11:17 AM, Matthias Leopold
>>  > 
>>  > >
>>  > 
>>
>>  > >
>>   hi,
>>
>>   i still don't completely understand the oVirt Node
>> update
>>  process
>>   and the i

Re: [ovirt-users] VM Portal looking for translators

2017-09-24 Thread nicolas 

Hi,

Spanish is currently translated at 100% as well.

Regards.

El 2017-08-14 19:37, Jakub Niedermertl escribió:

Hi all,

new VM Portal project [1] - a replacement of oVirt userportal -  is
looking for community translators. If you know any of

* Chinese (Simplified)
* French
* German
* Italian
* Japanese
* Korean
* Portuguese
* Russian
* Spanish

and want to join translation effort, please

* sign up to Zanata translation environment [2]

* request an access to language group of your choice [3]

* and join us at [4]

Thank you

Regards

Jakub

[1]: https://github.com/oVirt/ovirt-web-ui [1]
[2]: https://translate.zanata.org [2]
[3]: https://translate.zanata.org/language/list [3]
[4]:
https://translate.zanata.org/iteration/view/ovirt-web-ui/1.2.0/languages
[4]


Links:
--
[1] https://github.com/oVirt/ovirt-web-ui
[2] https://translate.zanata.org
[3] https://translate.zanata.org/language/list
[4] 
https://translate.zanata.org/iteration/view/ovirt-web-ui/1.2.0/languages


___
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-24 Thread Yaniv Kaul 
On Sep 21, 2017 7:09 PM, "Nathanaël Blanchet"  wrote:

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.


SDKv3 will not be removed in 4.2.

You may want to adapt it?


Note that you can gradually move to v4. You can mix v4 API with v3 API and
convert function by function.
Y.


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 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
>
>

-- 
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