Bug 1373509

Summary:	New Package Request: virtualbmc
Product:	Red Hat OpenStack	Reporter:	Mike Burns <mburns>
Component:	distribution	Assignee:	Steve Linabery <slinaber>
Status:	CLOSED ERRATA	QA Contact:	Udi Shkalim <ushkalim>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0 (Ocata)	CC:	dbecker, dtantsur, dyasny, kbasil, lmartins, markmc, mburns, morazi, ohochman, rhel-osp-director-maint, slinaber, srevivo, tvignaud
Target Milestone:	Upstream M3	Keywords:	Triaged
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-virtualbmc-0.1.1-0.20161216115645.bd3fca1.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1373468
Clones:	1373511 (view as bug list)		Environment:
Last Closed:	2017-05-17 19:33:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1373511
Bug Blocks:	1373468

Description Mike Burns 2016-09-06 12:56:09 UTC

Cloning for new package request.

+++ This bug was initially created as a clone of Bug #1373468 +++

Upstream Ironic is switching from using pxe_ssh driver to using pxe_ipmitool + a proxy tool called virtualbmc: https://github.com/openstack/virtualbmc. This allows using the same driver for testing and for production. This affects both undercloud and overcloud

Rough work items:
1. Package virtualbmc
2. Create puppet manifests for deploying it
3. Install virtualbmc in undercloud
4. Install virtualbmc in overcloud
5. Switch instack-virt-setup and ooo-quickstart to using it

Comment 1 Steve Linabery 2017-01-12 17:38:33 UTC

https://trunk.rdoproject.org/centos7-master/current/python-virtualbmc-0.1.1-0.20161216115645.bd3fca1.el7.centos.src.rpm to import

Comment 5 errata-xmlrpc 2017-05-17 19:33:34 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-2017:1245