Re: Vagrant boxes with Juju now available
On Thu, Dec 5, 2013 at 2:14 PM, Daniele Stroppa 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 > wrote: >> >> On Thu, Dec 5, 2013 at 9:59 AM, Daniele Stroppa >> 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 >> > 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
Re: Vagrant boxes with Juju now available
Thanks Antonio, using a 12.04 box fixed the issue, the shared folder /vagrant is accessible. 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 > 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 > 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
Re: Vagrant boxes with Juju now available
On Thu, Dec 5, 2013 at 9:59 AM, Daniele Stroppa 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 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
Re: How to make juju aware of IP address changes?
On 04/12/13 17:34, Peter Waller wrote: > This situation is now resolved with thanks to Roger, Gustavo and > others in real time. There is no way we could have resolved it > ourselves since there was corruption of the juju database caused by > running out of disk space, which was unfortunate. We as a team were > not aware that it is necessary to keep a backup of the juju database. Thanks for letting us dive in on it together, Peter. Would it help if Juju could maintain an awareness of the disk situation and gracefully avoid making the problem worse (and avoid corruption) by going read-only when disk is low? Mark -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Let's talk about bundle policy
Hi everyone, If you haven't noticed, the bundles feature is in beta. Bundles are a collection of charms that can be deployed in one go. So instead of deploying individual charms and relating them, you can just share entire environment's worth of charms and relationships and share those with people. Here's an example: https://code.launchpad.net/~jorge/charms/bundles/mediawiki-scalable/bundle and here are the docs for bundles: https://juju.ubuntu.com/docs/charms-bundles.html I've gone ahead and started adding bundle references in both policy and submission documentation (the docs will regenerate with these changes in a few hours): https://juju.ubuntu.com/docs/authors-charm-policy.html Most of the policy things there can apply to charms, however there is one item that I'd like to bring up to discussion. I added: "Bundles must only use charms that are already in the store, the cannot reference charms in personal namespaces" This makes sense to me because an official bundle should only be made out of official charms. Other than that specific bullet there's really nothing special about bundles that isn't covered by existing policy. I've tried to make the policy apply to both instead of having separate bundle and charm policies. (We've had these discussions at UDS and I have a general feel for the consensus of what we discussed and agreed to implement, I am just documenting that here to let people weigh in.) Also, remember that these restrictions are for what we show as part of the official charm store, you can of course, do whatever you want in your personal charm/bundle namespace. -- 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
Re: Vagrant boxes with Juju now available
On Thu, Dec 5, 2013 at 9:59 AM, Daniele Stroppa 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). > > Any suggestions? > > My Environment: > Mac OS X 10.8.5 > VirtualBox 4.2.18 > Vagrant 1.3.3 Thanks for the feedback. We are taking a look and will report back here. -Antonio > > Thanks, > Daniele > > > On Tue, Dec 3, 2013 at 6:04 PM, Jorge O. Castro 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
Re: Vagrant boxes with Juju now available
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). 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 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
New Juju GUI 0.14.0, Juju Quickstart 0.5.0
Here's the content of [our new blog post][1]. -- We are very happy to announce new versions of the Juju GUI and the Juju quickstart plugin. On the GUI, this work represents part of our current drive to make it a more effective day-to-day tool. For example, in the service inspectors, errors are now categorized by type, rather than grouped as “Error”, so you can see at a glance what’s going on. Error details are displayed more clearly and reliably. Services that are in the process of being destroyed don’t disappear immediately, so you can follow along and make sure there aren’t any problems that need your attention. Bundle deployments now give you better feedback so you have some insight into what’s going on. And so on, with other related features and bug fixes. More exciting work in this direction is coming, including long-requested features like per-unit debug logs and local charm deployments! The quickstart plugin is nearing feature completion, and has a lot of nice additions. For new users, if you don’t have Juju installed, after it adds the stable PPA to your system and installs Juju, it will create an environments.yaml file that you need to edit. For everyone, when you run quickstart, it will automatically log into the GUI for you as long as you accept the security certificate in your browser within two minutes of it appearing. We also fixed a bug triggered when your default series was not precise. The next release will guide new users through creating environments.yaml interactively, and then we intend to declare our first quickstart effort to be feature complete. To try out our new releases, existing users can upgrade their GUI charm to juju-gui-81; or run “juju deploy juju-gui && juju expose juju-gui”; or update the juju-quickstart plugin via apt and run “juju quickstart”. New users on Ubuntu can do the following to get everything installed and start an environment with the GUI running and ready: sudo add-apt-repository ppa:juju/stable sudo apt-get update && sudo apt-get install juju-quickstart juju-quickstart ### ...edit ~/.juju/environments.yaml file... ### juju-quickstart Next quickstart release will hopefully remove those last two steps. New users on other operating systems can’t use quickstart right now, but [the Juju installation instructions][2] can get you started, and “juju deploy juju-gui && juju expose juju-gui” can add the GUI to your bootstrapped environment. [More documentation is available][3]! [1]: http://jujugui.wordpress.com/2013/12/05/new-juju-gui-0-14-0-juju-quickstart-0-5-0/ [2]: https://juju.ubuntu.com/install/ [3]: https://juju.ubuntu.com/docs/howto-gui-management.html -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
