07:30:26 <zhihui_wu> #startmeeting qtip
07:30:26 <collabot> Meeting started Mon Jan 15 07:30:26 2018 UTC.  The chair is zhihui_wu. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:30:26 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
07:30:26 <collabot> The meeting name has been set to 'qtip'
07:30:52 <zhihui_wu> #topic roll call
07:31:14 <zhihui_wu> #info zhihui_wu
07:31:36 <Taseer> #info Taseer
07:32:10 <yujunz> #info yujunz
07:33:06 <zhihui_wu> #topic NPI
07:33:49 <zhihui_wu> #info qdai shares a PPT with us about integrate STCv with QTIP
07:35:02 <zhihui_wu> #link: https://drive.google.com/file/d/19sEFRQ5Mq-NsaFiyDmf-FdKEYttdHZ_Z/view?ths=true
07:35:56 <yujunz> Looks nice
07:36:15 <zhihui_wu> ping qdai
07:36:15 <qdai> rest api is draft, maybe there are minor changes for exensibility
07:37:55 <qdai> this is my first time to design rest api. so need any comments from you
07:38:56 <qdai> I reference storeperf in design and implementation
07:39:29 <yujunz> You mean the NetTest container is newly implemented for this task ?
07:39:38 <zhihui_wu> Taseer, what's your opinion about this REST API?
07:40:15 <Taseer> I think it is fine, though I personally do not have much experience in it
07:41:22 <qdai> yes, I plan to place more net test case into this container in the future
07:42:08 <yujunz> Have you already written some code for PoC?
07:43:38 <qdai> yes, I'm writing code and debug it on my local environment, but currently focus on server side
07:45:19 <qdai> as for now I have no time to think about client side carefully
07:45:38 <zhihui_wu> Do you need someone to implement client side?
07:47:39 <qdai> yes, if we get stable api, we can develop paraller
07:48:27 <zhihui_wu> OK
07:48:53 <zhihui_wu> I have a question about the stack
07:49:33 <qdai> when do you plan to finish first Fraser release?
07:50:04 <zhihui_wu> Is stack created by NetTest? or just post a request to tell QTIP
07:51:59 <yujunz> #link https://wiki.opnfv.org/display/SWREL/Fraser#Fraser-MilestoneGanttChart
07:52:06 <yujunz> The release schedule for Fraser
07:52:32 <qdai> stack is created by NetTest, because it is customized
07:54:38 <zhihui_wu> I see
07:54:38 <qdai> I feel QTIP can not do a stack for all kinds of test
07:55:16 <qdai> if let QTIP do it, it will make the interaction between QTIP and test driver more complex
07:56:24 <zhihui_wu> It seems qtip just need to tell Nettest the testcase name.
07:56:51 <zhihui_wu> because the image and flavor are all customized
07:56:56 <qdai> some necessary params
07:57:57 <qdai> not only image and flavor, even some user data
07:58:13 <qdai> and some configuration
07:59:19 <zhihui_wu> So the prerequisite is done by QTIP, right?
08:00:16 <qdai> if QTIP need know these infos, it will lock in concrete implementation
08:01:02 <qdai> yes
08:01:39 <zhihui_wu> OK
08:04:36 <zhihui_wu> When will you give the first patch about it?
08:09:22 <zhihui_wu> emmm...
08:09:38 <zhihui_wu> Let's start the next topic....
08:09:45 <zhihui_wu> #topic weekly update
08:09:52 <zhihui_wu> I'll go first.
08:10:25 <zhihui_wu> #info the ci job on zte-virtual is OK now.
08:10:42 <qdai> I feel I can finish it before spring festival
08:11:14 <zhihui_wu> qdai, waiting for your patch...:)
08:11:37 <zhihui_wu> #link https://build.opnfv.org/ci/view/qtip/job/qtip-compute-fuel-zte-virtual6-master/68/console
08:12:11 <zhihui_wu> QTIP compute test can run against MCP.
08:13:04 <yujunz> Good to know. So this task is done?
08:13:22 <zhihui_wu> yes, I think.
08:14:37 <zhihui_wu> OK, that's all.
08:15:04 <yujunz> My update.
08:15:21 <yujunz> Fixed the command not found error in qtip container
08:15:43 <yujunz> And converted ipynb to rst.
08:15:52 <yujunz> The job is done weeks ago but blocked by CI
08:16:06 <yujunz> Now the ipynb job is disabled. So it is successful now.
08:16:12 <yujunz> #link https://gerrit.opnfv.org/gerrit/#/c/48355/
08:17:04 <yujunz> That's all
08:18:33 <zhihui_wu> #topic tasks
08:19:34 <zhihui_wu> Taseer, I think we can continue working on vm test, what do you think?
08:22:58 <zhihui_wu> #info zhihui_wu will create a new ci job for vm test
08:23:17 <Taseer> okay
08:24:23 <zhihui_wu> akhilbatra, I heard from yujunz you are busy in looking for a job recently.
08:25:28 <akhilbatra> I got one offer recently :)
08:25:50 <akhilbatra> I will take it most probably
08:25:51 <zhihui_wu> congratulations
08:25:56 <akhilbatra> Thanks
08:27:13 <zhihui_wu> About AWX task, if you have some progress, please let's know.
08:28:01 <qdai> awx is still work on vpod?
08:29:06 <zhihui_wu> akhilbatra, is the awx container back to normal?
08:29:10 <qdai> I forgot the awx url, could you share it again?
08:29:54 <akhilbatra> It's up now
08:29:58 <akhilbatra> 172.80.0.239
08:30:11 <akhilbatra> user - admin
08:30:11 <akhilbatra> password - password
08:30:34 <zhihui_wu> ok, I will update the information in wiki page.
08:30:37 <qdai> could you give the full url?
08:31:06 <qdai> which port?
08:31:12 <akhilbatra> 80
08:31:29 <akhilbatra> It should directly open
08:32:22 <qdai> yes, it works, thanks
08:32:59 <zhihui_wu> anything else?
08:33:06 <akhilbatra> I am thinking of exlploting Ansible-tower api for composite tasks specific to qtip (e.g. Setup job run and "Run" job task template creation)
08:33:06 <akhilbatra> Which can be accessed at
08:33:06 <akhilbatra> 172.80.0.239/api/v2
08:33:12 <akhilbatra> *exploiting
08:35:09 <akhilbatra> I need feedback as to how should we achieve this
08:37:47 <yujunz> I haven't got time to think it through yet.
08:37:59 <akhilbatra> Does ansible playbook provide job triggers
08:38:00 <akhilbatra> ?
08:38:14 <yujunz> What kind of job trigger?
08:38:22 <yujunz> It has some callback on each stage
08:39:05 <akhilbatra> Like triggering a program which create a "Run" Job temaplate after successful "Setup" Job run
08:39:51 <yujunz> It sounds like the handler in ansible
08:40:20 <yujunz> It is sometimes used for trigger service restart on configuration change
08:41:28 <akhilbatra> ok I will look into it
08:41:42 <akhilbatra> We can discuss it offmeeting
08:42:27 <zhihui_wu> OK, thanks everyone！
08:42:34 <zhihui_wu> #endmeeting