/srv/irclogs.ubuntu.com/2015/07/21/#juju.txt

=== natefinch-afk is now known as natefinch
h0mer___hey guys can anyone here help out with a maas/juju/openstack networking question?00:39
tasdomashi06:54
tasdomasI'm working on introducing action support to amulet - should I propose the changes on launchpad or github?06:54
Odd_Blokejose: Pong.07:58
jamespagelazyPower, beisner, coreycb: bug in deployer for git repos08:38
jamespagehttps://code.launchpad.net/~james-page/juju-deployer/git-cwd/+merge/26536508:39
jamespagetvansteenburgh, dpb1: any chance one of you could review https://code.launchpad.net/~james-page/juju-deployer/git-cwd/+merge/26536509:09
jamespagethat fixes from challenges I had with git support09:09
=== lukasa is now known as lukasa_away
=== frobware is now known as mcd
=== mcd is now known as frobware
=== bloodear` is now known as bloodearnest
=== lukasa_away is now known as lukasa
tvansteenburghjamespage: i'll take a look11:45
beisnerjamespage, ah nice ^12:20
aisraeltasdomas: On github: https://github.com/juju/amulet12:59
beisnerhi jamespage, please review ... o-c-t: Q-G rename + pxc + wily/liberty prep   https://code.launchpad.net/~1chb1n/openstack-charm-testing/liberty-prep/+merge/265106   tia!13:31
beisnerhi gnuoy - not quite ready for final review, but wanted to alert you to some re-working in the openstack-mojo-specs @ https://code.launchpad.net/~1chb1n/openstack-mojo-specs/baremetal-bundle-constrainer/+merge/26455813:42
beisner^   this is what uosci is consuming atm, resolves several issues in automation, a few more yet to iron out13:43
gnuoyack, thanks13:43
beisnergnuoy, the lint checker just got a lot pickier ;-)   needed to ensure that specs are using sane u:os combos.13:44
gnuoyah, tip top13:44
jamespagebeisner, +1 lgtm13:44
beisnerjamespage, ty13:45
beisnerjamespage, ok, that's landed13:47
jamespageawesome13:47
arosalesmarcoceppi, aisrael, tvansteenburgh: I am loving cloud-benchmarks.org15:32
tvansteenburgharosales: <315:32
marcoceppiarosales: \o/15:32
arosaleshad an idea I wanted to bounce off you guys15:32
marcoceppiarosales: go for it15:32
arosalesif someone notices a key performance enhancing method is missing from the charm how can we make it clear for them on how to contribute to the charm?15:33
arosalesor they would like to add a benchmark.15:33
marcoceppiarosales: yeah, we have a little bit of a call to action at the bottom, but we don't make it clear. We do link to the jujudocs on writing a benchmark charm/action though15:34
marcoceppiarosales: we ahve a follow up blog post which addresses the comments our latest post has been getting, I think in there we'll discuss how contributions work since we're patching the charm in a few ways to iterate on feedback15:34
marcoceppiarosales: adding it to the about page as well, may not be a bad place at a high level15:35
arosalesAbout page may be nice for some additional pointers to the docs and how to contribute to charms15:36
arosalesmarcoceppi, be nice if on say "http://cloud-benchmarks.org/submissions/6" or "http://cloud-benchmarks.org/services/cassandra" there was a call to action there15:38
marcoceppiarosales: ack15:38
* arosales just thinking outloud atm15:38
arosaleswanted to see what folks thought15:38
marcoceppiarosales: I think it makes sense on the services overview page15:39
marcoceppiresults page as well, but not 100% sure where it'd fit in there15:39
arosalesas we would like to make it super simple for folks to see the benchmarks (done) but also easily contribute code to improve the charms performance15:39
arosalesmarcoceppi, may have to live in the submission page and parse out charm URLs15:39
arosalesmarcoceppi, something to think about. Specifically if we would like folks to contribute make the UI to do so amazingly easy15:40
arosalesin this case contribute performance tunings back to the charm. . .15:40
marcoceppi it's a good point15:42
tvansteenburghyeah it would be nice to parse charm urls out of the bundle and link to them at least15:42
* arosales really like how you got the juju quickstart command right there15:45
arosalesmakes it super simple to try15:45
* arosales was just thinking of try, "branch," tune, submit, share workflow and how that could be modeled for benchmarking15:46
arosalesfood for thought15:46
tvansteenburghgood ideas arosales, thanks15:46
=== dames is now known as thedac
g3narohi,, anyone used juju to deploy docker containers on aws ?16:09
lazyPowerg3naro: I sure have16:12
g3narolazyPower: haev you got any ref. guides for this?16:12
lazyPowerg3naro: are you looking just to spinup the docker based infrastructure and deploy containers to that? or are you looking to deploy your products docker container with juju?16:13
g3naroexactly what im trying to seutp16:13
lazyPoweryou have some options here16:13
g3narodeploy the products (docker container) into aws16:13
g3naroi guess try to see if it makes sense to use juju for that in first place, im not too experience with juju yet either :)16:14
lazyPowerwell, we have a charm that can deploy the docker infrastructure - which takes care of setting up the latest stable docker, configuring the backend storage service (like UFS enablement) - and to deploy container into that theres 2 options. Charm it up as a subordinate and relate to docker, or we can skip the docker charm all together and write a quick bash charm (50 lines or less) to deploy that specific container.16:15
g3naroohhh interesting16:16
g3naroso does infrastructure include things like elastic beanstalk (aws load-balancing app)16:17
g3narothat sounds very similar use cawse as well16:17
lazyPowerJuju doesnt' natively integrate with beanstalk, at least not today.16:17
g3naroahh ok16:17
g3naroso that could be a seperate task16:17
lazyPowerif you're looking to do load balancing, there's work and charms already written that leverages consul, consul-template, dns, and nginx to do this :)16:18
g3narook, nginx probally sounds the way to go16:19
g3naroi had the understanding that the aws ebs with docker does the service registry in one system16:19
g3narobut maybe i just dont understand it well enough16:19
lazyPowerELB can work - but unfortunately we dont have a representation of ELB in juju as it stands today16:19
g3naroahh kk no worries, then16:20
lazyPowerso what you could do, is deploy with juju, then configure ELB in the AWS control panel to point at those nodes.16:20
g3naroyeah that what i was thinking16:20
lazyPowerwhich sounds closer to what you want to achieve16:20
lazyPowerg3naro: https://github.com/chuckbutler/docker-charm is a good place to start. The readme gives you just enough to drill down and run a deployment16:22
g3narointeresting16:22
g3naroyeah i have deployed that into lxc container actually16:22
lazyPowerg3naro: the merge for AUFS backend storage is still pending for the charm store unfortunately :( But its available in my namespace and offers an easy upgrade path from there.16:22
lazyPoweri'm highly surprised if that works. default APPArmor profiles prevent docker from working properly in lxc16:23
g3naroi havent run the app on it16:23
g3narobut it worked on my box just about an hour ago16:23
lazyPowerimpressive, you've done what i've been brain bending around for a couple months now :)16:23
lazyPoweri can't even get the daemon to come online16:23
lazyPowerit gets immediately nuked when it requests cgroups resources16:24
g3naroroot@g3naro-local-machine-3:~# docker --version16:24
g3naroDocker version 1.0.1, build 990021a16:24
g3naroi used a different charm actually16:24
lazyPowerah thats deploying the package from archive16:24
g3naroand just did juju switch local, juju deploy docker16:24
lazyPower1.0.1 is quite old now16:24
g3narotrue16:25
lazyPowerbut that's still the same charm.16:25
lazyPowerjuju set docker latest=true version=1.0.7 will upgrade16:25
g3naroi guess you have to add repo and updated it16:25
g3naroohh16:25
lazyPower:) this is why managing docker as an infrastructure component makes sense. You get independent control of docker, where if you're shipping it with a charm you lose some of that, or you're duplicating effort16:26
g3naroahhh ok,, yeah now i see the point16:26
lazyPowerif you're following the mailing list, we're working through "juju compose" which will allow you to inheret from the docker charm, and only maintain the hooks that are important to your service - so delivering of that container and making sure its got hte proper env + relations.16:26
g3narobut then what about if application is packaged as docker image16:26
g3naroim not on the list, but i think i would be interested to16:27
g3narowell definately would be intersted to16:27
lazyPowerso, using the juju compose methodology, you inheret, write a config-changed hook thats specific to your container, add any relations you need if its going to communicate with other services, and generate your charm. As we cycle and update the docker charm you simply regenerate your charm and publish.16:27
lazyPowerg3naro: i'm going to run for lunch however, if you need additional information feel free to ping. I should be back in about 45 minutes to an hour.16:28
g3narointerestingok cool man, thanks alot16:28
g3naroill be here16:28
lazyPoweralso my colleague mbruzek has some experience with docker and charming :) so feel free to utilize him as a resource as well16:29
* mbruzek waves16:29
g3narowow cool :D16:30
g3narojust fyi, ive only started using juju/lxc/docker <1 month16:30
g3narobut very keen to build this out16:31
g3naroso i think step1 is creating a charm that will create docker inf. in aws16:31
g3narohttps://jujucharms.com/u/mattyw/docker/precise/316:32
g3narothis is what i had installed actually16:32
g3naro"/alias hidelevels.set set activity_hide_level parts joins quits nicks modes"16:33
g3naroseems a bit too quiet now16:38
g3naro:/16:38
mbruzekstill here16:45
g3naroheheh, sorry been rambling a bit16:45
mbruzekalthough your alias came across as text so I don't know how well that would work16:45
g3naroyeah i had to re-send it16:45
g3naroso.. yeah im trying to get my head around this still16:45
g3naroif the application is a docker image16:46
mbruzekJuju deploys a charm in AWS or GCE, or where ever.  That charm installs docker and configures it for you.  Then you can run commands on that unit to start docker containers16:47
g3naroso step 1- deploy the docker inf.16:49
g3narocreating ec2 instances with docker installed16:49
g3narothen deploying application into those boxes16:50
mbruzekg3naro: Juju can create an ec2 instance with docker inside it.  Just deploy the docker charm.16:50
mbruzekThen you can run commands on that unit to start docker containers inside the vm.16:51
g3narook, so on the vm you ship the docker image and run it16:51
mbruzekg3naro: Juju doesn't ship images, it configures the base image.  So a charm installs and configures Docker on that unit.16:52
g3naroohh16:52
mbruzekYou could write a charm that installs docker and starts a container with your application16:52
mbruzekIf you run it in a container.16:52
g3naroyeah that is the step needed then16:52
g3narocharm the application16:52
mbruzekBut you could start with the base image and just install the application on the VM.16:53
mbruzekBut it is up to you how you want to organize and architect that16:53
g3narohmm yeah,, thats what i have to find out,, and fast :)16:53
mbruzekg3naro: Well just ask here if you need help.  I have to run for lunch too.  There are others that can help.  Also lazyPower and myself use #system-zoo to discuss container stuff, you are welcome to join us there as well.16:56
g3narook cool man! thanks so much16:56
g3naroim trying to get started so would this charm lazy provided before be stuitable to test16:57
mbruzekg3naro: #juju is still your best bet for general Juju questions.   #system-zoo is a smaller group of container related technology16:57
g3naroyea.. juju is still new for me, and ill have few more by 2morrow :)16:57
g3naroim in UTC time16:57
mbruzekWe will be here16:57
g3naronice :)16:57
tasdomashi, I've submitted a PR that adds action support to amulet16:58
tasdomashttps://github.com/juju/amulet/pull/8016:58
mbruzekThere are folks working on Juju from all over the world.  I happen to be in CST, but we have an office in London, lots of folks on that timezone16:58
g3naroyeah man, would be great to be part of ubuntu one day ;)16:58
mbruzektasdomas: Thank you for your contribution!  tvansteenburgh, or marcoceppi will likely be the ones to review that16:58
tasdomasmbruzek, don't thank me yet ;-]16:59
mbruzektasdomas: if you don't get a review let me know and I can take a look as a back up.16:59
mbruzekhappy to have interest in making our tools better16:59
mbruzekOk I have to get going to lunch17:01
g3naroez bro17:01
mbruzekbe back in a few17:01
tvansteenburghtasdomas: thanks for the PR, i'll have a look in a bit17:03
joseOdd_Bloke: hey, I had some questions about the ubuntu-repository-cache charm. if you had a min, mind a pm?17:08
marcoceppig3naro: hey! Thanks for the contribution, we've left some feedback, though I usually jsut defer to tvansteenburgh17:20
tvansteenburgh1s/g3naro/tasdomas/17:21
=== tvansteenburgh1 is now known as tvansteenburgh
marcoceppiblehhhhhhh17:24
* marcoceppi disappears for a while17:24
lazyPowerg3naro: o/17:37
tasdomasmarcoceppi, thanks for the feedback17:46
marcoceppitasdomas: thanks for taking a stab at this, overall the implementation looks great, I just had some small comments that are pretty inconsequential17:48
tasdomasmarcoceppi, I'll try to address the comments shortly - I need the implementation of actions to be able to test my own charm (that uses actions extensively)17:49
marcoceppitasdomas: well we're starting ot see a lot of actions show up, so it's pretty perfectly timed17:49
Odd_Blokejose: I'm EOD now, but rcj can probably answer them.17:52
Odd_Bloke(Sorry rcj ;)17:52
joselol17:52
rcjOdd_Bloke, jose: no problem, I can answer questions on that17:53
tasdomastvansteenburgh, ping?18:02
* arosales got a sack full of k8 shirts18:12
arosalesI made sure to get a few for marcoceppi cause I know he loves himself some docker18:12
marcoceppiarosales: the winters are long and harsh here ;)18:12
arosalesmarcoceppi, :-) you need something to change the midget's oil in18:15
=== Viperz28_ is now known as Viperz28
=== xwwt_ is now known as xwwt
tvansteenburghtasdomas: pong18:58
tasdomastvansteenburgh, marcoceppi - thanks for the reviews, I'll speak to you tomorrow19:09
tvansteenburghtasdomas: sounds good, thanks!19:10
lamontif I have a service that was deployed and working with juju 1.18.1-0ubuntu1, and now I have juju 1.20.11-0ubuntu0.14.04.1 and it says 'ERROR no such request "NewServiceSetForClientAPI" on Client', what is the best fix?19:34
marcoceppilamont: well, that's not supposed to happen19:34
lamontmarcoceppi: I have an existance case to the contrary.. :(19:35
marcoceppidid you do an upgrade or fresh deploy?19:36
lamonthttps://pastebin.canonical.com/135766/19:37
lamontwhich isn't the answer to your question19:37
lamontdeployed with 1.18.1 (maas host, which ahs been up for 6 days) - dist-upgrade yesterday brought in 1.20.11 (backported to trusty), and today, juju set fails to perform19:38
lamontbut the 1.18.1 binary works just fine19:38
lamontmarcoceppi: interestingly, it looks like 1.18 was just ignoring the error and plowing on ahead, based on what the 1.18 binary produced in the machinelog19:40
lamontin slightly different questions: what do I need to restart to have juju notice that I changed the IP address of the machine?  and what side effects should I expect?19:46
marcoceppilamont: typically you need to restart the juju-machine agent on the instance, IIRC19:48
lamontmarcoceppi: should have no side effects?19:50
marcoceppilamont: well, 1.20 is still pretty "old", so can't say it won't have any side effects, ideally it should recover jsut fine. the agent will go from up to down to up again in status and in that time events will be queued but not dispatched, if a hooks is running it'll likely be marked as an error19:51
aisraelis debug-hooks part of juju-core20:37
aisraelor a plugin?20:37
lazyPoweri'm fairly certain its a plugin that lives in core.20:39
lazyPowerbut, a core dev might be a better candidate to answer that20:40
lazyPoweraisrael: i'm wrong its core - https://github.com/juju/juju/blob/596210921f2291010d94682f3fcc3cea71534efe/cmd/juju/commands/debughooks.go20:40
aisraellazyPower: ack, thanks. To open a bug report or write a patch, decisions decisions.20:41
* aisrael goes the lazy route20:41
lazyPoweraisrael: why not both?20:41
lazyPoweralso, i had no idea you hacked in golang20:41
aisraellazyPower: Maybe after I'm out of the weeds. :/20:42
lazyPowermarcoceppi: stop working aisrael so hard20:42
aisraelVery minor hacking in it, but it's piqued my curiosity so I just need a strong enough itch to scratch.20:42
lazyPoweri just recently picked up the golang bootcamp myself, so i can start learning and helping20:43
aisraelThere's already a bug for what I need. Almost two years old. Time to fire up the go machine20:48
mad4compHey guys.  I'm trying to deploy a Maas/Landscape/Opestack instance with 8 machines connected to two networks, but for some reason it seems that all my vm's get spun up, but can't reach out to the internet to configure the meta-data service.  Anyone know if this is a bug?21:14
blrhi there, is there a workaround for https://bugs.launchpad.net/juju-core/+bug/146433521:31
mupBug #1464335: debug-log does not work with local provider <debug-log> <local-provider> <regression> <vivid> <juju-core:Triaged> <juju-core 1.24:Fix Released by axwalk> <https://launchpad.net/bugs/1464335>21:31
tvansteenburghblr: i usually just tail the log i care about under /var/log/juju*22:02
blrtvansteenburgh: yep I'll do that thanks22:04
=== _thumper_ is now known as thumper

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