08:30:46 <rbbratta> #startmeeting yardstick work meeting
08:30:46 <collabot`> Meeting started Mon Jul 10 08:30:46 2017 UTC.  The chair is rbbratta. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:30:46 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:30:46 <collabot`> The meeting name has been set to 'yardstick_work_meeting'
08:30:54 <rbbratta> #topic roll call
08:31:10 <abhijitsinha> info Abhijit
08:31:10 <rbbratta> #info Ross
08:31:12 <Mingjiang> #info Rex
08:31:12 <deepaks> #info deepak
08:31:13 <Jing_> #info Jing Lu
08:31:19 <kubi001> #info kubi
08:31:34 <JackChan> #info Jack
08:31:47 <Kanglin> #info Kanglin
08:31:53 <rbbratta> #topic action item follow up
08:31:55 <abhijitsinha> #info Abhijit
08:32:47 <rbbratta> #info AP1 Danube 3.0 tag can't be delete, have to move to Danube 3.1
08:33:31 <rbbratta> #info AP2 https://gerrit.opnfv.org/gerrit/#/c/36507/  was merged, don't think we root causes Jenkins coverage problems
08:34:08 <rbbratta> any other action item follow ups?
08:34:45 <kubi001> rbbratta: I wonder how we will named our docker image for Danube 3.0
08:35:03 <rbbratta> danube3.1 I assume
08:35:31 <rbbratta> was there an email about that
08:35:34 <kubi001> rbbratta: that would be aligned with repo
08:36:18 <rbbratta> okay, found the email thread
08:36:47 <rbbratta> Jing_ already tagged yardstick docker 3.0
08:36:51 <kubi001> two solution for that
08:36:51 <kubi001> 1. repo 3.1  docker image 3.1
08:36:51 <kubi001> 2. repo 3.1 docker image 3.0
08:37:36 <rbbratta> do other projects expect danube 3.0,  dovetal, bottlenecks, etc?
08:37:56 <rbbratta> or do they just pull latest stable
08:39:04 <kubi001> dovetail pull danbue 3.0 for CVP.0.2.0
08:39:35 <kubi001> Bottlenecks pull the latest
08:40:39 <rbbratta> okay, so dovetail would have to be updated to pull danube 3.1, so we should just use danube 3.0
08:41:43 <kubi001> both would be Ok, they can easily to move to Danube 3.1 , It depends on what we like
08:42:17 <rbbratta> it would be more consistent and accurate to use danube 3.1
08:43:03 <kubi001> Dovetail team will tag new version for each weeks for beta version, eg.CVP.0.3.0 and CVP.0.4.0
08:43:51 <kubi001> that would not a big deal for them. we can just focus on the best way for us
08:44:00 <Jing_> 3.1 is fine as long as we make it clear in the release note
08:44:30 <rbbratta> okay, so we are agreed.  use danube 3.1 and notify dovetail team
08:45:17 <kubi001> OK
08:45:32 <rbbratta> and we have to fix the release notes
08:45:38 <kubi001> yep
08:45:50 <rbbratta> #agreed use danube3.1 for docker tag to make danube3.1 git tag
08:46:08 <Mingjiang> danube.3.1
08:46:47 <rbbratta> for docker, yes danube.3.1
08:47:11 <rbbratta> for git as well.
08:47:35 <rbbratta> #agree use danube.3.1 for git and docker tag
08:48:57 <rbbratta> there we some older action items about VES and moving the APAC timeslot
08:49:52 <kubi001> rbbratta: do you mean VES agent?
08:49:57 <kubi001> collectd
08:50:08 <rbbratta> kubi001: yes, VES agent for collectd
08:50:17 <kubi001> got it
08:50:27 <rbbratta> if we should adopt VES output format
08:50:56 <rbbratta> I'll add it again, and try to have something for next meeting
08:51:04 <rbbratta> #action Ross find out more details about VES agent and ask Bryan for slides
08:51:23 <kubi001> thanks
08:51:43 <rbbratta> I'm fine with the current APAC timeslot, I assume everyone else is okay with the current time.
08:52:39 <kubi001> deepaks: sure for me, how about deepaks?
08:54:25 <Mingjiang> ok for me
08:54:31 <Jing_> the time slot is  good.
08:54:37 <JackChan> ok for me.
08:54:39 <rbbratta> well if we moved it earlier it would effect Europe more, so I think the current time is okay.
08:55:03 <abhijitsinha> yes this time slot is ok
08:55:31 <rbbratta> okay, next topic
08:56:01 <rbbratta> #topic release branches and offline support
08:56:32 <rbbratta> I saw we are now cloning storperf in the Dockerfile
08:56:46 <Jing_> yes
08:56:46 <rbbratta> so we have to manage yardstick, releng, and storperf branches when cloning
08:57:29 <rbbratta> but releng hasn't implemented a stable branch yet, so we could run into the problem of releng master breaking again when Euphrates comes around
08:58:00 <rbbratta> we need to support a separate branch for each repo, so we can adjust in case other project breaks, or tags at a different time.
08:58:23 <Jing_> releng repo can be removed in E release
08:59:00 <rbbratta> okay, so they are moving fetch_os_creds?
08:59:23 <Jing_> as the fetch_os_creds.sh is preferred to run on Jump host
08:59:42 <Jing_> #link https://gerrit.opnfv.org/gerrit/#/c/37119/
09:00:13 <rbbratta> okay, so we just need a STORPERF_BRANCH variable
09:01:19 <JackChan> ok, it is also called in api, so I also need to remove it.
09:02:35 <rbbratta> we have https://jira.opnfv.org/browse/YARDSTICK-691 for Dockerfile changes
09:03:49 <rbbratta> but maybe we don't need YARDSTICK-691 is we always have good branches to clone.
09:04:27 <rbbratta> I'll add a comment to close once fetch_os_creds is removed
09:04:53 <rbbratta> And we can create a new Jira to add STORPERF_BRANCH to Jenkins job
09:07:08 <rbbratta> #info we will no longer run fetch_os_creds, it will run on jumphost, so we don't need to clone releng
09:07:23 <Jing_> agreed
09:09:02 <rbbratta> Jing_: can you create the Jira for STORPERF_BRANCH and assign it to yourself?
09:09:15 <Jing_> sure
09:09:28 <rbbratta> thanks
09:09:54 <rbbratta> okay, next topic
09:10:05 <JackChan> #link https://gerrit.opnfv.org/gerrit/#/c/36537/
09:10:27 <rbbratta> k8s support?
09:10:28 <JackChan> Hi, it is patch for kubernetes.
09:10:33 <JackChan> rbbratta: yes
09:10:43 <rbbratta> #topic kubernetes context
09:11:11 <JackChan> it is the first version. Please feel free to comment.
09:11:14 <rbbratta> #info https://gerrit.opnfv.org/gerrit/#/c/36537/ patch for k8s support
09:11:34 <rbbratta> it requires kubernetes==2.0.0
09:12:02 <rbbratta> is that the official python kubernetes client?
09:12:23 <JackChan> rbbratta: yes
09:13:26 <rbbratta> okay, and you are testing with OpenRetriever?
09:14:06 <rbbratta> #info everyone please review kubernetes context patch
09:14:22 <JackChan> yes, I use OpenRetriever code to install k8s. Then test in the environment.
09:14:40 <rbbratta> JackChan: great, good work
09:15:31 <kubi001> JackChan: Cool
09:15:40 <JackChan> :-)
09:16:18 <rbbratta> I'll try to get people to review
09:16:32 <rbbratta> okay, next topic, anteater
09:16:54 <rbbratta> #topic CI Gate Security (Anteater)
09:17:13 <rbbratta> the anteater want to start running it on all the projects
09:17:25 <rbbratta> it will just report issues but won't vote.
09:17:40 <rbbratta> is everyone familiar with what anteater checks?
09:18:03 <rbbratta> anteater checks for security issues, ssh keys, passwords, etc.
09:18:05 <kubi001> It is a good start. we should have the security scan
09:18:24 <rbbratta> we have to generate whitelist to ignore things
09:18:39 <rbbratta> I haven't run it yet, but I assume we have a bunch of issues.
09:18:50 <Jing_> I have a patch run security verify
09:18:56 <rbbratta> since we have example passwords hardcoded everywhere
09:19:00 <Jing_> #link https://build.opnfv.org/ci/job/opnfv-security-audit-verify-master/523/console
09:19:12 <kubi001> for C release, Luke gave a report  of yardstick for the scurity scaning
09:19:27 <Jing_> seems check  Licence header missing and other stuff
09:20:11 <rbbratta> okay, so I don't know when they will start scanning, just is just notice that it will happen at some point
09:21:19 <kubi001> it already run with releng
09:21:46 <kubi001> Luke gave a report  of yardstick for the scurity scaning, there were 100+ issues
09:22:06 <rbbratta> ah okay I missed that
09:22:16 <rbbratta> do we have the list of issues?
09:22:22 <kubi001> However, he said it is OK to keep it. no high risk. for C release
09:22:52 <rbbratta> C release? or D release?
09:23:12 <kubi001> C release, they didn't do security scanning in Danube
09:23:51 <rbbratta> okay I assume they will start scanning master branch via Jenkins
09:23:53 <kubi001> so that's why we really need to security scan with verify job
09:24:17 <kubi001> yes, that is a good idea.
09:24:48 <rbbratta> okay, we'll follow up with Luke and see when it can be enabled.
09:25:29 <rbbratta> #action Ross check when anteater will start checking master on Jenkins
09:25:39 <rbbratta> okay, next topic
09:25:44 <rbbratta> #topic AoB
09:26:59 <rbbratta> going once
09:27:05 <rbbratta> going twice
09:27:17 <abhijitsinha> yes this time slot is ok
09:27:30 <abhijitsinha> sorry wrong tab
09:27:43 <rbbratta> abhijitsinha: :)
09:27:47 <rbbratta> okay we are done
09:27:54 <rbbratta> #endmeeting