Bug 1032035 - [RFE]re-write auto install function for the cim plugin
Summary: [RFE]re-write auto install function for the cim plugin
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.4.1
Assignee: Ryan Barry
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-19 12:29 UTC by haiyang,dong
Modified: 2014-04-30 11:29 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-30 11:29:09 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 20641 0 master MERGED re-write auto install function for the cim plugin Never

Description haiyang,dong 2013-11-19 12:29:26 UTC 
Description of problem:
Due to cim as plugin package, so need remove auto install configuration functions for the cim plugin from ovirt-init-functions.sh of ovirt-node base iso.
Like "snmp_autoinstall.py" and "puppet_autoinstall.py", re-write auto install function for the cim plugin into "cim_autoinstall.py" to achieve only add 
cim auto install configuration functions for ovirt-node when installing cim plugin package into base iso 


Version-Release number of selected component (if applicable):
ovirt-node-iso-3.1.0-0.999.1222.el6.iso
ovirt-node-plugin-cim-3.1.0-0.999.20131115083921git237de0c.el6.noarch.rpm

How reproducible:
100%

Steps to Reproduce:

Actual results:


Expected results:

Additional info:
Comment 1 Fabian Deutsch 2013-11-28 15:22:47 UTC 
Ryan, can you please review the pending patch
Comment 2 Sandro Bonazzola 2014-02-04 12:39:20 UTC 
re-targeting to 3.3.4 since the attached patch is not merged.
Comment 3 Sandro Bonazzola 2014-03-04 11:02:16 UTC 
this is an automated message.
Moving remaining open bugs targeting 3.3.4 to 3.4.1.
If relevant for 3.3-stable, please reset target version accordingly.
Note You need to log in before you can comment on or make changes to this bug.