Bug 1117883 - [RFE] Provide Docker image for Keystone
Summary: [RFE] Provide Docker image for Keystone
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-containers
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M2
: 12.0 (Pike)
Assignee: Flavio Percoco
QA Contact: Prasanth Anbalagan
Andrew Burden
URL:
Whiteboard:
Depends On:
Blocks: 1442136 1468938
TreeView+ depends on / blocked
 
Reported: 2014-07-09 15:15 UTC by james labocki
Modified: 2017-12-13 19:14 UTC (History)
13 users (show)

Fixed In Version: openstack-keystone-docker-12.0-20170425.1
Doc Type: Enhancement
Doc Text:
This update provides the Docker image for the Keystone service.
Clone Of:
Environment:
Last Closed: 2017-12-13 19:14:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3457 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Containers Enhancement Advisory 2017-12-14 04:45:51 UTC

Description james labocki 2014-07-09 15:15:39 UTC
This is a request to provide a docker image that provides Keystone's services when run.

Comment 3 Adam Young 2016-01-12 15:25:08 UTC
Until the supported installer makes use of a Docker based system for deploying the OpenStack systems, this is going to be an unsupported and unsupportable configuration.

Is this part of a larger effort?  If so, please identify engineers on that effort that know and understand the Docker toolchain that can produce the base install.  I can provide guidance on how to properly configure the Keystone instance once the image is created.

If not, please close the bug report.

Comment 4 Adam Young 2016-02-09 20:25:18 UTC
I've been looking in to this, and have to suggest we work with the Kolla project on this.  A Keystone stand along image is going to be insufficient; we need a database, and that gets into multi-container orchestration.

Comment 6 Adam Young 2016-12-08 14:19:18 UTC
Reassigning to Tripleo.  The Keystone component will not be responsible for creating its own container, but rather that will be a product of the deployment mechanism.  For now, this should be filed under Tripleo until the container management approach gets better developed.  

The container building infrastructure for Kolla is well developed, and could be used today to do this, but it is unclear whether the Tripleo approach will use that or a comparable mechanism.

Comment 8 Jaromir Coufal 2017-01-11 20:36:03 UTC
Moving to Containers for now.

Comment 10 Red Hat Bugzilla Rules Engine 2017-03-13 04:31:22 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 19 errata-xmlrpc 2017-12-13 19:14:33 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:3457


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