Earlier  
Posted Nick Remark
#openstack-cyborg - 2017-05-24
15:24:46 jkilpatr isn't the pike deadline in like a month? or am I off
15:25:05 jkilpatr I guess that's possible
15:26:27 zhipeng_ no that was the spec deadline
15:26:47 zhipeng_ the end of cycle would be around Sep ?
15:26:49 crushil Hmmm, that would be complicated. I will be on PTO between Mid June to Mid July. Gone for almost a month
15:27:16 crushil August 28 is end of Pike I believe
15:27:28 zhipeng_ anyways let's try to shoot for Sep finish
15:27:30 jkilpatr oh man we have more time than I thought
15:27:35 jkilpatr that's doable
15:27:37 zhipeng_ Sep 11th is the PTG
15:27:39 zhipeng_ ya
15:27:44 jkilpatr where is it this time?
15:27:49 zhipeng_ lucky we are not doing actual releases :P
15:28:00 crushil Denver
15:28:41 jkilpatr can't say for sure if I'll be there yet.
15:28:59 crushil I'm still unclear on this, which backend should I use for the driver? VirtIO or a specific hardware?
15:29:23 jkilpatr well it's supposed to be generic, use virtIO
15:29:43 crushil ok
15:30:07 zhipeng_ i think virtio would be preferred choice now
15:34:04 zhipeng_ crushil you might consider what justin suggested for the generic patch
15:34:14 zhipeng_ gate god did not shine upon you today :P
15:34:19 crushil Lol
15:34:28 zhipeng_ two of J's specs are both merged
15:36:03 jkilpatr \0/
15:36:40 jkilpatr I have experience pleasing Zull the linter god.
15:36:44 jkilpatr Zuul*
15:37:27 crushil It's unable to install dependencies for some reason
15:37:50 jkilpatr yes but to what package?
15:38:25 crushil Will probably do a reverify in a couple of hours
15:38:32 crushil could not install deps [-r/home/jenkins/workspace/gate-cyborg-docs-ubuntu-xenial/test-requirements.txt, -r/home/jenkins/workspace/gate-cyborg-docs-ubuntu-xenial/requirements.txt]
15:40:43 jkilpatr crushil, test-requirements.txt is the file in cyborg repo
15:40:50 jkilpatr rebase your commit and see if an updated one works
15:41:07 jkilpatr or perhaps it's the other way around and my lack of rebasing means the old test-requirements.txt works and the new one doesn't
15:41:32 crushil Well rebased it now. We'll see what it does
15:41:33 jkilpatr either way the correct soltuion is to open up a new dummy commit, see if the linters run, then edit test-requirements until they do, then merge that and rebase everything else
16:41:05 ttk2[m] Anyways anything else?
16:41:13 ttk2[m] I think we lose zhipeng again.
16:41:17 ttk2[m] Lost*
16:41:28 zhipeng_ i was lost ..
16:41:35 zhipeng_ but managed to get back
17:03:35 crushil endmeeting?
17:04:09 zhipeng_ seems ok now
17:04:13 zhipeng_ #endmeeting
17:04:15 openstack Meeting ended Wed May 24 17:04:13 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
17:04:16 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-05-24-15.00.html
17:04:17 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-05-24-15.00.txt
17:04:18 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-05-24-15.00.log.html
#openstack-cyborg - 2017-05-26
19:42:52 jkilpatr starting to think about packaging before I get to work on the conductor/agent, I'm thinking pip and a simple playbook, do we just want to put the python modules into one repo for now?
#openstack-cyborg - 2017-05-31
14:54:05 jkilpatr \0
15:00:04 crushil \o
15:03:40 zhipeng_ hey folks
15:08:45 jkilpatr zhipeng_, you have a few typos to address on your commit, linters seem to have calmed down
15:11:28 zhipeng_ ya I saw the comment, will fix that tmr :)
15:11:36 zhipeng_ anyways let me start the meeting
15:11:55 zhipeng_ catch the discussion as people talk
15:12:06 zhipeng_ #startmeeting openstack-cyborg
15:12:07 openstack Meeting started Wed May 31 15:12:06 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng_. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:12:08 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:12:10 openstack The meeting name has been set to 'openstack_cyborg'
15:12:22 zhipeng_ jkilpatr about the packaging
15:12:30 zhipeng_ could you elaborate a little bit more ?
15:12:36 zhipeng_ #topic packaging options
15:12:52 jkilpatr So I was wondering how we easily setup the project while we're doing dev
15:13:19 jkilpatr I don't know what you guys have for test environments but I can stand them up and tear them down very easily, so an ansible playbook that just uses pip to install the components would make me happy.
15:13:39 jkilpatr I don't know what other sort of distribution system we would use. So suggestions are welcome.
15:14:19 zhipeng_ pip would be the common practice for OpenStack, right ?
15:14:42 jkilpatr I'm not actually sure never installed a project not packaged by someone for me...
15:15:07 jkilpatr but yes it's python I don't see what else they would use, except maybe some sort of heat / mistral stuff.
15:15:29 crushil I use devstack for dev or RDO if I want to test it in a production style environment
15:15:41 zhipeng_ mistral got a different system ?
15:15:45 zhipeng_ hey crushil
15:15:59 jkilpatr well you could do it with mistral I have no idea if it's a good idea, never did anything with it myself.
15:16:10 jkilpatr anyways sounds like no one has an issue with pip
15:16:19 zhipeng_ yep I guess so
15:17:14 zhipeng_ #agreed pip for packaging options
15:17:40 zhipeng_ #topic development process
15:18:31 zhipeng_ I will address ChirsD and Justin's comment on the api spec
15:18:51 zhipeng_ so after spec freezes, how should we coordinate on the code development ?
15:19:07 zhipeng_ shall we write each part first ?
15:20:10 jkilpatr I think we should start and put up a review quickly, wait until it's possible to use all the different reviews together and then merge them and move on from there.
15:20:18 jkilpatr it's important we have a good test/integration workflow
15:20:48 jkilpatr um what about standards, I assume most of pep8 (longer line length limit maybe) + some unit test coverage?
15:21:12 zhipeng_ that would be reasonable
15:21:26 zhipeng_ what do you mean by start and put up a review quickly ?
15:21:55 jkilpatr I mean don't go off and code everything then put it up for review. Ideally we start playing around with and testing each others code very early.
15:22:24 jkilpatr it's kinda embarassing to put up unfinished stuff, everyone want's to come in and micdrop great code. But it's not the best way to work.
15:23:30 zhipeng_ okey that I agree
15:24:30 zhipeng_ we will need multiple patches for the spec anyways
15:24:57 zhipeng_ no patch would be too small :P
15:34:20 jkilpatr any other business? I know we still haven't managed to fully define the nova workflow but I need to find time to play with that, ideally with skeleton versions of the rest of cyborg, which is what we agreed on last week.
15:36:40 zhipeng_ i don't have any other stuff on the plate
15:39:22 zhipeng_ so I will leave the channel open for another hour, then I'll close it
15:39:59 crushil Ok
15:40:01 jkilpatr cool, we can get the api commit in and meet next week to start putting things together sound good?
15:40:14 crushil Sounds good to me
15:42:33 zhipeng_ yes
15:42:56 crushil Does nova accelerators work well with virtIO today?
15:43:33 zhipeng_ I'm not aware Nova got vanila virtio based drivers
15:43:39 zhipeng_ for accelerators
15:44:17 zhipeng_ I think for Nova, it mainly means see if kvm got virtio support

Earlier   Later