Bug 1373509 - New Package Request: virtualbmc
Summary: New Package Request: virtualbmc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: distribution
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Upstream M3
: 11.0 (Ocata)
Assignee: Steve Linabery
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On: 1373511
Blocks: 1373468
TreeView+ depends on / blocked
 
Reported: 2016-09-06 12:56 UTC by Mike Burns
Modified: 2017-05-17 19:33 UTC (History)
13 users (show)

Fixed In Version: python-virtualbmc-0.1.1-0.20161216115645.bd3fca1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1373468
: 1373511 (view as bug list)
Environment:
Last Closed: 2017-05-17 19:33:34 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1245 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 Bug Fix and Enhancement Advisory 2017-05-17 23:01:50 UTC

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 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


Note You need to log in before you can comment on or make changes to this bug.