[09:49] <digv> hi.. is https://review.jujucharms.com/ is down? I am not able to access it
[09:54] <hloeung> digv: it's been shut down, see https://lists.ubuntu.com/archives/juju/2017-August/009294.html
[10:16] <digv> hloeung: thanks
[10:20] <digv> hloeung: one small help needed, I want to submit an updated charm which is already there in charm store.. can you guide me please
[10:21] <digv> is there any change in process of submitting updated patch?
[10:22] <hloeung> digv: if you own what's published i nthe charm store, it should just be this process here to update/publish a new/updated version - https://jujucharms.com/docs/2.2/authors-charm-store#pushing-to-the-store
[10:27] <digv> hloeung: this is my first attempt, some member from "ibmcharmers" was maintaining it... I've recently joined that Group.
[10:32] <hloeung> digv: right, so should just be charm build, cd <built_charm_dir>, charm push . cs:~ibmcharmers/xenial/mycharm, charm release cs:~ibmcharmers/xenial/mycharm-91 (replace 91 with what's output from the push command), charm grant cs:~ibmcharmers/xenial/mycharm-91 everyone
[11:30] <digv> hloeung: thanks for help.. able to submit a charm :)
[12:51] <kjackal> Hello AntonDan
[12:51] <kjackal> magicaltrout: are you around?
[13:42] <magicaltrout> kjackal__: kjackal_  whichever
[13:43] <kjackal__> Hey magicaltrout how is it going? I wanted you to introduce you to AntonDan that would be interesting in woring on Mesos+Lxd
[13:44] <kjackal__> AntonDan: are you there?
[13:44] <AntonDan> yup
[13:44] <magicaltrout> thanks kjackal__ !
[13:44] <magicaltrout> hey AntonDan
[13:44] <AntonDan> Hello
[13:45] <magicaltrout> someone with half an clue about C and wanting to offer some sage advice or help extended Mesos for the LXD container spec would be great
[13:45] <magicaltrout> s/extended/extending
[13:48] <kjackal__> I am sure AntonDan can help
[13:51] <magicaltrout> mesos added lxd support to their container roadmap AntonDan but they certainly won't prioritise it, so I'd like a community effort to drive it, I dont' think there is a massive amount of work as its just swapping the docker interface for lxd pretty much
[13:52] <kjackal__> AntonDan: would need some guidance in terms of where to meet the Mesos people interested in lxd, what meetings to attand and any advice on technical aspects would be appreciated. Bu he seems to be a strong coder so...
[13:52] <AntonDan> I'll try my best, my knowledge in C should be sufficient for the task. The unfamiliar terrain that is large projects is slightly obstructive but I'm treading said terrain slowly but surely
[13:52] <AntonDan> Ye I did take a look at the roadmap
[13:53] <AntonDan> There doesn't seem to be anyone else working on that task
[13:53] <magicaltrout> nope there wont be, I asked months ago about it and their response was "I don't really see a usecase for it"
[13:53] <magicaltrout> still people
[13:56] <magicaltrout> okay AntonDan what can I do to help facilitate your development? code, servers, tests, docs? anything specific?
[13:57] <magicaltrout> beer? food? caffiene?
[13:58] <AntonDan> The main thing that gives me trouble right now is my familiarity with the mesos project itself. Currently I'm fine testing on my local machine and on a virtual machine that was given to me by kjackal. I might need some server later on though for testing.
[13:59] <AntonDan> my familiarity or lack thereof, that is
[14:08] <magicaltrout> no problem AntonDan I'm happy to supply you with some server resource when you need it. For Mesos, it really only has 2 components, Mesos (Master/Slave) and Marathon. Don't worry about Marathon though for now, thats mostly just a UI wrapper around the Mesos service
[14:09] <AntonDan> I did set up marathon since I wanted to have a platform for me to communicate with mesos
[14:10] <AntonDan> I had someone recommend me Chronos as an alternative but I found setting marathon up an easier task
[14:10] <magicaltrout> I think Chronos is retired these days
[14:10] <magicaltrout> mostly
[14:11] <magicaltrout> yeah last update was months ago
[14:12] <AntonDan> I see
[15:22] <magicaltrout> AntonDan: if you can't find me in here and need anything, feel free to ping tom@spicule.co.uk
[15:23] <AntonDan> will add to contacts. I'll just pm you here if I do find you online in order to reduce spam in the juju channel
[16:06] <stormmore> o/ juju world, what madness is happening
[17:29]  * stormmore is having fun putting OpenStack on LXD on his poor little laptop
[17:42] <stormmore> hey rick_h hows the 2.3 testing going?
[18:55] <hallyn> so...   i seem to have juju working against a remote vsphere server.  it's downloading an .ova file.  That's good.  BUT it's downloading it to my laptop.
[19:00] <hallyn> Why do that?  Bc vsphere's folders won't work somehow?  I could see that... but...
[19:01] <hallyn> well *this* won't owrk for me.  a one time experiment is fine, but who the heck thought it would be a good idea.
[19:01] <hallyn> guess i'll try a vm closer to the datacenter.  but i'll do so under protest, noting how stupid and shortsighted it is...
[19:10] <hallyn> stokachu: \o  do you know if that's normal^ or if i misconfigured something?
[19:57] <stokachu> hallyn: I need to ask axw about that
[19:57] <stokachu> That doesn't sound right
[20:27] <hallyn> ok - hopefully there's just a setting I can fix on my local (macos) juju install, but for now I'm going to try and setup a base juju admin VM on the same vsphere.
[20:27] <hallyn> (will tkae an hour to push an iso there and another hour to install probably :)
[20:38] <rick_h> hallyn: so it looks like the docs state it works that way
[20:38] <rick_h> hallyn: I'm not sure on the limitations/etc that caused it to be that way. Would be worth a bug and maybe an email to the mailing list or something. hml do you have any insight? ^
[20:40] <stokachu> hallyn: yea that sounds like the opposite of what we want it to do :)
[20:41] <rick_h> stormmore: hallyn that's from the note box in https://jujucharms.com/docs/2.2/help-vmware
[20:45] <stokachu> hallyn: axw will be on in a few hours i think, i can ask him when he comes online
[20:47] <hml> rick_h: hallyn: no extra insight, sounds like something with the vmware provider.  perhaps an email is best, so other can see and chime in
[20:48] <hml> or even a bug
[21:05] <hallyn> bug against juju project?
[21:07] <rick_h> hallyn: yes
[21:40] <hallyn> hml: rick_h: stokachu: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1712431     Thanks.
[21:40] <mup> Bug #1712431: sphere controller stores OVA files locally <juju (Ubuntu):New> <https://launchpad.net/bugs/1712431>