Earlier  
Posted Nick Remark
#openstack-nova - 2018-12-06
18:07:12 lyarwood but that's a bug right? The source compute being offline should fail the attempt right there?
18:07:24 dansmith well,
18:07:37 dansmith you could argue that for sure
18:08:58 lyarwood k, this is from a downstream bug report where a user has tried to migrate instead of evacuate from an offline compute and the instance gets stuck in resize_prep etc.
18:20:39 openstackgerrit Jack Ding proposed openstack/nova master: [WIP] Preserve UEFI NVRAM variable store https://review.openstack.org/621646
18:21:18 spatel sean-k-mooney: afternoon
18:21:32 sean-k-mooney o/
18:22:02 spatel sean-k-mooney: i had question related horizon dashboard Overview section, its saying Active instance: 367
18:22:20 sean-k-mooney yep
18:22:23 spatel but when i run "nova list" its saying you have 280 instance total
18:22:36 spatel where that 367 came from?
18:22:51 sean-k-mooney that is a good question
18:23:05 sean-k-mooney i belive it hitting the simple teant usage api
18:23:11 spatel does it counting deleted instance too?
18:23:24 sean-k-mooney so it is proably showing the total number of instaces that were launched
18:23:49 sean-k-mooney let me take a look a dashboard for a sec
18:24:15 spatel ok
18:26:04 sean-k-mooney so i just opend my local hoizon you are lokking at the overview seaction in the project section or admin
18:26:53 sean-k-mooney in the project page it should just show the active instance not deleted
18:31:19 sean-k-mooney spatel: you could run "openstack usage list" or openstack usage show --project <your project> and see if that say 367
18:32:17 sean-k-mooney spatel: i do not have a version of horizon that has teh simple teant usage api support turned on so i just see the dashboard that show the currently active instances
18:35:11 spatel hold on doing it
18:36:19 spatel sean-k-mooney: http://paste.openstack.org/show/736782/
18:36:29 spatel here you go
18:36:57 sean-k-mooney so you were looking at the overview in the admin section
18:37:30 sean-k-mooney well maybe not
18:37:56 sean-k-mooney 314 != 367
18:40:54 openstackgerrit Dan Smith proposed openstack/nova master: Only warn about not having computes nodes once in rpcapi https://review.openstack.org/623282
18:40:55 openstackgerrit Dan Smith proposed openstack/nova master: Make compute rpcapi version calculation check all cells https://review.openstack.org/623284
18:40:55 openstackgerrit Dan Smith proposed openstack/nova master: Make service.get_minimum_version_all_cells() cache the results https://review.openstack.org/623283
18:40:56 dansmith mriedem: ^
18:41:34 dansmith mriedem: hopefully we can see the difference in just the logging, and measure the impact of the all-cells change
18:42:56 sean-k-mooney spatel: how many running vms does "openstack hypervisor stats show -c running_vms -f value" return
18:43:23 spatel running
18:45:35 sean-k-mooney ok so that is what you were exepcting
18:45:41 sean-k-mooney it should match "openstack server list -f value -c ID | wc -l"
18:45:57 sean-k-mooney but horizon is saying 367
18:46:31 sean-k-mooney it should match "openstack server list -f value -c ID | wc -l"
18:46:34 spatel I have two project so i need to run that command in specific project
18:46:51 spatel admin not giving me any data when i run "openstack server list -f value -c ID | wc -l"
18:47:05 sean-k-mooney am use this one instead "openstack server list -f value -c ID --all-projects | wc -l"
18:47:45 spatel across all project output is "287"
18:47:55 spatel when i run this "openstack server list -f value -c ID --all-projects | wc -l"
18:48:08 sean-k-mooney ok so that will inclode shelved or error state vms
18:48:20 spatel possible some machine are shutdown or error stat ...
18:48:35 sean-k-mooney its clode enought to the running vms for hypervior state that i would get horizon may be wrone
18:49:17 sean-k-mooney openstack server list would include all vm except deleted instances i think by default
18:49:47 spatel but 367 which horizon claiming is way way out..
18:50:14 sean-k-mooney yes it is
18:50:23 sean-k-mooney i honetly dont know why
18:50:31 spatel i assume its counting delete and other state also...
18:50:37 spatel I will open BUG :)
18:50:44 spatel lets see what other people chime in
18:50:47 sean-k-mooney spatel: it should not include deleted
18:50:56 spatel that is what i am thinking
18:51:24 sean-k-mooney out of interest what is the resulted of "openstack server list -f value -c ID --deleted --all-projects | wc -l"
18:51:38 sean-k-mooney is it around 80 ish?
18:53:39 mriedem dansmith: ack, we might get results by eod
18:53:47 dansmith mriedem: aye
18:54:07 dansmith mriedem: I just -1ed your placement client thing because I'm an ass, but I will make the change for you if you want
18:54:13 dansmith to make myself feel better
18:54:21 mriedem what assery is this
18:54:35 spatel sean-k-mooney: ^^
18:54:46 spatel i am confused now :(
18:55:36 openstack Launchpad bug 1807251 in OpenStack Dashboard (Horizon) "Horizon Overview summary showing wrong numbers " [Undecided,New]
18:55:36 spatel Here i file bug https://bugs.launchpad.net/horizon/+bug/1807251
18:55:56 cdent I imagine there is.a super upper ontology of assery
18:58:52 sean-k-mooney spatel: that is strange
18:59:16 spatel definitely bug or may be some DB cleanup stuff?
18:59:17 sean-k-mooney even teh other things like cpu hours are way out
18:59:27 spatel exactly
19:00:02 sean-k-mooney are they showing the same time period
19:00:03 sean-k-mooney 2018-11-08 to 2018-12-07
19:01:05 sean-k-mooney it looks like the cli is defaulting to the last month but maybe horizon has a differnt default
19:01:13 spatel on Horizon dates are default set to 2018-12-05 to 2018-12-06
19:01:21 spatel 24 hours period
19:01:43 sean-k-mooney that does not explain how horrizon is showing more usage
19:01:53 sean-k-mooney in fact it makes it less likely..
19:02:29 spatel hmm
19:02:35 sean-k-mooney so ya sorry i cant really help more then that
19:06:00 spatel don't worry it was good help to understand that i am not crazy...
19:06:19 spatel i thought i didn't understand or missing something but after you confirm it seems bug
19:06:26 spatel anyway i have opened ticket so lets see
19:07:32 cfriesen sean-k-mooney: do you know if anyone has ever looked at setting IRQ affinity for PCI devices? (would only really make sense for the "dedicated" case)
19:07:52 sean-k-mooney i did like 4 years ago
19:08:28 sean-k-mooney thre are two field of tought on this either user irq blanace or whatever to afinities all irq away form the cores used by vms
19:09:00 cfriesen sean-k-mooney: I'm talking about for PCI-passthrough, setting the affinity to the pCPUs used by the guest
19:09:02 sean-k-mooney or dynamicaly affinities irqs for a vf to the vm cpus
19:10:19 sean-k-mooney ya i was asked to make that change a few years ago and got push back rom redhat folks on the libvirt team.
19:10:26 sean-k-mooney let me see if i can find that.
19:21:18 sean-k-mooney hum i must have been an intel only bug which aparently i cant see
19:28:02 openstack sean-k-mooney: Error: Error getting bugzilla.redhat.com bug #1135668: NotPermitted
19:28:02 sean-k-mooney cfriesen: i assume you cant see https://bugzilla.redhat.com/show_bug.cgi?id=1135668
19:29:10 cfriesen sean-k-mooney: nope. :)
19:29:17 sean-k-mooney cfriesen: when we rant this by the libvirt people they were concerned that affinities the interups to the vm cores could cause alot of guest VM_exits to serivce the interupts
19:29:52 cfriesen sean-k-mooney: enough to outweigh the preloading of the cache?
19:30:39 openstackgerrit Matt Riedemann proposed openstack/nova master: DRY up SchedulerReportClient init https://review.openstack.org/623247
19:30:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Only construct SchedulerReportClient on first access from API https://review.openstack.org/623246
19:31:35 sean-k-mooney so this was created on 2014-08-29 so my memory is a little fuzzy but they wanted use to show that it would out way that overhead and at the time we did not have the capsity to test it in an openstack environmnt to messuer it
19:31:55 sean-k-mooney so it was drop becasue of lack of evidence to show ti was a usefull feature to add to libvirt

Earlier   Later