5.6. Disabling Obsolete Cartridges
Cartridges are updated over time, leaving older versions of a cartridge with fewer advantages. To acknowledge this, cartridges can be marked obsolete in their cartridge manifests. Obsolete cartridges represent technologies, or versions of technologies, for which you do not want developers to be able to deploy new applications or add-on cartridges, but that are still required by the applications already using them.
By default, obsolete cartridges are still available to developers when deploying new applications or add-on cartridges. However, you can disable the use of all obsolete cartridges, preventing developers from using them in these cases. Whether the use of obsolete cartridges is enabled or disabled, applications already using obsolete cartridges continue to function normally and can add new gears using the obsolete cartridges automatically, for example during scaling operations.
Procedure 5.4. To Disable Obsolete Cartridges:
- Ensure the
ALLOW_OBSOLETE_CARTRIDGESparameter in the/etc/openshift/broker.conffile on the broker host is set tofalse:ALLOW_OBSOLETE_CARTRIDGES="false"
- Add the
Obsolete: trueparameter to the/usr/libexec/openshift/cartridges/Cart_Name/metadata/manifest.ymlfile on each node host for any cartridge being marked obsolete:Obsolete: true
- Restart the MCollective service on each node host:
#
service ruby193-mcollective restart - Update the cartridge lists on the broker. For releases prior to OpenShift Enterprise 2.1, run the following command on the broker host to clear the broker cache and, if installed, the Management Console cache:
#
oo-admin-broker-cache --clear --consoleFor OpenShift Enterprise 2.1 and later, run the following commands on the broker host to import the latest cartridge manifests from the nodes and, if installed, clear the Management Console cache:#
oo-admin-ctl-cartridge -c import-profile#oo-admin-console-cache --clear - Restart the broker service:
#
service openshift-broker restart
