| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-20 | |||
| 12:54:08 | gibi | manually need to make sure that it is in sync with the bridge mappings | |
| 12:54:08 | gibi | manually need to make sure that it is in sync with the bridge mappings | |
| 12:54:11 | gibi | 08:08 < gibi> sean-k-mooney: I don't know how ovn does the bridge mapping so there it might | |
| 12:54:11 | gibi | 08:08 < gibi> sean-k-mooney: I don't know how ovn does the bridge mapping so there it might | |
| 12:54:14 | gibi | not be a problem | |
| 12:54:15 | gibi | not be a problem | |
| 12:54:17 | gibi | 08:09 < gibi> the vnic_type trait has a similar consequence | |
| 12:54:17 | gibi | 08:09 < gibi> the vnic_type trait has a similar consequence | |
| 12:55:43 | sean-k-mooney | ack. bridge mapping are stored in the ovn south db casisi table in the external-ids field | |
| 12:55:43 | sean-k-mooney | ack. bridge mapping are stored in the ovn south db casisi table in the external-ids field | |
| 12:56:35 | sean-k-mooney | although in general with ovn you just have one bridge br-int | |
| 12:56:35 | sean-k-mooney | although in general with ovn you just have one bridge br-int | |
| 12:56:59 | sean-k-mooney | it might be something to test out i need to redeploy openstack soon and ill likely try doing it with ovn | |
| 12:57:00 | sean-k-mooney | it might be something to test out i need to redeploy openstack soon and ill likely try doing it with ovn | |
| 12:57:05 | sean-k-mooney | ok brb | |
| 12:57:05 | sean-k-mooney | ok brb | |
| 12:57:47 | openstackgerrit | Merged openstack/osc-placement master: Note env OS_PLACEMENT_API_VERSION support https://review.opendev.org/c/openstack/osc-placement/+/791356 | |
| 12:57:47 | openstackgerrit | Merged openstack/osc-placement master: Note env OS_PLACEMENT_API_VERSION support https://review.opendev.org/c/openstack/osc-placement/+/791356 | |
| 12:59:09 | admin0 | "admin0: not quite the db is the souce of truth for what instance should be on the host" -- will deleteing the rabbitmq and re-creating it help ? | |
| 12:59:09 | admin0 | "admin0: not quite the db is the souce of truth for what instance should be on the host" -- will deleteing the rabbitmq and re-creating it help ? | |
| 13:00:43 | openstackgerrit | Merged openstack/osc-placement master: Add openstackclient-plugin-jobs https://review.opendev.org/c/openstack/osc-placement/+/780598 | |
| 13:00:43 | openstackgerrit | Merged openstack/osc-placement master: Add openstackclient-plugin-jobs https://review.opendev.org/c/openstack/osc-placement/+/780598 | |
| 13:02:59 | stephenfin | gibi: done | |
| 13:02:59 | stephenfin | gibi: done | |
| 13:05:13 | gibi | stephenfin: thanks for the clarification, It is clear now | |
| 13:05:13 | gibi | stephenfin: thanks for the clarification, It is clear now | |
| 13:29:11 | sean-k-mooney | gibi: too bad we cant rename the bandwith resouce classes | |
| 13:29:11 | sean-k-mooney | gibi: too bad we cant rename the bandwith resouce classes | |
| 13:33:50 | sean-k-mooney | although the orginal approved specs used ingress and egress | |
| 13:33:50 | sean-k-mooney | although the orginal approved specs used ingress and egress | |
| 13:34:27 | sean-k-mooney | the were retoactivly updated to the short names https://github.com/openstack/neutron-specs/commit/2af53625e7a2e39e53db394f97328e6427cd9fb9 | |
| 13:34:27 | sean-k-mooney | the were retoactivly updated to the short names https://github.com/openstack/neutron-specs/commit/2af53625e7a2e39e53db394f97328e6427cd9fb9 | |
| 13:34:35 | sean-k-mooney | which is why i was surprised we were using them | |
| 13:34:35 | sean-k-mooney | which is why i was surprised we were using them | |
| 13:36:17 | sean-k-mooney | if it was not for the fact that we cant remove standard resouce class i woudl be very tempeted to treat this a a bug and change them | |
| 13:36:18 | sean-k-mooney | if it was not for the fact that we cant remove standard resouce class i woudl be very tempeted to treat this a a bug and change them | |
| 13:36:44 | sean-k-mooney | but reshaps are way to expensive to waste it on something as trivial as this | |
| 13:36:44 | sean-k-mooney | but reshaps are way to expensive to waste it on something as trivial as this | |
| 13:39:25 | sean-k-mooney | sigh ... https://review.opendev.org/c/openstack/nova/+/570847/10/nova/rc_fields.py#45 | |
| 13:39:26 | sean-k-mooney | sigh ... https://review.opendev.org/c/openstack/nova/+/570847/10/nova/rc_fields.py#45 | |
| 13:39:32 | sean-k-mooney | so that how that happend | |
| 13:39:32 | sean-k-mooney | so that how that happend | |
| 13:40:32 | sean-k-mooney | gibi: unless you 100% agaisnt the long names i would prefer to use ingress and egress expanded but its not like im going to block on that point | |
| 13:40:32 | sean-k-mooney | gibi: unless you 100% agaisnt the long names i would prefer to use ingress and egress expanded but its not like im going to block on that point | |
| 13:50:01 | gibi | sean-k-mooney: I really don't want to change the bandwidth naming, lets accept that as history. a well discussed history as we see from the original review | |
| 13:50:01 | gibi | sean-k-mooney: I really don't want to change the bandwidth naming, lets accept that as history. a well discussed history as we see from the original review | |
| 13:50:08 | gibi | sean-k-mooney: I'm not against long names | |
| 13:50:08 | gibi | sean-k-mooney: I'm not against long names | |
| 13:50:51 | gibi | it will be weird when the bw and the pps resources next to each outher in a resource_request has different spelling | |
| 13:50:51 | gibi | it will be weird when the bw and the pps resources next to each outher in a resource_request has different spelling | |
| 13:51:50 | sean-k-mooney | i dont agree that it was well disucsed since it did not happen in the spec. but yes i accetp we cant change it for bandwith | |
| 13:51:50 | sean-k-mooney | i dont agree that it was well disucsed since it did not happen in the spec. but yes i accetp we cant change it for bandwith | |
| 13:54:47 | gibi | fine, I can change the name :) maybe we wil re-discuss it in the os-resource-classes review :) | |
| 13:54:47 | gibi | fine, I can change the name :) maybe we wil re-discuss it in the os-resource-classes review :) | |
| 13:54:59 | gibi | I will spell out egress and ingress | |
| 13:54:59 | gibi | I will spell out egress and ingress | |
| 13:55:18 | gibi | I don't want to get hung up on that. | |
| 13:55:18 | gibi | I don't want to get hung up on that. | |
| 13:55:22 | gibi | it is just a name | |
| 13:55:22 | gibi | it is just a name | |
| 13:55:33 | sean-k-mooney | well i was actully going to abstain form the name | |
| 13:55:34 | sean-k-mooney | well i was actully going to abstain form the name | |
| 13:55:43 | sean-k-mooney | pass my last comment | |
| 13:55:43 | sean-k-mooney | pass my last comment | |
| 13:56:07 | sean-k-mooney | if we can agree with the rest of the spec we could keep it as written | |
| 13:56:07 | sean-k-mooney | if we can agree with the rest of the spec we could keep it as written | |
| 13:56:30 | sean-k-mooney | just wanted to exprss my frustration at yet another case wehre part of the agreee api were changed at the implation time | |
| 13:56:30 | sean-k-mooney | just wanted to exprss my frustration at yet another case wehre part of the agreee api were changed at the implation time | |
| 13:56:40 | sean-k-mooney | im ok with implation detail chagne during code review | |
| 13:56:41 | sean-k-mooney | im ok with implation detail chagne during code review | |
| 13:56:59 | sean-k-mooney | i stongly dislike change any public aspect of the feature in code review | |
| 13:56:59 | sean-k-mooney | i stongly dislike change any public aspect of the feature in code review | |
| 13:57:03 | sean-k-mooney | which this way | |
| 13:57:03 | sean-k-mooney | which this way | |
| 13:57:06 | sean-k-mooney | *was | |
| 13:57:06 | sean-k-mooney | *was | |
| 13:57:42 | gibi | sean-k-mooney: based on the os-resource-classes review if that would happen in a spec it would have been approved by the same set of cores anyhow | |
| 13:57:42 | gibi | sean-k-mooney: based on the os-resource-classes review if that would happen in a spec it would have been approved by the same set of cores anyhow | |
| 13:58:24 | sean-k-mooney | * sean-k-mooney regrest that i had to proxy my inovlvment in this through others and was not directly invovle din the review a the time | |
| 13:59:20 | gibi | sean-k-mooney: don't feel bad about it, it just a name, we have soo many names to decide on in the future | |
| 13:59:20 | gibi | sean-k-mooney: don't feel bad about it, it just a name, we have soo many names to decide on in the future | |
| 13:59:29 | sean-k-mooney | lol :) | |
| 13:59:29 | sean-k-mooney | lol :) | |
| 13:59:33 | gibi | :) | |
| 14:00:34 | sean-k-mooney | gibi: well min bandwidth just feels a little more personal since i first discussed it with you after the briton mid cycle when you visited intel shannon | |
| 14:00:34 | sean-k-mooney | gibi: well min bandwidth just feels a little more personal since i first discussed it with you after the briton mid cycle when you visited intel shannon | |
| 14:01:41 | sean-k-mooney | and i tired to follow the implemation later via other at a high level but i tought we were still using the name in the orginal spec | |
| 14:01:41 | sean-k-mooney | and i tired to follow the implemation later via other at a high level but i tought we were still using the name in the orginal spec | |
| 14:01:52 | sean-k-mooney | anyway are you going to push an updates spec soon | |
| 14:01:52 | sean-k-mooney | anyway are you going to push an updates spec soon | |
| 14:02:02 | gibi | old times | |
| 14:02:02 | gibi | old times | |
| 14:02:04 | sean-k-mooney | with the other poitn address or should i re review the current version | |
| 14:02:05 | sean-k-mooney | with the other poitn address or should i re review the current version | |
| 14:02:15 | gibi | just read the current version | |
| 14:02:15 | gibi | just read the current version | |
| 14:02:28 | sean-k-mooney | ok will do | |
| 14:02:28 | sean-k-mooney | ok will do | |
| 14:02:31 | gibi | I will wait bauzas to check back about the OVS RP question | |
| 14:02:31 | gibi | I will wait bauzas to check back about the OVS RP question | |