Bug 1179012 - best practices for creating custom cartridges with multiple versions
Summary: best practices for creating custom cartridges with multiple versions
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Alex Dellapenta
QA Contact: brice
URL:
Whiteboard:
Depends On: 1179006
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-05 21:42 UTC by Eric Rich
Modified: 2019-10-10 09:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1179006
Environment:
Last Closed: 2016-07-13 14:05:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.