| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2017-08-02 | |||
| 15:15:39 | zhipeng | got disconnected ... | |
| 15:17:36 | zhipeng | any other outstanding issue ? | |
| 15:17:47 | zhipeng | crushil you got other upcoming patches ? | |
| 15:18:04 | crushil | Waiting for y'all's to get merged | |
| 15:18:34 | zhipeng | ?? | |
| 15:18:48 | zhipeng | https://review.openstack.org/#/q/status:open+project:openstack/cyborg | |
| 15:18:55 | zhipeng | there are no patches from you | |
| 15:19:42 | crushil | I know | |
| 15:20:24 | crushil | But I am waiting for the API and DB patches to get merged | |
| 15:20:55 | crushil | I need to base off my next change on zhuli and jkilpatr's patches | |
| 15:22:16 | crushil | I have a stub patch in. Now, we need a dev setup where we can play with all this. It can be ansible generated or it can be devstack generated | |
| 15:22:41 | crushil | Does this make sense? | |
| 15:22:48 | zhipeng | yes get your point | |
| 15:23:06 | zhuli | +1 | |
| 15:23:17 | NokMikeR | Hi folks. | |
| 15:23:28 | zhipeng | hey mikes | |
| 15:44:59 | jkilpatr | hey | |
| 15:45:11 | jkilpatr | man I need to put on a klaxxon or somthing for this meeting, I keep getting caught up | |
| 15:46:01 | zhipeng | jkilpatr no problem | |
| 15:46:10 | jkilpatr | crushil, I agree my db commit is stubby I say we land zhuli crushil and my patches then I'll put up a patch for the installer | |
| 15:46:44 | crushil | cool | |
| 15:46:55 | crushil | my initial driver stub is already in | |
| 15:47:14 | jkilpatr | wonder if we can get someone else to host the CI job or if I should just do it. | |
| 15:47:23 | crushil | I need to make some additions and I will push that in this week | |
| 15:47:35 | jkilpatr | as a note I'm going to test/target Tripleo with my install playbook, a playbook for targeting devstack I'll need help with. | |
| 16:21:01 | zhipeng | jkilpatr would Tripleo be a overkill for us ? | |
| 16:22:45 | jkilpatr | zhipeng, for random development work it totally is. I just happen to have tripleO clouds by the dozen since testing it is a big part of my role. | |
| 16:23:03 | zhipeng | ah ok | |
| 16:42:55 | jkilpatr | zhipengh[m], that being said it's probably best to test for 'prod' setups along instead of being devstack only until everything works there only to see it all break again when we try to deploy for real | |
| 16:43:29 | zhipeng | yes I agree with that | |
| #openstack-cyborg - 2017-08-03 | |||
| 12:24:24 | dims | zhipengh[m] : are you considering a tag/branch for pike for cyborg? | |
| 12:42:01 | zhipengh[m] | dims I'm definitely interested, although not familiar with the release engineering process | |
| 12:43:33 | dims | zhipengh[m] : most of the steps are documented here - https://docs.openstack.org/infra/manual/creators.html | |
| 12:45:44 | dims | zhipengh[m] : there's more stuff on this page - https://docs.openstack.org/infra/manual/drivers.html#tagging-a-release | |
| 12:46:18 | dims | see "Tagging a Release" for example | |
| 12:46:46 | zhipengh[m] | THX ! :) | |
| 12:49:19 | dims | zhipengh[m] : please join #openstack-release channel and we can talk more there if you have any questions | |
| 12:50:00 | dims | zhipengh[m] : since both cyborg and mogan are in the same boat, i've asked zhenguo to ping you as well | |
| 12:50:24 | zhipengh[m] | Haha ok | |
| 12:53:11 | zhipengh[m] | Looks similar to what we've been doing in OPNFV for release | |
| 12:54:10 | zhipengh[m] | dims since cyborg is not official, what would be the benefit to cut a release ? | |
| 12:55:22 | dims | zhipengh[m] : it's part of the process to become official, you can tell folks that there's a tag/branch for use with a specific openstack release if they wish to try it | |
| 12:55:47 | zhipengh[m] | Ah right | |
| 12:56:09 | zhipengh[m] | I remember Joe did this for tricircle | |
| 12:56:41 | dims | when it comes time to submit for governance, we can show that we have been putting out releases already and possibly picked up some operators/users | |
| 13:00:20 | zhipengh[m] | That is a great point | |
| 13:05:46 | zhipeng | okey I think the meetbot should capture dims's conversation on tag/branch | |
| 13:05:51 | zhipeng | #endmeeting | |
| 13:05:53 | openstack | Meeting ended Thu Aug 3 13:05:51 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 13:05:54 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-08-02-15.06.html | |
| 13:05:55 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-08-02-15.06.txt | |
| 13:05:56 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-08-02-15.06.log.html | |
| 13:07:46 | zhipeng | dims we have the longest openstack team meeting XD | |
| 13:11:17 | dims | LOL, i did not even know that a meeting was on :) | |
| 13:12:41 | zhipengh[m] | A little ambushy huh :P | |
| 13:21:42 | dims | LOL | |
| #openstack-cyborg - 2017-08-09 | |||
| 15:01:14 | crushil | \o | |
| 15:01:22 | zhipeng | o/ | |
| 15:01:30 | zhipeng | #startmeeting | |
| 15:01:37 | openstack | zhipeng: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' | |
| 15:01:47 | zhipeng | #startmeeting openstack-cyborg | |
| 15:01:49 | openstack | Meeting started Wed Aug 9 15:01:47 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 15:01:50 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 15:01:53 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 15:04:13 | zhipeng | anyone else is here for the meeting ? | |
| 15:05:15 | zhuli | I'am here | |
| 15:05:34 | zhipeng | hey zhuli :) | |
| 15:05:38 | zhipeng | thx for the new patches | |
| 15:05:42 | zhipeng | looks awesome | |
| 15:05:52 | zhipeng | #topic patch discussion | |
| 15:05:58 | zhipeng | #link https://review.openstack.org/#/q/status:open+project:openstack/cyborg | |
| 15:06:25 | zhipeng | zhuli could you go over the two patches you submitted ? | |
| 15:08:09 | zhuli | sure, one is for api which add some hook to cyborg | |
| 15:08:49 | zhuli | the other is WIP, aim to go through the api -> conductor -> db | |
| 15:10:07 | zhipeng | so about the second patch, what is the relationship between it and Justin's patch on conductor ? | |
| 15:10:21 | zhuli | after that, I'll add some unittest as well | |
| 15:13:12 | zhipeng | sorry got disconnected ... | |
| 15:13:28 | zhipeng | zhuli did you answer my previous question ? | |
| 15:13:39 | zhuli | hmm, justin's conductor patch is good for functionality but make all conductor related stuff together which I think should be refactored to be more modular | |
| 15:14:17 | zhipeng | modular on conductor itself ? | |
| 15:15:47 | zhuli | because we need a separate conductor service | |
| 15:16:13 | zhuli | modular on the whole cyborg project | |
| 15:16:48 | zhipeng | okey got it | |
| 15:17:04 | zhipeng | so the second patch would be a followup of Justin's patch , right ? | |
| 15:17:56 | zhuli | yes | |
| 15:18:07 | zhipeng | great :) | |
| 15:18:24 | zhipeng | crushil do you have any updates ? | |
| 15:18:33 | crushil | zhipeng, Nope | |
| 15:18:57 | zhipeng | your upcoming patch depends on the current unmerged Justin patch ? | |
| 15:19:42 | crushil | Yup | |
| 15:19:57 | crushil | Have some customer engagements going on right now and after that will get back working on the next driver patch | |
| 15:20:08 | zhipeng | okey | |
| 15:20:22 | zhipeng | if you got time plz review Justin's patch and help merge it | |
| 15:20:32 | zhipeng | I already gave my +2 | |
| 15:20:36 | crushil | zhipeng, Will do | |
| 15:20:41 | zhipeng | thx :) | |
| 15:20:51 | zhipeng | #topic release branching/tagging | |
| 15:21:18 | zhipeng | so last week dims from Technical Committee made a suggestion that we should consider cut a pike release branch | |
| 15:21:53 | zhipeng | as part of the evidence/effort when we apply for the official project status | |
| 15:22:14 | zhipeng | do you guys have any thoughts on the criteria for the release cutting ? | |