Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-23
21:27:56 mriedem i'll look for the d-g code
21:28:01 andreaf mriedem oh, right
21:28:07 andreaf mriedem I missed that in d-g
21:28:24 mriedem https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L783
21:28:28 mriedem andreaf: ^
21:28:34 mriedem d-g would run discover_hosts after the subnode was setup
21:28:48 mriedem so you'll need an ansible task to run discover_hosts on the primary node once the subnode is setup
21:28:50 mriedem that should do the trick
21:29:24 andreaf mriedem heh the one line I did not port to ansible!
21:29:48 andreaf mriedem I guess I kind of assumed cells did not matter for the base job :( but it's cells v2
21:29:50 mriedem mnaser: need to fix the commit message
21:29:58 mriedem cells v2 is king
21:30:11 andreaf mriedem cool thanks a lot, much appreciated!!
21:30:11 mnaser oops
21:30:15 mriedem yw
21:31:02 andreaf mriedem # NOTE(mriedem): We want to remove this if/when nova supports auto-registration of computes with cells, but that's not happening in Ocata.
21:31:12 mnaser ok fixed the commit msg, andreaf i'd borrow your +2 back please https://review.openstack.org/#/c/547431/ :)
21:31:18 andreaf mriedem I guess it's not happening in pike or queens either :D
21:31:25 mnaser s/Ocata/a while/
21:31:59 andreaf mnaser +2
21:32:08 mnaser thank you
21:33:21 mriedem andreaf: right
21:34:01 mriedem andreaf: also we don't run discover_hosts from the subnode because it's not configured to have access to the nova_api db
21:34:03 mriedem on purpose
21:34:48 mriedem we want to make sure that when people like leakypipes try to add code to nova-compute that hits the API it blows up :P
21:47:16 leakypipes mriedem: ha. ha.
21:52:43 cfriesen if we tell nova to boot an instance (specifying that we want interfaces on two networks), then the instance fails to start, so we reschedule to another node, would we expect to re-use the ports that were created for the first compute node?
21:58:59 cfriesen answering my own question, based on a comment in ComputeManager._build_networks_for_instance() the answer seems to be "yes"
21:59:08 cfriesen or at least "maybe"
#openstack-nova - 2018-02-24
02:27:46 openstackgerrit Matt Riedemann proposed openstack/nova master: Check for leaked server resource allocations in post_test_hook https://review.openstack.org/538510
03:22:01 Spazmotic Morning
03:43:55 openstackgerrit Merged openstack/nova master: [Placement] Invalid query parameter could lead to HTTP 500 https://review.openstack.org/539408
03:44:09 openstackgerrit Merged openstack/nova master: [placement] Add functional tests for traits API https://review.openstack.org/524094
04:09:37 alex_xu cfriesen: it is yes, but will remove the port for sriov https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1873
04:49:06 openstackgerrit Merged openstack/nova stable/ocata: Don't update RT in _allocate_network https://review.openstack.org/519943
06:49:58 WangShuaili When does nova-lifecycle-event trigger
08:45:09 openstackgerrit Tetsuro Nakamura proposed openstack/nova-specs master: Support shared and dedicated VMs in one host https://review.openstack.org/543805
#openstack-nova - 2018-02-25
02:52:18 Guest1511 Nickserv you being hateful over there?
02:58:01 Guest1511 Whew Freenode services are super grumpy
02:58:39 Spazmotic Morning folks.
11:13:54 melwitt mriedem: do you know anything about py3 support in osc-placement? dhellman was asking about it, said it claims support in the classifiers but he didn't see any py3 jobs configured for it
11:18:52 mriedem there isn't a job for it, i added that to the ptg etherpad
11:19:02 mriedem should be easy to add, i can work something up, in doug's honor
11:19:10 openstack Launchpad bug 1751564 in OpenStack Dashboard (Horizon) "unable to attach multiattach volume to server" [Undecided,New]
11:19:10 mriedem ildikov: fyi https://bugs.launchpad.net/horizon/+bug/1751564
11:19:28 mriedem if you know any horizon people
11:34:23 openstackgerrit Matt Riedemann proposed openstack/osc-placement master: Enable py35 unit and functional test jobs https://review.openstack.org/547809
11:34:24 mriedem melwitt: ^
11:38:04 melwitt mriedem: cool, thanks
12:04:07 openstackgerrit Matt Riedemann proposed openstack/osc-placement master: Enable py35 unit test job https://review.openstack.org/547809
12:10:14 openstackgerrit Matt Riedemann proposed openstack/osc-placement master: Migrate legacy-osc-placement-dsvm-functional job in-tree https://review.openstack.org/547812
12:25:49 openstackgerrit Matt Riedemann proposed openstack/osc-placement master: Add osc-placement-dsvm-functional-py3 job https://review.openstack.org/547815
12:38:12 Spazmotic Quiet in here tonight but forgot it's a sunday morning hehe
12:38:23 Spazmotic Night shift things~
15:29:00 openstackgerrit Merged openstack/nova stable/ocata: Fix instance lookup in hide_server_addresses extension https://review.openstack.org/518997
15:29:36 openstackgerrit Merged openstack/nova stable/ocata: Lazy-load instance attributes with read_deleted=yes https://review.openstack.org/545989
16:36:41 openstackgerrit Matt Riedemann proposed openstack/osc-placement master: Add osc-placement-dsvm-functional-py3 job https://review.openstack.org/547815
16:46:53 bauzas mriedem: melwitt: I was considering the opportunity whether to write a spec for tracking the last bits of vGPU effort but it would be only fixing the caveats that we already describe
16:47:06 bauzas mriedem: melwitt: do you think we should consider a specless BP approval ?
16:47:31 bauzas no real new features in Rocky are planned from my PoV except maybe NUMA affinity for vGPUs
16:47:46 bauzas the latter would describe a spec I guess
16:47:53 bauzas s/describe/require
16:49:29 mriedem if there are no api changes, then fixing caveats for vgpu scenarios are probably just bug fixes
16:50:48 bauzas mriedem: well, bugfixes require bug reports, I wonder if a blueprint would be better for those caveats (like say the migrate case which is not available yet)
16:50:57 bauzas but I can open bugs
16:51:14 bauzas for the NUMA affinity, I think a spec is required anyway
16:51:30 bauzas at least for discussing on the design
16:51:41 bauzas okay, I think I have my answer :)
16:51:48 bauzas thanks
16:51:50 mriedem are you not in a room with a bunch of people that could answer this question?
16:52:32 bauzas heh, upstream is upstream, downstream is downstream :p
16:53:00 bauzas while those people could have an idea, I tend to ask upstream things related upstream :)
16:56:53 openstackgerrit Takashi NATSUME proposed openstack/nova stable/queens: [placement] Add functional tests for traits API https://review.openstack.org/547843
17:48:33 openstackgerrit Ghanshyam Mann proposed openstack/nova-specs master: Spec for Granular API policy https://review.openstack.org/547850
18:04:54 openstackgerrit Ghanshyam Mann proposed openstack/nova-specs master: Spec for Granular API policy https://review.openstack.org/547850
#openstack-nova - 2018-02-26
09:17:25 dansmith melwitt: we really need to merge this before anyone else has a chance to propose something for compute RPC: https://review.openstack.org/#/c/543580/
09:21:03 mriedem johnthetubaguy: are you in the unified limits room?
09:22:14 hrw who is on PTG?
09:22:18 hrw morning
09:25:35 melwitt dansmith: k, looking
09:34:01 jaypipes alex_xu, https://review.openstack.org/543805
09:41:31 johnthetubaguy mriedem: yes
09:41:33 johnthetubaguy ttsiouts: are you in the limits room?
09:45:04 ttsiouts johnthetubaguy: no i'm in the public clouds
09:46:46 johnthetubaguy ttsiouts: I may be saying you are willing to work on quota
09:47:10 ttsiouts johnthetubaguy: yeap!
09:48:01 jaypipes johnthetubaguy, which is the "limits room"?
09:49:25 TheJulia jaypipes: level 4, right off the stairs
09:50:13 johnthetubaguy jaypipes: identity something Hogan Maezz 1 L4
09:50:24 johnthetubaguy ah, what TheJulia said
10:09:21 openstackgerrit Tetiana Lashchova proposed openstack/nova-specs master: Allow modification of user-data via the server update https://review.openstack.org/547964
10:14:04 openstackgerrit Tetiana Lashchova proposed openstack/nova-specs master: Allow modification of user-data via the server update https://review.openstack.org/547964
10:14:29 dayou With a fresh devstack I get this: Host 'ubuntubox' is not mapped to any cell.
10:15:20 dayou After "enable_service n-cell" and "VIF_PLUGGING_TIMEOUT=0 VIF_PLUGGING_IS_FATAL=False ", I was able to start an instance.
10:15:46 dayou Somehow, I tried other serivces such as octavia, it failed to plug vip there, a 500 is back from nova-api
10:16:58 dayou https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/attach_interfaces.py#L156
10:17:04 dayou From the line above
10:17:40 melwitt dayou: you shouldn't be using the n-cell service, that's the legacy cells v1 that has an extremely crippled API functionality
10:17:52 dayou Here is my local.conf: https://review.openstack.org/#/c/520878/5/devstack/samples/l3a2/local.conf
10:19:29 dayou melwitt, Any idea why I get the Host 'xxx' is not mapped to any cell problem?

Earlier   Later