Earlier  
Posted Nick Remark
#openstack-nova - 2018-11-17
21:26:42 openstackgerrit Dr. Clemens Hardewig proposed openstack/nova master: Fixes instance resizing/migration when swap volume is on lvm https://review.openstack.org/618621
#openstack-nova - 2018-11-18
08:01:14 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Consider root id is None in the database case https://review.openstack.org/613305
08:02:31 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Consider root id is None in the database case https://review.openstack.org/613305
12:16:33 openstackgerrit Balazs Gibizer proposed openstack/nova master: Calculate port_id rp_uuid mapping for binding https://review.openstack.org/616239
12:16:34 openstackgerrit Balazs Gibizer proposed openstack/nova master: Pass allocations and traits to neturonv2 api https://review.openstack.org/616240
12:16:35 openstackgerrit Balazs Gibizer proposed openstack/nova master: Send RP uuid in the port binding https://review.openstack.org/569459
12:16:35 openstackgerrit Balazs Gibizer proposed openstack/nova master: Test boot with more ports with bandwidth request https://review.openstack.org/573317
18:21:31 lucidguy Is it possible to install nova-compute on the controller, without virtualization? As in the controller is also a compute node
19:03:12 lucidguy for the life of me I can't figure out why my instances just sit in the BUILD/scheduling stage
19:03:30 lucidguy Anyone want to assist?
#openstack-nova - 2018-11-19
02:20:01 openstackgerrit zhufl proposed openstack/nova master: Add missing ws seperator between words https://review.openstack.org/618491
02:52:38 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Consider root id is None in the database case https://review.openstack.org/613305
04:33:57 openstackgerrit Merged openstack/nova master: Fix regression in glance client call https://review.openstack.org/618534
04:34:06 openstackgerrit Merged openstack/nova master: doc: Rewrite the console doc https://review.openstack.org/606148
04:34:13 openstackgerrit Merged openstack/nova master: doc: Add minimal documentation for RDP consoles https://review.openstack.org/606992
04:34:19 openstackgerrit Merged openstack/nova master: doc: Add minimal documentation for MKS consoles https://review.openstack.org/606993
05:17:07 openstackgerrit zhufl proposed openstack/nova master: Add missing ws seperator between words https://review.openstack.org/618491
07:42:19 bhagyashris artom: Hi,
09:20:29 melwitt frickler: thanks for jumping on that. agreed we should consider making the ceph job voting
09:34:52 jsheeren hi all I was curious about an issue we ran into
09:35:10 jsheeren we have an Opensack Pike env and we're using NFS as shared storage for /var/lib/nova/instances
09:36:31 jsheeren our env consists of 29 compute nodes, each has a mount to the volume for shared storage
09:36:36 kashyap melwitt: Have fun; and try to disconnect :-)
09:37:12 jsheeren we noticed the latency on that volume becoming very high and we were getting api timeouts. (with rabbitmq time-outs)
09:39:21 jsheeren our suspicion is the image cache manager as a cause of the latencies. when we did a rolling restart of nova-compute services (with a 5 min delay between them); the latency was gone
09:39:30 jsheeren and we are not seeing the api time-outs any more.
09:40:40 jsheeren has anyone had a similar experience? we increased the image cache manager interval as well, from the default 2400 sec to 4800 sec
09:43:16 jsheeren it seems the crawling of the /var/lib/nova tree takes longer than the message time-out. so we also increased the rcp_response time-out
09:43:43 jsheeren there are approx 700 instances on the env btw
09:55:47 openstackgerrit Matthew Booth proposed openstack/nova master: Call migrate_volume_completion after cinder migrate https://review.openstack.org/618717
10:39:46 tobias-urdin melwitt: we did hit this bug in rocky today https://review.openstack.org/#/c/591080/
10:39:53 tobias-urdin would that be acceptable for backport?
11:11:48 openstackgerrit Vlad Gusev proposed openstack/nova stable/rocky: Handle unicode characters in migration params https://review.openstack.org/618734
11:20:14 openstackgerrit Radoslav Gerganov proposed openstack/nova master: VMware: implement trigger crash dump https://review.openstack.org/618736
11:25:22 openstackgerrit Jason SUN proposed openstack/nova master: For instances end up in cell0, set its availability_zone to None. https://review.openstack.org/618737
12:09:34 tobias-urdin is it possible to flush the entries in instance_system_metadata for an instance manually without breaking something? there is cached content on user and project which is incorrect
12:09:53 tobias-urdin i assume the only other wait to force a rewrite of those values in the xml would be a hard reboot, but not sure that would do the trick either
13:25:07 openstackgerrit Surya Seetharaman proposed openstack/nova master: Add os_compute_api:servers:create:cell_down policy https://review.openstack.org/614783
13:41:20 openstackgerrit Surya Seetharaman proposed openstack/nova master: Add os_compute_api:servers:create:cell_down policy https://review.openstack.org/614783
13:46:11 openstackgerrit Matt Riedemann proposed openstack/nova master: Add DownCellFixture https://review.openstack.org/614810
14:03:09 openstackgerrit Takashi NATSUME proposed openstack/nova master: Add API ref guideline for body text https://review.openstack.org/605628
14:12:57 openstackgerrit Josephine Seifert proposed openstack/nova-specs master: Spec for the Nova part of Image Encryption https://review.openstack.org/608696
14:32:24 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix server query examples https://review.openstack.org/616834
14:56:38 openstackgerrit Elod Illes proposed openstack/nova master: Transform scheduler.select_destinations notification https://review.openstack.org/508506
14:56:39 mriedem jackding: some small changes for https://review.openstack.org/#/c/605902/ and then i'm +2
14:56:44 mriedem plus the glance image docs
15:04:03 jackding mriedem: ok thanks
15:04:27 spatel sean-k-mooney: morning!!!
15:19:17 sean-k-mooney hello
15:19:23 spatel_ how are you ?
15:20:02 spatel_ i had question related multi-queue for virt-io
15:20:06 sean-k-mooney not too bad. just rootcaused an issue in some logs so feeling quite good
15:21:00 spatel_ if i have 8 vCPU on instance in that queue what value should be good to set in ethtool -L eth0 combined <N> ?
15:22:09 sean-k-mooney 8
15:22:37 sean-k-mooney when you enable multiqueue openstack will allocate a tx and rx pair per core
15:24:17 spatel_ i thought i should keep some CPU core for other work
15:24:45 spatel_ This is what i am doing so far may be i am wrong here.. if i create 16 vCPU machine then i assign only 8 queue
15:25:06 spatel_ if i create 8 vCPU machine then i create 4 queue
15:25:42 spatel_ am i doing something wrong doing that or best practice is to give vCPU = Queue size
15:26:07 sean-k-mooney assinging a queue does nto mean you are assinging a cpu to manage it
15:26:39 sean-k-mooney the vswitch cannot know which queue the os is using so it will assume it can enqueue packets to all of them
15:27:11 sean-k-mooney if you dont config the kernel to pool on all queue you will miss packets
15:27:36 sean-k-mooney you can have one guess cpu pool all queue if you want
15:28:12 spatel_ so best option is to give all queue right?
15:28:25 spatel_ 8 vCPU = 8 queue ?
15:28:31 sean-k-mooney by assingin 1 queue per cpus its allows apps to transmit without haveing to take locks as you can use the cpu id as a queue index
15:28:37 sean-k-mooney yes
15:29:03 sean-k-mooney but your application that is processign the traffic in the vm can be confied to only 4 cpus if you like
15:29:25 sean-k-mooney you just need to configre the app to use 2 queues per core in that case
15:29:48 sean-k-mooney if you are using the kernel driver this is all handeled internally i belive
15:30:42 spatel_ I thought queue bind with vCPU so if you specify 4 queue size then only 4 vCPU parellel work on packet processing..
15:31:25 spatel_ that is why i was reserving 4 vCPU for OS and 4vCPU for queue (for networking work)
15:31:30 sean-k-mooney there are 2 level here. the host level were we will allocate 1 queu per vcpu and the guest level
15:32:02 spatel_ https://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/libvirt-virtiomq.html
15:32:40 spatel_ Host level ?? never heard that
15:33:24 sean-k-mooney what im trying to say is that nova will configure qemu with 1 queu per vcpu form the host/hyperviour perspective
15:33:44 sean-k-mooney provided you enable multique that is
15:34:47 spatel_ hmm!
15:34:59 sean-k-mooney as such if you do not set ethtool -L <NIC> combined $(nproc)
15:35:08 sean-k-mooney you will get incorrect behavior
15:35:16 tobias-urdin mriedem: could i steal some of your time, perhaps you know if it flushed the system metadata cache
15:35:19 tobias-urdin 12:58 < tobias-urdin> is it possible to flush the entries in instance_system_metadata for an instance manually without breaking something? there is cached content on user and project which is incorrect
15:35:23 tobias-urdin 12:58 < tobias-urdin> i assume the only other wait to force a rewrite of those values in the xml would be a hard reboot, but not sure that would do the trick either
15:35:26 spatel_ i think slowly i am following you... what you trying to say.. sean-k-mooney
15:35:55 openstackgerrit Tobias Urdin proposed openstack/nova stable/rocky: Handle unicode characters in migration params https://review.openstack.org/618734
15:35:55 sean-k-mooney but within the guest the application that process packts form that interface can pin to 1-n core independly form the number of quese that there are
15:36:38 spatel_ oh!! got it.. what you saying..
15:36:58 spatel_ i was wrong about queuing logic...
15:37:20 mriedem tobias-urdin: there is no external REST API for changing things within the instance system_metadata,
15:37:27 spatel_ let me change my all instance to use all nproc
15:37:41 mriedem and what goes in there depends on the instance and operation, and manually messing with it is probably a bad idea given it's system data
15:38:04 mriedem tobias-urdin: so you'd have to be more specific about the incorrect sysmeta data that needs to be fixed
15:38:05 spatel_ sean-k-mooney: thanks again for saving me!!!
15:38:10 tobias-urdin mriedem: we are affected by https://review.openstack.org/#/c/618734/ but we have renamed the project until then but live migrations fails since it's wrong in the XML
15:38:31 sean-k-mooney spatel_: no worries this is rather difficult to figure out all at once
15:38:49 tobias-urdin so i was not sure if doing a hard reboot would use the cached instance_system_metadata or not, it does rebuild the XML but perhaps with the wrong data
15:38:59 tobias-urdin perhaps better to just test it out in a test environment
15:39:26 spatel_ in document is not very clear! anyway i am totally on it now
15:39:28 tobias-urdin it's probably not a good idea to DELETE those rows in instance_system_metadata
15:39:56 mriedem tobias-urdin: no that's probably not a great idea

Earlier   Later