Activity log for bug #1279098

Date Who What changed Old value New value Message
2014-02-11 22:04:33 Viswa Vutharkar bug added bug
2014-02-11 22:09:04 Viswa Vutharkar affects trove trove-integration
2014-02-11 22:10:34 Viswa Vutharkar trove-integration: assignee Viswa Vutharkar (vvutharkar)
2014-02-12 01:01:30 OpenStack Infra trove-integration: status New In Progress
2014-03-02 20:52:34 Viswa Vutharkar description In the function cmd_set_datastore() in redstack, which invokes trove-manage CLI to wire up an image to a specific datastore/version info in trove DB, there is ability to provide 'PACKAGES' string by defining an environment variable. This allows to override the default strings defined inside the function when running "redstack kick-start". This enhancement aims to do the same thing for VERSION string as well, so that someone can do export VERSION="-2.4.9"; export PACKAGES="mongo-server"; redstack kick-start mongodb This will be convenient when people are using redstack kick-start and want to give more flexible names to versions (Especially if they are pointing to an internal ubuntu package repo that pulls a different version during install than what is hardcoded in the redstack script) In the function cmd_set_datastore() in redstack, which invokes trove-manage CLI to wire up an image to a specific datastore/version info in trove DB, there is ability to provide 'PACKAGES' string by defining an environment variable. This allows to override the default strings defined inside the function when running "redstack kick-start". This enhancement aims to do the same thing for Version string as well, so that someone can do export DATASTORE_VERSION="-2.4.9"; export PACKAGES="mongo-server"; redstack kick-start mongodb This will be convenient when people are using redstack kick-start and want to give more flexible names to versions (Especially if they are pointing to an internal ubuntu package repo that pulls a different version during install than what is hardcoded in the redstack script)
2014-03-02 20:53:41 Viswa Vutharkar description In the function cmd_set_datastore() in redstack, which invokes trove-manage CLI to wire up an image to a specific datastore/version info in trove DB, there is ability to provide 'PACKAGES' string by defining an environment variable. This allows to override the default strings defined inside the function when running "redstack kick-start". This enhancement aims to do the same thing for Version string as well, so that someone can do export DATASTORE_VERSION="-2.4.9"; export PACKAGES="mongo-server"; redstack kick-start mongodb This will be convenient when people are using redstack kick-start and want to give more flexible names to versions (Especially if they are pointing to an internal ubuntu package repo that pulls a different version during install than what is hardcoded in the redstack script) In the function cmd_set_datastore() in redstack, which invokes trove-manage CLI to wire up an image to a specific datastore/version info in trove DB, there is ability to provide 'PACKAGES' string by defining an environment variable. This allows to override the default strings defined inside the function when running "redstack kick-start". This enhancement aims to do the same thing for Version string as well, so that someone can do export DATASTORE_VERSION="-2.4.9"; export PACKAGES="mongo-server"; redstack kick-start mongodb This will be convenient when people are using redstack kick-start and want to give more flexible names to versions (Especially if they are pointing to an internal ubuntu package repo that pulls a different version during install than what is hardcoded in the redstack script) Also allows version specific elements pick during image building. (See comment below for further details)
2014-03-02 23:11:40 Viswa Vutharkar summary Allow VERSION string to be specified externally when invoking kick-start Add support for kickstarting different versions of a given datastore
2014-05-09 22:04:44 Nikhil Manchanda trove-integration: importance Undecided Medium
2014-05-09 22:04:46 Nikhil Manchanda trove-integration: milestone juno-1