| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-02-22 | |||
| 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 | |
| 20:08:06 | nicolasbock | Now to the next question :) | |
| 20:08:22 | melwitt | uh oh | |
| 20:08:24 | nicolasbock | If I understand this correctly, then the usage is not updated by default | |
| 20:08:43 | nicolasbock | For Pike I found `max_age` in the `[Quota]` section | |
| 20:08:53 | nicolasbock | Which defaults to `0` | |
| 20:09:03 | melwitt | ok, that's for the old quota syncing mechanism | |
| 20:09:27 | nicolasbock | I also found https://github.com/openstack/nova/blob/c8926feb2675c754048f8c7398747e3c29bfadaf/releasenotes/notes/remove-quota-options-0e407c56ea993f5a.yaml | |
| 20:09:28 | melwitt | in pike, we changed the way we do quota usage and count resources directly instead of tracking them in a separate table | |
| 20:09:33 | nicolasbock | Which suggests that it's deprecated | |
| 20:09:58 | nicolasbock | Ok. Does that mean that I don't have to worry about this setting? | |
| 20:10:04 | melwitt | yes, the use of the separate table (which could get out-of-sync with actual resource consumption) and the syncing related options are deprecated and removed | |
| 20:10:04 | nicolasbock | The usage should be updated automatically? | |
| 20:10:14 | melwitt | right | |
| 20:10:40 | nicolasbock | Ok. Let me rephrase this to make sure I understand this correctly: | |
| 20:10:43 | melwitt | actual resource usage is counted per quota check since pike. going out-of-sync is no longer possible, so quota syncing is no longer possible | |
| 20:11:03 | nicolasbock | I should look only at `openstack limits show` | |
| 20:11:11 | nicolasbock | And it should show me the quota and the usage | |
| 20:11:25 | nicolasbock | And it's automatically kept up to date? | |
| 20:11:39 | nicolasbock | Does that summarize the situation somewhat accurately? | |
| 20:11:40 | melwitt | yes, anything the API is showing was accounted for when things were changed | |
| 20:12:08 | nicolasbock | Cool | |
| 20:12:10 | melwitt | you'll always see "reserved=0" because we no longer do the two-step reserve + commit quota dance | |
| 20:12:16 | nicolasbock | Wow, that's a lot easier than I thought :) | |
| 20:14:25 | melwitt | you can look at either 'openstack limits show' or 'openstack quota list'. limits show seems more useful since it shows the usage too | |
| 20:15:01 | melwitt | I notice that quota list has some limits that are not in limits show, but those are all deprecated by now I think | |
| 20:15:06 | nicolasbock | Yes, that's true | |
| 20:15:29 | nicolasbock | I find that listing a quota without also showing usage less helpful ;) | |
| 20:15:30 | melwitt | but they pull data in the same way, so they should match where they are the same | |
| 20:51:33 | fried_rice | mriedem: Flushing oldymoldys, are you happy with the reno verbiage etc. on https://review.openstack.org/#/c/564193/ at this point? | |
| 21:00:08 | mriedem | ech idk | |
| 21:00:15 | mriedem | they should also update the image properties docs https://docs.openstack.org/glance/latest/admin/useful-image-properties.html | |
| 21:00:21 | mriedem | but that's in glance so a follow up | |
| 21:00:28 | mriedem | i haven't looked at that change in forever though | |
| 21:01:05 | mriedem | if you're happy with it go ahead | |
| 21:01:24 | fried_rice | well, I was happy with it before you ripped into it. | |
| 21:01:33 | mriedem | you can be happy once again | |
| 21:01:38 | fried_rice | k | |