Earlier  
Posted Nick Remark
#openstack-nova - 2017-04-13
11:31:36 voelzmo I guess this might be the one https://blueprints.launchpad.net/nova/+spec/userdata-modification
11:32:11 openstackgerrit Bryan Song proposed openstack/nova master: Migrate VMs failed when anti-affinity group was removed from VMs. https://review.openstack.org/451664
11:35:43 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Don't deprecate the 'live_migration_uri' https://review.openstack.org/456571
11:35:44 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Convert 'live_migration_inbound_addr' to HostAddressOpt https://review.openstack.org/456573
11:35:44 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Gather 'live_migration_scheme', 'live_migration_inbound_addr' https://review.openstack.org/456572
11:35:57 sfinucan johnthetubaguy, pkoniszewski, owalsh: ^
11:43:56 openstackgerrit Lee Yarwood proposed openstack/nova master: encryptors: Switch to os-brick encryptor classes https://review.openstack.org/391597
11:45:35 openstackgerrit Bryan Song proposed openstack/nova master: Migrate VMs failed when anti-affinity group was removed from VMs. https://review.openstack.org/451664
11:50:45 EmilienM hey folks, this patch is really critical for TripleO CI to run correctly again: https://review.openstack.org/#/c/456227/
11:51:04 openstack Launchpad bug 1682001 in tripleo "[promotion] nova hypervisors/detail fails when host is not mapped to any cell" [Critical,In progress] - Assigned to Oliver Walsh (owalsh)
11:51:04 EmilienM https://bugs.launchpad.net/tripleo/+bug/1682001
11:57:33 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Use plain routes list for flavors-extraspecs endpoint instead of stevedore https://review.openstack.org/456585
12:07:51 openstackgerrit NidhiMittalHada proposed openstack/python-novaclient master: Nova volume-attach doesn't care for device name https://review.openstack.org/454048
12:09:05 peter-hamilton johnthetubaguy: if you have any further questions on the cert validation spec just ping me
12:09:43 johnthetubaguy peter-hamilton: cool, I should hit that one now
12:14:22 johnthetubaguy peter-hamilton: do we want to return a 400 error when a user gives us a list of certs, but our cert checking is turned off?
12:16:23 peter-hamilton johnthetubaguy: good question; does it make sense to throw a warning and store the certs with the instance anyway?
12:17:00 johnthetubaguy peter-hamilton: I am bit worried the user would assume the cloud has done the verification, but it hasn't actually done it
12:17:04 peter-hamilton johnthetubaguy: that way cert validation could be enabled at a later date and boot would still work?
12:17:42 johnthetubaguy although we do allow folks to specify the cert list when the image doesn't require verification anyways
12:17:52 johnthetubaguy its probably more consistent to just log a warning
12:18:05 johnthetubaguy I mean the user doesn't see that I guess
12:18:08 peter-hamilton johnthetubaguy: i could go either way i think
12:18:16 johnthetubaguy peter-hamilton: honestly, me too
12:18:43 johnthetubaguy wonders which side of the fence to sit
12:18:54 peter-hamilton johnthetubaguy: should we hash this out during implementation?
12:19:35 johnthetubaguy peter-hamilton: thats probably the right call
12:20:17 peter-hamilton johnthetubaguy: i'll make a note of it for when i get to the API patches
12:26:30 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Use plain routes list for flavors-access endpoint instead of stevedore https://review.openstack.org/456589
12:31:43 openstackgerrit Yasufumi Ogawa proposed openstack/nova-specs master: Merge "Libvirt options for DPDK" https://review.openstack.org/456593
12:43:59 dane-fichter johnthetubaguy: Can you take a look at peter's spec when you get a chance? https://review.openstack.org/#/c/357151/
12:44:12 peter-hamilton dane-fichter: he's already on it :)
12:44:18 johnthetubaguy dane-fichter: yeah, have thinking through that now :)
12:44:25 dane-fichter oh lol sorry
12:44:39 johnthetubaguy no problem, its the right day to chase me down :)
12:44:53 openstackgerrit Bryan Song proposed openstack/nova master: Migrate VMs failed when anti-affinity group was removed from VMs. https://review.openstack.org/451664
12:47:14 peter-hamilton johnthetubaguy: awesome, thanks for the +2!
12:48:06 johnthetubaguy peter-hamilton: no problem, glad we are getting there, its a good feature folks need!
12:48:18 peter-hamilton johnthetubaguy: i agree :)
12:48:27 peter-hamilton johnthetubaguy: now, where is jaypipes...
12:49:12 johnthetubaguy hopefully he is having a coffee, putting on his flip flops, and about to open his laptop
12:57:40 openstackgerrit Yasufumi Ogawa proposed openstack/nova-specs master: Merge "Libvirt options for DPDK" https://review.openstack.org/456601
13:01:04 johnthetubaguy sean-k-mooney: sfinucan: any chance we could get use cases added in here quickly? https://review.openstack.org/#/c/361140
13:01:37 johnthetubaguy sean-k-mooney: sfinucan: something to describe the scenario(s) where each type of behaviour is what you want
13:01:37 sfinucan johnthetubaguy: Sure. Gimme 10
13:02:12 johnthetubaguy sfinucan: sweet, I have got all confused after re-reading them, particular around the good points cdent raised in there
13:06:33 sfinucan johnthetubaguy: Dumb question, but is there another name of the service that boots a VM other than 'nova-compute'?
13:07:13 johnthetubaguy sfinucan: hmm, duno really, n-cpu?
13:07:19 sfinucan i.e. we'd say "the scheduler" rather than 'nova-scheduler'
13:07:30 johnthetubaguy "the compute node" gets used a bit
13:07:37 johnthetubaguy or host
13:07:51 johnthetubaguy or just "in compute"
13:08:03 johnthetubaguy not sure thats a good thing though
13:09:01 sfinucan maybe I should just use nova-compute and nova-scheduler consistently instead
13:14:17 johnthetubaguy sfinucan: I guess thats always clear
13:17:12 bauzas sfinucan: if you talk about a running service having a RPC MQ, it's nova-compute
13:17:25 bauzas sfinucan: if you talk about an hypervisor, it's a node
13:37:04 peter-hamilton jaypipes: if you have any questions on cert validation just ping me
13:37:28 jaypipes peter-hamilton: will do. was on PTO yesterday. catching up today.
13:38:55 mriedem johnthetubaguy: as you probably saw i marked up your remove scope check patch, let me know if you want to talk about it
13:39:32 johnthetubaguy mriedem: so I didn't see that, looking now
13:39:41 mriedem you might want to sit down
13:40:02 johnthetubaguy funny you say that, I just adjusted my desk to sit down mode
13:45:07 artom For tagged attach, I need to invalidate the metadata API's cache - however, as far as I can tell, its cache is just a dict local to that process.
13:45:42 artom I'm trying to thinking of a good way to solve that, without suddenly requiring all deployment to run memcache.'
13:46:07 bauzas jaypipes: in case you have some brain time free, I'd love to get your insights on https://review.openstack.org/#/c/450122/15
13:46:53 bauzas jaypipes: my biggest concern is how a virt driver can return a single dict for a common RC if it has two distinct devices behind it
13:47:04 bauzas unless it's not really a problem and then meh.
13:48:04 mriedem artom: i wonder if we could set a flag in the db to signal when the cache should be dumped
13:48:30 mriedem and only look it up when requesting a version new enough for the tagged attach stuff,
13:48:37 mriedem although i think with config drive that would be every time
13:48:38 artom mriedem, it's not in the DB anywhere...
13:48:47 mriedem artom: i know
13:48:52 openstackgerrit Stephen Finucane proposed openstack/nova-specs master: PCI NUMA Policies https://review.openstack.org/361140
13:48:59 sfinucan johnthetubaguy: &
13:49:03 mriedem artom: is the cache per instance?
13:49:11 mriedem i'm not terribly familiar with this
13:49:13 artom mriedem, I think it's per process
13:49:14 johnthetubaguy sfinucan: cool, queued it
13:49:14 artom https://github.com/openstack/nova/blob/master/nova/cache_utils.py
13:49:32 sfinucan Also: cdent, sean-k-mooney, snikitin_, sgordon - https://review.openstack.org/361140
13:49:45 sfinucan I went with required, preferred and legacy
13:49:57 artom mriedem, the metadata handler calls get_client(), which, depending on conf, configures a cache region in a certain way
13:50:32 artom It's using dogpile.cache, in which a region is basically a frontend/client: https://dogpilecache.readthedocs.io/en/latest/usage.html
13:50:38 sfinucan jaypipes: You don't get to escape either :P https://review.openstack.org/361140
13:51:07 cdent ha
13:51:11 artom And I think the backend is basically a dict: https://github.com/openstack/oslo.cache/blob/master/oslo_cache/backends/dictionary.py
13:51:50 artom So unless the REST API request just happened to land on the same process that eventually handles the metadata request, we need some form of IPC
13:52:44 mriedem artom: default cache is just in-memory per process dict?
13:52:51 mriedem i think it's dogpile yeah?
13:52:59 artom mriedem, that's what I gather, yeah
13:55:02 mriedem well this is a sticky wicket
13:55:19 mriedem we have to look up an instance when it's not cache, or the cache is expired
13:55:48 mriedem i was thinking we could have set a flag in instance_extra that would tell metadata api to refresh the cache, but that defeats the purpose because you have to do the db lookup to find out
13:56:26 mriedem default cache expiration is 15 seconds right?
13:56:48 snikitin_ sfinucan: wow. Thank you for update! btw 'legacy' looks good because this behavior it really a little bit strange
13:56:57 mriedem does the guest need to see the tagged block device immediately?
13:57:10 artom mriedem, ah, you're saying just wait it out?
13:57:13 frickler mriedem: regarding your ML question, johnthetubaguy has a patch up to clarify things: https://review.openstack.org/#/c/438887/3
13:57:17 mriedem artom: that's what i'm asking

Earlier   Later