Adds support to override VERSION string via env var
Just like PACKAGES string can be overridden by supplying value via
defining the environment variable prior to running redstack kick-start,
the same facility is now extended to VERSION string as well.
If the VERSION is not defined as env var, then the behavior is
default. The code changes do not in any way alter the
default behavior
You may also want to set PACKAGES=" ", to prevent the triggering
of Package update at guestagent prepare() time if you are
already prebaking the required version you are interested in,
into the dib image itself. The PACKAGES update at guestagent
prepare() time is partially broken and you may want to avoid
that path to get the desired version of your datastore installed
and instead choose this VERSION string export mechanism
This allows 3 things
1) Specify the elements for your specific datastore version
(:eg mongodb 2.4.9) to be picked by dib from the location scripts/files/elements/ubuntui-mongodb-2.4.9 rather than
the default scripts/files/elements/ubuntui-mongodb when
no VERSION is specified. This allows you for example to
define a different install.d/* element for your specific
datastore version if it is different from default
2) when redstack invokes trove-manage to register the
glance image with specific version in trove DB it will
set the version for eg as 'mongodb-2.4.9'
3) Also if you are taking advantage of dib tools or redstack
kick-start in trove-integration to build your internal
company specific image/version of your datastore and
want to point these tools at your custom elements that
might be installing packages from custom (non distro
standard ) repos, then this change allows you to do
so without impacting the standard behavior for the
opensource trove-integration project
The git review submission
Adds support to override VERSION string via env var
Just like PACKAGES string can be overridden by supplying value via
defining the environment variable prior to running redstack kick-start,
the same facility is now extended to VERSION string as well.
If the VERSION is not defined as env var, then the behavior is
default. The code changes do not in any way alter the
default behavior
USAGE: export VERSION="-2.4.9"; redstack kick-start mongodb
You may also want to set PACKAGES=" ", to prevent the triggering
of Package update at guestagent prepare() time if you are
already prebaking the required version you are interested in,
into the dib image itself. The PACKAGES update at guestagent
prepare() time is partially broken and you may want to avoid
that path to get the desired version of your datastore installed
and instead choose this VERSION string export mechanism
This allows 3 things
scripts/ files/elements/ ubuntui- mongodb- 2.4.9 rather than files/elements/ ubuntui- mongodb when
1) Specify the elements for your specific datastore version
(:eg mongodb 2.4.9) to be picked by dib from the location
the default scripts/
no VERSION is specified. This allows you for example to
define a different install.d/* element for your specific
datastore version if it is different from default
2) when redstack invokes trove-manage to register the
glance image with specific version in trove DB it will
set the version for eg as 'mongodb-2.4.9'
3) Also if you are taking advantage of dib tools or redstack
kick-start in trove-integration to build your internal
company specific image/version of your datastore and
want to point these tools at your custom elements that
might be installing packages from custom (non distro
standard ) repos, then this change allows you to do
so without impacting the standard behavior for the
opensource trove-integration project