Thursday, 2017-08-31

*** edmondsw has quit IRC00:01
*** vladikr has quit IRC00:04
*** vladikr has joined #openstack-nova00:05
*** thegreenhundred has joined #openstack-nova00:14
*** ijw has joined #openstack-nova00:15
*** Swami has quit IRC00:15
*** ijw has quit IRC00:19
*** salv-orlando has joined #openstack-nova00:22
*** chyka has joined #openstack-nova00:22
*** chyka has quit IRC00:27
*** markvoelker_ has quit IRC00:27
*** markvoelker has joined #openstack-nova00:28
*** markvoelker has quit IRC00:28
*** Nel1x has joined #openstack-nova00:31
*** thorst_afk has joined #openstack-nova00:31
*** annegentle has joined #openstack-nova00:32
*** catintheroof has quit IRC00:35
*** Apoorva_ has quit IRC00:36
*** dtp has quit IRC00:36
*** liverpooler has joined #openstack-nova00:37
openstackgerritMatt Riedemann proposed openstack/nova master: [placement] Require at least one resource class in allocation  https://review.openstack.org/49927000:38
*** lyan has joined #openstack-nova00:38
*** markvoelker has joined #openstack-nova00:44
openstackgerritMatt Riedemann proposed openstack/nova master: Create allocations against forced dest host during evacuate  https://review.openstack.org/49939900:45
*** baoli has joined #openstack-nova00:46
*** baoli has quit IRC00:47
*** baoli has joined #openstack-nova00:48
*** markvoelker has quit IRC00:48
*** zhurong has joined #openstack-nova00:48
openstackgerritMatt Riedemann proposed openstack/nova master: Document tagged attach in the feature support matrix  https://review.openstack.org/49808600:52
openstackgerritMerged openstack/os-traits master: Updated from global requirements  https://review.openstack.org/49525500:53
*** Shunli has joined #openstack-nova00:55
*** lyan has quit IRC00:56
*** mriedem has quit IRC00:59
*** spotz has quit IRC01:00
*** phuongnh has joined #openstack-nova01:02
*** TuanLA has joined #openstack-nova01:04
*** ijw has joined #openstack-nova01:07
*** yangyapeng has joined #openstack-nova01:14
*** ijw has quit IRC01:14
*** ijw has joined #openstack-nova01:15
*** ijw has quit IRC01:20
*** Apoorva has joined #openstack-nova01:22
*** Apoorva has quit IRC01:26
*** Tom_ has joined #openstack-nova01:34
*** yangyapeng has quit IRC01:34
*** Tom_ has quit IRC01:34
*** yangyapeng has joined #openstack-nova01:35
*** spotz has joined #openstack-nova01:35
*** thorst_afk has quit IRC01:41
*** sapd has joined #openstack-nova01:42
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi: cached images should be cleaned up by time  https://review.openstack.org/46595401:43
*** markvoelker has joined #openstack-nova01:44
*** sapd has quit IRC01:49
*** hongbin has joined #openstack-nova01:50
openstackgerritHesam Chobanlou proposed openstack/nova master: add online_data_migrations to nova docs adding cli documentation for online_data_migrations to clarify when the command is complete.  https://review.openstack.org/49344201:56
*** sdague has quit IRC01:56
*** yangyape_ has joined #openstack-nova01:57
*** yangyapeng has quit IRC01:57
*** thorst_afk has joined #openstack-nova02:00
*** jmlowe has quit IRC02:00
*** jmlowe has joined #openstack-nova02:01
*** sapd has joined #openstack-nova02:02
*** litao__ has joined #openstack-nova02:02
*** catintheroof has joined #openstack-nova02:03
*** Swami has joined #openstack-nova02:06
*** markvoelker has quit IRC02:18
*** yamahata has quit IRC02:19
*** kiennt has joined #openstack-nova02:20
*** liverpooler has quit IRC02:21
*** yangyape_ has quit IRC02:28
*** yangyapeng has joined #openstack-nova02:28
*** xinliang has quit IRC02:31
*** xinliang has joined #openstack-nova02:44
*** thorst_afk has quit IRC02:45
*** thorst_afk has joined #openstack-nova02:46
*** Tom_ has joined #openstack-nova02:48
*** thorst_afk has quit IRC02:50
*** ijw has joined #openstack-nova02:56
*** gbarros has joined #openstack-nova02:59
*** ijw has quit IRC03:01
*** nicolasbock has quit IRC03:05
*** catintheroof has quit IRC03:07
*** tiendc has joined #openstack-nova03:09
*** jmlowe has quit IRC03:13
*** jmlowe has joined #openstack-nova03:14
*** markvoelker has joined #openstack-nova03:15
*** vladikr has quit IRC03:15
*** gbarros has quit IRC03:18
*** gbarros has joined #openstack-nova03:31
*** itlinux has quit IRC03:33
*** gbarros has quit IRC03:36
*** udesale has joined #openstack-nova03:37
*** links has joined #openstack-nova03:39
*** psachin has joined #openstack-nova03:43
openstackgerritMerged openstack/nova master: Updated from global requirements  https://review.openstack.org/49938903:46
*** thorst_afk has joined #openstack-nova03:47
*** markvoelker has quit IRC03:48
*** annegentle has quit IRC03:48
*** gouthamr has quit IRC03:49
*** thorst_afk has quit IRC03:51
*** vito_ has joined #openstack-nova03:53
*** vito_ has quit IRC03:54
*** chyka has joined #openstack-nova03:57
*** moshele has joined #openstack-nova04:01
*** chyka has quit IRC04:01
*** hongbin has quit IRC04:11
*** Donckers has quit IRC04:11
*** ijw has joined #openstack-nova04:16
*** yamahata has joined #openstack-nova04:18
*** ijw has quit IRC04:21
*** gbarros has joined #openstack-nova04:21
*** Tom_ has quit IRC04:23
*** baoli has quit IRC04:23
*** Tom has joined #openstack-nova04:23
*** gyee has quit IRC04:23
*** Tom has quit IRC04:27
*** bhagyashri_s is now known as bhagyashris04:28
*** zhurong has quit IRC04:29
*** gbarros has quit IRC04:29
*** itlinux has joined #openstack-nova04:35
*** salv-orlando has quit IRC04:37
*** baoli has joined #openstack-nova04:37
*** vladikr has joined #openstack-nova04:37
*** abhi89 has joined #openstack-nova04:38
*** markvoelker has joined #openstack-nova04:45
*** thorst_afk has joined #openstack-nova04:47
*** zhurong has joined #openstack-nova04:48
*** baoli has quit IRC04:49
*** itlinux has quit IRC04:52
*** thorst_afk has quit IRC04:52
*** phuongnh has quit IRC04:52
*** phuongnh has joined #openstack-nova04:53
*** armax has quit IRC04:53
*** salv-orlando has joined #openstack-nova05:09
*** ratailor has joined #openstack-nova05:18
*** markvoelker has quit IRC05:19
*** markvoelker has joined #openstack-nova05:24
*** markvoelker_ has joined #openstack-nova05:25
*** oomichi has quit IRC05:28
*** trinaths has joined #openstack-nova05:28
*** markvoelker has quit IRC05:29
*** oomichi has joined #openstack-nova05:30
*** slaweq has joined #openstack-nova05:31
*** slaweq has quit IRC05:35
*** diga has joined #openstack-nova05:36
*** sridharg has joined #openstack-nova05:38
*** slaweq has joined #openstack-nova05:41
*** slaweq has quit IRC05:42
*** yangyapeng has quit IRC05:42
*** yangyapeng has joined #openstack-nova05:43
*** markvoelker_ has quit IRC05:48
*** thorst_afk has joined #openstack-nova05:48
*** mdnadeem has joined #openstack-nova05:50
*** vvargaszte has joined #openstack-nova05:52
*** edmondsw has joined #openstack-nova05:52
*** thorst_afk has quit IRC05:53
*** diga has quit IRC05:59
openstackgerritMerged openstack/nova master: [placement] Add test for empty resources in allocation  https://review.openstack.org/49926906:01
*** jichen has joined #openstack-nova06:07
*** Oku_OS-away is now known as Oku_OS06:10
*** psachin has quit IRC06:10
*** psachin has joined #openstack-nova06:14
*** links has quit IRC06:15
*** psachin has quit IRC06:16
*** psachin has joined #openstack-nova06:16
*** vvargaszte has quit IRC06:18
*** Tom has joined #openstack-nova06:18
*** pcaruana has joined #openstack-nova06:22
openstackgerritRajesh Tailor proposed openstack/nova master: Host addition host-aggregate should be case-sensitive  https://review.openstack.org/49833406:22
*** lpetrut has joined #openstack-nova06:22
*** vladikr has quit IRC06:24
*** slaweq has joined #openstack-nova06:26
*** david-lyle has quit IRC06:28
*** david-lyle has joined #openstack-nova06:28
*** slaweq has quit IRC06:28
*** slaweq has joined #openstack-nova06:28
abhi89hey guys.. can someone please review https://review.openstack.org/#/c/485121/06:31
*** syqian has joined #openstack-nova06:31
*** shan has joined #openstack-nova06:32
*** hshiina has joined #openstack-nova06:35
openstackgerritjichenjc proposed openstack/nova master: check query param for used_limits function  https://review.openstack.org/49909106:35
*** lpetrut has quit IRC06:37
*** lpetrut has joined #openstack-nova06:38
*** syqian has quit IRC06:40
*** rcernin has joined #openstack-nova06:40
*** syqian has joined #openstack-nova06:41
*** lpetrut has quit IRC06:46
*** david-lyle has quit IRC06:47
*** dklyle has joined #openstack-nova06:47
*** thorst_afk has joined #openstack-nova06:49
*** dklyle has quit IRC06:53
*** david-lyle has joined #openstack-nova06:53
*** dpawlik has quit IRC06:53
*** thorst_afk has quit IRC06:54
*** phuongnh has quit IRC06:57
openstackgerritKevin Zhao proposed openstack/nova master: Add video type virtio for AArch64  https://review.openstack.org/49382206:57
*** phuongnh has joined #openstack-nova06:57
*** danpawlik has joined #openstack-nova06:57
*** Nel1x has quit IRC06:57
openstackgerritMerged openstack/nova master: [placement] Require at least one resource class in allocation  https://review.openstack.org/49927007:00
*** lajoskatona has joined #openstack-nova07:00
*** abalutoiu has joined #openstack-nova07:01
*** yamahata has quit IRC07:01
*** jianghuaw has quit IRC07:04
*** syqian_ has joined #openstack-nova07:04
*** hoonetorg has quit IRC07:04
*** syqian has quit IRC07:07
*** trinaths has quit IRC07:10
*** david-lyle has quit IRC07:17
*** hoonetorg has joined #openstack-nova07:17
jichenalex_xu: have time to look at https://review.openstack.org/#/c/485121/ ? seems abhi89 is eager to get it merged and backport to older release07:19
*** mnestratov has joined #openstack-nova07:23
*** Tom has quit IRC07:25
*** Tom has joined #openstack-nova07:25
*** vvargaszte has joined #openstack-nova07:27
*** ragiman has joined #openstack-nova07:28
*** links has joined #openstack-nova07:28
*** vvargaszte has quit IRC07:32
*** tesseract has joined #openstack-nova07:32
*** trinaths has joined #openstack-nova07:32
*** Tom has quit IRC07:35
*** claudiub has joined #openstack-nova07:35
*** david-lyle has joined #openstack-nova07:35
*** Tom has joined #openstack-nova07:36
*** cfriesen_ has quit IRC07:38
*** Ralgamasiel has joined #openstack-nova07:39
*** Tom has quit IRC07:40
*** Swami has quit IRC07:41
*** syqian__ has joined #openstack-nova07:41
*** jpena|off is now known as jpena07:43
*** oomichi has quit IRC07:44
*** oomichi has joined #openstack-nova07:44
openstackgerritZhenyu Zheng proposed openstack/nova master: block_device_mapping_v2.bus_type is missing from api-ref  https://review.openstack.org/49948807:44
*** syqian_ has quit IRC07:45
openstackgerritKevin Zhao proposed openstack/nova master: Make uefi as the default boot perproties for AArch64  https://review.openstack.org/48995107:48
*** thorst_afk has joined #openstack-nova07:50
*** thorst_afk has quit IRC07:55
*** zsli_ has joined #openstack-nova08:02
*** zsli_ has quit IRC08:03
*** zsli_ has joined #openstack-nova08:04
*** Shunli has quit IRC08:05
*** zsli_ has quit IRC08:05
*** zsli_ has joined #openstack-nova08:06
*** Tom has joined #openstack-nova08:07
*** edmondsw has quit IRC08:08
*** Tom has quit IRC08:12
*** cdent has joined #openstack-nova08:13
*** Tom has joined #openstack-nova08:15
*** zsli_ has quit IRC08:17
*** zsli__ has joined #openstack-nova08:17
*** openstackgerrit has quit IRC08:17
*** cdent has quit IRC08:22
*** efoley has joined #openstack-nova08:23
*** ralonsoh has joined #openstack-nova08:23
*** efoley_ has joined #openstack-nova08:24
*** efoley has quit IRC08:24
*** efoley_ has quit IRC08:25
*** efoley has joined #openstack-nova08:25
*** mdnadeem has quit IRC08:29
*** lucas-afk is now known as lucasagomes08:30
*** mdnadeem has joined #openstack-nova08:33
*** syqian__ has quit IRC08:41
*** syqian__ has joined #openstack-nova08:42
*** liusheng has quit IRC08:42
*** thorst_afk has joined #openstack-nova08:51
*** thorst_afk has quit IRC08:55
*** openstackgerrit has joined #openstack-nova08:59
openstackgerritLajos Katona proposed openstack/nova master: Extend ServerMovingTests with custom resources  https://review.openstack.org/49739908:59
*** openstackgerrit has quit IRC09:03
*** hferenc has joined #openstack-nova09:03
*** liusheng has joined #openstack-nova09:07
*** zsli__ has quit IRC09:11
*** sambetts|afk is now known as sambetts09:11
*** zsli__ has joined #openstack-nova09:12
*** Shunli has joined #openstack-nova09:16
*** zsli__ has quit IRC09:19
*** openstackgerrit has joined #openstack-nova09:21
openstackgerritRodolfo Alonso Hernandez proposed openstack/os-vif master: Add VersionedObjectPrintable mixin  https://review.openstack.org/49308209:21
*** chyka has joined #openstack-nova09:21
*** Shunli has quit IRC09:21
*** mdnadeem has quit IRC09:21
*** mdnadeem has joined #openstack-nova09:24
*** chyka has quit IRC09:25
*** Tom has quit IRC09:26
openstackgerritjichenjc proposed openstack/nova master: Enhance doc for nova services  https://review.openstack.org/49953609:26
*** Tom has joined #openstack-nova09:27
*** Tom has quit IRC09:27
*** jichen has quit IRC09:34
*** hoonetorg has quit IRC09:36
openstackgerritBalazs Gibizer proposed openstack/nova master: Test resource allocation during soft delete  https://review.openstack.org/49515909:38
openstackgerritBalazs Gibizer proposed openstack/nova master: Moving more utils to ServerResourceAllocationTestBase  https://review.openstack.org/49953909:38
*** sdague has joined #openstack-nova09:38
*** zz9pzza has quit IRC09:40
*** psachin has quit IRC09:45
*** thorst_afk has joined #openstack-nova09:51
*** chyka has joined #openstack-nova09:52
*** hoonetorg has joined #openstack-nova09:53
*** thorst_afk has quit IRC09:56
*** chyka has quit IRC09:56
*** claudiub|2 has joined #openstack-nova09:57
*** psachin has joined #openstack-nova09:58
*** liusheng has quit IRC09:59
*** claudiub has quit IRC10:01
*** nicolasbock has joined #openstack-nova10:02
*** ralonsoh has quit IRC10:03
*** mdnadeem has quit IRC10:03
*** ralonsoh has joined #openstack-nova10:04
*** priteau has joined #openstack-nova10:04
*** yangyapeng has quit IRC10:05
*** yangyapeng has joined #openstack-nova10:05
*** nicolasbock has quit IRC10:06
*** liusheng has joined #openstack-nova10:09
*** yangyapeng has quit IRC10:10
*** ebbex has quit IRC10:10
openstackgerritVladyslav Drok proposed openstack/nova master: Allow reschedules for ironic computes if one forced host specified  https://review.openstack.org/49954510:11
bauzashello folks10:13
bauzasback from traveling10:13
*** mdnadeem has joined #openstack-nova10:18
*** nicolasbock has joined #openstack-nova10:19
gibibauzas: hello! welcome back10:19
bauzasgibi: congrats to you ;)10:20
bauzasgibi: sorry, missed matt's email but was definitely +1 to you :)10:20
bauzasnow, I have a fun time to look at all the problems10:20
openstackgerritRajesh Tailor proposed openstack/nova master: Host addition host-aggregate should be case-sensitive  https://review.openstack.org/49833410:20
gibibauzas: thanks. :) We knew that you were off so no worries about the missing vote10:22
bauzaslooks like we have some problems with forcing a destination10:24
*** Tom has joined #openstack-nova10:25
gibibauzas: yeah, that the finding of the week I guess :)10:25
bauzasagain, I'm sad10:26
bauzasbecause I forgot to think about forced moves when I reviewing the scheduler allocations :(10:27
*** udesale has quit IRC10:27
*** priteau has quit IRC10:28
gibidon't be hard on yourself none of us noticed this in that review10:28
gibion the plus side now we are creating an extensive set of functional tests that will cover these cases so the next modification of that claim code will be a lot safer to do10:29
*** Tom has quit IRC10:29
openstackgerritVladyslav Drok proposed openstack/nova master: Allow reschedules for ironic computes if one forced host specified  https://review.openstack.org/49954510:30
*** amarao has quit IRC10:31
*** abhi89 has quit IRC10:31
*** priteau has joined #openstack-nova10:31
*** Tom has joined #openstack-nova10:39
*** szaher has quit IRC10:41
*** Tom has quit IRC10:44
*** szaher has joined #openstack-nova10:46
*** Tom has joined #openstack-nova10:49
*** thorst_afk has joined #openstack-nova10:52
*** gszasz has joined #openstack-nova10:56
*** thorst_afk has quit IRC10:57
*** salv-orlando has quit IRC11:00
*** hferenc has quit IRC11:00
*** hferenc has joined #openstack-nova11:02
*** TuanLA has quit IRC11:02
*** trinaths has left #openstack-nova11:03
*** psachin has quit IRC11:08
*** chyka has joined #openstack-nova11:08
*** yassine has quit IRC11:12
*** jistr is now known as jistr|biab11:12
*** chyka has quit IRC11:13
*** phuongnh has quit IRC11:14
*** dave-mccowan has joined #openstack-nova11:18
*** psachin has joined #openstack-nova11:19
*** yassine has joined #openstack-nova11:19
*** claudiub has joined #openstack-nova11:24
*** claudiub|2 has quit IRC11:27
*** salv-orlando has joined #openstack-nova11:36
*** thorst_afk has joined #openstack-nova11:40
*** rmart04 has joined #openstack-nova11:41
openstackgerritLajos Katona proposed openstack/nova master: Add functional migrate force_complete test  https://review.openstack.org/49620211:43
*** lucasagomes is now known as lucas-hungry11:44
*** mriedem has joined #openstack-nova11:47
*** efried_off is now known as efried11:50
*** smatzek has joined #openstack-nova11:50
*** thegreenhundred has quit IRC11:55
*** litao__ has quit IRC11:55
*** abhi89 has joined #openstack-nova11:58
*** mvk has joined #openstack-nova12:03
*** trinaths has joined #openstack-nova12:06
*** TuanLA has joined #openstack-nova12:07
*** lpetrut has joined #openstack-nova12:07
*** alexchadin has joined #openstack-nova12:08
*** kiennt has quit IRC12:14
*** claudiub has quit IRC12:14
*** claudiub has joined #openstack-nova12:14
*** kylek3h has quit IRC12:15
*** jpena is now known as jpena|lunch12:16
mriedemfunny that we don't check if the host specified during an evacuate is the same host that the instance is already running on and fail with a 400 early in the api12:16
openstackgerritBob Ball proposed openstack/nova master: XenAPI: Unit tests must mock os_xenapi calls  https://review.openstack.org/49957312:17
mriedemconductor would eventually fail with an rpc error probably but you don't get that information from the api, no fault is recorded, and the instance task_state is left in 'rebuilding'12:17
gibimriedem: could this be related to the bug https://bugs.launchpad.net/nova/+bug/171378312:19
openstackLaunchpad bug 1713783 in OpenStack Compute (nova) "After failed evacuation the recovered source compute tries to delete the instance" [Undecided,New]12:19
*** liverpooler has joined #openstack-nova12:19
gibimriedem: in that bug it seems that when the evacuation fails the migration object is not set to error statae12:20
*** jistr|biab is now known as jistr12:20
*** trinaths has left #openstack-nova12:21
*** sree has quit IRC12:21
*** sree has joined #openstack-nova12:21
mriedemgibi: unrelated12:21
mriedemhttps://bugs.launchpad.net/nova/+bug/171423512:23
openstackLaunchpad bug 1714235 in OpenStack Compute (nova) "evacuate API does not restrict one from trying to evacuate to the source host" [Low,Confirmed]12:23
openstackgerritEric Fried proposed openstack/nova master: Bump keystoneauth1 minimum to 3.2.0  https://review.openstack.org/49957712:23
*** sdague has quit IRC12:23
*** pchavva has joined #openstack-nova12:24
*** annegentle has joined #openstack-nova12:25
mriedemgibi: for that bug you pointed out, if the evacuate failed, the instance.host should still be pointed at the source host12:25
mriedemwe should only be removing the instance allocation for the source node if the instance.host != CONF.host12:25
*** sree has quit IRC12:26
mriedem_destroy_evacuated_instances doesn't seem to take that into account12:26
mriedemgibi: actually it looks like that's a recent regression https://review.openstack.org/#/c/491808/12:28
*** vladikr has joined #openstack-nova12:29
*** catintheroof has joined #openstack-nova12:30
mriedemmaybe not, but it looks suspect12:32
mriedemgibi: we could revert https://review.openstack.org/#/c/491808/ on top of https://review.openstack.org/#/c/498482/ and see what happens12:34
*** eharney has joined #openstack-nova12:34
gibimriedem: thanks. I can try out the revert12:36
*** sdague has joined #openstack-nova12:37
*** jaosorior has quit IRC12:37
*** thegreenhundred has joined #openstack-nova12:38
*** jaosorior has joined #openstack-nova12:38
efriedsdague https://github.com/openstack/nova/blob/master/nova/cmd/status.py#L198  <== I can't see where we're checking for registered compute nodes in this method.  Is this comment obsolete?12:38
efried(or, more likely, am I missing something?)12:39
gibimriedem: hm, _destory_evacuated_instances does filter for the instance.host https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L63812:39
*** liverpooler has quit IRC12:40
mriedemthat's finding the migrations12:40
mriedemso it will find the migration that started from this source host12:40
*** liverpooler has joined #openstack-nova12:40
mriedembut that's not checking that the instance.host has changed to another host12:40
gibimriedem: ahh, yes, my bad12:40
mriedemit's also weird that it's filtering on 'accepted' migrations, because that is set when the migration record is created in the api12:40
openstackgerritLajos Katona proposed openstack/nova master: Add functional for live migrate delete  https://review.openstack.org/49958312:41
mriedemso the migration might not actually be done12:41
gibimriedem: also the regression test shows that this migration never goes to error of failed state12:41
gibimriedem: it remains in accepted state12:41
mriedemthat was another question - how is the evacuate actually failing?12:42
gibimriedem: here is the regression test https://review.openstack.org/#/c/498482/12:42
mriedemis it failing in conductor?12:42
*** Tom has quit IRC12:42
gibimriedem: scheduler fails to found a host12:42
mriedemah12:42
mriedemyeah12:42
*** smatzek has quit IRC12:42
gibimriedem: here is one way to solve this https://review.openstack.org/#/c/499237/1/nova/conductor/manager.py (still WIP)12:43
*** jaosorior has quit IRC12:44
mriedemyeah that's pretty straight forward12:44
gibimriedem: btw is there a doc about the possible migration status values? I found both error and failed in the code12:45
mriedemodd that we don't pass the migration record over rpc from api to conductor, but that would be a separate cleanup12:45
*** jaosorior has joined #openstack-nova12:45
*** jaosorior has quit IRC12:45
mriedemi don't think there is really12:45
mriedemi think takashi was cataloging some of that for his blueprint to list more than just in-progress live migrations out of the api12:46
*** kylek3h has joined #openstack-nova12:46
mriedemso he was defining what 'in-progress' meant12:46
*** jaosorior has joined #openstack-nova12:46
gibimriedem: cool I fully support documenting the possible statuses12:46
mriedemsome of it is in here https://specs.openstack.org/openstack/nova-specs/specs/pike/approved/list-show-all-server-migration-types.html#proposed-change12:46
bauzasmriedem: when you say "asking to evacuate to the same host", do you imply using the force flag or not ?12:46
mriedembauzas: sure12:47
mriedemif force=False, you'd get NoValidHost12:47
mriedembecause of the ComputeFilter12:47
bauzascorrect12:47
mriedembut if force=True, you'd bypass the scheduler12:47
mriedemand fail the rpc cast to compute12:47
*** kylek3h_ has joined #openstack-nova12:47
bauzasbut that's your fault12:47
*** TuanLA has quit IRC12:47
bauzasyou *forced*12:47
mriedemit just seems weird that we don't have that one line validation check in the api code12:48
*** lajoskatona has quit IRC12:48
mriedemif host and host == instance.host: raise 40012:48
bauzasthat said, I think there is a call made by the API verifying if the destination is alive before we call the conductor12:48
bauzasfor evacuate I mean12:48
mriedembauzas: yes there is12:48
mriedemand that can pass12:48
mriedemand you can call conductor on the same host as instance.host12:49
bauzaswait12:49
bauzasah, nevremind12:49
*** esberglu has joined #openstack-nova12:49
mriedemand eventually either it fails with NoValidHost and the instance state is reset (best case scenario), or we bypass the scheduler and rpc fails, and your instance is stuck in 'rebuilding' state12:49
bauzasthe API check is verifying the *source*12:49
mriedemcorrect12:49
mriedemyou will fail either way, but a straight 400 is better than weird undefined failures once we've cast to compute12:50
mriedems/compute/conductor/12:50
bauzaswell, when I wrote the original Newton spec about force flags and so on, I made it clear that if people are using 'force', they have to be super-cautious12:50
bauzasthat's what we said to them12:50
*** kylek3h has quit IRC12:50
mriedemhow many operators do you think have read that spec?12:50
bauzasthe real problem was that pre-Newton, we weren't clear whether we were enforcing rules12:50
bauzasI think I translated that in the API docs12:51
bauzasbut I could be missing that12:51
mriedemthis is the description of the force parameter in the api ref12:51
mriedem"Force an evacuation by not verifying the provided destination host by the scheduler."12:51
*** lucas-hungry is now known as lucasagomes12:51
mriedem^ is not, "holy shit, don't do this"12:51
mriedemwe should put a warning in there probably12:51
mriedemalso,12:52
bauzasmriedem: I didn't wanted to be pedantic when I said about the spec, I just try to explain that I saw there was by that time I wrote the spec, a pretty clear consensus that if operators are providing destinations, they *have to* make sure it's an acceptable one12:52
bauzasbecause it's anti-cloud12:53
bauzasyou specify a destination, fair enough12:53
mriedemwith https://review.openstack.org/#/c/499399/ now, we should probably seriously consider splitting the rebuild_instance conductor method / rpc api into rebuild_instance and evacuate_instance12:53
bauzasbut then, make sure it's a good one12:53
mriedembecause the if/else logic in there is getting pretty hairy12:53
sdagueefried: yeh, I don't know12:53
*** lyan has joined #openstack-nova12:53
*** salv-orlando has quit IRC12:54
efriedsdague Just something I noticed while I was in the neighborhood; and you're git blamed on that comment :)12:54
bauzasmriedem: there is a side concern to me: you can specify a destination but we don't tell whether it's case-sensitive or not12:54
bauzasmriedem: and somewhere, it breaks12:54
mriedemyou'd get NoValidHost i'd thikn12:55
mriedemsince we'd filter out all hosts12:55
mriedemsince the ComputeNode.host doesn't match12:55
bauzasthere is a bug12:56
bauzaswait, finding it12:56
mriedemlemme guess, case insensitivity in mysql?12:56
bauzashttps://bugs.launchpad.net/nova/+bug/170926012:57
openstackLaunchpad bug 1709260 in OpenStack Compute (nova) "Addition of host to host-aggregate should be case -sensitive" [Low,In progress] - Assigned to Rajesh Tailor (ratailor)12:57
bauzasit seems that DNS is case-insentive12:57
bauzascase-insensitive12:57
*** dave-mccowan has quit IRC12:57
bauzasso in theory, we should accept to migrate to foo or FOO12:57
bauzasbut yeah, I guess it's because mysql12:58
bauzasratailor: around ?12:58
ratailorbauzas, yep12:58
bauzasratailor: I feel I badly triaged your bug12:58
bauzasratailor: since DNS is case-insensitive, hostnames should be too12:59
ratailorbauzas, I reproduced it, and found that mysql doesn't support case-sensitivity by-default. So I had to change the collation on related tables.12:59
ratailorbauzas, which seems to work.12:59
*** udesale has joined #openstack-nova13:00
mriedemyou know what is case sensitive by default (i think)?13:00
mriedemPOSTGRESQL!13:00
*** tiendc has quit IRC13:01
*** Tom has joined #openstack-nova13:01
mriedemsort of https://stackoverflow.com/questions/21796446/postgres-case-sensitivity13:01
ratailorI was discussing it with alex_xu some days ago and he mentioned that mysql is case-insensitive by-default.13:01
bauzasratailor: tbh, I just feel that we should allow HoStNaME1 as a possible value for a host to be added in an aggregate13:01
mriedemdepends on quotes13:01
bauzasratailor: and rather fix the filter13:01
mriedemratailor: yeah, the mysql case issue is a known one13:01
mriedemthat breaks several things13:01
bauzasyup13:01
*** baoli has joined #openstack-nova13:02
ratailormriedem, the host-aggregate metadata keys as well,13:02
bauzasratailor: I'll rephrase your bug report if you agree13:02
mriedemratailor: https://specs.openstack.org/openstack/nova-specs/specs/newton/approved/lowercase-metadata-keys.html13:02
ratailorbauzas, no problem.13:02
bauzasmriedem: well, hostnames can be FQDNs13:02
bauzasmriedem: if so, those have to be case-insensitive13:03
*** smatzek has joined #openstack-nova13:03
openstackgerritMatt Riedemann proposed openstack/nova master: Create allocations against forced dest host during evacuate  https://review.openstack.org/49939913:04
*** Tom has quit IRC13:05
ratailorbauzas, I don't understand you mentioning HoStNaME1 as possible value for host to add in aggregate.13:05
bauzasmriedem: about your point above with providing the same host for the target and source, if we accept to verify that by the API, we also need to add this to the live-migration one13:05
ratailorbauzas, As of now, if hostname is set as "compute0.example.com" (in lower case)13:06
ratailorand user tries to add this host to host-aggregate but by-mistake types13:06
ratailor"COMPUTE0.example.com" (in capital case), then instead of throwing13:06
ratailorHostNotFound error, that host is successfully added to host-aggregate13:06
ratailoras "COMPUTE0.example.com". And after that if instance creation request13:06
ratailorwith flavor matching metadata as host-aggregate metadata comes, this13:06
ratailorhost is not filtered by scheduler, since there is no host with hostname13:06
ratailorCOMPUTE0.example.com, as added in host-aggregate13:06
*** annegentle has quit IRC13:06
bauzasratailor: I got the problem13:09
*** dave-mcc_ has joined #openstack-nova13:09
ratailorbauzas, cool,13:09
bauzasratailor: what I feel is that we somehow should still accept COMPUTE0 as a possible value for the host to be added in the aggregate13:09
bauzasfrom an API perspective13:09
bauzasif we want to follow the DNS RFC13:10
bauzasratailor: what we could do tho is to lowercase that string before amending the aggregate13:10
bauzasand that wouldn't trample https://specs.openstack.org/openstack/nova-specs/specs/newton/approved/lowercase-metadata-keys.html13:11
ratailorbauzas, But that can happen other way round as well, hostname can be COMPUTE0 and user tries to add compute0 which should fail, as there is no hostname with compute0.13:11
*** sree has joined #openstack-nova13:12
bauzasthen the filter has to be fixed too13:12
bauzasbecause it fails due to the filtter, right?13:13
ratailorbauzas, I think, that's separate bug, which is only concerned about metadata keys. Is it somehow related to hostname.13:13
ratailorbauzas, I think, the issue is with mysql only,13:14
ratailorbauzas, https://github.com/openstack/nova/commit/402b3abf990d08d2af8331079d36a92d84d84b8013:14
*** zhurong has quit IRC13:14
*** udesale has quit IRC13:15
ratailorbauzas, similar problem was there, and he has changed collation type for mysql backend.13:15
*** artom has quit IRC13:15
*** annegentle has joined #openstack-nova13:16
*** gouthamr has joined #openstack-nova13:18
ratailorbauzas, you want to discuss anything else, it EOD here. Can we continue tomorrow, if anything is left ?13:18
bauzasratailor: for sure13:20
*** jpena|lunch is now known as jpena13:20
bauzasratailor: have a good evening13:20
ratailorbauzas, same to you!13:20
*** alexchadin has quit IRC13:22
gibimriedem: I reverted https://review.openstack.org/#/c/491808 top of https://review.openstack.org/#/c/498482 and I still see that the recovered source compute tries to delete the instance13:23
*** ratailor has quit IRC13:24
gibimriedem: so I think setting the migration to failed is the solution we need. Do you suggest to add an extra check to the destroy_evacuated_instances about that instance.host != CONF.host as well?13:25
gibihm, the bug disappeared from launchpad https://bugs.launchpad.net/nova/+bug/171378313:26
openstackgibi: Error: malone bug 1713783 not found13:26
*** gszasz has quit IRC13:29
openstackgerritBob Ball proposed openstack/nova master: XenAPI: Unit tests must mock os_xenapi calls  https://review.openstack.org/49957313:29
*** slaweq has quit IRC13:29
gibimriedem: but you were able to just update that bug. that is weird13:30
hrwmorning13:31
hrwcan someone tell me where nova defines default VM scheme? As 'hi libvirt, here I have some VM definition for you' way13:31
*** slaweq has joined #openstack-nova13:32
*** salv-orlando has joined #openstack-nova13:33
gibihrw: hi, I think this is the place https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L517013:35
hrwgibi: thanks13:35
*** ssmith has joined #openstack-nova13:38
*** lyan has quit IRC13:38
*** andreas_s has joined #openstack-nova13:39
*** smatzek has quit IRC13:39
*** gyee has joined #openstack-nova13:41
*** lyan has joined #openstack-nova13:42
*** gszasz has joined #openstack-nova13:45
*** crushil has quit IRC13:45
*** awaugama has joined #openstack-nova13:46
*** rajathagasthya has joined #openstack-nova13:48
*** xyang1 has joined #openstack-nova13:48
*** danpawlik has quit IRC13:50
*** edmondsw has joined #openstack-nova13:51
*** slaweq has quit IRC13:52
*** slaweq has joined #openstack-nova13:53
*** gszasz has quit IRC13:53
*** sree has quit IRC13:54
*** gszasz has joined #openstack-nova13:55
*** sree has joined #openstack-nova13:55
*** crushil has joined #openstack-nova13:55
mriedemgibi: one thing on the fix for that evacuate issue is, i'd like to backport that further than just pike,13:56
mriedembut we don't have the ServerMovingTests stuff before pike13:56
mriedemso backporting to ocata and newton will be difficult if we don't decouple those13:56
mriedemit would be nice if the code fix patch is self-contained13:56
*** cleong has joined #openstack-nova13:57
*** josecastroleon has quit IRC13:57
*** slaweq has quit IRC13:57
*** jaosorior has quit IRC13:57
*** rmart04 has quit IRC13:58
*** Donckers has joined #openstack-nova13:58
*** slaweq has joined #openstack-nova13:59
*** jaosorior has joined #openstack-nova13:59
*** josecastroleon has joined #openstack-nova13:59
*** smatzek has joined #openstack-nova13:59
*** mdnadeem has quit IRC14:00
*** gbarros has joined #openstack-nova14:00
gibimriedem: would you like to have an independent regression test for that bug under tests/functional/regressions ?14:01
gibimriedem: that could be backportable14:01
mriedemit's not really a regression14:02
mriedembut yes a separate standalone test would be nice14:02
mriedemit's just a latent bug from what i can tell14:02
mriedemwell, it was maybe regressed when the migration record stuff was changed to track evacuations, but that's pretty old now (liberty or mitaka i think)14:03
mriedemso you could put it in tests/functional/regressions if you wanted, that's fine14:03
mriedemjust decouple from ServerMovingTests14:03
*** psachin has quit IRC14:04
*** cristicalin has joined #openstack-nova14:05
*** jobewan has joined #openstack-nova14:06
gibimriedem: OK, cool14:06
*** hongbin has joined #openstack-nova14:07
mriedemi also need to look at splitting https://review.openstack.org/#/c/499399/ up a bit later today14:08
mriedemsince it's a pretty large change atm14:08
*** marst has joined #openstack-nova14:08
*** armax has joined #openstack-nova14:10
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove deprecated 'null_kernel' opt  https://review.openstack.org/49961114:10
openstackgerritStephen Finucane proposed openstack/nova master: WIP! conf: Remove deprecated 'multi_instance_display_name_template' opt  https://review.openstack.org/49961214:10
*** armax_ has joined #openstack-nova14:12
*** ijw has joined #openstack-nova14:13
*** shan has quit IRC14:15
*** itlinux has joined #openstack-nova14:15
*** armax has quit IRC14:15
*** armax_ is now known as armax14:16
*** gyee has quit IRC14:17
efriedwhere da source for the placement API reference doc?  https://developer.openstack.org/api-ref/placement/14:17
efriedfound typo, wanna fix.14:17
*** gyee has joined #openstack-nova14:17
sdaguenew ironic issue - https://bugs.launchpad.net/nova/+bug/1714248 ?14:17
openstackLaunchpad bug 1714248 in OpenStack Compute (nova) "Compute node HA for ironic doesn't work due to the name duplication of Resource Provider " [Undecided,New]14:17
*** hshiina has quit IRC14:18
efriednova project, placement-api-ref/source/parameters.yaml?14:18
sdagueefried: yep14:19
efriedthx14:19
efriedstarts_with => startswith, according to my playing around.14:19
efried...for GET /traits14:19
sdagueefried: cool14:21
sdaguethe names of parameters is in the rst, so depending you might only need to change that side, not that parameters.yaml14:21
efriedsdague rgrep showed starts_with only in that yaml file, so...14:22
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: [placement] Add test for empty resources in allocation  https://review.openstack.org/49961514:23
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: [placement] Require at least one resource class in allocation  https://review.openstack.org/49961614:23
*** mriedem is now known as mriedem_away14:23
bauzasmriedem: I'm still not at full steam, but how can I help by reviewing changes ?14:23
bauzasmriedem_away: the above gibi's changes ?14:23
gibibauzas: that change need some work based on the above discussion to make it backportable14:24
bauzask14:24
efriedThe list of links returned by GET /resource_providers doesn't have one for .../allocations.  I think it should (because that URI responds).  LP bug?14:26
*** sree has quit IRC14:28
*** sree has joined #openstack-nova14:29
*** annegentle has quit IRC14:30
gibibauzas: mriedem_away has a refactor here https://review.openstack.org/#/c/498596/ that needs a +214:30
gibibauzas: and some more test coverage here https://review.openstack.org/#/c/496202 that also needs some core love14:31
bauzasgibi: I need to look at what you added during my 2.5wks PTO :)14:31
*** cfriesen_ has joined #openstack-nova14:31
gibibauzas: I had my one week PTO during that time so not that much but others were busy14:32
*** slaweq has quit IRC14:32
*** slaweq has joined #openstack-nova14:33
*** sree has quit IRC14:33
*** artom has joined #openstack-nova14:36
edleafeefried: that sounds reasonable, but I would wait for cdent to chime in. It may be an oversight, or there might be a good reason.14:37
edleafeefried: my money's on an oversight14:38
edleafe:)14:38
efriededleafe Rgr.  Found the spot in the code where it would be added.  I think the per-microversion link splitup was done before the allocations microversion.14:38
edleafeefried: that would make sense14:39
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove deprecated 'allow_instance_snapshots' opt  https://review.openstack.org/49962114:39
*** coreywright has quit IRC14:39
efriedWill confirm, open bug, and if it's intentional, cdent can just close the sucker.14:39
*** tidwellr has joined #openstack-nova14:39
*** slaweq_ has joined #openstack-nova14:43
efriednope, https://review.openstack.org/#/c/366789/ merged 20160909; https://review.openstack.org/#/c/468923/ merged 20170606.  Both authored by cdent.  So... maybe intentional.14:43
openstackgerritStephen Finucane proposed openstack/nova master: conf: Move additional nova-net opts to 'network'  https://review.openstack.org/49916814:45
*** abalutoiu has quit IRC14:47
efriededleafe FYI: https://bugs.launchpad.net/nova/+bug/171427514:47
openstackLaunchpad bug 1714275 in OpenStack Compute (nova) "GET /resource_providers: "links" doesn't include "allocations"" [Undecided,New]14:47
*** slaweq_ has quit IRC14:47
*** josecastroleon has quit IRC14:48
edleafeefried: cool. I'm sure cdent will contribute his 2 cents when he is back on the ground14:49
dansmithedleafe: are you going to be in denver? know about cdent?14:51
*** josecastroleon has joined #openstack-nova14:51
edleafedansmith: we both are14:51
dansmithokay cool14:51
*** annegentle has joined #openstack-nova14:52
*** coreywright has joined #openstack-nova14:52
*** Swami has joined #openstack-nova14:52
*** josecastroleon has quit IRC14:53
*** armax has quit IRC14:53
gibimriedem_away: I added my subteam update to the nova meeting agenda as I cannot joint today14:55
*** jobewan is now known as jobewan_away14:58
*** shan has joined #openstack-nova14:58
*** moshele has quit IRC15:00
kashyapmelwitt: Following up from yesterday, and as your test proved, re-defining from live domain is expected to work - Eric, the author of the API confirms15:02
*** trungnv has quit IRC15:03
*** sridharg has quit IRC15:03
*** trungnv has joined #openstack-nova15:04
*** annegentle has quit IRC15:08
*** salv-orlando has quit IRC15:08
*** cristicalin has quit IRC15:08
*** cristicalin has joined #openstack-nova15:10
*** mriedem_away is now known as mriedem15:10
mriedemgibi: ok15:10
openstackgerritEric Fried proposed openstack/nova master: Update placement docs: api-ref link, startswith  https://review.openstack.org/49963515:11
efriedsdague FYI ^15:12
efriedmriedem backport potential? ^15:12
*** kbaegis has joined #openstack-nova15:12
efried(test out that gerritbot update :)15:12
*** cristicalin has quit IRC15:13
openstackgerritBob Ball proposed openstack/nova master: XenAPI: Unit tests must mock os_xenapi calls  https://review.openstack.org/49957315:13
sdagueefried: api-ref doesn't need backporting15:13
sdagueonly master is published15:14
efriedright, okay15:14
efriedsdague But the rst...15:14
sdagueefried: what about it?15:15
efriedcould be backported15:15
efriedto provide the link for readers @pike level15:15
*** Oku_OS is now known as Oku_OS-away15:16
sdagueefried: oh, in that case you probably want to split the 2 up15:16
sdaguedo the parameter fix first15:16
sdaguethen do the rst separate15:16
sdaguebecause we don't backport api-ref15:17
*** moshele has joined #openstack-nova15:17
*** sridharg has joined #openstack-nova15:17
efriedAnd we can't have a separate thing that just drops to pike?15:17
efriedhas to be a backport?15:17
sdagueefried: you could modify the backport15:17
sdagueand drop that field15:17
sdaguesorry, that file15:17
sdagueit's just a cleaner backport if it was 2 patches15:17
efriedYeah, wfm.15:17
efriedI'll split it up.  And open a bug, cause that's required to backport, yah?15:18
sdagueefried: sure15:19
*** ragiman has quit IRC15:20
*** salv-orlando has joined #openstack-nova15:21
*** annegentle has joined #openstack-nova15:21
*** andreas_s has quit IRC15:22
*** gmann has quit IRC15:23
*** gmann has joined #openstack-nova15:23
*** ralonsoh has quit IRC15:23
openstackgerritMatt Riedemann proposed openstack/nova master: Add recreate test for forced host evacuate not setting dest allocations  https://review.openstack.org/49967815:25
openstackgerritEric Fried proposed openstack/nova master: [placement] api-ref GET /traits name:startswith  https://review.openstack.org/49968215:28
mriedemgibi: replied in https://review.openstack.org/#/c/499399/ - basically, you're correct, but this is for backporting to pike, and we don't really support things like shared resource providers yet anyway15:29
mriedemi think when we do, we remove this code and have conductor call the scheduler to sort that all out during the move operation15:29
*** chyka has joined #openstack-nova15:30
openstackgerritEric Fried proposed openstack/nova master: [placement] Update user doc with api-ref link  https://review.openstack.org/49963515:31
*** pcaruana has quit IRC15:32
*** salv-orlando has quit IRC15:35
*** slaweq has quit IRC15:36
openstackgerritMatt Riedemann proposed openstack/nova master: Create allocations against forced dest host during evacuate  https://review.openstack.org/49939915:37
*** slaweq has joined #openstack-nova15:37
*** edmondsw has quit IRC15:40
*** jobewan_away is now known as jobewan15:40
*** moshele has quit IRC15:41
*** slaweq has quit IRC15:41
*** yangyapeng has joined #openstack-nova15:43
*** vikrant has joined #openstack-nova15:43
*** abalutoiu has joined #openstack-nova15:45
mriedemgah, why do we have nova.tests.unit.scheduler.test_utils and nova.tests.unit.scheduler.test_scheduler_utils?!15:45
*** itlinux has quit IRC15:46
artomBack when I worked web hosting support, I reeeaaally wanted to answer those type of why questions ("why is server down?") with "because god hates you."15:47
vdrokgood morning folks! in ironic, we sometimes hit the issue with one of the smoke tests in tempest not being able to boot an instance on a specific host as RescheduledException happens. the reason seems to be this piece of code https://review.openstack.org/#/c/499545/2/nova/scheduler/utils.py. Is there a better way to achieve this kind of thing? as this does not look pretty15:49
openstackgerritLucian Petrut proposed openstack/nova master: HyperV: Perform proper cleanup after failed instance spawns  https://review.openstack.org/49969015:50
vdrokbasically, for ironic it would be good to distinguish cases when len(force_hosts)==1 and still do reschedules in this case, as there are multiple nodes assigned to the host15:51
*** edmondsw has joined #openstack-nova15:51
*** Ralgamasiel has quit IRC15:52
*** moshele has joined #openstack-nova15:53
mriedem1:M :(15:54
*** dtp has joined #openstack-nova15:54
mriedemplus forcing anything15:54
vdrokbasically the failing test is https://github.com/openstack/tempest/blob/master/tempest/scenario/test_server_multinode.py#L40, we could skip it. but it kinda helps to ensure that hash ring works15:55
*** kbaegis has quit IRC15:55
*** kbaegis has joined #openstack-nova15:55
*** edmondsw has quit IRC15:56
bauzasmriedem: FWIW, I'm writing a new spec for changing the boot request to be using the requested_destination flag15:57
bauzasmriedem: and no "force" flag to be used15:57
bauzasmriedem: so we could just send force_hosts in hell15:57
bauzasthat said, there is a flaw15:57
bauzassince live-migrate and evacuate only accept a single string for passing a target, the usual tuple (host,node) isn't possible15:58
bauzasso in Ironic, you can't specify a specific ironic node to boot against15:58
bauzasoops15:58
bauzasto move15:58
*** armax has joined #openstack-nova15:59
*** mvk has quit IRC15:59
vdrokwell, we don't live migrate or evacuate yet :) tho I've seen a spec to enable it in case of boot from volume15:59
bauzasexactly this16:00
bauzasso that's why it wasn't a problem for the move operations16:00
mriedemthere are TODOs all over the code when doing nodes[0] though16:01
bauzasbut if I'm writing a new spec for modifying the boot operation to use the same, then I need to think about how to pass a destination that is an Ironic node16:01
bauzasmriedem: yeah, because Ironic doesn't support both evacuate and live-migrate so we don't really care16:01
mriedemcleaning up the hundred TODOs around request spec usage in the code would also be nice16:02
mriedemi'm going to be starting on some stuff like that in the conductor task api code16:02
bauzasmriedem: you know that I was having an approved BP for cleaning up that mess16:02
bauzasmriedem: the scheduler-claims vamped up all my implementation and review time but I seriously consider working on that again for Queens16:03
bauzasthat and the API microversion for changing how we pass a destination when booting16:03
*** lucasagomes is now known as lucas-hungry16:04
dansmithyeah, that mess was giving me heartache yesterday16:05
dansmithgibi: around?16:06
dansmithgibi: I think I'm failing a bunch of tests because of notification things, is that right? http://logs.openstack.org/50/498950/3/check/gate-nova-tox-functional-ubuntu-xenial/0a8068d/testr_results.html.gz16:07
bauzasit wasn't fun I was away when you folks had those problems with the force flag and the Requestspec :(16:07
bauzasdrop me a ping next time, because I hardly read the ML when I'm off16:07
*** moshele has quit IRC16:09
*** slaweq has joined #openstack-nova16:10
*** slaweq has quit IRC16:14
*** hoonetorg has quit IRC16:18
mriedemlbragstad: at some point you should educate us on the new enhanced password in sql hashing stuff you guys have in keystone in pike, i saw that in release notes16:18
mriedemwe are storing cell mapping creds in the db16:19
lbragstadmriedem: oh - it's pretty straight forward, most of the context for the change is in https://bugs.launchpad.net/keystone/+bug/166850316:20
openstackLaunchpad bug 1668503 in OpenStack Security Notes "sha512_crypt is insufficient, use pbkdf2_sha512 for password hashing" [High,Fix committed] - Assigned to Luke Hinds (lhinds)16:20
lbragstadmriedem: we generate a mapping of supported hashing mechanisms and use that when dealing with things we need to hash16:21
abhi89Hi guys.. can someone please review https://review.openstack.org/#/c/485121/..16:21
lbragstadmriedem: we pulled most of the password hashing logic into a separate module https://github.com/openstack/keystone/blob/master/keystone/common/password_hashing.py]16:21
*** shan has quit IRC16:22
mriedemlbragstad: cool, thanks. sounds like dansmith has an alternative that he's been keeping secret too.16:23
*** moshele has joined #openstack-nova16:23
lbragstadmriedem: for hashing cells mapping creds?16:23
mriedemfor not storing them in the db16:23
lbragstadinteresting16:24
*** jobewan has quit IRC16:24
lbragstadmriedem: after they are hashed, where are they stored?16:24
mriedemconfig16:25
mriedemsomething, idk16:25
lbragstadahh16:25
mriedemthat's why it's a secret16:25
dansmithlbragstad: there's some way of configuring access creds by host/db, like DSN-based stuff16:25
dansmithI haven't done it myself, you should talk to zzzeek, maybe in the oslo channel or something16:25
mriedemdansmith: do you know if tripleo has this built in yet?16:25
mriedembecause i know they were complaining at one point about storing creds in the db16:26
dansmithmriedem: not for creds reasons,16:26
mriedemwe could copy this into devstack16:26
dansmithbut for source ip, which I think was a similar thing16:26
dansmiths/thing/solution/16:26
lbragstadinteresting16:27
*** gbarros has quit IRC16:29
*** vladikr has quit IRC16:30
*** esberglu has quit IRC16:30
*** jistr is now known as jistr|afk16:31
*** kbaegis has quit IRC16:31
*** kbaegis1 has joined #openstack-nova16:31
*** gbarros has joined #openstack-nova16:31
*** yangyapeng has quit IRC16:32
*** yarokifor has joined #openstack-nova16:34
*** sambetts is now known as sambetts|afk16:34
*** salv-orlando has joined #openstack-nova16:36
*** vladikr has joined #openstack-nova16:37
*** crushil has quit IRC16:41
*** salv-orlando has quit IRC16:41
*** Apoorva has joined #openstack-nova16:41
*** browne has joined #openstack-nova16:42
mriedemugh this always drives me crazy16:44
mriedem"remote: (W) No changes between prior commit a0be7d3 and new commit d375135"16:44
mriedemi'm re-ordering a series of changes to split some apart16:44
mriedemwhen i try to git review, it won't let me b/c the base change hasn't changed at all16:44
mriedemanyone know a special trick here? rebase doesn't work as i'm up to date16:45
*** itlinux has joined #openstack-nova16:46
openstackgerritMatt Riedemann proposed openstack/nova master: Add recreate test for forced host evacuate not setting dest allocations  https://review.openstack.org/49967816:46
openstackgerritMatt Riedemann proposed openstack/nova master: Create allocations against forced dest host during evacuate  https://review.openstack.org/49939916:46
openstackgerritMatt Riedemann proposed openstack/nova master: Refactor out claim_resources_on_destination into a utility  https://review.openstack.org/49971816:46
mriedemupdate the commit message i guess16:46
*** lpetrut has quit IRC16:47
*** user1124 has joined #openstack-nova16:47
user1124hello16:47
user1124i have a qq16:47
user1124does the nova policy for listing flavors actually work?16:47
user1124os_compute_api:flavors16:48
user1124os_compute_api:flavors:discoverable16:48
*** crushil has joined #openstack-nova16:53
*** user1124 has quit IRC16:55
*** annegentle has quit IRC16:55
*** gbarros has quit IRC16:57
melwittkashyap: thanks for confirming that with Eric16:57
*** gbarros has joined #openstack-nova16:58
*** felipemonteiro has joined #openstack-nova16:58
*** dave-mcc_ is now known as dave-mccowan17:01
*** gbarros has quit IRC17:03
*** baoli has quit IRC17:04
*** baoli has joined #openstack-nova17:04
*** abhi89 has quit IRC17:05
*** baoli has quit IRC17:06
melwittmriedem: more swap volume fun https://review.openstack.org/#/c/407346/ swapping a bootable volume on a BFV instance for a non-bootable volume results in problems. that patch changes to deny bootable -> non-bootable in the API which seems right to me. I wanted to get more opinions17:06
*** moshele has quit IRC17:11
*** psachin has joined #openstack-nova17:11
*** esberglu has joined #openstack-nova17:12
*** rcernin has quit IRC17:12
*** felipemonteiro_ has joined #openstack-nova17:12
*** trinaths has joined #openstack-nova17:13
*** felipemonteiro__ has joined #openstack-nova17:13
*** tesseract has quit IRC17:14
*** felipemonteiro has quit IRC17:14
*** baoli has joined #openstack-nova17:15
*** esberglu has quit IRC17:16
*** felipemonteiro_ has quit IRC17:17
*** shan has joined #openstack-nova17:18
*** esberglu has joined #openstack-nova17:20
*** shan7 has joined #openstack-nova17:22
*** shan has quit IRC17:23
*** shan7 has quit IRC17:23
*** shan has joined #openstack-nova17:24
*** Swami has quit IRC17:27
*** ijw has quit IRC17:28
*** ijw has joined #openstack-nova17:29
*** felipemonteiro_ has joined #openstack-nova17:30
*** kbaegis1 has quit IRC17:31
*** ijw has quit IRC17:33
*** yangyapeng has joined #openstack-nova17:33
*** felipemonteiro__ has quit IRC17:34
*** felipemonteiro_ has quit IRC17:35
*** liverpooler has quit IRC17:36
*** salv-orlando has joined #openstack-nova17:37
*** browne has quit IRC17:37
*** yangyapeng has quit IRC17:38
*** salv-orlando has quit IRC17:41
*** kbaegis has joined #openstack-nova17:42
*** edmondsw has joined #openstack-nova17:42
*** Tom has joined #openstack-nova17:43
*** abalutoiu has quit IRC17:43
*** crushil has quit IRC17:43
*** edmondsw_ has joined #openstack-nova17:44
*** Swami has joined #openstack-nova17:45
*** edmondsw has quit IRC17:46
*** Apoorva has quit IRC17:47
*** Tom has quit IRC17:47
*** edmondsw_ has quit IRC17:48
*** Apoorva has joined #openstack-nova17:49
*** baoli has quit IRC17:49
*** yangyapeng has joined #openstack-nova17:49
*** baoli has joined #openstack-nova17:49
*** jistr|afk is now known as jistr17:50
*** efoley has quit IRC17:51
*** psachin has quit IRC17:52
*** links has quit IRC17:52
*** trinaths has left #openstack-nova17:53
*** yangyapeng has quit IRC17:53
*** crushil has joined #openstack-nova17:55
*** eharney has quit IRC17:56
*** yangyapeng has joined #openstack-nova17:58
openstackgerritEric Fried proposed openstack/nova stable/pike: [placement] Update user doc with api-ref link  https://review.openstack.org/49974817:59
*** vikrant has quit IRC18:00
efriedWhee, stable branch bot notifications ^18:00
*** gszasz has quit IRC18:00
cburgessAnyone know if a resize of an instance will update the flavor extra specs stored in the instance_extra table for the instaince?18:00
*** yangyapeng has quit IRC18:02
*** ijw has joined #openstack-nova18:03
*** yamahata has joined #openstack-nova18:05
dansmithcburgess: it should yeah18:06
cburgessCool18:06
cburgessThanks18:06
*** dave-mccowan has quit IRC18:07
*** Tom has joined #openstack-nova18:09
*** edmondsw has joined #openstack-nova18:12
*** dave-mccowan has joined #openstack-nova18:14
*** edmondsw has quit IRC18:17
*** edmondsw has joined #openstack-nova18:17
*** lpetrut has joined #openstack-nova18:17
*** brad[]` has quit IRC18:20
mriedemmelwitt: swap from BFV to non-BFV, that's great18:20
*** browne has joined #openstack-nova18:20
*** jistr is now known as jistr|off18:21
melwitthaha, yep18:21
*** edmondsw has quit IRC18:21
*** browne has quit IRC18:22
*** kbaegis has quit IRC18:23
*** kbaegis has joined #openstack-nova18:24
*** edmondsw has joined #openstack-nova18:25
efried[resource providers] How does an individual resource get assigned an arbitrary property/value?18:27
efriedE.g. how does a PCI_DEVICE get a PCI address associated with it?18:27
efriedPerhaps the answer is, "In placement, it doesn't" ?18:28
dansmithefried: in placement, it doesn't18:28
dansmithefried: placement tracks resource types and quantities18:28
dansmithit's not a k=v store18:29
openstackgerritMerged openstack/nova master: [placement] Update user doc with api-ref link  https://review.openstack.org/49963518:29
dansmithplacement tracks how many are present and allocated,18:29
dansmithnova has to track *which* one is allocated18:29
*** edmondsw has quit IRC18:29
efrieddansmith So placement knows how many, but not individual identifiers (UUIDs)18:30
efriedand nova knows which ones are allocated18:30
dansmithcorrect, with an exception18:30
efriedwhere does the split occur?18:30
dansmithif a pci device has multiple VFs, it might be modeled as a resource provider of VF_THINGY resources18:31
dansmithbut still, placement will only know that it has 16 to provide, of which 3 are used18:31
dansmithwhere does what split occur?18:31
efriedYeah, so placement can tell me "X a resource_provider providing 8 GPUs with traits(a,b,c)"18:32
efriedAnd nova can say "take GPU with UUID Y from resource_provider X and assign it to VM 34"18:32
efriedBut where did we find out that one of the 8 GPUs was called Y?18:32
dansmithwell, none of that actually works today really, so.. nowhere :)18:33
dansmithhowever,18:33
dansmithnova has tables for pci devices reported from the compute nodes, with actual addresses and stuff18:33
dansmithif that's what you mean18:33
efrieddansmith But those tables aren't plugged into placement/RP yet, right?18:35
dansmiththey won't be really18:35
efriedCertainly not in their current form, yeah.18:35
dansmiththere is some work to do to plug in a pci device as a provider, under the compute provider, which provides VF_THINGYs or whatever18:36
dansmiththat's the nested resource providers stuff yeah18:36
openstackgerritDan Smith proposed openstack/nova master: Pre-create migration object  https://review.openstack.org/49895018:36
efrieddansmith Yeah, okay.  I'm trying to synthesize ^ with stuff jaypipes has said plus functionality needed by e.g. HyperV (claudiub) and PowerVM (moi) and others (various DOA blueprints) for discussion at the PTG.18:37
dansmithyeah, good effing luck with that :P18:37
*** salv-orlando has joined #openstack-nova18:38
efriedSo it seems like what came out of the above is: We don't have a framework in place that knows how to identify individual resources within a RP.18:38
efriedAnd18:38
efriedWe need that.18:38
efriedIf we're going to talk about device passthrough of any sort (GPU, SR-IOV, etc.)18:39
dansmithyes, I still have minor issues with the way you're phrasing it,18:39
dansmithbut only because RP is really a placement thing and placement won't ever know *which* one18:39
dansmithbut from nova's perspective it'll be closer to what you're saying18:39
dansmithwell,18:39
efrieddansmith Please do help me phrase things correctly.18:40
dansmithpci passthrough of specific SRIOV devices works today,18:40
efriedvia placement?18:40
dansmithit won't ever be *via* placement, but we'll be using placement to do our accounting of *how many* of those things we have available18:40
efriedSo part of what I'm driving here is total replacement of the existing PCI passthrough setup.18:40
dansmithit won't be materially different from today, except faster, cleaner, and less racy18:40
dansmithno, because the existing pci passthrough stuff knows *which* and placement does not and will not18:41
dansmithin tha' future,18:41
dansmithwe'll pick a host with enough GPU_THINGs, reserve one of the eight it provides,18:41
dansmithand then later we get to the compute mostly guaranteed that one will be available, where we'll pick the actual one18:42
dansmithbut placement will only ever know that we're using one of the eight18:42
efriedWho's that second 'we'?18:42
efriedThe virt driver?18:42
efriedThe resource tracker?18:42
dansmiththe we before "pick the actual one" ?18:42
efriedyeah18:42
*** salv-orlando has quit IRC18:43
dansmithwell, today it's super confusing I think, as it's kindof "the scheduler filter" I think18:43
dansmithfor certain things18:43
dansmithbut regardless,18:43
dansmiththat we will be something on the nova side, likely closer to the compute node than not18:43
dansmithclear as mud? :)18:43
dansmithjaypipes may have a better idea of how that will actually shake out long term,18:43
dansmithbut regardless, placement will only ever be counting things, not choosing things18:43
efrieddansmith Yeah, this is a shared jaypipes dream.18:44
efriedLest you should think it was just efried's pipe dream18:44
efriedOkay, so there's gonna be a generic device passthrough management module of some sort that sits in nova and coordinates among placement, scheduler, and virt driver to do whitelisting, claims, allocations18:45
dansmithwell, there is that today :)18:46
efriedJust for PCI, right?18:46
dansmith(sans the telling-placement-about-it) thing18:46
dansmith...just for pci.... aren't we talking about pci here?18:46
efriedWell, that's one of Jay's bugbears: it should work the same for any device, not just PCI.18:47
dansmithum18:47
dansmithI'm confused then18:47
efriedWhich intersects with one of my bugbears, which is: not every device has a PCI address.18:47
dansmithGPU devices need not be managed as raw PCI devices for this I think18:48
dansmithmaybe that's what you mean18:48
dansmithso I think eventually you should be able to say I want VGPU=1, traits=nvidia,gen518:48
dansmithand placement will pick you a host that has one of those available18:49
*** armax has quit IRC18:49
dansmithwhen you get to the host, that compute node will tell the virt driver (which I think will be generalizing gpus, at least in the case of libvirt), to give it a gpu, which it'll assign to your guest18:49
artomefried, is not every device having a PCI address a problem? My understanding is that the compute reports its resources (devices) to placement18:49
artomHow it figures out what resources it has is up to it18:49
dansmithartom: it doesn't report which resources it has, it reports how many of each it has18:50
artomdansmith, ah, right, thanks18:50
efriedRight right.  So there's the gap.  Right now, artom, not having a PCI address *is* a pretty serious problem.18:50
openstackgerritLucian Petrut proposed openstack/nova master: HyperV: Perform proper cleanup after failed instance spawns  https://review.openstack.org/49969018:50
artomSo for PCI devices it can use addresses, for other stuff, or PCI devices that don't have addresses for whatever reason, it can use a different mechanism18:50
*** annegentle has joined #openstack-nova18:51
efriedBecause the existing PCI device management subsystem expects every device it gets from the virt driver to have a PCI address in domain:bus:slot.func format.18:51
artomefried, ah, it's a problem because we can't manage them with the current way of doing things?18:51
dansmithfor devices we can generalize (like a GPU or NIC) we can talk about what we want in terms of quantity and traits18:51
dansmithwe can kindof ask for that in the flavor today,18:51
dansmithbut we're not exposing things like GPUs from things like libvirt yet,18:52
dansmithwhich needs to happen18:52
efried"ask for that in the flavor today" - are you talking about pci_passthrough:alias or something else?18:53
dansmithno,18:53
dansmithin the flavor, you can do things like resources:VGPU=118:53
dansmithand placement will not consider hosts that don't expose a VGPU resource type that has at least one available18:53
dansmithnothing does right now, but you can ask for it18:53
*** liverpooler has joined #openstack-nova18:54
efriedheh, okay.  But we don't have any accomodation for resources:PCI_DEVICE=1,traits=whatever ?18:55
dansmithwell, that doesn't make sense18:55
dansmithyou wouldn't ask for one pci device, any pci device18:55
dansmithlike "give me a nic, or a sata controller, or a serial UART, I'll take anything!"18:55
efriedNo, I agree that's too broad.18:55
artomMaybe they're working on the pci kernel subsystem ;)18:56
dansmithbut you might ask for a NIC or a NIC_PF or a NIC_VF I thnk18:56
efriedAnd I *think* I see that we can accomodate broad groupings18:56
efriedBut I'm concerned that we can't accomodate narrow groupings.18:56
*** eharney has joined #openstack-nova18:57
efriedIn particular, what if I want a specific device?18:57
dansmithjay might argue that we should ask for a NIC=1, traits=definiteily_a_pf18:57
*** yangyapeng has joined #openstack-nova18:57
artomefried, define 'specific device'?18:57
dansmithefried: like "give me device 00:01:5f on host $foo" ?18:57
efried"device with UUID X"18:57
artomBecause the 'non-cloud way of doing things' argument will come up really fast with that one ;)18:57
dansmithbecause that's not a thing we want to do18:57
dansmithyeah18:57
efriedheh18:57
dansmithreeeeeal fast :)18:57
efriedWell, okay, let me put it a different way.18:58
* dansmith gets out his nerf guns18:58
efriedI want my aliasing to be able to create a group of specific devices.18:58
openstackgerritMerged openstack/nova master: Fix _delete_inventory log message in report client  https://review.openstack.org/49883318:58
dansmithyou mean like we can do with pci today18:58
efriedEXCEPT18:59
dansmithwhere you choose a vendor and model, and we gather up all those things18:59
efriedtoday we can only do it by product/vendor ID.18:59
efriedAnd only a single product/vendor ID pair.18:59
dansmithright, because that's the industry standard18:59
* dansmith glares at efried's weirdo platform18:59
efriednono, this isn't a weirdo platform thing anymore.18:59
efriedI have two NICs, exact same vendor/product IDs18:59
efriedBut they're attached to different networks.19:00
efriedI don't want them in the same alias group19:00
dansmithright, so you ask for a nic attached to network foo,19:00
dansmithnot "give me the fifth nic from the left"19:00
dansmithNIC=1, traits=network-public19:00
dansmithor something19:00
*** mnestratov has quit IRC19:00
efriedRight, got it.19:00
artomSo that would put potentially mutable deployment details into the nova.conf on the compute?19:01
*** rcernin has joined #openstack-nova19:01
artomThat seems... unwise19:01
dansmithartom: well, that's kinda part of the problem with the pci stuff today,19:01
dansmithbut the nic attachment thing is managed dynamically today I think19:01
dansmithlike we have some way of correlating actual nics to what physical network they're attached to19:01
*** yangyapeng has quit IRC19:01
efriedFor SR-IOV we do19:02
dansmithright19:02
efriedpci_passthrough_devices lists a physical_network on a PF19:02
dansmithyeah19:02
efriedBut that's a single, specific attr19:02
dansmithartom: so yeah if someone goes and moves the yellow cable to the blue port in the datacenter, then bad things happen, but that's kinda the risk you run with giving people hardware passthrough It hink19:03
efriedSo with generic device management, you could have arbitrary traits, one of which is physical_network19:03
artomYeah, and now that I think about it more, there's no way to avoid it really19:03
artomNo sane way, at any rate19:03
dansmithefried: yeah like maybe you'd want has-tls-offload on your nic as well as physnet-private3719:04
artomUnless you want to start having admin REST APIs where you associate device addresses with what network they're connected to19:04
*** jose-phillips has quit IRC19:04
efriedSo qualitative attributes are handle via traits; and in the example of physical_network, I sorta have to have the key and value both stuffed into the value?19:04
*** gbarros has joined #openstack-nova19:04
efriedLike, CUSTOM_NETWORK_MYNET would be a trait?19:05
dansmithefried: well, you have to arrange things as traits, not k=v19:05
dansmithyes19:05
efriedAnd I'd have to have a separate one for every network.19:05
efriedOkay; so how are qualitative attrs handled?19:05
efriedLike, "give me a VGPU >= 10GHz"19:05
dansmithwe don't do that19:05
artomActually, in that situation, wouldn't the physical network become a resource, not a trait?19:05
efriedsorry ^ quantitative19:06
dansmithefried: we don't do that :)19:06
efriedAre we gonna?19:06
dansmithevery time someone brings it up, jay has an aneurism19:06
efriedReally?  Cause he's the one who brought it up.19:06
dansmithit's too much complexity I think19:06
dansmithwe have to model something19:07
*** jose-phillips has joined #openstack-nova19:07
dansmithso let's say you had some 5GHz and some 10GHz gpus19:07
*** edmondsw has joined #openstack-nova19:07
efriedHere's a jaypipes quote: "With the advent of the resource provider modeling, which includes an appropriate modeling of quantitative and qualitative things split out into resources (with inventory and allocation) and traits, we have a system that can (and IMHO should) be the basis for any future improvements to device management in Nova."19:07
dansmithyou could have traits of gpu-5ghz on the 5ghz ones and gpu-5ghz and gpu-10ghz on the 10s19:07
*** ijw has quit IRC19:08
dansmithefried: yep, totes19:08
efrieddansmith So what did he mean by "quantitative"?19:08
dansmithefried: counts of resources19:08
efriedoh.19:08
dansmithefried: counts of actual things19:08
efriedBugger.19:08
dansmithso my model above19:08
dansmithif you care about the fast one, you ask for a gpu-10ghz and you would weed out the 5s19:09
efriedBut if you want to set a minimum, you'll never get the 10s19:09
dansmithif you want at least 5, you would ask for that, and might get a 10 if that's how it falls19:09
dansmithI don't get that last statement19:09
efriedHuh?  How would that work?19:09
dansmithso,19:10
efriedPlacement doesn't know that "gpu-10ghz" is an okay thing to match to "gpu-5ghz"19:10
dansmiththe 10g gpus has at-least-5g and at-leadt-10g traits attached19:10
efriedIt doesn't even know they're related19:10
dansmithright,19:10
dansmithwhich is why you put both traits on the 10s19:10
efriedohjeez19:10
dansmithand arrange your grammar in terms of traits19:10
efriedokay, I reread your original statement, which I misread the first time.19:11
artomWe need nested traits ;)19:11
dansmiththe reason for doing this is that it's easy to model to everything19:11
efried"easy"19:11
dansmithcompare this which is numerical to processor flags19:12
dansmithI can't say "give me a cpu with at least sse3"19:12
*** edmondsw has quit IRC19:12
efriedI don't know what that means19:12
dansmithbecause there were later procs without those things because they weren't the high-end one, but were faster, and had some other features that earlier ones didn't19:12
dansmithi.e. processor flags are not numerical, linear, and neat sets19:12
efriedokay, right, I get that - those are qualitative measures.  That's different.19:13
efriedA proc either has that feature or it doesn't.19:13
*** sridharg has quit IRC19:13
efriedI just don't see this model-quantity-as-quality thing scaling.19:13
efriedWhat if I've got to deal with microversions or something.19:14
dansmithum, what?19:14
*** hoonetorg has joined #openstack-nova19:14
efriedI don't want to have to tag my resource provider with version-at-least-1.1,version-at-least-1.2,version-at-least-1.3,version-at-least-1.4,...19:15
*** krtaylor has quit IRC19:15
dansmithefried: so you want to add semver understandings to a request processor for things?19:15
*** ijw has joined #openstack-nova19:16
*** slaweq has joined #openstack-nova19:16
dansmithis 1.4.3 > 1.3.7?19:16
efriedyes it is; and yes, but not limited to semver.19:16
dansmithno it's not19:16
*** slaweq has quit IRC19:16
*** ijw has quit IRC19:16
dansmithbecause I need a particular bug fix that was backported to 1.3.7 and 1.4.519:16
efried1.4.3 isn't > 1.3.7 ?19:16
dansmith1.4.3 will not give me the bug fix, but you would choose it19:16
*** ijw has joined #openstack-nova19:16
*** slaweq has joined #openstack-nova19:16
dansmithso then I need to say >= 1.3.7 || (! <1.4.6)19:17
dansmithor something19:17
dansmithand that gets crazy19:17
dansmithwhich is why boiling this down to abstract traits is useful19:17
artomWhat real resource would even have something like thing?19:18
dansmithit won't let you model everything down to the tiniest detail, but it's also something that people can grasp and can be reasonably generic19:18
dansmithartom: a hypervisor19:18
artomI understand clock speeds of various kinds of processors, but...19:18
dansmithartom: I assume that's where he was going19:18
dansmithand it's a common thing19:18
dansmithpeople need to be on at least hyperv 2012.4 in order to be able to use some fragile windows  driver19:18
dansmithso instead of them needing to know versions, you can expose has-multiqueue-nics or something19:19
efriedYeah; I was trying to come up with an example of something that could have a lot of different quantitative traits where enumerating them becomes very unwieldy.19:19
dansmithand then if you have an older release with that fix backported, then that's all that matters19:19
mriedembauzas: didn't you say that before 2.29 and the force flag on the evacuate API, that if you specified a host we'd bypass the scheduler, but now we only do it if you specify a host AND pass force=True?19:19
dansmithinstead of needing to know the version semantics of the thing you're asking for19:19
edleafedansmith: didn't we discuss trait comparisons like this a while ago, and concluded that anything beyond simple boolean "has trait" would be a unmanageable tangle of special comparison cases?19:20
dansmithedleafe: yes, precisely19:20
efriedSpitballin here, but what I think I would like to see is a way for me to pass some part of the request spec down to the virt driver, who's responsible for understanding it in whatever manner it wants.19:20
dansmithefried: and that is precisely what we do not want you to be able to do19:21
mriedembauzas: nvm, that's correct19:21
artomThat would *definitely* not scale19:21
dansmithwe have way too much of that shit today19:21
dansmithyeeeeah.19:21
artomEvery boot request would go to every compute?19:21
mriedemif you pass 2.1 and host, force ends up being None in the API and we pass the host to conductor, which then bypasses the scheduler19:21
*** brad[] has joined #openstack-nova19:21
efriedartom ohh, I see.19:21
edleafeHey! Why don't we allow *extensions*? That'll solve all these problems!19:21
efriedWay it's set up today, you can do the whole resource allocation business based on what the compute told you last time it checked in.19:22
* dansmith fires his loaded nerf guns at edleafe 19:22
*** jose-phillips has quit IRC19:22
*** Tom has quit IRC19:22
efried...from a centralized spot (placement/scheduler)19:22
dansmithand don't forget multi-hypervisor clouds19:22
dansmithwhere much of the details aren't known until you get down to the compute, so if you couldn't pick the right one based on some generic properties,19:23
dansmithyou get there and libvirt says "wtf is a hyperv 2012.4?"19:23
dansmiththat's hugely wasteful19:23
efriedSo if I need to do something funkily virt-specific, I have to do it at get_inventory time.19:24
efriedand setting-up-resource-providers time.19:24
dansmithyou have to expose it as a generic count of resources with traits19:24
efriedbut constrained to ... yeah, what you said.19:24
*** pchavva has quit IRC19:25
dansmithbecause that's a model that the rest of nova can understand19:25
artomThere was talk of doing virt driver capabilities as resources (or traits?), I think?19:25
dansmithyep, exactly his hypervisor version query19:25
artomWell, nova virt driver != hypervisor, but yeah, same gist19:26
*** liverpooler has quit IRC19:26
efriedWhich is why we need nested resource providers: so my hypervisor can be an outermost one and tag itself with e.g. "CUSTOM_AIX_CAPABLE", and then everything else underneath that will inherit that trait?19:26
dansmithartom: sure, some of both19:26
dansmithefried: no, no trait inheritance plans that I know of,19:27
dansmithbut if you request that trait from your compute node, then you won't consider resources under compute nodes that don't19:27
artomefried, I think the nested stuff was thought up for PFs/VFs19:27
efriedHow do I request a trait for my compute node?19:27
efriedI can't... ask for a compute node as a resource19:28
efriedcan I?19:28
dansmithno19:28
*** slaweq_ has joined #openstack-nova19:28
*** slaweq has quit IRC19:28
edleafeFlavor extra_specs19:28
dansmithI just mean a trait for whatever the top-level resource provider is that has your custom_aix_foo thing on it19:28
*** edmondsw has joined #openstack-nova19:28
efriedWhat, like a VCPU??19:30
efriedSorry, thought I was getting the picture here, but that last one threw me for a loop.19:30
dansmithefried: it was your example above19:30
dansmith<efried>Which is why we need nested resource providers: so my hypervisor can be an outermost one and tag itself with e.g. "CUSTOM_AIX_CAPABLE", and then everything else underneath that will inherit that trait?19:30
efriedIt's the hypervisor that's AIX-capable19:30
dansmithI'm just drilling in on your comment about inheritance19:30
efriedAs in, you can deploy an AIX VM on it.19:31
dansmithright so that would be virt driver capabilities19:31
efriedRight, where/how do those get exposed?  Is that still somehow in the placement universe?19:31
dansmithso we're asking for a resource provider that has at least 2 VCPUs available, at least 1G of memory, with a trait of CUSTOM_AIX_WHYWOULDIWANNA19:32
dansmithwhich would be your node with a virt driver that exposes sufficient inventory and traits19:32
artomWait, do traits apply to resources or resource providers?19:32
*** edmondsw has quit IRC19:32
dansmiththere is no resources, only resource providers :)19:33
dansmitha resource provider has a set of traits19:33
dansmitha request demands or prefers traits, and asks for quantities of resources by name19:33
artomErr19:33
dansmithwe find providers that have sufficient inventory and traits19:33
efriedokay, right, my host is the resource provider that provides VCPU and MEM_GB and DISK_GB19:33
edleafeartom: inventory == resources19:33
artom"quantities of resource"19:33
efriedand the resource provider has traits19:34
artom"there is no resources"19:34
dansmithartom: meaning there is no object called a resource19:34
artomThis isn't the Matrix, yo19:34
efriedartom I *think* dansmith means that *placement* doesn't know anything about specific resources.19:34
dansmithartom: there are resource providers that have quantities of a given type, but that type isn't a thing that can have a trait, only the provider19:34
dansmithefried: yeah19:34
edleafeartom: no, but I have an inventory with resource_class == "spoon"19:34
efried(Could it have been Ghostbusters, not Matrix, dansmith?)19:34
*** xyang1 has quit IRC19:35
dansmithI think I was thinking "there is no try, only do" or whatever19:35
artomThat's Star Wars19:35
dansmithyeah, I dunno, I'm not a big enough nerd19:35
efriedYup, and we've reached our limit of three nerd movie franchises.19:35
dansmithyeah,19:36
efriedresource_class=SPOON would have a quantity of 8 or whatever19:36
dansmithand eff jay for being on a plane and leaving me with you wolves19:36
efriedplacement doesn't know about individual spoons19:36
dansmithefried: well, SPOON=8 for consistency but yeah19:36
artomThere must always be a core in #openstack-nova19:36
artom(Speaking of wolves)19:36
edleafeer, CUSTOM_SPOON, but whatever19:37
dansmithedleafe: if it's a custom resource yeah19:37
dansmithedleafe: you understand all this, why are you making me squirm alone? :D19:38
efriedBut if we had soup spoons and dessert spoons, we would either have to make two separate resource classes (SPOON_SOUP, SPOON_DESSERT), or two separate resource providers with traits (CUSTOM_SPOON_SOUP, CUSTOM_SPOON_DESSERT)19:38
*** brad[] has quit IRC19:38
edleafeefried: pretty much, yeah19:38
mriedemit'd be a spoon with different traits19:38
efriedmriedem The spoon doesn't have traits.19:39
*** salv-orlando has joined #openstack-nova19:39
dansmithyeah19:39
edleafeonly spoon providers can have traits19:39
efriedThe resource provider has traits19:39
efriedyeah19:39
tbachmanthere is no spon19:39
tbachmanspoon19:39
artomAnd anyways, there is no19:39
mriedemso the spoon drawer is the provider19:39
artomDammit!19:39
mriedemthat provides spoons19:39
* tbachman runs and hides19:39
* artom glares at tbachman 19:39
tbachmanlol19:39
efriedmriedem Right, but you can't have soup spoons and dessert spoons in the same drawer.19:39
* edleafe bends a spoon with his mind19:39
dansmithokay so this conversation is over right/19:39
mriedemi do19:39
mriedemi have all sorts of spoons in the same drawer19:39
*** ijw has quit IRC19:39
efriedDude, okay, we're getting meta here, but I'm actually still trying to understand this seriously.19:40
mriedemwhat psycho separates them19:40
edleafeefried: ok, let me try, using the spoons19:40
mriedemdid someone make a soundgarden joke yet?19:40
artomWe've only covered Ghostbusters, the Matrix, Star Wars, and GoT19:41
bauzasmriedem: that's correct, before 2.29, when providing a target, we were directly calling the compute service without asking the scheduler to verify it19:41
edleafeif you have a drawer with 2 types of spoons, you have to created nested resource providers with the different traits, and assign the spoons as inventory to each19:41
efriededleafe Okay, so that's yet a third way of doing it.19:41
edleafethe drawer would be the root provider19:41
edleafeefried: that's the only way with just one drawer19:41
efriedand the slots in the silverware holder thingy would be the child providers19:41
*** tbachman has quit IRC19:41
edleafeefried: yup19:42
mriedembauzas: yes this always trips me up https://github.com/openstack/nova/blob/2a4ca8bd6aa40ccd26300feaef4267aa71f69abf/nova/compute/api.py#L401719:42
mriedembecause force is None if microversion < 2.2919:42
efriededleafe I thought I could create a separate resource class?19:42
artomIt's a purely arbitrary construct though - the spoons can be inventory of RPs with different traits, or there can be one RP with two inventories, one for each kind of spoon19:42
*** rajathagasthya has quit IRC19:43
bauzasmriedem: yeah, because we still need to support microversion < 2.29 :)19:43
artom(Right?)19:43
bauzasmriedem: so, like you said, Force=None if so19:43
edleafeefried: sure, but then you wouldn't have "spoons", you'd have dessert_spoon and soup_spoon19:43
efriedRight, okay.19:43
*** salv-orlando has quit IRC19:43
efriedIf we don't have nested resource providers yet19:44
mriedembauzas: right, it's just confusing19:44
edleafeefried: we still have some work to do with traits and nested providers before any of this will actually work19:44
mriedemlooks like our api ref docs also say a host is required in the request when live migrating, which is wrong19:45
dansmithmriedem: so would you kill me if I wasn't around for the nova meeting today?19:45
mriedemi'd like to not be around for the nova meeting today19:45
dansmithis that a joke or are you hoping someone else would run it?19:46
mriedemin 15 minutes i'm going to be knee deep in in-laws19:46
mriedemi'll run it19:46
dansmithokay19:46
mriedemi'm just not happy about it19:46
dansmithhaving to run a meeting is like the best possible in-law scenario I can think of personally19:46
*** slaweq_ has quit IRC19:47
mriedemholy crap we actually do require that you specify the 'host' parameter in the os-migrateLive action19:47
mriedembut you can pass 'host': None19:47
mriedemdumb19:47
*** slaweq has joined #openstack-nova19:48
*** moshele has joined #openstack-nova19:49
efrieddansmith edleafe artom Thanks a bunch for the talk, guys.  I have a much better understanding now.19:50
openstackgerritMatt Riedemann proposed openstack/nova master: api-ref: add warnings about forcing the host for live migrate/evacuate  https://review.openstack.org/49976919:52
mriedembauzas: dansmith: cfriesen_: ^19:52
bauzasmriedem: I'm not sure the comment is really understanding19:54
*** egonzalez has joined #openstack-nova19:54
bauzasmriedem: why did you commented about the over-subscription ?19:54
bauzasmriedem: anyway, commenting the change19:55
*** annegentle has quit IRC19:55
*** yangyapeng has joined #openstack-nova19:58
mriedemwell i was thinking more about failing a resource claim, but that could be removed19:59
mriedemand just generalized19:59
*** slaweq_ has joined #openstack-nova20:00
*** slaweq has quit IRC20:02
*** yangyapeng has quit IRC20:02
bauzasanyway, I'm bad at wording, so your call20:02
bauzasjust providing my thoughts that we should just be commenting at the top-level20:03
*** brad[] has joined #openstack-nova20:06
openstackgerritMatt Riedemann proposed openstack/nova master: api-ref: add warnings about forcing the host for live migrate/evacuate  https://review.openstack.org/49976920:07
*** smatzek has quit IRC20:08
*** rajathagasthya has joined #openstack-nova20:09
*** cristicalin has joined #openstack-nova20:09
cfriesen_taking a look20:10
openstackgerritIldiko Vancsa proposed openstack/nova-specs master: Add multiattach support to Nova  https://review.openstack.org/49977720:12
*** krtaylor has joined #openstack-nova20:16
*** jpena is now known as jpena|brb20:18
cfriesen_mriedem: v2 looks reasonable to me.20:21
*** slaweq_ has quit IRC20:30
*** lpetrut has quit IRC20:30
*** esberglu has quit IRC20:31
*** esberglu has joined #openstack-nova20:31
*** annegentle has joined #openstack-nova20:32
efrieddansmith edleafe artom Okay, here's a much better example.  I can create SR-IOV VFs on the fly.  On a given PF (which is a (nested) RP) I can create a maximum of 48 VFs.  But each can be assigned a minimum egress bandwidth, let's say as a percentage of the PF's total bandwidth.20:34
*** jose-phillips has joined #openstack-nova20:35
efried1) It would suck for my PF to have to say traits=egress-pct-capable-1,egress-pct-capable-2,...,egress-pct-capable-10020:35
*** esberglu has quit IRC20:36
efried2) Assuming I did the above, I ask for e.g. egress-pct-capable-75, you peel off one of the 48... but I can no longer create 47 more VFs.  At a maximum, I can now create 25, assuming they each get 1% of the egress bandwidth.20:36
dansmithefried: that's the same as your gpu >= 10GHz example20:37
efriedYeah.  It's just a more convincing case because I've got 100 values instead of like three or four.20:37
efriedand it's also a real thing20:37
dansmithefried: you could model bandwidth as a resource amount though20:37
efriedNow, I can probably do #2 just by, next time you ask me for get_inventory, I bust my number down to 25 (or blow up my reserved number)20:38
cfriesen_this is for kind of a weird use-case...is it possible to set up a nova-api with a configuration read from nova.conf such that only a specific user (presumably with admin privileges) can issue requests, and no other users can (even if they're in keystone)?20:38
dansmithefried: no you can't20:38
dansmithefried: inventory doesn't change due to allocation, otherwise you're breaking the other parts of the model20:38
edleafeefried: when you add the inventory, you can set a minimum for a request20:38
efrieddansmith Then why is get_inventory called more than once?20:38
artomdansmith, actually your last sentence is problematic for vGPUs20:38
*** slaweq has joined #openstack-nova20:39
dansmithefried: because you could get more inventory periodically20:39
edleafeartom: why?20:39
efriedwhat, hot-plugging stuff?20:39
dansmithefried: sure20:39
*** salv-orlando has joined #openstack-nova20:39
artomedleafe, there's this thing where a GPU can give you different numbers of vGPUs based on how many, err, I think shaders, or cores, each gets20:40
dansmithefried: can we continue this conversation in denver? I think it'll be more productive20:40
*** ijw has joined #openstack-nova20:40
dansmithartom: right, but a lot of the existing models for this end up with you carving those resources out into multiple virtual devices,20:40
artomSo a GPU with, for example, 12 shaders/cores, can give you 2 vGPUS with 6 each, or 4 with 3 each20:40
dansmithand then those devices can be assigned and de-assigned20:40
*** slaweq has quit IRC20:40
dansmithyou _could_ do the assignment of shaders completely dynamically,20:40
efrieddansmith Well, yeah, what I'm trying to do is compose notes in enough detail - and with enough of the "easy" questions answered - that we can have a productive conversation in Denver (and not devolve into spoon metaphors).20:41
edleafeartom: one of the things that came up in discussions in Austin about CAPI and such was that management of dynamic resources would never be handled by nova20:41
dansmithbut in reality, I think most cases will be satisfied by carving up your GPUs into chunks20:41
*** slaweq has joined #openstack-nova20:41
edleafeso if your resources change, the virt driver has to report that change20:41
artomedleafe, they would, I'm pretty sure20:41
dansmithefried: sure, I know, but it'll go a lot quicker in person I think20:41
artomedleafe, nova would still have to update its inventories though20:42
edleafeartom: it does that periodically, based on what the virt driver tells it20:42
efriedYeah, I'd like to understand more about how it breaks the model for me to change the inventory of something - for whatever reason I see fit.20:42
artomedleafe, ah, we're fine then20:42
efried^ me == virt driver in this case20:42
* artom has to run20:43
*** armax has joined #openstack-nova20:43
cristicalinhy, anyone have an idea why instances libvirt.xml may be missing metadata for user_id / project_id ?20:43
dansmithefried: I said in response to allocation20:43
edleafeefried: I always thought you looked like a virt driver20:43
*** moshele has quit IRC20:43
efrieddansmith Well, yeah, it's sort of in response to allocation.20:43
efriedI guess I would call it in response to actually doing the virt driver work of satisfying the allocation.20:43
dansmithefried: you should be exposing how much of a thing you have and the allocations come out of that20:43
dansmithefried: you don't expose "available" you expose "total"20:43
*** esberglu has joined #openstack-nova20:44
efriedHm, so I guess in this scenario I don't expose SRIOV_VF=48; instead I expose SRIOV_VF_EGRESS_PERCENTAGE_POINT=10020:44
*** eharney has quit IRC20:45
*** salv-orlando has quit IRC20:45
*** cleong has quit IRC20:45
efriedbut that doesn't allow me to model the max #VFs as 48 at the same time.  Or two separate VFs in the same claim.20:45
*** ijw has quit IRC20:45
*** annegentle has quit IRC20:46
efriedick20:46
dansmithefried: regardless,20:47
dansmithif your NIC has 10G of bandwidth, you can have your provider expose CUSTOM_GIGS=10,20:47
*** artom has quit IRC20:47
dansmithand have your flavor consume some number of those to avoid over-subscribing20:47
cfriesen_efried: wouldn't you still say that you have 48 VFs total, and allocate from that?20:50
*** tonygunk has joined #openstack-nova20:50
openstackgerritMatt Riedemann proposed openstack/nova master: Modernize set_vm_state_and_notify  https://review.openstack.org/49979920:50
dansmithpresumably if you have 3 VFs left, but no GIGs left, you don't want to allocate any more20:51
cfriesen_efried: presumably you could also model total bandwidth, and divide it up nonuniformly between the VFs20:51
efrieddansmith So the VFs and the GIGs would be separate resource classes sitting next to each other, and you have to claim VF=1,GIG=2 or whatever in your request20:52
efriedcfriesen_ Could, but that kills the flexibility20:52
*** annegentle has joined #openstack-nova20:52
efriedcfriesen_ No idea at the outset how the end user is gonna want to split 'em up.20:52
dansmithefried: yeah, so you end up with either one capping the things that can be there20:52
dansmitheither you run out of tiny VFs or GIGs from requests with large bandwidth requirements20:53
*** yangyapeng has joined #openstack-nova20:53
tonygunkJust upgraded from Ocata to Pike and trying to upgrade nova DB - getting error: "AttributeError: 'module' object has no attribute 'get_rpc_transport'"20:53
tonygunkhttp://paste.openstack.org/raw/620137/20:53
efrieddansmith So in that scenario a claim that specifies VF=1 but doesn't specify GIG would have to fail.20:53
efriedI can't default GIG because placement wouldn't know about it.20:53
efriedBut20:53
efriedI would have to fail at compute20:53
dansmithefried: that'd be up to the guy making out the flavors yeah20:53
tonygunkAnyone know what is going on?20:53
dansmithtonygunk: you have an outdated oslo_messaging I think20:54
edleafeefried: sounds analogous to vcpu/ram/disk in splitting a physical server20:54
edleafeefried: it's all in how the flavors are configured20:54
dansmithedleafe: right, you waste some memory if you run out of disk20:54
dansmithwhich is why we have flavors anyway,20:54
dansmithso you can pack things so you don't waste stuff if you care about that20:55
dansmithinstead of just letting users request 1 cpu and 20TB of disk20:55
tonygunkdansmith: Ok - thanks - I'll see if that resolves it20:55
efriedAnd a flavor that specifies CPU but not memory is useless.20:55
efriedOkay, I dig it.  Thanks again.20:55
*** mnestratov has joined #openstack-nova20:55
cfriesen_efried: I meant what dansmith is saying....two separate resource classes20:56
*** vladikr has quit IRC20:56
efried(dansmith edleafe - that's the other thing I want to avoid in Denver - being the only one in the room needing to have basic concepts explained to him, and wasting everyone else's time.)20:56
efriedcfriesen_ Dig.20:56
dansmithefried: understood, it's just not as fun for me if we do it this way20:57
mriedemnova meeting in 3 minutes20:57
cfriesen_is it possible for an admin user to boot an instance "on behalf" of another user/project?20:57
dansmithmriedem: dude I cannot effing wait20:57
*** yangyapeng has quit IRC20:57
dansmithmriedem: PC BROS!20:57
efriedSorry dansmith.  I'll allocate you a predetermined number of units of your libation of choice.20:58
*** crushil has quit IRC20:58
dansmithefried: traits=wheat,unfiltered20:58
efriednoted20:58
mriedemdansmith: better check your privilege20:59
dansmithheh20:59
tonygunkdansmith: now I'm getting this error after upgrading oslo.messaging to 5.3021:01
tonygunkhttp://paste.openstack.org/raw/620138/21:01
dansmithtonygunk: paste is old? :P21:02
dansmithtonygunk: I can't help you as much with that one, sorry21:03
*** yusef has joined #openstack-nova21:04
*** ijw has joined #openstack-nova21:05
*** annegentle has quit IRC21:07
*** thorst_afk has quit IRC21:08
*** tbachman has joined #openstack-nova21:09
*** penick has joined #openstack-nova21:10
tonygunkdansmith: actually uninstalling and reinstalling PasteDeploy was the solution.. weird..21:11
dansmith*shrug* but good21:12
efriedtonygunk Seen that a hundred times.  Curse PasteDeploy!21:12
efriedSorry I didn't punch through your last paste, woulda been able to tell you right off.21:12
tonygunkefried: :-)21:13
*** crushil has joined #openstack-nova21:15
*** jpena|brb is now known as jpena21:15
*** ijw has quit IRC21:16
*** moshele has joined #openstack-nova21:16
*** tbachman_ has joined #openstack-nova21:17
*** tbachman has quit IRC21:17
*** tbachman_ is now known as tbachman21:17
*** moshele has quit IRC21:19
*** moshele has joined #openstack-nova21:20
*** dave-mccowan has quit IRC21:20
efriedI think if you give me nested resource providers, with some careful modeling I can do everything in the virt driver.  The rest of nova doesn't need to know about a device as being any different from any other resource.21:22
efriededleafe You mentioned earlier that "we still have some work to do with traits and nested providers before any of this will actually work" - somewhere I can find a summary of what's still on the table?21:27
*** moshele has quit IRC21:29
*** esberglu has quit IRC21:31
*** catintheroof has quit IRC21:31
cfriesen_efried: I think the PTG etherpad has some links21:33
efriedah, cool21:33
efriedthanks cfriesen_21:33
*** cfriesen_ is now known as cfriesen21:34
*** burt has quit IRC21:34
*** thorst_afk has joined #openstack-nova21:34
*** annegentle has joined #openstack-nova21:34
*** thorst_afk has quit IRC21:36
cfriesenefried: I think this is the nested providers work: https://review.openstack.org/#/q/topic:bp/nested-resource-providers,n,z21:37
edleafeefried: yeah. There's the series from alex_xu starting with https://review.openstack.org/#/c/489206/, as well as Jay's nested RP series starting with https://review.openstack.org/#/c/470575/21:38
efriededleafe cfriesen Thanks.  Looks like not toooo much; hopefully containable in early q?21:38
*** egonzalez has quit IRC21:38
edleafeefried: only when you look at the code with light-red-tinted lenses21:38
cfriesenefried: edleafe: I think there's also a missing piece to wire it up to live migration21:38
*** thorst_afk has joined #openstack-nova21:39
efriedSigh.21:39
efriedI just thought you were blushing.21:39
mriedemthere are bugs that still need to be fixed from claims in the scheduler before we can add nested and shared RPs21:40
mriedemthe move operations are all over the floor21:40
openstackgerritMatt Riedemann proposed openstack/nova master: Modernize set_vm_state_and_notify  https://review.openstack.org/49979921:40
*** salv-orlando has joined #openstack-nova21:40
mriedemfor anyone that cares, the main ones i'm tracking for backports to pike are21:41
mriedem1. https://bugs.launchpad.net/nova/+bug/171378621:41
openstackLaunchpad bug 1713786 in OpenStack Compute (nova) "Allocations are not managed properly in all evacuate scenarios" [High,In progress] - Assigned to Matt Riedemann (mriedem)21:41
*** penick has quit IRC21:41
mriedem2. https://bugs.launchpad.net/nova/+bug/171379621:41
openstackLaunchpad bug 1713796 in OpenStack Compute (nova) "Failed unshelve does not remove allocations from destination node" [High,Triaged]21:41
mriedemi think that's it for right now21:41
mriedemonce those are fixed and backported to pike and merged, we can do a pike patch release21:41
*** abalutoiu has joined #openstack-nova21:42
mriedemi've got the fix for half of the first bug up for review21:42
bauzasroger.21:42
mriedemstarting here https://review.openstack.org/#/c/499678/221:42
mriedemtomorrow i'm going to work on the 2nd half, which is if evacuate fails on the compute, we have to cleanup the allocations created by the scheduler for the dest node21:43
*** abalutoiu has quit IRC21:43
*** Donckers has quit IRC21:43
mriedemlike, if the rebuild claim fials21:43
mriedem*fails21:43
*** baoli has quit IRC21:43
*** baoli has joined #openstack-nova21:45
*** salv-orlando has quit IRC21:45
*** tidwellr has quit IRC21:46
cfriesenquestion about flavors...if I create a flavor that isn't public, does that automatically give my tenant access to that flavor?  if so, where is that code?21:46
mriedemstephenfin: gibi: sdague: fyi, new docs theme breaks the hide/show ability in the versioned notifications samples https://bugs.launchpad.net/nova/+bug/171436321:47
openstackLaunchpad bug 1714363 in OpenStack Compute (nova) "docs: versioned notification samples are always shown now and you can't hide them" [Medium,Confirmed]21:47
mriedemcfriesen: don't think so21:48
mriedemlooking at nova.compute.flavors.create21:48
*** kylek3h_ has quit IRC21:48
*** priteau has quit IRC21:49
*** baoli has quit IRC21:50
cfriesenmriedem: good, I'm not blind. :)21:51
*** yangyapeng has joined #openstack-nova21:54
*** lyan has quit IRC21:56
*** lyan has joined #openstack-nova21:56
*** yangyapeng has quit IRC21:58
*** tbachman has quit IRC21:59
*** tbachman has joined #openstack-nova21:59
*** ssmith has quit IRC22:00
*** tbachman has quit IRC22:04
*** shan has quit IRC22:05
openstackgerritEric Fried proposed openstack/nova master: Include /resource_providers/uuid/allocations link  https://review.openstack.org/49982622:07
*** gouthamr has quit IRC22:08
*** ijw has joined #openstack-nova22:17
*** cristicalin has quit IRC22:19
*** lyan has quit IRC22:20
*** ijw has quit IRC22:23
*** ijw has joined #openstack-nova22:27
*** annegentle has quit IRC22:27
*** krtaylor has quit IRC22:28
*** salv-orlando has joined #openstack-nova22:29
*** edmondsw has joined #openstack-nova22:30
*** rcernin has quit IRC22:30
openstackgerritMerged openstack/nova master: api-ref: add warnings about forcing the host for live migrate/evacuate  https://review.openstack.org/49976922:32
*** slaweq has quit IRC22:32
*** itlinux has quit IRC22:34
*** annegentle has joined #openstack-nova22:34
*** thegreenhundred has quit IRC22:38
*** armax has quit IRC22:41
*** armax has joined #openstack-nova22:41
*** jgriffith has quit IRC22:43
*** jgriffith has joined #openstack-nova22:44
*** claudiub has quit IRC22:47
*** mnestratov has quit IRC22:48
*** yamahata has quit IRC22:49
*** slaweq has joined #openstack-nova22:49
*** slaweq has quit IRC22:54
*** yangyapeng has joined #openstack-nova22:55
*** vladikr has joined #openstack-nova22:55
*** yangyapeng has quit IRC22:59
*** salv-orlando has quit IRC23:01
*** salv-orlando has joined #openstack-nova23:02
*** annegentle has quit IRC23:03
*** salv-orlando has quit IRC23:06
*** salv-orlando has joined #openstack-nova23:06
*** jpena is now known as jpena|off23:09
*** ijw has quit IRC23:11
*** ijw has joined #openstack-nova23:12
*** ijw has quit IRC23:16
*** rajathagasthya has quit IRC23:18
*** kbaegis has quit IRC23:20
*** hongbin has quit IRC23:22
*** salv-orlando has quit IRC23:23
*** salv-orlando has joined #openstack-nova23:23
*** salv-orlando has quit IRC23:28
*** yamamoto_ has joined #openstack-nova23:31
*** yamamoto_ has quit IRC23:31
*** yamamot__ has joined #openstack-nova23:31
*** slaweq has joined #openstack-nova23:33
*** dtp has quit IRC23:34
*** slaweq has quit IRC23:38
*** Nel1x has joined #openstack-nova23:38
*** thorst_afk has quit IRC23:39
*** tbachman has joined #openstack-nova23:41
*** chyka has quit IRC23:42
*** ijw has joined #openstack-nova23:45
*** salv-orlando has joined #openstack-nova23:47
*** edmondsw has quit IRC23:48
*** priteau has joined #openstack-nova23:49
*** artom has joined #openstack-nova23:50
*** ijw has quit IRC23:51
*** yangyapeng has joined #openstack-nova23:52
*** sdague has quit IRC23:54
*** priteau has quit IRC23:54
*** catintheroof has joined #openstack-nova23:55
*** marst has quit IRC23:57
*** yangyapeng has quit IRC23:57
*** Apoorva_ has joined #openstack-nova23:57
*** edmondsw has joined #openstack-nova23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!