Re: Released update to jujucharms.com today the 10th.
On Thu, 11 Dec 2014, Andrew Wilkins wrote: > On Thu, Dec 11, 2014 at 9:30 AM, Andrew Wilkins < > andrew.wilk...@canonical.com> wrote: > > on the landing page the search box kinda washes out a bit. It took me a > little while to find where the search box is... I've had the same thought a couple of times. If you're willing a bug report we can assign Luca, I mean the UX folks :) would be useful and we can get them that feedback from outside folks. -- Rick Harding Juju UI Engineering https://launchpad.net/~rharding @mitechie -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Released update to jujucharms.com today the 10th.
On Thu, Dec 11, 2014 at 3:04 AM, Rick Harding wrote: > Heads up that a new release has hit jujucharms.com. This contains several > smaller things but you might be interested. Please check it out and let us > know if you hit any issues. > > > http://jujugui.wordpress.com/2014/12/10/new-jujucharms-com-release-dec-10th/ > > >- Add blog support. https://jujucharms.com/community/blog >- Fix ‘show more’ revisions link on the details page. >- Correct the bug link in the footer to the correct location. >- Add sorting for search results. >- Redesign the ‘Get started’ page. >- Import loegacy download stats for charms (bundles coming in next >release) >- Improve search results rankings. >- Improve charm icons by auto adding viewbox attribute when missing. >- UI tweaks in the Juju GUI for the Inspector, Canvas, and Machine >View. > > Maybe it's just me, but I thought I should bring this up anyway: on the landing page the > >- Add animations to the Added Services bar interactions. > > > The UI Engineering team. > > -- > 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: Released update to jujucharms.com today the 10th.
Rick and UI team, thanks for getting this fixes in. We had gotten a few questions on download stats so thanks for addressing that and posting here for everyone's info on the fix. -Antonio On Wed, Dec 10, 2014 at 12:04 PM, Rick Harding wrote: > Heads up that a new release has hit jujucharms.com. This contains several > smaller things but you might be interested. Please check it out and let us > know if you hit any issues. > > http://jujugui.wordpress.com/2014/12/10/new-jujucharms-com-release-dec-10th/ > > Add blog support. https://jujucharms.com/community/blog > Fix ‘show more’ revisions link on the details page. > Correct the bug link in the footer to the correct location. > Add sorting for search results. > Redesign the ‘Get started’ page. > Import loegacy download stats for charms (bundles coming in next release) > Improve search results rankings. > Improve charm icons by auto adding viewbox attribute when missing. > UI tweaks in the Juju GUI for the Inspector, Canvas, and Machine View. > Add animations to the Added Services bar interactions. > > > The UI Engineering team. > > -- > 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
[Review Queue] Additional BigData Reviews and Bundle Updates
hdp-pig received the openstack updates https://code.launchpad.net/~asanjar/charms/trusty/hdp-pig/trunk/+merge/242830 hdp-zookeeper was updated to make the cut https://code.launchpad.net/~bigdata-dev/charms/trusty/hdp-zookeeper/trunk/+merge/243358 hdp-storm was also updated with the same networking corrections https://code.launchpad.net/~asanjar/charms/trusty/hdp-storm/trunk/+merge/243352 https://code.launchpad.net/~bigdata-dev/charms/trusty/hdp-storm/trunk/+merge/244212 I also took another look at a proposed charm for the MapR distribution of Hadoop - however it failed deployments on hp-cloud and a bug was filed here: https://bugs.launchpad.net/maprcharm/+bug/1401266 The follow up work has been lodged as merge proposals for the bundles which will need review: https://code.launchpad.net/~bigdata-charmers/charms/bundles/data-analytics-with-pig-latin/bundle/+merge/240855 https://code.launchpad.net/~bigdata-charmers/charms/bundles/high-performance-batch-processing/bundle/+merge/240857 -- All the best, Charles Butler - Juju Charmer Come see the future of datacenter orchestration: http://jujucharms.com -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue] LimeSurvey, Apache2 (precise and trusty)
LimeSurvey: This MP [1] introduces unit tests. The tests run, but the install hook is failing due to an upstream change. The current stable version has changed, and a new download location needs to be added to the charm. +1 to this MP, and I’ve filed a bug [2] against the charm to update the latest stable release. Apache2 (precise and trusty): These MPs add additional SSL security options. The author has addressed all concerns raised by previous reviews. While I did run into two failed tests, I’m confident we’ll see this work promulgated soon. [1] https://code.launchpad.net/~mbruzek/charms/precise/limesurvey/tests/+merge/240950 [2] https://bugs.launchpad.net/charms/+source/limesurvey/+bug/1401267 [3] https://code.launchpad.net/~hloeung/charms/precise/apache2/ssl-security-options/+merge/233877 [4] https://code.launchpad.net/~hloeung/charms/trusty/apache2/ssl-security-options/+merge/233878 -- Adam Israel -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Released update to jujucharms.com today the 10th.
How do we add events to the sidebar on the blog page? We have several coming up. On Wed Dec 10 2014 at 2:04:43 PM Rick Harding wrote: > Heads up that a new release has hit jujucharms.com. This contains several > smaller things but you might be interested. Please check it out and let us > know if you hit any issues. > > > http://jujugui.wordpress.com/2014/12/10/new-jujucharms-com-release-dec-10th/ > > >- Add blog support. https://jujucharms.com/community/blog >- Fix ‘show more’ revisions link on the details page. >- Correct the bug link in the footer to the correct location. >- Add sorting for search results. >- Redesign the ‘Get started’ page. >- Import loegacy download stats for charms (bundles coming in next >release) >- Improve search results rankings. >- Improve charm icons by auto adding viewbox attribute when missing. >- UI tweaks in the Juju GUI for the Inspector, Canvas, and Machine >View. >- Add animations to the Added Services bar interactions. > > > The UI Engineering team. > -- > 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
Released update to jujucharms.com today the 10th.
Heads up that a new release has hit jujucharms.com. This contains several smaller things but you might be interested. Please check it out and let us know if you hit any issues. http://jujugui.wordpress.com/2014/12/10/new-jujucharms-com-release-dec-10th/ - Add blog support. https://jujucharms.com/community/blog - Fix ‘show more’ revisions link on the details page. - Correct the bug link in the footer to the correct location. - Add sorting for search results. - Redesign the ‘Get started’ page. - Import loegacy download stats for charms (bundles coming in next release) - Improve search results rankings. - Improve charm icons by auto adding viewbox attribute when missing. - UI tweaks in the Juju GUI for the Inspector, Canvas, and Machine View. - Add animations to the Added Services bar interactions. The UI Engineering team. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Custom AWS Endpoint / Region
It requires a custom compilation atm, as the list of valid aws endpoints [0] is embedded in a library dependency @ launchpad.net/goamz (the originator of 50+ forks on github). It would be nice to have the endpoints constructed at runtime from its environment.yaml config parameters, the primary issue is that endpoint configuration is typically a bit more indepth even for ec2+s3 then an end user typically would engage with (as an example https://github.com/mitchellh/goamz/blob/master/aws/aws.go). [0] https://github.com/juju/juju/blob/master/provider/ec2/config.go#L123 On Wed, Dec 3, 2014 at 9:06 AM, Michael Hempel wrote: > Hello all, > > > > we are running an internal AWS like cloud and I would like to use Juju to > deploy services. Is there a way to configure a custom AWS like endpoint > which can be used in the environments,yaml? > > > > Any help is much appreciated. > > > > Thanks > > Michael > > -- > 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: juju vs. Puppet/Chef/Salt/Ansible/etc.
On Wed Dec 10 2014 at 10:26:48 AM Eric Snow wrote: > I had tried the explanation route to no avail. I'll probably work up > a demo for the specific folks I have in mind. I think juju is one of > those things that makes more sense when you see it in action. > > One thought I had is that we could work up a demo-in-a-box. Either > make a VM image available (with local provider in it?) or fix local > provider so that it runs entirely in VMs/containers. For the latter > we could distribute a script that spins up the new local provider to > make it super easy for someone to try juju out locally, AKA > juju-in-a-box. > We have most of this already, we spin vagrant images that have the local provider installed, configured, and bootstrapped on vagrant up > -eric > > -- > 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: juju vs. Puppet/Chef/Salt/Ansible/etc.
On Wed, Dec 10, 2014 at 8:28 AM, Marco Ceppi wrote: > On Wed Dec 10 2014 at 10:26:48 AM Eric Snow wrote: >> >> I had tried the explanation route to no avail. I'll probably work up >> a demo for the specific folks I have in mind. I think juju is one of >> those things that makes more sense when you see it in action. >> >> One thought I had is that we could work up a demo-in-a-box. Either >> make a VM image available (with local provider in it?) or fix local >> provider so that it runs entirely in VMs/containers. For the latter >> we could distribute a script that spins up the new local provider to >> make it super easy for someone to try juju out locally, AKA >> juju-in-a-box. > > We have most of this already, we spin vagrant images that have the local > provider installed, configured, and bootstrapped on vagrant up That's great! I may be able to use this with the people I'm talking to. -eric -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju vs. Puppet/Chef/Salt/Ansible/etc.
On Wed Dec 10 2014 at 10:28:41 AM Marco Ceppi wrote: > On Wed Dec 10 2014 at 10:26:48 AM Eric Snow > wrote: > >> I had tried the explanation route to no avail. I'll probably work up >> a demo for the specific folks I have in mind. I think juju is one of >> those things that makes more sense when you see it in action. >> >> One thought I had is that we could work up a demo-in-a-box. Either >> make a VM image available (with local provider in it?) or fix local >> provider so that it runs entirely in VMs/containers. For the latter >> we could distribute a script that spins up the new local provider to >> make it super easy for someone to try juju out locally, AKA >> juju-in-a-box. >> > > We have most of this already, we spin vagrant images that have the local > provider installed, configured, and bootstrapped on vagrant up > Forgot the link! https://juju.ubuntu.com/docs/config-vagrant.html > >> -eric >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/juju >> > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju vs. Puppet/Chef/Salt/Ansible/etc.
On Wed, Dec 10, 2014 at 8:23 AM, Kapil Thangavelu wrote: > On Wed, Dec 10, 2014 at 10:16 AM, Eric Snow wrote: >> It would be great if we could leverage what you've done to be >> more visible to customers. Having similar support for Puppet, Chef, >> and Salt would be awesome too. It's just a matter of justifying the >> resources to get it done... > > michael's done most of the legwork on both ansible and saltstack in > charmhelpers [0], although i'm not aware of any public charms that use the > saltstack support. For chef, the rails charm is a good example [1]. Sweet. I'd missed that. -eric -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju vs. Puppet/Chef/Salt/Ansible/etc.
Thanks for the feedback, Kapil. On Tue, Dec 9, 2014 at 5:03 AM, Kapil Thangavelu wrote: > On Mon, Dec 8, 2014 at 6:35 PM, Eric Snow wrote: >> The reaction I get most often from folks that aren't familiar with >> juju and skim through the juju site is that it looks like a competitor >> to the various configuration management tools out there like Puppet or >> Salt. However, my experience is that while they have some overlap, >> they sit at different layers. > > Agreed. I think the messaging on the sites messaging could use some work, How do we go about doing something about this? >> Have I grown out of touch? Conceivably those projects have or are >> working on juju-like functionality that I'm not aware of. > > They aren't, there's a whole new set of tools though that are working on > orchestration features, though it may be a rather ambiguous term yet, they > still advertise themselves as such. the growth of containers/docker has > reinforced the value of orchesrtation tools since image delivery obviates > most config management, ie. having a bunch of containers that don't talk to > each across nodes other is obviously a problem in want of a a solution > (discovery, connectivity, topology composition) aka orchestration. Very interesting. >> If not (or >> even if so), what's the best way to educate people on what juju is and >> how it will help them when they're already steeped in the lower-layer >> config. management world? > > Explain orchestration as a higher level construct which focuses on services > management via iaas provisioning, service discovery, service automation (db > creation, etc) in a reusable way. Coupled with an ecosystem of service > definitions that offers user composed multi-node solutions. > > Try showing them a deployer config/bundle and ask them to compare to the > comparable lower level tool config. I had tried the explanation route to no avail. I'll probably work up a demo for the specific folks I have in mind. I think juju is one of those things that makes more sense when you see it in action. One thought I had is that we could work up a demo-in-a-box. Either make a VM image available (with local provider in it?) or fix local provider so that it runs entirely in VMs/containers. For the latter we could distribute a script that spins up the new local provider to make it super easy for someone to try juju out locally, AKA juju-in-a-box. >> Related to that, how can we help those same folks wrap all their >> existing recipes, etc. in charms? It's got to be easy enough that >> they can justify the effort. > > michael's reply goes through the most cm tool used in charms, ansible. we've > got production and example charms written with several different tools. > nutshell using cm tools in solo single host with facts/vars fed in via > config, and relations, and executed in place of hooks. Awesome. It seems to me that we could advertise this better. -eric -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju vs. Puppet/Chef/Salt/Ansible/etc.
On Wed, Dec 10, 2014 at 10:16 AM, Eric Snow wrote: > On Mon, Dec 8, 2014 at 5:54 PM, Michael Nelson > wrote: > > In online-services we've been using ansible together with juju for > > quite a while, and have pushed some generic helpers into charm-helpers > > that allow running a hook to equate to running all tasks in a playbook > > tagged with the hook name [1][2]. After using that for over a year, > > we've also developed some reusable ansible roles which make it much > > easier for us to maintain lots of charms, but ymmv (as they're often > > for specific ways which we need to do things, like deploying code from > > a swift container, or setting up nrpe checks etc.) [3] > > > > Using those ansible helpers within juju really won't allow you to > > simply re-use your ansible playbook, but it's pretty easy to adapt an > > ansible playbook to a charm (ie. just tagging tasks for certain > > relations). > > That's pretty cool stuff. Thanks for sharing that (and doing the > work). It would be great if we could leverage what you've done to be > more visible to customers. Having similar support for Puppet, Chef, > and Salt would be awesome too. It's just a matter of justifying the > resources to get it done... > > michael's done most of the legwork on both ansible and saltstack in charmhelpers [0], although i'm not aware of any public charms that use the saltstack support. For chef, the rails charm is a good example [1]. cheers, Kapil [0] http://micknelson.wordpress.com/2013/06/24/easier-juju-charms-with-python-helpers/ [1] https://bazaar.launchpad.net/~charmers/charms/precise/rails/trunk/files -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju vs. Puppet/Chef/Salt/Ansible/etc.
On Mon, Dec 8, 2014 at 5:54 PM, Michael Nelson wrote: > In online-services we've been using ansible together with juju for > quite a while, and have pushed some generic helpers into charm-helpers > that allow running a hook to equate to running all tasks in a playbook > tagged with the hook name [1][2]. After using that for over a year, > we've also developed some reusable ansible roles which make it much > easier for us to maintain lots of charms, but ymmv (as they're often > for specific ways which we need to do things, like deploying code from > a swift container, or setting up nrpe checks etc.) [3] > > Using those ansible helpers within juju really won't allow you to > simply re-use your ansible playbook, but it's pretty easy to adapt an > ansible playbook to a charm (ie. just tagging tasks for certain > relations). That's pretty cool stuff. Thanks for sharing that (and doing the work). It would be great if we could leverage what you've done to be more visible to customers. Having similar support for Puppet, Chef, and Salt would be awesome too. It's just a matter of justifying the resources to get it done... -eric -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
