Re: Currently experiencing outages with jujucharms.com

[Brad Crittenden]

The outage has been resolved and the jujucharms.com site and juju deploys are 
working again. 

Best,

Brad Crittenden


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: New jujucharms.com released -- upgrade to Juju 2.0-beta16 required

[Brad Crittenden]

> On Aug 31, 2016, at 09:14 , Marco Ceppi <marco.ce...@canonical.com> wrote:
> 
> What happened to the charms that were in development channel? Are they now in 
> edge?
> 
> Marco


Yes, they were migrated to edge.

—bac


> 
> 
> On Wed, Aug 31, 2016, 9:06 AM Brad Crittenden <b...@canonical.com> wrote:
> The new version of the charmstore provides support for four channels (edge, 
> beta, candidate, stable). The development channel is now dropped.
> 
> The versions of Juju 2.0 prior to beta 16 only recognized the development and 
> stable channels.
> 
> So if you are using Juju 2.0 it is necessary that you upgrade to beta 16 now.
> 
> More information is available at this blog post:
> 
> https://blog.jujugui.org/2016/08/30/jujucharms-com-updated-with-new-channel-support/
> 
> Best,
> 
> Brad Crittenden
> 
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/juju-dev


-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: New jujucharms.com released -- upgrade to Juju 2.0-beta16 required

[Brad Crittenden]

> On Aug 31, 2016, at 09:14 , Marco Ceppi <marco.ce...@canonical.com> wrote:
> 
> What happened to the charms that were in development channel? Are they now in 
> edge?
> 
> Marco


Yes, they were migrated to edge.

—bac


> 
> 
> On Wed, Aug 31, 2016, 9:06 AM Brad Crittenden <b...@canonical.com> wrote:
> The new version of the charmstore provides support for four channels (edge, 
> beta, candidate, stable). The development channel is now dropped.
> 
> The versions of Juju 2.0 prior to beta 16 only recognized the development and 
> stable channels.
> 
> So if you are using Juju 2.0 it is necessary that you upgrade to beta 16 now.
> 
> More information is available at this blog post:
> 
> https://blog.jujugui.org/2016/08/30/jujucharms-com-updated-with-new-channel-support/
> 
> Best,
> 
> Brad Crittenden
> 
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/juju-dev


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

New jujucharms.com released -- upgrade to Juju 2.0-beta16 required

[Brad Crittenden]

The new version of the charmstore provides support for four channels (edge, 
beta, candidate, stable). The development channel is now dropped.

The versions of Juju 2.0 prior to beta 16 only recognized the development and 
stable channels.

So if you are using Juju 2.0 it is necessary that you upgrade to beta 16 now.

More information is available at this blog post:

https://blog.jujugui.org/2016/08/30/jujucharms-com-updated-with-new-channel-support/

Best,

Brad Crittenden



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

New jujucharms.com released -- upgrade to Juju 2.0-beta16 required

[Brad Crittenden]

The new version of the charmstore provides support for four channels (edge, 
beta, candidate, stable). The development channel is now dropped.

The versions of Juju 2.0 prior to beta 16 only recognized the development and 
stable channels.

So if you are using Juju 2.0 it is necessary that you upgrade to beta 16 now.

More information is available at this blog post:

https://blog.jujugui.org/2016/08/30/jujucharms-com-updated-with-new-channel-support/

Best,

Brad Crittenden



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju should be built with go 1.6

[Brad Crittenden]

> On Aug 22, 2016, at 13:11 , Nate Finch  wrote:
> 
> 
> // This line intentionally does not compile.  This file will only be compiled 
> if
> // you are compiling with a version of Go that is lower than the one we 
> support.
> var requiredGoVersion = This_project_requires_Go_1_6
> 
> 
> If this file is compiled on a version of go that is 1.6 or higher, it'll get 
> excluded from the build, and all will be well. If you compile it on a version 
> of go that is lower than 1.6, you'll get an error like this:
> ./version_canary.go:10: undefined: This_project_requires_Go_1_6
> This is (hopefully) a much clearer error message than something like this:
> ../utils/tls.go:24: undefined: tls.TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
> (which is the error message we used to get if we compiled with an earlier 
> version of go).

Thanks for this Nate. I got caught by this last week when setting up a CI 
machine and it took me a while to figure out.

—Brad


-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: A new development release of Juju, 2.0-beta15, is here!

[Brad Crittenden]

> On Aug 11, 2016, at 20:05 , Nicholas Skaggs <nicholas.ska...@canonical.com> 
> wrote:
> 
> A new development release of Juju, 2.0-beta15, is here!

Juju 2.0 beta 15 has some changes that are incompatible with the previous 
version of the Juju GUI (v 2.1.8).

We have released v 2.1.10 and it is available at 
https://github.com/juju/juju-gui/releases/tag/2.1.10

You can use the GUI with beta 15 by downloading the tar.bz2 from the above 
location and updating your Juju controller.  Assuming you’ve downloaded the GUI 
tarball to your current directory, use the following command:

juju update-gui jujugui-2.1.10.tar.bz2

Best,

Brad Crittenden


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: A new development release of Juju, 2.0-beta15, is here!

[Brad Crittenden]

> On Aug 11, 2016, at 20:05 , Nicholas Skaggs <nicholas.ska...@canonical.com> 
> wrote:
> 
> A new development release of Juju, 2.0-beta15, is here!

Juju 2.0 beta 15 has some changes that are incompatible with the previous 
version of the Juju GUI (v 2.1.8).

We have released v 2.1.10 and it is available at 
https://github.com/juju/juju-gui/releases/tag/2.1.10

You can use the GUI with beta 15 by downloading the tar.bz2 from the above 
location and updating your Juju controller.  Assuming you’ve downloaded the GUI 
tarball to your current directory, use the following command:

juju update-gui jujugui-2.1.10.tar.bz2

Best,

Brad Crittenden


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Missing yaml import for charmhelpers on Xenial?

[Brad Crittenden]

> On Jul 1, 2016, at 11:15 , Pete Vander Giessen 
>  wrote:
> 
> Hi All,
> 
> I ran into an issue making a version of the mariadb charm for Xenial, and 
> wanted to know if others had run into it, and whether we had any best 
> practices or workarounds.
> 
> Mariadb is a non layered charm that uses hooks written in Python. Two of the 
> hooks -- "install' and "config-changed", specifically -- import charmhelpers. 
> Both of those hooks fail on an import error on Xenial, when charmhelpers 
> attempts to import yaml.
> 
> Pyaml isn't part of the Python standard library, but it looks like it is 
> installed by default in the default Python distribution on any given series 
> of Ubuntu. On Xenial, this means that yaml is automatically available to  
> Python 3, but not to Python 2, which is what the scripts were using.
> 
> The solution is either to a) port the install and config-changed hooks to 
> python3, which is what I did while rushing to meet a deadline yesterday, or 
> b) to install yaml in Python 2, which is the simpler solution that seems 
> obvious this morning, after I am no longer worried about deadlines :-)  (Note 
> that solution "a" breaks the charm in trusty, as Python 3 is not the default 
> version of Python for Trusty, and does not have yaml installed by default in 
> that series.)
> 
> I wanted to ping the list to see if anybody had run into similar problems 
> porting charms to Xenial, however. Should I open a ticket against 
> charmhelpers to add pyaml as a dependency? Are there other, better 
> workarounds?

We have run into this problem. Our solution was to make the charms work with 
Python3 on trusty and xenial. The yaml issue was solved by creating a script 
that installs python3-yaml and other required packages before calling our 
python install hook. I can provide an example if you want.

—Brad



-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

jujucharms.com updated

[Brad Crittenden]

Hello,

A few hours ago we updated the services at jujucharms.com. As a result any 
outstanding authentication macaroons were invalidated.  If you experience 
authentication errors you’ll need to logout and log back in again from a 
browser and the charm CLI if you’re using it.

Apologies for the inconvenience.

—Brad


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju charm store currently off-line

[Brad Crittenden]

Right before 18:00 UTC the services were restored.  https://jujucharms.com is 
functioning as normal.

Sorry for the inconvenience.

Best,

Brad Crittenden
Juju UI Engineering



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Juju charm store currently off-line

[Brad Crittenden]

Due to failures of some internal networking equipment, the Juju charm store 
(https://jujucharms.com) is currently off-line.  Our operations team is working 
to resolve the problem.

During the downtime, any action that requires the use of the charm store will 
be affected, such as deploying charms from the charm store.

We apologize for the inconvenience and will send an update when more 
information is known.

Best,

Brad Crittenden
Juju UI Engineering


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: charmstore client authentication(help! :) )

[Brad Crittenden]

> On Apr 8, 2016, at 11:56 , Tom Barber  wrote:
> 
> Hi Martin 
> 
> Thanks for reaching out, a solution to keep me moving would be much 
> appreciated.
> 
> In an ideal world, you guys could delete the f-tom-n charms, they are old 
> duplicates of whats in spicule nothing more, they are also named the same, so 
> you'll have an interesting merge situation on your hands.
> 
> Tom
> 


Hi Tom,

The changes that Martin orchestrated have been applied.  Can you check to see 
if everything is working for you now?

Thanks,

Brad



> --
> 
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316  
> 
> (Thanks to the Saiku community we reached our Kickstart goal, but you can 
> always help by sponsoring the project)
> 
> On 8 April 2016 at 16:54, Martin Hilton  wrote:
> Hi Tom,
> 
> Sorry about this, being locked out if you change your launchpad username is a 
> limitation of the system that we do know about, and are currently 
> investigating how to fix. We can probably update charmstore's databases 
> manually to use the new username, but it will mean that the charms that are 
> currently available in the "~f-tom-n" namespace will have to be accessed 
> using the "~spicule" namespace instead.
> 
> Please let me know if you're happy to proceed?
> 
> Thanks, Martin
> 
> On 8 April 2016 at 12:18, Tom Barber  wrote:
> I'm a company of one currently so it doesn't matter a great deal also I 
> didn't know you could do such a thing on Launchpad :)
> 
> Sorry! Misunderstood, I went looking for a debug method. I got it built but I 
> don't understand go enough to setup the debugger, I just wanted to prod the 
> webservice to see if I could switch the LP block.
> 
> 
> 
> --
> 
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316  
> 
> (Thanks to the Saiku community we reached our Kickstart goal, but you can 
> always help by sponsoring the project)
> 
> On 8 April 2016 at 12:11, Marco Ceppi  wrote:
> While not an answer, I have some hindsight comments. Of you're going to 
> register a company on Launchpad it'd be best to do as a team instead of a 
> user. That way other users could be added and removed from that team without 
> breakage.
> 
> Finally, I pointed you to the gh repo to file bugs, building it is a hair 
> tricky, but basically follows the juju build style. What's in master there is 
> essentially in 2:2.1.0 charm Debian package.
> 
> Marco
> 
> 
> On Fri, Apr 8, 2016, 5:31 AM Tom Barber  wrote:
> (apologies juju-dev moderators, sent this to the wrong place)
> 
> Hi folks, 
> 
> I'm like the guy who just does stuff to annoy developers! :)
> 
> When I registered for launchpad my assigned name was f-tom-n, when I 
> registered a company for Juju related stuff I changed my launchpad ID to 
> spicule.
> 
> Last night I tried to fix my saiku charm because its been sat in the review 
> queue for weeks and finally got looked at, so I made my changes and tried to 
> push it through LP ingestion like usual. Apparently thats basically broken :)
> 
> Anyway, the upshot was, I was told to use the charm push stuff, which I'd 
> been looking forward to for weeks anyway. 
> 
> But there is an issue where by when I authenticate with the charm store it 
> picks up my old f-tom-n name not my new ID, so I can't push my charm to my 
> correct namespace, and ingestion doesn't work, so basically I'm locked out of 
> the charm store.
> 
> Marco pointed me towards the CS client code: 
> https://github.com/juju/charmstore-client so I spent 90 minutes this morning 
> fumbling around trying to work out how to build it, which I finally sussed, 
> but then I can't figure out how to debug it, I'm' not a golang guy and and 
> sadly I have a day job. I'm happy to investigate further, but I suspect 
> someone who knows probably has a much quicker answer/fix than I do.
> 
> I raised a bug(https://launchpad.net/bugs/1567690) but figured it was worth 
> mentioning on here as well.
> 
> Moral of the story, don't change your launchpad ID!
> 
> Thanks
> 
> Tom
> --
> 
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316  
> 
> (Thanks to the Saiku community we reached our Kickstart goal, but you can 
> always help by sponsoring the project)
> --
> 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


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

jujucharms.com updated

[Brad Crittenden]

Hello,

Yesterday the Juju UI Engineering team updated jujucharms.com with some 
improvements we hope you find interesting and useful.  The highlights are:

* Improved getting started page (https://jujucharms.com/get-started)

The Juju installation instructions have been re-written to be more 
straightforward and the page is more welcoming.

* Community cards (https://jujucharms.com/community/cards)

In order to allow charm and bundle authors an engaging way to promote their 
work, we’ve introduced cards, a slug of Javascript and HTML that can be 
embedded into a web site which will then serve a visual representation of the 
charm or bundle. The details are fetched from our servers so the data will 
always be up-to-date.  Change your bundle and the representation of it on your 
blog will be updated for future visitors.

Madison has written a blog post demonstrating their use at 
http://writing.drab-makyo.com/posts/tech/2016/03/02/cards/

Note that this first implementation is Javascript-based and therefore will not 
work in every environment, specifically platforms that block the use of 
embedded Javascript.

* Improved topic pages (e.g. https://jujucharms.com/big-data)

A cleaner design utilizing the cards for each bundle presented.

* Charm labeling on bundle visualisations.

Previously the rendered image for a bundle only showed the service icons which 
could be confusing as there was no way to intuit the role each service played. 
Now we are labeling each service with the custom name so you can easily 
identify master/slave relationships, for example.

If you have questions or comments on these changes, you can find us in 
#juju-gui on Freenode or respond here.

If you find a bug please file it at 
https://github.com/CanonicalLtd/jujucharms.com/issues

Best,

Brad Crittenden
Juju UI Engineering


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju