[00:10] smoser i've plugged into travis before, worked pretty good for my use-case [00:11] using it for https://github.com/yahoo/Zake [00:11] pretty easy to hookup https://github.com/yahoo/Zake/blob/master/.travis.yml into it [00:13] yeah we used it for github.com/rackerlabs/teeth-agent and github.com/rackerlabs/teeth-overlord before we moved to working on Ironic [00:26] smoser hmmmm, https://review.openstack.org/#/c/119909/ [00:26] hmmmm [00:27] alessandro why :( [00:28] Competetition is good for your heart [00:28] or was that exercise? [00:33] lol [00:33] JayF ya ya [00:33] heart, competietion... [00:33] sleep [00:33] lol [00:33] food [00:33] all good for something, ha === pquerna_ is now known as pquerna === praneshp_ is now known as praneshp [04:36] harlowja: I updated https://code.launchpad.net/~jason-oldos/cloud-init/upgrade-configdrive/+merge/232312 in response to your comments; I still have to fix the vendor_data handling to match what smoser wants but I' [04:36] *I'll do that first thing in the mornign [04:36] :) [04:36] cool [04:39] JayF how does smoser want to treat the vd? === harlowja is now known as harlowja_away === rcj` is now known as rcj [13:05] JayF, when you get a chance, could you point me at whatever dock you have of the json netork definition format? [13:05] the only thing i have is at https://review.openstack.org/#/c/85673/13/specs/juno/metadata-service-network-info.rst [13:17] https://gist.github.com/jayofdoom/b035067523defec7fb53 is all i have right now. [14:45] smoser: There's a blueprint up in Openstack Nova right now, but it's not approved and won't be until K so there is no "official" JSON network format... there's just basically what our automation emits [14:45] for better or worse :/ [14:46] All our devices follow a similar network config: two phys interfaces bonded, and vlans on top of the bonded interface [14:46] so I don't think we ever documented how it'd look for anything else [14:46] right. [14:46] thats fine [14:46] its 'v1' [14:47] yeah so tl;dr: no documentation :) [14:48] as I understand it, this is more or less a dump of the information neutron sends to nova [14:49] ok. [14:49] did pquerna sign cla ? [14:51] He has patches in already [14:51] so I believe so [14:51] I have to leave in a few minutes to get on a bus and head into the city for work :) [14:52] this is what I intend on working on today ... I want to get the vendor_data reading stuff in sans network json today [14:52] then all I'll have is that patch to get network json support in [14:52] seem reasonable? [14:57] JayF, yeah. [14:57] it does [14:57] i want to get this stuff in too [15:55] smoser: i've signed the cla previously [15:55] pquerna, thanks. [15:55] aren't you supposed to be being married right now? [15:55] I think he's supposed to be honeymooning right now [15:56] :) [15:58] i board a flight to FRA in a few hours [16:03] Nice. [16:03] You two have fun :) [17:10] can I use Travis on premises? [17:10] JayF: or is it payware if I want to use it for private projects? [17:12] on premises is $$$$$ [17:12] bigtime [17:12] they don't even publish the code iirc, because they basically say the magic is the infra [17:13] They seem to publish a lot of code: https://github.com/travis-ci/ [17:13] Including chef cookbooks for deploying... [17:13] That's apparently changed since I last looked then, nice :) [17:13] Although afaict using travis-ci without using github is a nonstarter [17:13] hmk [17:13] ah ok, well thats to bad then [17:14] heh, linked from wikipedia from a while back: https://github.com/travis-ci/travis-ci/blob/2ea7620f4be51a345632e355260b22511198ea64/README.textile#we-are-not-done-yet [17:14] it really is [17:14] I like the github workflow a lot better than any other tool I've used, but I really dislike the number of things that are becoming github only [17:14] yea well, I'm using svn and bzr realy [17:14] ndonegan_: that sounds like what I remember :) [17:15] Started using Gerrit internally at work. Can be annoying at time, but the workflow it enforces is handy. [17:15] ever heard of the OpenSuse buildservice? [17:15] Gerrit is what I use for Openstack, obviously [17:15] though tht might be restricted to purely building (rpm/deb) packages [17:15] never heard of it [17:16] gerrit is nice, yes [17:17] anyway, perhaps Jenkins is any good for building all sorts of things [17:18] Jenkins is what I've used [17:18] generally speaking managing build systems is terrible [17:18] why :) [17:18] which is why my knee-jerk was to suggest the hosted (travisci) service I've used before [17:18] heh [17:18] hhe [17:18] lazy :P [17:19] eh, I just come from an ops background and put a very high value on "just works" [17:19] ah ok [17:21] you know if jenkins can build rpm packages as well? [17:21] next to cloud-init, or even cirros [17:25] Of course :) [17:25] Jenkins is a fancy bash script runner [17:25] among a shitton of other things [17:25] hehe ok [17:25] * firing up a centos7 instance === harlowja_away is now known as harlowja [17:42] arg, when will the multi prefix stuff land in Neutron [17:42] I want dualstack :p [18:06] " yea well, I'm using svn and bzr realy" [18:06] harmw, youre not supposed to say thinhgs like that out loud :) [18:06] lol wut [18:07] I'm not allowed to use both? :P [18:07] right jenkins can do just about anything [18:07] its really just script runner. [18:07] and really that is all travis-ci is too [18:07] probably, yea [18:08] don't you have some c-i stuff to merge or something? :P [18:08] cirros doesn't seem like it would fit on travis-ci because somewhere i saw a "50 minute time limit" [18:08] isn't it fair use? [18:08] ? [18:08] i think its perfectly valid for them to do that. [18:09] I thought the plans had fair use on a number of opensource stuff [18:09] oh ofcourse [18:09] but cirros will take longer than that to build [18:09] right [18:09] well, if jenkins can build cirros [18:09] my experience is it takes ~30 seconds per arch. [18:10] the goal i would have would be to have a jenkins that luanched slaves on ec2 or digital ocean [18:10] or somewhere [18:10] and then built the things there [18:10] sucked in the results [18:10] and then published the output somewhere [18:10] yea [18:10] wicked :) [18:13] wtf, jenkins comes with svn support and.... cvs [18:13] like, wtf [18:13] time to look into the plugin repository :p [18:14] ah and it wants me to add bash stuff, per step [18:14] yeah lots of plugins [18:14] You can put a whole bash script in any of the steps [18:14] yea I'm just looking at that [18:14] nice [18:15] if it's prefixed with a #!/bin/bash it'll be run with bash, otherwise it runs as /bin/sh [18:15] travis-ci is basically the same. [18:15] lets you run arbitrary commands [18:16] so you could probably abuse their build service by putting *something* on github [18:16] and pushing to it every time you needed it to build. and then that something pull from somewhere else inside the build system. [18:16] hehe [18:35] harmw: We have Jenkins building RPMs, Gems, the hated omnibus pacakges, and even full blown image for use in OpenStakc. [18:36] cool [19:04] well that was easy, having Jenkins do a bzr checkout [19:09] smoser: do we have a build script for cirros that I can have Jenkins call? [19:11] harmw, ./bin/build-release [19:11] mostly does it. [19:12] ok, lets take a look [19:12] read doc/create-release.txt [19:12] hat is honestly all i do to create something [19:13] ok [19:14] if I make jenkins install stuff through either apt-get or yum, does that intrfere with the os itself or does jenkins use chroots? [19:14] jenkins doesn't by itself use chroots. [19:14] harmw: It depend on how you set it up. [19:14] you'd have to have something that would do that. [19:15] oh. maybe ndonegan_ knows more. maybe there is explicit support for that. [19:15] I'm seeing a plugin that does something with regards to chroot [19:15] my goal would be to allow me to build anybody's branch [19:15] without security concerns [19:15] ndonegan_: please enlighten me :) [19:15] For example, I tend to use venv for certain Python projects. For using apt, you'll probably need to look at chroot. [19:15] which would mean doing it in a throw away VM or instance on a cloud [19:16] smoser: thats a cool idea as well [19:16] just one system that runs the Jenkins master and have that interact with a cloudsystem to spawn additonal worker vm's [19:17] harmw: The image building I mentioned is using oz, which just starts up local VMs using libvirtd. [19:17] (instead of what I'm currenly after, which is doing it all in just 1 vm) [19:17] ah, that can be roughly compared to using some decent cloud then :) [19:18] Also, it's spectacularly easy to tell jenkins to use alternative build hosts for certain builds. [19:18] It's just an ssh account and key, and it sorts the rest itself. [19:18] well that is very nice [19:19] However, when it comes down to it, all it's doing is running a few scripts for you. [19:19] https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Havemasterlaunchslaveagentviassh [19:19] So, if you want to do something like use a chroot, you have to script it the same as if you were doing it on your own shell. [19:20] great, well thanks :) [22:07] smoser i just learned how much heat is doing with cloud-init, lol [22:07] scary :-P [22:08] btw, since i know all u guys care [22:08] https://etherpad.openstack.org/p/TaskFlow-0.4 (new release)