17:00:19 <tmcpeak> #startmeeting security
17:00:20 <openstack> Meeting started Thu Jan  7 17:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is tmcpeak. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:22 <tmcpeak> #chair hyakuhei
17:00:23 <openstack> The meeting name has been set to 'security'
17:00:25 <openstack> Current chairs: hyakuhei tmcpeak
17:00:26 <hyakuhei> whaddup!
17:00:29 <tkelsey> o/
17:00:30 <tmcpeak> yo yo
17:00:35 <elmiko> heyo/
17:00:41 <hyakuhei> Happy 2016 security peoples!
17:00:45 <sicarie> o/
17:00:50 <hyakuhei> #link https://etherpad.openstack.org/p/security-20160107-agenda
17:00:51 <elmiko> \o/ likewise =)
17:01:08 <bknudson_> hi
17:01:23 <shelleea007> o/
17:01:35 <tmcpeak> allright, full house
17:01:35 <ccneill> o/ howdy, all
17:01:53 <hyakuhei> hey, I wonder if we'll have many people along?
17:02:08 <hyakuhei> First meeting of 2016, also the last meeting before the mid-cycle!
17:02:25 <michaelxin> hi
17:02:31 <hyakuhei> mhayden: Are you around at all?
17:02:31 <tmcpeak> woot
17:02:45 <mdong> o/
17:02:45 <hyakuhei> #topic MidCycle
17:02:48 <wayward710> hi
17:03:04 <hyakuhei> Lots of people here, how exciting!
17:03:15 <hyakuhei> #link https://etherpad.openstack.org/p/security-mitaka-midcycle
17:03:31 <hyakuhei> It would be very useful if people could update the list of interested folks
17:03:34 <hyakuhei> To say if they're coming
17:03:38 <hyakuhei> or if not
17:03:48 <elmiko> yea, i crossed my name off =(
17:03:51 <michaelxin> happy new yer
17:04:22 <hyakuhei> oh no elmiko  :(
17:04:31 <michaelxin> appreciate if people can update the page with their availability.
17:04:34 <michaelxin> what !
17:04:42 <michaelxin> elmiko: You are not coming :-(
17:04:42 <dg__> can you post the link again, i missed it
17:04:48 <hyakuhei> Outrageous - I'll be sending redhat an angry letter
17:04:50 <tmcpeak> https://etherpad.openstack.org/p/security-mitaka-midcycle
17:04:51 <elmiko> sadly, no
17:04:52 <hyakuhei> #link https://etherpad.openstack.org/p/security-mitaka-midcycle
17:04:57 <elmiko> hyakuhei: haha, thanks ;)
17:05:04 <tkelsey> elmiko: thats a shame :(
17:05:04 <dg__> ty
17:05:26 <michaelxin> this is unacceptable.
17:05:34 <hyakuhei> Completely.
17:05:39 <elmiko> lol, i'm gonna forward this irc log to me bosses
17:05:48 <ccneill> we demand elmiko!
17:05:51 <hyakuhei> +1
17:06:25 <hyakuhei> So all might not be lost, dg__ is going to try to participate remotely
17:06:36 <hyakuhei> and we were even talking about trying to lead a session remotely
17:06:40 <dg__> Im going to give it a try, be really good if we can do it remotely
17:06:43 <elmiko> interesting...
17:06:46 <hyakuhei> which is exciting
17:06:56 <hyakuhei> Any suggestions on how we can best achieve this would be appreciated.
17:06:57 <tkelsey> dg__: +1
17:07:12 <tmcpeak> Twitch
17:07:17 <elmiko> hahaha!
17:07:20 <tmcpeak> stream people doing work and open up for commentary ;)
17:07:23 <elmiko> yes, definitely yes
17:07:27 <ccneill> michaelxin: do our cameras work with Skype, I wonder?
17:07:28 <tkelsey> lol
17:07:42 <michaelxin> I do no think that room has VC
17:07:50 <greg_a> ccneill we can do a public link can't we?
17:07:54 <tmcpeak> "wow, it certainly appears that Rob's whiteboarding skills have skyrocketed since last time"
17:08:14 <hyakuhei> hehe
17:08:14 <ccneill> yeah we can do a hangout or something, it's just more whether they'll be able to hear us
17:08:24 <ccneill> laptop mics are notoriously bad for whiteboarding sessions
17:08:26 <michaelxin> If possible, we need the list of names of companies for folks
17:08:42 <greg_a> I though those rooms do have VC? They're the same ones g_swift used right?
17:08:44 <michaelxin> so that we can pre-register you all to save check in time.
17:08:45 <hyakuhei> Should we just throw them on the Eetherpad ?
17:08:55 <hyakuhei> welcome nkinder !
17:09:00 * nkinder sneaks in late :)
17:09:02 <michaelxin> greg_a: no
17:09:18 <tmcpeak> michaelxin: should we just throw on etherpad?
17:09:29 <hyakuhei> nkinder: elmiko can't come to the mid-cycle..... sort it out kthnxbye!
17:09:39 <michaelxin> tmcpeak: That will be great.
17:09:44 <tmcpeak> sweet
17:09:50 <elmiko> if only nkinder were my boss ;)
17:10:00 <tmcpeak> dammit Rob, didn't you take the training? it's "Hewlett Packard Enterprise"
17:10:05 <hyakuhei> well he's someones boss damnit!
17:10:14 <elmiko> lol, too true
17:10:17 <nkinder> Ade is going from my team at least
17:10:20 <hyakuhei> tmcpeak: So long as we don't call it HP Enterprise we're ok
17:10:20 <michaelxin> We need a more accurate number.
17:10:23 <hyakuhei> whoops
17:10:27 <wayward710> I saw that video about "Hewlett Packard Enterprise."  It was well-done.
17:10:35 <tmcpeak> :D
17:11:02 <ccneill> ok I'm gonna make a "confirmed" section to make this easier to read
17:11:08 <hyakuhei> It's going to be very interesting overlapping with Barbican
17:11:09 <tmcpeak> ccneill: ++
17:11:14 <hyakuhei> +1
17:11:36 <michaelxin> gee, we have 26
17:11:36 <hyakuhei> So the topic list is looking a little devoid of content
17:11:55 <hyakuhei> nkinder - you can't make it either?
17:11:56 <tmcpeak> michaelxin: at least half won't show up
17:12:26 <tmcpeak> although in this case we might do better, lot of Rackers :)
17:12:26 <nkinder> hyakuhei: nope. :( Have another trip coming up, and it's too much to do back to back
17:12:52 <michaelxin> ccneill: Thanks.
17:13:02 <hyakuhei> nkinder: That's a shame, it would have been good to have you but I understand what you're saying, first few months of the year always seem to be travel heavy.
17:13:28 <michaelxin> nkinder: we will miss you for sure.
17:13:32 <hyakuhei> So tkelsey, tmcpeak does one of you want to lead the bandit sprint/work? I filled in some fluff around it
17:13:45 <tmcpeak> I'm happy to do it
17:14:00 <tkelsey> hyamauchi: tmcpeak or I will :)
17:14:04 <hyakuhei> we've got three people interested in working on the security guide but sicarie can't make it which makes me wonder what we should do about that section
17:14:13 <tkelsey> I want to talk  about comfig stuff etc
17:14:19 <elmiko> ooph..
17:14:30 <hyakuhei> well tmcpeak or tkelsey can you add some meat around the bandit section on the agenda please?
17:14:37 <hyakuhei> michaelxin: ditto for Syntribos
17:14:37 <tkelsey> yup
17:14:43 <tmcpeak> cool
17:14:44 <michaelxin> hyakuhei: got it.
17:14:48 <hyakuhei> Cheers
17:14:56 <tmcpeak> yeah maybe we should punt the sec guide without any of the cores making it
17:14:58 <hyakuhei> I'll do the same for Outreach
17:14:59 <elmiko> hyakuhei: depending on how much work we want to do on the sec guide, we could try to organize a virtual sprint for next week?
17:15:05 <hyakuhei> dg__:  something for killick on there?
17:15:19 <redrobot> o/
17:15:21 <tmcpeak> heh I didn't see you had outreach
17:15:29 <tmcpeak> I'll paste the bit I had in evangelism there
17:15:32 * redrobot is running late today
17:15:43 <hyakuhei> elmiko: sicarie - that could work. On last review it was a little short on things like policy configurations, in fact that's _horribly_ documented everywhere for everything
17:16:01 <hyakuhei> Tried working out what afew things meant yesterday, burned a whole day dragging through code.
17:16:09 <elmiko> hyakuhei: we could use a nice guide on policy in general, +1
17:16:11 <sicarie> yep
17:16:31 <dg__> hyakuhei yeah I figured you could cover killick
17:16:33 <ccneill> dave-mccowan, sigmavirus24, KarthikB: wasn't sure if y'all were confirmed or not; copy yourself to the "confirmed" list on the etherpad when you get a chance if you are
17:16:33 <hyakuhei> That'd be an interesting thing to tackle, maybe a sprint on policy chapter/section
17:16:48 <michaelxin> we can continue updating these agenda
17:16:50 <sigmavirus24> ccneill: I'm definitely going to be there.
17:16:55 <ccneill> shweet
17:17:22 <elmiko> hyakuhei: right, if there are enough folks who want to work on it, we could definitely participate remotely on the content with respect to reviews and laying out the chapter/section
17:17:50 <hyakuhei> Everyone happy to follow a similar unconference style to the last few? I think it helps keeps things flexible and stops pigeon holing
17:17:59 <tmcpeak> yeah, I like the way it's been going
17:18:07 <michaelxin> unconference is fine.
17:18:13 <hyakuhei> ok good, makes it easy to changs things if it's going wrong too I guess :P
17:18:17 <michaelxin> What should we do with Baribican
17:18:20 <michaelxin> ?
17:18:21 <redrobot> unconference?  like propose topics first day, schedule them out for the rest of the day?
17:18:29 <redrobot> michaelxin hyakuhei I'm here to talk about that :)
17:18:32 <KarthikB> I'm coming, I'll update the etherpad
17:18:41 <michaelxin> Should we plan some sessions with Barbican team together?
17:18:45 <hyakuhei> redrobot: yeah, we'll have topics on the etherpad
17:18:59 <michaelxin> redrobot: +1
17:19:03 <tmcpeak> looks like we have pretty good turnout
17:19:06 <hyakuhei> and we normally split up into two-three groups and work on a topic each for half the day
17:19:07 <tmcpeak> what's the food situation?
17:19:27 <redrobot> I like that idea... maybe I'll try that with the Barbican folks for our side of the midcycle
17:19:28 <michaelxin> tmcpeak: what do you want?
17:19:37 <tmcpeak> michaelxin: are you guys ordering?
17:19:53 <michaelxin> tmcpeak: Yes
17:19:53 <redrobot> this is our etherpad btw
17:19:54 <redrobot> #link https://etherpad.openstack.org/p/barbican-mitaka-midcycle
17:19:59 <tmcpeak> michaelxin: awesome! thank you
17:20:02 <michaelxin> Here is our plan.
17:20:12 <michaelxin> We will order breakfast, lunch for every day.
17:20:29 <michaelxin> We will have dinner and happy hour on Tuesday night.
17:20:30 <hyakuhei> michaelxin: HEROS!
17:20:43 <tmcpeak> sweet! our RAX overlords are good
17:20:47 <elmiko> hehe
17:20:57 <ccneill> remember, we're in breakfast taco country too ;)
17:20:57 <michaelxin> hyakuhei: How about HP sponsoring one night?
17:21:01 <hyakuhei> I'll try to get some funmoney too, either to throw in on Tuesday or do something another night
17:21:04 <hyakuhei> ^
17:21:05 <hyakuhei> Should be fine
17:21:06 <dg__> sweet! Can you guys set up a hangout for happyhour too?
17:21:08 <tmcpeak> ccneill: awwwyeahhh
17:21:13 <hyakuhei> Haha yes
17:21:24 <michaelxin> dg__: we will send you pictures.
17:21:24 <elmiko> breakfast taco... /mind-blown
17:21:26 <tmcpeak> dg__: :P
17:21:30 <dg__> :D
17:21:58 <ccneill> elmiko: see what you're missing out on?!
17:21:58 <michaelxin> you guys need to check in first.
17:22:02 <ccneill> :D
17:22:09 <elmiko> ccneill: inorite
17:22:18 <michaelxin> We will have rackers in the front to greet you and lead you to the room.
17:22:31 <tmcpeak> lol
17:22:33 <michaelxin> elmiko: you still have time. :-)
17:22:43 <michaelxin> elmiko: talk with you boss again. :-)
17:22:57 <hyakuhei> Sounds like a dealbreaker to me...
17:23:17 <elmiko> michaelxin: i told him about the threats of angry letters ;)
17:23:24 <redrobot> btw, if anyone is coming early to spend Monday with Barbican, please sign up on our Eventbrite so we can plan for food accordingly.
17:23:27 <hyakuhei> It would be nice to make sure we integrate with the Barbican lot
17:23:34 <hyakuhei> redrobot: tkelsey and I will be there early
17:23:51 <tkelsey> redrobot: yuo
17:23:58 <tkelsey> redrobot: *yup
17:24:09 <redrobot> tkelsey hyakuhei https://www.eventbrite.com/e/openstack-barbican-mitaka-midcycle-tickets-19784674494
17:24:12 <tkelsey> ty
17:24:18 <tmcpeak> redrobot: I'll be there first thing Tuesday as well
17:24:39 <hyakuhei> So I hope to drop into a number of barbican sessions
17:25:04 <ccneill> would probably be good if we could get a few barbican reps when discussing bandit gate jobs too
17:25:13 <tmcpeak> I've got some Bandit stuff to chat about also at some point\
17:25:14 <redrobot> hyakuhei ok... I'm liking this unconference idea more and more... that way we can have a schedule for people who are hopping between the two
17:25:21 <tkelsey> ccneill: +1
17:25:22 <ccneill> lessons learned, sticking points, tips for easing adoption, whatever
17:25:27 <hyakuhei> Yeah, we normally just throw it all into etherpad
17:25:42 <hyakuhei> So in the morning we take 5-15 minutes to talk about the day before and what group will work on what
17:25:45 <michaelxin> redrobot: Thanks.
17:25:54 <hyakuhei> That all goes on the etherpad, rinse-repeat after lunch
17:26:04 <tkelsey> ccneill: I have put some words in the pad about Bandit, please chip in with your input :)
17:26:19 <hyakuhei> It'd be really great to get some Barbican people dropping in
17:26:24 <redrobot> we usually do etherpad as well, but we just go down the list...  I think actually assigning time slots would work well for crosspollination
17:26:32 <ccneill> tkelsey: sure thing
17:26:41 <rm_work> LBaaS is at the same time, I don't know if we'll need security crossover but we'll also be doing barbican crossover some :P
17:26:45 <redrobot> I'll try to stick around for Thursday & Friday with you guys.
17:26:48 * rm_work hides
17:27:04 <hyakuhei> likewise if anyone is staying for the extra days (Thursday/Friday) let us know on the etherpad
17:27:18 <hyakuhei> rm_work: Excellent!
17:27:34 <rm_work> (LBaaS midcycle is Tuesday-Friday)
17:27:57 <hyakuhei> tmcpeak: tkelsey Maybe, as there are LBaaS and Barbican people around, a workshop session on writing Bandit tests would be useful
17:28:09 <hyakuhei> Gotcha's, clever stuff, debugging, filters etc
17:28:13 <tkelsey> hyakuhei: can do
17:28:15 <tmcpeak> sure, that sounds like a great idea
17:28:18 <hyakuhei> As a separate thing to the development sessions
17:28:37 <tmcpeak> it's a lot easier to just see it face-to-face than try to figure it out from docs
17:28:43 <hyakuhei> So it gets scheduled separately
17:28:46 <hyakuhei> Yeah totally
17:29:19 <michaelxin> good iea
17:29:22 <michaelxin> idea
17:29:32 <ccneill> tmcpeak: and we can use that new knowledge to write better docs :)
17:29:55 <tmcpeak> yeah, docs are one thing I'd really like to get better.  We've got feedback that it's tough to learn how to use in some cases
17:29:59 <michaelxin> ccneill: +1
17:30:08 <hyakuhei> Excellent.
17:30:27 <hyakuhei> I was hoping mhayden would be around so we could add some content around the ansible-security topic
17:30:43 <tmcpeak> yeah, I'd love to spend a session or two playing with that stuff
17:30:49 <tmcpeak> it looks like he is coming
17:31:35 <hyakuhei> Yeah, I think he works in the castle
17:31:40 <hyakuhei> Also, is it really a castle. I hope so
17:31:52 <tmcpeak> I was thinking the same thing
17:32:09 <elmiko> +1
17:32:20 <tmcpeak> if there is a place where you might actually get a castle it's Texas
17:32:41 <redrobot> hyakuhei used to be a mall  :-O
17:32:41 <ccneill> haha well, we need some ramparts and a moat
17:32:45 <ccneill> but it's at least as big as a castle
17:33:10 <bknudson_> https://www.google.com/maps/place/Rackspace+Hosting/@29.5083528,-98.3939156,3a,75y,43.2h,90.98t/data=!3m8!1e1!3m6!1sZeaJCgozmlHTIpjXs0IBBA!2e0!3e2!6s%2F%2Fgeo0.ggpht.com%2Fcbk%3Fpanoid%3DZeaJCgozmlHTIpjXs0IBBA%26output%3Dthumbnail%26cb_client%3Dsearch.TACTILE.gps%26thumb%3D2%26w%3D129%26h%3D106%26yaw%3D70.909088%26pitch%3D0!7i13312!8i6656!4m5!1m2!2m1!1srackspace+san+antonio!3m1!1s0x865cf358fc55c7c3:0xdfd632e8e5ff24a2
17:33:14 <michaelxin> hyakuhei: Major is coming.
17:33:21 <michaelxin> I already contacted him
17:33:30 <hyakuhei> excellent
17:33:37 <tmcpeak> looks kind of castl-y
17:34:02 <hyakuhei> pfft. Americans think they know what castles look like
17:34:09 <hyakuhei> *cough* disneyland
17:34:14 <dg__> hah ^this
17:34:19 <bknudson_> the closest things we have to castles are shopping malls
17:34:23 <browne> we do.  they look like White Castle
17:34:28 <tkelsey> hyakuhei: lol
17:34:28 <elmiko> lol
17:34:29 <michaelxin> please check the https://etherpad.openstack.org/p/security-mitaka-midcycle. We will add some useful information like direction, contact number, etc.
17:34:46 <wayward710> Yeah, I guess McMansions aren't exactly castles. :)
17:35:13 <hyakuhei> #link https://www.youtube.com/watch?v=OV2PbKpsMRk <- where the history comes from. (For after the meeting, obvs)
17:35:17 <ccneill> problem is, castles usually don't have escalators
17:35:23 <ccneill> Americans are too fat to climb castle walls
17:35:30 <ccneill> (myself included)
17:35:31 <hyakuhei> ouch.
17:35:32 <tmcpeak> lool
17:35:32 <wayward710> guilty
17:35:37 <mhayden> hyakuhei: sorry, just got back from a mtg
17:35:43 <elmiko> ccneill: haha
17:36:02 <tmcpeak> the Texas BBQ isn't going to help with the fat either
17:36:18 <tkelsey> mmmmm BBQ :D
17:36:19 <hyakuhei> hey mhayden - so we were just discussing the midcycle
17:36:20 <tmcpeak> I'm going to have to arrange a wheelbarrow to the airport
17:36:33 <hyakuhei> I notice that the ansible security work is down as a topic
17:36:37 <mhayden> hyakuhei: woot, yes
17:37:08 <hyakuhei> Could you add one-two sentances to the topic? So people know what they're signing up for please?
17:38:01 <mhayden> hyakuhei: absolutely -- could you link me where i need to add the verbiage?
17:38:20 <michaelxin> https://etherpad.openstack.org/p/security-mitaka-midcycle
17:38:25 <hyakuhei> #link https://etherpad.openstack.org/p/security-mitaka-midcycle
17:38:33 <hyakuhei> tsk, michaelxin you're too fast man
17:38:49 <michaelxin> The power of the castle
17:38:50 <hyakuhei> So my big bossman says we'll pay for a night out / beerage / something
17:38:54 <mhayden> i think michaelxin is overclocked :)
17:38:58 <hyakuhei> hah
17:39:04 <tmcpeak> hyakuhei: awesome!
17:39:07 <michaelxin> hyakuhei: +1
17:39:13 <michaelxin> great
17:39:43 <ccneill> this is gonna be a barn burner, y'all! ;)
17:39:48 <tmcpeak> hyakuhei: mind if I discuss some new Bandit stuff?
17:39:58 <hyakuhei> 'course
17:40:00 <hyakuhei> #topic Bandit
17:40:24 <tmcpeak> ok so I did some work before Christmas to figure out the best way to get projects to use bandit-baseline as part of a voting gate
17:40:35 <mhayden> should we be planning to make a few slides on our topic? or just discussion + dive into the code?
17:40:49 <tmcpeak> initially I was thinking we'd just have it as a template job projects could use, but the problem is that requires all the overhead of spinning up an entire new machine in CI
17:40:50 * mhayden is a general midcycle noob ;)
17:41:05 <michaelxin> mhayden: slides help
17:41:06 <tmcpeak> the infra folks and I came up with a solution that we'd have a new target
17:41:10 <tmcpeak> 'python-jobs-linters'
17:41:26 <tmcpeak> that does the exact same as 'python-jobs' except it calls 'linters' tox target instead of 'pep8'
17:41:36 <tmcpeak> and then you can add Bandit and whatever other linters you might have in the linters section
17:41:51 <tmcpeak> so basically bandit-baseline will now be run as part of your regular python-jobs voting check
17:42:01 <tmcpeak> we've already done this for Bandit itself and I threw up some directions
17:42:12 <tmcpeak> this should make it really easy for new projects to adopt Bandit gates
17:42:18 <hyakuhei> mhayden: yeah a couple of informal slides if it's the first time something has been covered at a midcycle or is generally new/shiny.
17:42:21 <browne> so would multiple linters appear as that single job?
17:42:32 <tmcpeak> browne: yes
17:42:45 <tmcpeak> that was a concern of mine as well, but in the end it's fairly easy to find which is which in the log
17:42:46 <mhayden> michaelxin / hyakuhei: got it
17:43:06 <browne> so now when 1 fails you need to dig in order to figure out which one?
17:43:07 <tmcpeak> also we advise making a separate target so you can still run tox -e codesec
17:43:09 <tmcpeak> and tox -e pep8
17:43:20 <tmcpeak> browne: yeah, but you have to dig in to find out why anyway
17:43:36 <tmcpeak> if my pep8 fails I have to dig through the log to see why anyway, right?
17:43:51 <browne> i guess before it was at least clear which linter failed.  i liked the separation
17:44:36 <tmcpeak> browne: I would have preferred it that way too, but to spin up a separate machine in infra just to run Bandit checks seems excessive and they assured me there weren't many better ways
17:44:43 <tmcpeak> s/many/any
17:44:45 <bknudson_> was there a reason infra wanted that? does it use less hardware?
17:44:57 <browne> tmcpeak: ok
17:44:58 <bknudson_> I also liked the separation.
17:45:01 <hyakuhei> tmcpeak: Containers?
17:45:25 <tmcpeak> bknudson_: yeah, it uses less hardware.  They have to spin up a separate machine for each new job.  There is no way to run jobs serially on the same hardware, they're all designed to run in parallel
17:45:30 <bknudson_> I thought it reused already-booted machines.
17:45:39 <hyakuhei> My NY resolution is to containerize all the things.
17:45:44 <tmcpeak> bknudson_: hmm, that's not what they told me
17:45:50 <tmcpeak> hyakuhei: yeah, containers would be much better
17:46:02 <tmcpeak> no reason why you couldn't drop the current code and Bandit in a container
17:46:14 <tmcpeak> I don't think infra is set up that way though ;)
17:46:24 <bknudson_> one of the nice things about bandit vs pep8 is that it doesn't require installing all the service's test-requirements.
17:46:32 <hyakuhei> pfft, there must be a way to sideload docker without them noticing.
17:46:36 * hyakuhei should stop "helping"
17:46:59 <browne> tmcpeak: how does the voting vs. non-voting linters work now?  i assume they are always voting
17:47:05 <tmcpeak> bknudson_: agreed, we've been using Bandit this way for a couple of weeks now though and in practice you don't notice it.  It's just run as part of normal 'python-jobs'
17:47:34 <tmcpeak> browne: yeah, always voting.  The idea is that you set a profile or filters that you're willing to abide by and then you're using a differential run so not getting old issues dragged up
17:48:35 <tmcpeak> I'm definitely open to other ways of doing this though
17:48:57 <tmcpeak> in the end I couldn't justify having to spin up a whole new instance just for a separate output report from Bandit though
17:49:25 <tmcpeak> also other projects don't have to do it this way, they're still free to set up whatever they want, it's just what I got going to lead the way
17:49:48 <browne> to me if its a hardward issue, then rearrange how hardware is scheduled.  rather than change the usability to the end user.  but i can understand
17:50:24 <tmcpeak> browne: yeah, that sounds reasonable to me too.  Maybe we can chew this over at the midcycle more, your and bknudson_'s concerns occurred to me as well
17:50:30 <tmcpeak> it's kind of the compromise I struck with infra
17:50:41 <bknudson_> it's best to keep infra happy
17:50:45 <ccneill> question: would it be worth it to folks to have a separate machine
17:50:51 <ccneill> if they were running BOTH bandit and syntribos?
17:50:54 <ccneill> i.e. a "security" job?
17:51:08 <tmcpeak> then we have bundled reports for Syntribos and Bandit ;)
17:51:20 <elmiko> that's an interesting thought
17:52:07 <ccneill> at least then you're getting your money's worth for the machine
17:52:17 <ccneill> and you could do the same thing tmcpeak was talking about with tox I assume
17:53:01 <ccneill> interchangeable logs/finding format wouldn't be such a bad thing either :)
17:53:13 <tmcpeak> fwiw projects that really want a separate tox target for bandit baseline can do it, and I'm sure infra will approve.  I just don't think the wanted me making a template to do it
17:53:25 <ccneill> ah
17:53:25 <tmcpeak> ccneill: true
17:53:45 <tmcpeak> that's all I had for Bandit, we can probably discuss more at midcycle
17:54:13 <hyakuhei> excellent
17:54:17 <hyakuhei> Anything else people?
17:54:49 <hyakuhei> ok then thanks everyone!
17:54:50 <hyakuhei> #endmeeting