Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-02-09
17:08:57 openstackgerrit John Garbutt proposed openstack/nova master: Use admin context to create neutron ports https://review.openstack.org/357540
17:12:06 openstackgerrit John Garbutt proposed openstack/nova master: Use admin context to create neutron ports https://review.openstack.org/357540
17:14:06 openstackgerrit John Garbutt proposed openstack/nova master: Use admin context to create neutron ports https://review.openstack.org/357540
17:37:56 oomichi johnthetubaguy: hi, can you take a look at https://review.openstack.org/#/c/389338 again ? I replied your question
17:42:14 openstackgerrit Maxim Nestratov proposed openstack/nova-specs master: libvirt: reintroduce runtime image type detection https://review.openstack.org/363547
17:43:22 openstackgerrit John Garbutt proposed openstack/nova master: Assume neutron port_binding extensions enabled https://review.openstack.org/357726
17:44:57 openstackgerrit John Garbutt proposed openstack/nova master: Use admin context to create neutron ports https://review.openstack.org/357540
17:45:59 openstackgerrit melanie witt proposed openstack/nova master: Request zero root disk for boot-from-volume instances https://review.openstack.org/428481
17:46:00 openstackgerrit melanie witt proposed openstack/nova master: Claim and report zero root disk for boot-from-volume instances https://review.openstack.org/428505
17:53:00 openstackgerrit Andreas Jaeger proposed openstack/nova master: Prepare for using standard python tests https://review.openstack.org/429391
17:54:11 cdent jaypipes, edleafe: I'm on PTO tomorrow. If one of you is feeling inspired on the resource providers update front, please do one.
17:54:49 jaypipes cdent: unfortunately, I won't have the time to do it :(
17:54:56 jaypipes edleafe: would you have the bandwidth?
17:55:45 cdent jaypipes: no worries. I was hoping to do it this evening, but getting https://review.openstack.org/#/c/421846/ ready used up all my capacity for processing
17:55:46 dansmith we should merge this now that pike is open, before we land any other migrations: https://review.openstack.org/#/c/427900/
17:56:00 edleafe jaypipes: cdent: yes
17:56:06 cdent edleafe++
17:56:20 jaypipes edleafe: thank you Ed, I appreciate that very much.
17:56:23 cdent thanks
17:57:16 cdent I'm offf to birmingham to see my son before he heads off to southeast asia for a few months. He'll probably end up deciding not to come back to the western world. (I wouldn't)
17:59:06 edleafe jaypipes: Anything in particular besides https://review.openstack.org/#/c/404472/ ?
18:00:35 jaypipes edleafe: not from me, no. I need to get that rebased, along with the entire nested resource providers series.
18:00:49 jaypipes edleafe: also, need to work on traits bp/spec and PoC reviews before PTG
18:01:08 edleafe jaypipes: roger that
18:01:24 cdent edleafe: my usual strategy (if you're talking about the update email) is look for patches from the usual suspects that appear to be related, and then look at any pending specs, and then see what bugs tagged placement or scheduler are being worked on
18:02:38 mriedem johnthetubaguy: if you go through the multiattach nova spec again before the ptg, we should maybe highlight some sticky points from that for discussion
18:02:45 mriedem like i think evacuate, upgrade,
18:02:58 mriedem something about changing status on the attachment from the nova side which i disagreed with
18:04:06 johnthetubaguy mriedem: thats a good idea, get a list of sticking point
18:05:56 mriedem sdague: i can use your local_conf builder in project-config now right? it just won't do anything until the d-g changes are in
18:09:42 cfriesen can someone explain why we need to check "if 'id' in self" in objects/flavor.py? Do we not populate the "id" field when retrieving from the api DB?
18:10:35 mriedem has to do with the api db lookup doesn't it?
18:12:43 melwitt id gets generated only after a create(). so if a flavor object wasn't looked up and hasn't yet been create()'d, it won't have 'id'
18:13:10 dansmith all of this needs to diaf now
18:13:24 dansmith it's long since unused
18:13:37 cfriesen dansmith: I'm in newton
18:13:47 mriedem but...when i upgrade directly from mitaka to pike...i might need this to work dansmith
18:14:02 dansmith mriedem: oh well in that case, I'll kill it right now
18:14:13 mriedem cfriesen: melwitt answered your question
18:14:21 mriedem cfriesen: and dansmith is talking about killing it in pike
18:14:41 cfriesen melwitt: thanks. yes, killing in pike is fine.
18:15:24 mriedem well i know what dan is going to be doing later today
18:16:30 dansmith s/later today/right fucking now/
18:30:53 openstackgerrit Maciej Szankin proposed openstack/nova master: A demo script for updating resource inventory https://review.openstack.org/382613
18:51:36 mriedem raj_singh: johnthetubaguy: fyi https://review.openstack.org/#/c/431713/
18:53:22 openstackgerrit Diana Clarke proposed openstack/nova master: Fix nova-manage cell_v2 metavar strings https://review.openstack.org/431714
18:58:51 raj_singh mriedem: nice, thx
18:59:20 dansmith have I mentioned that I hate flavors?
18:59:28 EmilienM I hate discover_hosts command
18:59:37 EmilienM and the fact you need to run it manually for big clouds
19:00:17 EmilienM we are having hard time in tripleo to understand when to run it (at the end of deployment I guess) but it's racy because we can't control the nova-compute registration
19:03:26 EmilienM dansmith: do you know how many time (roughly) would take a discover_hosts with ~100 hosts?
19:03:32 mriedem EmilienM: then enable the auto discovery in the scheduler
19:03:45 openstackgerrit Anusha Unnam proposed openstack/nova master: Disassociate floating ip when fixed ip is removed https://review.openstack.org/350299
19:03:54 dansmith EmilienM: loading 100 rows from the database is pretty fast
19:04:14 EmilienM mriedem: it's not suggested by nova if I read the code
19:04:26 mriedem EmilienM: i think that means like CERN
19:04:40 mriedem 10's of thousands of hosts
19:04:43 mriedem but dansmith can correct me
19:05:02 dansmith mriedem: nah, fewer per cell
19:05:09 dansmith mriedem: a few hundred at most I think
19:05:12 mriedem oh right
19:05:18 EmilienM mriedem: https://github.com/openstack/nova/blob/master/nova/conf/scheduler.py#L138-L143
19:05:19 dansmith which at host add time is.. not a problem
19:05:52 mriedem i'd think 100 hosts per cell is small enough
19:06:00 mriedem but i assume there is also some hedging in there
19:06:03 mriedem given it came in late
19:06:09 EmilienM dansmith: would it be acceptable in TripleO / Director to use discover_hosts_in_cells_interval ?
19:06:24 EmilienM you can say no, but I need to find another way to run this command after all computes are run then
19:06:36 dansmith EmilienM: I think you'll just race with it, and I don't understand why you can't run this after everything is setup
19:07:06 mriedem tripleo doesn't have some kind of post-deploy hook?
19:07:13 EmilienM dansmith: because nova-compute start at step 5 (last step)
19:07:20 mriedem so add a step 6?
19:07:34 EmilienM that's an option but it adds runtime in deployment
19:08:28 EmilienM mriedem: we have post-deploy
19:08:40 EmilienM mriedem: we're currently investigating if it fits in there
19:16:14 cfriesen does nova handle modifying extra-specs on flavors that are currently in-use by instances? If so, is there any way to retrieve the flavor extra specs that were actually used to boot a given instance?
19:25:14 mriedem cfriesen: the flavor, along with it's extra specs, are stored with the instance after it's created
19:25:19 mriedem in the instance_extra table
19:25:28 mriedem so you can delete the original flavor and still resize/migrate the instance
19:26:06 mriedem cfriesen: as for the 2nd part of your question, i think you can pull deleted flavors if you're an admin
19:26:31 mriedem i.e. i think you get the flavor id via the server GET, and then can GET /flavors/id
19:26:36 mriedem which will read deleted flavors
19:26:55 mriedem but you have to be admin to read deleted flavors
19:28:15 cfriesen mriedem: if I boot an instance with a flavor, then admin changes extra specs on that flavor, is there any way for me to dump the extra-specs that were used when I booted the instance?
19:29:10 mriedem cfriesen: not via the REST API i don't think so
19:29:16 mriedem we had a spec proposed in mitaka for this...
19:29:18 mriedem i'll dig it up
19:29:21 openstackgerrit Dan Smith proposed openstack/nova master: Remove main_db flavor compatibility https://review.openstack.org/431722
19:29:51 mriedem cfriesen: https://review.openstack.org/#/c/265282/
19:30:05 mriedem basically i think the idea was, add GET /servers/<server_id>/flavor
19:30:37 mriedem cfriesen: mayhap you want to dust that off for pike
19:31:56 cfriesen mriedem: sweet, thanks.
19:32:46 mriedem let me know if you want me to restore that
19:33:43 openstackgerrit Ken'ichi Ohmichi proposed openstack/nova master: Remove unused validation code from block_device https://review.openstack.org/410006
19:34:13 cfriesen mriedem: I'll have to talk to some folks here. looks useful though.
19:34:33 mriedem cfriesen: it might be easier than whatever fork you're cooking up :)
19:35:15 openstackgerrit Artom Lifshitz proposed openstack/nova master: Use unique volume id in fake_volume https://review.openstack.org/431723
19:35:15 openstackgerrit Artom Lifshitz proposed openstack/nova master: Run api sample tests against 2.latest https://review.openstack.org/430352
19:36:12 cfriesen mriedem: we've got a longstanding private patch to prevent deleting or modifying flavors that are in-use, was just wondering if it was worth porting it. I like that spec better long-term.

Earlier   Later