Re: charmstore client authentication(help! :) )

[Tom Barber]

Legendary! Thanks guys, seems to be happily pushing to the charm store now.

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
)

On 8 April 2016 at 20:10, Brad Crittenden  wrote:

>
> > 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
> >

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

Re: charmstore client authentication(help! :) )

[Tom Barber]

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

--

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://l

Re: charmstore client authentication(help! :) )

[Martin Hilton]

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

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

[Mark Shuttleworth]

On 08/04/16 15:03, Pete Vander Giessen wrote:
> @Charles: Aha! The various destroy commands don't have a --force flag; I
> didn't know about the "remove-machine" command, which does accept --force.
>
> That seemed to work. Thank you :-)
>

We should definitely clean that up in 2.0 final.

Mark

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

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

[Charles Butler]

Happy to help! Glad it got you sorted.

All the best 

> On Apr 8, 2016, at 10:03 AM, Pete Vander Giessen  wrote:
> 
> @Charles: Aha! The various destroy commands don't have a --force flag; I 
> didn't know about the "remove-machine" command, which does accept --force.
> 
> That seemed to work. Thank you :-)
> 
> ~ PeteVG
> 
>> On Fri, Apr 8, 2016 at 9:47 AM Charles Butler  
>> wrote:
>> I haven't validated this but you can try to remove the machine forcibly
>> 
>> Juju remove-machine ## --force
>> 
>> That should force removal of the container from the controller and let you 
>> destroy-service to remove it from the model.
>> 
>> 
>> 
>> > On Apr 8, 2016, at 8:56 AM, Pete Vander Giessen  wrote:
>> >
>> > Hi All,
>> >
>> > Let's say that someone (okay, me) is experimenting with juju2 (develop) 
>> > locally, and I've rudely destroyed an lxc container that had a juju charm 
>> > deployed to it (lxc stop  && lxc delete ).
>> >
>> > Is there a way to convince juju that the charm is no longer deployed? juju 
>> > destroy-service and juju destroy-unit both fail, because juju cannot 
>> > connect to the machine. Is there a way, short of clobbering 
>> > ~/.local/shrare/juju and attempting to start from scratch, of making juju 
>> > let go of the charm?
>> >
>> > Thank you in advance,
>> >
>> > ~ PeteVG
>> > --
>> > 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: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

[Pete Vander Giessen]

@Charles: Aha! The various destroy commands don't have a --force flag; I
didn't know about the "remove-machine" command, which does accept --force.

That seemed to work. Thank you :-)

~ PeteVG

On Fri, Apr 8, 2016 at 9:47 AM Charles Butler 
wrote:

> I haven't validated this but you can try to remove the machine forcibly
>
> Juju remove-machine ## --force
>
> That should force removal of the container from the controller and let you
> destroy-service to remove it from the model.
>
>
>
> > On Apr 8, 2016, at 8:56 AM, Pete Vander Giessen 
> wrote:
> >
> > Hi All,
> >
> > Let's say that someone (okay, me) is experimenting with juju2 (develop)
> locally, and I've rudely destroyed an lxc container that had a juju charm
> deployed to it (lxc stop  && lxc delete ).
> >
> > Is there a way to convince juju that the charm is no longer deployed?
> juju destroy-service and juju destroy-unit both fail, because juju cannot
> connect to the machine. Is there a way, short of clobbering
> ~/.local/shrare/juju and attempting to start from scratch, of making juju
> let go of the charm?
> >
> > Thank you in advance,
> >
> > ~ PeteVG
> > --
> > 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: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

[Charles Butler]

I haven't validated this but you can try to remove the machine forcibly

Juju remove-machine ## --force

That should force removal of the container from the controller and let you 
destroy-service to remove it from the model.



> On Apr 8, 2016, at 8:56 AM, Pete Vander Giessen  wrote:
> 
> Hi All,
> 
> Let's say that someone (okay, me) is experimenting with juju2 (develop) 
> locally, and I've rudely destroyed an lxc container that had a juju charm 
> deployed to it (lxc stop  && lxc delete ).
> 
> Is there a way to convince juju that the charm is no longer deployed? juju 
> destroy-service and juju destroy-unit both fail, because juju cannot connect 
> to the machine. Is there a way, short of clobbering ~/.local/shrare/juju and 
> attempting to start from scratch, of making juju let go of the charm?
> 
> Thank you in advance,
> 
> ~ PeteVG
> -- 
> 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

Is there a way to let juju know that an lxc container has gone away and isn't coming back?

[Pete Vander Giessen]

Hi All,

Let's say that someone (okay, me) is experimenting with juju2 (develop)
locally, and I've rudely destroyed an lxc container that had a juju charm
deployed to it (lxc stop  && lxc delete ).

Is there a way to convince juju that the charm is no longer deployed? juju
destroy-service and juju destroy-unit both fail, because juju cannot
connect to the machine. Is there a way, short of clobbering
~/.local/shrare/juju and attempting to start from scratch, of making juju
let go of the charm?

Thank you in advance,

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

[Review Queue] ubuntu-devel, Openjdk, OpenAirInterface LTE eNB-UE simulator, ELK and more...

[Konstantinos Tsakalozos]

Hi all,

Here is what the big data team has been reviewing the past weeks.

April 7, 2016: Cory/Kevin/Kostas

   -

   Bird lint fixes
   -


  https://code.launchpad.net/~johnsca/charms/trusty/bird/lint/+merge/287962
  -

  Fixes lint errors
  -

  Merged
  -

   haproxy
   -


  
https://code.launchpad.net/~jacekn/charms/precise/haproxy/haproxy-updates/+merge/272559
  -


  
https://code.launchpad.net/~verterok/charms/trusty/haproxy/statistics-interface/+merge/288005
  -

  SSL support, new config options, monitoring fixes (precise)
  -

  New statistics interface (trusty)
  -

  Merged, and we asked the author if precise fixes should be merged
  into trusty
  -

   apache2
   -


  
https://code.launchpad.net/~kwmonroe/charms/trusty/apache2/timeouts/+merge/287222
  -

  Increase deployment timeouts in amulet tests
  -

  Merged
  -

   saikuanalytics-enterprise
   -

  https://bugs.launchpad.net/charms/+bug/1524715
  -

  This is a review for a new charm, Saiku Analytics is a flexible &
  lightweight web based OLAP Analysis tool.
  -

  We found a couple of issues that need the author’s attention. During
  review we followed the README instructions and we couldn’t deploy a trial
  license through the proposed action. We found a couple of unused files
  within the charm.
  -

  We will have to wait for the author to address these issues before we
  proceed with this charm.


Mar 31, 2016:  Andrew/Cory/Kevin/Kostas

   -

   Logstash
   -

  https://bugs.launchpad.net/charms/+bug/1560167
  -

  Logstash is designed to efficiently process a growing list of log,
  event, and unstructured data sources for distribution into a variety of
  outputs, including Elasticsearch.
  -

  The review process showed a few minor issues. We offered our
  suggestions to the author in
  https://github.com/juju-solutions/layer-logstash/pull/16
  -

   add-dashboard-loader-action into Kibana
   -


  
https://code.launchpad.net/~lazypower/charms/trusty/kibana/add-dashboard-loader-action/+merge/289684
  -

  With this extra action we can deploy dashboards bundled with the
  charm. This is useful for  distributing dashboards created
against KB4 and
  then making them available to the consumers of kibana at large.
  -

  We were not able to test all dashboards proposed yet we were able to
  see that the new dashboard are available.
  -

  A flaky test was spotted.
  -

   Filebeat
   -

  https://bugs.launchpad.net/charms/+bug/1560166
  -

  Filebeat is a lightweight, open source shipper for log file data.
  -

  The review process revealed a couple of (mostly minor) issues that
  need the attention of the author.
  -

   Topbeat
   -

  https://bugs.launchpad.net/charms/+bug/1560164
  -

  Topbeat is ightweight way to gather CPU, memory, and other
  per-process and system wide data, then ship it to Elasticsearch
to analyze
  the results.
  -

  The review process revealed a couple of issues (flaky test and repo
  directive missing) that call the attention of the author.



Mar 24, 2016:  Andrew/Cory/Kevin/Kostas

   -

   ubuntu-devenv
   -

  https://bugs.launchpad.net/charms/+bug/1550564
  -

  This charm provides an ubuntu-based development environment. It also
  includes relations to other developer-oriented charms (java, xl-c,
  xl-fortran).
  -

  Tests ran fine
  -

  +1, promulgated
  -

   Openjdk
   -

  https://bugs.launchpad.net/charms/+bug/1551442
  -

  This is a layered charm that implements the java interface to provide
  openjdk
  -

  We reviewed the charm and found no issues
  -

  +1, promulgated


Mar 17, 2016:  Andrew/Cory/Kevin/Kostas

   -

   diaspora
   -

  https://bugs.launchpad.net/charms/+bug/1553534
  -

  Charm is good, but offered some suggested improvements, such as using
  status-set
  -

   OpenAirInterface LTE eNB-UE simulator
   -

  https://bugs.launchpad.net/charms/+bug/1533300
  -

  This charm sets up a simulation of an LTE base station of
  OpenAirInterface
  -

  This charm poses a challenge as for us since we cannot deploy it due
  to its nature.
  -

  We asked the authors to provide unit and/or amulet tests. Another
  option the authors could consider is the use of bundles and tests at a
  higher level.
  -

  We would also like the authors to address the issues they have
  identified in their README and bring the charm to a production level.
  -

  We cannot proceed with the charm at this point.


Cheers,
-- 
Konstantinos Tsakalozos
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listin

Re: charmstore client authentication(help! :) )

[Tom Barber]

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

Re: charmstore client authentication(help! :) )

[Marco Ceppi]

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

charmstore client authentication(help! :) )

[Tom Barber]

(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