14:02:36 #startmeeting Sec Grp 09/11 14:02:36 Meeting started Wed Nov 9 14:02:36 2016 UTC. The chair is lhinds. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:02:36 The meeting name has been set to 'sec_grp_09_11' 14:02:37 Hi Ari 14:02:43 local time change here was the previous weekend 14:03:06 same in Stockholm 14:04:18 #info agenda: https://etherpad.opnfv.org/p/opnfv-sec-meetings 14:04:22 #topic agenda 14:04:42 I don't have much at all for this week, if anyone has a topic though, please add. 14:05:22 #topic anteater 14:06:05 I have not had time to work on this, but opnfv is now mirroed to github, so when I have some time I will contact aric to try and get this wired into CI somewhere 14:07:14 #topic security-scanning 14:07:33 same story again, been really busy with red hat stuff and not had much time. 14:07:54 in fact I needed to reduce the scope for Danube release by dropping fuel support. 14:08:15 so serverascode you can hold off on the debian ports of OpenSCAP 14:08:56 what is needed to be done with openscap? 14:09:08 to integrate with CI? 14:09:14 No one from fuel seems interested in working on the topic, and never had a response from them over my threat reports, so I don't see the value of including fuel support 14:09:54 openscap debian DEB packages Sona 14:10:17 ok, 14:10:45 or rather then 'I don't see the value', I don't see the community support there, and don't have the bandwidth to cover it myself anymore. 14:11:02 I see 14:11:35 so will keep Apex support going in functest, and code in some of the improvements they want to see. 14:11:46 ok 14:11:48 #topic AOB 14:12:18 I was also very busy but I have started to look at sec doc 14:12:41 so I was thinking if we should go bi-weekly with the meetings? 14:12:42 do you think we should start working with secdoc? 14:12:56 Sona: better to work upstream on security docs. 14:13:09 opnfv does not really grok security. 14:13:10 yes, it is better 14:13:26 I am code on openstack security docs, so I can review and +2 anything you do there. 14:13:35 s/code/core 14:13:49 good 14:13:57 we can have bi-weekly meeting. it is ok 14:14:23 sure, seems the attendance is not growing 14:14:26 cool, so amend your calenders and we can the next meeting will be on the 23/11 14:14:41 ok 14:14:44 ok 14:14:50 I think we are done now, nice and quick :) 14:15:06 thanks, cu 14:15:12 unless any other matters, do feel free to jump in 14:15:16 thanks bye 14:15:28 thanks all! 14:15:31 #endmeeting