Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-03-19
10:38:58 diranerpi So for example, if in my instance data i create a metadata like "service = database", i want this instance to be deployed on a specific aggregate host
10:39:14 diranerpi johnthetubaguy: So for example, if in my instance data i create a metadata like "service = database", i want this instance to be deployed on a specific aggregate host
10:50:23 openstackgerrit Silvan Kaiser proposed openstack/nova master: Exec systemd-run with privileges in Quobyte driver https://review.openstack.org/554195
10:54:31 openstackgerrit Chris Dent proposed openstack/nova master: WIP: Ensure that os-traits sync is attempted only at start of process https://review.openstack.org/553857
11:09:25 johnthetubaguy bhagyashris: hi
11:09:50 johnthetubaguy bhagyashris: that sounds spot on
11:17:47 bhagyashris johnthetubaguy: ok thank you :) actually cleanup-backup api will purge all the backup images of instance so is that be ok? or should i give the provision to cleanup the backup images for example cleanup last two backups etc?
11:24:10 bhagyashris johnthetubaguy: and on current master at the time of createbackup the delete image backup is implementated so should i remove that implementation from create backup so should i kept it as it is?
11:32:18 gibi melwitt: regarding the nova onboarding session in Vancouver. I can only give a tentative yes as my company haven't approved my travel yet.
11:39:32 kashyap Is it just me, fetching from: https://git.openstack.org/openstack/nova.git fails?
11:42:14 kashyap It's just me
11:42:31 cdent works for me
11:44:13 kashyap Fir me, it's just hung here:
11:44:20 kashyap Running: `GIT_CURL_VERBOSE=1 GIT_TRACE=1 git pull`
11:44:22 kashyap http://paste.openstack.org/show/704380/
11:54:05 johnthetubaguy bhagyashris: the old API has to keep working like it does today
11:55:25 johnthetubaguy kashyap: you tried doing http rather than https?
11:55:45 kashyap johnthetubaguy: I tried all three, git, https, http.
11:55:49 kashyap None works for me, bizarrely
11:55:50 johnthetubaguy bummer
11:56:56 bhagyashris johnthetubaguy: ok . i just need to add the functionality of roatation parameter value 0 in cleanup backup api right?
11:57:54 johnthetubaguy bhagyashris: yes, that sounds correct. Will be easier to review the spec with all the details, to make sure I haven't missed a bit :)
11:59:09 bhagyashris johnthetubaguy: ok thank you for your inputs will upload spec ASAP :)
11:59:33 johnthetubaguy bhagyashris: no problem, sounds good
12:24:19 openstackgerrit Theodoros Tsioutsias proposed openstack/nova-specs master: Add PENDING vm state https://review.openstack.org/554212
12:28:42 openstackgerrit Chris Dent proposed openstack/nova-specs master: Provide error codes for placement API https://review.openstack.org/418393
12:55:08 openstackgerrit Theodoros Tsioutsias proposed openstack/nova-specs master: Enable rebuild for instances in cell0 https://review.openstack.org/554218
13:29:34 openstackgerrit Matt Riedemann proposed openstack/nova master: Add VIFMigrateData object for live migration https://review.openstack.org/515423
13:29:35 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: libvirt: use dest host vif migrate details for live migration https://review.openstack.org/551370
13:29:35 openstackgerrit Matt Riedemann proposed openstack/nova master: Port binding based on events during live migration https://review.openstack.org/434870
13:29:36 openstackgerrit Matt Riedemann proposed openstack/nova master: Add "delete_port_binding" network API method https://review.openstack.org/552170
13:29:36 openstackgerrit Matt Riedemann proposed openstack/nova master: compute: use port binding extended API during live migration https://review.openstack.org/551371
13:29:37 openstackgerrit Matt Riedemann proposed openstack/nova master: conductor: use port binding extended API in during live migrate https://review.openstack.org/522537
13:29:37 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Turn on new port binding extended live migrate flow https://review.openstack.org/552173
13:30:32 openstackgerrit Zhenyu Zheng proposed openstack/nova master: nova-manage db archive_deleted_rows is not multi-cell aware https://review.openstack.org/507486
13:44:01 kaisers1 efried: Hi! Regarding https://review.openstack.org/#/c/554195/ : I looked into using privsep but as the spec says true root user context will continue to use rootwrap i went with that. If privsep does offer a root execution mechanism i can go that way. Do you have a hint on docs/examples of that for me?
13:45:11 efried kaisers1: mikal is the expert on that. I believe he's in Australia, so time zones may be a bit of a challenge. I'm sure I can at least dig up the spec for the privsep work. Stand by...
13:45:55 efried kaisers1: Meanwhile, if you want to see some examples for how mikal has transitioned existing code over to privsep: https://review.openstack.org/#/q/topic:bp/hurrah-for-privsep+(status:open+OR+status:merged)
13:47:03 dansmith kaisers1: you should be using privsep not rootwrap for new things
13:47:21 dansmith kaisers1: the whole point of privsep is to replace rootwrap, and doing so does indeed get you root escalation for your code
13:47:52 efried dansmith: Is there a spec (I can't find one) or documentation for how to use privsep?
13:48:12 dansmith efried: there's lots of code now
13:48:22 kaisers1 I did read the spec
13:48:32 kaisers1 dansmith: thanks for the inputs!
13:48:47 efried kaisers1: For my edification, where did you find that spec?
13:49:00 kaisers1 efried: https://specs.openstack.org/openstack/oslo-specs/specs/liberty/privsep.html
13:49:04 dansmith privsep was born of lots of conversation and design, I'm sure there are things to read, but I expect a lot of the formal documentation focuses on capability contexts, which we've short-circuited to a single root one,
13:49:07 efried ah, in oslo.
13:49:10 dansmith so it may be more reading than you need
13:49:40 efried So yeah, kaisers1 you may do best following the code examples I linked above.
13:50:05 kaisers1 efried: will do, thanks!
13:50:09 dansmith definitely
13:50:10 efried enjoy
13:54:22 jaypipes ugh, the warnings barfed out in py36 test runs is getting ridiculous.
13:55:09 edleafe Scheduler subteam meeting in 5 minutes in #openstack-meeting-alt
13:55:53 cdent jaypipes: fun, isn't it?
13:57:04 tssurya dansmith: I am really sorry about this accidental rebase : https://review.openstack.org/#/c/553831/; could you please rebase it to the right topic before someone +W's it ?
13:57:44 jaypipes cdent: makes it very annoying to run tests.
13:58:16 cdent jaypipes: I keep meaning to find some to fix and then forget for whatever reason
13:58:50 dansmith tssurya: it doesn't really matter
13:59:16 tssurya dansmith: ok, yea still sorry
13:59:42 dansmith tssurya: it's not a problem, gerrit-review does that
13:59:58 dansmith tssurya: in the future -R will prevent you from rebasing the thing underneath you if you intentionally don't want it to move
14:00:29 tssurya dansmith: yep will keep that in mind next time
14:00:33 tssurya thank you
14:00:38 dansmith np
14:05:04 Maddy Hello, I was hitting this bug https://bugs.launchpad.net/nova/+bug/1717547 and I see that the workaround for that is not using the image parameters name as 'version', 'context' and 'method'.
14:05:05 openstack Launchpad bug 1717547 in OpenStack Compute (nova) "Creating snapshot fails when image metadata has version field" [Low,Confirmed]
14:05:14 Maddy This is not good because the user needs to be aware of that. One solution is make Glance to deny use of these parameters name on it's images. Other solution is to rename the variables in Nova 'Call' function to begin with '_' (underscore), but for that we also need to enforce Glance to now allow parameters beginning with '_' (underscore).
14:05:24 Maddy What's your thoughts about that? Any better solution? In case not, what do you think about implementing one the above solutions?
14:14:33 openstackgerrit Jay Pipes proposed openstack/nova master: tests for alloc candidates with nested and traits https://review.openstack.org/531899
14:14:33 openstackgerrit Jay Pipes proposed openstack/nova master: add test for scenario with sum of child resources https://review.openstack.org/534339
14:14:34 openstackgerrit Jay Pipes proposed openstack/nova master: _get_trees_matching_all_resources() sum children https://review.openstack.org/534866
14:14:34 openstackgerrit Jay Pipes proposed openstack/nova master: add _get_usages_from_trees() function https://review.openstack.org/534967
14:14:35 openstackgerrit Jay Pipes proposed openstack/nova master: validate provider summary structure https://review.openstack.org/536516
14:14:35 openstackgerrit Jay Pipes proposed openstack/nova master: WIP - populate alloc cands for trees https://review.openstack.org/534968
14:20:55 openstackgerrit Jay Pipes proposed openstack/nova master: tests for alloc candidates with nested and traits https://review.openstack.org/531899
14:20:55 openstackgerrit Jay Pipes proposed openstack/nova master: add test for scenario with sum of child resources https://review.openstack.org/534339
14:20:56 openstackgerrit Jay Pipes proposed openstack/nova master: _get_trees_matching_all_resources() sum children https://review.openstack.org/534866
14:20:56 openstackgerrit Jay Pipes proposed openstack/nova master: add _get_usages_from_trees() function https://review.openstack.org/534967
14:20:57 openstackgerrit Jay Pipes proposed openstack/nova master: validate provider summary structure https://review.openstack.org/536516
14:20:57 openstackgerrit Jay Pipes proposed openstack/nova master: WIP - populate alloc cands for trees https://review.openstack.org/534968
14:23:26 openstackgerrit Merged openstack/nova-specs master: Add host info to instance action events https://review.openstack.org/543277
14:27:44 jaypipes efried: ^^ I'm getting that nested providers in allocation candidates series back inline...
14:27:53 efried jaypipes: Cool dude.
14:28:33 efried Did you see my potentially earth-shattering dissenting opinion on the "split one resource across multiple providers" thing?
14:28:45 jaypipes efried: no. link?
14:29:22 efried jaypipes: https://review.openstack.org/#/c/534339/ -- my last comment, on PS5 before rebases
14:38:01 mriedem dansmith: replied in https://review.openstack.org/#/c/543277/
14:38:16 mriedem still don't see the need for hostId in the action events API, but people at the PTG wanted it
14:38:48 dansmith mriedem: I'm commenting about the rst syntax, using `` instead of "
14:40:25 mriedem oh, heh
14:40:46 mriedem i can push a doc cleanup patch on that
14:41:34 kashyap mriedem: melwitt: Heya, I've read the full chat between you both, dansmith, et al (including the quip: "besides the fix, you can also configure nova for other goodies!").
14:41:49 kashyap Not to discuss this to death, but 3 quick points:
14:42:03 dansmith mriedem: that's all I was saying :)
14:42:16 kashyap (1) I want to do the Right Thing & not rush anything in.
14:42:16 kashyap (2) The two Nova config options thing just causes untold pain for all vendors with all their unique deployment tools; and just wastes precious time all around for little gain.
14:42:20 kashyap (3) On your point: "well, what I mean is if you use it and it breaks something in queens/pike/ocata then we're probably not going to fix things to accommodate the various flags they enable" — That's a good point. Yes, we have to loudly and clearly document that "NB: There's a huge combination of CPU flags possible, just by virtue of them being available in a given CPU. It's not reasonable to
14:42:26 kashyap test all combinations; so if an Operator wants to try certain flags, it's their responsibility to test if that works in their environment".

Earlier   Later