=== freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === defunctzombie is now known as defunctzombie_zz [01:25] how do you push a local charm to launchpad? im getting "bzr: ERROR: Invalid url supplied to transport: "lp:~dotted1337/charms/precise/sendy/trunk": No such source package sendy." when doing bzr push [01:31] figured it out bzr didnt know my lp username [01:32] nice [01:33] I ran into a bootstrap issue within a maas environment [01:34] bootstrap has its node installed, but juju then can't connect to mongodb on that node [01:36] 2013-09-21 16:59:18 ERROR juju.agent agent.go:448 failed to initialize state: no reachable servers [01:36] 2013-09-21 16:59:18 ERROR juju supercommand.go:282 command failed: no reachable servers [01:36] error: no reachable servers [01:36] freeflying: what does /var/log/cloudinit-output.log on the bootstrap node say ? [01:36] most likely it could not add the PPA [01:36] and installed the wrong version of mongodb [01:37] davecheney, which ppa shall it add? I can try manually, see if its related to network(pproxy) [01:38] freeflying: check the output of cloudinit-output.log [01:38] all the details are there [01:40] freeflying: are you using a proxy in your environment ? [01:40] juj basically assumes it has a working defualt route [01:40] if that isn't the case [01:40] well, shit is going to break [01:40] davecheney, yes [01:41] davecheney, no direct internet for the maas environment, all traffic have to go via a proxy, which we set on maas server by using squid-deb-proxy [01:41] davecheney, I can't add the proxy manually :) [01:42] freeflying: yup, that is supported (and recommended) [01:42] just finding the magic settings [01:42] davecheney, thanks :) [01:42] basically if the host you are bootstrapping from uses the proxy [01:42] we sniff that and pass the same details down to the bootstrap node [01:44] freeflying: try this [01:44] apt-config dump | grep -e 'Acquire::[a-z]+::Proxy\s+"[^"]+"' [01:44] if that returns anything in on the client [01:44] then we'll pass those details via cloud init [01:44] if the client and the maas instance are using differnt proxy config [01:45] then youre probably stuck [01:45] that isn't a configuration we anticipated [01:45] davecheney, returns empty [01:45] freeflying: short solution [01:45] configure your workstation to use the apt proxy [01:45] davecheney, what does my workstation mean? [01:46] freeflying: where you typ ethe command 'juju bootstrap' [01:46] davecheney, on maas server [01:47] freeflying: that honestly isn't a configuration we anticipated [01:49] davecheney, interesting thin is the node has no problem to access internet [01:52] freeflying: which is 'the node' ? [01:54] davecheney, the bootstraped one [01:55] freeflying: i'm sorry, i am confused [01:55] i thought you told me that the bootstrapped node did not have direct access to the internet [01:55] 11:41 < freeflying> davecheney, no direct internet for the maas environment, all traffic have to go via a proxy, which we set on maas server by using squid-deb-proxy [01:57] davecheney, in maas's preseed, the proxy has been set up, so bootstrap node has a default gw via that proxy [01:59] freeflying: so, the host does _not_ have direct internet access ? [01:59] is that correct ? [02:00] davecheney, the host here means which? maas server? [02:01] freeflying: the bootstrap node [02:01] freeflying: can you paste the /var/log/cloudinit-output.log from the bootstrap node [02:01] that will make everything clear [02:02] davecheney, hold one plz [02:09] davecheney, sent you in msg === defunctzombie_zz is now known as defunctzombie [02:10] kk [02:10] is your squid-apt-proxy configyured to proxy ppa.launchpad.net [02:10] by default it does not [02:12] freeflying: does this work [02:13] env https_proxy=$YOURPROXY curl https://launchpad.net/~juju/+archive/stable/+files/mongodb-dev_2.2.4-0ubuntu1~ubuntu12.04.1~juju1_i386.deb [02:14] sorry add a -L to that cur; [02:14] sorry add a -L to that curl [02:14] basiscally trying to emulate what cloud-init is doing [02:15] curl: (56) Received HTTP code 403 from proxy after CONNECT [02:15] ok, that is why it isn't working [02:15] by default squid-apt-proxy does not allow that [02:16] from memory there are comments in the configuratoin file to allow it to talk to ppa sources [02:17] you mean enable ssl? or have ppa.launchpad.net enable in squid-deb-proxy? [02:17] http://askubuntu.com/questions/303150/apt-get-403-forbidden-but-accessible-in-the-browser [02:17] sorry, not an awesome answer [02:18] https://answers.launchpad.net/ubuntu/+source/squid-deb-proxy/+question/179075 [02:18] gives another hint where the config is [02:40] davecheney, I have ppa.launchpad.net added to squid-deb-proxy's mirror-dstdomian.acl via maas, but still, it can cache ppa [02:41] freeflying: can or cannot ? [02:41] davecheney, sorry, can't [02:42] freeflying: add some more, like launchpad.net and launchpadlibrarian.net === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [05:15] davecheney, thanks, have it solved [05:16] freeflying: cool [05:16] what was the solution ? [05:17] davecheney, add keyserver and launchpad to squid-deb-proxy's mirror-dstdomian [05:17] davecheney, also modify maas's preeed to add the ppa in late_command with http/https_proxy [05:18] davecheney, all in short, its a proxy issue :) [05:18] freeflying: you do not need to modify the maas preseed [05:18] we handle that in cloud init [05:19] maas preseed and cloudinit have a strong overlap [05:19] davecheney, seems it for http_proxy, but doesn't work for https_proxy [05:20] freeflying: did you setup the apt-proxy as i showed above [05:20] if that regex does not return anything [05:20] then the correct value will not be supplied to cloud init when you bootstrap an environment [05:20] davecheney, no, didn't set anything then === CyberJacob|Away is now known as CyberJacob === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === teknico1 is now known as teknico [10:50] raywang, should work as described in the README [10:51] jamespage, it claims supporting add relation to keystone, but it's missing hooks, dosaboy report that bug https://bugs.launchpad.net/charms/+source/ceph-radosgw/+bug/1229645 [10:51] <_mup_> Bug #1229645: ceph-radosgw missing identity relation links [10:54] raywang, I've merged dosaboys branch [10:57] hi all. wondering if anyone has a link or explanation to what is required from a cloud image to bootstrap with juju? Say I get a non-ec2 but ec2 API compatible provider to work up until bootstrap - will a default ubuntu server image do or does it require some custom image that for example Amazon has? [11:10] jaywink: the first thing you need is a juju provider [11:11] we have providers for ec2, openstack (including private openstack clouds), maas and azure [11:11] if your virtual environment looks *identical* to one of those [11:11] it will work [11:11] if not, it won't [11:23] davecheney, by provider you mean the actual cloud image? I've got up to the actual RunInstance call on GreenQloud which has an EC2 compatible API - they have a precise server image available [11:24] jaywink: we call a provider a piece of software designed to translate juju's abstract view of the world onto a real provider of virtual (or physical) machines [11:24] jaywink: the problem you'll find with something that smells like EC2 is the AMI instance numbers won't match [11:24] so, you say to juju 'precise/amd64 1 core, 1.7gb of ram please' [11:24] and we have to find the AMI that matches that [11:25] davecheney, I set it as POC to the code itself :P [11:25] these values are fixed for ec2, and vary even per refion [11:25] jaywink: i think IRC is a poor medium to this [11:25] i suggest continuing this discussion on juju-dev ML [11:26] jaywink: what you want to do is possible [11:26] but will take some tweaking [11:26] especially with the ec2 provider as it has never been tested against ec2 workalikes [11:27] davecheney, don't mind tweaking :) and GQ is very interested too to get things working, even if as POC with non-stable code mods to begin with. I'll subscribe to the list and throw in the questions - thanks! :) [11:28] jaywink: i'm sure it can be done with a bit of hacking [11:28] the image/AMI selection will be the trickiest bit [11:30] jaywink: writing a new provider, copying the ec2 provider would be the simplest solution [11:30] again, the best way to approach this is via the development list [11:31] davecheney, I just used 'euca-describe-images' against GQ and took the most suitable one - GQ doesn't have that many :) But just worried while waiting for GQ to fix one thing that whether their server image will work or does Juju require some custom Ubuntu builds. [11:33] jaywink: we have a product [11:33] well [11:33] not really a product [11:33] it's just a shittonne of json [11:33] which allows you to describe the images available in a cloud [11:33] this will probably be the best solution to solving the image selection issue [11:33] and glue together what juju expects with what GQ provides [11:36] ok cool, sounds good. just joining the list, will throw something in there. Thanks! [11:36] jaywink: kk === Guest47103 is now known as ehw === natefinch is now known as natefinch-afk [13:10] adeuring, Bug #1229708 [13:10] <_mup_> Bug #1229708: UnavailableSradsException from cstats [13:10] * adeuring is looking === BradCrittenden is now known as bac === freeflying is now known as freeflying_away === scuttlemonkey_ is now known as scuttlemonkey === hatch_ is now known as hatch === kentb-out is now known as kentb === natefinch-afk is now known as natefinch [14:59] adam_g, some of my ceph redux was fud [14:59] https://code.launchpad.net/~james-page/charm-helpers/fixup-ceph-pool-creation/+merge/187260 [14:59] I've already merged those fixes into the openstack-charmers branch and re-syced cinder and glance [15:06] how do I recover a local environment after a reboot? [15:07] (reboot of the host system) [15:33] adeuring, how goes the elasticsearch issue on staging? [15:34] sinzui: fixed, but in a hackish way: I changed the ES clustername and rebuilt the index [15:34] \o/ [15:34] sinzui: where do we store the configs of charmwold? [15:35] (we don't want to run juju set elasticsearch cluster-name=new_name manually during deployment ;) [15:35] adeuring, I don't think that is hackish? I added the config but but never used it [15:36] sinzui: well, I just declared a new cluster name, but that should be automatically used when staging is freshly deployed [15:37] adeuring, your are right about the deploy...and I warned webops that running 2 ES stacks in prodstack will require them to have different cluster names. I suck for not writing it down [15:37] adeuring, staging was deployed using the pseudo script in the orangestack branch [15:38] sinzui: can you give me the URL? [15:38] We want to update ./deploy script in it [15:38] adeuring, you don't already have a branch? [15:39] ahh, I am using the old name. adeuring look in lp:~ce-orange-squad/charmworld/staging-tools [15:39] sinzui: could be -- can't find it at least... Maybe I'm just confused [15:39] sinzui: ah, sure... [15:40] sinzui: I'll update it [15:40] adeuring, lets update the Charmworld page for webops to include the cluster name with each deploy. [15:40] we might also want to update the deployer file. I need to find that branch [15:41] sinzui: yep. I'll also write an internal email that we might step on each other's toes by not setting the cluser name. Perhaps my change affects otherES instances... [15:42] adeuring, thank you! === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie [18:22] when deploying the gui using local provider on 1.14.1-precise-amd64 the instance-state of the GUI machine is 'missing' - is this intended or an issue of some sort [18:42] ahh found the docs - that's normal [19:11] hey sinzui you're doing release now? [19:11] I mean you're doing the juju releases these days? [19:12] yes [19:12] are we defaulting to the local provider yet? [19:13] jcastro, Sorry I don't understand. [19:13] ok so say I do a clean install [19:13] and do `juju init` [19:14] do we write out local as the default environment yet? [19:14] May be to 1.15.0 (if we fixed the bug) [19:14] I can check [19:16] I know it's a filed bug [19:16] darned if I can't find it now though [19:17] jcastro, https://launchpad.net/juju-core/+milestone/1.16.0 [19:17] ^ targeted to next week [19:18] ok [19:18] jcastro, I need to reset my juju-core. It thinks it is 1.14.1 from the release [19:21] sinzui: https://bugs.launchpad.net/juju-core/+bug/1229903 [19:21] <_mup_> Bug #1229903: Default to local provider [19:21] jcastro, 1.15.0 will use amazon as the default provider [19:21] sinzui: I'd like to nominate it for 1.16 but not like, step on any release toes by just assigning it in LP [19:22] jcastro, I (as a heavy juju lxc user) endorse your nomination. Are you arguing that Saucy (1.16.0) needs this out of the box setting for a great 30 minute experience? [19:22] right! [19:23] we had agreed verbally at the sprint, along with thumper [19:23] I just realized today that we hadn't followed up and actually done that yet [19:24] jcastro, I accept your argument and have targeted the bug. I will ask for forgiveness if I must [19:24] I'll talk to the leads [19:24] yes, cowboy the world, I like how you think. :p === freeflying_away is now known as freeflying === defunctzombie is now known as defunctzombie_zz [21:49] afternoon juju mack daddy's [21:49] hi! === kentb is now known as kentb-out === defunctzombie_zz is now known as defunctzombie === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === CyberJacob is now known as CyberJacob|Away === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying