Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-08
21:10:43 mriedem oh right devstack does that...
21:11:05 cdent I had to fix how wait_for_compute works in the devstack fix
21:13:02 cdent Perhaps tomorrow I'll try it with the filters enabled to see what happens
21:14:21 mriedem in your nova boot calls,
21:14:27 mriedem i see you used --min-count once
21:14:33 mriedem but not later in the loops, is there a reason for that?
21:14:46 mriedem like, boot 100 per request, in a loop of 10
21:15:57 cdent yeah, it's only when making lots of requests to /allocation_candidates that placement shows any load at all (and loading placement is the goal of all this)
21:16:10 bauzas dansmith: like I said to cdent, now there are no reasons to not support workers
21:16:16 dansmith this is all unsurprising though right?
21:16:25 dansmith placement should be mostly an http-to-sql adapter
21:16:31 cdent so many smal requests hits things way harder than anything
21:16:31 dansmith bauzas: ack
21:16:46 cdent dansmith: yes, and I've been saying that all along, but it's good to confirm it
21:16:51 dansmith cdent: ack, okay
21:16:53 cdent as an initial starting point of the exploration
21:17:31 cdent it supports the assertion I've been making for a while: Placement is not going to be a a bottleneck, at least not until we clean up some of the other stuff.
21:18:03 cdent mriedem: the first paragraphs after "playing with it" header talk about some of
21:18:05 cdent that
21:18:06 dansmith well, that was the assertion jaypipes made when he proofed all this early on, but yeah :)
21:18:48 mriedem i think this is still useful / good to see someone kicking things around,
21:18:55 ianw apropos nothing -- does configdrive work with aarch64? afaict it's just a libvirt level thing, so shouldn't have particular problems on a different architecture?
21:19:00 mriedem i've literally had some of this on my paper todo list on my desk for months
21:19:17 dansmith mriedem: oh yah, I'm not saying it's bad at all
21:19:35 dansmith mriedem: we learned a lot doing this for my instance list patch you were trying to blame :P
21:19:41 cdent dansmith: of course, but his tests were at just sql level, and the sql's changed a lot since then
21:19:50 dansmith cdent: totes
21:19:54 cdent so more playing the merrier
21:20:18 mriedem dansmith: heh and see how productive that was?
21:20:59 dansmith mriedem: again, not saying we shouldn't do this, I just thought this was going somewhere and thought the implication was "huh, well, placement isn't the bottleneck"
21:22:27 cdent it is going somewhere: more (concrete) info on how to arrange services and confirmation of stuff we mostly know (like scheduer needs workers and "apache is meh, use nginx") etc
21:22:34 efried cdent: s/duel/dual/
21:22:39 cdent thanks efried
21:22:46 efried unless it is duel, idk
21:25:15 cdent dansmith: what were you hoping for? Maybe I can try it now that I've leveled my brain up a bit.
21:25:19 efried cdent: s/message bug/message bus/ ?
21:25:26 cdent efried: heh, yup
21:25:31 efried I mean....
21:25:33 efried could be...
21:25:52 cdent plenty of message bugs
21:26:02 mriedem cdent: this might be of interest to you https://cloudblog.switch.ch/2017/08/28/starting-1000-instances-on-switchengines/
21:26:25 cdent mriedem: yeah saw that when it came out
21:29:20 efried cdent: "the placement api process are lost" => "...processes..."?
21:29:37 efried "of the much great effort"?
21:29:44 cdent you're hired
21:29:53 mriedem heh, better do this blog post via gerrit review first next time
21:30:03 efried At some point I'll contribute a substantive comment.
21:30:07 mriedem and then pick up the brain and skull bits from the wall
21:30:38 mriedem melwitt: on https://review.openstack.org/#/c/522161/ idk
21:30:41 mriedem don't know what regressed it
21:30:46 mriedem but i know it's busted w/o this
21:31:07 cdent I suspect if it had gone through gerrit it would fall on the floor and I'd give up before it got through the nit factory. post hoc nit fixing ++
21:31:14 mriedem and for anyone in china/japan/etc they'd probably like to be able to create a vm in queens
21:33:46 mriedem melwitt: ha https://review.openstack.org/#/c/541442/3/nova/virt/libvirt/driver.py@5404
21:33:52 mriedem no one wins when it's block_device_info
21:34:12 melwitt you can say that again
21:34:19 mriedem not all entries are a list of dicts
21:34:24 mriedem 'root_device_name': instance.root_device_name,
21:34:25 mriedem AND
21:34:30 melwitt :|
21:34:32 mriedem the 'block_device_mapping' entry is not a list of dicts
21:34:35 mriedem no ma'am
21:34:44 melwitt FINE
21:34:47 melwitt :)
21:34:49 mriedem it's a list of DriverVolumeBlockDevice objects, which wrap a BlockDeviceMapping object
21:34:55 mriedem and proxy all of the bdm object stuff to the db
21:35:15 mriedem DriverVolumeBlockDevice at some level might extend dict, so maybe you're right :)
21:35:34 mriedem it does https://github.com/openstack/nova/blob/master/nova/virt/block_device.py#L81
21:35:35 mriedem heh
21:35:38 mriedem shows what i know
21:36:59 melwitt from this, they're probably not all lists
21:37:01 melwitt https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1566-L1569
21:37:25 melwitt or maybe swap's not. I dunno
21:38:07 mriedem swap,
21:38:18 mriedem is a list of DriverSwapBlockDevice objects which extend DriverVolumeBlockDevice (i think)
21:38:20 jaypipes cdent: nice article.
21:38:27 mriedem https://github.com/openstack/nova/blob/master/nova/virt/block_device.py#L202
21:38:31 melwitt hah
21:39:16 mriedem or not, wtf knows
21:39:20 mriedem it's bdm roulette
21:39:55 mriedem melwitt: +W if you want to start backports
21:40:35 melwitt thanks
21:41:31 cdent thanks jaypipes
21:43:53 mriedem general observation,
21:44:07 mriedem i feel like this rc1 period has been much less of a clusterfuck than pike and ocata
21:44:17 mriedem right?
21:44:17 mriedem so i think that's progress
21:46:06 cdent mriedem: it has kind of felt like this cycle has been more to do with either fixing stuff or laying ground work for later stuff, so perhaps that means less exposure? but I agree things do seem a bit more chilled out
21:54:56 openstackgerrit Takashi NATSUME proposed openstack/nova stable/ocata: Add 'delete_host' command in 'nova-manage cell_v2' https://review.openstack.org/513721
21:55:37 openstackgerrit Takashi NATSUME proposed openstack/nova master: List/show all server migration types (1/2) https://review.openstack.org/430608
21:56:10 openstackgerrit Takashi NATSUME proposed openstack/nova master: List/show all server migration types (2/2) https://review.openstack.org/459483
21:56:52 openstackgerrit Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers.inc https://review.openstack.org/528201
21:57:19 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Add functional tests for traits API https://review.openstack.org/524094
21:57:53 openstackgerrit Takashi NATSUME proposed openstack/nova master: api-ref: Example verification for servers.inc https://review.openstack.org/529520
21:58:09 openstackgerrit Takashi NATSUME proposed openstack/python-novaclient master: Microversion 2.61 - List/Show all server migration types https://review.openstack.org/430839
21:58:49 openstackgerrit Takashi NATSUME proposed openstack/nova master: api-ref: Fix parameter order in rebuild https://review.openstack.org/529718
21:59:21 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Move body examples to an isolated directory https://review.openstack.org/529998
21:59:23 openstackgerrit Matt Riedemann proposed openstack/nova master: Add a nova-caching-scheduler job to the experimental queue https://review.openstack.org/539260
22:00:52 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix 500 error while passing 4-byte unicode data https://review.openstack.org/407514
22:03:00 mriedem hmm, we seem to be running both legacy-tempest-dsvm-neutron-full and tempest-full on changes

Earlier   Later