14:11:12 #startmeeting 2016-02-10 14:11:12 Meeting started Wed Feb 10 14:11:12 2016 UTC. The chair is aripie. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:11:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:11:12 The meeting name has been set to '2016_02_10' 14:14:20 back in business 14:14:57 hi Ari 14:15:23 I don'yt think Aric fixed the permissions issue for me 14:15:31 ok 14:15:40 I can't send patch for review 14:15:58 I send you by email 14:16:08 I seem to have the same problem 14:17:36 Aric hopefully will sort it out 14:18:01 so far perhaps we can send our patches by email & sync what we have been writing? 14:18:21 we can do that, yes 14:18:32 Can you please have a look at my patch and let me know what do you think 14:18:50 I just need to if I am on right direction :) 14:19:00 #agree until gerrit access sorted out, sync patches over email 14:19:11 Dows it make any sens what I have been written so far 14:19:42 I will also send my stuff for your comments 14:19:46 ok Son, I will do that 14:20:03 good, I will look at 14:20:23 yes, based on a quick look, your contribution looks fine 14:20:28 I have been digging into trusted computing 14:20:52 that is a pretty complex territory 14:21:07 yes :) 14:21:25 I learned that my chromebook uses TMP 14:21:34 I will a little better now :) 14:21:45 have you tried using it? 14:22:07 this feature is used by default 14:22:23 ... in addition to the default use 14:22:29 it is a nice featutre which I was not aware of 14:22:51 I assume you could store your secrets there (well, some of them at least) 14:23:41 I haven't used anything on chromebook but when I was booting a test image on hierofalcon I noticed that the trust boot id disabled 14:24:14 sounds positive 14:24:32 maybe because I wanted to use another OS so we needed to disable it 14:24:45 anyway I will continue with this 14:25:12 yes, keep going! 14:25:14 is there any deadline for updating ? 14:25:15 Any news from the release? 14:25:45 OK lets discuss agenda 14:25:52 #topic Agenda 14:26:05 #info Deadlines 14:26:12 #info Release 14:26:30 any other topics to discuss today 14:26:32 ? 14:26:48 not from me 14:27:12 ok, if something comes to mind we can take AOB 14:27:21 # topic Deadlines 14:27:43 we have not really fixed any target dates for the Guideline 14:28:24 we are still in learning mode, so maybe we just do best effort 14:28:29 ok, good 14:29:02 ok so there is no deadline for B-release 14:29:05 good 14:29:30 should we plan some internal timelines? 14:30:23 it would be good just to set internal goals 14:31:25 we have each different area, so we try to wite as much as we can 14:32:26 yes, it is easy to process in parallel 14:33:19 #agree With next OPNFV release in mind, define timelines for security guideline 14:34:07 so lets talk Release 14:34:14 #topic Release 14:34:39 regarding Brahmaputra, we do not have an official delivarable 14:37:04 had a network disconnect... hopefully stable now 14:37:40 I was disconnected, back again 14:37:48 ...I dont know what happened, same here 14:38:09 ... anyway, regarding Release, I suppose 14:38:30 we could target for some version of the guide to be released 14:38:37 within a month or so 14:38:53 it does not need to be in sync with the sw releases as this is 14:38:56 generic documentation 14:39:08 assuming that is ok with the project 14:39:53 that is right 14:40:01 #info discussion about the release not necessarily needing be in syunc with sw releases 14:40:22 #info as the security guideline is generic documentation 14:40:34 #info that is not specific to a release 14:41:18 #agree discuss with project if OK to release first version out-of-sync with project release 14:41:45 hello bryan_att 14:42:23 aripie: hi 14:42:31 welcome 14:42:39 Hi Bryan 14:43:04 hi all, just lurking 14:43:14 feel free! 14:43:46 Ari, is there any security related activity which OPNFV needs for this coming release? 14:43:47 anyone: more thoughts on release scheduling of opnfvsecguide? 14:44:51 scheduling of opnfvsecguide: let's just say untill next week we try to send some text for review (it doesn't need to be very advanced) 14:45:10 that sounds fine 14:45:11 just to get started 14:45:43 #agree send input for review per email until next week 14:45:50 The way I see it, the security guide will start as a general document and as OPNFV releases roll out, the guide will touch on various features introduced with new releases 14:46:22 pretty much like OpenStack equivalent 14:46:55 on any security related activity which OPNFV needs for this coming release; 14:47:08 Openstack has good documentation 14:47:13 I do not think there is anything specified for the coming release 14:47:38 ok good, I will continue to scan CVEs for OPNFV components 14:48:15 and I should get active on pushing to fill gaps in audit information generation 14:48:30 ... in all opnfv projects 14:48:44 yes that would be good :) 14:49:17 and I know Luke is looking into the CII Badges program 14:49:40 related to how and to what extent opnfv should self-assess 14:50:03 our secure design practices 14:50:26 so we have stuff going on, even though not very visible 14:50:28 to the rest of the community 14:51:47 ok, good discussion, AOB? 14:51:48 #topic AOB 14:53:12 I do not come up with more now 14:53:22 Nothing from me 14:53:54 OK, I will stay around for a while so if anything, let me know 14:53:57 but closing the meeting 14:54:03 #endmeeting