[ovirt-users] Import an exported VM using Ansible

2020-01-15 Thread paolo
Hello everybody!

I'm trying to automate a copy of a VM from one Datacenter to another using an 
Ansible.playbook.

I'm able to:
- Create a snapshot of the source VM
- create a clone from the snapshot
- remove the snapshot
- attach an Export Domain
- export the clone to the Export Domain
- remove the clone
- detach the Export domain from the source Datacenter and attach to the 
destination.

Unfortunately I cannot find a module to:
- import the VM from the Export Domain
- delete the VM image from the Export Domain.

Any hint on how to do that?

Thanks in advance. Cheers.

Paolo


PS: if someone is interested I can share the playbook.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QMFXXQFYYW6SJ43QO6W44IQZ2M3V2WU2/


[ovirt-users] Re: upgrade issue

2020-01-15 Thread Jingjie Jiang

Hi Paul,

Thanks for your reply.

I did install ovirt-release43 before I install the 
ovirt-node-ng-image-update package.



Here is the brief procedure:

1. Install the 4.2.8 ovirt host on CentOS7.6 by adding the node from 
AdminPortal.


2. Upgrade ovirt 4.2.8 engine to 4.3.6.

3. Set the host to maintainence from AdminPortal.

4. Yum install ovirt-release43 rpm

    # yum install 
http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm


5.Yum install node update package

   # yum install 
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.6-1.el7.noarch.rpm


6. reboot


vdsm did not get update.


-Jingjie


On 1/15/20 6:14 AM, Staniforth, Paul wrote:
Hel# yum install 
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.6-1.el7.noarch.rpmlo 
Jingjie,
   I think you need to install 
https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm 
 
so yum updates to the 4.3 release otherwise it will stay on the 4.2 
release (4.2.8 being the last version).



Regards,
   Paul S.

*From:* Jingjie Jiang 
*Sent:* 14 January 2020 15:30
*To:* Parth Dhanjal 
*Cc:* users 
*Subject:* [ovirt-users] Re: upgrade issue

*Caution External Mail:* Do not click any links or open any 
attachments unless you trust the sender and know that the content is safe.


Hi Path,

Thanks for your rely.

Please check my inline comments

-Jingjie

On 1/14/20 2:28 AM, Parth Dhanjal wrote:

Hello Jingjie!

You can follow 
https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_to_oVirt_4.2.html 



I tried the above link before and it worked.

But, I'd like to know how  the upgrade with ovirt-node-ng-image-update 
package works.


Any suggestion about the issue I reported in previous email?

Also, about the link you pointed, "imgbase check" command crashed when 
I ran from the ovirt host based on CentOS:


# imgbase check
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/lib/python2.7/site-packages/imgbased/__main__.py", line 
53, in 

    CliApplication()
  File "/usr/lib/python2.7/site-packages/imgbased/__init__.py", line 
82, in CliApplication

    app.hooks.emit("post-arg-parse", args)
  File "/usr/lib/python2.7/site-packages/imgbased/hooks.py", line 120, 
in emit

    cb(self.context, *args)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", 
line 185, in post_argparse

    run_check(app)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", 
line 225, in run_check

    status = Health(app).status()
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", 
line 358, in status

    status.results.append(group().run())
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", 
line 385, in check_thin

    pool = self.app.imgbase._thinpool()
  File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 
120, in _thinpool

    return LVM.Thinpool.from_tag(self.thinpool_tag)
  File "/usr/lib/python2.7/site-packages/imgbased/lvm.py", line 227, 
in from_tag

    assert len(lvs) == 1
AssertionError




Under this link you can find a tab to upgrade the hosts. Instead of
https://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm 
 
You can use 
https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm 



Regards
Par

[ovirt-users] Re: Power management and storage domains error when running Ansible tasks!

2020-01-15 Thread Alex K
Hi,

On Tue, Jan 14, 2020 at 7:51 PM  wrote:

> I don't have power management devices on the Intel NUC. You probably
> missed the message where I posted this because of
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4WRVQKDASO7YORTR24UINCHVGAWWXU4T/
> .
>

For production you will need hardware that supports power management
(either the servers or external device, like UPS). In case you need just to
test ovirt with power management, you can setup software power management
on the hypervisor, where the ovirt nodes will be hosted as nested. I had
luck with following approach:

Assumption:
Baremetal: the host where nested KVM is setup.
Ovirt VMs: CentOS7-ovirt0, CentOS7-ovirt1

[root@baremetal ~]# yum install python-pip -y
[root@baremetal ~]# yum install -y zeromq-devel
[root@baremetal ~]# yum install -y gcc python-devel libvirt-devel
[root@baremetal ~]# firewall-cmd --permanent --zone=public
--add-port=623-624/udp
[root@baremetal ~]# firewall-cmd --reload
[root@baremetal ~]# vbmc add CentOS7-ovirt0 --username root --password
yourpass --port 623
[root@baremetal ~]# vbmc add CentOS7-ovirt1 --username root --password
yourpass --port 624

[root@baremetal ~]# vbmc list
+++-+--+
| Domain name| Status | Address | Port |
+++-+--+
| CentOS7-ovirt0 | down   | ::  |  623 |
| CentOS7-ovirt1 | down   | ::  |  624 |
+++-+--+

[root@baremetal ~]# vbmc start CentOS7-ovirt0
2019-10-16 18:44:57,397.397 26596 INFO VirtualBMC [-] Started vBMC instance
for domain CentOS7-ovirt0
[root@baremetal ~]# vbmc start CentOS7-ovirt1
2019-10-16 18:45:38,056.056 26596 INFO VirtualBMC [-] Started vBMC instance
for domain CentOS7-ovirt1
[root@baremetal ~]# vbmc list
++-+-+--+
| Domain name| Status  | Address | Port |
++-+-+--+
| CentOS7-ovirt0 | running | ::  |  623 |
| CentOS7-ovirt1 | running | ::  |  624 |
++-+-+--+

at node0 host (VM) check:
ipmitool -I lanplus -U root -P yourpass -H  power status
(default port is 623)
ipmitool -I lanplus -U root -P yourpass -H  power status
-p 624

at ovirt GUI you need lanplus=1,-p623 and lanplus=1,-p624 options for each
host.

___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SBA4MTQT62YFIGOLLBRQDEGYCDDDQYOU/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ENR5EYVELCNWVHZON63MZHG6J2RCQXOX/


[ovirt-users] Re: upgrade issue

2020-01-15 Thread Staniforth, Paul
Hi Jingjie,

  If you have a node installed using ovirt-node-ng it created a 
thin LVM pool and ovirt-node-ng-image-update creates a new LVM layer so you 
have 2 versions of the node that you can switch between.


Regards,
  Paul S.

From: Jingjie Jiang 
Sent: 14 January 2020 15:30
To: Parth Dhanjal 
Cc: users 
Subject: [ovirt-users] Re: upgrade issue


Caution External Mail: Do not click any links or open any attachments unless 
you trust the sender and know that the content is safe.

Hi Path,

Thanks for your rely.

Please check my inline comments

-Jingjie

On 1/14/20 2:28 AM, Parth Dhanjal wrote:
Hello Jingjie!

You can follow 
https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_to_oVirt_4.2.html

I tried the above link before and it worked.

But, I'd like to know how  the upgrade with ovirt-node-ng-image-update package 
works.

Any suggestion about the issue I reported in previous email?

Also, about the link you pointed, "imgbase check" command crashed when I ran 
from the ovirt host based on CentOS:

# imgbase check
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/site-packages/imgbased/__main__.py", line 53, in 

CliApplication()
  File "/usr/lib/python2.7/site-packages/imgbased/__init__.py", line 82, in 
CliApplication
app.hooks.emit("post-arg-parse", args)
  File "/usr/lib/python2.7/site-packages/imgbased/hooks.py", line 120, in emit
cb(self.context, *args)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 185, 
in post_argparse
run_check(app)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 225, 
in run_check
status = Health(app).status()
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 358, 
in status
status.results.append(group().run())
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 385, 
in check_thin
pool = self.app.imgbase._thinpool()
  File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 120, in 
_thinpool
return LVM.Thinpool.from_tag(self.thinpool_tag)
  File "/usr/lib/python2.7/site-packages/imgbased/lvm.py", line 227, in from_tag
assert len(lvs) == 1
AssertionError




Under this link you can find a tab to upgrade the hosts. Instead of
https://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
 You can use 
https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

Regards
Parth Dhanjal

On Mon, Jan 13, 2020 at 11:44 PM 
mailto:jingjie.ji...@oracle.com>> wrote:
Hello,

By following the instruction at 
https://www.ovirt.org/documentation/upgrade-guide/appe-Manually_Updating_Hosts.html,
 I tried to upgrade host from 4.2.8(CentOS 7.6) to 4.3.7.
After the reboot, the host still running 4.2.8 vdsm.
 # rpm -qa | grep vdsm
vdsm-common-4.20.46-1.el7.noarch
vdsm-yajsonrpc-4.20.46-1.el7.noarch
vdsm-hook-vhostmd-4.20.46-1.el7.noarch
vdsm-4.20.46-1.el7.x86_64
vdsm-client-4.20.46-1.el7.noarch
vdsm-python-4.20.46-1.el7.noarch
vdsm-hook-fcoe-4.20.46-1.el7.noarch
vdsm-network-4.20.46-1.el7.x86_64
vdsm-jsonrpc-4.20.46-1.el7.noarch
vdsm-hook-vmfex-dev-4.20.46-1.el7.noarch
vdsm-http-4.20.46-1.el7.noarch
vdsm-api-4.20.46-1.el7.noarch
vdsm-hook-ethtool-options-4.20.46-1.el7.noarch
vdsm-hook-openstacknet-4.20.46-1.el7.noarch
[root@ovs260 ~]#


Looks like the upgrade did

[ovirt-users] Re: upgrade issue

2020-01-15 Thread Staniforth, Paul
Hello Jingjie,
   I think you need to install 
https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
 so yum updates to the 4.3 release otherwise it will stay on the 4.2 release 
(4.2.8 being the last version).


Regards,
   Paul S.

From: Jingjie Jiang 
Sent: 14 January 2020 15:30
To: Parth Dhanjal 
Cc: users 
Subject: [ovirt-users] Re: upgrade issue


Caution External Mail: Do not click any links or open any attachments unless 
you trust the sender and know that the content is safe.

Hi Path,

Thanks for your rely.

Please check my inline comments

-Jingjie

On 1/14/20 2:28 AM, Parth Dhanjal wrote:
Hello Jingjie!

You can follow 
https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_to_oVirt_4.2.html

I tried the above link before and it worked.

But, I'd like to know how  the upgrade with ovirt-node-ng-image-update package 
works.

Any suggestion about the issue I reported in previous email?

Also, about the link you pointed, "imgbase check" command crashed when I ran 
from the ovirt host based on CentOS:

# imgbase check
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/site-packages/imgbased/__main__.py", line 53, in 

CliApplication()
  File "/usr/lib/python2.7/site-packages/imgbased/__init__.py", line 82, in 
CliApplication
app.hooks.emit("post-arg-parse", args)
  File "/usr/lib/python2.7/site-packages/imgbased/hooks.py", line 120, in emit
cb(self.context, *args)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 185, 
in post_argparse
run_check(app)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 225, 
in run_check
status = Health(app).status()
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 358, 
in status
status.results.append(group().run())
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 385, 
in check_thin
pool = self.app.imgbase._thinpool()
  File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 120, in 
_thinpool
return LVM.Thinpool.from_tag(self.thinpool_tag)
  File "/usr/lib/python2.7/site-packages/imgbased/lvm.py", line 227, in from_tag
assert len(lvs) == 1
AssertionError




Under this link you can find a tab to upgrade the hosts. Instead of
https://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
 You can use 
https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

Regards
Parth Dhanjal

On Mon, Jan 13, 2020 at 11:44 PM 
mailto:jingjie.ji...@oracle.com>> wrote:
Hello,

By following the instruction at 
https://www.ovirt.org/documentation/upgrade-guide/appe-Manually_Updating_Hosts.html,
 I tried to upgrade host from 4.2.8(CentOS 7.6) to 4.3.7.
After the reboot, the host still running 4.2.8 vdsm.
 # rpm -qa | grep vdsm
vdsm-common-4.20.46-1.el7.noarch
vdsm-yajsonrpc-4.20.46-1.el7.noarch
vdsm-hook-vhostmd-4.20.46-1.el7.noarch
vdsm-4.20.46-1.el7.x86_64
vdsm-client-4.20.46-1.el7.noarch
vdsm-python-4.20.46-1.el7.noar