Earlier  
Posted Nick Remark
#openstack-nova - 2019-02-22
17:40:57 openstackgerrit Artom Lifshitz proposed openstack/nova master: [DERP] Remove _legacy_dict methods https://review.openstack.org/636210
17:40:58 openstackgerrit Artom Lifshitz proposed openstack/nova master: Add migration param to check_can_live_migrate_destination https://review.openstack.org/634605
17:40:58 openstackgerrit Artom Lifshitz proposed openstack/nova master: Introduce live_migration_claim() https://review.openstack.org/635669
17:40:59 openstackgerrit Artom Lifshitz proposed openstack/nova master: Use live_migration_claim() to check dest resources https://review.openstack.org/634606
17:41:00 openstackgerrit Artom Lifshitz proposed openstack/nova master: New objects to transmit NUMA config from dest to source https://review.openstack.org/634827
17:41:00 openstackgerrit Artom Lifshitz proposed openstack/nova master: LM: Make dest send NUMAMigrateData to the source https://review.openstack.org/634828
17:41:00 openstackgerrit Artom Lifshitz proposed openstack/nova master: LM: update NUMA-related XML on the source https://review.openstack.org/635229
17:41:01 openstackgerrit Artom Lifshitz proposed openstack/nova master: [WIP] Drop MoveClaim in rollback_live_migration_at_destination https://review.openstack.org/638654
17:41:24 mriedem kashyap: ok ok
17:41:56 kashyap I just spent 2 hours talking to the QEMU guys to carefully go through all the logs. I've got a couple of nice action items for DevStack, though :-)
17:42:18 kashyap I'll write a comment from the investigation. And see if a "trend" shows up on Monday. (1 failure is not a trend :D)
17:51:01 aspiers haha
17:51:24 aspiers mriedem: I wish I could say I'm young and naive but I'm just ... naive
17:51:29 mriedem kashyap: logstash is also behind so i'm not sure if it's rare or new
17:52:01 melwitt dansmith: as one of the primary reviewers on the spec, you might fancy reviewing the patch for ironic conductor groups. has one +2 already https://review.openstack.org/635006
17:52:16 dansmith guhhhh
17:52:21 dansmith it's friday, don't make me work
17:52:24 aspiers OK it's time for the weekend. Thanks all for your help, catch you next week o/
17:52:39 temka dansmith, don't be so edgy
17:52:46 melwitt haha
17:53:27 kashyap mriedem: Yeah, I saw your comment on indexing; I'm really curious now, after all the time I spent tongiht
17:53:38 kashyap mriedem: Monday I should get to know I suppose, if there's a pattern
17:54:06 kashyap dansmith: You'll like this: https://basecamp.com/books/calm
17:54:36 openstackgerrit Stephen Finucane proposed openstack/nova-specs master: Add 'flavor-extra-spec-image-property-validation' spec https://review.openstack.org/638734
17:54:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Remove misleading code from _move_operation_alloc_request() https://review.openstack.org/638700
17:54:44 mriedem fried_rice: ^
17:55:27 mriedem "It Doesn't Have to Be Crazy at Work (if you work in the EU"
17:58:53 kashyap LOL
17:59:10 kashyap Well ... it is always "hustle" if you make it a hustle :D
17:59:58 kashyap (That book is written by Americans :D) One of them is a Rails co-founder. They _really_ know what they're talking about.
18:01:19 kashyap ) The Rails part is to note that it's written by a developer, and not some "tech journalist"
18:01:30 kashyap Anyhow, /me --> dinner and air
18:33:21 openstackgerrit Artom Lifshitz proposed openstack/nova master: Remove _legacy_dict methods https://review.openstack.org/636210
18:33:22 openstackgerrit Artom Lifshitz proposed openstack/nova master: Add migration param to check_can_live_migrate_destination https://review.openstack.org/634605
18:33:22 openstackgerrit Artom Lifshitz proposed openstack/nova master: Introduce live_migration_claim() https://review.openstack.org/635669
18:33:23 openstackgerrit Artom Lifshitz proposed openstack/nova master: Use live_migration_claim() to check dest resources https://review.openstack.org/634606
18:33:23 openstackgerrit Artom Lifshitz proposed openstack/nova master: New objects to transmit NUMA config from dest to source https://review.openstack.org/634827
18:33:24 openstackgerrit Artom Lifshitz proposed openstack/nova master: LM: Make dest send NUMAMigrateData to the source https://review.openstack.org/634828
18:33:24 openstackgerrit Artom Lifshitz proposed openstack/nova master: LM: update NUMA-related XML on the source https://review.openstack.org/635229
18:33:25 openstackgerrit Artom Lifshitz proposed openstack/nova master: [WIP] Drop MoveClaim in rollback_live_migration_at_destination https://review.openstack.org/638654
18:34:30 temka mriedem_lunch, fixed https://review.openstack.org/#/c/636210/11 when you're back
18:34:43 temka Or actually dansmith, you wanna handle it?
18:35:31 dansmith temka: what was the issue?
18:36:08 temka There's a field called connection_info_json that's a string, but was being printed the way a dict would
18:36:27 temka So I was trying and failing to assert equality between two dicts when they were actually strings
18:37:01 temka Or rather, I was asserting about their containing dicts, and sometimes the JSON would be in the wrong order and compare false
18:37:30 temka And I was trying to fix it by treating the JSON like a dict, when I should have just loads and compared that
18:38:47 dansmith ah, Is ee
18:39:37 sean-k-mooney i have no other context of this but just looking a dmesg after a kernel update i noticed this
18:39:40 sean-k-mooney "capability: warning: `privsep-helper' uses deprecated v2 capabilities in a way that may be insecure"
18:41:02 sean-k-mooney considering this is an an all in one containerised deployment i have no idea which privsep-help that might be but i have never noticed this before
18:41:07 temka dansmith, cheers!
18:48:41 dansmith fried_rice: I just -1d this that you had +2d.. not sure if you know the answer to my concern, but: https://review.openstack.org/#/c/635006
19:13:57 dansmith jroll: ^
19:14:42 jroll y u so mean
19:15:50 dansmith man, I've deleted like three non-PC joke responses to that
19:16:51 jroll heh
19:19:07 jroll dansmith: even worse, I agree with you
19:19:13 jroll I'll respin monday morning
19:19:16 dansmith YASS
19:25:36 mriedem twizzlers really needs to rethink their packaging because the smashed together brick of licorice that you have to destroy the bag to get 1 rope from is frustrating
19:26:07 jroll you need fresher twizzlers yo
19:26:16 mriedem does not exist
19:26:53 mriedem and by destroying the bag, you guarantee staleness within 48 hours
19:27:20 temka Solution: eat the whole bag.
19:27:25 mriedem in progress
19:28:08 dansmith lol
19:39:05 melwitt lol, it's so timely that you said that. I got the SAME problem earlier this week
19:39:37 melwitt and their "resealable" bag design cannot be opened without destroying the bag
19:40:01 sean-k-mooney its a secret conspiacy to get you to get them allin in one go so you have to buy more
19:40:19 melwitt probably
19:40:56 melwitt I put the tattered bag and brick into a gallon size ziplock freezer bag. nailed it
19:50:41 nicolasbock Hi, I am trying to understand the concept of quotas and limits. I don't quite see how they differ.
19:56:20 melwitt nicolasbock: lots of people use the words interchangeably. but there is quota usage (amount of resources being used) and quota limits (configured limit for the amount of a resource)
19:56:43 melwitt when people say "quotas" they usually mean quota limits
19:57:18 nicolasbock Ah, what I was thinking of are `openstack quota list` and `openstack limits show`
19:58:04 melwitt ah, ok. 'openstack limits show' is probably for showing keystone unified limits (which we are not yet leveraging in nova)
19:58:11 melwitt let me double check
20:00:02 nicolasbock Ok
20:00:30 nicolasbock So historically, limits came first and is now being unified under Keystone?
20:00:33 melwitt looks like I'm wrong. I'm looking for what it's calling underneath
20:00:40 nicolasbock Ok
20:01:59 melwitt limits show calls a compute api https://github.com/openstack/python-openstackclient/blob/4bde9af89251431791fc8d69fe09d5e17a8fba8f/openstackclient/common/limits.py#L90
20:02:38 fried_rice dansmith: ack, looking.
20:03:06 melwitt nicolasbock: which is this one, which is the old school rate-limiting api https://github.com/openstack/python-novaclient/blob/master/novaclient/v2/limits.py#L85
20:03:38 mriedem dansmith: remind me, is a compute node for vcenter still 1:1 with the compute service host? or 1:M like ironic?
20:03:52 mriedem is the compute node the vcenter cluster, or is a compute node an esxi host in that cluster?
20:04:02 melwitt nicolasbock: hah, it's actually for both. nice https://developer.openstack.org/api-ref/compute/?expanded=show-rate-and-absolute-limits-detail#limits-limits
20:04:15 nicolasbock Thanks melwitt
20:04:29 melwitt so that's showing quota limits and the old rate limit part is empty
20:04:47 melwitt now, what does 'openstack quota list' do
20:04:50 dansmith mriedem: yeah I think the compute node is a cluster, which is multiple machines
20:05:18 mriedem but all instances on the same compute service host point at the same compute node...
20:05:20 dansmith mriedem: so it looks 1:1 like libvirt, not 1:N like ironic, but the 1 is actually N
20:05:31 mriedem yeah ok
20:06:55 melwitt nicolasbock: ok, so that one does this https://developer.openstack.org/api-ref/compute/?expanded=show-a-quota-detail#show-a-quota
20:07:27 melwitt nicolasbock: two different APIs that do nearly the same thing. the 'openstack limits show' will show the quota limits and quota usage, the 'openstack quota list' will show the quota limits only
20:07:52 nicolasbock Ok
20:07:57 nicolasbock Thanks!
20:08:05 melwitt np

Earlier   Later