Earlier  
Posted Nick Remark
#openstack-nova - 2019-05-14
21:50:23 efried I know, try to do a nice thing...
22:48:30 openstackgerrit Eric Fried proposed openstack/nova master: WIP: TC Vision Reflection https://review.opendev.org/658932
22:48:57 efried A little more every day
22:49:35 efried maybe by meeting time I'll have enough for folks to start ripping apart
#openstack-nova - 2019-05-15
01:54:19 openstackgerrit Boxiang Zhu proposed openstack/nova master: Fix failure to boot instances with qcow2 format images https://review.opendev.org/640271
02:05:45 openstackgerrit Merged openstack/nova master: Add zvm driver image type capabilities https://review.opendev.org/655732
02:26:42 openstackgerrit Brin Zhang proposed openstack/nova master: Cap sphinx for py2 to match global requirements https://review.opendev.org/659201
02:30:18 openstackgerrit Brin Zhang proposed openstack/python-novaclient master: Cap sphinx for py2 to match global requirements https://review.opendev.org/659202
02:35:34 openstackgerrit Merged openstack/nova master: Disable limit if affinity(anti)/same(different)host is requested https://review.opendev.org/658110
02:44:17 openstackgerrit Brin Zhang proposed openstack/nova-specs master: Cap sphinx for py2 to match global requirements https://review.opendev.org/659205
02:46:51 openstackgerrit Tetsuro Nakamura proposed openstack/nova stable/stein: Skip _exclude_nested_providers() if not nested https://review.opendev.org/659206
02:51:00 openstackgerrit Tetsuro Nakamura proposed openstack/nova stable/rocky: Skip _exclude_nested_providers() if not nested https://review.opendev.org/659207
02:58:30 openstackgerrit Boxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server https://review.opendev.org/645520
03:43:36 openstackgerrit Brin Zhang proposed openstack/python-novaclient master: Cap sphinx for py2 to match global requirements https://review.opendev.org/659202
07:06:15 openstackgerrit Brin Zhang proposed openstack/python-novaclient master: Cap sphinx for py2 to match global requirements https://review.opendev.org/659202
08:08:36 sean-k-mooney bauzas: have you seen http://logs.openstack.org/97/652197/17/check/grenade-py3/7b3cac4/logs/grenade.sh.txt.gz#_2019-05-15_02_34_39_701 recently
08:08:52 sean-k-mooney im not sure if our grenade job is broken after the change to os-dev
08:08:59 sean-k-mooney *opendev
08:19:03 sean-k-mooney ya... 337 hits in the last 12 hours http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Could%20not%20install%20packages%20due%20to%20an%20EnvironmentError:%20HTTPSConnectionPool(host%3D'git.openstack.org',%20port%3D443)%5C%22
08:23:46 bauzas sean-k-mooney: nope, not yet
08:25:22 bauzas sean-k-mooney: there is a redirect for https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt
08:25:31 sean-k-mooney http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Could%20not%20install%20packages%20due%20to%20an%20EnvironmentError:%20HTTPSConnectionPool(host%3D'git.openstack.org',%20port%3D443)%5C%22
08:25:35 bauzas sean-k-mooney: so we shouldn't get the exception
08:26:05 sean-k-mooney bauzas: we should not but there have been 337 filures since in the last week
08:26:13 sean-k-mooney so i think its not always working
08:26:20 sean-k-mooney i just mention this on the infra channel
08:26:36 bauzas ok
08:26:41 sean-k-mooney i might create an elastic recheck query and file a bug but im not sure where to file it
08:27:00 bauzas good question
08:27:19 bauzas we used to create bugs in Nova even if they were related to infra
08:27:28 bauzas and we marked them as critical
08:27:48 bauzas we also had a tag for them
08:28:13 sean-k-mooney ok i can do that. its affecting neutron jobs too but the grenade jobs seam to be the onse teh hit it most
08:28:22 bauzas sean-k-mooney: https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure
08:29:20 sean-k-mooney ah cool ill file one and add the gate-failure tag
08:48:38 openstackgerrit Surya Seetharaman proposed openstack/nova stable/stein: Disable limit if affinity(anti)/same(different)host is requested https://review.opendev.org/659239
08:49:04 sean-k-mooney bauzas: should i set it to critical by the way or just high. i have hit it twice in a row but i dont think its failing in all builds its just annoying
08:49:18 bauzas sean-k-mooney: on 1:1, sorry
08:49:28 sean-k-mooney no worries
08:58:55 openstackgerrit Alex Xu proposed openstack/nova master: Remove the request_destination check in the scheduler https://review.opendev.org/659243
08:59:57 alex_xu ^ efried, is it something we can removed?
09:02:53 bhagyashris efried, bauzas: Hi, I just want to discuss about http://logs.openstack.org/81/555081/28/check/openstack-tox-docs/6314f69/html/specs/train/approved/cpu-resources.html#configuration-options regarding the reserved_host_cpu calculation for PCPU resource,
09:03:02 bhagyashris f I have total 16 cpus and 4 are assigned to cpu_dedicated_set and 2 are assign to cpu_shared_set then in that case reserved_cpus for PCPU resource class will be (16- (4+2)) = 10 and for VCPU resource class it will be 0 .
09:03:09 bhagyashris Then in that case if I request instance which requires 1 PCPU then placement returns the 0 allocation_candiacted () (reason is it fails at _capacity_check_clause())
09:03:58 bhagyashris Please correct me if I am wrong while calculating the reserved host cpu.
09:04:41 kashyap sean-k-mooney: dansmith: Yesterday you said: just like how you don't want Nova to not land instances based on "fan speed, or cpu temperature, or firmware patch levels..." you also don't want to stop launching instances on Compute hosts with vulnerable hypervisors.
09:04:43 openstackgerrit Surya Seetharaman proposed openstack/nova stable/rocky: Disable limit if affinity(anti)/same(different)host is requested https://review.opendev.org/659246
09:05:24 kashyap sean-k-mooney: dansmith: Fan speed & CPU temp are really different, as they don't really affect the guest.
09:07:26 bhagyashris sean-k-mooney: ^^
09:08:19 openstackgerrit Surya Seetharaman proposed openstack/nova stable/queens: Disable limit if affinity(anti)/same(different)host is requested https://review.opendev.org/659247
09:23:49 sean-k-mooney bhagyashris: no
09:24:26 sean-k-mooney if you have 4 cpus in cpu_dedicated_set then that capasity of the inventory will b 4 and the resrved value will be 0
09:25:30 sean-k-mooney similarly for vcpus the capasity will be defiened by the total number of cores defiened in the cpu_shared_set
09:25:56 sean-k-mooney bhagyashris: so the reserved value will effectivly always be 0 unless you set it to something else via the api
09:26:36 bhagyashris sean-k-mooney: How? but What formula says (set(all_cpus) - (set(dedicated) - set(shared)))
09:27:07 sean-k-mooney that is not waht the current version fo the spec say if i rememeber correctly
09:27:19 bhagyashris So in my case the total cpu count on host is 16 and I have define dedicated set as 4 cpus and shared as 2 cpus
09:27:47 bhagyashris Ok then in my case what will be the all_cpus value
09:27:50 sean-k-mooney then the inventory will be PCUP total 4 reserved 0
09:27:56 sean-k-mooney no
09:28:13 sean-k-mooney we will only be reporting the consumable cpus to placement
09:28:19 sean-k-mooney not all the cpus on the plathform
09:28:25 bhagyashris ok
09:29:08 sean-k-mooney let me just double check the spec to ensure that is correct but i belive that is what we settled on
09:29:36 bhagyashris ok check and let me help to understand
09:30:07 bhagyashris Sorry help me to understand
09:30:12 sean-k-mooney looks like that has not been updated yet https://review.opendev.org/#/c/555081/28/specs/train/approved/cpu-resources.rst@201
09:30:37 sean-k-mooney ill leave a comment
09:30:54 sean-k-mooney stephenfin: ^ is the above correct
09:31:55 bhagyashris I am still confuse what will be the all_cpus value
09:32:12 sean-k-mooney there wont be one
09:32:35 bhagyashris if you check the Upgrade section there they have mentioned the formula
09:32:38 sean-k-mooney at least i dont think there shoudl be
09:32:53 bhagyashris To calculate the reserved hot
09:32:59 bhagyashris Host cpu*
09:33:24 sean-k-mooney that is not present in the current verion as far as i can see
09:34:12 bhagyashris http://logs.openstack.org/81/555081/28/check/openstack-tox-docs/6314f69/html/specs/train/approved/cpu-resources.html#configuration-options
09:34:19 bhagyashris Here they have mentioned
09:35:51 bhagyashris sean-k-mooney: ^^
09:36:11 sean-k-mooney ya i think that is in correct. this was one of the part of the spec that i really disliked but we still need to get agreement on that
09:36:54 bhagyashris Yeah and there I am still unclear what will be the all_cpus value
09:37:08 sean-k-mooney i am suggstion there should not be one
09:37:40 sean-k-mooney i think it is incorrect to track cpus that cant be consumed in placement
09:37:58 sean-k-mooney it give an incorrect assement of your capastity
09:39:59 bhagyashris yeah
09:41:13 bhagyashris Then how will calculate the reserved value
09:41:35 sean-k-mooney we dont we always set it to 0 when creting the rp
09:42:48 bhagyashris Okay mean for both the PCPU and VCPU resource class inventory it will be 0
09:42:55 sean-k-mooney yes
09:43:08 bhagyashris But didn't get why this is added in spec
09:43:11 sean-k-mooney that is not what the spec says but i think we shoudl updated it to say that
09:43:29 bhagyashris As I am implementing the spec so it's till bit confusing to me
09:43:58 sean-k-mooney well we have changed the design a bit form last cycle
09:44:18 sean-k-mooney this was one of the point that there was still some disagrement on
09:45:01 bhagyashris Ohh ok.
09:46:05 bhagyashris stephenfin: Hi, do you give me some suggestion and opinion about it
09:46:25 sean-k-mooney i think the UX of what was prosped in the spec is incrroect and i fully expect to get bug report because of it which is why i wanted to change it
09:46:34 bhagyashris Regarding the reserved_host_cpu calculation
09:47:50 bhagyashris sean-k-mooney: Yeah , still waiting for final decision how will be the reserved value for cpus
09:47:59 stephenfin sean-k-mooney: Yeah, that's a mistake that should be updated

Earlier   Later