Wednesday, 2015-01-14

*** jraim has joined #openstack-security00:10
*** LinstatSDR has joined #openstack-security00:16
*** serverascode has joined #openstack-security00:36
*** LinstatSDR has quit IRC00:40
*** jraim has quit IRC00:54
*** tmcpeak has quit IRC00:56
*** tmcpeak has joined #openstack-security00:58
*** elo has quit IRC00:59
*** jraim has joined #openstack-security01:00
*** mohitsharma has joined #openstack-security01:01
*** bpokorny_ has joined #openstack-security01:01
*** bpokorny has quit IRC01:05
*** JAHoagie has quit IRC01:08
*** jraim has quit IRC01:13
*** jraim has joined #openstack-security01:19
*** tmcpeak has quit IRC01:20
*** nkinder has joined #openstack-security01:22
*** tmcpeak has joined #openstack-security01:26
*** bpokorny has joined #openstack-security01:31
*** tmcpeak has quit IRC01:32
*** bpokorn__ has joined #openstack-security01:32
*** bpokorny_ has quit IRC01:34
*** bpokorny has quit IRC01:35
*** salv-orlando has quit IRC01:41
*** bpokorn__ has quit IRC01:59
*** salv-orlando has joined #openstack-security02:00
*** amrith is now known as _amrith_02:02
*** salv-orlando has quit IRC02:19
*** LinstatSDR has joined #openstack-security02:21
*** tmcpeak has joined #openstack-security02:23
*** tmcpeak has quit IRC02:28
*** mgagne has quit IRC02:47
*** mgagne has joined #openstack-security03:04
*** mgagne is now known as Guest3302503:05
*** LinstatSDR has quit IRC03:11
*** mohitsharma has quit IRC03:13
*** jraim has quit IRC03:18
*** jraim has joined #openstack-security03:20
*** mohitsharma has joined #openstack-security03:20
*** opr has joined #openstack-security03:22
*** opr has quit IRC03:24
*** salv-orlando has joined #openstack-security03:43
*** jraim has quit IRC03:45
*** jraim has joined #openstack-security03:47
*** salv-orlando has quit IRC04:02
*** LinstatSDR has joined #openstack-security04:03
*** mohitsharma has quit IRC04:08
*** mohitsharma has joined #openstack-security04:10
*** mohitsharma has quit IRC04:11
*** mohitsharma has joined #openstack-security04:11
*** mohitsharma has quit IRC04:25
*** mohitsharma has joined #openstack-security04:25
*** mohitsharma has quit IRC04:26
*** Guest33025 has quit IRC04:32
*** mgagne has joined #openstack-security04:34
*** mgagne is now known as Guest5760504:35
*** salv-orlando has joined #openstack-security04:35
*** salv-orlando has quit IRC04:39
*** JAHoagie has joined #openstack-security04:43
*** mohitsharma has joined #openstack-security04:59
*** tmcpeak has joined #openstack-security05:03
*** tmcpeak has quit IRC05:05
*** vozcelik has joined #openstack-security05:32
*** subscope_ has joined #openstack-security05:52
*** mohitsharma has quit IRC06:09
*** LinstatSDR has quit IRC06:16
*** mohitsharma has joined #openstack-security06:18
*** salv-orlando has joined #openstack-security06:26
*** JAHoagie_ has joined #openstack-security06:42
*** JAHoagie has quit IRC06:43
*** JAHoagie_ is now known as JAHoagie06:43
*** subscope_ has quit IRC06:45
*** salv-orlando has quit IRC06:46
*** salv-orlando has joined #openstack-security06:51
*** salv-orlando has quit IRC06:52
*** serverascode has quit IRC07:12
*** serverascode has joined #openstack-security07:15
*** salv-orlando has joined #openstack-security07:38
*** salv-orlando has quit IRC07:39
*** vozcelik has quit IRC07:56
*** mohitsharma has quit IRC08:16
*** mohitsharma has joined #openstack-security08:19
*** nkinder has quit IRC08:25
*** Guest57605 has quit IRC08:31
*** mgagne has joined #openstack-security08:33
*** mgagne is now known as Guest553808:33
*** nkinder has joined #openstack-security08:37
*** salv-orlando has joined #openstack-security08:57
*** serverascode has quit IRC09:09
*** salv-orlando has quit IRC09:11
*** serverascode has joined #openstack-security09:12
*** mohitsharma has quit IRC09:22
*** jamielennox is now known as jamielennox|away09:31
*** mohitsharma has joined #openstack-security09:34
*** Guest5538 has quit IRC09:51
*** salv-orlando has joined #openstack-security09:51
*** mgagne has joined #openstack-security09:55
*** mgagne is now known as Guest8097909:55
*** mohitsharma has quit IRC10:04
*** _amrith_ is now known as amrith12:07
*** amrith is now known as _amrith_13:30
*** LinstatSDR has joined #openstack-security13:50
*** mvangund has joined #openstack-security14:07
*** tmcpeak has joined #openstack-security14:07
*** mvangund is now known as singlethink14:08
*** paulmo has joined #openstack-security14:12
*** nkinder has quit IRC14:20
*** _amrith_ is now known as amrith14:28
*** JAHoagie has quit IRC14:48
*** mohitsharma has joined #openstack-security14:48
*** mohitsharma has quit IRC15:06
*** voodookid has joined #openstack-security15:06
*** nkinder has joined #openstack-security15:10
*** amrith is now known as _amrith_15:41
*** _amrith_ is now known as amrith15:48
*** Guest80979 is now known as mgagne15:57
*** mgagne has joined #openstack-security15:57
*** amrith is now known as _amrith_16:07
*** vozcelik has joined #openstack-security16:24
*** Guest8210 is now known as redrobot16:54
*** bdpayne has joined #openstack-security17:10
*** tmcpeak has quit IRC17:11
*** tmcpeak has joined #openstack-security17:16
*** bknudson has quit IRC17:33
*** elo has joined #openstack-security18:10
*** _amrith_ is now known as amrith18:13
*** vozcelik has quit IRC18:35
*** bknudson has joined #openstack-security18:36
*** Kinokoio has joined #openstack-security18:41
*** bdpayne has quit IRC19:05
*** vozcelik has joined #openstack-security19:05
*** vozcelik has quit IRC19:07
*** elo has quit IRC19:20
*** elo has joined #openstack-security19:25
*** nkinder has quit IRC19:38
*** elo1 has joined #openstack-security20:03
*** elo has quit IRC20:06
*** elo1 has quit IRC20:17
*** elo has joined #openstack-security20:20
*** Kinokoio has quit IRC20:22
*** elo has quit IRC20:26
*** sicarie has joined #openstack-security20:52
*** amrith is now known as _amrith_20:59
*** bdpayne has joined #openstack-security21:00
* elmiko waves at bdpayne 21:00
bdpayneelmiko and sicarie Now still work for you guys?21:01
* sicarie tips hat21:01
elmikoworks for me =)21:01
bdpayneok cool21:01
bdpayneso... hi :-)21:01
bdpayneso perhaps we should start by chatting a little about what you guys are currently working on wrt the book21:01
bdpayneelmiko you want to start?21:02
elmikoi'm working on putting together a chapter for the book on the Data Processing service21:02
elmikois where i'm collecting ideas and some draft text21:02
elmikoi'm really hoping to get this in during the Kilo cycle21:03
*** elo has joined #openstack-security21:03
elmikoi also work on the sahara team, so i've got all that stuff going on too =)21:03
bdpaynekeeping busy is important :-)21:03
bdpayneelmiko, I know I gave you lots to think about in that etherpad... did it all make sense?21:04
elmikobdpayne: yes, it was a great help. i went back and tried to refine the intro text based on your comments.21:04
elmikoi'm a little worried about getting too detailed in the wrong places21:04
bdpayneit is a challenge21:05
bdpayneand a bit or an art21:05
elmikoi'm also meeting with some of the sahara team next week to discuss this at greater length21:05
bdpayneif you don't have enough detail, people's eyes glaze over21:05
elmikoain't that the truth lol21:05
bdpaynebut too much, and your writing it out of date next week21:05
bdpayneand you also lose readers in the "weeds"21:06
bdpaynewe have found that using running examples works pretty well in this book21:06
elmikoi do wonder what the default assumptions for our readers will be, as i'd like to not recover material they already understand21:06
bdpaynethat's a good question21:06
elmikore: examples, yea i'm trying to create opportunities for little examples sprinkled throughout21:07
bdpaynegenerally we are assuming cloud admin types that know openstack but that don't know much about securty21:07
elmikoyou had some questions about whether things were in the cloud or not, and i was a little confused about how in-depth i should get when describing something like the controller node21:07
bdpayneI'd suggest just calling out places where you are saying something that may be deployment specific21:08
elmikothat makes sense21:08
bdpaynebut those kinds of details are probably a good thing21:08
bdpayneok, great21:09
bdpayneso sicarie, could you share a little about what you're doing with the book these days?21:09
sicarieI started doing general editing and bug filing21:09
sicarieFigured that would get me familiar with the contents to be able to better look at the big picture later21:10
sicarieI'm reviewing the document conventions now as there are things that always bugged me that I'm not sure if they're 'allowed' or not21:10
sicarieor good style21:10
bdpayneon that point... we use the ibm style guide for a lot of those decisions21:10
sicarieFiled a few bugs, I think I'm up through ch4 now21:10
bdpayneI have a copy of that guide21:10
sicarieI'm looking at this:
elmikobdpayne: is it available online?21:11
bdpayneso if you guys ever have questions, just shoot them my way21:11
bdpayneyeah, that's a good resource as well21:11
*** elo has quit IRC21:11
bdpayneunfortuately not, the IBM style guide is purchase only21:11
bdpaynebut you can get it for kindle, for example21:11
elmikook, cool21:11
elmikomaybe we have one available internally21:11
bdpaynein general, the link about should be your first resource21:12
sicarieYeah, so I'm curious about uses of 2nd/3rd person21:12
sicarieLots of you and we21:12
bdpayneif it isn't answered in there, then check the IBM guide21:12
elmikosicarie: good question21:12
bdpayneI think that's ok21:12
bdpaynethe problem is that if you don't do that... then it gets hard to read21:12
bdpayneand starts to sound more like an academic paper21:13
elmikoi've been following the "we" pattern a bunch21:13
elmikoespecially as i try to write recommendations21:13
bdpaynewe recommend blah... ?21:13
bdpayneyeah, I think that's nice21:13
*** nkinder has joined #openstack-security21:14
elmikoi thought so too, and i agree it makes the doc easier to digest21:14
bdpayneok so thanks sicarie21:14
bdpayneso sicarie has been doing a pass on the existing book21:14
bdpayneand elmiko is working on adding a new chapter21:14
bdpayneso you guys are both bringing different background to the table21:15
bdpaynewhich is part of the reason that I thought it would be great to have you both involved21:15
bdpayneplease lean on your personal experiences there to help us make this better for all21:15
bdpayneI have a few thoughts on next steps for us21:15
bdpaynebut first wanted to see if you guys had any pressing ideas on what we need to be doing21:15
elmikoi think getting the terminology in-line with the official terms would be nice21:16
elmikoe.g. many uses of tenant21:16
bdpayneso we should probably file tickets for those items as we find them21:16
elmikoshould we file them by chapter or section?21:17
bdpayneif you don't know, you can easily file a ticket by clicking on the bug on the webpage version of the doc21:17
elmikoooh, that's nice21:17
bdpaynewhatever works... chapter, section, etc21:17
bdpaynestep 1 is to create the tickets for the work we need to do21:17
bdpaynestep 2 is to actually triage those tickets21:17
sicarieYeah, I've been doing them individually to allow for new contributors to come up and snag a simple commit21:18
paulmo3) Profit! :)21:18
bdpayneI'm thinking that we should use this meeting (in future weeks) to do some ticket triage21:18
elmikosicarie: +121:18
bdpaynewho is this paulmo guy? ;-)21:18
paulmoWhere is he!?!?21:18
elmikobdpayne: sounds good to me21:18
bdpayneyeah, small scoped tickets is nice21:18
bdpaynepeople do tend to pick them up21:19
bdpaynewhich is both great and surprising21:19
bdpayneso I think that (1) and (2) are really the bread and butter21:19
bdpayneperhaps we should get good at those first21:19
bdpayneand then we, in future weeks, we can explore creating larger milestones / tasks for the group21:20
elmikook, i can put some time aside to create some tickets this week. i'll probably focus on terminology to start with.21:20
bdpaynesounds great21:20
bdpayneanything else for today?21:21
elmikonothing from me21:21
bdpaynenext week we can pick up with ticket triage and see where that takes us21:21
sicarienothing from me either21:21
elmikosounds like a plan =)21:21
bdpayneok, so thanks to both of you for helping out with this21:21
sicarieThanks bdpayne!21:21
elmikoyea, thanks for organizing21:21
bdpaynego team!21:21
bdpaynenp, cya later21:21
elmikotake care21:21
*** bpokorny has joined #openstack-security21:22
elmikosicarie: side note21:22
elmikosicarie: i replied to a bug you picked up in barbican about the bit_length stuff21:22
sicarieOh, cool21:22
elmikoi started looking at it and found a bunch of stuff, so i tried to capture it in my reply21:22
elmikohopefully it'll help =)21:22
sicarievI was off trying to set up a barbican vm so I can actually test my fix21:23
sicariebefore submitting21:23
sicarieSo yeah, greatly appreciated elmiko21:23
elmikono prob, you beat me to the punch!21:23
sicarieSorry - I'd been trolling launchpad for a few months looking for a good 'starter' bug to get me moving21:24
elmikonah, no apologies necessary. i had been doing a little bit of the same =)21:25
*** elo has joined #openstack-security21:42
*** paulmo has quit IRC21:47
*** singlethink has quit IRC22:03
*** bknudson has quit IRC22:37
*** tmcpeak has quit IRC22:49
*** jamielennox|away is now known as jamielennox22:56
*** bknudson has joined #openstack-security23:03
*** sicarie has quit IRC23:26
*** voodookid has quit IRC23:49

Generated by 2.14.0 by Marius Gedminas - find it at!