[00:10] Hmm, is the manual provisioning supposed to be as buggy as it is? [00:22] Kyle: you mean the ssh "null" provider? (have they come up with a better name for it yet?) [00:22] sarnold: Yeah [00:22] I just can't get it to bootstrap period [00:23] Kyle: .. if so, probably -- the ssh support is very new, and because the machine doesn't start with a blank slate (as the other providers do), the risk for existing configuration on the systems conflicting with charms is a lot higher.. [00:23] hrm. I'd expect bootstrapping to work. :) [00:23] 2013-10-29 00:23:15 ERROR juju supercommand.go:282 Get sftp://kyle@192.168.1.15//var/lib/juju/storage/tools/releases/juju-1.16.0-precise-amd64.tgz: unsupported protocol scheme "sftp" -- mmm [00:24] and based on that, it was "fixed" 15 or so days back === hloeung is now known as Guest93605 === Guest93605 is now known as hloeung === hloeung is now known as Guest69967 === Guest69967 is now known as hloeung === CyberJacob|Away is now known as CyberJacob [08:32] not able to upgrade maas to 1.4? | http://askubuntu.com/q/367734 === racedo` is now known as racedo [10:14] Juju bootstrap fails for Windows Azure | http://askubuntu.com/q/367778 === freeflying is now known as freeflying_away === gary_poster is now known as gary_poster|away [12:24] hi guys, where can I find some documentation about peer relations? [12:25] a search on juju.ubuntu.com isn't helping much [12:26] ah, this has something: https://juju.ubuntu.com/docs/authors-charm-metadata.html === gary_poster|away is now known as gary_poster [12:29] ahasenack: and mysql I know has one if that helps with an example http://bazaar.launchpad.net/~charmers/charms/precise/mysql/trunk/view/head:/metadata.yaml [12:30] rick_h_: ah, thanks === freeflying_away is now known as freeflying [13:52] ahasenack: I saw your email, I don't think a peer relation is what you want. [13:52] ahasenack: Are you trying to share db relations between units? [13:54] marcoceppi: no, I need a way for the /1 unit to get the db password that the /0 unit set [13:54] marcoceppi: it would be like wordpress, except we used the db admin credentials to create another user, unprivileged, that the app will use [13:55] marcoceppi: and we don't relate via just db, because we need the admin user for certain tasks [13:55] ahasenack: Okay, so /0 gets db-admin creds, then creates an unpriviledged user that it and other units will use? [13:55] marcoceppi: right [13:56] ahasenack: cool, then peer is def what you'll want [13:56] marcoceppi: thanks :) [13:57] ahasenack: just don't make any unit number assumptions. If you deploy with --num-units 3 and unit/1 comes up first it should do the creation/sharing. In other words becareful with idempotency and leader election [13:57] marcoceppi: sure [13:57] marcoceppi: I'm wrapping my head around that now, considering those scenarios [13:57] ahasenack: cool [14:00] marcoceppi: maybe I'll decide it will be easier to get an extension on the db-admin relation to create additional users, but I want to explore this peer relation first [14:00] ahasenack: please don't change the definition of the db-admin relation [14:01] what I meant with "get an extension" is to start a discussion [14:01] I'm still recovering from our sprint conversations about the http releation [14:01] ahasenack: whew, okay [14:01] not just put up innocent-looking MPs that change it :) [14:02] ahasenack: I'm working on a charm helper to assist with sane peer election, as a few of my charms require it [14:04] marcoceppi: cool === freeflying is now known as freeflying_away === zz_paulczar is now known as paulczar [16:25] marcoceppi: are peer relations established automatically, or do I need to explicitly add-relation them? [16:25] I think the latter [16:25] ahasenack: automatically [16:25] oh, really [16:25] ok [16:25] marcoceppi: thanks === paulczar is now known as zz_paulczar === zz_paulczar is now known as paulczar === paulczar is now known as zz_paulczar === zz_paulczar is now known as paulczar === paulczar is now known as zz_paulczar === zz_paulczar is now known as paulczar === freeflyiz is now known as freeflying === stokachu_ is now known as stokachu [22:51] I'm wondering what UserData does in the control instance, I see a lot of commands, are they run right away? [22:52] olafura: I'm not sure what you mean [22:52] also though [22:52] heading to the gym now [22:52] feel free to leave questions [22:53] and if no one has answered, I'll look when I get back [22:53] cool, it's in the command RunInstance and UserData is the parameter it's when you bootstrap [23:08] I think I got my answer it runs a script on the instance and the tool is cloud-config === paulczar is now known as zz_paulczar [23:19] olafura: I believe that passes data to cloud-init [23:19] olafura: so that juju can get the machine provisioned at boot [23:21] marcoceppi: Thank you I'm very close to making GreenQloud working with the old python version of juju ( it's easier test things out in it ). I'm just talking with them now about providing the Ubuntu Cloud images which have the cloud-config [23:23] olafura: I don't mean to be a downer, but the python version is no longer used and has been deprecated. All efforts, updates, and merges should be going in to the new juju-core [23:24] marcoceppi: That's my intent but it's much easier finding out what they are doing differently with it then having to recompile the go version over and over [23:25] olafura: well, it's fast to recompile ;) but just wanted to make sure you knew about it ahead of time [23:25] olafura: do you work over at GreenQloud? [23:25] thumper: did you find out why that one guy was having issues with local provider and bootstrapping at the sprint? (ecryptfs/weird timeout issues)? [23:26] marcoceppi: no I'm just going to be using their services, I needed a cloud provider in Iceland and they are the only game in town [23:26] olafura: very cool, thanks for putting the work in to do so! [23:27] olafura: there's a #juju-dev room where the juju-core go developers hang out, if you have questions about moving your changes to golang you're free to ask here of course, but you might get a more targeted response in ther [23:27] jcastro arosales ^^ [23:30] marcoceppi: Thanks, I will probably try hanging out there. I'm will probably have to iron out some things, in python before I move to go. I got somethings working in go before I moved, mostly s3 based stuff. Are you still on Soup or have you moved to rest? [23:30] * marcoceppi is not a core developer, just a charmer [23:31] olafura: I have no idea [23:31] olafura: is greenqloud openstack? [23:32] Or did they make their own "compute" stuff? [23:32] marcoceppi: It's CloudStack but it's basically ec2 api, but with enough warts to cause a problem [23:32] olafura: gotchya [23:33] There are some CloudStack providers now so many I need a general class for them [23:34] olafura: writing a generic cloudstack provider would be great if you could generalize them enough === CyberJacob is now known as CyberJacob|Away [23:35] olafura, good to hear you are working on a provider [23:36] marcoceppi: The only problem with all of this is that everything get's compiled into one binary so I can't just provide an plugin [23:36] olafura, as marcoceppi said #juju-dev is a good resource [23:37] arosales: yes I opened I new tab with it. I will probably ask more detailed questions there [23:38] olafura: providers are "plugin"-ish, they're seperated in core by directories, but this is a provider we'd love to have merged in core. [23:39] olafura: when I do compilations of core, it takes less than a second (after I've fetched the dependencies once) so it shouldn't be too much more tedious to rev [23:40] marcoceppi I'm also new to Go so it's easier to get going, the old code also had a configurable option of the urls which helped [23:41] olafura: I believe a lot of those options were moved over, but I'd have to hunt through the code to confirm [23:41] marcoceppi: and there was an other developer that already gave up on testing it out in Go [23:42] marcoceppi: I will probably use a similar approach because I don't know all the url of the providers [23:43] olafura: well, best of luck! Please feel free to ping me/the room if you get stuck of have questions. We're happy to help out [23:43] maroceppi: thanks for the help, I'll probably get stuck on something else :) [23:47] roughly how much effort is it to create a new provider? the digitalocean api looks very easy, and i've heard good things about them.. https://www.digitalocean.com/api/ [23:51] sarnold: from my understanding, it's not too complicated, but thumper could probably answer level of difficulty. You just need to code how to launch instances, where to store user data, firewall stuff, and maybe a few other odd bits and bobs [23:53] marcoceppi: hrm. maybe digitalocean is too simplistic. :) [23:53] sarnold: I'm not a developer on Juju but what I've seen of the code it uses a storage like s3 to manage some of the things so you need something that replaces that. I'm working on some thing that is very close to e2 and s3 apis so I don't have to do as much work but it's probably a week or two of coding from scratch. I also don't see at first glance that they have a way to upload you own image which would probably be needed or talk [23:53] to them about storing the Ubuntu cloud images. [23:54] sarold: There are also no security groups, so I don't know about firewall configuration [23:54] sarold: ok they provide a way to do that with domains [23:55] olafura: oh I thought the domains were just DNS stuff.. [23:55] security groups [23:55] sarnold: yes I think your right [23:57] olafura: sarnold so, right now we need an object store to place stuff, I think they're working on a way to get around this for providers that don't have it. Also, firewalling isn't required, it'd just mean that your isntances are exposed by default. Not something we would want but I'm nto sure if it's a deal breaker. Again, not a core dev can't speak to that [23:59] marcoceppi,olafura, thanks :)