[00:39] <travnewmatic> not sure if this is the right place to ask
[00:40] <travnewmatic> but can anyone point me in the direction of deploying centos with maas
[00:40] <sarnold> travnewmatic: #maas ?
[00:40] <travnewmatic> i've asked
[00:40] <sarnold> aha
[00:41] <travnewmatic> the closest they've got was this thing https://github.com/jjasghar/maas/blob/centos/recipes/centos.rb
[00:41] <travnewmatic> said it was a chef recipe
[00:41] <travnewmatic> but i'm not sure how to use it
[03:11] <hazmat> travnewmatic: requires uploading custom linux image
[03:12] <travnewmatic> i got that
[03:12] <travnewmatic> its where do i get that custom linux image thats the question
[07:37] <toyo|work> for whatever reason juju-gui is stuck pending
[07:37] <toyo|work> dunno whats up
[10:37] <Guest85589> hello
[12:00] <Murali> Hi jamespage
[12:00] <jamespage> Murali, o/
[12:01] <Murali> we are able to see the ipaddresses for lxc containers
[12:01] <Murali> with fastinstaller
[12:07] <Murali> jamespage all the charms for openstack are installed and showing green in juju-gui. But we are not seeing the relations b/n the charms does it takes some time to come-up
[12:07] <jamespage> Murali, \o/
[12:08] <jamespage> Murali, I think the gui will wait for all units to come up and then add the relations
[12:08] <Murali> http://paste.ubuntu.com/10323487
[12:09] <Murali> it looks like everything is started
[12:09] <Murali> or installed
[12:11] <Murali> http://paste.ubuntu.com/10323517
[12:11] <Murali> these keeps repeating the debug-logs
[12:18] <Murali> jamespage its waiting for longtime. do we need trigger something here?
[12:24] <jamespage> Murali, looking
[12:32] <jamespage> Murali, I don' think that log message is anything to worry about
[12:32] <jamespage> Murali, I'm at a bit of a loss as to why no relations
[12:32] <jamespage> Murali, any errors in the juju-gui?
[12:43] <Murali> jamespage we saw one notification that error oaccured but no description
[12:44] <jamespage> Murali, tbh I'm not a juju-gui expert
[12:44] <jamespage> Murali, you can use juju-deployer to try and add them now
[12:44] <jamespage> Murali, download the bundle and use "juju-deployer -c bundles.yaml" - it should see that the services are deployed and just add the relations
[12:48] <Murali> ok will try this
[12:59] <Murali> jamespage do you need to do juju bootstrap again?
[12:59] <jamespage> Murali, no
[13:00] <Murali> http://paste.ubuntu.com/10324052
[13:00] <Murali> we are seeing this meassage?
[13:05] <jamespage> huh?
[13:05] <jamespage> odd
[13:06] <jamespage> Murali, does your bundles file look like this - http://paste.ubuntu.com/10324139/ ?
[13:08] <Murali> ours is http://paste.ubuntu.com/10324149
[13:08] <Murali> basic in top is missing in my file
[13:10] <jamespage> Murali, I have no idea why it does this but use - https://api.jujucharms.com/v4/bundle/openstack-28/archive/bundles.yaml.orig
[13:28] <Murali> jamespage after adding "openstack:" in our bundle.yaml file we able to see relations are getting adding
[13:29] <Murali> top corner of the file
[15:27] <CompanionCube> Is this the right channel for questions about building juju from source?
[15:30] <jw4> CompanionCube: probably - what is your question?
[15:30] <CompanionCube> wait, I think I'm missing some packages
[15:30]  * CompanionCube forgot to install mercurial
[15:31] <jw4> CompanionCube: I think the make install-dependencies step will ensure all those dependencies
[15:31] <CompanionCube> yes, but mercurial is apparently needed to download some of the packages used by go get
[15:32] <jw4> CompanionCube: yes, I'm pretty sure make install-dependencies will install mercurial, and 'go get github.com/juju/juju' will get that makefile at least
[15:32] <CompanionCube> ...good point
[15:41] <lazyPower> CompanionCube: epic handle. o/
[15:43] <CompanionCube> lazyPower: Been using it on multiple networks for a few years.
[15:44] <CompanionCube> Freenode is not one of my usually frequented ones however :p
[15:44] <lazyPower> Welcome to the crowd :) really happy to see new potential juju-core hackers
[15:45] <CompanionCube> not a hacker, just a bug that's affecting me is at 'Fix Comittted'
[15:49] <CompanionCube> Wait, damm. Just realised my target-system is an ARM computer, so I'll need to dig out an ARM emulator.
[15:50] <adamgreig> mbruzek: heya
[16:00] <lazyPower> CompanionCube: thats typically how it starts right? :)
[16:13] <mbruzek> adamgreig: Have a nice day, let me know if you have any other questions.
[16:14] <adamgreig> thanks again, will do
[16:14] <adamgreig> it certainly all makes a lot more sense to me now :)
[16:23] <whit> adamgreig, was nice to meet you!
[16:24] <whit> adamgreig, and thanks for coming to charm school so well prepared :)
[16:24] <adamgreig> it was good to meet you too, thanks for your time! haha, you're welcome
[16:25] <adamgreig> wish I'd found the debug tools before I started just sshing into everything ;)
[16:25] <whit> adamgreig, yeah, they make a huge difference. especially the syncing w/ dhx
[16:25] <adamgreig> yea that sounds ace
[16:26] <adamgreig> very familiar with fixing something on a running system and then nuking it and realising I hadn't copied the changes back...
[16:26] <whit> adamgreig, "the joy of the cloud"
[16:27] <adamgreig> hehe
[16:28] <whit> adamgreig, I know you are on a rather tight deadline for the demo, so just to reiterate, do not hesitate to pick our brains
[16:29] <whit> adamgreig,  if anything does not make sense or is not intuitive.   that's why we are here!
[16:30] <adamgreig> got it, thanks very much :)
[16:30] <adamgreig> time to get started on this charm then I guess ;)
[16:32] <adamgreig> should I mostly be sticking with trusty for new stuff?
[16:34] <lazyPower> yeah
[16:35] <lazyPower> unless you have a specific need to target p recise, i would target trusty
[16:38] <adamgreig> cool
[16:47] <adamgreig> is there any particularly juju-integrated way to worry about mapping machine IPs to DNS, or do you tend to do that out of band?
[16:47] <lazyPower> adamgreig: actually - interesting that you ask that
[16:47] <lazyPower> i have written a bind9 charm to use in dev (not in prod)
[16:47] <lazyPower> but i have plans on extending this with "proxy service wrappers"
[16:47] <lazyPower> let me fish up the url for you
[16:48] <lazyPower> https://github.com/chuckbutler/dns-charm - again, not prod ready (so this may not be useful to you)
[16:48] <adamgreig> ah neat, so a service could tell bind what its IP is and what it'd like its hostname to be?
[16:48] <lazyPower> basically you define a blanket domain on this bind provider
[16:49] <lazyPower> and each service gets its own group/host dns entry, and upon relation-join it updates the resolvconf template to add that dns server
[16:49] <lazyPower> so you can add the ip of that dns-charm to your workstation and get the perks of not having to know your service ip's
[16:50] <adamgreig> cool. and then in theory you have that be authoritative for that zone publically and now your services automatically get their IPs publicised?
[16:51] <lazyPower> correct, its a huge SPOF but as POC ware - thats what its achieved
[16:51] <adamgreig> got it
[16:51] <lazyPower> all contributions in forms of bug reports, feature requests, comentary are appreciated
[16:51] <adamgreig> in theory you could do something very similar only instead of installing bind and updating its local conf, you publish new records to some dns service (AWS's or linode or whatever)?
[16:51] <lazyPower> (and pr's if you're feeling adventerous)
[16:52] <lazyPower> exactly i wanted the dns-charm to be a one stop shop for that
[16:52] <lazyPower> by implementing a provider, you wrap their API and execute the proper motions on behalf of the user in their given provider
[16:52] <lazyPower> like godaddy, awsrt53, dnsimple - all have api's and were targets for the 1.0 release
[16:52] <lazyPower> thats all outlined in docs/HACKING.md
[16:52] <lazyPower> and https://github.com/chuckbutler/DNS-Charm/blob/master/docs/provider.md
[16:57] <adamgreig> nice
[16:57] <lazyPower> I'd love to get back on this in the near future, i haven't touched it since mid 2014 unfortunately. but with some new interest - lets plan and make something great :)
[17:00] <adamgreig> sounds fun! it seems like a pretty neat way to get everything totally set up
[17:00] <adamgreig> atm vzzual's infrastructure is mostly on rackspace's cloud for various reasons but I imagine their DNS API is amenable (not played with it yet)
[17:01] <CompanionCube> I'm getting 'storage/volume.go:11: undefined: names.DiskTag' when running 'go install'
[17:07] <lazyPower> CompanionCube: might want to join #juju-dev - as the core devs are typically paying attention in there.
[17:07] <CompanionCube> ah, okay
[17:08] <CompanionCube> I'll be there shortly
[17:08] <marcoceppi> CompanionCube: you shouldn't need to run go install
[17:08] <marcoceppi> CompanionCube: just `go get github.com/juju/juju/...`
[17:10] <marcoceppi> CompanionCube: you may also need to run `JUJU_MAKE_GODEPS=true make godeps`
[17:11] <CompanionCube> yay works now, got an ARM version of juju built.
[17:11] <lazyPower> \o/
[17:12] <marcoceppi> CompanionCube: if you're bootstrapping anything other than local
[17:12] <marcoceppi> you'll need to bootstrap with --upload-tools when you compile from source
[17:14] <CompanionCube> marcoceppi: anyway to upload tools like that with an already bootstrapped environment? or do I need to tear-down and redeploy
[17:15] <marcoceppi> CompanionCube: was the fix you need on the client or agent side?
[17:15] <marcoceppi> (what was teh bug, btw?)
[17:17] <CompanionCube> https://bugs.launchpad.net/juju-core/+bug/1420049 - visibly affetcs ppc64el, but I spotted the error on my ARM deployment also
[17:17] <mup> Bug #1420049: ppc64el - jujud: Syntax error: word unexpected (expecting ")") <deploy> <openstack> <regression> <uosci> <juju-core:Triaged> <juju-core 1.22:Fix Committed by axwalk> <https://launchpad.net/bugs/1420049>
[17:21] <marcoceppi> CompanionCube: yeah, so you'll need to upgrade juju. You can try a juju upgrade-juju with --upload-tools from the newly compiled juju
[17:21] <marcoceppi> CompanionCube: but it might be easier to just re-bootstrap
[17:21] <CompanionCube> thanks
[17:58] <lazyPower> nicopace: gave you some initial looks over those test plans on the charms i'm familiar with
[17:58] <CompanionCube> Works. Yay :)
[17:58] <lazyPower> +1 on those - good strategies. thanks for publishing the bugs.
[18:41] <Airdawg> Hi ppl. Did something happen with juju-charms? There's only 13 charms/solutions and no bundles.
[18:42] <Airdawg> The number is slowly increasing though.
[22:35] <ctlaugh> I'm looking for some help on the correct way to configure the charm(s) to deploy Nova correctly to use either Neutron or FlatDHCPManager (whatever is easier) when deployed by Juju on a MAAS node.  The node only has 1 network interface that is brought up (eth0) and it is already bridged to juju-br0.
[22:37] <ctlaugh> ^^ The examples I find all involve needing more than one network interface, but MAAS/Juju only bring up 1 of them.