| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-10-02 | |||
| 18:30:25 | mriedem | 186 for pci_devices | |
| 18:30:26 | efried | 186 hits when I include 'pci-devices' | |
| 18:30:27 | efried | yeah. | |
| 18:31:02 | efried | Well, the good news is that'll make it easier to rip out later | |
| 18:31:04 | mriedem | pci_requests is only 16 | |
| 18:31:28 | efried | Presumably because only 16 of 'em requested PCI devices? | |
| 18:31:35 | mriedem | no | |
| 18:31:40 | mriedem | but not really sure | |
| 18:31:48 | mriedem | this ci job doesn't include any pci stuff | |
| 18:32:05 | mriedem | so anything we're loading here is not used | |
| 18:37:48 | efried | The claimer doesn't log for PCI claims like it does for cpu, mem, and disk. So it's tough to tell if it *thinks* it's doing some kind of PCI claim. | |
| 18:42:47 | openstackgerrit | Chris Dent proposed openstack/nova master: Whether to use configdrive disk depends on instance.configdrive https://review.openstack.org/485930 | |
| 18:52:30 | efried | cdent Would ^ this mean I could switch from `if configdrive.required_by(instance):` to `if instance.config_drive` in my driver? | |
| 18:53:15 | cdent | efried: sorry, don’t really know, I was just rebasing that to get it lined back up with the present | |
| 18:53:29 | cdent | sort of a rebase/recheck combo | |
| 18:53:47 | efried | Heh, okay. Yeah, it was after I said that that I realized you weren't really the author. | |
| 19:02:37 | sdague | mriedem: sure, I can take another cycle through it | |
| 19:23:48 | openstackgerrit | Merged openstack/nova-specs master: Add a spec for POST /allocations in placement https://review.openstack.org/499259 | |
| 19:34:49 | cdent | jaypipes: except it’s not me he’s arguing with | |
| 19:35:11 | jaypipes | cdent: yes, sorry, with edleafe :) | |
| 19:35:18 | efried | whoah, something merged. | |
| 19:35:20 | cdent | but it is funny having the two most typo ridden people in the same place at the same time | |
| 19:35:24 | cdent | efried: i know, right? | |
| 19:36:14 | sean-k-mooney | jaypipes: :) semantics and grammer i understand, its spelling and typing i have issues with :) | |
| 19:36:14 | cdent | I find quite a lot of comfort in the fact the sean-k-mooney is a capable person and spells in the sae phonetically weird way that I do | |
| 19:36:21 | jaypipes | sean-k-mooney: :) | |
| 19:36:27 | cdent | see it just happened :) | |
| 19:37:37 | sean-k-mooney | well i have dyslexia so really phonetics is the best i can do without google/a spellcheck unfortunetly english spelling and phonetics rarely agree | |
| 19:38:31 | openstackgerrit | Sean Dague proposed openstack/nova master: Remove non libguestfs file injection for libvirt https://review.openstack.org/324720 | |
| 19:38:54 | edleafe | I always felt "performant" was a BS word. | |
| 19:39:19 | cdent | sean-k-mooney: I’ve often wondered about this: Do you happen to know if dyslexia is both ways: read and write? I had assumed it was read ony? | |
| 19:39:43 | cdent | edleafe: indeed it is but specs are mostly bullshit anyway, so having a few bullshit words is only right, right? | |
| 19:39:55 | mriedem | stephenfin: sdague: do you know if this ever came over from the openstack-manuals repo? https://github.com/openstack/openstack-manuals/blob/stable/ocata/doc/user-guide/source/cli-config-drive.rst | |
| 19:40:00 | sean-k-mooney | cdent: i think its different for different people. | |
| 19:40:18 | edleafe | cdent: there are several processing issues that are lumped into the term 'dyslexia' | |
| 19:40:45 | cdent | I’m aware of dysgraphia too, but I’ve never been clear on how/if connected | |
| 19:41:09 | sdague | mriedem: I don't see it anywhere in tree | |
| 19:41:11 | sean-k-mooney | cdent: for me i find it very difficult to read a singel word in isolation. its almost imposible for me to "sound it out" so i infer the meaning of a word form the context it is used in | |
| 19:41:36 | mriedem | sdague: yeah me neither | |
| 19:41:43 | edleafe | cdent: I don't have any dyslexia or dysgraphia; just dysphagia | |
| 19:41:54 | mriedem | i noticed b/c our api-ref says in the "config_drive" parameter description: "Read more in the OpenStack End User Guide." | |
| 19:42:08 | sdague | yeh | |
| 19:42:27 | sean-k-mooney | when i am writhing or typeing i then not to be able to keep up with the rate at which is am internally thinking about the phrase i intend to express so i miss words or part of them | |
| 19:42:56 | cdent | sean-k-mooney: do you find that when you make an error it often rhymes with the correct thing? | |
| 19:43:35 | sean-k-mooney | i do this less when typing as i can type faster, but the isssue is because i dont read word but instead infer them from context i dont see the error when i re read the sentence | |
| 19:43:53 | sean-k-mooney | cdent: yes sometimes or at least it will be phonetically similar | |
| 19:44:19 | cdent | interesting | |
| 19:44:40 | mriedem | https://bugs.launchpad.net/nova/+bug/1720873 | |
| 19:44:41 | openstack | Launchpad bug 1720873 in OpenStack Compute (nova) "end user guide was not migrated from openstack-manuals" [High,Confirmed] | |
| 19:47:36 | sean-k-mooney | cdent: i have started to use https://www.grammarly.com more when writing docs/commit message/release notes but i have not figured out a good way to integreate it or a spellchecker into my normal patch authoring workflow. | |
| 19:48:17 | cdent | ah, interesting, thanks | |
| 19:49:09 | efried | Technically "dysgraphia" is the writing part and "alexia" is the reading part. In a move which surely caused the classical-language-root scholars to tear out their hair, "dyslexia" became the portmanteau covering both. | |
| 19:50:19 | efried | My favorite is when sean-k-mooney uses "taught" for "thought", because it combines phonetic spelling with his Irish accent. | |
| 19:52:02 | sean-k-mooney | i was about to drink some coffee when i read that lol its ture i do that alot | |
| 19:55:47 | edleafe | Question on the retry flow for failed VM builds. Does the cast from superconductor to cell conductor use the same method in the cell conductor as the cast from the ComputeTaskAPI | |
| 19:56:04 | edleafe | 's cast to the cell conductor's build_instances? | |
| 19:56:24 | edleafe | I'm trying to determine if the cell conductor can tell if it's retrying or not | |
| 19:57:48 | sean-k-mooney | edleafe: it was my impression that reties would only propergate within the same cell as we did not want an upcall to the superconductor | |
| 19:58:40 | edleafe | sean-k-mooney: true. what I'm wondering is if the cell conductor can tell that the build is a retry or not | |
| 19:59:55 | sean-k-mooney | edleafe: good question dansmith would propably be the best person to ask. i would assume so but im not sure if that would chage anything other then the fact we are eliminating the fail hosts form the allocation candidates | |
| 20:00:32 | dansmith | edleafe: yeah because it's two operations | |
| 20:00:45 | dansmith | edleafe: the top level one is schedule_and_build_instances, the other is build_and_run or something like that | |
| 20:00:56 | edleafe | dansmith: thanks | |
| 20:01:07 | edleafe | rewriting the alternate hosts spec | |
| 20:01:21 | edleafe | totally spaced that the call to compute is a cast | |
| 20:01:59 | mriedem | hmm, if we deprecate personality files from the API, we would presumably also deprecate showing limits on personality files in the API too - and if the alternative for personality files is user_data and config drive, we don't have any quota limits on those - so would we need to add some? | |
| 20:02:36 | mriedem | edleafe: superconductor doesn't cast to cell conductor | |
| 20:03:38 | edleafe | mriedem: I was talking about the cell conductor -> compute. That's the cast | |
| 20:03:43 | mriedem | superconductor (schedule_and_build_instances) -> scheduler (select_destinations) -> superconductor (schedule_and_build_instances) -> compute (build_and_run_instance) -> cell conductor (retry = build_instances) | |
| 20:03:56 | mriedem | yeah then it's build_and_run_instance both ways | |
| 20:04:02 | sean-k-mooney | mriedem: well the user-data is stored perinsance correct so im not sure we need limits on it if its a fixed lenght string in the db | |
| 20:04:30 | cdent | ‘night all | |
| 20:04:32 | mriedem | sean-k-mooney: yeah, wasn't sure if that's why we had quota on injected files or what | |
| 20:04:36 | mriedem | i guess it's rate limiting | |
| 20:05:27 | mriedem | ooo we have 3 options for file injection quota | |
| 20:05:47 | sean-k-mooney | if its sored as a text field we may want a quota | |
| 20:06:13 | sean-k-mooney | injected files, injected file content bytes and ? | |
| 20:06:19 | mriedem | quota_injected_file_path_length | |
| 20:07:05 | mriedem | melwitt: AbsoluteResource just means it's global per deployment? or per project? | |
| 20:07:07 | sean-k-mooney | is that litrally just a path lenght ? e.g. a file system constrait | |
| 20:07:23 | mriedem | yes, default is 255 for the file path length | |
| 20:07:41 | sean-k-mooney | that the fat32 limit right | |
| 20:07:56 | mriedem | yeah i think so | |
| 20:11:16 | mriedem | god i've already forgotten how all of this quota checking code works already | |
| 20:11:43 | sean-k-mooney | looking at the instances table it looks like user_data mediumtext field which means its got a 16 Mib limit on mysql | |
| 20:12:11 | sean-k-mooney | *user_data is a mediumtext | |
| 20:14:39 | mriedem | ok it looks like this quota limit is per project/user | |
| 20:15:32 | mriedem | so by default you can have 5 files, at 10mb each | |
| 20:15:45 | mriedem | wait, no | |
| 20:15:46 | mriedem | kb | |
| 20:17:10 | sean-k-mooney | mriedem: yes it is. userdata however is handeled seperatly from that limit today | |
| 20:18:17 | mriedem | right, there is no quota limit on user_data | |
| 20:18:20 | mriedem | it's just the limit in the db per instance | |
| 20:18:25 | mriedem | which is as you said 16MB | |
| 20:18:30 | sean-k-mooney | yes | |
| 20:19:04 | sean-k-mooney | we could change that in the future or mysql could be we dont have a contract in place with the end user on this today | |
| 20:20:32 | sean-k-mooney | having a qouta on this in the future would not nessicalily be a bad thing it is sotre on you db node after all so it could cause issues if allowed to grow too large | |
| 20:35:05 | dansmith | mriedem: are you aware of any cells-based short circuiting around InstanceMapping? | |
| 20:35:17 | dansmith | in the api_samples_tests | |
| 20:35:46 | dansmith | in looking at some of them, they create a server, which exists in the cell db, but we never set the InstanceMapping.cell_mapping for those | |