18:01:42 #startmeeting OSSG 18:01:43 Meeting started Thu Feb 21 18:01:42 2013 UTC. The chair is hyakuhei. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:46 The meeting name has been set to 'ossg' 18:02:03 Good morning/afternoon/evening all 18:02:51 #info bdpayne might not be able to make it to this meeting - he sends his apologies 18:03:30 #topic Encryption 18:04:06 Right, so there's been a lot of discussion on-list regarding encryption, especially in regard to Cinder. Anyone care to comment / update? 18:04:25 Welcome guys :) 18:04:35 Topic is 'Encryption' atm. 18:04:46 there's been a lot of discussion on-list regarding encryption, especially in regard to Cinder. Anyone care to comment / update? 18:05:00 There is an email thread called "Volume Encryption" in dev mailing list 18:05:12 That one has been really active lately. 18:05:16 Yup, that's mainly what I'm referring to. 18:05:34 The thing that scares me is the lackluster discussion with regard to key management 18:05:38 We are talking about encryption problems with regards to clone and snapshot operations 18:05:59 There will be a discussion on key management at the April summit 18:06:00 Yeah, I know some of our Block Storage guys had some concerns there. 18:06:11 Tangentially related, I have submitted a talk for the summit on a key management work that Rack is doing currently 18:06:17 Pure fluke I noticed this meeting/topic - But Moniker (DNS service) would be interested in some sort of secure key storage too for DNSSEC signing keys etc 18:06:33 We plan to do a talk on disk encryption at the summit as well to talk about possible solutions for clones and snapshots 18:06:36 key management is needed in many areas 18:06:59 I think Malini also has a talk on key management 18:07:02 rellerreller: a dev discussion or a presentation (I forget the correct parlance) 18:07:24 A dev discussion 18:07:37 #idea Share the love, vote on the security topics for the Summit 18:07:56 #link http://summit.openstack.org/cfp/details/6 for the key manager dev discussion 18:08:16 mtesauro: which track did you register your talk? 18:08:20 is there voting on the dev discussions or just the user sessions? 18:08:25 Keystone, cinder, etc 18:08:26 rellerreller: great. I'm really concerned about key management, in my experience with systems like this the easiest way to circumvent/undermine is typically to go after the key management 18:08:42 here's the link to the talk 18:08:43 lglenden: voting is just for the summit presentations 18:09:01 [link] http://www.openstack.org/summit/portland-2013/vote-for-speakers/presentation/573 18:09:13 #link https://www.openstack.org/summit/portland-2013/vote-for-speakers/#538 for the OSSG talk 18:09:33 So I think we can agree to meet up and discuss this at the summit. 18:09:43 #topic Security Notes 18:09:50 #link http://www.openstack.org/summit/portland-2013/vote-for-speakers/presentation/573 18:10:28 I have an outstanding action to publish the LXC note, I've got agreement from the OpenStack guys on how they'd like it to be done so I'll action that this week 18:11:26 Does anyone else have ideas for security notes? I think we must all have a pocket full of 'configure it this way or its a security nightmare' thoughts - Security Notes are a way to document them for the rest of the community to use while we wait for the hardening guide. 18:13:01 Well, if there's something you think might be relevant I'm happy to talk about it. Similarly I'm happy to do the write-up and publishing of OSNs for anyone who has issues they think should be documented in this way. 18:13:35 Any comments/issues before we move on? 18:13:53 #action hyakuhei - publish the LXC note, begin work on the next ones. 18:14:21 #topic Hardening Guide 18:15:01 At the last summit there was a really strong call for something along these lines. I think everyone is keen to see it happen but of course, everyone is busy trying to fix OpenStack! 18:15:47 Just curious, why latex? I'd think a more simple markup like markdown or aciidoc would lower the contribution threashhold. 18:15:55 I'm going to get the outline turned into LaTeX this week. Happy to take any contributions and convert to tex if authors aren't comfortable withtex. 18:16:15 Academic Snobbiness ? 18:16:28 I've collected some feedback on the guide from my team, what is the best venue to discuss it? the mailing list? 18:16:30 I'm not against changing the format particularly. 18:16:57 That's great and all but if you want people to contribute, best to keep the stuff they have to know down to a minimum. 18:17:15 lglenden: perhaps use the team mailing list or if you'd prefer to just mail it to bryan or myself 18:17:17 I've done Tex/Latex and its great but lots of people don't really like it or want to learn 18:17:27 mtesauro: You're correct 18:17:38 hyakuhei: will do, I will start off with an email to you and Bryan 18:17:53 Also - The existing doc team, and infra tooling don't do latex :) 18:18:16 #action current authors bdpayne and hyakuhei to discuss the proposal to move the Hardening Guide to a different format that's more accessible 18:18:18 Ouch. So what's a good alternative? Whats the existing doc team using? 18:18:22 lglenden: thanks 18:18:47 We're already using a close approximation of MD for Security Notes. 18:18:48 mtesauro, the doc team uses DocBook and some Sphinx+RST thrown in 18:19:20 #idea email robert.clark@hp.com with your suggestions for the (possible) reformat 18:19:23 Interesting. I know you can go from asciidoc => DocBook. Not sure about markdown 18:20:07 I think there's a lot of value in following the way others are doing it. 18:20:15 mtesauro, BTW I'm not saying anything about weather a switch is necessary.. Just worth pinging anne gentile and the infra guys before introducing a new format :) 18:20:26 @hyakuhei: Totally agree on that point 18:20:36 Any concerns with doing the development of the docs inside of git? 18:21:02 #link https://github.com/openstack/openstack-manuals 18:21:11 Not really - if we pick a non-binary format, it gives us version, branches, etc 18:21:13 #action lglenden to email robert.clark@hp.com with some feedback on the hardening guide 18:21:25 yarp 18:21:33 Ok, any more comments on the HG ? 18:21:42 yes. 18:21:50 Go ahead :) 18:22:03 I have done a bit of work and will send a pull request tomorrow.. 18:22:23 and yes Tex is a problem for me..in terms of time and proper tools. 18:22:39 Fantastic! If we do a format change I'm happy to take on converting any existing content. 18:22:58 some "hardening" best practices coming out of the federal government will be added.. 18:23:18 that is all. :) 18:23:45 @noslzzp: If you're using Linux, look at Lyx - make Latex/Tex much nicer. 18:23:53 Fantastic - thanks for your contribution. 18:24:02 http://www.lyx.org/ 18:24:09 OSX over here. :) 18:24:13 Probably not worth investing much time in tooling this week, in case we do decide to change the format ;) 18:24:32 #topic AOB 18:24:45 mtesauro: How's the OWASP-OpenStack group coming? 18:25:15 I've got the Wiki page up, the mail list up and have ~6 queued requests to join I'm going to reply to today 18:25:40 Cool! Anything we can do to help, cross-linking etc just say. 18:25:56 Next steps is to see what interests the members have 18:26:15 Yes, I'm trying to have suggested work for people who join. 18:26:25 Any suggestions ideas are very welcome 18:26:56 OpenStack is pretty broad so I hate to leave it up to them if they are interested but not sure how to help 18:27:19 Yeah, well at least there's a lot to do ;) 18:27:30 Right, one last topic, somewhat out-of-order. 18:27:40 #topic Summit Meetup 18:29:52 I will be at the summit and am game for a meetup 18:31:44 bugger. 18:32:12 dropped out and came back I see 18:32:19 apparantly. 18:32:25 We're over time so I'll close this out. 18:32:33 #topic Summit Meetup 18:32:41 I'll send a mail around but we should meetup. Either at,before or after one of the main events. 18:32:46 Any votes/requests/demands on the back of a postcard. 18:32:51 Thank you to all of you for putting time into this group right at the start. It's going to become an important part of OpenStack, thanks to people putting in effort on day 1. 18:32:56 perfect. 18:33:00 #endmeeting 18:33:21 #endmeeting