Earlier  
Posted Nick Remark
#openstack-nova - 2017-06-05
14:31:05 mriedem i see
14:31:06 artom Nothing's really changed
14:31:15 artom Comments, and formatting, and...
14:31:16 mriedem well i've got to dig into mordred's problem first
14:31:28 artom mriedem, no, my stuff is obviously way more important
14:31:29 mriedem i can star it
14:31:32 wy mriedem but i think it would not migrate successfully forever
14:31:35 mordred artom: :)
14:32:03 mriedem wy: i may be mistaken but i though there was a way to check progress with virsh or qemu command line
14:32:13 mordred mriedem: I just pushed up a silly patch in shade to look for "Successfully synced instances from host" in the scheduler logs before starting to run shade's tests
14:32:50 wy mriedem i have found none.openstack has not provide command to see the process
14:33:52 wy mriedem i am seesing the compute log.but the remaining data decends for a while then asend..
14:34:14 wy mriedem could I think it would not migrate successfully forever?
14:34:56 mriedem wy: i mean like "migrate -d URI" https://www.linux-kvm.org/page/Migration#Management
14:36:16 mriedem wy: https://www.youtube.com/watch?v=Vy8rS_5vea4 about 9 minutes in talks about some of this
14:36:23 mriedem virsh domjobinfo <domain>
14:36:25 mriedem for example
14:36:36 wy mriedem thanks,i will have a look at
14:36:44 wy mriedem you are so helper
14:37:46 mordred mriedem: because looking througha few logs of successful runs, that seems to happen approximately around when we launch functional tests anyway - so it may just be a legit race-condition between the cloud settling in and the tests getting started (although also maybe there is a real bug obvs)
14:37:48 wy mriedem sorry
14:37:55 wy mriedem i do not understand
14:38:03 wy mriedem but what is the uri?
14:38:06 mordred mriedem: also, every time someone types "virsh" I think they're mistyping vishy ...
14:38:14 wy mriedem what i should input in the command
14:39:56 mriedem wy: virsh domjobinfo --help ?
14:40:03 mriedem i assume <domain> is the domain id
14:40:10 wy mriedem It is still migrating about many minutes..I just shut down the video.it successfully migrate
14:40:12 mriedem e.g. 00000000ef or something
14:40:17 wy mriedem ok
14:40:27 wy mriedem is the video affects?
14:41:20 mriedem wy: i assume so yes
14:41:33 mriedem everything the source vm is doing has to be transferred to the destination vm
14:42:10 wy mriedem but i just open the video but not playing it ..it means the video is suspend
14:43:33 wy mriedem open the video but not playing it,this will contribute to the change of the ram?
14:44:13 wy mriedem or we can say,my bandwidth is not enough,so the changes of ram is bigger than the transmit??
14:47:30 wy mriedem thanks very much.it is 11,i have to go to dormitory to sleep.It is my pleasure to make friends with you.You are so kind
14:48:01 wy mriedem but ,If you have seen,please help me solve my questions...ahah
14:50:06 openstackgerrit Andrey Volkov proposed openstack/nova master: [WIP] [placement] Add api-ref for allocations https://review.openstack.org/470933
14:50:06 openstackgerrit Andrey Volkov proposed openstack/nova master: [placement] Add api-ref for aggregates https://review.openstack.org/470932
14:50:12 mriedem wy: you're welcome. i don't have a good answer to your question about a paused video during a live migration
14:50:23 mriedem and this isn't really the place to debug that level of detail probably
14:51:06 mriedem mordred: ok so back to your thing, this stacktrace is when the compute starts up and calls update_instance_info before the host is mapped http://logs.openstack.org/95/468095/2/gate/gate-shade-functional/3f5d8dc/logs/screen-n-sch.txt.gz#_Jun_02_12_45_15_755877
14:51:14 mriedem then we map the host here http://logs.openstack.org/95/468095/2/gate/gate-shade-functional/3f5d8dc/logs/devstacklog.txt.gz#_2017-06-02_12_46_19_540
14:52:07 mriedem the server create request hits the scheduler here http://logs.openstack.org/95/468095/2/gate/gate-shade-functional/3f5d8dc/logs/screen-n-sch.txt.gz#_Jun_02_12_46_59_055921
14:52:18 mriedem 40 seconds later
14:55:12 mriedem mordred: methinks the problem isn't with the compute host not being mapped,
14:55:20 mriedem but rather the compute host failing to register with placement
14:55:49 mriedem b/c the scheduler is asking placement for resource providers (comptue nodes) to satisfy the request
14:56:44 openstackgerrit Sean Dague proposed openstack/nova master: Be more tolerant of keystone catalog configuration https://review.openstack.org/438049
14:58:48 openstackgerrit Eric Berglund proposed openstack/nova master: Add PowerVM to nova support matrix https://review.openstack.org/470999
14:59:26 mordred mriedem: ah -ok that makes sense to me
14:59:42 mriedem mordred: still tracing the n-cpu logs
14:59:59 mriedem sdague: fyi while you were out, a few of the clients you needed for the global request id stuff got blacklisted
15:00:06 mriedem the versions that is, neutronclient 6.3.0 for sure
15:00:36 cdent dansmith: that was just an example of a pattern, not a plan
15:00:37 openstackgerrit Eric Berglund proposed openstack/nova master: Add PowerVM to nova support matrix https://review.openstack.org/470999
15:00:53 sdague mriedem: yeh, saw that, but the glance one looks fine now
15:01:02 edleafe dansmith: what cdent said
15:01:09 sdague mriedem: so I flipped that around
15:01:19 dansmith cdent: okay it seemed like it would be specifically targeted stuff for nova's scheduler though
15:01:50 jaypipes cdent, alex_xu, edleafe, dansmith: join #novaschedulercontd
15:01:50 edleafe dansmith: it doesn't have to be
15:02:00 dansmith jaypipes: ugh, can't we hangout?
15:02:13 jaypipes dansmith: I'm happy to hangout.
15:02:16 dansmith jaypipes: new irc channels ftl, even if short-lived
15:02:30 cdent i can hangout
15:02:37 jaypipes ok, let's do a hangout.
15:02:42 jaypipes one sec, I will set up
15:02:45 dansmith can we have five mins for food/coffee?
15:02:50 dansmith I have had neither yet
15:02:54 edleafe dansmith: +1
15:03:12 edleafe How about at <yourtime>:15 ?
15:03:24 cdent wfm
15:03:29 mriedem sfinucan: looks like we deprecated the use_neutron config option, which is going to be a bit confusing if you're using nova-network with cells v1
15:03:38 openstackgerrit Chris Dent proposed openstack/nova master: Sync os-traits to Traits database https://review.openstack.org/469578
15:04:19 dansmith yeah
15:04:31 dansmith I can fill out three or four employment applications in 15 mins
15:04:31 jaypipes dansmith, cdent, edleafe, alex_xu: https://hangouts.google.com/call/fxu4kc4ufrakhiwjyq6idxrmcqu
15:04:54 jaypipes I'll just sit in the hangout. join as you will.
15:05:02 cfriesen_ did anyone sort out the issue with jenkins getting stricter about releasenotes?
15:06:05 cfriesen_ I'm looking at this in particular, hitting it on my local machine as well: https://review.openstack.org/#/c/435141
15:07:06 lei-zh jaypipes, for requesting traits part, are we going to let users to specify traits associated with top resource providers and nested ones?
15:09:34 jaypipes lei-zh: my initial thoughts on that matter were that we would continue to use the flavor as the thing that users would request, and flavors would have a "required" attribute that was a list of string traits that were required by that flavor.
15:10:30 jaypipes lei-zh: long-term, I would love to have a compute API that allowed the user (or certain users I suppose) to request specific traits directly and not have to request a particular flavor.
15:10:39 jaypipes lei-zh: but we're a ways from that. :)
15:11:23 alex_xu jaypipes: lei-zh , I'm thinking the meaning of required_traits is that 'give me a resource provider or it's nested provider includes those required traits'
15:11:51 jaypipes alex_xu: correct. (also shared provider)
15:13:30 mordred mriedem: in general, please let me know if there is anything I can do to help - I'm pretty sure we've passed my level of understanding of being helpful with debugging further, but I'll dig in to whatever if it's useful
15:14:09 mriedem mordred: sure, if it's placement it should be fairly easy for me to see what's up
15:14:34 mordred mriedem: also, is there any way as a user to get "no hosts could schedule this request" is the cause of the error?
15:19:25 sdague mriedem: did you ever get the mysql specific test case merged from a couple of weeks ago?
15:20:47 mriedem sdague: nope
15:20:53 mriedem sdague: haven't found time to get back to it yet
15:21:00 sdague mriedem: was it working?
15:21:02 sdague or not?
15:21:27 mriedem sort of
15:21:42 mriedem https://review.openstack.org/#/c/467772/
15:21:54 mriedem https://review.openstack.org/#/c/467772/2/nova/tests/functional/test_servers.py@1029
15:22:21 mriedem i think we have to do some things manually for setting up the cell mapping pointed at the mysql backend

Earlier   Later