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 On Thu, Dec 5, 2013 at 11:33 PM, Antonio Rosales < antonio.rosa...@canonical.com> wrote: > On Thu, Dec 5, 2013 at 2:14 PM, Daniele Stroppa > <daniele.stro...@joyent.com> wrote: > > Thanks Antonio, using a 12.04 box fixed the issue, the shared folder > > /vagrant is accessible. > > Great to hear, and thanks again for the feedback and follow up. > > -Antonio > > > > > Daniele > > > > > > On Thu, Dec 5, 2013 at 7:08 PM, Antonio Rosales > > <antonio.rosa...@canonical.com> wrote: > >> > >> On Thu, Dec 5, 2013 at 9:59 AM, Daniele Stroppa > >> <daniele.stro...@joyent.com> wrote: > >> > Hi Jorge, > >> > > >> > I've tried the Vagrant boxes and they look great. > >> > > >> > However, I'm having a small issue. I've spin up a Saucy (amd64) box, > >> > boots > >> > up fine, I can access the GUI and 'juju status' shows the 'juju-gui' > >> > service > >> > deployed. If I try to deploy my charm from /vagrant (juju deploy > >> > --repository /vagrant/charms local:precise/node-app) it just gets > stuck, > >> > nothing happens and I need to Ctrl-C to go back to the console. Same > >> > happens > >> > if I do a simple 'ls /vagrant'. (This works in a plain Ubuntu box with > >> > Juju > >> > installed). > >> > >> Talking with Ben you may be running into: > >> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1239384 > >> > >> Thus the recommendation is to use a 12.04 vbox image with latest > >> vagrant and current vbox. > >> > >> Let us know if this helps resolve the issue you are seeing, and thanks > >> for the feedback. > >> > >> -thanks, > >> Antonio > >> > >> > > >> > Any suggestions? > >> > > >> > My Environment: > >> > Mac OS X 10.8.5 > >> > VirtualBox 4.2.18 > >> > Vagrant 1.3.3 > >> > > >> > Thanks, > >> > Daniele > >> > > >> > > >> > On Tue, Dec 3, 2013 at 6:04 PM, Jorge O. Castro <jo...@ubuntu.com> > >> > wrote: > >> >> > >> >> Hi everyone, > >> >> > >> >> Ben's been working on providing Vagrant images with Juju built in: > >> >> > >> >> > >> >> > >> >> > http://blog.utlemming.org/2013/12/beta-cross-platform-juju-development.html > >> >> > >> >> This is particularly important for those of you on Windows or OSX we > >> >> share the /vagrant directory, allowing you to quickly hack on your > >> >> charm locally and deploy to running Ubuntu Cloud instances just as > you > >> >> would to a provider. (Except without the cost!) > >> >> > >> >> Please feel free to send feedback to this list! > >> >> > >> >> -- > >> >> Jorge Castro > >> >> Canonical Ltd. > >> >> http://juju.ubuntu.com/ - Automate your Cloud Infrastructure > >> >> > >> >> -- > >> >> Juju mailing list > >> >> Juju@lists.ubuntu.com > >> >> Modify settings or unsubscribe at: > >> >> https://lists.ubuntu.com/mailman/listinfo/juju > >> > > >> > > >> > > >> > -- > >> > Juju mailing list > >> > Juju@lists.ubuntu.com > >> > Modify settings or unsubscribe at: > >> > https://lists.ubuntu.com/mailman/listinfo/juju > >> > > > > > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
