| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-02-15 | |||
| 09:46:36 | bauzas | np | |
| 09:46:37 | kashyap | I noticed the question and prompted you :-) | |
| 09:46:43 | kashyap | I _think_ he's left the channel :-( | |
| 09:47:00 | kashyap | I recognize the name of the developer from Kubernetes community | |
| 09:47:41 | cdent | stephenfin: it's funny how that works isn't it? so much stuff can stay under the radar, no matter how long you're around. | |
| 09:48:25 | stephenfin | cdent: For sure. You never stop learning new stuff | |
| 09:48:34 | stephenfin | Though I suppose if you did, it would probably be time to move on | |
| 09:49:07 | cdent | true | |
| 10:00:44 | openstackgerrit | Bence Romsics proposed openstack/nova master: Clarify 'capacity' in placement api-ref https://review.openstack.org/544347 | |
| 10:08:40 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Move resource provider objects into placement hierarchy https://review.openstack.org/540049 | |
| 10:08:41 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Isolate placement database config https://review.openstack.org/541435 | |
| 10:08:41 | openstackgerrit | Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766 | |
| 10:08:42 | openstackgerrit | Chris Dent proposed openstack/nova master: Isolate config parse_args for placement https://review.openstack.org/543495 | |
| 10:13:37 | bauzas | does anyone know if our nova documentation includes HTML rendered docstrings of our internal interfaces ? | |
| 10:13:40 | bauzas | stephenfin: ^ | |
| 10:14:01 | bauzas | I'd like to point in a document some object structures | |
| 10:14:05 | stephenfin | bauzas: Nope | |
| 10:14:17 | bauzas | okay, then I'll say look at the code | |
| 10:14:22 | stephenfin | That would need Sphinx's 'apidoc' tool, which we don't use enable | |
| 10:14:29 | stephenfin | That'd be the best call, yeah | |
| 10:23:29 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: doc: Clarify how to create your own filter https://review.openstack.org/544836 | |
| 10:23:44 | bauzas | stephenfin: gibi: doc nits fix in https://review.openstack.org/544836 | |
| 10:24:07 | bauzas | related to kashyap's proxying someone for clarifications about scheduler filters | |
| 10:24:28 | kashyap | bauzas: Thanks; will look at the review in a few | |
| 10:24:56 | stephenfin | bauzas: One newline missing and I'm +2 | |
| 10:29:49 | bauzas | stephenfin: ack, thanks | |
| 10:37:18 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: doc: Clarify how to create your own filter https://review.openstack.org/544836 | |
| 10:38:35 | openstackgerrit | Stephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec https://review.openstack.org/541290 | |
| 10:38:45 | stephenfin | bauzas: Boom ^ | |
| 10:39:18 | bauzas | stephenfin: okay, I'll look at your spec once I'm done with jaypipes's one about aggregate ratios | |
| 10:42:42 | openstackgerrit | Ameed Ashour proposed openstack/osc-placement master: Change documentation theme https://review.openstack.org/542378 | |
| 11:02:23 | openstackgerrit | Stephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec https://review.openstack.org/541290 | |
| 11:12:57 | openstackgerrit | Ameed Ashour proposed openstack/osc-placement master: Change documentation theme https://review.openstack.org/542378 | |
| 11:28:37 | openstackgerrit | Ameed Ashour proposed openstack/osc-placement master: Change documentation theme https://review.openstack.org/542378 | |
| 11:31:56 | openstackgerrit | Merged openstack/nova master: doc: Clarify how to create your own filter https://review.openstack.org/544836 | |
| 12:33:54 | openstackgerrit | Chris Dent proposed openstack/nova-specs master: VMware: add support for live migration https://review.openstack.org/299207 | |
| 13:13:42 | openstackgerrit | Bence Romsics proposed openstack/nova master: Clarify 'capacity' in placement api-ref https://review.openstack.org/544347 | |
| 13:26:52 | openstackgerrit | Thomas Goirand proposed openstack/nova master: Python 3 fix for sphinx doc https://review.openstack.org/544956 | |
| 13:30:57 | ameeda | Hello, what do you think if I take this review and complete on it ? https://review.openstack.org/#/c/525253/ | |
| 13:48:32 | hrw | ameeda: you mean "take it, update, send for review"? | |
| 13:48:57 | hrw | ameeda: if you feel that change is needed but abandoned by original author then why not | |
| 13:48:59 | ameeda | yes | |
| 13:49:48 | hrw | ameeda: my way from 'wth is kolla' to 'kolla core reviewer' started from taking over one patch | |
| 13:49:51 | ameeda | original author doesn't do any activity from awhile "5 weeks" | |
| 13:54:42 | ameeda | hrw: I am not sure if that is legal to take this patch, I want approval, what if I comment on the bug to ask current assignee if he still working on the bug. also I am not sure about the rank of this bug. | |
| 13:55:24 | ameeda | hrw: since I have patches need for review from awhile. | |
| 13:59:30 | hrw | ameeda: do what you think. nova is foss and mia maintainer can be overriden imho with new ver of patch | |
| 14:00:43 | hrw | ameeda: sometimes during review it is easier for reviewer to send new version than comment | |
| 14:02:16 | ameeda | hrw: so you guess me to mark current patch as abandoned then upload new patch | |
| 14:02:20 | jroll | ameeda: cfriesen is the author, he is active in this channel, might as well ask him | |
| 14:02:38 | hrw | ameeda: no. | |
| 14:02:44 | ameeda | cfriesen: are you around ? | |
| 14:03:15 | hrw | ameeda: git review 525253 -d; edit, git commit --amend, git review | |
| 14:03:42 | ameeda | hrw: thanks | |
| 14:04:10 | mriedem | heh, mnaser check out https://review.openstack.org/#/c/525253/ being discussed; look familiar? | |
| 14:05:50 | ameeda | mriedem: Hello :) | |
| 14:06:21 | mnaser | mriedem: lol, well now that I’ve learned a whole lot, I can tell that shouldn’t work for scenarios involving new flow :p | |
| 14:07:07 | mnaser | I don’t think it would be a fun time to replicate all the code used in the clean up section (but maybe it could be moved out to utils somewhere and reused) | |
| 14:07:31 | mnaser | But imho transactionally It feels more correct that bdms for failed instances aren’t disappearing | |
| 14:07:32 | mriedem | mnaser: yup, that's part of my -1 | |
| 14:07:59 | mnaser | If the detach fails there should still be some sort of reference, right now there’s nothing | |
| 14:09:24 | mnaser | mriedem: as much as I’d hate to rebase the series again, should we add a release note for operators that “hey, if you have a lot of failed scheduled instances, your bdm table might get bigger because they’re saved now” | |
| 14:10:03 | mriedem | mnaser: those will be deleted when the failed instance is deleted | |
| 14:10:22 | mnaser | mriedem: oh okay so thats not a big impact, i guess bdms are not soft deleted | |
| 14:10:23 | mriedem | i doubt anyone would need to know that we start putting bdms in cell0 now | |
| 14:10:29 | mriedem | bdms are soft deleted | |
| 14:10:37 | mriedem | like instances and everything else (except tags) in the 'nova' table | |
| 14:10:51 | mriedem | so you'd still have to archive/purge that stuff at some point | |
| 14:10:55 | mnaser | gotcha | |
| 14:11:59 | mnaser | anyways, whole series is ready to be reviewed (and i don't think i have a lot of review karma saved up for my lack of nova reviews to use :p) | |
| 14:12:22 | mriedem | i've got +2s on the first 3 | |
| 14:12:25 | mnaser | it's causing a ton of annoyance for some customers because they cant delete their volumes | |
| 14:12:37 | mriedem | there is a force detach in cinder | |
| 14:12:50 | mnaser | afaik thats an admin op | |
| 14:13:01 | mriedem | yeah maybe | |
| 14:13:57 | mriedem | yup it's an admin action by default os-force_detach | |
| 14:14:01 | mriedem | http://git.openstack.org/cgit/openstack/cinder/tree/cinder/api/contrib/admin_actions.py#n203 | |
| 14:14:08 | mnaser | anyways no worries, i know the first 3 are much more simple, the last one is the tough one but i'm ready to pick up any other work that comes on top so ping me if anything :> | |
| 14:22:46 | efried | melwitt: I have to duck out of the nova meeting around quarter after, FYI. On the hook for school runs again. | |
| 14:44:11 | jaypipes | bauzas: would you mind pinging sahid to hop on #openstack-nova please? just for a few minutes. have a question for him.. | |
| 14:44:25 | bauzas | sure, lemme try ;) | |
| 14:44:37 | jaypipes | merci | |
| 14:44:59 | bauzas | mmm, he's not on our internal IRC, lemme verify if he has some PTO | |
| 14:48:50 | jaypipes | bauzas: ok, no worries. | |
| 14:49:08 | bauzas | jaypipes: well, I don't see any PTO on our agenda | |
| 14:49:24 | jaypipes | bauzas: danpb isn't available is he? | |
| 14:50:03 | jaypipes | bauzas: specifically, I am looking to find out whether Dan's comment here: https://review.openstack.org/#/c/527631/9/nova/virt/libvirt/driver.py@a4299 (that was removed by tetsuro) is still valid. | |
| 14:50:18 | bauzas | jaypipes: I can ask danpb to go here | |
| 14:50:25 | jaypipes | bauzas: cool, cheers :) | |
| 14:50:34 | bauzas | even if he's no longer working on nova | |
| 14:52:36 | stephenfin | jaypipes: kashyap is the person to ask about that | |
| 14:52:47 | stephenfin | Far as I know, that comment is still valid. We've got support or emulator threads enabled but not IO threads | |
| 14:53:02 | kashyap | And clicks on the URL | |
| 14:53:03 | stephenfin | However, iirc, kashyap was in talks where the value of IO threads was called into question | |
| 14:53:22 | stephenfin | Well, IO threads > 1 anyway | |
| 14:53:35 | kashyap | stephenfin: jaypipes: (I have a discussion for it (IO Threads at Dublin too) | |
| 14:53:38 | kashyap | That said... | |
| 14:55:06 | kashyap | Yeah, the IO Threads value is in contention | |
| 14:55:33 | kashyap | Recently, I saw a presentation at KVM Forum where someone from oVirt claimed the "ideal" number of IO Threads is ...1! | |
| 14:55:37 | kashyap | (In their benchmarks) | |