08:31:16 <rbbratta> #startmeeting yardstick work meeting
08:31:16 <collabot> Meeting started Mon Aug  7 08:31:16 2017 UTC.  The chair is rbbratta. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:31:16 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:31:16 <collabot> The meeting name has been set to 'yardstick_work_meeting'
08:31:24 <rbbratta> #topic roll call
08:31:29 <Mingjiang> #info Rex
08:31:37 <JingLu> #info JingLu
08:31:43 <JackChan> #info Jack
08:31:48 <rbbratta> #info Ross
08:32:05 <rbbratta> #topic action item follow up
08:32:36 <rbbratta> #action rbbratta add LOG.debug to dump Heat template  still need to do this
08:33:45 <rbbratta> #info AP JackChan replace ping 0.2 library due to GPL license issue
08:33:55 <rbbratta> did we replace ping library?
08:34:10 <JackChan> Currently no.
08:34:39 <JackChan> I plan to do it later.
08:35:14 <rbbratta> JackChan: please do it now, it should not have been merged in the first place.
08:35:38 <JackChan> OK, got it.
08:36:02 <rbbratta> #action rbbratta figure out how to tag Jira tasks for testcases  still need to do this
08:36:03 <JackChan> I will upload a patch tomorrow then.
08:36:12 <rbbratta> JackChan: okay, thank you
08:36:47 <rbbratta> any other action item follow up before we talk about Danube 3.2
08:36:56 <JackChan> -:)
08:37:05 <Mingjiang> may be we need to update requirements.txt about license at the line end
08:37:20 <rbbratta> Mingjiang: good idea
08:38:05 <Mingjiang> just like functest https://git.opnfv.org/functest/tree/requirements.txt
08:38:12 <rbbratta> no linking to GPLv2 or GPLv3, we can only link to LGPL
08:38:55 <rbbratta> any volunteers to add licnese info to requirements.txt?
08:39:36 <rbbratta> #action rbbratta add license info to requirements.txt
08:39:56 <rbbratta> #topic Danube 3.2
08:40:52 <rbbratta> #info David McBride suggested we update the documentation, tag repo as danube.3.2
08:41:15 <rbbratta> #info David is out on vacation, have to follow up with Ray Paik this week.
08:41:39 <JackChan> so we should modify in stable/danube and then tag danube.3.2?
08:41:45 <kubi002> #info Kubi
08:41:47 <rbbratta> so sounds like we can merge the fix to stable/danube and prepare to tag once we here back from Ray
08:42:35 <JingLu> Release note should also be updated.
08:42:47 <rbbratta> JingLu: yes that too
08:43:18 <rbbratta> we can do that tomorrow
08:43:58 <kubi002> sounds good
08:44:29 <rbbratta> any other questions on Danube 3.2?
08:45:06 <rbbratta> the yardstick.conf issue doesn't affect Dovetail or Bottlenecks does it?
08:45:32 <rbbratta> they can stay on danube.3.1?
08:46:02 <JingLu> so we do not need to remove 3.1 docker image after 3.2 is built, right?
08:46:25 <kubi002> yes, Dovetail could workaround it
08:46:41 <kubi002> they stay on danube.3.1
08:47:31 <rbbratta> okay, and they are aware of the issue already?
08:47:59 <Mingjiang> can docker image danube.3.1 removed if we move to 3.2?
08:48:25 <JingLu> rbbratta yes, they are aware of it.
08:50:05 <Kanglin> #info Kanglin
08:50:22 <rbbratta> we can't remove danube.3.1 image unless Dovetail changes, right?
08:51:22 <kubi002> yes
08:51:36 <Mingjiang> yes, i think dovetail need to update to 3.2 then we can remove it
08:51:49 <Ace__> #info Ace
08:53:45 <rbbratta> okay, so we release 3.2 soon, dovetail updates, then we remove 3.1 at some point.
08:54:07 <kubi002> +1
08:54:36 <JingLu> agree
08:54:50 <JackChan> +1
08:54:58 <Mingjiang> +1
08:55:14 <rbbratta> #agree release danube.3.2 docker image, dovetail updates, then we remove danube.3.1 docker image
08:55:32 <rbbratta> next topic
08:55:46 <rbbratta> #topic Euphrates MS5 feature freeze August 11th
08:56:53 <rbbratta> NSB update patche just needs one or two more unittest fixes and rebase then it should be ready
08:57:13 <kubi002> good news
08:57:56 <rbbratta> it is being functionally tested here, so it is working
08:58:13 <Mingjiang> great
08:59:34 <rbbratta> some of the NSB tests will require neutron provider networks aka external networks.
08:59:40 <Ace__> rbbratta: hello. we have talked about the compass4nfv provider network last week.
08:59:51 <rbbratta> yes I was just going to mention
09:00:14 <Ace__> Yep, I have asked the compass4nfv team
09:01:10 <Ace__> If you create a JIRA about this requirments. They will add this function to master code.
09:02:47 <rbbratta> #action rbbratta add Jira for provider networks topology for compass4nfv
09:03:12 <Ace__> and you could use the master compass code to create several provider network by changing config file.
09:03:35 <rbbratta> I talked with Apex team they provide an external network by default.  external network/provider network are the same thing it looks like.
09:04:08 <rbbratta> anything else on MS5 or MS6 or the rest of the schedule?
09:05:14 <rbbratta> the new schedule puts MS11 on October 6th
09:05:50 <rbbratta> The next Plugfest will be at Intel in Oregon on December 4th.
09:07:19 <rbbratta> #topic AoB
09:08:52 <Ace__> maybe you could use the default provider network to do the test.
09:09:17 <Ace__> If you use the Apex.
09:10:14 <rbbratta> Ace__: yes that might be possible, might have to do a little neutron config to share the network
09:10:41 <rbbratta> we added the provider and segmentation ID code to heat context already
09:11:51 <rbbratta> JingC Zhang did that I think.  anyway needs testing at some point
09:12:11 <rbbratta> okay, is there anything else?
09:12:37 <Ace__> JingC, I think the patch use default tenant network.
09:12:55 <Ace__> maybe you can't use the code directly.
09:13:11 <Ace__> you need to create a provider network as a tenant network.
09:14:02 <Ace__> so yardstick should use the network you created transform it into heat template.
09:15:17 <rbbratta> yes I think we have to use pre-defined network in heat template
09:15:28 <Ace__> ok.
09:17:27 <rbbratta> okay, anything else?  I think meeting is finished
09:17:56 <rbbratta> #endmeeting