Bug 1179012

Summary:	best practices for creating custom cartridges with multiple versions
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	Documentation	Assignee:	Alex Dellapenta <adellape>
Status:	CLOSED DEFERRED	QA Contact:	brice <bfallonf>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.1.0	CC:	erich, jdetiber, jokerman, libra-bugs, libra-onpremise-devel, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1179006	Environment:
Last Closed:	2016-07-13 14:05:39 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:
Bug Depends On:	1179006
Bug Blocks:

Description Eric Rich 2015-01-05 21:42:56 UTC

+++ This bug was initially created as a clone of Bug #1179006 +++

Use-cases (that I can currently think of):
  a) How should cartridge versioning be handled compared to the software versions provided.
  b) How to properly version software versions, cartridge versions to allow for upgrading with oo-admin-upgrade and automatically upgrade existing gears to the latest software version (the key here is to genericize the software version enough to allow all "minor" upgrades to provide the same version number (the way we currenlty do with ruby-1.8, php-5.4, etc) This should also cover compatible vs. incompatible upgrades (compatible are done online, incompatible require a gear restart).
  c) How to provide multiple versions with the same cartridge manifest, including how to properly obsolete, and remove old versions.