Earlier  
Posted Nick Remark
#openstack-cyborg - 2017-08-23
16:25:38 zhipeng not for official mascot
16:26:28 crushil Somebody for Ironic designed their own thing
16:26:42 crushil I know some folks who could do the design for us
16:27:40 zhipeng for free right ? lol
16:48:19 crushil Ya
17:53:07 jkilpatr zhipengh[m], https://docs.google.com/spreadsheets/d/18DmI9ydq6dKr4hAcoAN83vYXWn8TV1NEvy09Ll02_Y0/edit#gid=0
19:17:56 crushil zhipengh[m], Do it on monday or tuesday
19:18:21 crushil Or tuesday. Can't do it on monday
#openstack-cyborg - 2017-08-24
02:58:32 zhipeng jkilpatr crushil okey seems like I need to re-register since only Tuesday and Wed showing here
03:01:48 zhipeng ah no worries, i misunderstood
03:02:41 zhipeng put it down on Tuesday right before lunch
03:02:46 zhipeng #endmeeting
03:02:49 openstack Meeting ended Thu Aug 24 03:02:46 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
03:02:50 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-08-23-15.07.html
03:02:51 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-08-23-15.07.txt
03:02:52 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-08-23-15.07.log.html
#openstack-cyborg - 2017-08-28
17:55:15 jkilpatr zhuli, so I want to implement a complete command. right now it doesn't look like api can be configured to do rpc? Does that need to be added
18:03:38 zhuli that's weird, I have tested on my env the rpc works fine, so do api
18:04:27 jkilpatr really? where would I put the rpc configuration url?
18:05:30 zhuli did you configure the /etc/cyborg/cyborg.conf with correct database.connect and default.transport_url?
18:06:18 jkilpatr nope, I was looking in the code for where it was loaded, let me guess the openstack service library handles that?
18:07:04 zhuli yes, the oslo.config handles it
18:07:16 jkilpatr ok I'll give that a try
19:48:31 jkilpatr zhuli, ok yup it does work
#openstack-cyborg - 2017-08-29
01:14:36 zhuli Justin, let me known if you need help or any questions :)
13:55:27 crushil zhuli, Can you please provide a more detailed commit message for https://review.openstack.org/#/c/497711/ and https://review.openstack.org/#/c/497828/?
13:58:11 zhipeng hi crushil, we did an internal review of cyborg application for official projects
13:58:40 zhipeng one of the advice I got is to have at least one integration testing available for one accelerator hardware
13:58:54 zhipeng so that people could kick around
13:59:04 zhipeng is it possible to do before the PTG ?
13:59:46 crushil Before the PTG?
13:59:53 crushil I am double booked till then
14:00:01 crushil I was planning on working on it after the PTG
14:00:19 zhipeng ok cool, just want to know your status :)
14:00:33 zhipeng so what is the accelerator you could play with in your lab ?
14:08:39 crushil zhipengh[m], I have a Tesla K80 in the lab
14:31:25 zhipengh[m] crushil cool
#openstack-cyborg - 2017-08-30
15:01:23 zhipeng cyborgers
15:01:46 jkilpatr booyha
15:02:03 jkilpatr got a working version of the deployment patch up, need someone to test it on devstack
15:02:20 zhipeng great !
15:02:21 jkilpatr well I could test it on devstack, but it could be quicker if someone else has one already stood up.
15:02:37 zhipeng #startmeeting openstack-cyborg
15:02:38 openstack Meeting started Wed Aug 30 15:02:37 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:40 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:42 openstack The meeting name has been set to 'openstack_cyborg'
15:02:57 jkilpatr one comment for zhuli you capture rpc connection errors and log them in the common service code, but you don't change the exit code, this makes automated checks difficult :(
15:03:00 jkilpatr I'
15:03:17 jkilpatr I'm not really sure what to do to fix it, since there seems to be some graceful exit code there I didn't want to break
15:04:22 zhipeng i will let him know if he's not here
15:04:22 zhipeng zhuli around ?
15:04:36 zhipeng #topic patch discussion
15:04:49 zhuli yep, I'm here
15:04:52 crushil jkilpatr, I can test it on devstack
15:05:03 zhipeng crushil that'd be great
15:05:16 zhipeng zhuli did you get justin's question ?
15:05:18 crushil I will add a devstack plugin too soon. Hopefully this week
15:06:35 zhipeng thx crushil, looking forward to it
15:06:49 zhuli I will confirm the rpc exit code issue later
15:08:00 zhipeng thx zhuli
15:08:16 zhuli jkilpatr, I will test it on devstack too if I have time
15:09:38 zhipeng so any questions on zhuli's three new patches ?
15:09:55 jkilpatr commit messages!
15:10:00 zhipeng other than comit msg fixing as uaual
15:10:04 zhipeng haha I was just saying
15:10:04 jkilpatr lol
15:10:24 jkilpatr looks good to me otherwise, I think I commented on at least two, I'll have to go and look at the third.
15:10:49 zhuli I think I need fulfill the commit messages before merged
15:10:56 zhuli yep
15:12:20 zhipeng zhuli just git commit --amend everytime after git commit -a -m :P
15:12:42 zhipeng so we got one more new patch, from a colleague of mine
15:12:47 zhipeng #link https://review.openstack.org/#/c/498690/
15:13:12 zhipeng this is a new spec (targeting queen) for SPDK driver
15:13:23 zhipeng for high perf NVMe SSDs as accelerators
15:13:39 zhuli zhipeng, thx
15:14:08 zhipeng zhuli no problem
15:14:20 zhipeng everyone plz help review the spdk spec when you got time
15:14:32 zhipeng altho this is not Pike priority
15:15:12 jkilpatr so this involves cyborg reconfiguring other openstack services
15:15:25 zhipeng not really I think
15:15:34 jkilpatr don't we need to do some config in cinder?
15:15:36 jkilpatr can we do that live?
15:15:51 zhipeng no we only do that for spdk
15:16:05 jkilpatr ok then I'm less concerned about the scope getting too big then.
15:16:58 zhipeng so spdk is in the config anyways
15:16:58 zhipeng the premise of this scenario is that Cinder will use a accelerated backend
15:17:04 zhipeng yep
15:17:16 jkilpatr just don't want to obligate us to restart other services
15:17:24 zhipeng definitely
15:18:32 jkilpatr so the conductor is in charge of nova placement api interaction?
15:18:39 jkilpatr we should start looking into that.
15:18:56 zhipeng I was gonna discuss with you about that
15:19:04 zhipeng okey let's move on to the next topic
15:19:18 zhipeng #topic Denver PTG TC presentation prep
15:20:41 zhipeng for us to better present the project to the TC
15:20:41 zhipeng I did a internal check with our TC member, and get several really good suggestions
15:20:41 zhipeng so I will do a project update presentation to TC on Sep 12th
15:20:57 jkilpatr oh cool we're presenting to TC
15:21:04 zhipeng So one thing would be an end to end workflow demo of Nova works with Cyborg
15:21:14 zhipeng could be just bare minimum functionality

Earlier   Later