Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-29
14:27:02 frickler rpodolyaka: ah, great, the v2.41 is the trick, osc uses 2.1 by default and then it is missing. if I explicitly call for 2.41, I see the correct information. thx alot
14:27:39 rpodolyaka frickler: oops, that may be a red herring - that just what I get for `nova --debug show <uuid>`
14:27:59 rpodolyaka frickler: so just test it on 2.1, I
14:28:29 rpodolyaka *I'm not aware of any changes related to the info we return on attached volumes
14:28:34 frickler rpodolyaka: no, I confirmed that "openstack --os-compute-api-version=2.41 server show test1" shows the attribute, without setting the api version it doesn't
14:28:42 frickler rpodolyaka: was added in 2.16 it seems
14:28:49 rpodolyaka ah, ok
14:29:15 frickler makes me wonder why OSC doesn't use latest API by default
14:30:35 rpodolyaka frickler: neither does python-novaclient. Every new microversion is potentially backward-incompatible - you have to explicitly ask for it and make changes to the code (if necessary)
14:31:54 openstackgerrit Dan Smith proposed openstack/nova master: Make conductor ask scheduler to limit migrates to same cell https://review.openstack.org/438025
14:32:07 sdague rpodolyaka: that's not true, novaclient CLI uses latest by default
14:33:31 rpodolyaka sdague: hmm, won't it break novaclient if we remove field X from the output of some endpoint and novaclient expects it to be present?
14:33:54 rpodolyaka I thought we defaulted to the minimum
14:34:06 rpodolyaka and only ask for newer version if that's needed
14:34:26 rpodolyaka or if the command, let's say nova show now supports it (and so does the nova-api we talk to)
14:35:51 efried Did nova recently change what kind of threads the compute process uses?
14:36:12 rpodolyaka sdague: or by latest you mean latest supported by novaclient? not the latest returned by nova-api?
14:36:43 sdague rpodolyaka: we default to latest novaclient understands that the server supports
14:36:55 rpodolyaka ah, I see, that makes sense
14:36:59 rpodolyaka frickler: ^
14:37:08 rpodolyaka frickler: sorry for misleading you :P
14:37:25 sdague efried: nothing that I know of, what kind of things are you running into?
14:37:55 efried sdague Got an open() hanging in a subthread - and it's hanging the entire compute process.
14:38:55 sdague efried: there was an eventlet bump not that long ago
14:38:56 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Rename '[neutron] ovs_bridge' https://review.openstack.org/450266
14:38:56 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Move 'floating_ips' opts into 'network' https://review.openstack.org/431039
14:38:57 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Deprecate 'default_floating_pool' https://review.openstack.org/431038
14:38:57 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Add neutron.default_floating_pool https://review.openstack.org/431037
14:39:45 efried sdague Ah, that could do it. Got a pointer on hand, save me digging?
14:39:54 efried thorst ^^
14:40:49 efried It's the open() in the GlanceImageServiceV2.download method. I know why it's hanging - it's opening a FIFO and the reader side hasn't been opened yet - but the problem is that it's blocking all the other threads in the process - one of which is the reader side of that fifo :(
14:41:11 frickler sdague: rpodolyaka: so do you happen to know why OSC behaves different? or is it just lagging behind?
14:41:11 sdague efried: check out the openstack dev list on some issues around poll that were found
14:41:21 sdague frickler: ask the osc team?
14:41:26 efried sdague rgr that.
14:41:37 efried frickler I actually ran into this same thing yesterday.
14:42:10 frickler sdague: efried: o.k., moving over to -sdks, thx
14:42:22 efried Talked about it on #openstack-sdks - let me get you an eavesdrop reference...
14:43:06 efried http://eavesdrop.openstack.org/irclogs/%23openstack-sdks/%23openstack-sdks.2017-03-28.log.html#t2017-03-28T17:33:58
14:43:19 efried frickler ^^ Read down to the 20:21 mark.
14:44:34 efried frickler Adding your voice to the "use latest version" argument might help to get things moving in that direction \o/
14:44:50 frickler efried: will do, thx for the pointer
14:45:44 openstackgerrit Matthew Booth proposed openstack/nova master: Add InstanceMappingList.get_by_instance_uuids https://review.openstack.org/445139
14:45:44 openstackgerrit Matthew Booth proposed openstack/nova master: Make server_external_events use an optimal number of db queries https://review.openstack.org/445142
14:45:45 openstackgerrit Matthew Booth proposed openstack/nova master: Add RequestContext.for_cell() https://review.openstack.org/445140
14:45:45 openstackgerrit Matthew Booth proposed openstack/nova master: Add InstanceList.get_by_instance_mapping_list() https://review.openstack.org/445141
14:52:18 EmilienM sdague or mriedem: can you please click on https://bugs.launchpad.net/nova/+configure-bugtracker and paste the text you use ? thanks
14:52:47 mriedem paste the text we use?
14:52:52 mriedem i don't understand the request
14:53:03 mdbooth mriedem: If you like my meta-test, could we re-merge https://review.openstack.org/#/c/450383/ ?
14:53:29 EmilienM mriedem: yes, the text that appears when someone fils a bug
14:53:34 mriedem mdbooth: i'm leaving in about 10 minutes so won't have time for that right now.
14:53:37 EmilienM mriedem: I want to re-use it in tripleo somehow
14:53:50 mdbooth mriedem: Ok.
14:54:01 mriedem EmilienM: like http://paste.openstack.org/show/604670/ ?
14:54:16 sdague EmilienM: is that not visible to you if you just try to open a new bug?
14:54:32 EmilienM mriedem: perfect
14:54:44 EmilienM sdague: yes but I didn't want to spam your bug tracker
14:54:54 sdague EmilienM: you don't have to save the bug :)
14:55:19 EmilienM sdague: in fact, I'm interested by the popup that appears when the bug is saved
14:55:35 sdague EmilienM: ah, yeh, that's another field, let me grab
14:55:42 EmilienM thanks a lot
14:55:51 sdague http://paste.openstack.org/show/604672/
14:55:56 EmilienM awesome, thx again
14:56:00 sdague no prob
15:27:33 mdbooth dansmith: Did you see this change, btw: https://review.openstack.org/#/c/445142/
15:28:10 mdbooth It's not incredibly important itself, although I think it's useful, but it illustrates the idea of using object contexts
15:28:18 dansmith mdbooth: yes, but I've been completely swamped with other stuff
15:28:36 mdbooth dansmith: Ok, cool. Just wondered if it had hit your radar.
15:28:45 openstackgerrit Sujitha proposed openstack/nova master: Adding tags field to InstancePayload https://review.openstack.org/407228
15:39:36 jaypipes sfinucan: hmm, weird. for some reason I was under the impression that emulator threads would all be pinned to the same physical CPU core (when emulator thread policy was ISOLATE)
15:40:09 jaypipes sfinucan: since, my impression was that the emulator threads were actually pretty lightly loaded in a RT environment
15:40:53 sfinucan jaypipes: Not per my understanding, no - emulator cores aren't really any different to instance cores
15:41:28 sfinucan the only difference is that emulator cores are always on node 0
15:41:31 jaypipes sfinucan: ok, no worries. just a bad recollection of mine, I guess :)
15:41:42 sfinucan plus how they're tracked is totally different :)
15:41:45 sfinucan cool cool
15:42:08 jaypipes sfinucan: you good on https://review.openstack.org/#/c/400877/?
15:42:18 openstackgerrit Maciej Szankin proposed openstack/nova master: conf: remove *_topic config opts https://review.openstack.org/433924
15:42:52 sfinucan jaypipes: Hmm, don't know why I missed that. Checking now
15:57:26 openstackgerrit Sujitha proposed openstack/nova master: Adding tags field to InstancePayload https://review.openstack.org/407228
15:57:51 mriedem lyarwood: first thing i noticed right away https://review.openstack.org/#/c/439520/
15:59:48 johnthetubaguy mriedem: dam it, I -1ed for that in a previous version
16:01:10 mriedem sure you did, sure you did
16:01:12 mriedem :P
16:04:12 mdbooth mriedem: Incidentally, I also wanted to highlight this patch to you: https://review.openstack.org/#/c/445142/
16:04:46 mdbooth As I said to dansmith, it's not that important itself, but it demonstrates using object context when you've got a bunch of instances from different cells
16:04:49 vks1 hi, how does nova configure tag for VM ports ?
16:05:12 mdbooth So as well as being less error prone, it can also be more efficient
16:05:36 vks1 I see for 2 ports of a network on different compute has different tag.
16:06:33 vks1 is this valid ? can someone point to the document for the behavior ?
16:07:29 mriedem vks1: you want to talk to artom
16:07:42 mriedem mdbooth: https://review.openstack.org/#/c/439520/ is my goal for the week
16:07:56 artom vks1, heya
16:08:04 vks1 mriedem: thanks
16:08:04 artom vks1, I don't understand your question :(
16:08:07 mdbooth mriedem: You mean the actual detach calls, right? ;)
16:08:59 clarkb kashyap: mdbooth: hello, right now three of the four top bugs tracked by elastic-recheck originate in libvirt http://status.openstack.org/elastic-recheck/index.html#1643911 http://status.openstack.org/elastic-recheck/index.html#1638982 http://status.openstack.org/elastic-recheck/index.html#1646779 I know kashyap has poked at these in the past, but would it be possible to try and figure out these
16:09:01 clarkb issues? ianw started working on getting devstack to collect core dumps (though those aren't thought to be of help here) and was going to try running libvirt under electric fence. Maybe we can get a small group of people to coordinate around this and work together?
16:09:02 vks1 artom: I have 2 VMs launched on 2 different compute. When I see the tap ports on OVS , on one compute I see tag:1 and on other compute its tag:3

Earlier   Later