Bug 1486249 - [RFE] Introduce Ansible role to set up a VM
Summary: [RFE] Introduce Ansible role to set up a VM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-ansible-roles
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.0
: ---
Assignee: Ondra Machacek
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On: 1462821 1486299
Blocks: 1486577
TreeView+ depends on / blocked
 
Reported: 2017-08-29 10:09 UTC by Martin Perina
Modified: 2019-05-16 13:19 UTC (History)
4 users (show)

Fixed In Version: ovirt-ansible-roles-1.1.0-0.el7ev
Doc Type: Enhancement
Doc Text:
The oVirt.vm-infra Ansible role can be used to automate creating a virtual machine infrastructure.
Clone Of:
: 1486577 (view as bug list)
Environment:
Last Closed: 2018-05-15 17:59:47 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:
pkubica: testing_plan_complete+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1534 0 None None None 2018-05-15 18:00:27 UTC

Description Martin Perina 2017-08-29 10:09:48 UTC 
Description of problem:

Introducing ovirt-vm-infra role which can be used to automate creating a VM. More information can be found at:

https://github.com/oVirt/ovirt-ansible/blob/master/roles/ovirt-vm-infra/README.md

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Petr Kubica 2017-12-19 10:49:07 UTC 
Verified in
ovirt-ansible-vm-infra-1.1.3-1.el7ev.noarch
ansible-2.4.1.0-1.el7ae.noarch
ovirt-ansible-infra-1.1.2-1.el7ev.noarch
ovirt-ansible-image-template-1.1.3-1.el7ev.noarch
ovirt-ansible-cluster-upgrade-1.1.3-1.el7ev.noarch
ovirt-ansible-roles-1.1.2-1.el7ev.noarch
ovirt-ansible-manageiq-1.1.3-1.el7ev.noarch
Comment 7 errata-xmlrpc 2018-05-15 17:59:47 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1534
Comment 8 Franta Kust 2019-05-16 13:08:25 UTC 
BZ<2>Jira Resync
Note You need to log in before you can comment on or make changes to this bug.