Bug 1404896

Summary: Document Extension Support in OpenShift as it applies to xPaaS Docs
Product: Red Hat xPaaS Reporter: Vikram Goyal <vigoyal>
Component: DocumentationAssignee: Andrew Burden <aburden>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Schlosser <tschloss>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: medium    
Version: unspecifiedCC: jlieskov, sgilda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-04 05:51:12 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:
Embargoed:

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
Comment 1 Andrew Burden 2017-07-04 05:51:12 UTC 
These updates have been included in the relevant docs and published on the Portal:

JDV for OpenShift:
https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtualization/6.3/html/red_hat_jboss_data_virtualization_for_openshift/get_started#Preparing-JBoss-Data-Virtualization-Project-Artifacts

EAP for OpenShift:
https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_for_openshift/3/html/red_hat_jboss_enterprise_application_platform_for_openshift/installation_and_configuration#Build-Extensions-Project-Artifacts