=== CyberJacob is now known as CyberJacob|Away [01:28] wallyworld: around? I just replied to the bug, and I'm still up if IRC is easier to resolve everything. [01:29] wallyworld: thank you for your help, BTW. [01:29] rbasak: hey, let me read the bug real quick [01:30] Oh, it hasn't even appeared in Launchpad yet (I replied by email) [01:30] ah [01:30] I'll forward you a copy [01:30] kk [01:30] Done [01:32] rbasak: i added a LICENSE file to gomaaspi as requeted in the original bug, but as you say, you can't see that easily [01:32] wallyworld: ah, OK. Sorry. [01:32] rbasak: so on that basis, think we're ok. i can get a tarball to you [01:33] wallyworld: thanks! [01:33] but that will be tomorrow as i have to update the dependencies file and let the CI server do its thing [01:33] I wonder what the easiest route is to get an upload sorted with licensing fixed, but I can resolve that with sinzui. [01:33] rbasak: np, thank you for being patient with me :-) i no next to nothing about licensing [01:33] know [01:34] rbasak: 1.20.2 will be released real soon (next week) with the correct source with the licensing fixes etc [01:34] we need to get some other development done first though [01:34] wallyworld: ah, that'll be the easiest thing then. I'll just hold on - no harm in a few days wait I think. [01:35] rbasak: i can give you a tarball earlier though [01:35] just in case we need to make any other changes [01:35] wallyworld: no problem - I appreciate you jumping straight on it. [01:36] welcome. i'm really keen for this release not to be blocked [01:36] wallyworld: yeah - that's a good idea. I can work with the tarball - thanks. [01:36] sure, will keep you in the loop [01:36] wallyworld: getting closer to keeping the archive up-to-date much quicker with new releases. It'll be great to push this back to Trusty, too. [01:37] oh yes, given the juju/mongo issues that will be fixed in this release [01:37] wallyworld: I'd like to also get some process changes in place so that copyright/licensing can be verified earlier in the process, so by the time there's a release, me or James can upload without any further review at that stage. [01:38] Then there's less to hold an update up. [01:38] We can worry about that later, though. [01:38] rbasak: agreed, we (juju core leadership team) is onto that and will be putting processes in place to properly introduce new 3rd party dependencies [01:39] so all new dependencies are properly vetted and licensed up front [01:39] wallyworld: that's great - thanks. [01:39] wallyworld: technically the uploader (to the Ubuntu archive) is responsible for checking upstream licensing when uploading a new release. [01:39] wallyworld: that's more geared around random upstreams though - not when they're working closely together like this. [01:40] wallyworld: and we have to update the debian/copyright file which maps every single file to a list of copyright holders and licenses. [01:40] rbasak: yeah, at the level i'm taling about, it's where a dev will simple add a 3rd party bit of code to the juju core code base [01:40] wallyworld: what I'm thinking is that maybe this file can be updated much earlier in the process - basically by you guys at the time you update dependencies.tsv. [01:41] we will ensure at that point there's proper copyright assignment via the CLA etc and license file etc in place [01:41] oh ok [01:41] wallyworld: right, but for third party deps also. [01:41] (where we can't rely on CLA) [01:41] rbasak: can you email alexis with the details of what yu want and we can follow up from there? [01:42] wallyworld: sure [01:42] thanks, that will allow us to properly collaborate and work how how to move forward in the best way [01:42] To be clear, these are really just my musings on what we might be able to do to make everything go smoothly. [01:43] They aren't requirements or anything. [01:43] sure, understood. but good cnversations to have and if we can expend a little effort now to save pain down the line, that's good imo :-) [01:43] we can collectively agree on how to proceed [02:01] rbasak, Each time CI blesses a 1.20.x tarball we get to ask "why not release now" When wallyworld indicates all the fixed packages are imported we can start the release. [02:02] sinzui: there are other bug fixes to com first though [02:02] but i can update the 1.20 dependnecies file so intermediate tarballs get generated with the right source [02:03] wallyworld, sure, but I haven't done a release this week, and devel still has regression, so I think 1.20.2 will be released first [02:03] sinzui: i don't think we should release 1.20.2 until the current milestone bugs are all fixed, agree? [02:06] wallyworld, I am not strongly inclined to delay goodness. I would rather release often. Since devel gets a new regression every day, I am happy to release a 1.20.x each week [02:06] sinzui: but won't that just case churn for the packaging guys? [02:06] getting the backport into trusty [02:07] regardless, 1 bug we shouldn't release without fixing is bug 1307434 talking to mongo can fail with "TCP i/o timeout" [02:07] <_mup_> Bug #1307434: talking to mongo can fail with "TCP i/o timeout"

[02:08] that is the primary focus of the 1.20.2 release [02:08] wallyworld, good point. we need a good pace, every two weeks was fine for james last year. [02:08] that bug should be fixed friday or more likely early next week [02:09] wallyworld: back now [02:09] kids weren't that fussed on tinkerbell :-) [02:09] thumper: lol, ok, give me a minute [02:11] menn0: https://github.com/juju/juju/pull/321 [02:11] thumper: in call now [02:11] thumper: looking === scuttlemonkey is now known as scuttle|afk === thumper is now known as thumper-afk === thumper-afk is now known as thumper === thumper is now known as thumper-back-at- === thumper-back-at- is now known as thumper-af-ktill === thumper-af-ktill is now known as thumper-afk === vladk|offline is now known as vladk === cmagina_ is now known as cmagina === uru_ is now known as urulama === CyberJacob|Away is now known as CyberJacob === seelaman` is now known as seelaman [07:22] hi === bradm1 is now known as bradm === CyberJacob is now known as CyberJacob|Away [07:48] lazyPower: i confirm y the error in the juju status after the reboot of the Host Machine was linked to the firewall's status set on it. thanks a lot for your patience and support. see y soon bye g. [08:27] hi anyone knows how to change the distro of the series of each nodes from " juju status "? [08:31] which nodes have been already added in juju [08:37] hi [08:37] is -relation-departed hook is executed after remove unit from service? === wwitzel3_ is now known as wwitzel3 === Guest63023 is now known as wallyworld === BradCrittenden is now known as bac === rbasak_ is now known as rbasak [12:25] Hi all [12:26] i'm trying to deploy a wordpress sample using juju maas and lxc containers [12:26] i'm not connected to internet so I'm facing some challenges [12:27] when trying to deploy an lxc cotainer it cannot download the cloud-img rootfs from cloud-images.ubuntu.com [12:27] i have to make this available offline somehow, any pointers? === Ursinha is now known as Ursinha-afk [13:56] Hello..We have deployed OpenStack Icehouse using the Juju and Maas on Ubuntu 14.04 (Trusty). I am having issues with installing Ceph on it. Are there any reference documents for installing Ceph as a backend to Cinder [13:58] william_home: internal mirror? === Ursinha-afk is now known as Ursinha [14:13] I am using the cinder charm and am trying to work through a problem installing on a system with only a single disk. What's the right way to specify using a loopback file on trusty/icehouse? I am putting block-device: "/srv/cinder.data|750G" in a config file, and, once I SSH in, I can see that the file gets created, but the loopback device and volume group don't get created. [14:26] niemeyer: around? About src/launchpad.net/goyaml licensing. [14:27] niemeyer: which files are covered by which licenses? [14:27] rbasak: I will add a note to the LICENSE.libyaml file [14:27] niemeyer: thanks! [14:27] rbasak: The *c.go files were ported from the C files from libyaml [14:28] rbasak: and thus are still covered by its license [14:28] Ah - I see. [14:28] That makes sense [14:28] rbasak: Please note that lp.net/goyaml is stale [14:28] rbasak: The project currently lives at github.com/go-yaml/yaml [14:28] rbasak: and that's where the update will be made [14:28] niemeyer: OK. I guess I'll see it switch in the next 1.20 release tarball then? [14:29] rbasak: I don't really know, sorry.. I'm not involved in packaging juju [14:29] Or if not I can deal with that I guess. I don't think this change needs to be in the source tree, as long as I'm clear on how to update debian/copyright. [14:29] OK, no problem. [14:30] rbasak: I can tell you that right now: the following files are covered by LICENSE.libyaml: [14:30] *c.go? I can match against that. Even directly in debian/copyright :) [14:30] rbasak: emitterc.go, parserc.go, readerc.go, scannerc.go, writerc.go, yamlh.go, yamlprivateh.go [14:30] OK [14:31] rbasak: Oh, and apic.go [14:31] Right [14:31] I can run with that - thank you! [14:31] rbasak: No problem, let me know if I can help further [14:32] Hello..I have deployed OpenStack Icehouse using the Juju and Maas on Ubuntu 14.04 (Trusty). I am having issues with installing Ceph on it. Are there any reference documents for installing Ceph as a backend to Cinder [14:35] A new Juju charm in introdcuced for 14.04 called Cinder-Ceph but I did not find and reference documents (besides release notes) [14:35] rbasak: LICENSE.libyaml was updated with those notes [14:43] I asked this question yesterday but no one answered me.. so I raised it again. I'm looking for a way to distribute my public key to all juju nodes including containers. I tried to use juju authorized-keys add command but no luck. it says the key can not be added and invalid key when I issued the command "juju authorized-keys add key-file.pub". Am I doing anything wrong here? [14:45] pmatulis: yes, local mirror [14:49] niemeyer: thank you! [14:57] anyone here try juju + salt? [14:58] i just figured it out.. it turned out not add key file, intead add copy/pasted key [14:59] ziliu2020_: Where to paste the key? environment.yaml? [15:01] no use this command [15:02] juju authorized-keys add 'ssh-rsa AAAAA.......' [15:02] ziliu2020_: Ok great! Thanks. [15:02] it will update environment and then populate the keys to all juju nodes [15:04] william_home: so you shouldn't have a problem, no internet required === anthonyf` is now known as anthonyf [15:13] pmatulis: well define local mirror then :), i have a mirror off all precise /trusty packages [15:14] pmatulis: but how do i mirror the cloud-images and how do i define those? [15:15] my setup is running from trusty maas and juju install [15:20] william_home: Any idea about ceph deployment using Juju for Trusty/Icehouse? [15:24] Hello [15:26] when I try to deploy charm from local dir, that dir has to be named same as the charm. Is there a way to circumvent that? I'm doing: juju deploy local:precise/apache2-test1, and I get an error that there is no charm inside apache2-test1. But if I rename apache2-test1 to apache2, then I can deploy. === urulama_ is now known as urulama [15:27] MrkiMile: i'm prolly missing something but how else would juju know what charm you want to use if you don't tell it? [15:29] MrkiMile: You have to rename the "name" key in the metadata.yaml to match the directory [15:29] MrkiMile: it's best to simply creat a new tree, ~/charms/test1/precise/apache2 [15:29] and seperate them by JUJU_REPOSITORY than go renaming metadata.yaml [15:34] marcoceppi: So, there is no way to tell juju to use charm from the directory that's not named as the charm ? === vladk is now known as vladk|offline [16:20] I'm playing around with writing my own charm for an app we have [16:21] basically I'm just trying to install the package and start a process provided by the package [16:21] does juju deploy myapp run the start hook? [16:22] * elarson just realized where he might find the answer in the manual... [16:29] how are most folks using juju? do you create your own charm for your application? [16:33] elarson: you can use a charm for your application nature, like I do with drupal, and then a subordinated charm [16:35] yesterday having a juju workshop :) https://www.facebook.com/photo.php?fbid=826602450708048&set=a.590513300983632.1073741832.354420671259564&type=1&theater [16:36] sebas5384: that sounds like you deploy drupal as a charm and then apply your changes as a subordinate, which means it ends up in the same container? [16:36] elarson: yep [16:37] but thats not a complete solution [16:37] at this point i'm just looking for a good place to start ;) [16:38] thats a good place then [16:38] hehe === scuttle|` is now known as scuttlemonkey [17:37] sshuttle is really a bottleneck in the vagrant workflow [17:37] :( [17:38] just use iptables and you will notice a big diference === vladk|offline is now known as vladk === CyberJacob|Away is now known as CyberJacob [18:10] sebas5384, hey are you guys devving locally on your laptops and then pushing to a cloud? [18:10] yes! [18:11] hey so there's a guy in core leading a team to make local dev to cloud suck less [18:11] mind if I link you guys up over email? I'm sure you guys have a bunch of suggestions [18:11] yeahhh sure!!! we already have a lot of troubleshooting and feedback :) [18:11] also, if you think we should use iptables instead of sshuttle [18:12] write it up and we can put that in the docs instead? [18:12] yes or other proxy things like hipache for example [18:13] i'm doing an experiment with a proxy in the vbox [18:13] so you shouldn't be doing no more iptables thingis === roadmr is now known as roadmr_afk [18:14] other things like using a plugin for vagrant [18:14] vagrant install vagrant-nfs_guest [18:14] to mount the directory of the deployed project into the container [18:22] yeah [18:23] heh, devving [18:28] Anyone here have knowledge about the cinder charm? [18:29] ctlaugh: not yet :P === CyberJacob is now known as CyberJacob|Away === boci^ is now known as b0c1 === scuttlemonkey is now known as scuttle|afk [19:30] Anyone with information about correct ceph charm for OpenStack on 14.04? [19:34] I am confused between ceph and cinder-ceph charm and how they are different? === roadmr_afk is now known as roadmr === vladk is now known as vladk|offline === Ursinha is now known as Ursinha-afk