18:15:26 <edwarnicke> #startmeeting Armoury Weekly Meeting 18:15:26 <odl_meetbot> Meeting started Mon Sep 14 18:15:26 2015 UTC. The chair is edwarnicke. Information about MeetBot at http://ci.openstack.org/meetbot.html. 18:15:26 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:15:26 <odl_meetbot> The meeting name has been set to 'armoury_weekly_meeting' 18:15:40 <edwarnicke> #chair alagalah adetalhouet ariel_noy grmontpetit mmarsale subh trozet 18:15:40 <odl_meetbot> Current chairs: adetalhouet alagalah ariel_noy edwarnicke grmontpetit mmarsale subh trozet 18:15:50 <edwarnicke> #topic Rollcall 18:15:55 <edwarnicke> Please #info in :) 18:15:57 <edwarnicke> #info edwarnicke 18:16:01 <mmarsale> #info mmarsale 18:16:06 <adetalhouet> #info adetalhouet 18:16:11 <grmontpetit> @info grmontpetit 18:16:12 <ariel_noy> #info ariel_noy 18:16:19 <grmontpetit> #info grmontpetit 18:16:22 <subh> #info subh 18:16:22 <edwarnicke> grmontpetit: Could you #info instead of @info :) 18:16:31 <edwarnicke> alagalah: you here? 18:16:32 <alagalah> #info alagalah 18:16:38 <edwarnicke> Anyone else... 18:16:41 <edwarnicke> Going once... 18:16:43 <edwarnicke> Going twice... 18:16:44 <edwarnicke> Sold 18:16:45 <trozet> #info trozet 18:16:50 <edwarnicke> #topic Agenda Bashing 18:17:02 <edwarnicke> So... lets see what folks have for agenda items 18:17:12 <edwarnicke> I know I have: 18:17:17 <edwarnicke> a) Getting our M1 email out 18:17:27 <edwarnicke> b) Getting our M2 email in shape 18:17:47 <edwarnicke> I think mmarsale and ariel_noy may have some patches they had as action items from last week 18:17:57 <edwarnicke> Anyone else want to speak up with topics? 18:18:29 <adetalhouet> Maybe define our release plan? 18:18:36 <edwarnicke> adetalhouet: That is a good idea :) 18:18:40 <adetalhouet> this is part of M2 if I'm correct 18:18:48 <edwarnicke> Yes, but that makes it no less a good idea :) 18:18:55 <alagalah> edwarnicke, :) 18:19:45 <edwarnicke> OK... other agenda items/ 18:19:46 <edwarnicke> ? 18:19:57 <adetalhouet> talk about the design of the model for NF catalog (mmarsale's patch) 18:20:04 <edwarnicke> adetalhouet: :) 18:20:11 <adetalhouet> same for workload 18:20:12 <mmarsale> Just wanted to mention that todat Subhash has joined us ... he might be able to help us with the project as we move forward 18:20:20 <edwarnicke> mmarsale: That's awesome :) 18:20:28 <edwarnicke> Welcome subh :) 18:20:29 <subh> yes sure ! 18:20:31 <adetalhouet> mmarsale: cool, welcome subh 18:20:34 <subh> thanks ! 18:20:47 <edwarnicke> Shall we dive into the M1 email first? 18:21:01 <mmarsale> edwarnicke: sure 18:21:02 <adetalhouet> Sure 18:21:10 <edwarnicke> #topic M1 email 18:21:17 <edwarnicke> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#M1:_Joining_the_Release <- link to M1 email template 18:21:32 <edwarnicke> First question... what offset are we? 18:21:43 <mmarsale> edwarnicke: the latest possible :) 18:21:51 <adetalhouet> I think offset 2 is good 18:22:12 <edwarnicke> mmarsale: adetalhouet I think I agree with you both, alagalah ariel_noy grmontpetit etc opinions? 18:22:25 <adetalhouet> we don't really depends on anyone right now, but latter on then we could 18:22:37 <ariel_noy> late as possible. new project 18:22:48 <edwarnicke> Cool... so any objections to offset 2 then? 18:22:56 <adetalhouet> nope 18:22:57 <edwarnicke> #agreed Armoury will be offset 2 in Beryllium 18:22:58 <grmontpetit> nope 18:23:00 <ariel_noy> nope 18:23:36 <edwarnicke> Next up we need a PTL, contact, test contact, and documentation contact... 18:24:03 <adetalhouet> I'm willing to be the test contact :) 18:24:12 <mmarsale> edwarnicke: I volunteer as contact :) 18:24:25 <edwarnicke> mmarsale: adetalhouet Awesome :) 18:24:33 <edwarnicke> Who is willing to volunteer as doc contact? 18:25:03 <subh> I will take. 18:25:28 <edwarnicke> subh: Many thanks :) 18:25:37 <adetalhouet> I will help you with that if needed subh - but don't want to hold the doc contact hat :) 18:25:38 <edwarnicke> Anyone else want to contend for those posts, or are we ok with 18:25:42 <edwarnicke> mmarsale: contact 18:25:42 <subh> ok, I will try my best 18:25:45 <edwarnicke> adetalhouet: test contact 18:25:51 <edwarnicke> subh: test contact 18:25:52 <edwarnicke> ? 18:25:57 <adetalhouet> I can be test contact 18:26:03 <edwarnicke> sorry 18:26:08 <edwarnicke> subh: doc contact 18:26:08 <adetalhouet> I'll help subh for doc 18:26:12 <edwarnicke> adetalhouet: I mistyped before 18:26:17 <edwarnicke> adetalhouet: Many thanks :) 18:26:19 <adetalhouet> edwarnicke: ok good :) 18:26:22 <edwarnicke> So 18:26:25 <subh> :) 18:26:36 <edwarnicke> #agreed mmarsale will be Armoury contact for Beryllium 18:26:45 <edwarnicke> #agreed adetalhouet will be Armour test contact for Beryllium 18:26:59 <edwarnicke> #agreed subh will be Armoury doc contact for Beryllium 18:27:05 <edwarnicke> So... about PTLs :) 18:27:14 <edwarnicke> We need to hold an election among the committers for that 18:27:19 <edwarnicke> And usually that's done on the mailing lists 18:27:32 <edwarnicke> I'd like to be clear up front that I don't really want to be PTL of armoury :) 18:27:39 <grmontpetit> :) 18:27:39 <mmarsale> We should send a mail with nominee right ? 18:27:43 <edwarnicke> mmarsale: Yes 18:27:53 <alagalah> edwarnicke, I say we break from convention and nominate someone in absentia 18:28:00 <edwarnicke> So who's willing to take the #action to send that email to the armoury-dev list? 18:28:07 <alagalah> I can send it 18:28:07 <mmarsale> I can do that 18:28:11 <alagalah> mmarsale, you got it 18:28:11 <edwarnicke> alagalah: Do you have someone particular in mind ? ;) 18:28:20 <mmarsale> ok taking an action item 18:28:26 <alagalah> edwarnicke, Someone other than me :D 18:28:34 <edwarnicke> #action mmarsale to send email for PTL election to armoury-dev 18:28:48 <alagalah> trozet, Should we make Sam do it? Since he isn't here ? 18:29:01 <trozet> LOL 18:29:25 <alagalah> edwarnicke, In all seriousness though... 18:29:36 <alagalah> mmarsale, Do you know the rules for the whole PTL election thing ? 18:29:50 <alagalah> mmarsale, Its strictly self-nomination only. 18:30:06 <mmarsale> alagalah: oh is it ? ok :) 18:30:25 <alagalah> edwarnicke, give 1 week for nominations then a week for voting ? 18:30:37 <adetalhouet> alagalah: edwarnicke sounds good :) 18:30:38 <edwarnicke> alagalah: I don't strictly think that's a rule... but it is the local tradition for most projects ;) 18:30:42 <edwarnicke> alagalah: And probably a good idea :) 18:31:03 <edwarnicke> alagalah: Giving 1 week for nominations and then voting is probably also a good idea :) 18:31:17 * edwarnicke actually went looking for a best practice wiki page for this and didn't find one 18:31:56 <alagalah> edwarnicke, yes you are right, its not a rule, more a convention (as I said earlier but then trod all over) 18:32:04 <edwarnicke> Coo... so mmarsale you'll send out the email to get nominations going today then? 18:32:13 <alagalah> Project Leads. The project lead is a Committer selected by vote from the Committers in the project. If there is initially only one member of the project, then that member is automatically the project lead. It is possible, and in some cases desirable, for one person to take on roles of project lead, Committer, and Contributor. 18:32:18 * edwarnicke prefers good cultural conventions to rules most of the time :) 18:32:56 <mmarsale> edwarnicke: Ill send out the email, looking for nominations 18:33:10 <edwarnicke> mmarsale: Many thanks :) 18:33:47 <edwarnicke> Next up on the M1 email, we need a draft project release plan and a project main page 18:34:11 <edwarnicke> #link https://wiki.opendaylight.org/view/Armoury <- Armoury main page 18:34:27 <edwarnicke> #link https://wiki.opendaylight.org/view/Armoury/Beryllium_Release_Plan <- very very draft release plan 18:34:45 <edwarnicke> Do you guys mind if we punt the detailed discussion of the release plan to the M2 topic? 18:35:14 <adetalhouet> No, this is fine. M2 related 18:35:49 <edwarnicke> Cool... so I *think* that other than the PTL election, we have what we need to fill in the M1 template 18:36:16 <edwarnicke> Who would be willing to send the M1 email, with a pointer to mmarsale 's PTL election email to let them know we are in the process of electing a PTL? 18:36:45 <adetalhouet> I'll do it 18:37:23 <anipbu> *Excited* to get Armoury's M1 email :) 18:37:25 <adetalhouet> #action adetalhouet to send the M1 email 18:38:12 <edwarnicke> anipbu: Me too! :) 18:38:32 <edwarnicke> Anyone have anything else on the M1 email before we switch to the M2 email? 18:38:34 <alagalah> edwarnicke, Is there an email/doc somewhere with a feature wishlist ? 18:39:34 <edwarnicke> alagalah: https://wiki.opendaylight.org/view/Project_Proposals:Armoury#Description is the closest we have so far 18:41:08 <mmarsale> #info an email looking for a PTL already sent to the mailing list 18:41:25 * alagalah reading ... 18:41:34 <edwarnicke> alagalah: We also have some initial patches for the registry piece and the api piece from mmarsale and ariel_noy repectively I believe 18:42:29 <adetalhouet> https://git.opendaylight.org/gerrit/#/q/project:armoury 18:42:37 <edwarnicke> #topic M2 email 18:42:54 <edwarnicke> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#M2:_Final_Release_Plan <- M2 Email template 18:43:19 <alagalah> #link https://wiki.opendaylight.org/view/Project_Proposals:Armoury#Description Features starting point 18:43:32 <edwarnicke> #link https://lists.opendaylight.org/pipermail/release/2015-September/003668.html <- completely ludicrous (needs to be redone) M2 email I sent out 18:43:46 <alagalah> #info imho #1 is a given. 18:43:50 <edwarnicke> Shall we walk through the M2 email by the numbers ? 18:43:55 <alagalah> edwarnicke, sure 18:44:03 <alagalah> edwarnicke, But isn't the meat the list of things we will do ? 18:44:07 <alagalah> edwarnicke, but ok :) 18:44:40 <edwarnicke> alagalah: Yes... but lets get everybodies drink order first :) 18:44:51 <adetalhouet> :) 18:44:53 <edwarnicke> #link https://git.opendaylight.org/gerrit/#/q/project:armoury+status:merged <- merged patches, which also point to a bug :) 18:45:26 <edwarnicke> #link https://lists.opendaylight.org/pipermail/armoury-dev/2015-September/thread.html <- email traffic on list 18:45:46 <adetalhouet> #link https://bugs.opendaylight.org/show_bug.cgi?id=4274 <-- bug 18:45:57 <edwarnicke> adetalhouet: :) 18:46:03 <edwarnicke> #link https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/armoury/ <- nexus artifacts :) 18:46:21 <adetalhouet> #link https://sonar.opendaylight.org/dashboard/index/57038 <- sonar 18:46:27 <edwarnicke> #link http://sonar.opendaylight.org/dashboard/index/57038 <- sonar report 18:46:32 <adetalhouet> #undo 18:46:32 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1ab7e10> 18:46:39 <adetalhouet> sorry for that, I let you drive edwarnicke 18:47:07 <edwarnicke> adetalhouet: Nope.. its good :) 18:47:11 <edwarnicke> adetalhouet: I appreciate the help :) 18:47:19 <edwarnicke> #link https://git.opendaylight.org/gerrit/gitweb?p=armoury.git;a=blob;f=pom.xml;h=f0e8e44de31e323fc0bc71af75c21aab468c9dc3;hb=HEAD <- root pom :) 18:48:28 <edwarnicke> Actually... adetalhouet You want to take over driving through the M2 email template? I'd actually appreciate it if you did :) 18:49:23 <adetalhouet> edwarnicke: ok 18:49:30 <edwarnicke> adetalhouet: Go for it :) 18:49:47 <adetalhouet> #info Does your project have any special needs in CI Infrastructure? No 18:50:07 <edwarnicke> adetalhouet: Cool :) 18:50:11 <adetalhouet> #info Is your project release plan finalized? No 18:50:24 <alagalah> adetalhouet, Should we put a date ? 18:50:53 <adetalhouet> Yes, I was thinking about that. When could we come up with a finalize release plan? 18:51:14 <adetalhouet> I don't really know all it needs so I don't know how much time it involves 18:51:18 <edwarnicke> mmarsale: anipbu ariel_noy grmontpetit You guys have been quiet... thoughts? 18:51:29 <grmontpetit> edwarnicke all ok 18:51:31 <edwarnicke> adetalhouet: It kind of depends on how much you put into it 18:52:03 <edwarnicke> adetalhouet: Usually you want to identify the things you think you can do (and preferably put names to them, but that's not required) and see if you can peg them to milestones (also not required, but nice) 18:52:05 <adetalhouet> Ok let's say by 30 September ? 18:52:08 <ariel_noy> late as possible. 18:52:22 <edwarnicke> When is the M3 deadline for feature freeze? 18:52:28 <mmarsale> just a reminder 15.10 feature freeze 18:52:37 <alagalah> mmarsale, 10/15 ? 18:52:53 <edwarnicke> 2016-10-15 I presume (using a civilized date format ;) ) 18:52:56 <alagalah> mmarsale, (btw I think dd/mm/yy makes much more sense than mm/dd/yy) 18:52:56 <edwarnicke> Sorry 18:52:59 <edwarnicke> 2015-10-15 18:53:14 <adetalhouet> agree with alagalah 18:53:24 <alagalah> edwarnicke, yyyy-mm-dd > dd-mm-yy > mm/dd/yy 18:53:32 <adetalhouet> #undo 18:53:32 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1d32750> 18:53:49 <adetalhouet> #info Is your project release plan finalized? No, it will be done for 30-09-2015 18:54:04 <adetalhouet> are you guys agree on that 18:54:18 * edwarnicke #link https://en.wikipedia.org/wiki/ISO_8601 <- I've always liked ISO 8601 for date formats ;) 18:54:30 <adetalhouet> #undo 18:54:30 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1d32750> 18:54:33 <edwarnicke> adetalhouet: I think its fine for the email, but I'd like us to aim more aggressively internally 18:54:38 <alagalah> adetalhouet, I think we need to be more aggressive 18:54:43 <alagalah> edwarnicke, ack 18:54:49 <adetalhouet> #info Is your project release plan finalized? No, it will be done for 2015-09-30 18:55:03 <adetalhouet> ok so let's continue 18:55:07 <adetalhouet> All project dependencies (requests on other project's release plans) have been acknowledged and documented by upstream projects? 18:55:21 <adetalhouet> I don't think we have any dependency nor projects depending on us 18:55:36 <adetalhouet> #info All project dependencies (requests on other project's release plans) have been acknowledged and documented by upstream projects?: No 18:55:54 <adetalhouet> #info Were there any project-specific deliverables planned for this milestone? No 18:55:55 <edwarnicke> adetalhouet: I think we probably depend on yangtools, controller, mdsal, and netconf (for restconf) 18:56:20 <adetalhouet> edwarnicke: Oh sure, I never think about those as I think they should be there by default 18:56:23 <adetalhouet> #undo 18:56:23 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1d32290> 18:56:26 <adetalhouet> #undo 18:56:26 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1d32150> 18:56:35 <edwarnicke> adetalhouet: Yeah... everyone forgets them :) 18:56:40 <adetalhouet> #info All project dependencies (requests on other project's release plans) have been acknowledged and documented by upstream projects?: yangtools, controller, mdsal, and netconf 18:56:59 <adetalhouet> #info Were there any project-specific deliverables planned for this milestone? No 18:57:22 <alagalah> adetalhouet, well.... 18:57:32 <alagalah> adetalhouet, Actually before we get off "dependencies" 18:57:46 <anipbu> Just to clarify, these are dependancies on existing functionality. No dependency on new feature request or changes in other project's release plan, right? 18:57:59 <adetalhouet> anipbu: right 18:58:09 <alagalah> adetalhouet, So I assume the point of all this is for cataloging "NFs" or AKA SFs for the SFC project, yes? 18:58:55 <adetalhouet> alagalah: Yes, this seems correct. But SFC will depend on us, we don't depend on them 18:59:33 <ariel_noy> Who will do the addition in SFC to use us? 18:59:47 <alagalah> adetalhouet, Riiiighhhhht 18:59:54 <ariel_noy> In which release? 18:59:57 <alagalah> ariel_noy, bingo 19:00:09 <adetalhouet> alagalah: ariel_noy Ok I understand the point now 19:01:32 <adetalhouet> Do you guys think during Be timeframe Armoury will be fully functional and ready to be used by other projects? 19:01:47 <edwarnicke> adetalhouet: I think we should try for it 19:01:53 <edwarnicke> adetalhouet: But we can do what we do 19:02:02 <mmarsale> adetalhouet: at least the catalog component should be 19:02:11 <adetalhouet> edwarnicke: I agree, but if it is not the case, SFC won't be able to use us 19:02:16 <edwarnicke> adetalhouet: Sure 19:02:39 <edwarnicke> I don't think SFC depends on us. I think we should talk to them though as we go forward as a prospective user :) 19:02:45 <adetalhouet> what I'm saying is, let's bring all the functionality, then we can talk about who will add it to SFC 19:02:52 <edwarnicke> adetalhouet: Damn straight :) 19:03:02 <edwarnicke> adetalhouet: However, we *should* talk to them as we go :) 19:03:17 <alagalah> edwarnicke, adetalhouet cool, thats all. 19:03:20 <edwarnicke> So we are at the top of the hour, adetalhouet do you have what you need to send an M2 email out? 19:04:12 <adetalhouet> Ok, so I guess I have to send the M2 email also :) 19:04:17 <edwarnicke> LOL 19:04:21 <adetalhouet> Note: I don't really want to be the PTL 19:04:24 <edwarnicke> You have figured out my evil plan :) 19:04:31 <adetalhouet> Yeah just did 19:04:42 * edwarnicke is not so good at hidden agendas... 19:05:06 <edwarnicke> Guys... can we close with #linking in the patches and asking folks to review them? 19:05:12 <adetalhouet> Ok so I think we're good for now 19:05:20 <alagalah> adetalhouet, but adetalhouet ... the first rule of PTL club is that you don't want to be PTL ... that's awesome... see, you are already supremely qualified. 19:05:40 <mmarsale> #link https://git.opendaylight.org/gerrit/#/c/26641/ 19:05:41 <adetalhouet> alagalah: huh... don't know what to say 19:05:43 <adetalhouet> :) 19:05:44 <mmarsale> plese review 19:05:46 * edwarnicke fought for sometime before relenting to be PTL of integration/distribution 19:06:08 <mmarsale> theats the first cut for the catalog component, its there to start the discussion and to define its scope 19:06:30 * alagalah gotta run... we done ? 19:06:42 <edwarnicke> I think so... 19:06:47 <adetalhouet> Yes we are 19:06:49 <edwarnicke> Any objection before we #endmeeting 19:06:52 <edwarnicke> #endmeeting