Bug 1084001

Summary: [RFE] provision and configure VMs on Foreman using the Foreman provider
Product: [oVirt] ovirt-engine Reporter: Oved Ourfali <oourfali>
Component: RFEsAssignee: Yaniv Bronhaim <ybronhei>
Status: CLOSED WONTFIX QA Contact: movciari
Severity: medium Docs Contact:
Priority: low    
Version: 3.5.0CC: bazulay, bugs, gklein, iheim, lpeer, mgoldboi, rbalakri, Rhev-m-bugs, sherold, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: oourfali: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-29 10:08:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1081371    

Description Oved Ourfali 2014-04-03 11:39:24 UTC
Use the Foreman provider in order to provision and/or configure new VMs.
The provisioning means installing the VM from scratch (PXE boot), whereas configuring means to use oVirt templates as the base OS, and add the host to Foreman for policy/updates post boot.

Comment 1 Red Hat Bugzilla Rules Engine 2015-12-01 15:25:01 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Red Hat Bugzilla Rules Engine 2015-12-01 15:25:01 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Moran Goldboim 2016-11-29 10:08:26 UTC
this integration should probably be done from CFME side.
closing this request for now.