/srv/irclogs.ubuntu.com/2016/03/10/#juju.txt

=== psivaa_ is now known as psivaa
=== thumper-dogwalk is now known as thumper
=== JoseeAntonioR is now known as jose
=== scuttle|afk is now known as scuttlemonkey
nvalerkosmorning05:13
nvalerkosmarcoceppi: Marco are you there?05:13
nvalerkosI have a problem with creating a mysql database, its not providing the password file to login as root in order to create the user/database when I add a relationship with an webapp i created05:15
nvalerkosI think i have my metadata.yaml wrong or something on the relationship with mysql05:16
=== med_ is now known as Guest93664
BlackDexHello there. I get the following error, does some know where to look? "Service placement to machine not supported"10:35
magicaltroutwhat you doing BlackDex ?10:54
BlackDexmagicaltrout: Deploing ;)11:07
BlackDexBut i fond the problem11:07
BlackDexi pointed to a wrong machine11:07
magicaltroutcool11:08
magicaltroutthat was going to be my suggestion :P11:08
BlackDexhehe thx !11:49
marcoceppijamespage: https://github.com/juju-solutions/layer-basic/pull/45 however, you can patch this in the charms in the future by having the following in your layer.yaml http://paste.ubuntu.com/15340870/12:02
marcoceppithose will be evaluated before any pip calls are made (so if you need like buildessentials or libX-dev installed for a pip module, you can have that defined in the packages option)12:03
jamespagemarcoceppi, oh nice - thanks!12:11
marcoceppijamespage: either way, it'll land when cory_fu or someone else takes a look and +1's it12:11
jamespagemarcoceppi, thanks for doing the fix - I was about to poke around and see if I could fix that up12:12
jamespagemarcoceppi, btw12:12
jamespagehttp://paste.ubuntu.com/15340899/ works lovey12:12
nvalerkosmarcoceppi: Hello Marco, I have a quick question.13:57
nvalerkosif you are there that is13:57
marcoceppio/ nvalerkos13:57
nvalerkosso, I am trying to generate a new database connection with a non root user through metadata.yaml13:57
nvalerkosbut I am not getting it right13:58
marcoceppinvalerkos: sounds good, which charm are you connecting to?13:58
marcoceppipostgresql? mysql?13:58
nvalerkosI am making my own charm, I am using the mysql13:58
marcoceppinvalerkos: sounds good - do you have your charm uploaded somewhere so I can follow along and take a look?13:59
nvalerkosmarcoceppi: sent on prv message14:00
marcoceppinvalerkos: okay, so your charm "requires" a MySQL interface, it's not a peer14:01
nvalerkosmarcoceppo: I used it that, however it was connecting without the root password when using the db-relation-joined and getting a couldn't connect in log of python charm (mysql side)14:02
marcoceppinvalerkos: the MySQL relations will provide database, user, password, port, hostname, you will need to check to make sure you have those values before contining since tihs is an async system14:05
nvalerkosoh14:05
nvalerkosok got it, so the relation with requires is correct I just need to wait for complete relation credentials.14:06
nvalerkosAsync.14:06
nvalerkosmarcoceppi: thanks.14:08
marcoceppinvalerkos: here's an example of a charm that does tomcat + MySQL and it's hook: https://api.jujucharms.com/charmstore/v5/~spagobi-charmers/trusty/spagobi-4/archive/hooks/metadatadb-relation-changed and https://jujucharms.com/u/spagobi-charmers/spagobi/14:08
marcoceppimetadatadb is the name of the MySQL relation for this charm14:08
marcoceppinvalerkos: the system is async, but don't block the hook waiting. If you don't have the data just exit 0 from the hook and wait for the hook to be called again14:09
nvalerkosmarcoceppi: ok got it. I am using python14:10
marcoceppinvalerkos: ah, same concept, but without all the base ;)14:10
marcoceppibash14:10
nvalerkosah14:10
nvalerkosok14:10
nvalerkoswill do. thanks again.14:10
nvalerkosI saw that when you first gave me that charm link yesterday and did not gave any attention to it.14:11
jamespagethedac, coreycb, beisner: got time for a quick one?14:11
jamespagehttps://review.openstack.org/#/c/291146/14:11
beisnerjamespage, sure.  2-for-1? :-)   https://review.openstack.org/#/c/290943/     https://review.openstack.org/#/c/288483/14:12
jamespagebeisner, sure - looking14:13
beisnerjamespage, ps, we've got the charm-single config file repo live now.  https://github.com/openstack-charmers/bot-control/tree/master/config/charm-single14:13
beisnerso ceph single is good, and the odl ones get the right vars, but odl seems to be trusty-only14:13
jamespagebeisner, I just put up a fix for odl - it was missing systemd support for wily14:13
beisnerjamespage, sweet, thanks14:14
jamespageI had that in an old bzr branch that I had some other stuff in14:14
jamespagepicked it out - hopefully should work OK now14:14
beisnerjamespage, did you see the c-h fork that one of the odl charms is using?14:14
jamespagebeisner, yes14:14
jamespagebeisner, openvswitch-odl is a bit of a mess tbh - we need to move it to layers properly14:15
jamespagebeisner, it now passes amulet smoke at least14:15
jamespagehttps://review.openstack.org/#/c/287153/14:15
jamespagebeisner, just kicked off a full run of that14:16
jamespagebeisner, another fairly trivial one - https://review.openstack.org/#/c/289249/14:18
beisnerjamespage, oooo.  idea.  we should have more magic words to kick of relevant mojo specs.  in this case, it'd be the ssl-everywhere specs.  it would take rejigging the specs a bit to use the change branch, but doable and probably what we want.14:19
jamespagesounds awesome14:19
jamespagetinwood, not sure whether you spotted but https://review.openstack.org/#/c/288733/ needs a rebase14:25
tinwoodjamespage, Thanks for spotting this.  I was waiting on gnuoy's keystone_v3 to get merged before I did the rebase.  I'm guessing that's gone through, so I'll rebase after I push this fix to charm-helpers.14:27
jamespagetinwood, it has14:27
tinwoodthanks, will do.14:28
jamespagethedac, narindergupta: hey - I'm due to push the nuage charms live today - but I think they are all in a private team I can't see14:31
jamespagehttps://bugs.launchpad.net/charms/+bug/151067214:32
mupBug #1510672: Nuage Canonical Charm: vrsg <Juju Charms Collection:Fix Committed> <https://launchpad.net/bugs/1510672>14:32
narinderguptajamespage: let me give you access for same.14:33
jamespagenarindergupta, ta14:33
narinderguptajamespage: you are part of team now and will subscraibe you that bug14:34
narinderguptajamespage: done14:35
narinderguptajamespage: please let me know once live so that we can comnunicate the same to nuage team as well14:37
jamespagemarcoceppi, ok I'm going to put these nuage charms into the charm store using charm upload/publish etc...14:40
marcoceppijamespage: gl14:40
jamespagemarcoceppi, if I place them under 'charmers' does that make them the official charm?14:40
marcoceppijamespage: no, that's not really how it works14:41
jamespagemarcoceppi, ok I'm missing a step then14:41
marcoceppijamespage: you upload then publish them /somewhere/14:41
jamespageI could see how to go from development to published14:41
marcoceppiie ~nuage/trusty/nuage-charm14:41
marcoceppior whever14:42
jamespageok14:42
marcoceppithen, you just "charm promulgate"14:42
jamespageoh - ok14:42
jamespagelemme try that14:42
jamespageand that makes that revision the actual official one then...14:42
marcoceppijamespage: pretty much14:44
jamespagemarcoceppi, bleh - charm-store does not know I'm a member of nuage-charmers...14:47
jamespageI suspect regular injestion from lp?14:47
marcoceppijamespage: what's the error you're getting? have you `charm login` yet?14:47
jamespage"unauthorized: access denied for user "james-page"14:48
jamespage"14:48
jamespagemarcoceppi, I've been publishing aodh all morning so I know I'm normally ok14:48
jamespagehttps://jujucharms.com/u/james-page/aodh/914:48
jamespageI guess I can put them under charmers for now and move them later14:49
marcoceppijamespage: huh, looks like you're a member as of 2 mins ago ;) https://launchpad.net/~nuage-charmers14:49
jamespagemarcoceppi, yeah - I just created that team :-)14:49
marcoceppijamespage: I wouldn't moving later sounds painful14:49
marcoceppijamespage: try logging in again?14:49
marcoceppijrwren: help ^?14:50
marcoceppierr, frankban ^?14:50
rick_h__jamespage: will have to log out/in to catch the new team?14:51
jamespagerick_h__, how do I logout?14:51
jamespagebeing a dumbass14:51
rick_h__jamespage: oh, from cli?14:51
rick_h__jamespage: rm -rf .go-cookies14:51
jrwrenrm ~/.go-cookies, IIRC14:51
rick_h__jamespage: think it's still there14:51
jamespageta that did the trick14:52
marcoceppi\o/14:52
* marcoceppi pines for the new charm command14:53
jamespageworking nicely14:55
jamespagenarindergupta, https://jujucharms.com/u/nuage-charmers/14:55
jamespagerick_h__, marcoceppi: the series in metadata support is great bt14:56
narinderguptajamespage: thanks14:56
jamespagew14:56
rick_h__jamespage: <314:56
marcoceppijamespage: yeah, I can't take credit for that, but it makes charming so much easier14:56
narinderguptajamespage: vrsg is not listed yet. Are we releasing vrsg as well?14:56
jamespagenarindergupta, I have slow upstream internet :-)14:57
marcoceppijamespage: what a concept, you're the bottleneck to the store and not some ingestion process ;)14:57
jamespagemarcoceppi, lol14:57
narinderguptajamespage: thanks14:58
jamespagemarcoceppi, I was local deving this morning and deploying on serverstack - boucing via the charm-store was neat14:58
jamespagenarindergupta, all done14:58
narinderguptajamespage: thanks I can see it now14:58
marcoceppi:D jamespage with the new channel stuff, it'll be even more awesome to rev around in the store14:58
jamespagenarindergupta, a bundle would be a nice next step :-)14:58
narinderguptajamespage: yeah thay have bundle and i will ask team to work on with latest upstream charm and submit for review14:59
jamespagenarindergupta, sure14:59
jamespagethedac, all promulgated - did it new style15:02
jamespagethedac, I'll explain later15:02
marcoceppijamespage: looks great https://jujucharms.com/nuage-vrs/15:04
jamespagemarcoceppi, indeed15:04
jamespagesomething is odd with interface-rabbitmq - always takes forever to clone15:05
lazyPowermarcoceppi - just one thing, and i'm guilty of this too. but the card says "by: undefined"15:11
lazyPowerwe're missing a data point on the charms to populate that field in the card15:11
marcoceppilazyPower: that's something for the charmstore15:12
magicaltroutalso it would be cool (if you can't already) to embed a paragraph of the readme into the card15:13
beisnerjamespage, shall we land openvswitch-odl?  full passes too.  https://review.openstack.org/#/c/287153/15:15
jamespagebeisner, go for it15:15
jacekncould one of the charms tell me if hold up on https://bugs.launchpad.net/charms/+bug/1538573 is expected? AFAICT it just needs to be merged15:16
mupBug #1538573: New collectd subordinate charm <Juju Charms Collection:Fix Committed> <https://launchpad.net/bugs/1538573>15:16
jamespagethedac, gnuoy, beisner: retro'ed my upload script into designate* charms15:23
jamespagehttps://jujucharms.com/u/openstack-charmers-next/designate15:23
jamespagehttps://jujucharms.com/u/openstack-charmers-next/designate-bind15:23
magicaltroutjacekn: for some reason that request is blankly ignored :) I even asked yesterday for you and got no response either......15:23
jamespagemarcoceppi, is the 'charm' binary a go binary?15:24
magicaltroutyou must have done something mean in a past life15:24
beisnerjamespage, cool.  we should probably add both to openstack-charmers @ github for dev, then propose upstream projects from there.15:24
beisneraodh and designate that is15:24
jamespagebeisner, we can actually just slurp them direct from lp15:24
beisnerjamespage, oh cool.15:24
jamespagebeisner, yah - them being git repos and all15:24
jamespagebeisner, we should probably sort out some tests first tho15:25
beisnerright15:25
jamespagethey are a bit cowboy right now but only due to the very early lifecycle they are in15:25
jamespageI'd prefer to push under openstack once we have them in better shape...15:25
beisnerack15:25
jamespagebeisner, series in metadata is a must for all of our charms...15:26
jamespageits a single charm upload command and the charm-store does the rest!15:26
beisnerjamespage, yes. so, what happens if we define series now, and try to use the charms with 1.25.x ?15:26
jamespagebeisner, it all works15:26
beisnerwell then we should add that metadata now :-)15:27
jamespagebeisner, charm store interprets the cs:xxx request and figures out the right thing todo15:27
jamespagebeisner, agreed15:27
jamespagebeisner, I feel we could move to a post-commit charm upload quite quickly now15:27
jamespagebeisner, http://paste.ubuntu.com/15341662/15:28
jamespageits that simple15:28
jaceknmagicaltrout: maybe people are afraid of collectd :)15:29
magicaltroutjacekn: indeed15:30
magicaltroutspam the mailing list as well until you get a response :)15:30
magicaltroutpost a commend on the LP tracker as well15:30
magicaltroutsomeone will be watching somewhere15:30
jaceknI'm also afraid that there is a bigger problem with the review process here15:31
magicaltroutjacekn: i believe the process is being overhauled so its a lot more visible, but you need to ask marcoceppi and/or tvansteenburgh about that stuff15:32
jaceknthere should be no need to chase your contributions, it's charmers who should be chasing and encouraging people to do this work15:32
tinwoodjamespage, beisner: are you seeing anything odd with ceilometer testing?15:32
magicaltroutit shouldn't take 3 or 4 days of asking to get an answer :)15:32
magicaltroutabsolutely jacekn15:32
jamespagetinwood, yes - what do you see?15:32
magicaltroutkick marcoceppi15:32
tinwoodTypeError: can't pickle thread.lock objects.15:32
jamespagetinwood, nope never seen that one15:33
tinwoodjamespage, it's in ceilometerclient/v2/client.py15:33
tinwoodMight be a version thing.15:33
* tinwood hmmm15:33
jamespagemaybe...15:33
marcoceppijamespage: it is, it's being switched to that in xenial15:34
magicaltroutjacekn: my charm went into the review process, got reviewed once then stopped, but I didn't know if I had to do something or not to get it re-reviewed, so its just waiting until I get enough time to stand it back up again15:34
magicaltroutso I know what you mean15:34
thedacjamespage: narindergupta: \o/ Thanks for getting nuage charms promulgated. That was a long time coming.15:34
marcoceppijacekn: there's a huge problem with the review process, it's being overhauled with a public beta of the new process coming out in a few weeks15:34
jamespagenarindergupta, what's your lp id?15:35
narinderguptathedac: thanks for your patience as well i know it was long dur15:35
thedacno problem15:35
narinderguptajamespage: narindegupta15:35
jaceknmarcoceppi: cool! Maybe in the mean time nominate one person a day and put them in the topic here so that people know who to chase?15:35
marcoceppijacekn: what do you mean?15:36
jamespagenarindergupta, thedac: I created https://launchpad.net/~nuage-charmers15:36
jamespagethat's the team under which the charms are uploaded and published on the charm store15:36
thedacgreat15:36
jaceknmarcoceppi: so instead of me asking every day and getting silence I could hilight somebody directly and get a response, even if that response is "your review is in the queue"15:36
narinderguptajamespage: thanks15:36
jamespageso adding people to that will allow future charm upload's15:36
narinderguptajamespage: gotch you15:37
jamespagethedac, narindergupta: they are one of the first partners I've promugated this way ...15:37
jamespageits neat15:37
thedacSounds like a much better process15:37
narinderguptajamespage: yeah looks cool15:37
jamespagenarindergupta, if they want to move they charm development out of launchpad that's ok - the requirement for bzr branches for charm injestion is going away15:37
narinderguptajamespage: is it possible to move other partners also on same process specially plumgrid?15:37
jamespagenarindergupta, yes15:38
narinderguptajamespage: please look into it whenever gets time. Also it seems nuage and plumgrid wants to stick to launchpad for now. May be in future they might move to github15:39
jamespagenarindergupta, they can do git on launchpad if they prefer - and this is only vcs15:39
jamespagenot bug tracking etc...15:39
narinderguptajamespage: gotch you and will inform them.15:40
jamespagenarindergupta, I made you an admin of nuage-charmers so you can add the nuage guys15:41
narinderguptajamespage: sure will ask the team who else to be involved and add them.15:41
tinwoodjamespage, is ceilometer charm written against the v2 client?15:41
jamespagetinwood, tbh you're outside of my knowledge now15:42
jamespageit might be - the tests?15:42
tinwoodoh it's definitely tests.  Whose our ceilometer specialist? :)15:42
marcoceppijacekn: well, the queue is open, http://review.juju.solutions15:42
jamespagetinwood, sounds like you might be now :-)15:43
* tinwood lol15:43
tinwoodjamespage, I will dig into it.15:43
jamespagetinwood, tbh its always been a peripheral charm - not that many users user it15:43
jamespagewe don't on serverstack15:43
tinwoodah, I see.  I don't think it'll be a big change, just need to work out what's going on and whether it needs to be backwards compatible.15:44
jamespagelazyPower, you gonna use charm upload for nexenta as well?15:44
lazyPowerYep!15:44
lazyPowerNow that all the pipeline bits are there, there's almost no reason not to :)15:45
jamespageindeed15:45
beisnertinwood, ceilometer charm tests seem ok.  lmk if you see troubles therein.15:46
tinwoodthanks beisner - it's probably a difference in versions on the test box vs my bastion.15:51
tinwoodbeisner, I have on the bastion: python-ceilometerclient             2.3.0-0ubuntu115:52
cory_fuIs it always the case that the first leader-elected hook will run before install?15:57
=== JoseeAntonioR is now known as jose
deanmanIs there a way to download manually the cloud-trusty lxc image before issuing a deploy --to lxc:x ?16:08
marcoceppideanman: there is16:13
marcoceppikind of16:13
marcoceppiwell, in general, it's in http://cloud-images.ubuntu.com, but the process for preseeding on a deployed node I'm not 100% on16:13
deanmanmarcoceppi: when issuing a deploy it's not very informative on what goes on the background and whether is downloading the lxc or something. So i was thinking that maybe if i could download it manually i could present some more feedback to the user...16:16
marcoceppitvansteenburgh: my stab at updating charmworldlib turned out pretty decently using theblues instead, finishing up tests now16:24
tvansteenburghmarcoceppi: excellent16:24
marcoceppiit's not a perfect match charmworldlib -> libcharmstore, but it's easy enough to patch16:24
aisraelIt looks like the base charm layer is installing/upgrading pip outside of what's packaged in trusty, creating a /usr/local/bin/pip that calls python3 instead of python2. Does that sound right?16:34
aisraelI'm running into issues because something I'm installing has a syntax error with python3. I expect pip vs. pip3 similar to the packaged versions.16:35
stokachuwallyworld: new bootstrap for maas built-in is nice16:43
stokachuwallyworld: especially now you can just define your credentials for maas and not a local name16:43
pmatuliswith ec2 provider, how do i specify the instance type for the controller? tried '--config instance-type=t2.micro' but it didn't work, and did not complain16:46
marcoceppiaisrael: if you need to, use the venv flag in the basic layer to work around this16:52
aisraelmarcoceppi: ack. I'm trying the wheelhouse approach, but I'll look at that next if this doesn't work.16:53
aisraelmarcoceppi: in general, though, I'm worried this behavior could be problematic (pip actually being pip3)16:54
marcoceppiaisrael: yes, this is why I always recommend we use virtualenv for all packaging and managing of pip16:55
marcoceppideb and pip are competing packaing formats, and many people don't care16:55
jamespagetvansteenburgh, hey - can we get the juju-deployer release into https://launchpad.net/~juju/+archive/ubuntu/stable ?16:57
jamespagethen I can transition our core bundles over to use git directly rather than lagging on bzr mirrors...16:57
aisraelmarcoceppi: That totally sounds like a blog post waiting to be written. ;)16:57
marcoceppiaisrael: I will, getting tired of finding problems because people pip install willy nilly16:58
* marcoceppi rage posts16:58
tvansteenburghjamespage: yeah. have you used the latest release?16:59
=== bcsaller_ is now known as bcsaller
jamespagetvansteenburgh, yes I put it in xenial last week and have been using it since...17:00
tvansteenburghjamespage: great, thanks. i'll get it in stable then17:00
marcoceppitvansteenburgh: lmk if you need help backporting to the ppa17:03
* marcoceppi has a script17:03
jamespagetvansteenburgh, ta17:04
tvansteenburghmarcoceppi: i always just ask frankban to do it. i need to fix a build problem first though17:04
frankbantvansteenburgh: I think we decided to just copy the daily built deployer package when you are ready for a new release and you have QAed the deb17:05
tvansteenburghfrankban: yes that's correct!17:06
marcoceppifrankban: where's that built?17:06
cholcombehow do you specify the amazon machine image when deploying ?17:06
tvansteenburghhttps://launchpad.net/~ahasenack/+archive/ubuntu/juju-deployer-daily17:06
tvansteenburghmarcoceppi:  ^17:07
frankbanmarcoceppi: there17:07
rick_h__cholcombe: the instance type?17:07
marcoceppicool17:07
cholcomberick_h__, yeah i want to deploy on xenial to test17:07
rick_h__cholcombe: oh series?17:07
rick_h__cholcombe: --series=17:07
cholcombeah cool17:07
rick_h__cholcombe: on 2.0?17:07
rick_h__cholcombe: or 1.25?17:07
cholcombeno i'm 1.2517:07
rick_h__cholcombe: so there you need to local charm it and do the series directory/etc17:08
cholcombelooks like maybe juju set-env "default-series=xenial" ?17:08
stokachuso how do i bootstrap with juju 2.0 and define a different default model?17:22
stokachuI was thinking something like: juju bootstrap maas-production:prod1 maas/192.168.10.114 --debug --upload-tools17:23
rick_h__stokachu: 'default model'?17:23
stokachuso when you define the controller it creates a model with the same name17:23
rick_h__stokachu: oh, that's coming in the future code17:23
rick_h__stokachu: I thought it was in beta2 to go out today but I'm told it didn't make it17:23
stokachuah ok17:23
stokachui would like to have like maas-production:development,staging,production models17:23
rick_h__stokachu: soon, (beta3?) the default model will always be called admin, and that's the main controller model. Juju will also create a model called 'default' which you are auto put into17:24
rick_h__stokachu: and to change that you can pass an arg that's something like '--default-name'17:24
rick_h__stokachu: so you'd have models "admin" and your custom name passed on the flag17:24
stokachuso there will always be a default model for admin?17:24
rick_h__stokachu: there will always be an "admin" model as that's technically the 'controller'17:24
rick_h__stokachu: but folks shouldn't mess with it much, but we expect folks to do things common to all models there17:25
stokachuyea i think that's a bit confusing, having a 'controller' but a model that is also the 'controller'17:25
rick_h__stokachu: yea, it's an implementation detail that's leaked that we'll work on over time17:25
stokachuok cool17:25
rick_h__stokachu: but yea, you can't remove-model admin17:26
rick_h__stokachu: because that's your controller17:26
stokachuah right, yea i think once the definition of the admin model is more clearer that'll help the confusion17:26
rick_h__stokachu: yep17:26
rick_h__that's the hope17:26
stokachuis the --default-name something that was part of the changes in beta2 that didnt make it?17:27
stokachuim running from master as well17:27
tvansteenburghahasenack: ping17:35
ahasenacktvansteenburgh: hi17:37
tvansteenburghahasenack: hey, i'm trying to figure out why juju-deployer daily build started failing. i can see the test failure in the build log, but the confusing bit is when i look in older (successful) build logs, there's no indication that `make test` was ever run17:39
ahasenacktvansteenburgh: I think, if I remember correctly, that tests might be skipped if it detects it's in a launchpad buildd17:39
ahasenacktvansteenburgh: maybe that check failed, and it thought it should run the tests17:39
ahasenackI have to check17:40
bbaqarHey guys. Any way I can get the CIDR of the maas network in a charm?17:54
tvansteenburghahasenack: okay thanks for your time. i just pushed a test fix so we'll see if that fixes the build18:00
tvansteenburghjamespage: whenever this build succeeds we can get the package moved to stable ^18:03
tvansteenburghahasenack: okay the build is fixed, but the version is behind (should be 0.6.4, not 0.6.1). how does that get updated?18:11
ahasenacktvansteenburgh: it's in the packaging branch18:19
ahasenacktvansteenburgh: let me update that18:19
ahasenacktvansteenburgh:  juju-deployer - 0.6.1~bzr168~48~ubuntu16.04.1 <-- that's your build?18:20
tvansteenburghahasenack: yep18:20
ahasenacktvansteenburgh: updated, r4918:21
josemarcoceppi: ping18:22
marcoceppio/18:22
josemarcoceppi: do you have a sec to take a look at an ubucon branch?18:22
marcoceppijose: link me up18:23
josehttps://code.launchpad.net/~ubucon-site-developers/ubucon-site/update-source-action18:23
tvansteenburghahasenack: ta. for future reference, do i need to contact you for version bumps?18:23
ahasenacktvansteenburgh: I think so, the pkging branch the recipe uses is mine, https://code.launchpad.net/+branch/~ahasenack/juju-deployer/juju-deployer-packaging18:23
josemarcoceppi: so, I think that update-source action is pretty straightforward, but are there any services that need restarting apart from that?18:24
josemarcoceppi: action is here http://bazaar.launchpad.net/~ubucon-site-developers/ubucon-site/update-source-action/view/head:/actions/update-source18:24
marcoceppijose: that won't work18:24
marcoceppijose: you have to run an entire migration, etc in addition18:24
tvansteenburghahasenack: ok thanks!18:24
josemarcoceppi: the site isn't live-running from the directory?18:24
ahasenacktvansteenburgh: if you want you could copy the recipe to a team-owned account perhaps18:24
marcoceppijose: it is, but you have to run db migrations and such in addition to just updating the files18:25
josehmmk I'll dig a bit more into it18:25
marcoceppijose: you need the event to show up in the reactive framework and to reset the djang.ready or intalled or whatever event18:26
joseok, thanks18:27
tvansteenburghahasenack: can you force a new build so i get the new version?18:27
ahasenacktvansteenburgh: yep18:27
tvansteenburghahasenack: ta18:27
ahasenackdone: https://code.launchpad.net/~ahasenack/+recipe/juju-deployer-daily18:27
ahasenacktvansteenburgh: can you kick that as well? Just curious18:28
tvansteenburghahasenack: i don't see a way to do so18:28
ahasenackok18:29
ahasenack"Request build(s)" green link just above "Recipe contents"?18:29
tvansteenburghahasenack: heh, there it is18:29
ahasenackcool18:29
tvansteenburghgood to know, thanks18:30
tvansteenburghahasenack: just noticed that frankban is offline now. can you copy that build to juju/stable, or tell me who can? jamespage has been using it for a week now and is ready to get it in stable18:34
ahasenackwow, that built fast18:35
ahasenacktvansteenburgh: hm, there might be a problem with the version number18:35
ahasenacktvansteenburgh: xenial has 0.6.4-0ubuntu118:36
ahasenackthat's the same?18:36
ahasenackI mean, it's higher than my PPA, and on purpose18:36
tvansteenburghit's the same18:36
ahasenacktvansteenburgh: that being said, no, I cannot copy. I don't see the juju stable ppa in the target list18:37
tvansteenburghahasenack: ok, will wait til tomorrow, thanks18:37
tvansteenburghjamespage: ^18:37
ahasenacktvansteenburgh: have you tried sinzui?18:38
ahasenackor any of the juju a folk I bet18:38
tvansteenburghahasenack: good idea, will try sinzui18:38
ahasenacks/a/qa/ I meant18:38
cholcombefor systemd with charmhelpers host.service_stop i need to pass an id parameter.  It looks like I need to add that to the function18:55
cholcombewait.. i think i can pass the service name with the id.  I'm going to try it18:56
wallyworldstokachu: yeah, the built in maas was a last minute idea which seemed worthwhile. we'll get the credentials stuff sroted and it will be even better19:51
tvansteenburghjamespage: new deployer is in juju/stable19:51
stokachuwallyworld: yea man sounds awesome20:06
stokachuwallyworld: is there a way via list-models to determine which one is the admin model?20:30
stokachui want to be able to fitler out the admin model when presenting deployment models to an end user20:30
wallyworldstokachu: for now, it's the one called "admin". we'd have to look at tagging or something to do it better20:31
wallyworldstokachu: wait20:31
wallyworldthat will be the case in the next beta20:32
stokachuah ok20:32
wallyworldfor this beta it's the one named after the controller20:32
wallyworldjuju bootstrap mycontroller lxd20:32
stokachuright i figured as much, rick_h__ mentioned --default-name will that be exposed for the admin model?20:32
wallyworldthe admin model will be mycontroller20:32
wallyworld--default-model will be to name the initial hosted model20:33
wallyworldthe admin model will be "admin"20:33
stokachunot the admin model correct?20:33
stokachuok20:33
wallyworldthe default hosted nodel will be "default"20:33
stokachucool so i can just filter out based on the name20:33
wallyworldyeah20:33
stokachuok perfect20:33
wallyworldwe may do it better with an attribute or something20:33
stokachucan i change the name of default with --default-model?20:33
wallyworldbut for now that will work20:33
wallyworldyes20:33
wallyworldin the next beta20:34
stokachuok cool20:34
wallyworldthe nme of the hosted model20:34
stokachuwallyworld: https://paste.ubuntu.com/15343579/ just to clarify what im thinking20:35
wallyworldlooking20:35
wallyworldstokachu: yep, looks good to me. the next beta should drop next week20:36
stokachusweet20:36
wallyworldlte next week20:36
stokachualso, one last thing i promise, did you see my bug on determining the provider type through list-controllers?20:36
wallyworldyeah, we're looking into it20:37
stokachuok cool thanks man20:37
wallyworldnp, might be a nice surprise next beta also :-)20:37
stokachuhah ill keep a lookout20:37
wallyworldstokachu: btw, thanks for the awesome feedback and bugs etc - we're racing against time to get this work done so that external perspective if great20:40
stokachuwallyworld: np! so far i think the experience is great, just small things here and there20:41
wallyworldyeah, we can fix those :-)20:42

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