Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-07-05
22:03:10 sean-k-mooney so we will not allow vms that request more ram then the host has to be schduled to a node
22:03:19 sean-k-mooney the same is true from ram and disk
22:03:54 sean-k-mooney i havent read the full scrollback but that is the first limitation that came to mind
22:05:09 sean-k-mooney reading back
22:05:22 sean-k-mooney we reserve 512MB of ram for the host by default
22:08:04 openstackgerrit Matt Riedemann proposed openstack/nova master: Refresh instance in MigrationTask.execute Exception handler https://review.opendev.org/669012
22:08:04 openstackgerrit Matt Riedemann proposed openstack/nova master: Add negative test for cross-cell finish_resize failing https://review.opendev.org/643451
22:08:05 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Add confirm_snapshot_based_resize_at_source https://review.opendev.org/637058
22:08:05 openstackgerrit Matt Riedemann proposed openstack/nova master: Add negative test for prep_snapshot_based_resize_at_source failing https://review.opendev.org/669013
22:08:06 openstackgerrit Matt Riedemann proposed openstack/nova master: Add confirm_snapshot_based_resize conductor RPC method https://review.opendev.org/637075
22:08:06 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Add ConfirmResizeTask https://review.opendev.org/637070
22:08:07 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Add revert_snapshot_based_resize_at_dest compute method https://review.opendev.org/637630
22:08:07 openstackgerrit Matt Riedemann proposed openstack/nova master: Confirm cross-cell resize from the API https://review.opendev.org/637316
22:08:08 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Add finish_revert_snapshot_based_resize_at_source compute method https://review.opendev.org/637647
22:08:08 openstackgerrit Matt Riedemann proposed openstack/nova master: Deal with cross-cell resize in _remove_deleted_instances_allocations https://review.opendev.org/639453
22:08:09 openstackgerrit Matt Riedemann proposed openstack/nova master: Add revert_snapshot_based_resize conductor RPC method https://review.opendev.org/638047
22:08:09 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Add RevertResizeTask https://review.opendev.org/638046
22:08:10 openstackgerrit Matt Riedemann proposed openstack/nova master: Confirm cross-cell resize while deleting a server https://review.opendev.org/638268
22:08:10 openstackgerrit Matt Riedemann proposed openstack/nova master: Revert cross-cell resize from the API https://review.opendev.org/638048
22:08:11 openstackgerrit Matt Riedemann proposed openstack/nova master: Add CrossCellWeigher https://review.opendev.org/614353
22:08:11 openstackgerrit Matt Riedemann proposed openstack/nova master: Add archive_deleted_rows wrinkle to cross-cell functional test https://review.opendev.org/651650
22:08:12 openstackgerrit Matt Riedemann proposed openstack/nova master: Support cross-cell moves in external_instance_event https://review.opendev.org/658478
22:08:12 openstackgerrit Matt Riedemann proposed openstack/nova master: Add functional test for anti-affinity cross-cell migration https://review.opendev.org/661859
22:10:32 Nick_A sean-k-mooney thanks
22:11:53 sean-k-mooney i would have to think about it some more but im guessing you are hiting one of the limit we have to make sure a single vm does not exceed the total amount of one of the resouce we have on the host
22:30:06 Nick_A yeah that's clearly why 32768 wasn't working. We were just surprised it had a limit of that sort when the RAM allocated to multiple smaller instances could still cross that threshold.
22:36:17 sean-k-mooney i think the qemu error is proably a similar similar safte check
22:37:25 sean-k-mooney the os and qemu both need some ram to work properly. so there is some overhad per host that should not be allocated to a guest unless you have enough swap space
22:37:42 sean-k-mooney but even then i generally do not recommend ram over commit at all
22:38:40 sean-k-mooney it causes more issues the in sovles as the kernel OOM killer will reap the vms first if it need to allocate memory and it can swap the vm memory to make room
22:54:08 openstackgerrit Merged openstack/nova master: libvirt: Remove MIN_LIBVIRT_PERF_VERSION https://review.opendev.org/669128
23:00:14 openstackgerrit Merged openstack/nova master: libvirt: vif: Remove MIN_LIBVIRT_MACVTAP_PASSTHROUGH_VLAN https://review.opendev.org/669176
#openstack-nova - 2019-07-06
07:33:33 openstackgerrit garyk proposed openstack/nova master: Nova compute: add in log eception to help debug failures https://review.opendev.org/669545
#openstack-nova - 2019-07-07
00:05:16 openstack Launchpad bug 1835637 in OpenStack Compute (nova) "(404) NOT_FOUND - failed to perform operation on queue 'notifications.info' in vhost '/nova' due to timeout" [Undecided,New]
00:05:16 spatel sean-k-mooney: can you take a look here https://bugs.launchpad.net/nova/+bug/1835637
00:57:46 openstackgerrit Merged openstack/nova master: Set COMPUTE_STATUS_DISABLED trait from update_provider_tree flow https://review.opendev.org/668565
16:31:53 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Add test coverage of existing os-agents policies https://review.opendev.org/669578
22:05:59 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (13) https://review.opendev.org/576020
22:06:11 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (14) https://review.opendev.org/576027
22:06:25 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (15) https://review.opendev.org/576031
22:06:43 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (16) https://review.opendev.org/576299
22:06:59 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (17) https://review.opendev.org/576344
22:07:17 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (18) https://review.opendev.org/576673
22:07:34 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19) https://review.opendev.org/576676
22:07:52 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20) https://review.opendev.org/576689
22:08:10 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21) https://review.opendev.org/576709
22:08:30 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22) https://review.opendev.org/576712
22:08:51 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix cleaning up console tokens https://review.opendev.org/637716
#openstack-nova - 2019-07-08
00:39:20 openstackgerrit Sundar Nadathur proposed openstack/nova master: ksa auth conf and client for cyborg access https://review.opendev.org/631242
00:39:21 openstackgerrit Sundar Nadathur proposed openstack/nova master: WIP: Create and bind Cyborg ARQs. https://review.opendev.org/631244
00:39:21 openstackgerrit Sundar Nadathur proposed openstack/nova master: WIP: Add Cyborg device profile groups to request spec. https://review.opendev.org/631243
00:39:22 openstackgerrit Sundar Nadathur proposed openstack/nova master: WIP: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML. https://review.opendev.org/631245
02:35:09 openstackgerrit Yongli He proposed openstack/nova master: clean up orphan instances https://review.opendev.org/627765
03:28:50 openstackgerrit Boxiang Zhu proposed openstack/nova master: Support agile samples name https://review.opendev.org/669591
03:33:53 openstackgerrit Sundar Nadathur proposed openstack/nova master: ksa auth conf and client for cyborg access https://review.opendev.org/631242
03:33:54 openstackgerrit Sundar Nadathur proposed openstack/nova master: WIP: Create and bind Cyborg ARQs. https://review.opendev.org/631244
03:33:54 openstackgerrit Sundar Nadathur proposed openstack/nova master: WIP: Add Cyborg device profile groups to request spec. https://review.opendev.org/631243
03:33:55 openstackgerrit Sundar Nadathur proposed openstack/nova master: WIP: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML. https://review.opendev.org/631245
03:43:28 prometheanfire I'm guessing volumes showing up as attached in nova but not cinder (and not actually being attached) is a nova problem?
03:43:34 prometheanfire can't 'remove volume' it No volume with a name or ID of '3e92f9b6-1a3b-4a7e-8487-6ff253e888db' exists.
03:50:11 prometheanfire problem starts when attaching it, times out with a 504 :|
04:22:03 openstackgerrit Takashi NATSUME proposed openstack/python-novaclient master: Deprecate cells v1 and extension commands and APIs https://review.opendev.org/669597
06:16:30 openstackgerrit Arthur Dayne proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.opendev.org/623120
06:45:02 openstackgerrit Merged openstack/nova master: Clean up test_virtapi https://review.opendev.org/667419
07:20:44 openstackgerrit wangwei1 proposed openstack/nova master: fix spelling error in nova/api/validation/__init__.py https://review.opendev.org/669244
07:22:06 openstackgerrit Boxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server https://review.opendev.org/645520
08:41:22 openstackgerrit Merged openstack/nova master: Add VirtAPI.update_compute_provider_status https://review.opendev.org/668706
09:51:20 openstackgerrit Brin Zhang proposed openstack/nova master: Specify availability_zone to unshelve https://review.opendev.org/663851
09:57:49 openstackgerrit Miguel Ángel Herranz Trillo proposed openstack/nova stable/queens: Fix type error on call to mount device https://review.opendev.org/669629
10:16:06 moshele @sean-k-mooney: hi
10:37:25 gokhani hi team, because of power outage, Most of our compute nodes unexpectedly shut down and now I can not start our instances. Instances Power status is No State. Error log is http://paste.openstack.org/show/754107/. My environment is OpenStack Pike and Instances are on a nfs shared storage. Nova version is 16.1.6.dev2. There are more important instances on my environment. How can I rescue my istances? What would you suggest ?
11:19:25 openstackgerrit Ivaylo Mitev proposed openstack/nova master: VMware VMDK detach: get adapter type from instance VM https://review.opendev.org/653738
11:56:19 openstackgerrit Merged openstack/nova master: Correct the comment of RequestSpec's network_metadata https://review.opendev.org/667061
12:33:08 openstackgerrit Brin Zhang proposed openstack/nova master: Specify availability_zone to unshelve https://review.opendev.org/663851
12:35:24 openstackgerrit Shilpa Devharakar proposed openstack/nova master: Support filtering of hosts by forbidden aggregates https://review.opendev.org/667952
12:57:44 openstackgerrit Merged openstack/os-resource-classes master: Add Python 3 Train unit tests https://review.opendev.org/669479
13:00:04 openstackgerrit Merged openstack/os-traits master: Add Python 3 Train unit tests https://review.opendev.org/669480
13:25:41 openstackgerrit Matt Riedemann proposed openstack/nova stable/rocky: Fix type error on call to mount device https://review.opendev.org/669664
13:41:51 bauzas mriedem: around ?
13:42:01 bauzas mriedem: I replied to the thread but I wonder about something
13:42:06 mriedem yes
13:42:27 bauzas in both http://paste.openstack.org/show/734146/ and https://github.com/larsks/os-placement-tools/blob/master/check_placement.py they first ask about all the instances
13:42:55 bauzas and then they loop around allocations by checking some persisted object
13:43:05 bauzas but then, we could have some races
13:43:20 bauzas plus, it could be super huge to get all the instances for CERN eg.
13:43:36 bauzas so, I wonder whether I should call the API for every instance
13:43:49 bauzas erh
13:43:53 bauzas I mean, checking the DB
13:46:03 mriedem i'd think you'd avoid races by checking if an instance has a task_state != None, and if looking at migrations, is the migration in progress
13:48:09 mriedem mnaser's script doesn't loop over instances,
13:48:27 mriedem it gets hypervisors and the servers on those hypervisors and compares to the resource provider inventory/allocation per hypervisor/server
13:50:13 mriedem i'd think it would be easiest to first determine what kinds of problems the audit command is going to try and find
13:50:29 mriedem and then figure out the best way to implement that
13:51:08 mriedem i think we know the two main issues are missing allocations (which heal_allocations should fix) and leaked / orphaned allocations, so i'd start by focusing on the latter issue
13:55:17 mriedem i think we could pretty easily identify leaked allocations by starting from the provider allocations and working backward - looking for servers or migration records with the allocation consumer id (since we don't have the type recorded yet)
13:59:30 mriedem so i'd probably start by getting all hypervisors (nodes/resource providers) and for each hypervisor, get the allocations - similar to what mnaser's script does
14:00:00 mriedem getting the hypervisors + servers in the same call like his script would also tell you if allocations on that provider was a server or not - and if not, it's either leaked or it's a migration allocation
14:00:09 mriedem so no i don't think you need to loop over all instances
14:00:18 mriedem maybe i should just write this thing :)
14:06:37 bauzas mriedem: I'm pretty sure I can do it

Earlier   Later