Vagrant boxes with Juju now available

John Arbash Meinel john at
Fri Dec 6 17:16:12 UTC 2013

Hash: SHA1

On 2013-12-06 19:35, Daniele Stroppa wrote:
> One more thing I noticed while working on a charm. After a
> debug-hooks session, I modified some files in my local charm repo
> (/vagrant/charms), destroyed the service that was deployed and
> re-deploy it from the local repo with modified files. However, the
> latest changes were not picked up and the charm was still using a
> previous version of the hooks. The only way I've found for juju to
> pick up the latest changes is to destroy the environment and
> bootstrap it again.
> It looks like juju "caches" the content of the /vagrant folder at 
> bootstrap (just a wild guess).
> This happens using both the boxes with Juju built-in or a plain
> Ubuntu box.
> Daniele
You probably want to look at "juju upgrade-charm". When you deploy, we
take the contents of the local repository and zip it up to store in
the environment and deploy from there. You need to "upgrade-charm" to
copy in a new version and tell the system that you want to switch to it.


Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird -


More information about the Juju mailing list