| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-06-02 | |||
| 22:32:55 | tosky | melwitt: crossing fingers :) | |
| 22:33:13 | melwitt | :) | |
| #openstack-nova - 2021-06-03 | |||
| 01:19:17 | gmann | melwitt: replied on this - https://review.opendev.org/c/openstack/nova/+/762013/2/doc/source/configuration/policy-concepts.rst#220 | |
| 01:20:03 | gmann | melwitt: I agree on your point. I will add the current limitation for force_host and requested_destination | |
| 01:20:41 | gmann | zero_disk and external-network seems good. later one depends on neutron policy but that is open for project reader also | |
| 01:37:05 | opendevreview | Ghanshyam proposed openstack/nova master: Remove PROJECT_ADMIN limitation from zero-disk and external-network policy https://review.opendev.org/c/openstack/nova/+/794360 | |
| 01:38:07 | gmann | melwitt: ^^ | |
| 02:18:06 | opendevreview | Ghanshyam proposed openstack/nova master: Improve policy doc for supported scope info https://review.opendev.org/c/openstack/nova/+/762013 | |
| 02:18:10 | gmann | melwitt: stephenfin ^^ updated | |
| 05:06:39 | opendevreview | melanie witt proposed openstack/nova master: Make test_refresh_associations_* deterministic https://review.opendev.org/c/openstack/nova/+/794396 | |
| 05:10:22 | melwitt | gmann: did you mean to remove the table when you went from PS2 to PS3? https://review.opendev.org/c/openstack/nova/+/762013/2..3/doc/source/configuration/policy-concepts.rst#b307 | |
| 05:17:05 | melwitt | added a comment on the review ^ | |
| 07:44:13 | bauzas | hmpf, reminder that we have an office hour in 15 mins , I guess | |
| 07:58:04 | gibi | yes | |
| 07:58:09 | gibi | in 2 mins :) | |
| 07:58:17 | gibi | ... | |
| 07:58:17 | gibi | I'm almost ready to start | |
| 08:00:16 | gibi | #startmeeting nova_extra | |
| 08:00:17 | opendevmeet | Meeting started Thu Jun 3 08:00:16 2021 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 08:00:18 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 08:00:20 | opendevmeet | The meeting name has been set to 'nova_extra' | |
| 08:00:58 | gibi | welcome o/ | |
| 08:01:16 | suzhengwei__ | \o/ | |
| 08:01:38 | XinxinShen | o/ | |
| 08:01:51 | gibi | ... waiting a minute to lets everybody join | |
| 08:03:24 | gibi | So a quick summary. We agree to have this meeting time slot one a Months in every first Thursday here in #openstack-nova | |
| 08:03:33 | gibi | s/one/once/ | |
| 08:04:04 | gibi | but we haven't talked about yet what would be a good format for it | |
| 08:04:19 | gibi | should we go through the normal meeting agenda | |
| 08:04:33 | gibi | talking about bugs, CI, release, stable, | |
| 08:04:44 | gibi | or just go with an open agenda, like in an office hour | |
| 08:05:06 | gibi | what is the preference of the people present? | |
| 08:05:14 | gibi | I can do both if needed | |
| 08:07:07 | suzhengwei__ | This is the first extra meeting. My colleague didn't prepare for it enough. | |
| 08:07:18 | gibi | suzhengwei__: no worries | |
| 08:07:56 | suzhengwei__ | Open agenda will be all right. | |
| 08:08:09 | gibi | If no oppinions about the format then I would go with the simple open agenda | |
| 08:08:19 | gibi | suzhengwei__: cool, then we are on the same page | |
| 08:08:23 | suzhengwei__ | ok | |
| 08:08:27 | gibi | and we can change later if needed | |
| 08:08:59 | gibi | I have one agenda point for today | |
| 08:09:47 | gibi | just want to refresh the process we have in nova about the release | |
| 08:09:56 | gibi | so we just had Milestone 1 last week | |
| 08:10:07 | gibi | that that point of time there is no special deadline in nova | |
| 08:10:23 | gibi | the next Milestone will happen in 5 weeks from now | |
| 08:10:33 | gibi | at Milestone 2 we will do spec freeze | |
| 08:11:09 | gibi | it means that if you have open specs then you have to get merged before M2 or it will need to be re-proposed to the Y release during the autumn | |
| 08:11:21 | gibi | I'm planning to have a spec review day before M2 | |
| 08:11:29 | gibi | similarly how we had such day before M1 | |
| 08:12:12 | gibi | those features that got approved before M2 could be implemented and merged before M3 | |
| 08:12:20 | gibi | at M3 we will have feature freeze | |
| 08:12:34 | bauzas | sorry for being late, got some issue with my laptop notification | |
| 08:12:42 | gibi | bauzas: no worried :0 | |
| 08:12:43 | gibi | :) | |
| 08:13:03 | gibi | basically this is the importnat deadlines | |
| 08:13:20 | gibi | the exact dates are #link https://releases.openstack.org/xena/schedule.html | |
| 08:13:31 | gibi | is there any question about these? | |
| 08:14:42 | suzhengwei__ | Got it. | |
| 08:15:12 | gibi | cool | |
| 08:15:47 | gibi | that was what I prepared for today. | |
| 08:15:53 | gibi | Is there any topic you want to discuss? | |
| 08:15:53 | bauzas | next open office hour would be around the spec freeze | |
| 08:16:01 | bauzas | so, I have a concern | |
| 08:16:02 | gibi | bauzas: god point | |
| 08:16:05 | gibi | good even | |
| 08:16:20 | gibi | bauzas: tell us | |
| 08:16:29 | bauzas | how can we help contributors that are not in the nova meeting for their own specs ? | |
| 08:16:41 | bauzas | how can we discuss ? | |
| 08:17:08 | gibi | bauzas: what problem do you see that we need to dicuss in a meeting? stuck reviews? | |
| 08:17:19 | bauzas | and if we want to have priorities between some reviews, how could we know which ones ? | |
| 08:18:05 | bauzas | gibi: my point is that sometimes it's nice to discuss directly in IRC when you have some spec questions | |
| 08:18:10 | gibi | sure | |
| 08:18:19 | gibi | but it does not need to be a in the form of a meeting | |
| 08:18:28 | bauzas | yup | |
| 08:18:50 | bauzas | so, I wonder how we could help the contributors that aren't around in general | |
| 08:18:53 | gibi | still if there is question now, I'm happy to hear them even during this meeting | |
| 08:19:22 | gibi | bauzas: I'm OK to do discussion primarily in the spec review | |
| 08:19:52 | gibi | and if we hit a wall there then we can try to find a common time between the spec author and the reviewers to resolve | |
| 08:19:57 | gibi | the block | |
| 08:20:01 | bauzas | yup | |
| 08:20:16 | gibi | suzhengwei, XinxinShen do you have a view on this? | |
| 08:21:22 | gibi | do you feel it is hard to discuss issues about the specs? | |
| 08:23:21 | bauzas | in general, it takes more than one week | |
| 08:23:37 | bauzas | for example, when I review a spec, I provide some comment | |
| 08:23:50 | bauzas | but then the reply could be on the next day | |
| 08:24:00 | bauzas | and then I'd only see it honestly by the end of the week | |
| 08:24:23 | suzhengwei | Is this channel often open to all? I means if i want to get help, would someone react in time? | |
| 08:24:41 | bauzas | suzhengwei: yes, in general, we do it this way | |
| 08:24:50 | suzhengwei | good | |
| 08:24:58 | bauzas | suzhengwei: for example, when I'm reviewing some gibi's spec, I'm pinging him | |
| 08:25:04 | gibi | suzhengwei: it depends on the time zone. like I tend to be here between UTC 7:00 - UTC 17:00 on workdays | |
| 08:25:08 | bauzas | telling him that I had some questions | |
| 08:25:25 | bauzas | so, sometimes we directly discuss on IRC for a spec | |
| 08:25:31 | suzhengwei | cool | |
| 08:25:35 | bauzas | but like gibi said, we're both on the same TZ | |
| 08:25:45 | bauzas | so it's simple | |
| 08:26:09 | gibi | suzhengwei: I keep my client up during the night so I will see pings next day | |
| 08:26:14 | bauzas | me too | |
| 08:28:37 | XinxinShen | cool, We should ensure that the spec author and reviewer can communicate in time. | |
| 08:28:46 | gibi | suzhengwei: if you ping us, one thing to help is not just pinging but stating your problem right away | |