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