Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-09
13:55:30 sean-k-mooney sfinucan: but cool thanks ill take a look and see
13:58:15 cdent coreycb (or anyone else): where's the right place to report an apparent bug in the the packaging (specifically the apache config) for placement api?
13:58:50 mriedem cdent: probably ubuntu/nova
13:58:59 cdent thanks mriedem
13:59:06 mriedem https://bugs.launchpad.net/ubuntu/+source/nova/+bugs ?
13:59:23 coreycb cdent, mriedem, yes that's correct
13:59:25 mriedem i'm not entirely sure, jamespage can probably help too
13:59:27 mriedem \o/
13:59:38 cdent gold star for mriedem
13:59:42 coreycb :)
13:59:52 coreycb cdent, mind forwarding that along once it's open?
14:00:02 cdent yeah, will do,
14:00:12 coreycb cdent, thanks
14:14:24 jaypipes sean-k-mooney, sfinucan: fancy a hangout to discuss this?
14:15:02 sfinucan jaypipes: The NIC feature spec, you mean?
14:18:16 jaypipes sfinucan: ya
14:18:41 sfinucan jaypipes: Sure, once the meeting is over
14:18:43 jaypipes sfinucan: because, frankly, it's more than just the NIC features.
14:31:19 openstackgerrit Lee Yarwood proposed openstack/nova master: compute: Move detach logic from manager into driver BDM https://review.openstack.org/439520
14:31:20 openstackgerrit Lee Yarwood proposed openstack/nova master: objects: Add attachment_id to BlockDeviceMapping https://review.openstack.org/437665
14:31:21 openstackgerrit Lee Yarwood proposed openstack/nova master: compute: Only destroy BDMs after successful detach call https://review.openstack.org/440693
14:34:25 sean-k-mooney jaypipes: sfinucan rodolfo will be tied up for an hour he is presenting in a meeting. but after that sure
14:34:37 jaypipes sean-k-mooney: coolio.
14:35:15 sfinucan sean-k-mooney: (y)
14:44:51 mdbooth cdent: Pinging you only because you raised it in the meeting, but fwiw I'm -1 on the patch which implements https://blueprints.launchpad.net/nova/+spec/lvm-thin-pool for 'spec type reasons'
14:45:04 mdbooth There's no spec for me to -1, though
14:45:09 gibi jaypipes: hi! Here is a fix to for the orphaning of the instance.flavor we talked about at the PTG. https://review.openstack.org/#/c/440347/ Could you check it please if you have time?
14:45:35 cdent mdbooth: yeah, I'm not up to date on any of that, was just parroting the agenda
14:45:43 mdbooth cdent: Figured
14:46:01 mdbooth mri
14:46:05 mdbooth Bleargh
14:46:10 mdbooth He's not here
14:46:20 cdent he has to parent
14:46:25 asettle johnthetubaguy: in relate to your question earlier about testing packages, there's a bit of info here: https://docs.openstack.org/contributor-guide/release/taskdetail.html
14:46:33 asettle Under "installation tutorial testing"
14:46:38 mdbooth I hate it when that happens
14:46:46 asettle TL;DR - locate pre-release packages for each distribution, and disseminate information about obtaining the packages for testing purposes.
14:49:32 mdbooth TL;DR thin pools are very similar to sparse volumes. I don't want to support both. Happy to support thin pools, but only if we deprecate sparse volumes, we have a plan to convert sparse volumes to thin pools automatically (so we don't need to support both), and it's painless for the operator.
14:49:35 lyarwood mdbooth: I'll go over it again, did you see my comment a few days ago about the current lvm.conf in F25 defaulting to using thinp with the current lvcreate commands for sparse volumes in Nova
14:49:50 mdbooth lyarwood: I did, yes.
14:50:13 mdbooth I wonder if there are any implications of mixing them in the same VG.
14:50:42 mdbooth i.e. I created these sparse LVs before that change, and these other LVs after that change, so I have a mix in the same VG.
14:51:26 lyarwood mdbooth: I assume that's fine as they wouldn't change the default otherwise right?
14:51:29 mdbooth lyarwood: Anyway, I don't object to thin pools, only supporting 2 very similar ways to do the same thing.
14:52:03 mdbooth lyarwood: Hard data would be nice.
14:52:08 lyarwood yup agreed
14:53:25 openstack Launchpad bug 1671509 in nova (Ubuntu) "placement api configuration in apache configure CustomLog incorrectly" [Undecided,New]
14:53:25 cdent coreycb: that bug https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1671509
14:54:55 jaypipes edleafe, cdent: your reviews on https://review.openstack.org/#/c/441544/ would be great. thx in advance!
14:55:07 cdent jaypipes: noted!
14:55:27 coreycb cdent, thanks we'll get that fixed up asap
14:55:36 edleafe jaypipes: queued
14:55:42 jaypipes danke
14:57:31 jaypipes mdbooth: you previously reviewed https://review.openstack.org/#/c/399679/. would be great to have a once over from you on that.
14:57:57 mdbooth jaypipes: Sure.
14:58:03 jaypipes cheers
14:58:55 asettle johnthetubaguy: further explanation, package managers test often with automatic setup and that might include updating config files
14:58:57 mdbooth jaypipes: Incidentally, I was looking for validation of this approach for handling RequestContexts for cells: https://review.openstack.org/#/c/443627/
14:59:14 mdbooth Or invalidation, obviously, which is why I haven't tried to do the whole job yet.
14:59:25 jaypipes mdbooth: k, queued.
14:59:37 mdbooth jaypipes: Thanks
15:01:30 openstackgerrit Gábor Antal proposed openstack/nova master: Add json style checking for sample notifications https://review.openstack.org/443677
15:03:05 dansmith mdbooth: I skimmed it briefly
15:03:28 dansmith mdbooth: I think we can go with that approach for things for object contexts, where we iterate over multiple cells
15:03:36 dansmith mdbooth: I don't like it for clearly single-cell-targeted operations on an instance or a host
15:04:03 dansmith mdbooth: because after getting all of this to work, I feel confident we'll have some leaks where we don't realize that we've now got two copies of the context
15:04:06 mdbooth dansmith: Ok. So it's worth adding context.for_cell() and fixing up say get_all() and its users?
15:04:12 dansmith mdbooth: the context _is_ gobal and by reference everywhere
15:04:21 dansmith mdbooth: we get it by reference from the request
15:05:31 dansmith mdbooth: maybe, I also would want to see that change on top of a fully working tempest run of the current stack to prove it doesn't break anything else
15:05:59 jaypipes sfinucan: so https://review.openstack.org/#/c/399653/is going to require the gate to have libvirt 1.2.9
15:06:01 mdbooth dansmith: That was another reason I didn't want to go all the way down this rabbit hole. I expect there are a bunch of tricky cases.
15:06:12 dansmith mdbooth: there are a ton
15:06:31 mdbooth dansmith: However, I was hoping that by removing the whole side-effect of changing the global context there might be significantly less
15:06:41 dansmith mdbooth: I think you might be surprised
15:07:03 sfinucan jaypipes: I thought the point of those tests was to fake out libvirt?
15:07:12 mdbooth dansmith: Ok, I'll limit to get_all() initially and see how it looks.
15:07:14 mdbooth Thanks for looking.
15:07:28 jaypipes sfinucan: see the functional test failure :)
15:07:30 cdent coreycb: I think I've got another one. Is it considered a bug for the service.conf files to have uncommented config settings?
15:08:11 coreycb cdent, not necessarily. some of the packages set defaults.
15:08:24 sfinucan jaypipes: Well that doesn't look right :D
15:08:36 cdent coreycb: in this case it is that os_region_name in the [placement] section is being set
15:08:50 sfinucan Guess we can mock out that version check too
15:08:55 dansmith mdbooth: fwiw, we already had a discussion about whether or not to fork the context in the objects that are tied to cells and decided on this approach to start
15:09:09 dansmith mdbooth: one thing to remember is that if you send an object over rpc, it resets the context on all the objects in the stack
15:09:25 dansmith mdbooth: so if you make a call over to conductor, for anything like boot or resize, contexts get reset anyway
15:09:33 coreycb cdent, that may not need to be set. we set defaults so that the service will can start after the package is installed.
15:10:13 openstackgerrit Dan Smith proposed openstack/nova master: WIP: Temporarily untarget context when deleting from cell0 https://review.openstack.org/443403
15:10:21 cdent coreycb: the reason I noticed was because the docs I was testing changed it, i made all those changs at the top of the section, and then realized it was going to conflict with something that's set further below
15:10:47 cdent coreycb: ah, okay, yeah, that makes sense then
15:10:53 cdent it won't start without that
15:10:57 cdent (there's no default)
15:11:42 mriedem dansmith: ftr, i did give you the business, yes
15:11:44 mriedem :)
15:11:55 dansmith mriedem: yeah, I just totally wasn't paying attention when I wrote that :)
15:11:59 dansmith mriedem: see my rev
15:12:00 dansmith ?
15:13:02 mriedem yes
15:13:08 mriedem wait, what?

Earlier   Later