I think the overwhelming response here amounts to "There be dragons there". I had suspected that what I was doing was potentially dangerous in long running environments.
Thanks for all the information! On Wed, Jan 14, 2015 at 4:29 PM, Charles Butler < [email protected]> wrote: > Greetings, > > I've been running juju 1.21-beta4 for a while now and I haven't altered > any streams information as the announcement email would suggest I need to. > I'm aware of the --upload-tools command and have used it in place of doing > any environments.yaml edits when my bootstraps fail due to finding the > proper streams. > > Now - I dont *really* know whats going on with --upload-tools. I think its > just building the agent from source and shipping it off to my state server > - but what's the implications of doing this on a long running environment? > My environments on day to day use are typically created and destroyed > within a few hours as I move between projects. So i have no scope of > knowledge on what this does when upgrading environments, etc. > > Can someone shed some light as to what I've been doing that *just works* > and why its not the recommended method? > > Thanks! > > -- > All the best, > > Charles Butler <[email protected]> - Juju Charmer > Come see the future of datacenter orchestration: http://jujucharms.com > -- All the best, Charles Butler <[email protected]> - Juju Charmer Come see the future of datacenter orchestration: http://jujucharms.com
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
