Earlier  
Posted Nick Remark
#openstack-cyborg - 2017-03-29
15:33:46 zhipeng the local copy is just cache for all the local updates, refreshed constantly
15:33:55 zhipeng that is my thinking
15:34:08 _gryf zhipeng, +1 for the cache instead of full blown db
15:34:37 ttk2[m] Sounds like a workable compromise.
15:34:56 crushil that sounds ok to me
15:35:36 zhipeng great :) then the DB design would remain the same, and there will be an additional design on the local cache for the agent
15:35:57 zhipeng is this ttk2[m] or crushil's ?
15:36:44 ttk2[m] I'll do the agent cache.
15:37:14 zhipeng fantastic :)
15:37:15 crushil cool
15:37:30 zhipeng #action Justin to update with the agent cache design
15:37:46 ttk2[m] Should I put that in the same blueprint?
15:37:59 zhipeng i think you could do that
15:38:12 zhipeng it should not be a big deal
15:40:33 zhipeng okey any other topics ?
15:40:50 zhipeng any questions on Roman's BP re the interaction between Nova and Cyborg
15:43:19 crushil nothing from me
15:44:02 zhipeng well let's keep review the spec anyways :P
15:44:09 zhipeng #topic AoB
15:44:17 zhipeng any other buisness ?
15:44:36 ttk2[m] Do we want to set a blueprint finish goal?
15:44:52 zhipeng ttk[m] what do you mean ? for a deadline date ?
15:44:58 _gryf ttk2[m], like a deadline or smth?
15:45:14 ttk2[m] Yes. Just something to keep things moving.
15:45:42 _gryf in other projects that depends on how big is the core reviewers pipe
15:46:10 zhipeng i would love to set a deadline lol
15:46:28 _gryf in nova there are deadlines, so they can be sure, that core reviewers spend quality time on desired and accepted features
15:46:35 zhipeng what we called in China is the lazy cancer kicked in all the time :P
15:47:03 _gryf otoh, I've seen projects, (smaller ones), that they obey only openstack release schedule
15:47:45 zhipeng I think setting a deadline/milestone would be a good idea
15:47:54 _gryf that fine.
15:47:56 zhipeng so that everyone on the same page and pace
15:48:05 zhipeng others ?
15:48:20 ttk2[m] As long as it's not too tight.
15:48:22 crushil So, for current specs, should we say EOR should be the deadline?
15:48:28 zhipeng (if we have a milestone then maybe we need a sprint someday ...)
15:48:41 zhipeng crushil for specs that would be too relax
15:48:49 zhipeng we need to get code in for Pike
15:48:59 crushil I meant implementation of the specs
15:49:07 zhipeng yes that'd agre
15:49:18 zhipeng I would agree
15:49:23 ttk2[m] Let's just put a deadline on specs for now.
15:49:29 zhipeng Apr 15th ?
15:49:46 ttk2[m] That's what 3 meetings?
15:49:57 crushil lol
15:50:02 zhipeng sounds about right
15:50:10 zhipeng too relax or too tight ? lol
15:50:40 crushil I think for most of the specs, the owners know what needs to be added
15:50:57 crushil So, it is slightly on the more relaxed side
15:51:01 zhipeng it is the reviews that takes time
15:51:25 zhipeng _gryf we are not that famous project so we could move faster XD
15:51:25 crushil Fair
15:51:31 _gryf which obviously means slipping to the next release :>
15:51:40 crushil Let's do April 15th then
15:51:52 ttk2[m] +1
15:52:10 zhipeng #vote Apr 15th as the deadline for specs
15:52:21 zhipeng okey wrong cmd ...
15:52:32 zhipeng but anyway we should all agree on this
15:52:46 zhipeng #info Apr 15th for the first milestone on spec freeze
15:53:01 zhipeng #agreed Apr 15th for the first milestone on spec freeze
15:53:31 zhipeng great discussions folks
15:53:36 zhipeng any other buisness ?
15:54:36 zhipengh[m] My Chromebook just died..
15:54:58 crushil zhipengh[m], Get a real computer. :P
15:55:11 zhipengh[m] lol give me money
15:58:18 zhipengh[m] Okey if no other biz, let me try to end meeting using this handle... Not sure it will work
15:58:27 zhipengh[m] #endmeeting
15:59:14 zhipengh[m] Bummer...
15:59:48 _gryf #endmeeting
15:59:56 _gryf lol
17:51:01 zhipeng the longest meeting ever...
17:51:05 zhipeng #endmeeting
17:51:07 openstack Meeting ended Wed Mar 29 17:51:05 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
17:51:08 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-03-29-15.00.html
17:51:09 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-03-29-15.00.txt
17:51:10 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-03-29-15.00.log.html
#openstack-cyborg - 2017-04-05
15:03:03 crushil \o
15:03:18 zhipeng_ hey
15:03:28 zhipeng_ let's go
15:03:38 openstack Meeting started Wed Apr 5 15:03:38 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng_. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:38 zhipeng_ #startmeeting openstack-cyborg
15:03:39 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:41 openstack The meeting name has been set to 'openstack_cyborg'
15:03:55 zhipeng_ #info zhipeng crushil
15:04:02 zhipeng_ who else do we have at the meeting ?
15:10:34 jkilpatr o/
15:10:36 jkilpatr sorry I'm late
15:12:08 zhipeng_ no problem,just saw your patch
15:12:16 zhipeng_ #topic BP discussion
15:12:54 zhipeng_ I must apologize that due to the cloudnativecon week, I have not been attentive to the api BP
15:13:09 zhipeng_ will get to it starting tmr I hope
15:13:29 zhipeng_ crushil jkilpatr could you guys walk through the updates ?
15:13:44 crushil Sure
15:14:08 jkilpatr crushil, you first?
15:14:15 crushil yup
15:14:28 crushil Updated the bp for the generic driver implementation and trying to incorporate all the changes that were requested
15:15:08 crushil Did some reviews on other BPs as well and waiting for the BP owners to come back with a response
15:15:53 zhipeng_ crushil cool man, any outstanding issues at the moment ?
15:15:58 crushil The generic driver implementation bp is at https://review.openstack.org/#/c/447257/
15:16:19 crushil zhipeng_, Nope, just need more review comments atm

Earlier   Later