magicaltrout | woop figured it out tvansteenburgh, after looking at a hadoop test I found out that because pgrep was coming from an external call, it was picking itself up recursively! Needed to grep it out! | 00:07 |
---|---|---|
magicaltrout | thanks for you help and advice today. | 00:07 |
tvansteenburgh | magicaltrout: ah, glad you figured it out. happy to help! | 00:07 |
arosales | tych0! :-) | 00:49 |
arosales | tych0: sorry missed you ping | 00:50 |
arosales | tych0: are you running the lastest beata or the alpha? | 00:51 |
cherylj | tych0: you can pass the enable-os-upgrade flag in the bootstrap command: `juju bootstrap <controller name> google --config enable-os-upgrade=false | 00:57 |
tych0 | arosales: np, from source so latest everything :) | 00:57 |
tych0 | cherylj: cool, thanks! | 00:57 |
cherylj | tych0: I'll be back around this evening (after I do bedtime for the kiddo) | 00:58 |
* arosales was just reading release notes | 00:58 | |
arosales | cherylj: thanks | 00:58 |
cherylj | tych0: You can check out a presentation I did for the STS folks if you get stuck on other bootstrappy things | 00:58 |
cherylj | tych0: https://docs.google.com/presentation/d/1XnKjnBpCYY44Bw9EMnvkY8tYfhPPl-0I__HibXhYWS0/edit#slide=id.p3 | 00:58 |
arosales | cherylj: will there be a way in juju 2.0 to keep these settings? | 00:58 |
cherylj | arosales: they should be applied to the model config after bootstrap | 00:59 |
cherylj | arosales: if you're seeing that they're not, I would think that's a bug | 00:59 |
tych0 | cherylj: ah, no worries. i actually have a branch coming up to make things a bit nicer for juju/lxd image handling | 00:59 |
cherylj | tych0: Look starting on slide 14 for the bootstrap help | 00:59 |
tych0 | cherylj: but i need something to be merged into lxd first, and everyone on my team is eating dinner :( | 00:59 |
tych0 | cherylj: cool, will check it out thanks | 00:59 |
arosales | cherylj: sorry I was saying will there be a file on the client local filesystem to keep these changes through controller destroys, or will it always have to be passed in via the command line? | 01:00 |
cherylj | arosales: you will always need to supply it, but you can pass in a file with config to bootstrap | 01:01 |
cherylj | like juju bootstrap foo aws --config=/path/to/my/config.yaml | 01:01 |
cherylj | arosales: that was one of my gripes, but now I have files for config for each type of cloud I bootstrap | 01:01 |
arosales | cherylj: ah interesting and that config.yaml will probably have conventions similar to env.yaml in 1.25? | 01:01 |
arosales | ya I don't like editing env.yaml file, but once I have it working I don't have to touch it | 01:02 |
cherylj | arosales: yeah, checkout slide 15 in that deck | 01:02 |
cherylj | I show the contents of my config file | 01:02 |
arosales | so setting up a cloud is tedious, but then I do like having my setting for each cloud env persist | 01:02 |
arosales | cherylj: ok thanks for the pointer | 01:02 |
arosales | cherylj: post 2.0 may be a usability point we gather feedback on, but for now doesn't seem like that big of a deal | 01:03 |
arosales | cherylj: thanks for the reply here | 01:03 |
arosales | cherylj: and have a good weekend | 01:03 |
cherylj | np! It took me a while to experiment enough to put that deck together. If it help people get started, then it's definitely worth it | 01:03 |
cherylj | you too! | 01:03 |
arosales | cherylj: one other reminder we should meld your slides with rick_h__ ones he did for the summit and then mail the list. Very helpful info | 01:04 |
cherylj | arosales: I'll be using that deck to generate a "Getting started" section in the release notes | 01:04 |
cherylj | once we release beta2 | 01:04 |
arosales | cherylj: very cool --thanks | 01:04 |
* cherylj disappears for a bit | 01:04 | |
arosales | I'll let you get to your kiddo :-) | 01:05 |
metsuke | will 16.04 be available for bootstrapping as soon as it comes out or will there be some lag time until you can use it in juju? | 02:14 |
cherylj | metsuke: you can use xenial now if you use daily streams. What cloud are you using for bootstrap? aws? local / lxd? maas? | 02:34 |
metsuke | cherylj: we wiped our deployment, but we plan on using a private cloud with maas, juju deploying openstack and lxd hypervisor | 02:38 |
cherylj | metsuke: if you change the boot images Sync URL to http://maas.ubuntu.com/images/ephemeral-v2/daily/, you'll see 16.04 as a option for your MAAS images | 02:39 |
cherylj | metsuke: but I guess you need them in glance for openstack | 02:40 |
cherylj | you'll specify a default-series: xenial in your environments.yaml for that environment (if you're using juju 1.25) | 02:40 |
metsuke | we want to use juju2...if we can get it to work, but if all we need to do is change that url then we should be set, thanks! | 02:41 |
cherylj | metsuke: there's a lot that's changed to bootstrap for juju2. Want some help getting it set up? | 02:41 |
metsuke | we were able to get it up and running and got to the login screen | 02:42 |
cherylj | oh great! | 02:42 |
metsuke | as soon as we entered the credentials, it just spun forever | 02:42 |
cherylj | oh hmm, not so great | 02:42 |
cherylj | are you talking about logging into the maas controller? or a juju bootstrap node? | 02:42 |
metsuke | unfortunately we were on a deadline so we didn't look into it too much, but since we re-wiped again, we will try juju 2 again | 02:42 |
metsuke | logging into the juju-gui charm | 02:43 |
cherylj | oooh | 02:43 |
cherylj | are you using 2.0-beta1? | 02:43 |
metsuke | yes, that was the one | 02:43 |
cherylj | there were some API changes that have made juju incompatible with the gui, but the gui team is working hard to get it fixed. I thought I saw that they were going to release the updated version soon | 02:44 |
cherylj | let me see if I can find that announcement | 02:44 |
metsuke | that would explain it then. We really like juju and we think it would fit perfectly with our organization. We just need to work out the kinks ;) | 02:45 |
rick_h__ | metsuke: there's a beta juju gui charm that works on 2.0 | 02:45 |
rick_h__ | metsuke: cs:~juju/trusty/juju-gui | 02:46 |
rick_h__ | cherylj: ^ | 02:46 |
cherylj | thanks, rick_h__ ! | 02:46 |
cherylj | I was trying to dig that up | 02:46 |
metsuke | do we need a different repo for that? | 02:47 |
rick_h__ | metsuke: cherylj see http://ubuntuonair.com | 02:47 |
rick_h__ | for a lot of yalking on the new stuff, etc from today | 02:47 |
metsuke | very cool | 02:48 |
rick_h__ | metsuke: no, it's just not on the short main namespace until it leaves beta (cs:juju-gui) | 02:48 |
rick_h__ | only on trusty/etc in beta | 02:48 |
rick_h__ | for the deployed charm | 02:49 |
nagyz | is there a sahara charm that works? :-) | 16:59 |
marcoceppi | nagyz: I don't think we have a sahara charm at this point in time. We do have apache hadoop charms and a whole suite of big data plugins | 18:43 |
nagyz | marcoceppi, thanks! | 20:11 |
Akarat | hey guys! | 21:42 |
Akarat | Anyone can answer why the install hook downloaded files are deleted? | 21:44 |
Akarat | someone? | 21:46 |
jose | what do you mean by deleted? they shouldn't be | 21:52 |
jose | unless specified, of course | 21:52 |
Akarat | downloaded files | 21:52 |
Akarat | they aren't in the home folder | 21:53 |
Akarat | '~' | 21:53 |
jose | no, they shouldn't be | 21:53 |
jose | everything runs on the charm folder, which is where it will be | 21:53 |
jose | unless you specify a download location | 21:53 |
Akarat | do you know where the charm folder is? | 21:54 |
Akarat | in the vm? | 21:54 |
Akarat | the bitnami stack is installed =) | 21:56 |
Akarat | nice | 21:56 |
metsuke | Are there any plans for an Openstack: Manila charm? Or is there something in Juju that can give the same functionality (shared directories between containers/instances)? | 23:35 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!