Activity log for bug #838238

Date Who What changed Old value New value Message
2011-08-31 16:56:31 Clint Byrum bug added bug
2011-08-31 16:57:17 Clint Byrum bug task added ensemble (Ubuntu)
2011-08-31 17:33:39 Launchpad Janitor ensemble (Ubuntu): status New Confirmed
2011-08-31 17:34:04 Juan L. Negron bug task added cloudfoundry
2011-08-31 17:34:41 Juan L. Negron cloudfoundry: status New Confirmed
2011-08-31 17:35:06 Juan L. Negron bug added subscriber Dustin Kirkland
2011-08-31 17:35:23 Juan L. Negron bug added subscriber Brian Thomason
2011-08-31 17:35:30 Juan L. Negron bug added subscriber Marc Cluet
2011-08-31 17:48:57 Dustin Kirkland  description If you use the version of ensemble in Ubuntu 11.10beta1, it will add the ensemble PPA by default and install the latest version in said PPA on your instances. Likewise if you use the version in Macports. In order to have a predictable environment, ensemble should store its .deb in the provider file storage, and use that for installing itself. For dependencies that don't exist in older releases, a separate PPA should be used, or Ubuntu backports if possible. If you use the version of ensemble in Ubuntu 11.10beta1, it will add the ensemble PPA by default and install the latest version in said PPA on your instances. Likewise if you use the version in Macports. In order to use Ensemble in production, we must be able to have a predictable environment, from the client to all managed nodes. How do we lock an Ensemble-deployed service to a particular version of Ensemble on all of the managed nodes?
2011-08-31 22:32:23 Dustin Kirkland  marked as duplicate 828147