Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1414841 - An xPaaS enabled image to use with oc cluster up
Summary: An xPaaS enabled image to use with oc cluster up
Status: NEW
Alias: None
Product: Container Development Kit (CDK)
Classification: Red Hat
Component: vms
Version: ---
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Lalatendu Mohanty
QA Contact: Ondřej Pták
Robert Krátký
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-19 15:08 UTC by Jeremy Davis
Modified: 2017-02-06 15:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Jeremy Davis 2017-01-19 15:08:03 UTC
Description of problem:
It would be nice to have a Docker image that comes with the xPaaS registry so that customers didn't have to set that up themselves

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Ben Parees 2017-01-19 16:47:07 UTC
What are you defining as the "xpaas registry"?

With 3.4 you can now choose to start oc cluster up with either the centos imagestreams or the rhel imagestreams, if you choose the rhel imagestreams, the xpaas imagestreams will be available, but it does not affect what templates/quickstarts will be available.

Comment 2 Jeremy Davis 2017-01-19 19:50:12 UTC
I would like to have the templates available for EAP, BRMS, etc.  

Is this the flag,
"# Use a different set of images
 oc cluster up --image="registry.example.com/origin" --version="v1.1""

I started 3.4 with the centos7 image stream.  What would I enter for the RHEL image?  

I can move this to documentation if the functionality is already there.


Comment 3 Ben Parees 2017-01-19 19:59:04 UTC
the new flag is 
--image-streams='centos7': Specify which image streams to use, centos7|rhel7

but that won't get you the templates, only the imagestreams.

Comment 4 Jeremy Davis 2017-01-20 14:34:11 UTC
Could we add a flag to pull in imagestreams?

Comment 5 Ben Parees 2017-01-20 14:52:00 UTC
I'd rather not add one off flags just to import additional imagestreams (or templates) when we already have commands to do that (oc create).

it's easy enough to wrap a script around cluster up to import additional artifacts once the cluster is up, if you want to do that.

No to mention the potential maintenance headache if the xpaas team relocates their artifacts (or your cluster up environment doesn't have network connectivity).

Also I believe using the xpaas images requires specific licensing, so making it trivial to use them from oc cluster up means people may use them w/o realizing they are not licensed to do so.

Comment 6 Ben Parees 2017-02-06 15:46:15 UTC
We discussed this and feel that including xPaaS imagestreams and templates makes more sense as a CDK feature than an oc cluster up feature, so we are transferring this RFE to that product/component.

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