Bug 1404896 - Document Extension Support in OpenShift as it applies to xPaaS Docs
Summary: Document Extension Support in OpenShift as it applies to xPaaS Docs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat xPaaS
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Andrew Burden
QA Contact: Tomas Schlosser
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-15 03:03 UTC by Vikram Goyal
Modified: 2017-07-04 05:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-04 05:51:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLOUD-1741 0 Major Verified [Docs] Document extension support for EAP (and derived) images 2018-01-03 22:22:53 UTC

Description Vikram Goyal 2016-12-15 03:03:22 UTC
* EAP image update - changes for JDV being implemented. EAP 6 image already has these changes, EAP 7 docs update. Ability to pull in external builds and extensions.

* JDV/JDG image - docs side of things - mid Jan/end Jan - big implications of the change - create extensions for the build process - majority of the documentation time might be spent. Rather than extend the image it might allow customers to create extensions directly to make changes in the configurations. Eg. Oracle driver. in the build process.

From email from Kevin:
Rob and Bill worked on this feature recently, it is now available in JDV and will be coming to the other images as we get them scheduled.

There is a template highlighting the mechanism within our repo, it handles both the building of the extension image and its inclusion within the BuildConfig of the quickstart however the idea would be to have customers create their own extensions independently.

This is how the extension image is currently linked, note that there is a bug in OpenShift limiting it to 1 extension however it should be addressed soon if not already through OCP 3.4.

https://github.com/jboss-openshift/application-templates/blob/master/datavirt/datavirt63-extensions-support-s2i.json#L445-L458

This is how the example builds the extension image, it's included in the template for simplicity and expediency.

https://github.com/jboss-openshift/application-templates/blob/master/datavirt/datavirt63-extensions-support-s2i.json#L380-L426

Here is the example extension which includes Derby in the image

https://github.com/jboss-openshift/openshift-quickstarts/tree/master/datavirt/derby-driver-image


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