Earlier  
Posted Nick Remark
#openstack-nova - 2021-05-12
10:18:03 sean-k-mooney the release contiang the default change patch would have to be a major version bump
10:18:23 sean-k-mooney having the ablity to auto negociate is not a breaking change turning it on by default is
10:18:23 sean-k-mooney having the ablity to auto negociate is not a breaking change turning it on by default is
10:21:33 sean-k-mooney gibi: stephenfin if ye want to not revert and you make sure the next version of osc is a major version then i could proably live with that but i still think min required would be better that said i would like thinks like flavor validation to be on by default
10:21:33 sean-k-mooney gibi: stephenfin if ye want to not revert and you make sure the next version of osc is a major version then i could proably live with that but i still think min required would be better that said i would like thinks like flavor validation to be on by default
10:22:05 stephenfin this only affects osc-placement, not osc btw
10:22:05 stephenfin this only affects osc-placement, not osc btw
10:22:19 gibi * gibi lunches 
10:22:27 sean-k-mooney oh it does?
10:22:27 sean-k-mooney oh it does?
10:22:44 sean-k-mooney i tought it was all of osc
10:22:44 sean-k-mooney i tought it was all of osc
10:23:06 stephenfin no. That's happening but separately. The change above was just for osc-placement
10:23:06 stephenfin no. That's happening but separately. The change above was just for osc-placement
10:23:46 sean-k-mooney i still woudl prefer auto negociating the min reqruied not latest but maybe i have to just live with it being unstable
10:23:46 sean-k-mooney i still woudl prefer auto negociating the min reqruied not latest but maybe i have to just live with it being unstable
10:24:08 sean-k-mooney i rarely have need to script against osc so maybe it not worth avocating for those that do
10:24:08 sean-k-mooney i rarely have need to script against osc so maybe it not worth avocating for those that do
10:24:33 stephenfin tbf, those users could simply request an explicit base version manually
10:24:33 stephenfin tbf, those users could simply request an explicit base version manually
10:24:48 stephenfin '--os-compute-api-version 2.1' or whatever
10:24:48 stephenfin '--os-compute-api-version 2.1' or whatever
10:24:50 sean-k-mooney i just dont want verizon complaining that they cant create flavor when the insitent on setting hw:numa_mem_policy that does not exist
10:24:50 sean-k-mooney i just dont want verizon complaining that they cant create flavor when the insitent on setting hw:numa_mem_policy that does not exist
10:26:23 sean-k-mooney stephenfin: ya i know but many dont know what microverions are or care they just want the command they always used to work
10:26:23 sean-k-mooney stephenfin: ya i know but many dont know what microverions are or care they just want the command they always used to work
10:27:27 sean-k-mooney stephenfin: gibi if the desisin to move all of osc to latest has aleready been made then dont revert the placment patch
10:27:27 sean-k-mooney stephenfin: gibi if the desisin to move all of osc to latest has aleready been made then dont revert the placment patch
10:29:39 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Enable 'vmcoreinfo' feature by default https://review.opendev.org/c/openstack/nova/+/752912
10:29:40 openstackgerrit Stephen Finucane proposed openstack/nova master: tests: Remove 'create_fake_libvirt_mock' https://review.opendev.org/c/openstack/nova/+/790945
10:29:40 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Make vmcoreinfo dependent on feature flag https://review.opendev.org/c/openstack/nova/+/779342
10:29:41 openstackgerrit Stephen Finucane proposed openstack/nova master: WIP: libvirt: Make vmcoreinfo checks guest arch specific https://review.opendev.org/c/openstack/nova/+/790946
10:33:57 gibi sean-k-mooney: OK, then I won't revert.
10:33:57 gibi sean-k-mooney: OK, then I won't revert.
10:34:10 gibi I honestly don't know what will be the overall osc policy
10:34:10 gibi I honestly don't know what will be the overall osc policy
10:35:16 sean-k-mooney gibi: right now i really dont like that its different per command
10:35:16 sean-k-mooney gibi: right now i really dont like that its different per command
10:35:27 sean-k-mooney as it make it much harder to use
10:35:27 sean-k-mooney as it make it much harder to use
10:36:09 sean-k-mooney that said i know ironic broke the consitency years ago so its not a new thing
10:36:09 sean-k-mooney that said i know ironic broke the consitency years ago so its not a new thing
10:36:10 gibi I think it is the same for each call . max(server,client)
10:36:10 gibi I think it is the same for each call . max(server,client)
10:36:35 sean-k-mooney gibi: not i mean nova and cinder command wont auto negociate
10:36:35 sean-k-mooney gibi: not i mean nova and cinder command wont auto negociate
10:36:41 sean-k-mooney but ironic and plamcent will
10:36:41 sean-k-mooney but ironic and plamcent will
10:36:47 gibi I see
10:36:47 gibi I see
10:37:04 gibi but if the overall osc change is coming the it will be in sync again
10:37:04 gibi but if the overall osc change is coming the it will be in sync again
10:37:26 sean-k-mooney yes if but there was never a cross project agreement to do that as far as i knew
10:37:26 sean-k-mooney yes if but there was never a cross project agreement to do that as far as i knew
10:37:52 sean-k-mooney but if its happeing then i just hope it gets done this cycle
10:37:52 sean-k-mooney but if its happeing then i just hope it gets done this cycle
10:38:07 sean-k-mooney draging it out over multiple cycle will not be a good ux
10:38:07 sean-k-mooney draging it out over multiple cycle will not be a good ux
10:38:39 sean-k-mooney which is why i was expecting this type of change to be a cross project goal
10:38:39 sean-k-mooney which is why i was expecting this type of change to be a cross project goal
10:38:40 gibi OK, then please propose a revert on the osc patch and lets bring it up on cross project levels
10:38:40 gibi OK, then please propose a revert on the osc patch and lets bring it up on cross project levels
10:39:04 stephenfin I don't think this is a serious issue
10:39:04 stephenfin I don't think this is a serious issue
10:39:16 stephenfin If people don't like it, then they'll let us know
10:39:16 stephenfin If people don't like it, then they'll let us know
10:39:18 gibi It seems it is serious for sean-k-mooney
10:39:18 gibi It seems it is serious for sean-k-mooney
10:39:29 stephenfin Otherwise 🤷
10:39:29 stephenfin Otherwise 🤷
10:41:29 jrosser if i put debug=True in [DEFAULT] of nova.conf (for example) should that be sufficient to then be able to see https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L608-L610 in the nova-conductor log file?
10:41:29 jrosser if i put debug=True in [DEFAULT] of nova.conf (for example) should that be sufficient to then be able to see https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L608-L610 in the nova-conductor log file?
10:41:37 sean-k-mooney i just dont want to have to explain in our downstream doc and to customer why openstack server create and openstack resource provider list work differently
10:41:37 sean-k-mooney i just dont want to have to explain in our downstream doc and to customer why openstack server create and openstack resource provider list work differently
10:42:24 sean-k-mooney jrosser: am im not sure i thought that was only for the nova log level
10:42:24 sean-k-mooney jrosser: am im not sure i thought that was only for the nova log level
10:42:36 sean-k-mooney but maybe its everything
10:42:36 sean-k-mooney but maybe its everything
10:43:05 jrosser sean-k-mooney: yeah, i'm not seeing those and am struggling to find how to enable oslo.messaging debug in the context of a nova service
10:43:05 jrosser sean-k-mooney: yeah, i'm not seeing those and am struggling to find how to enable oslo.messaging debug in the context of a nova service
10:44:24 gibi jrosser: I think you need this config https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.default_log_levels
10:44:24 gibi jrosser: I think you need this config https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.default_log_levels
10:44:46 gibi there the oslo.messaging is set to INFO by default
10:44:46 gibi there the oslo.messaging is set to INFO by default
10:44:51 gibi so you have to change that
10:44:51 gibi so you have to change that
10:45:01 jrosser ah! let me try that
10:45:01 jrosser ah! let me try that
11:18:45 ignaziocassano1 ralonsoh looking at this bug https://bugzilla.redhat.com/show_bug.cgi?id=1917675 seems redhat released patches only for rhel8 ....so Think for centos8
11:18:46 openstack bugzilla.redhat.com bug 1917675 in openstack-nova "Nova evacuate fails due to timeout waiting for a network-vif-plugged event for instance" [Urgent,On_qa] - Assigned to smooney
11:18:46 openstack bugzilla.redhat.com bug 1917675 in openstack-nova "Nova evacuate fails due to timeout waiting for a network-vif-plugged event for instance" [Urgent,On_qa] - Assigned to smooney
11:18:46 ignaziocassano1 ralonsoh looking at this bug https://bugzilla.redhat.com/show_bug.cgi?id=1917675 seems redhat released patches only for rhel8 ....so Think for centos8
11:19:19 ignaziocassano1 I am using centos7
11:19:19 ignaziocassano1 I am using centos7
11:20:02 sean-k-mooney you are using packages from RDO not form Redhat
11:20:02 sean-k-mooney you are using packages from RDO not form Redhat
11:20:31 sean-k-mooney ignaziocassano1: and RDO support train on 7 and 8
11:20:31 sean-k-mooney ignaziocassano1: and RDO support train on 7 and 8
11:21:05 ignaziocassano1 Yes, I wonder if they will be' released on rdo for centos 7
11:21:07 ignaziocassano1 Yes, I wonder if they will be' released on rdo for centos 7

Earlier   Later