=== bigjools_ is now known as bigjools === gary_poster|away is now known as gary_poster === gary_poster is now known as gary_poster|away === gary_poster|away is now known as gary_poster [16:37] mramm: do you guys have a juju-tools tar ball for 1.9.11 that I can use to make a control buck on HP's cloud? === deryck is now known as deryck[lunch] [18:05] arosales: sorry, was in a meeting and then went to lunch without seeing your message, looking... [18:06] mramm: thanks === deryck[lunch] is now known as deryck === deryck is now known as deryck-afk === fss_ is now known as fss [21:42] mramm, I found http://juju-dist.s3.amazonaws.com/tools/juju-1.9.11-precise-amd64.tgz [21:43] cool [21:43] I am at the airport waiting for my flight, and haven't had time to look [21:43] I added two new tickets: [21:43] * arosales is going to see if that works for hp, and if so send my notes to the list. [21:44] one for adding HP and private openstack cloud's to our "tools just work" story. [21:49] mramm, hmm I don't see those yet @ http://goo.gl/ but perhaps I am looking at the wrong search [21:50] https://canonical.leankit.com/boards/view/103148069/104185973 [21:50] https://canonical.leankit.com/boards/view/103148069/104185972 [21:50] I do not expect them to be done this week [21:51] but hopefully next week before 1.9.12 [21:52] I will get them estimated and on the calendar this week -- but I expect that they will both be small [21:57] mramm, ah ok I was looking for an lp bug. Thanks [21:58] yea, we are using LP for features users ask for, and for actual bugs [21:58] but are tracking everyday development tasks and internally generated stuff on the kanban board (which is a better fit for our team's processes) [22:34] question: should "juju destroy-environment" also remove my control bucket in go-juju 1.9.11? [22:51] arosales: yes, the control bucket gets deleted [22:53] wallyworld__, hmm ok [22:53] not what you were expecting? [22:55] wallyworld__, I guess not as I manually made the control bucket, but perhaps that is a work around . . . [22:56] arosales: yes, normally the control bucket gets made automatically and is considered part of the environment, you needed to make it manually since we dont yet have a well defined public bucket in which to put tools like for ec2 [22:57] wallyworld__, ya for ec2 I don't see the deleting control bucket message [22:57] on destroy-environment, thta is. [22:57] just for hpcloud [22:58] arosales: for ec2, the control bucket is deleted also, perhaps the logging is different [22:58] hmm, same logging [22:59] wallyworld__, ah ok. perhaps cause I got a failed to delete control-bucket message from hp [22:59] although it did delte [22:59] *delete [22:59] that can happen sometimes according to a comment in the code [22:59] not sure why [22:59] we should fix that [22:59] wallyworld__, http://pastebin.ubuntu.com/5606299/ [23:00] thanks, that error code is useful, i'll see what the openstack docs say [23:01] we may be able to catch that specific error and deal with it [23:01] so, even with that error, the container was indeed deleted? [23:01] wallyworld__, since on hp cloud the control bucket has to be manually do you have any suggestions for a workaround if juju destroy-environment deletes? [23:01] wallyworld__, correct with that error the control bucket was still deleted. [23:02] arosales: i normally just do a upload-tools each time i bootstrap, but i'm guessing you don't have the source to do that? [23:02] wallyworld__, it looks like the compute instances were also terminated, which is good as I wasn't able to sucessfully process juju destroy-environment on hp cloud [23:03] yes, destroy nukes compute nodes and control bucket [23:03] wallyworld__, correct, I was trying to get around building from source, but perhaps I should just go the source route [23:04] wallyworld__, sure I was just wondering if the error on deleting the control-bucket stopped terminating the compute instances. [23:04] arosales: you can create a separate bucket and add it to the config as public-bucket-url. i'll work up an example and tell you what the correct config is [23:04] but it did not, compute instances were also terminated (just as a side note). [23:04] arosales: what's your timezone there, will you be around for a bit? [23:04] us central [23:05] so getting close to end of day for me. [23:05] arosales: the bucket deletion is done last, and error is ignore as such [23:05] wallyworld__, good to know on destroying the resources, thanks. [23:05] arosales: would it be ok if i emailed you the setup notes? [23:05] wallyworld__, no rush. an email works fine for an example. [23:05] i'll do it now, but not sure how long it will take to get right [23:05] no worries, just if you have a spare moment. [23:05] need to spin it up to test etc [23:06] wallyworld__, I can make a public URL control bucket [23:07] wallyworld__, https://region-a.geo-1.objects.hpcloudsvc.com:443/v1/49578719334052/juju-6de995f1bc7f4d72a1275f25f7a1ef1a/tools/juju-1.9.11-precise-amd64.tgz [23:07] not quite - when we decide how/where to make a public bucket available with all the tools in (like for ec2), you add public-bucket-url as a config item [23:07] in the above axample, you add something like @public-bucket-url: https://region-a.geo-1.objects.hpcloudsvc.com:443/v1/49578719334052/juju-6de995f1bc7f4d72a1275f25f7a1ef1a@ to your yaml [23:08] s/@/" [23:08] so long as the bucket is one you made manually and is separate to your control bucket, you put tools there and it won't be deleted [23:09] wallyworld__, ok I can give that a try [23:11] arosales: the issue with openstack is that the url contains the tenant id, unlike ec2, and we need to figure out a good way to publicise an acceptable public bucket url [23:12] wallyworld__, yup http://pastebin.ubuntu.com/5606323/ [23:12] I ran into that [23:12] arosales: public-bucket-url [23:13] not public-control-bucket [23:13] sorry I had "public-control-bucket" [23:13] np [23:17] wallyworld__, do I need to specify the tools path in the url I pass to my yaml file? [23:17] http://pastebin.ubuntu.com/5606337/ [23:18] arosales: let me check [23:21] wallyworld__, trying with appending /tools and /tools/juju-1.9.11-precise-amd64.tgz didn't help the finding the tools [23:22] arosales: juju appends "tools" automatically to the public bucket url. at first glance, what you have seems correct. [23:22] arosales: are you running quantal locally? [23:23] wallyworld__, correct [23:23] running quantal locally [23:23] arosales: so you need default-series: precise in your yaml [23:23] to tell juju to not just try and use the same series and you are running locally [23:23] yup got that default-series: precise [23:24] oh ok, and still failing [23:24] wallyworld__, I got juju to work on hpcloud with this control bucket just had the removal of the control-bucket which I was seeing if I could make easier for other folks wishing to test on hpcloud [23:26] arosales: it would be better if we could just point folks at a public bucket, even if it has a tenant id in it (imho). i'll plug in your bucket above into my setup and see what i need to do to get it to work [23:26] wallyworld__, no worries, seems the way forward is to build from source [23:26] i'd like to get this working ie it should work [23:27] i'll figure out what needs to be done and let you know, may only take a few minutes so i'll ping you if you are still around, otherwise email [23:27] ya, I was hoping to give my public bucket to others to test, if they wish for an easier setup . . . [23:27] wallyworld__, sounds good. [23:27] please don't let this pre-empt any of your more critical work though :-) [23:27] indeed. this should work, it's been tested before, just a doc issue i think unless something has broken [23:27] oh no, to me this is critical [23:28] you are the first guinea pig to try this. we only just got it working last week with the control bucket trivk [23:28] trick [23:29] wallyworld__, ok, thanks. [23:29] wallyworld__, I am happy to test or write up bugs, just let me know :-) [23:29] thanks. appreciate your patience [23:30] ah no worries, part of the fun :-) [23:30] yes. we were so exciting last thurday when "juju deploy" wordpress worked for the first time on hp cloud :-) [23:31] yup I also saw it working here with the control bucket removal [23:31] \o/ :-) [23:32] indeed [23:36] wallyworld__, I'll take a look at email tonight, but need to log off for a bit. [23:36] wallyworld__, thanks for the help [23:36] sure, np. will email as soon as i figure it out.