/srv/irclogs.ubuntu.com/2013/09/24/#juju.txt

=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== defunctzombie is now known as defunctzombie_zz
Dottedhow 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 push01:25
Dottedfigured it out bzr didnt know my lp username01:31
davecheneynice01:32
freeflyingI ran into a bootstrap issue within a maas environment01:33
freeflyingbootstrap has its node installed, but juju then can't connect to mongodb on that node01:34
freeflying2013-09-21 16:59:18 ERROR juju.agent agent.go:448 failed to initialize state: no reachable servers01:36
freeflying2013-09-21 16:59:18 ERROR juju supercommand.go:282 command failed: no reachable servers01:36
freeflyingerror: no reachable servers01:36
davecheneyfreeflying: what does /var/log/cloudinit-output.log on the bootstrap node say ?01:36
davecheneymost likely it could not add the PPA01:36
davecheneyand installed the wrong version of mongodb01:36
freeflyingdavecheney, which ppa shall it add?  I can try manually, see if its related to network(pproxy)01:37
davecheneyfreeflying: check the output of cloudinit-output.log01:38
davecheneyall the details are there01:38
davecheneyfreeflying: are you using a proxy in your environment ?01:40
davecheneyjuj basically assumes it has a working defualt route01:40
davecheneyif that isn't the case01:40
davecheneywell, shit is going to break01:40
freeflyingdavecheney, yes01:40
freeflyingdavecheney, 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-proxy01:41
freeflyingdavecheney, I can't add the proxy manually :)01:41
davecheneyfreeflying: yup, that is supported (and recommended)01:42
davecheneyjust finding the magic settings01:42
freeflyingdavecheney, thanks :)01:42
davecheneybasically if the host you are bootstrapping from uses the proxy01:42
davecheneywe sniff that and pass the same details down to the bootstrap node01:42
davecheneyfreeflying: try this01:44
davecheneyapt-config dump | grep -e 'Acquire::[a-z]+::Proxy\s+"[^"]+"'01:44
davecheneyif that returns anything in on the client01:44
davecheneythen we'll pass those details via cloud init01:44
davecheneyif the client and the maas instance are using differnt proxy config01:44
davecheneythen youre probably stuck01:45
davecheneythat isn't a configuration we anticipated01:45
freeflyingdavecheney, returns empty01:45
davecheneyfreeflying: short solution01:45
davecheneyconfigure your workstation to use the apt proxy01:45
freeflyingdavecheney, what does my workstation mean?01:45
davecheneyfreeflying: where you typ ethe command 'juju bootstrap'01:46
freeflyingdavecheney, on maas server01:46
davecheneyfreeflying: that honestly isn't a configuration we anticipated01:47
freeflyingdavecheney, interesting thin is the node has no problem to access internet01:49
davecheneyfreeflying: which is 'the node' ?01:52
freeflyingdavecheney, the bootstraped one01:54
davecheneyfreeflying: i'm sorry, i am confused01:55
davecheneyi thought you told me that the bootstrapped node did not have direct access to the internet01:55
davecheney11: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-proxy01:55
freeflyingdavecheney, in maas's preseed, the proxy has been set up, so bootstrap node has a default gw via that proxy01:57
davecheneyfreeflying: so, the host does _not_ have direct internet access ?01:59
davecheneyis that correct ?01:59
freeflyingdavecheney, the host here means which?  maas server?02:00
davecheneyfreeflying: the bootstrap node02:01
davecheneyfreeflying: can you paste the /var/log/cloudinit-output.log from the bootstrap node02:01
davecheneythat will make everything clear02:01
freeflyingdavecheney, hold one plz02:02
freeflyingdavecheney, sent you in msg02:09
=== defunctzombie_zz is now known as defunctzombie
davecheneykk02:10
davecheneyis your squid-apt-proxy configyured to proxy ppa.launchpad.net02:10
davecheneyby default it does not02:10
davecheneyfreeflying: does this work02:12
davecheneyenv https_proxy=$YOURPROXY curl https://launchpad.net/~juju/+archive/stable/+files/mongodb-dev_2.2.4-0ubuntu1~ubuntu12.04.1~juju1_i386.deb02:13
davecheneysorry add a -L to that cur;02:14
davecheneysorry add a -L to that curl02:14
davecheneybasiscally trying to emulate what cloud-init is doing02:14
freeflyingcurl: (56) Received HTTP code 403 from proxy after CONNECT02:15
davecheneyok, that is why it isn't working02:15
davecheneyby default squid-apt-proxy does not allow that02:15
davecheneyfrom memory there are comments in the configuratoin file to allow it to talk to ppa sources02:16
freeflyingyou mean enable ssl? or have ppa.launchpad.net enable in squid-deb-proxy?02:17
davecheneyhttp://askubuntu.com/questions/303150/apt-get-403-forbidden-but-accessible-in-the-browser02:17
davecheneysorry, not an awesome answer02:17
davecheneyhttps://answers.launchpad.net/ubuntu/+source/squid-deb-proxy/+question/17907502:18
davecheneygives another hint where the config is02:18
freeflyingdavecheney, I have ppa.launchpad.net added to squid-deb-proxy's mirror-dstdomian.acl via maas, but still, it can cache ppa02:40
davecheneyfreeflying: can or cannot ?02:41
freeflyingdavecheney, sorry, can't02:41
davecheneyfreeflying: add some more, like launchpad.net and launchpadlibrarian.net02:42
=== 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
freeflyingdavecheney, thanks, have it solved05:15
davecheneyfreeflying: cool05:16
davecheneywhat was the solution ?05:16
freeflyingdavecheney, add keyserver and launchpad to squid-deb-proxy's mirror-dstdomian05:17
freeflyingdavecheney, also modify maas's preeed to add the ppa in late_command with http/https_proxy05:17
freeflyingdavecheney, all in short, its a proxy issue :)05:18
davecheneyfreeflying: you do not need to modify the maas preseed05:18
davecheneywe handle that in cloud init05:18
davecheneymaas preseed and cloudinit have a strong overlap05:19
freeflyingdavecheney, seems it for http_proxy, but doesn't work for https_proxy05:19
davecheneyfreeflying: did you setup the apt-proxy as i showed above05:20
davecheneyif that regex does not return anything05:20
davecheneythen the correct value will not be supplied to cloud init when you bootstrap an environment05:20
freeflyingdavecheney, no, didn't set anything then05:20
=== 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
jamespageraywang, should work as described in the README10:50
raywangjamespage, 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/122964510:51
_mup_Bug #1229645: ceph-radosgw missing identity relation links <ceph-radosgw (Juju Charms Collection):In Progress by hopem> <https://launchpad.net/bugs/1229645>10:51
jamespageraywang, I've merged dosaboys branch10:54
jaywinkhi 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?10:57
davecheneyjaywink: the first thing you need is a juju provider11:10
davecheneywe have providers for ec2, openstack (including private openstack clouds), maas and azure11:11
davecheneyif your virtual environment looks *identical* to one of those11:11
davecheneyit will work11:11
davecheneyif not, it won't11:11
jaywinkdavecheney, 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 available11:23
davecheneyjaywink: 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) machines11:24
davecheneyjaywink: the problem you'll find with something that smells like EC2 is the AMI instance numbers won't match11:24
davecheneyso, you say to juju 'precise/amd64 1 core, 1.7gb of ram please'11:24
davecheneyand we have to find the AMI that matches that11:24
jaywinkdavecheney, I set it as POC to the code itself :P11:25
davecheneythese values are fixed for ec2, and vary even per refion11:25
davecheneyjaywink: i think IRC is a poor medium to this11:25
davecheneyi suggest continuing this discussion on juju-dev ML11:25
davecheneyjaywink: what you want to do is possible11:26
davecheneybut will take some tweaking11:26
davecheneyespecially with the ec2 provider as it has never been tested against ec2 workalikes11:26
jaywinkdavecheney, 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:27
davecheneyjaywink: i'm sure it can be done with a bit of hacking11:28
davecheneythe image/AMI selection will be the trickiest bit11:28
davecheneyjaywink: writing a new provider, copying the ec2 provider would be the simplest solution11:30
davecheneyagain, the best way to approach this is via the development list11:30
jaywinkdavecheney, 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:31
davecheneyjaywink: we have a product11:33
davecheneywell11:33
davecheneynot really a product11:33
davecheneyit's just a shittonne of json11:33
davecheneywhich allows you to describe the images available in a cloud11:33
davecheneythis will probably be the best solution to solving the image selection issue11:33
davecheneyand glue together what juju expects with what GQ provides11:33
jaywinkok cool, sounds good. just joining the list, will throw something in there. Thanks!11:36
davecheneyjaywink: kk11:36
=== Guest47103 is now known as ehw
=== natefinch is now known as natefinch-afk
sinzuiadeuring, Bug #122970813:10
_mup_Bug #1229708: UnavailableSradsException from cstats <elasticsearch> <charmworld:Triaged> <https://launchpad.net/bugs/1229708>13:10
* adeuring is looking13:10
=== 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
jamespageadam_g, some of my ceph redux was fud14:59
jamespagehttps://code.launchpad.net/~james-page/charm-helpers/fixup-ceph-pool-creation/+merge/18726014:59
jamespageI've already merged those fixes into the openstack-charmers branch and re-syced cinder and glance14:59
wedgwoodhow do I recover a local environment after a reboot?15:06
wedgwood(reboot of the host system)15:07
sinzuiadeuring, how goes the elasticsearch issue on staging?15:33
adeuringsinzui: fixed, but in a hackish way: I changed the ES clustername and rebuilt the index15:34
sinzui\o/15:34
adeuringsinzui: where do we store the configs of charmwold?15:34
adeuring(we don't want to run juju set elasticsearch cluster-name=new_name manually during deployment ;)15:35
sinzuiadeuring, I don't think that is hackish? I added the config but  but never used it15:35
adeuringsinzui: well, I just declared a new cluster name, but that should be automatically used when staging is freshly deployed15:36
sinzuiadeuring, 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 down15:37
sinzuiadeuring, staging was deployed using the pseudo script in the orangestack branch15:37
adeuringsinzui: can you give me the URL?15:38
sinzuiWe want to update ./deploy script in it15:38
sinzuiadeuring, you don't already have a branch?15:38
sinzuiahh, I am using the old name. adeuring look in lp:~ce-orange-squad/charmworld/staging-tools15:39
adeuringsinzui: could be -- can't find it at least... Maybe I'm just confused15:39
adeuringsinzui: ah, sure...15:39
adeuringsinzui: I'll update it15:40
sinzuiadeuring, lets update the Charmworld page for webops to include the cluster name with each deploy.15:40
sinzuiwe might also want to update the deployer file. I need to find that branch15:40
adeuringsinzui: 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:41
sinzuiadeuring, thank you!15:42
=== 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
hatchwhen 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 sort18:22
hatchahh found the docs - that's normal18:42
jcastrohey sinzui you're doing release now?19:11
jcastroI mean you're doing the juju releases these days?19:11
sinzuiyes19:12
jcastroare we defaulting to the local provider yet?19:12
sinzuijcastro, Sorry I don't understand.19:13
jcastrook so say I do a clean install19:13
jcastroand do `juju init`19:13
jcastrodo we write out local as the default environment yet?19:14
sinzuiMay be to 1.15.0 (if we fixed the bug)19:14
sinzuiI can check19:14
jcastroI know it's a filed bug19:16
jcastrodarned if I can't find it now though19:16
sinzuijcastro, https://launchpad.net/juju-core/+milestone/1.16.019:17
sinzui^ targeted to next week19:17
jcastrook19:18
sinzuijcastro, I need to reset my juju-core. It thinks it is 1.14.1 from the release19:18
jcastrosinzui: https://bugs.launchpad.net/juju-core/+bug/122990319:21
_mup_Bug #1229903: Default to local provider <juju-core:New> <https://launchpad.net/bugs/1229903>19:21
sinzuijcastro, 1.15.0 will use amazon as the default provider19:21
jcastrosinzui: I'd like to nominate it for 1.16 but not like, step on any release toes by just assigning it in LP19:21
sinzuijcastro, 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
jcastroright!19:22
jcastrowe had agreed verbally at the sprint, along with thumper19:23
jcastroI just realized today that we hadn't followed up and actually done that yet19:23
sinzuijcastro, I accept your argument and have targeted the bug. I will ask for forgiveness if I must19:24
sinzuiI'll talk to the leads19:24
jcastroyes, cowboy the world, I like how you think. :p19:24
=== freeflying_away is now known as freeflying
=== defunctzombie is now known as defunctzombie_zz
weblifeafternoon juju mack daddy's21:49
jcastrohi!21:49
=== 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

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!