Tuesday, 2017-09-05

*** Tom_ has quit IRC00:01
*** yangyapeng has joined #openstack-nova00:04
*** kbaegis has quit IRC00:05
*** yangyapeng has quit IRC00:09
*** kbaegis has joined #openstack-nova00:15
*** claudiub|2 has quit IRC00:17
*** kbaegis has quit IRC00:18
*** thorst_afk has joined #openstack-nova00:24
*** adisky__ has joined #openstack-nova00:26
*** edmondsw has quit IRC00:26
*** markvoelker has joined #openstack-nova00:26
*** crushil has quit IRC00:29
*** crushil has joined #openstack-nova00:29
*** crushil has quit IRC00:30
*** crushil has joined #openstack-nova00:31
*** kiennt has joined #openstack-nova00:47
*** jichen has joined #openstack-nova00:49
*** zhurong has joined #openstack-nova00:50
*** gbarros has joined #openstack-nova00:51
*** thorst_afk has quit IRC00:55
*** dixiaoli has joined #openstack-nova00:57
*** markvoelker has quit IRC00:59
*** zxy has joined #openstack-nova01:00
*** Shunli has joined #openstack-nova01:01
*** kbaegis has joined #openstack-nova01:09
*** yangyapeng has joined #openstack-nova01:11
*** ijw has quit IRC01:11
*** ijw has joined #openstack-nova01:16
*** david-lyle has joined #openstack-nova01:20
*** bkopilov has quit IRC01:28
*** baoli has joined #openstack-nova01:30
*** StevenK_ is now known as StevenK01:30
*** gcb has joined #openstack-nova01:34
*** thorst_afk has joined #openstack-nova01:39
*** thorst_afk has quit IRC01:39
*** takashin has left #openstack-nova01:44
*** TuanLA has joined #openstack-nova01:54
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi: Support live migration in pooled multi-nodes environment  https://review.openstack.org/48945101:55
*** markvoelker has joined #openstack-nova01:56
openstackgerritjichenjc proposed openstack/nova master: Update doc to indicate nova-network deprecated  https://review.openstack.org/50065401:59
openstackgerritHironori Shiina proposed openstack/nova-specs master: Ironic: Cold migration support  https://review.openstack.org/44915502:02
*** hongbin has joined #openstack-nova02:03
*** takashin has joined #openstack-nova02:03
*** phuongnh has joined #openstack-nova02:06
*** gouthamr has quit IRC02:08
*** thorst_afk has joined #openstack-nova02:17
*** thorst_afk has quit IRC02:17
*** hongbin has quit IRC02:18
*** baoli has quit IRC02:24
*** markvoelker has quit IRC02:30
*** Tom has joined #openstack-nova02:31
*** hongbin has joined #openstack-nova02:45
*** baoli has joined #openstack-nova02:45
*** Tom has quit IRC02:46
*** bkopilov has joined #openstack-nova02:46
*** Tom has joined #openstack-nova02:48
*** trinaths has joined #openstack-nova02:53
*** hongbin has quit IRC02:58
*** hongbin has joined #openstack-nova02:59
*** Tom has quit IRC02:59
*** Tom has joined #openstack-nova02:59
*** Sree has joined #openstack-nova03:01
*** Tom has quit IRC03:04
*** trinaths has left #openstack-nova03:04
openstackgerritTetsuro Nakamura proposed openstack/nova master: fix server creation error using az name with ':'  https://review.openstack.org/49072203:04
*** baoli has quit IRC03:07
*** gbarros has quit IRC03:07
*** thorst_afk has joined #openstack-nova03:18
*** ijw has quit IRC03:22
*** abhi89 has joined #openstack-nova03:23
*** thorst_afk has quit IRC03:23
*** kiennt_ has joined #openstack-nova03:33
*** kiennt has quit IRC03:36
*** kiennt_ is now known as kiennt03:38
*** kiennt_ has joined #openstack-nova03:44
*** kiennt has quit IRC03:47
*** links has joined #openstack-nova03:51
*** sridharg has joined #openstack-nova03:53
*** hshiina has joined #openstack-nova04:02
*** ijw has joined #openstack-nova04:03
*** slaweq has joined #openstack-nova04:03
*** hongbin has quit IRC04:05
*** ijw has quit IRC04:08
*** Sree has quit IRC04:08
*** slaweq has quit IRC04:08
*** Sree has joined #openstack-nova04:08
*** zxy has quit IRC04:12
*** Sree_ has joined #openstack-nova04:12
*** Sree_ is now known as Guest7480504:13
*** gcb has quit IRC04:13
*** kiennt_ is now known as kiennt_AWAY04:16
*** Sree has quit IRC04:17
*** udesale has joined #openstack-nova04:18
*** ratailor has joined #openstack-nova04:18
*** thorst_afk has joined #openstack-nova04:19
*** psachin has joined #openstack-nova04:21
*** thorst_afk has quit IRC04:23
*** hieulq has joined #openstack-nova04:24
*** tbh_ has joined #openstack-nova04:25
*** gcb has joined #openstack-nova04:26
*** zxy has joined #openstack-nova04:26
*** markvoelker has joined #openstack-nova04:27
*** zxy has quit IRC04:33
*** zxy has joined #openstack-nova04:34
*** yamahata has joined #openstack-nova04:47
*** ratailor has quit IRC04:49
*** pcaruana has joined #openstack-nova04:52
*** baoli has joined #openstack-nova04:54
openstackgerritTetsuro Nakamura proposed openstack/nova master: fix server creation error using az name with ':'  https://review.openstack.org/49072204:57
*** baoli has quit IRC04:59
*** markvoelker has quit IRC05:00
*** claudiub|2 has joined #openstack-nova05:07
*** jaosorior has quit IRC05:08
*** lpetrut has joined #openstack-nova05:09
*** ratailor has joined #openstack-nova05:12
*** shan has joined #openstack-nova05:12
*** liverpooler has joined #openstack-nova05:16
*** thorst_afk has joined #openstack-nova05:20
*** thorst_afk has quit IRC05:24
*** liverpooler has quit IRC05:27
*** liverpooler has joined #openstack-nova05:27
*** jaosorior has joined #openstack-nova05:30
*** Tom has joined #openstack-nova05:32
*** trinaths has joined #openstack-nova05:34
openstackgerritHironori Shiina proposed openstack/nova master: [WIP] ironic: Support cold migration  https://review.openstack.org/50067705:35
*** suresh12 has joined #openstack-nova05:38
*** lpetrut has quit IRC05:46
*** josecastroleon has joined #openstack-nova05:46
*** jaosorior has quit IRC05:47
*** moshele has joined #openstack-nova05:53
*** markvoelker has joined #openstack-nova05:58
*** Guest74805 has quit IRC05:58
*** lpetrut has joined #openstack-nova05:59
*** hoonetorg has quit IRC06:05
*** Sree_ has joined #openstack-nova06:05
*** Sree_ is now known as Guest4882606:06
*** Oku_OS-away is now known as Oku_OS06:12
*** lpetrut has quit IRC06:18
*** takashin_ has joined #openstack-nova06:18
*** takashin has quit IRC06:19
*** thorst_afk has joined #openstack-nova06:20
gibigood morning nova06:21
*** hoonetorg has joined #openstack-nova06:22
*** thorst_afk has quit IRC06:25
*** lpetrut has joined #openstack-nova06:26
*** litao__ has joined #openstack-nova06:26
*** jaosorior has joined #openstack-nova06:26
*** suresh12 has quit IRC06:27
*** markvoelker has quit IRC06:31
*** takashin_ has left #openstack-nova06:31
*** ekuris has quit IRC06:37
*** ekuris has joined #openstack-nova06:38
*** zsli_ has joined #openstack-nova06:40
*** Shunli has quit IRC06:43
*** trungnv has joined #openstack-nova06:46
*** rcernin has joined #openstack-nova06:46
openstackgerritMerged openstack/nova master: Fix scope of errors_out_migration in finish_resize  https://review.openstack.org/48751506:46
*** Guest48826 has quit IRC06:48
*** lpetrut has quit IRC06:54
*** Tom has quit IRC07:03
*** Tom has joined #openstack-nova07:03
*** Tom_ has joined #openstack-nova07:05
*** sahid has joined #openstack-nova07:05
*** sahid has quit IRC07:05
*** Tom_ has quit IRC07:06
*** Tom_ has joined #openstack-nova07:06
openstackgerritzhangbailin proposed openstack/nova master: Replace http with https for doc links in nova  https://review.openstack.org/50069307:06
*** Tom has quit IRC07:08
*** zsli_ has quit IRC07:12
*** tesseract has joined #openstack-nova07:13
*** sahid has joined #openstack-nova07:14
*** ygl has joined #openstack-nova07:15
*** zxy has quit IRC07:20
*** zxy has joined #openstack-nova07:21
*** thorst_afk has joined #openstack-nova07:22
*** gcb has quit IRC07:22
*** gcb has joined #openstack-nova07:22
*** trinaths has quit IRC07:24
openstackgerritTetsuro Nakamura proposed openstack/nova master: disable numa feature when virt_type=qemu  https://review.openstack.org/46516007:24
*** andreas_s has joined #openstack-nova07:24
*** thorst_afk has quit IRC07:26
*** slaweq has joined #openstack-nova07:29
*** jpena|off is now known as jpena07:33
*** ralonsoh has joined #openstack-nova07:41
*** moshele has quit IRC07:54
*** rmart04 has joined #openstack-nova07:56
openstackgerritRodolfo Alonso Hernandez proposed openstack/nova master: Add datapath type information to OVS vif objects  https://review.openstack.org/47489207:58
*** moshele has joined #openstack-nova08:03
*** udesale has quit IRC08:03
openstackgerritTetsuro Nakamura proposed openstack/nova master: disable numa feature when virt_type=qemu  https://review.openstack.org/46516008:04
*** slaweq_ has joined #openstack-nova08:04
*** Tom_ has quit IRC08:04
*** Tom_ has joined #openstack-nova08:05
*** udesale has joined #openstack-nova08:05
*** Tom____ has joined #openstack-nova08:06
*** Tom____ has quit IRC08:06
*** Tom____ has joined #openstack-nova08:07
*** slaweq_ has quit IRC08:08
*** Tom_ has quit IRC08:09
*** thorst_afk has joined #openstack-nova08:22
*** priteau has joined #openstack-nova08:24
*** trinaths has joined #openstack-nova08:25
*** thorst_afk has quit IRC08:27
*** udesale has quit IRC08:27
*** udesale has joined #openstack-nova08:27
*** suresh12 has joined #openstack-nova08:28
*** markvoelker has joined #openstack-nova08:28
*** jaosorior has quit IRC08:29
*** alexchadin has joined #openstack-nova08:30
*** lucas-afk is now known as lucasagomes08:32
openstackgerritHironori Shiina proposed openstack/nova master: [WIP] ironic: Support cold migration  https://review.openstack.org/50067708:32
*** suresh12 has quit IRC08:32
*** avolkov has joined #openstack-nova08:33
*** yangyapeng has quit IRC08:34
*** yangyapeng has joined #openstack-nova08:35
openstackgerritRodolfo Alonso Hernandez proposed openstack/os-vif master: Add support for Windows network commands  https://review.openstack.org/48740508:40
*** derekh has joined #openstack-nova08:42
*** ygl has quit IRC08:42
*** dtantsur|afk is now known as dtantsur08:46
*** hshiina has quit IRC08:49
*** Tom____ has quit IRC08:50
*** yangyapeng has quit IRC08:52
*** yangyapeng has joined #openstack-nova08:53
openstackgerritJeremy Liu proposed openstack/nova master: Put base policy rules at first  https://review.openstack.org/50073608:55
*** markvoelker has quit IRC09:01
openstackgerritRodolfo Alonso Hernandez proposed openstack/nova master: Read Neutron port 'binding_profile' during boot  https://review.openstack.org/44925709:05
*** amotoki__away is now known as amotoki09:07
*** gszasz has joined #openstack-nova09:09
*** sambetts|afk is now known as sambetts09:20
*** thorst_afk has joined #openstack-nova09:23
*** thorst_afk has quit IRC09:28
openstackgerritRodolfo Alonso Hernandez proposed openstack/os-vif master: Add ``HostPortProfileInfo`` class  https://review.openstack.org/44159009:31
*** Sree_ has joined #openstack-nova09:32
*** Sree_ is now known as Guest4962409:32
*** jichen has quit IRC09:44
openstackgerritzhangbailin proposed openstack/nova master: Replace http with https for doc links in nova  https://review.openstack.org/50069309:45
*** alexchadin has quit IRC09:46
*** alexchadin has joined #openstack-nova09:47
*** priteau has quit IRC09:51
*** yassine has quit IRC09:55
*** dixiaoli has quit IRC09:56
*** markvoelker has joined #openstack-nova09:58
*** yamamoto has quit IRC10:00
*** nicolasbock has joined #openstack-nova10:05
*** lpetrut has joined #openstack-nova10:05
*** dtantsur is now known as dtantsur|lunch10:06
*** nicolasbock has quit IRC10:09
*** dixiaoli has joined #openstack-nova10:12
*** dixiaoli has quit IRC10:13
*** ratailor has quit IRC10:14
*** yamamoto has joined #openstack-nova10:15
*** ratailor has joined #openstack-nova10:15
*** abhi89 has quit IRC10:20
*** nicolasbock has joined #openstack-nova10:22
*** jaosorior has joined #openstack-nova10:23
*** thorst_afk has joined #openstack-nova10:24
openstackgerritAlexandru Muresan proposed openstack/nova master: Pass config object to oslo_reports  https://review.openstack.org/48557510:25
*** thorst_afk has quit IRC10:28
*** bkopilov has quit IRC10:31
*** markvoelker has quit IRC10:31
*** moshele has quit IRC10:32
*** moshele has joined #openstack-nova10:34
*** yamamoto has quit IRC10:37
*** udesale__ has joined #openstack-nova10:37
stephenfinDo we use reno for bugfixes?10:38
*** udesale has quit IRC10:39
openstackgerritStephen Finucane proposed openstack/nova master: Pass config object to oslo_reports  https://review.openstack.org/48557510:39
*** udesale__ has quit IRC10:40
*** udesale has joined #openstack-nova10:40
openstackgerritPooja Jadhav proposed openstack/nova master: Fix ValueError if invalid max_rows passed to db purge  https://review.openstack.org/50077110:42
*** ratailor has quit IRC10:43
*** yangyapeng has quit IRC10:43
*** Oku_OS is now known as Oku_OS-away10:47
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove deprecated 'null_kernel' opt  https://review.openstack.org/49961110:49
openstackgerritStephen Finucane proposed openstack/nova master: WIP! conf: Remove deprecated 'multi_instance_display_name_template' opt  https://review.openstack.org/49961210:49
*** Oku_OS-away is now known as Oku_OS10:53
*** moshele has quit IRC10:58
*** moshele has joined #openstack-nova10:59
*** yamamoto has joined #openstack-nova11:02
*** moshele has quit IRC11:03
*** lucasagomes is now known as lucas-hungry11:05
*** moshele has joined #openstack-nova11:06
*** moshele has quit IRC11:09
*** ZZelle has joined #openstack-nova11:14
*** sdague has joined #openstack-nova11:19
*** smatzek has joined #openstack-nova11:21
*** yassine has joined #openstack-nova11:24
*** thorst_afk has joined #openstack-nova11:25
*** tbh_ has quit IRC11:25
*** priteau has joined #openstack-nova11:26
openstackgerritRodolfo Alonso Hernandez proposed openstack/os-vif master: Migration from ``ip`` commands to ``pyroute2``  https://review.openstack.org/48438611:28
openstackgerritRodolfo Alonso Hernandez proposed openstack/nova master: Add datapath type information to OVS vif objects  https://review.openstack.org/47489211:29
*** markvoelker has joined #openstack-nova11:29
*** fried_rice is now known as efried11:29
efriedstephenfin If behavior changed?11:30
*** thorst_afk has quit IRC11:33
*** rcernin has quit IRC11:36
*** rcernin has joined #openstack-nova11:36
openstackgerritRodolfo Alonso Hernandez proposed openstack/os-vif master: Add plugin names as constants.  https://review.openstack.org/50011111:38
*** jpena is now known as jpena|lunch11:41
*** alexchadin has quit IRC11:44
*** alexchadin has joined #openstack-nova11:44
*** dikonoor has joined #openstack-nova11:45
*** Guest49624 has quit IRC11:46
*** kiennt_AWAY has quit IRC11:46
*** Sree has joined #openstack-nova11:46
*** Sree has quit IRC11:51
*** moshele has joined #openstack-nova11:52
*** dtantsur|lunch is now known as dtantsur11:57
*** moshele has quit IRC11:58
*** nicolasbock has quit IRC11:58
*** Sree has joined #openstack-nova11:58
*** nicolasbock has joined #openstack-nova12:00
*** thorst_afk has joined #openstack-nova12:00
*** jaypipes has joined #openstack-nova12:00
openstackgerritBalazs Gibizer proposed openstack/nova master: use already loaded BDM in instance.<action> (2)  https://review.openstack.org/48395512:01
openstackgerritBalazs Gibizer proposed openstack/nova master: use already loaded BDM in instance.create  https://review.openstack.org/48396912:01
openstackgerritBalazs Gibizer proposed openstack/nova master: use already loaded BDM in instance.<action>  https://review.openstack.org/48332412:01
*** markvoelker has quit IRC12:01
*** dave-mccowan has joined #openstack-nova12:05
*** abhi89 has joined #openstack-nova12:06
*** moshele has joined #openstack-nova12:07
*** TuanLA has quit IRC12:09
*** litao__ has quit IRC12:13
*** markvoelker has joined #openstack-nova12:16
*** lucas-hungry is now known as lucasagomes12:18
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements  https://review.openstack.org/50001112:19
openstackgerritBalazs Gibizer proposed openstack/nova master: Factor out duplicated notification sample data (3)  https://review.openstack.org/45282012:21
openstackgerritBalazs Gibizer proposed openstack/nova master: Factor out duplicated notification sample data  https://review.openstack.org/45281812:21
openstackgerritBalazs Gibizer proposed openstack/nova master: Factor out duplicated notification sample data (2)  https://review.openstack.org/45281912:21
openstackgerritBalazs Gibizer proposed openstack/nova master: Refactor instance.power-off notification samples  https://review.openstack.org/47586012:21
bhagyashrisjaypipes: Hi, Is there any placement api to get resource provider for a given instance uuid?12:21
*** edmondsw has joined #openstack-nova12:21
*** zhurong has quit IRC12:22
bhagyashrisjaypipes: if there is no direct api, is it possible to get resource provider if I know the instance uuid12:22
*** udesale has quit IRC12:25
*** shan7 has joined #openstack-nova12:25
*** edmondsw has quit IRC12:26
*** shan has quit IRC12:26
*** shan has joined #openstack-nova12:27
*** edmondsw has joined #openstack-nova12:27
*** shan has quit IRC12:28
*** yangyapeng has joined #openstack-nova12:28
*** shan has joined #openstack-nova12:28
*** shan has quit IRC12:29
*** shan7 has quit IRC12:30
*** Sree has quit IRC12:31
*** edmondsw has quit IRC12:31
*** hferenc has joined #openstack-nova12:32
openstackgerritBalazs Gibizer proposed openstack/nova master: Send soft_delete from context manager  https://review.openstack.org/47645912:37
openstackgerritBalazs Gibizer proposed openstack/nova master: use context mgr in instance.delete  https://review.openstack.org/44376412:37
openstackgerritBalazs Gibizer proposed openstack/nova master: Transform missing delete notifications  https://review.openstack.org/41029712:37
*** jaosorior has quit IRC12:41
*** eharney has quit IRC12:45
stephenfinefried: What do you think of this one, in that case? https://review.openstack.org/#/c/465160/ Looks like a change in behavior12:46
efriedstephenfin ...12:46
*** shan has joined #openstack-nova12:47
efriedstephenfin Well, I definitely don't claim understanding of the plumbing here, but if I'm reading it right, it's making an ugly/unpredictable error into a crisp, predictable one.12:49
*** scottda_ has joined #openstack-nova12:49
efried...which IMO would not warrant a reno.12:49
efriedIf it is in fact explicitly removing support for something which used-to-sort-of-work-maybe-sometimes and now definitely won't work ever for anyone, then *maybe* it warrants a reno.  RBB kind of thing.12:50
stephenfinefried: Yup, agree with all of the above. I'll drop the -1 for that and let him address sahid's comments12:51
stephenfinefried: Thanks for the input :)12:51
*** lyan has joined #openstack-nova12:51
efriedstephenfin Sure thing, for whatever it's worth :)12:51
*** mgariepy has quit IRC12:53
efriedsean-k-mooney Can I just say I think it's neat how you start each line of a paragraph with a capital.  It's like poetry.12:54
*** baoli has joined #openstack-nova12:54
*** baoli has quit IRC12:54
*** mgariepy has joined #openstack-nova12:54
*** catintheroof has joined #openstack-nova12:55
*** catintheroof has quit IRC12:55
*** catintheroof has joined #openstack-nova12:55
efriedOne question: you said, "...in this case the bandwidth resource provider will be a child of the PF"  -- not to split hairs, but wouldn't the bandwidth resource provider be the PF itself?  That is, the PF needs to provide the pool of VFs *and* the pool of bandwidth... units.12:55
*** pchavva has joined #openstack-nova12:56
*** zhurong has joined #openstack-nova12:56
*** jpena|lunch is now known as jpena12:57
*** esberglu has joined #openstack-nova12:57
*** kylek3h has joined #openstack-nova12:58
*** edmondsw has joined #openstack-nova12:58
*** gszasz has quit IRC12:59
*** baoli has joined #openstack-nova13:00
*** gszasz has joined #openstack-nova13:02
*** mriedem has joined #openstack-nova13:06
*** shaohe_feng has quit IRC13:06
*** bkopilov has joined #openstack-nova13:07
efriedmriedem Was going to move the pike powervm bp from approved/ to implemented/, but noticed there seems to be a script that does that for everything.  Which made me assume someone else (like you) would be doing that at some designated point in the release cycle.  True?13:09
*** zhurong has quit IRC13:10
kashyapmriedem: When you're about, do you have any further remarks on this - https://review.openstack.org/#/c/498983/13:10
jaypipesbhagyashris: GET /allocations/{instance_uuid}13:11
jaypipesbhagyashris: no, that's not right... never mind.13:12
bhagyashrisjaypipes: ok.13:12
efriedjaypipes bhagyashris Not sure what that means, "resource provider for an instance"?13:13
mriedemgmann: i'm missing something here https://review.openstack.org/#/c/500369/213:13
mriedemefried: see ^13:13
jaypipesefried: he means get the resource providers that an instance is consuming from.13:13
efriedah, that makes sense.13:13
*** shaohe_feng has joined #openstack-nova13:14
*** alexchadin has quit IRC13:14
*** gouthamr has joined #openstack-nova13:14
efriedmriedem Roger that, thanks.13:14
*** shan has quit IRC13:14
bhagyashrisefried, jaypipes: I have tried to search but haven't found any api or anyway I guess we can not get the resource provider if we know the instance uuid13:14
jaypipesbhagyashris: no, I was correct the first time... GET /allocations/{instance_uuid}13:15
bhagyashrisjaypipes: ok let me check.13:15
jaypipesbhagyashris: https://github.com/openstack/nova/blob/master/nova/api/openstack/placement/handlers/allocation.py#L111-L12813:16
jaypipesbhagyashris: that's what the response will look like.13:16
jaypipesbhagyashris: you can get the resource provider UUIDs by grabbing response.get('allocations').keys()13:16
bhagyashrisjaypipes: yes13:16
bhagyashrisjaypipes: {"allocations": {"0cda7039-eee9-4ea4-90c5-78308b1990e9": {"generation": 1004, "resources": {"VCPU": 1, "MEMORY_MB": 512, "DISK_GB": 1}}}}13:17
bhagyashrisjaypipes: like this got it.13:17
jaypipesbhagyashris: also, see here: https://developer.openstack.org/api-ref/placement/13:18
jaypipeshttps://developer.openstack.org/api-ref/placement/#list-allocations13:18
*** phuongnh has quit IRC13:18
openstackgerritYongMing Zeng proposed openstack/nova master: optimized code  https://review.openstack.org/50082013:19
bhagyashrisjaypipes: thanks, I have two doubt can you please guide me13:20
bhagyashrisjaypipes: is it  possible to assign resources from different resources providers for a given instance?13:20
jaypipesbhagyashris: yes.13:21
jaypipesbhagyashris: see above link for an example.13:21
bhagyashrisjaypipes: As per my finding if i used the custom resource classes to create the inventory using the resource provider then it's possible but if i used the existing resource classes then it's not possible13:22
bhagyashrisjaypipes: am i correct?13:22
bhagyashrisjaypipes: ohh ok.13:22
jaypipesbhagyashris: custom vs. standard resource classes don't matter when creating inventory against multiple providers.13:25
*** lpetrut_ has joined #openstack-nova13:27
bhagyashrisjaypipes: ok.13:27
bhagyashrisjaypipes: how a aggregate is selected in placement service?13:28
jaypipesbhagyashris: just remember that when you call PUT /resource_providers/{rp_uuid}/inventory, that you are *replacing* the inventory of the resource provider each time you call that.13:28
jaypipesbhagyashris: aggregates are not selected. only resource providers are selected. aggregates allow relationships between resource providers, for example, to denote a grouping of like providers.13:29
bhagyashrisjaypipes: for example, I have host-aggregate-1 and host-aggregate-2, and when a new request comes to boot an instance, then how the placement api decides in which host aggregate this new vm should be created13:29
*** burt has joined #openstack-nova13:29
bhagyashrisjaypipes: ok.13:29
*** lpetrut has quit IRC13:29
jaypipesbhagyashris: that's not how things work :) instances don't get created "in an aggregate". Instead, instances get created on a compute host. That compute host may be associated with one or more aggregates.13:30
jaypipesbhagyashris: perhaps you're confusing availability zone with host aggregate?13:30
bhagyashrisjaypipes: yes.13:31
*** shaohe_feng has quit IRC13:33
jaypipesbhagyashris: availability zone is an attribute (metadata key/value pair) against a Nova host aggregate. All compute hosts in the host aggregate belong to the availability zone that the host aggregate is marked with. That said, the placement API does not have anything to do with the availability zone. The Nova host aggregate and the placement aggregate are different things. For example, a Nova host aggregate actually refers to the nova-compute13:33
jaypipesservice daemon, not the provider of resources. This is why, for example, Ironic baremetal nodes cannot individually be assigned to a Nova host aggregate. But Ironic baremetal nodes *can* be associated individually with a placement aggregate.13:33
*** shaohe_feng has joined #openstack-nova13:33
jaypipesbhagyashris: it's all ludicrously confusing, I know :(13:34
jaypipesbhagyashris: perhaps you could describe what you're attempting to do so I can assist you in finding the answers you seek :)13:35
*** crushil has quit IRC13:37
*** eharney has joined #openstack-nova13:37
*** artom_ has quit IRC13:41
bhagyashrisjaypipes: actually my doubt was regarding the selection host aggregate in placement when i request to boot instance but host aggregates are not selected to create the instance at placement that is only used for the relationships between the providers13:43
*** mriedem has quit IRC13:43
*** baoli_ has joined #openstack-nova13:43
*** mriedem has joined #openstack-nova13:44
*** gbarros has joined #openstack-nova13:44
efriedjaypipes I also would like to understand what an aggregate is (in placement context).  Is this the best thing to read? https://developer.openstack.org/api-ref/placement/#resource-provider-aggregates13:44
efried(though ^ seems to assume a foreknowledge of what a "host aggregate" is... which I lack013:44
efried)13:44
mriedemhttps://docs.openstack.org/nova/latest/user/aggregates.html13:45
mriedemfor host aggregates13:45
*** jaosorior has joined #openstack-nova13:45
*** baoli has quit IRC13:46
efriedThanks13:46
*** crushil has joined #openstack-nova13:47
jaypipesefried: placement aggregates are groupings of resource providers, nothing more. Placement aggregates do not have traits associated with them. Placement aggregates are not "in an availability zone" or anything like that. Nova host aggregates are groupings of nova-compute service daemons (NOT the compute hosts that actually provide the resources). Nova host aggregates have metadata key/value pairs associated with them. Nova host aggregates are13:49
jaypipesan entity in any of themselves, whereas placement aggregates are nothing more than a UUID that provides a grouping to resource providers.13:49
jaypipesbhagyashris: ^ you too. :)13:49
*** marst has joined #openstack-nova13:50
efriedjaypipes What are placement aggregates useful/used for?13:50
jaypipesefried: associating a resource provider to another.13:50
jaypipesefried: that's it. nothing more.13:50
efriedAssociating for programmatic or human consumption?13:50
jaypipesefried: right now, mostly programmatic.13:51
jaypipesefried: it's currently how we handle shared resources.13:51
efriedSo placement aggregates can overlap.13:51
efriedI seem to recall asking this very question in Boston :)13:52
efriedAnd the answer was yes13:52
stephenfinmriedem: Could you take another look at this this week? https://review.openstack.org/#/c/412356/13:52
edleafeefried: placement can't select based on nova host agg13:52
jaypipesefried: in the future, I envision aggregates being associated to each other via a distance attribute. In other words, agg A and agg B are distance 1 apart. agg X and agg A are distance 4 apart, etc.13:52
edleafeefried: that's done in the scheduler filters13:52
jaypipesefried: this will provide us a way to model affinity and anti-affinity concerns in placement.13:52
jaypipesefried: yep, aggregates (either placement or Nova host aggregate) can overlap.13:53
efriedjaypipes So it also makes sense that a nested resource provider will be implicitly aggregated with its parent.13:53
*** tidwellr has joined #openstack-nova13:54
efried...and by extension, with its "siblings" and "cousins"...13:54
jaypipesefried: yes. I was planning on making a constraint that only root provider UUIDs could be associated with an aggregate.13:55
*** zxy has quit IRC13:55
*** zxy has joined #openstack-nova13:55
mriedemstephenfin: replied13:56
stephenfinta13:57
mriedemstephenfin: if we're going to play fast and loose we should at least have a release note13:57
*** ijw has joined #openstack-nova13:57
bhagyashrisjaypipes: Thanks for your inputs :)13:58
stephenfinmriedem: 'upgrade' section?13:59
mriedemstephenfin: yeah i suppose13:59
sean-k-mooneyefried: hehe that is more my email client enforcing it then i doing it intentionally but thanks in any case.14:03
*** erlon has quit IRC14:03
*** kbaegis has quit IRC14:03
*** suresh12 has joined #openstack-nova14:03
openstackgerritStephen Finucane proposed openstack/nova master: rbd: Remove unnecessary 'encode' calls  https://review.openstack.org/41235614:04
*** kbaegis has joined #openstack-nova14:04
stephenfinsean-k-mooney: I'd suggest using something like Evolution but don't - it's buggy af :(14:04
sean-k-mooneystephenfin: currently im still using outlook because im too lazy to figure out how to get tunderbird to work with our exchange servers. but since you helped me to get inline respconces to text only mail working i think it does the job well enough14:06
stephenfinmriedem: Done. The important bit is that this will only affect users running under Python 314:06
stephenfinsean-k-mooney: Heh, I actually blogged that when I left Intel https://that.guru/blog/sane-outlook/14:07
stephenfinone of my very few posts. I should probably use that more14:07
sean-k-mooneyoh cool i should send that to sdake14:08
sean-k-mooneysdake: you were asking how i got outlook to work with inline plain text before. stephens blog should help https://that.guru/blog/sane-outlook/14:09
*** hongbin has joined #openstack-nova14:09
*** gszasz has quit IRC14:10
sean-k-mooneystephenfin: speanking of blogs in need to set min up again ...14:10
bauzasmriedem: could you please tell me again which series to review ? I now have a new laptop and I don't find it14:10
sdakesean-k-mooney the problem is the line doesn't break in replies14:10
sdakesean-k-mooney therefore one cnnot reply inline14:10
bauzasmriedem: I mean, the bug series about the problems with allocations14:11
sdakestephenfin does your solution fix thta?14:11
sdakesean-k-mooney everyting I've read says its an outlook bug and microsoft doesn't care14:11
stephenfinsdake: Afraid not, I'd to guess what 80 characters looked like14:11
sdakeit has to dowith the way word is integrated into outlook14:11
mriedembauzas: starts here https://review.openstack.org/#/c/499678/314:11
*** hferenc has quit IRC14:11
bauzasmriedem: ta14:12
bauzasCC'ing14:12
stephenfinMS don't care for plain text. If you use outlook.com and try to switch to plain text, you suddenly can't paste links14:12
mriedembauzas: and https://review.openstack.org/#/c/498861/14:12
sdakestephenfin there is a bar on the left side of replies, - it has nothign to do with 80 chars however the bar can't be broken - if there are 4 layers of replies, there is no way to "put a new reply" in14:12
stephenfinIt formats them as HTML14:12
bauzasmriedem: will reviewing them in the next hour14:12
bauzasthanks14:12
sean-k-mooneysdake: this is what it looks like when i reply http://lists.openstack.org/pipermail/openstack-dev/2017-September/121804.html14:12
stephenfinsdake: Ah, I remember that, though not what I did to resolve it14:13
sdakei am on outlook 201614:13
sdake2016 is where is broke - it worked on 2013 and prior14:13
openstackgerritRodolfo Alonso Hernandez proposed openstack/os-vif master: Add VersionedObjectPrintable mixin  https://review.openstack.org/49308214:13
bauzasFWIW, I now have again an Entry button \o/14:13
sdakeit even worked briefly for 201614:14
*** cfriesen__ has joined #openstack-nova14:14
sdakesean-k-mooney are ou using 2016 outlook?14:14
stephenfinsdake: Maybe it's a feature, heh14:14
sean-k-mooneysdake: no still on 2013 i am afraid14:14
stephenfinFor what it's worth, I ended up using Mutt for everything except openstack-dev in the end (ovs-dev, patchwork, dpdk-dev etc.)14:14
sdakesean-k-mooney if you want a sane mail client don't upgrade14:14
sdakei just use gmail for mailing lists - since i can actually reply14:14
openstackgerritRodolfo Alonso Hernandez proposed openstack/os-vif master: Migration from ``ip`` commands to ``pyroute2``  https://review.openstack.org/48438614:15
sean-k-mooneysdake: if i do an os reinstall or upgrade ill just setup tunderbird. but since outlook is not currently broken im not going to change it14:15
*** suresh12 has quit IRC14:15
stephenfinExchange is still an excellent protocol (at least from a usability perspective), but the lack of things like auto-wrap in Outlook makes it tough to work with14:15
stephenfinsean-k-mooney: Good luck. That is also terrible, IMO14:15
sean-k-mooneystephenfin: well i have been usingin it since i created my first email account at home so im used to it. it works for me.14:17
*** suresh12 has joined #openstack-nova14:17
stephenfinsean-k-mooney: Ah, then you're not too badly off. I thought it was ugly as sin and calendering with Gmail was seriously broken. Evolution would be excellent if it just weren't so damn buggy :(14:18
sean-k-mooneyim currently in a "its not broke so im not going to fix it" mode with my apps and workflow. eventully ill upgrading things when i have too.14:20
*** andreas_s has quit IRC14:20
sean-k-mooneyits kindo fo like openstack. our dev cloud has been running on newton rc1 for almost a year. it is now finally beging to have issue so im going to go strait to stable pike once kolla-ansible make its release but while it was working no need to upgrade it14:22
*** rabel has joined #openstack-nova14:22
*** gszasz has joined #openstack-nova14:23
*** dikonoor has quit IRC14:23
*** yamamoto has quit IRC14:24
*** ratailor has joined #openstack-nova14:24
openstackgerritMatt Riedemann proposed openstack/nova master: Moving more utils to ServerResourceAllocationTestBase  https://review.openstack.org/49953914:24
openstackgerritMatt Riedemann proposed openstack/nova master: Test resource allocation during soft delete  https://review.openstack.org/49515914:24
openstackgerritMatt Riedemann proposed openstack/nova master: Refactor ServerMovingTests for non-move tests  https://review.openstack.org/49859614:24
*** ratailor has quit IRC14:24
*** beekneemech is now known as bnemec14:25
*** ratailor has joined #openstack-nova14:25
*** yamamoto has joined #openstack-nova14:25
*** hferenc has joined #openstack-nova14:25
*** suresh12 has quit IRC14:26
*** eharney_ has joined #openstack-nova14:26
*** eharney has quit IRC14:27
*** ratailor has quit IRC14:28
*** suresh12 has joined #openstack-nova14:28
*** ebbex has joined #openstack-nova14:31
*** vikrant has joined #openstack-nova14:32
sdakestephenfin i used thunderbird for 10 years - your correct it is awful :)14:33
sdakeif i relaly feel like osme pain I use mac mail for responding to mailing lists and outlook for reading14:34
sdakewish i could find a mail client that worked with exchange that was good14:34
sdakethere is this rockin mac client, however, it lacks exchange support......14:34
sdakein other words, its useless :)14:34
*** yamamoto has quit IRC14:35
openstackgerritMatt Riedemann proposed openstack/nova master: Remove compatibility code for flavors  https://review.openstack.org/46037714:36
*** kristian__ has joined #openstack-nova14:36
sean-k-mooneystephenfin: by the way, you mentioned before that we can associate multiple email accounts with a singel openstack account correct? do you have a link to how to do this. if not ill just google it14:37
*** links has quit IRC14:37
stephenfinsean-k-mooney: Sure. Sec14:38
stephenfinsean-k-mooney: So I _think_ you do it from Launchpad. Go to https://launchpad.net/ and click your user in the top right14:38
stephenfinThat'll bring you to your profile. Emails are listed on the left. IIRC, this gets propagated to Gerrit14:40
*** eharney_ is now known as eharney14:41
dansmithhope you guys don't mind me interrupting the email chat to talk about nova...14:41
dansmithmriedem: so the people working on skip level upgrades pointed out that our ironic flavor migration thing will be a problem for them,14:42
sean-k-mooneyok ill give that a try and if it doesnt work ill ask the infra guys next week.14:42
dansmithwhich is correct, and a little contrary to the promises we've been making about being able to do offline upgrades with nova-manage14:42
sean-k-mooneydansmith: sorry :)14:42
dansmithso I'm trying to think about the best way to make that doable without compute running14:42
dansmithsean-k-mooney:  :)14:42
*** moshele has quit IRC14:42
dansmithmriedem: I'm thinking that the best plan would just be a dedicated subcommand for this specific case since it's kinda weird14:43
mriedemdansmith: well, we can do some purely db intensive stuff in nova-manage14:43
*** hrw has quit IRC14:43
dansmithmriedem: yeah, but we need to know which instances are ironic and not, so I'm kinda thinking that maybe we should make a dedicated command that takes an ironic compute's hostname and migrates instances that are on that compute14:44
dansmithwhich makes it not really fit the online-data-migrations model14:44
*** udesale has joined #openstack-nova14:44
dtantsurmriedem: hey! when do you folks plan on finalizing your PTG schedule? I specifically wonder about the scheduling discussion, as we have a couple of topics there14:44
mriedemwe can figure out the ironic nodes via the hypervisor_type on the compute_nodes table right?14:44
mriedemdtantsur: it's something i need to work on this week14:44
dansmithmriedem: we can yeah14:44
mriedemit's pretty open ended atm, except for thursday morning being cinder time14:44
dtantsurmriedem: we have a few topics depending on the scheduling discussion outcome to an extent. so I guess Wed would work better, probably afternoon.14:45
*** suresh12 has quit IRC14:46
dtantsurbut it's up to you of course :)14:46
dtantsurvdrok: ^^14:46
dansmithmriedem: so your preference would be to do it fully automatic like that? we kinda need to backport this if we're going to remove the migration from queens14:46
mriedemdansmith: so the problem with the offline data migrations command with this is we don't really have a marker i don't think14:46
dtantsuror just don't remove the migration from queens...14:46
mriedemsince the extra specs are a json blob14:46
mriedembut i haven't thought it through fully14:46
dansmithmriedem: yup, hence my thinking that a one-shot command for a host would be good14:46
dansmithdtantsur: yeah, but we really want to stop allowing the old model too, which we *could* do separate from the migration piece, but...14:47
mriedemfor all compute nodes where hypervisor_type == 'ironic'; find all instances where host/node in that list; do migrate instance extra spec14:47
dansmiththe migration piece in compute also brings overhead14:47
mriedemdansmith: i wouldn't want to require a host, but it could be an option14:47
*** udesale has quit IRC14:47
*** jheroux has joined #openstack-nova14:47
*** udesale has joined #openstack-nova14:48
dansmithmriedem: well, for a dedicated command I was thinking make it specifically "run for instances on this host" so you're responsible for iterating hosts and therefore not running twice14:48
*** hrw has joined #openstack-nova14:49
*** udesale has quit IRC14:49
*** coreywright has quit IRC14:50
mriedemhow do you know you've hit all hosts?14:50
mriedemand then someone will say, how do i get the list of hosts14:50
dansmithwell, I'm thinking about tripleo where that's easy to determine14:51
mriedemrunning twice isn't a problem either right? it's just a no-op if already migrated14:51
dansmithsure, it's just super expensive14:51
mriedemi'm generally never thinking about tripleo14:51
mriedem:)14:51
dansmithheh14:51
dtantsur:D14:51
mriedemmy preference would be, host is optional, so if someone thinks they know better and want to iterate hosts client side, fine14:51
mriedemotherwise we do it14:51
dansmithhow about we make it expected, else there's an --all option,14:52
dansmithso it's clear that it's not just idempotent and zero impact?14:52
dansmithand to be clear, this is a dedicated command with specific behaviors, yes?14:52
mriedemit is idempotent except for the db read hit right?14:52
dansmithright, idempotent is the wrong word, because it is, I meant "resumable" or "zero impact if nothing to do"14:53
dansmithlike, don't just run this on every puppet run14:53
mriedemhow is tripleo going to determine that it's done all of the migrations?14:53
mriedemand can stop14:53
dansmithtripleo won't,14:54
dtantsurso, are you going to call into ironic in this command?14:54
mriedemdtantsur: no14:54
dtantsursorry, I don't quite understand how you're going to know the resource class of the node14:54
mriedemdtantsur: this is just duplicating what we do in nova-compute startup14:54
dansmithit'll be a specific skip-level upgrades script14:54
dtantsurwell, in nova compute we're using data from ironic14:54
dansmithdtantsur: yeah, we'll have to take a RC as well14:54
dansmithit's going to be super offline14:54
dtantsurI know, hence my concern :)14:54
dansmithyup14:54
dtantsurone mistake - and the cloud is in a very strange state14:55
dansmithbut that's the risk of skip level upgrades,14:55
dansmithyou're taking the complexity of skipping into your own hands14:55
dansmithit's a tradeoff of complexity and downtime for infrequent upgrades14:55
dtantsurokie, but how is the command invokation going to look?14:55
dansmiththat's been a core part of my messaging on the topic at least :)14:55
dansmithnova-manage db migrate-ironic-things --resource_class 'undercloud' --do-all-make-my-db-hurt14:56
dtantsur$ nova-migrate-to-pike <host> --node <uuid>=<class> --node <uuid2>=<class2>14:56
dtantsur?14:56
dtantsurdansmith: wait, tripleo uses one resource class, but that does not mean everyone does14:56
jaypipesdansmith: would you be able to attend this session in Denver? https://etherpad.openstack.org/p/queens-PTG-skip-level-upgrades14:56
dansmithor if you have different ones, then:14:56
dansmithnova-manage db migrate-ironic-things --resource_class 'undercloud' --host foo114:56
dansmithdtantsur: sure, that means you have to do your hosts one at a time with a rc then14:57
dtantsurdansmith: host == ironic node, not nova-compute process, right?14:57
dansmithjaypipes: um yes? been working on this with lyarwood :)14:57
dtantsur(sorry, I always confuse the terms)14:57
dansmithdtantsur: ah, well, that's a fair point14:57
dansmithdtantsur: I was meaning compute, but yeah --node is probably the better option14:57
rabelmriedem: i answered to your questions on https://review.openstack.org/#/c/494169/ . could you have a look at it again?14:58
vdrokdtantsur: yeah everything except friday works for me14:59
openstackgerritMatt Riedemann proposed openstack/nova master: Mark LXC as missing for swap volume support  https://review.openstack.org/48221614:59
*** josecastroleon has quit IRC15:01
dansmithdtantsur: mriedem: anyway, let me cook something up along these lines and ya'll can rip on it15:01
dtantsuryes please :)15:01
mriedemwe do have this compute_nodes.mapped column now15:01
mriedemwonder if we could use that for dumb paging15:01
dansmithmriedem: not really a good idea, I don't think15:02
dansmithmriedem: we'd have to bump that for all the non-ironic computes too if we did15:02
mriedemtrue15:02
mriedemthis is probably going to have to use all sqla orm code,15:03
dansmithand15:03
mriedemsince we don't have some query methods you'd need on the objects15:03
mriedemunless you just did ComputeNodeList.get_all and filter in python15:03
dansmithmaybe yeah15:03
dansmithjust some non-remotable object queries to make it clean is fine I think15:03
dansmithno rpc impact there15:03
*** coreywright has joined #openstack-nova15:04
*** abhi89 has quit IRC15:04
*** abhi89 has joined #openstack-nova15:04
*** artom_ has joined #openstack-nova15:04
mriedemtaking a uuid would be nice, but you don't get the uuid out of the rest api until you're at pike15:04
mriedemso that's out of the question probably15:04
openstackgerritIldiko Vancsa proposed openstack/nova master: Add attachment_complete call to volume/cinder.py  https://review.openstack.org/49332315:05
openstackgerritIldiko Vancsa proposed openstack/nova master: Tweak connection_info translation for the new Cinder attach/detach API  https://review.openstack.org/49332415:05
openstackgerritIldiko Vancsa proposed openstack/nova master: Implement new attach Cinder flow  https://review.openstack.org/33028515:05
*** Oku_OS is now known as Oku_OS-away15:07
*** vikrant has quit IRC15:07
*** felipemonteiro has joined #openstack-nova15:07
*** felipemonteiro_ has joined #openstack-nova15:09
melwittabhi89: the cell with uuid of all zeros is "cell0" which contains only instances that failed to be scheduled. it's not associated with any compute host. see doc https://docs.openstack.org/nova/latest/user/cellsv2_layout.html15:11
*** rmart04 has quit IRC15:11
*** felipemonteiro has quit IRC15:13
*** lucasxu has joined #openstack-nova15:17
*** kristian__ has quit IRC15:17
*** kristian__ has joined #openstack-nova15:18
*** kristia__ has joined #openstack-nova15:19
*** kristian__ has quit IRC15:19
*** kristia__ has quit IRC15:20
*** kristian__ has joined #openstack-nova15:20
*** kristian__ has quit IRC15:22
*** kristian__ has joined #openstack-nova15:23
*** suresh12 has joined #openstack-nova15:23
*** gmann has quit IRC15:24
*** annegentle has joined #openstack-nova15:24
*** gmann has joined #openstack-nova15:24
*** lbragstad has joined #openstack-nova15:25
*** hferenc has quit IRC15:26
*** kristian__ has quit IRC15:27
*** cleong has joined #openstack-nova15:28
efriedavolkov yt?15:29
*** gyee has joined #openstack-nova15:32
*** tidwellr has quit IRC15:33
*** vikrant has joined #openstack-nova15:33
*** b4rti has quit IRC15:33
openstackgerritMatt Riedemann proposed openstack/nova master: Add some inline code docs tracing the cold migrate flow  https://review.openstack.org/49686115:34
*** tidwellr has joined #openstack-nova15:34
*** yamamoto has joined #openstack-nova15:35
*** kristian__ has joined #openstack-nova15:36
avolkovefried: hi15:37
*** baoli_ has quit IRC15:37
efriedavolkov Was just about to respond to your ML post about HA/anti-affinity of SR-IOV VFs...15:37
*** baoli has joined #openstack-nova15:38
efriedavolkov I think we can do a bit better even within the bounds of the existing placement API (assuming we get nested RPs).15:38
efried...by chunking the PFs into HA groups.15:39
efriedSo I don't think you need the ports labeled P1, P2, P3, P4.  I think you can label them G1 and G2, spread across your switches.15:39
avolkovefried: some meta group based on those properties? sounds good15:40
efriedThis gets a little weird in flavor land, though, cause you'd need a separate flavor for each group I think.15:40
efriedSo you would have one flavor that says "give me two VFs: one from Switch 1 + Group 1; one from Switch 2 + Group 1"15:41
efriedThen another that says "give me two VFs: one from Switch 1 + Group 2; one from Switch 2 + Group 2"15:41
*** kristia__ has joined #openstack-nova15:41
efried...and somehow alternate which one you use to do spawns, so you get saturation of the different ports.15:41
*** ssmith has joined #openstack-nova15:41
efriedUsing P1/P2/P3/P4 you have that same problem, only twice as bad :)15:42
avolkovefried: yeah :), it's another question I wanted to ask15:42
mriedemjohnthetubaguy: here you go https://bugs.launchpad.net/nova/+bug/171518215:42
openstackLaunchpad bug 1715182 in OpenStack Compute (nova) "_rollback_live_migration does not remove allocations from destination node" [High,Triaged]15:42
edmondswefried what does the group signify that knowing the switch doesn't tell you?15:42
*** yamamoto has quit IRC15:43
edmondswi.e., isn't the switch tag essentially a group tag?15:43
efriedno15:43
edmondswoh, I guess you could have the switches wired differently15:43
efried(sorry, got an interrupt, gimme a few mins...)15:44
*** kristian__ has quit IRC15:45
*** lucasagomes is now known as lucas-afk15:46
efriedokay, so avolkov that's a point: how many VFs do you want?15:47
edmondswI guess what I'm getting at is that you shouldn't need to know switch or port... just groups15:48
efriedavolkov If you want four, then yeah, you only need one flavor.15:48
openstackgerritMerged openstack/os-vif master: Add plugin names as constants.  https://review.openstack.org/50011115:48
efried"give me four VFs: Switch1 x Group1; Switch1 x Group2; Switch2 x Group1; Switch2 x Group2"15:49
*** kristian__ has joined #openstack-nova15:49
mriedemdtantsur: i've started a rough agenda at the bottom of this etherpad https://etherpad.openstack.org/p/nova-ptg-queens15:49
mriedempenciled in ironic for 3pm on wed15:49
edmondswefried why wouldn't that be (give me 2 from group 1 and 2 from group 2)?15:50
dtantsurcool, lemme check our schedule15:50
efriededmondsw Because then you might get both from the same switch in group 115:50
*** kbaegis has quit IRC15:50
edmondswefried not if they defined the groups properly...15:51
dtantsurmriedem: do you remember when we have lunch?15:51
mriedemsdague: lyarwood: stable/pike backport for a novaclient thing regressed since 9.0.0 https://review.openstack.org/#/c/495901/15:51
dtantsuris it right after or...?15:51
mriedemdtantsur: i was told 12-115:51
dtantsurthnx15:51
efriededmondsw How can you define two groups to ensure you get four separate ports across two separate switches?15:51
mriedem3pm wednesday would be *after* lunch :)15:51
edmondswgroup 1 = one port to sw1 and one to sw2, group 2 = one port to sw1 and one to sw2, then ask for 2 ports in each group15:52
*** artom_ is now known as artom15:53
*** kristia__ has quit IRC15:53
*** kristian__ has quit IRC15:53
efriededmondsw But placement doesn't know enough to not give you both VFs from group 1 on the same switch.15:53
*** kairo has joined #openstack-nova15:53
edmondswefried there aren't 2 ports in group 1 with the same switch15:54
efriedYes, there are multiple VFs on each pport.15:54
edmondswoh, VFs...15:54
edmondswI gotcha now15:55
efriedAnd yes, you could conceivably do this same thing with four groups - but enumerating switches might make more sense to the user; and you also want the model to extend to >2 switches, >2 ports per switch.15:55
*** psachin has quit IRC15:55
dtantsurmriedem: okay, sounds good15:55
efriedalthough... avolkov that might actually make more sense.  If you always know you want four VFs, you could just tag your PFs in groups so they'll always be spread out.15:56
edmondswefried how about group 1 = 2 ports to sw1 and group 2 = 2 ports to sw2?15:56
efriededmondsw Then again you'll ask for two VFs from group 1 and they might wind up coming from the same pport15:56
edmondswyep, k... better for PFs but doesn't help with VFs15:57
efriedeh?15:57
edmondswnm... it doesn't work, so it doesn't work :)15:57
edmondswI'm not following why you wouldn't tag them with the port, then15:58
efriedavolkov In your email example, it's no different than having labeled P1,P2,P3,P4 - but extending to more than four pports (or reducing the problem set to fewer than 4 desired VFs) it makes more sense to think of groups - where the total number of groups is the number of VFs you're going to want from a single allocation request.15:58
efriededmondsw ^^15:58
avolkovefried: groups are okay if you have the same requirements for each boot request16:00
avolkovefried: with original properties you can ask distinct ports for one boot request and distict switches for another16:01
efriedavolkov Yeah, I get it.  If they're different, then it makes more sense for each PF to have its own label, and you do your HA/anti-affinity by constructing your flavors appropriately.16:01
efriedProblem with that, though, is if you don't have exactly the same number and configuration of SR-IOV cards on all your hosts.16:02
edmondswwill it be possible to request ports on separate identical cards (HA if a card fails)?16:02
efriedSo it probably makes more sense to *call* them groups anyway, even if they usually/always map to PFs :)16:03
sean-k-mooneyefried: i would prefer if we did not model this in flavor or image properties though16:03
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Add functional recreate test for live migration pre-check fails  https://review.openstack.org/50090716:03
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Cleanup allocations on invalid dest node during live migration  https://review.openstack.org/50090816:03
efriedsean-k-mooney Which "this"?16:03
sean-k-mooneyefried: really we should try to model the bond requiremetn as an atribute of the neutron port16:03
sean-k-mooneyvf selection policy16:03
avolkovsean-k-mooney: +1 not to use flavors )16:04
efriedYeah, that makes sense, sorry.16:04
*** hamzy has quit IRC16:04
openstackgerritmelanie witt proposed openstack/nova master: Request zero root disk for boot-from-volume instances  https://review.openstack.org/42848116:04
openstackgerritmelanie witt proposed openstack/nova master: Claim and report zero root disk for boot-from-volume instances  https://review.openstack.org/42850516:04
efriedbut wait16:05
*** marst has quit IRC16:05
efriedwouldn't we like to be able to do a spawn with SR-IOV VFs in one command rather than two?16:05
sean-k-mooneyefried: did you see the section i added to the ptg etherpad https://etherpad.openstack.org/p/nova-ptg-queens lines 107-12516:05
sean-k-mooneyefried: no16:05
*** marst has joined #openstack-nova16:05
sean-k-mooneyefried: and yes but not via flavor16:06
efriedIs a port bound to a host?16:06
sean-k-mooneyif we can do it with one command via nova-boot sure but i dont whant to create a flavor multiple time with just different number of interfaes16:06
*** sahid has quit IRC16:06
sean-k-mooneyefried: it is after nova selects the host16:06
sean-k-mooneyefried: before that it is just a logical port in a db16:07
sean-k-mooneyefried: as part of portbinding nova compute updates the neutron port with the host id16:07
*** dtantsur is now known as dtantsur|afk16:07
efriedSo you want to create the port with an anti-affinity/HA spec which specifies the number of VFs and how they should be spread out...16:08
sean-k-mooneyefried: yep16:08
*** yassine has quit IRC16:08
openstackgerritMatt Riedemann proposed openstack/nova master: Skip more racy rebuild failing tests with cells v1  https://review.openstack.org/49900116:08
efried...and then we schedule to the host and spawn attaches the right number of VFs with the right distribution.16:08
*** kristian__ has joined #openstack-nova16:09
efriedThere's a big hand-wavey part in the middle there, though, where the scheduler was able to figure out which compute host(s) would be able to honor that request.  Is the scheduler (and/or, gods forbid, the placement API) supposed to introspect the port metadata to help with that decision??16:10
sean-k-mooneyefried: yep see my comments in https://review.openstack.org/#/c/463526/ and https://review.openstack.org/#/c/182242/ to this effect16:10
sean-k-mooneyno basically before the scheduler starts scheduling today the neutron v2 client api in nova retrives the port from neutorn16:11
*** marst_ has joined #openstack-nova16:11
*** marst has quit IRC16:12
sean-k-mooneyif that port is vnic_type direct/macvtap or virtio-forwarder it create a new pcieresutespec object16:12
sean-k-mooneywe need to extend that to also read the ha spec and add that to the picerequeste spec so that when tha tis passed to the sceduler/placement it can fufille the requirementes for ha16:12
sean-k-mooneythis is what we have imlemented for the feature based scheduing also16:13
efriedYeah, okay, so that's how it works today; but I thought we were trying to move away from that kind of special-casing as we get into placement.16:13
sean-k-mooneyefried: yes so in placement i would like to be able to express affinity and anti affintiy16:13
*** yamahata has quit IRC16:14
sean-k-mooneyso we would ask for 2 vf with pf antiaffinity16:14
*** Apoorva has joined #openstack-nova16:14
*** kristian__ has quit IRC16:14
sean-k-mooneyplacement would filer host based on that and then the scheduler would make the final desision16:14
efriedHas jaypipes weighed in yet on how affinity/anti-affinity might be made to work with placement?16:15
dansmithefried: distance16:16
sean-k-mooneyproably its not the first time i have mentioned this to him but not aware of his current stance16:16
dansmithefried: as mentioned earlier this morning, but also quite a bit in boston during that session16:16
*** suresh12 has quit IRC16:16
edmondswthere are anti-affinity needs at multiple layers... 1) device, 2) PF, 3) switch...16:16
sean-k-mooneyedmondsw: yes i was hoping we could model the switch as a trait on the pf if that made sense?16:17
efriedRight, so basically placement would need a generic, multi-layer-capable distance/affinity mechanism, and then consumers could model as they see fit within that framework.16:17
sean-k-mooneyefried: yes ideally. its just up to the consumers to model the dependcies with traits and netested providers correctly16:18
*** shan has joined #openstack-nova16:18
*** marst has joined #openstack-nova16:18
sean-k-mooneythat is easier said then done however16:18
sean-k-mooneyideally i would like to see a request for a bonded port that looked someting like this16:19
efriedsean-k-mooney Definitely makes sense for the switch to be a trait on the PF.  Or for the switch to be a RP with its PFs nested underneath it.  Either way would work.  But if these affinity gizmos are separate from traits, then it probably doesn't matter as much how the RPs are nested.16:19
sean-k-mooneyneutron port-create --binding:vnic_type=direct --binding:profile={bond=true, bond_mode=active-backup,bound_count=2,bond_antiafinity=pf} --name bond1 private16:19
*** marst_ has quit IRC16:19
efriedWhere you could conceivably also say bond_antiaffinity=pf,switch ?16:19
sean-k-mooneyefried: yes16:20
jaypipesefried: distance would be stored in an aggregate_distances table, which would store the distance between the providers in one aggregate and providers in another.16:20
jaypipesefried: distance would just be a number. higher the number, greater the relative distance.16:20
edmondswor bond_antiaffinity=card,switch if you want the PFs to come from different physical CNAs?16:21
sean-k-mooneyjaypipes: im not sure that distance would be a good match to antiafinity/affinity if i need to manually create agggreates for the vfs but ingeneral it is usefull16:21
sean-k-mooneyedmondsw: you could but you see the general pattern i would love to express this requirement on the neutorn port in a general way rather then statically defiened in a flavor16:22
edmondswsean-k-mooney yeah, and I think I agree with that if we can make it work16:23
efriedNow, let me make sure I understand something: placement is never going to be in the business of assigning individual VFs around.  It's just gonna decrement the count and say "you got one from this RP".16:23
sean-k-mooneybassically i would like to keep flavor extraspecs for compute requirement16:23
*** marst_ has joined #openstack-nova16:23
*** marst has quit IRC16:23
*** trinaths has left #openstack-nova16:23
efriedThen it's up to the virt driver (or maybe the mech driver in this case?) to decide which specific VF to use -- or even to create the VF on the fly if that's something it can do.16:23
sean-k-mooneyefried: maybe... i think jay would agree i would not mind extending it to be able to do indvidual assignment16:24
jaypipessean-k-mooney: it's a possibility.16:24
efriedPoint is, placement shouldn't be aware of an individual VF any more than it's aware of an individual memory megabyte.16:24
jaypipessean-k-mooney: in the same way that we agreed not to have aggregates have traits (instead, we "push down" all traits to the resource provider)16:25
jaypipesefried: not necessarily.16:25
dansmithjaypipes: eh?16:25
efriedjaypipes: eh?16:25
jaypipesefried: if you need to differentiate between two VFs on a host because those two VFs expose different capabilities, then you will need to create each different VF as a resource provider.16:26
sean-k-mooneyefried: well i would like to have the mem_page resouce provider track indiviual pages too but i have more importing things to adress first16:26
*** rajathagasthya has joined #openstack-nova16:26
dansmithah, sure16:26
efriedOkay, yeah.16:26
dansmithnot sure when/how that would happen16:26
dansmithbut if it did, then I guess16:26
dansmithalthough then we're going to have a shitton of single-resource providers16:26
jaypipesdansmith: ask sean-k-mooney. Intel excels at creating uses for complexity.16:26
dansmithI'd hope that you could separate that into 32 VFs with tls-offload and 32 without, for a 64-vf nic16:27
efriedokay, as long as the general case is to have the inventory of VFs just be a number.16:27
dansmithbut..16:27
dansmithefried: it's still that,16:27
dansmithefried: you'd just have inventory=1 for these16:27
efriedyeah yeah.16:27
efriedI get it.16:27
efriedBut the tls-offload thing...16:27
sean-k-mooneywell i can certenly do a lot with singel-resouce proverders16:28
efriedI would really hope there would be some other way to specify that.16:28
*** annegentle has quit IRC16:28
dansmithefried: I wouldn't16:28
jaypipessean-k-mooney: would single resource providers provide spell checking? :)16:28
sean-k-mooneyhaha perhaps...16:28
dansmithefried: tls-offload being a trait for regular nics, and vfs, so if some have it and some don't...16:28
jaypipessean-k-mooney: :P16:28
efriedBut if I create my VFs on the fly, and could assign that trait to any one of 'em on the fly (say, based on a prop in the binding profile)...16:29
jaypipesdansmith, efried: technically you wouldn't necessarily need to have single resource providers for each VF. just one resource provider per set of VFs with similar capabilities.16:29
dansmithefried: no, that's not the same16:29
dansmithjaypipes: right exactly16:29
*** itlinux has joined #openstack-nova16:29
* jaypipes runs away before calling it pci device pools.16:29
dansmithefried: I meant if some VFs would be unable to provide tls offload, then they go in a separate provider without that trait16:30
sean-k-mooneyso our current generation of nics cant do this but in future nics we will be able to load firmware that gives different feature per vf16:30
dansmithefried: if they all can and it's a by-request thing, then that means they're all in one provider with that trait and the virt driver decides to configure it as such based on the request16:30
*** kristian__ has joined #openstack-nova16:30
sean-k-mooneywith fortvile XL710 its card wide16:30
sean-k-mooneyso all vf would have same features/tratis16:30
dansmithsean-k-mooney: yeah and we're all REALLY glad for that16:30
dansmith(not)16:30
efrieddansmith Ah, exactly what I was getting at earlier, but you said you didn't want.16:30
dansmithefried: huh?16:31
dansmithefried: a request has a list of required and preferred traits16:31
jaypipesdansmith: don't tempt sean-k-mooney. he will call up the hw designers and ask them to rework it to be more complicated :P16:31
*** marst has joined #openstack-nova16:31
dansmithefried: what I said was I didn't want virt-specific communication from the api user to the virt driver16:32
*** marst_ has quit IRC16:32
sean-k-mooneyhaha well i did ask them to make atleas per pf instead of per card...16:32
dansmithefried: this is not that, this is a generic and abstract requested trait.. placement has already filtered out virt hosts that can't do that generic thing16:32
efriedokay, "preferred trait" is new to me.16:32
dansmithefried: doesn't matter, required trait is the same16:32
dansmithfor this example16:32
sean-k-mooneyefriad: the idea was the required traits would be enforced by filter and prefered trais would be consumed by weigher16:33
dansmithsean-k-mooney: and both could feed into how the virt driver does something eventually16:33
sean-k-mooneyyes16:34
abhi89hey guys.. can someone please review https://review.openstack.org/#/c/485121/.. pending from a long time..16:34
sean-k-mooneymy go to examle is dpdk requires sse3 to work but would prefer avx for performance reasons16:34
lbragstadmriedem: https://review.openstack.org/#/c/500918/16:34
*** kristian__ has quit IRC16:35
*** Swami has joined #openstack-nova16:37
*** cfriesen__ has quit IRC16:38
*** gbarros has quit IRC16:38
*** ijw has quit IRC16:40
mriedemlbragstad: comment inline16:41
efriedWhat's the plan for associating physnets with RPs?16:41
efriedDoes the RP have a trait like CUSTOM_PHYSNET_XXX where XXX is somehow associated with the port's physnet?16:42
lbragstadmriedem: good call - done16:43
openstackgerritIldiko Vancsa proposed openstack/nova master: Add attachment_complete call to volume/cinder.py  https://review.openstack.org/49332316:46
openstackgerritIldiko Vancsa proposed openstack/nova master: Tweak connection_info translation for the new Cinder attach/detach API  https://review.openstack.org/49332416:46
openstackgerritIldiko Vancsa proposed openstack/nova master: Implement new attach Cinder flow  https://review.openstack.org/33028516:46
*** yamahata has joined #openstack-nova16:49
*** Apoorva has quit IRC16:49
*** Apoorva has joined #openstack-nova16:50
*** suresh12 has joined #openstack-nova16:50
*** kristian__ has joined #openstack-nova16:51
*** kbaegis has joined #openstack-nova16:52
*** kbaegis has quit IRC16:52
*** kbaegis has joined #openstack-nova16:53
*** Apoorva has quit IRC16:54
*** kristian__ has quit IRC16:55
*** gbarros has joined #openstack-nova16:56
*** shan has quit IRC16:57
*** abalutoiu has joined #openstack-nova16:57
*** jpena is now known as jpena|off16:57
*** david-lyle has quit IRC16:59
*** cfriesen__ has joined #openstack-nova17:00
*** derekh has quit IRC17:00
*** erlon has joined #openstack-nova17:01
*** kbaegis has quit IRC17:02
*** kbaegis has joined #openstack-nova17:02
*** kbaegis has quit IRC17:02
*** ralonsoh has quit IRC17:02
*** kbaegis has joined #openstack-nova17:02
*** lpetrut_ has quit IRC17:03
*** eharney_ has joined #openstack-nova17:04
*** eharney has quit IRC17:05
*** eharney_ is now known as eharney17:05
sean-k-mooneyefried: i think physnet can be a standard trait prefix. so NW_PHYSNET_XXX17:07
efriedOkay; I thought you weren't allowed to create a trait with anything other than a CUSTOM_ prefix.17:08
efriedBut that wasn't really my question.17:08
*** harlowja has joined #openstack-nova17:08
sean-k-mooneyefried: this was one of the usecases i wanted to have key value traits for originally but standard prefixes i think are ok too17:08
efriedMy question is: who's responsible for recognizing that the XXX corresponds to the physnet in the neutron port?17:08
*** Apoorva has joined #openstack-nova17:09
sean-k-mooneyefried: technically yes but lacking key value traits i was hoping we could have a set of stadard prefixes that you were also allowed to create. phynets is one the other option is to have physnet be a field of resouce class17:09
*** shan has joined #openstack-nova17:09
efriedOkay, but who's responsible for recognizing that the XXX corresponds to the physnet in the neutron port?17:10
sean-k-mooneyefried: well if nova reads the phynet form the port it can compute the trait name and placement can then just do a sting match17:10
efriedThat would be one way... is that how it's going to work?  Or is this still part of the open discussion?17:11
*** kristian__ has joined #openstack-nova17:11
sean-k-mooneystill open. i was also thinking of ways to have neutron pass traits/resouce prodier request to nova so that nova does not have to compute the trait name17:12
sean-k-mooneyfor example addint a traits field to the vif_binding details with the physnet name trait so that nova does not have to query neutron for the physnet17:13
sean-k-mooneyagain this is up for discussion17:13
*** david-lyle has joined #openstack-nova17:14
efriedsean-k-mooney Okay, thanks for the info.17:15
*** kristian__ has quit IRC17:16
*** penick has joined #openstack-nova17:16
mriedemdtantsur|afk: vdrok: do you know if there are any docs that talk about quota considerations for a tenant that is accessing both VMs and BMs? it's a topic i added here for the ptg: https://etherpad.openstack.org/p/queens-PTG-vmbm17:16
vdrokhrm, not in ironic docs I think.17:17
sean-k-mooneynova is currently the main thing interacting with traits and placement but i would like to add some knolowe of those apis to neutron so that nova does not have to know as much deails about the networking contriants going forwand and can jsut fowrad the reques for resouce providers and traints form neutorn.17:17
mriedemsean-k-mooney: i think mlavalle already started something like a placement client in neutron a few releases ago17:18
sean-k-mooneymriedem: cool we will need if for thinks like bandwith qos. e.g. if we model bandwith in placement and you increase the minium bandwith for a port i should go to placement and check that there is capasity left and increase the claim if so or fail the requst if not17:20
sean-k-mooneye.g. if port is bound it should only allow bandwith to be increased if placement says there is capasity to do so and provide error to user if it cannot17:21
*** hamzy has joined #openstack-nova17:21
*** kbaegis has quit IRC17:22
*** sambetts is now known as sambetts|afk17:22
*** tesseract has quit IRC17:25
*** rcernin has quit IRC17:25
*** ijw has joined #openstack-nova17:27
jaypipessean-k-mooney: there is no such thing as a standard trait prefix.17:30
jaypipessean-k-mooney: that XXX means it has to be a custom trait.17:30
*** david-lyle has quit IRC17:30
*** suresh12 has quit IRC17:31
sean-k-mooneyjaypipes: correct today. i was hopping we could add them if we were going to use them for standard thing like physnets to differenciate them for user created traits17:31
sean-k-mooneybasically any traint that does not start with custom_ i consider to be a trait that must be defiend in os-traits17:32
jaypipessean-k-mooney: I would oppose that. traits are boolean values.17:32
*** gouthamr has quit IRC17:32
jaypipessean-k-mooney: the physical network that a NIC is associated with must be a custom trait.17:33
sean-k-mooneybut just as we have defiend the custom_ as a user defiend prefix i was hoping we could have other prefiex reseved for internal use such as the physnet17:33
jaypipessean-k-mooney: why though?17:33
jaypipessean-k-mooney: what benefit does that bring?17:33
sean-k-mooneyso i can tell the differnece between traits used by openstack to function and ones added by admins for there own use17:33
*** vikrant has quit IRC17:34
jaypipessean-k-mooney: that'17:34
dansmithsean-k-mooney: that's custom17:34
jaypipess the CUSTOM_ prefix.17:34
sean-k-mooneydansmith: a physnet is custom?17:34
*** yassine has joined #openstack-nova17:35
*** yassine has quit IRC17:35
dansmitho.O17:35
dansmithif it's not a standard one, then it's custom :)17:35
sean-k-mooneywe need to apply physnets to all sriov vf otherwise we cant use them with neutron networks17:35
jaypipesthere's no such thing as a "standard physnet"...17:35
jaypipesit's a named entity17:36
sean-k-mooneyyes we cant standaries the full trait because its just a config option17:36
sean-k-mooneyhence haveing a standard prefix17:36
jaypipesno, it's not a config option... it's an attribute of the port profile isn't it?17:36
sean-k-mooneyno17:36
dansmithnot for sriov right?17:36
sean-k-mooneyit a neutorn and nova config option17:36
dansmithbut even still, those'll all have to be custom ones anyway right?17:37
sean-k-mooneyfor sriov its set in the pci whitelist17:37
jaypipesugh17:37
dansmithbecause they're not enumerable across all deployments17:37
*** annegentle has joined #openstack-nova17:37
*** shan7 has joined #openstack-nova17:37
jaypipeswhat dansmith said.17:37
sean-k-mooneywell no because i have no ideay which pci device is connected to which phyical network unless you tell me17:37
dansmithum, wat?17:38
jaypipesdansmith: he's saying "you" as in the nova.conf setting.17:38
*** liverpooler has quit IRC17:38
sean-k-mooneyyes its not automatically discoverable so we have to declare it statically in the nova.conf17:38
dansmithwe will probably have to do something like we were going to do for ironic, which is synthesize CUSTOM_PHYSNET_$thing_in_your_config17:38
jaypipesi.e. unless the nova.conf pci whitelist indicates which PCI devices are asssociated with which physnet, there's no way for code on the compute host to know.17:38
dansmithsean-k-mooney: right, I know17:38
dansmithsure17:39
dansmithwe have that today17:39
sean-k-mooneydansmith: yes so when we systesize traiths i was suggesting uses a prefix other then custom to do that17:39
dansmithsean-k-mooney: yeah but that does't work17:39
dansmithsean-k-mooney: because anything but a CUSTOM_ is a hard enum in a library17:39
dansmithsean-k-mooney: anything synthesized by the operator or somecode has to be CUSTOM_17:40
*** armax has joined #openstack-nova17:40
sean-k-mooneydansmith: correct so im suggesting that we extend os tratis to have other prefixes that are not enums. if that is not desirabel then CUSTOM_ works too17:40
sean-k-mooneyi just can tell if its created by a person of synthesize by openstack17:41
*** shan has quit IRC17:41
*** shan7 has quit IRC17:42
*** moshele has joined #openstack-nova17:43
*** shan has joined #openstack-nova17:44
sean-k-mooneymay main concern is that as an enduse i have no way of knowing is  CUSTOM_PHYSNET_<XYZ> is special custom trait that casuse a change in the behaior of openstack vs  CUSTOM_MY_TRAIT_<XYZ> that does not.17:44
*** david-lyle has joined #openstack-nova17:46
*** shan7 has joined #openstack-nova17:47
*** shan has quit IRC17:48
*** shan7 has quit IRC17:48
sean-k-mooneyanyway got to run. food is calling17:48
*** shan has joined #openstack-nova17:48
*** gvrangan has joined #openstack-nova17:52
*** kristian__ has joined #openstack-nova17:53
gvranganhttps://docs.openstack.org/nova/pike Folloed the latest install in centOs717:55
gvranganthe hypervisot list is not listing17:55
gvranganthe computes are not added to cells17:56
gvranganShould the doc be updated?17:56
*** kristia__ has joined #openstack-nova17:56
*** suresh12 has joined #openstack-nova17:57
*** kristian__ has quit IRC17:57
*** cdent has joined #openstack-nova17:59
*** gouthamr has joined #openstack-nova17:59
*** baoli has quit IRC18:00
*** baoli has joined #openstack-nova18:01
*** moshele has quit IRC18:02
*** Apoorva_ has joined #openstack-nova18:03
gvranganwhen I execure the discover, the computes are not getting listed18:04
gvranganshould the nova compute be configure differntly in pike?18:04
*** Apoorva has quit IRC18:06
*** karthiks has quit IRC18:06
melwittgvrangan: which instructions did you follow? this? https://docs.openstack.org/nova/latest/user/cells.html#fresh-install18:07
jaypipesgvrangan: pls see /topic. Best to ask your question on the @openstack mailing list.18:07
gvranganmelwitt, I followed only the nhttps://docs.openstack.org/nova/pike/install/controller-install-rdo.html and https://docs.openstack.org/nova/pike/install/compute-install-rdo.html18:08
*** rabel has quit IRC18:08
openstackgerritJackie Truong proposed openstack/python-novaclient master: Microversion 2.54 - Add trusted_certificates param  https://review.openstack.org/50039618:11
melwittgvrangan: okay. I see all of the commands you need are in those docs. so you have to make sure you see cell0 and cell1 when you do 'nova-manage cell_v2 list_cells' and then make sure you did 'nova-manage cell_v2 discover_hosts --verbose' after you have brought up the compute node18:13
*** suresh12 has quit IRC18:14
*** suresh12 has joined #openstack-nova18:17
*** gszasz has quit IRC18:20
rybridges1Hello all18:20
rybridges1I had a quick question about nova cells18:20
rybridges1We are currently attempting to deploy a fresh ocata cluster. I was wondering if [cells] section of nova.conf is required for cells v2 at all? I read in the comments that the stuff under that section is only for cells v1, but just wanted to make sure18:21
*** karthiks has joined #openstack-nova18:22
melwittrybridges1: that's correct. see 4. on the FAQ, [cells] section is not to be used https://docs.openstack.org/nova/latest/user/cells.html#faqs18:23
efriedjaypipes We were talking last week about how to model e.g. minimum egreess bandwidth support on SR-IOV VFs.18:24
rybridges1Okay great! Thanks melwitt18:24
jaypipesefried: who is we? :)18:25
efrieddansmith suggested we would model the PF as a RP with e.g. SRIOV_VFS=48,EGRESS_BW_PCT=10018:25
efriedSo that basically you would grab some number of VFs and some percentage of the bandwidth, and whichever you exhausted first would take that PF out of the running for subsequent requests, kind of thing.18:26
efriedFirst of all, is this along the lines of what you've been thinking?18:26
efriedDoesn't have to be percentage; could be bps or whatever; point is the number of VFs and the total bandwidth are separate but parallel resource classes in the RP.18:27
cdent“parallel”?18:27
efriedjust meaning that they're RC inventories on the same RP18:27
* efried will stop trying to invent terminology18:28
cdentisn’t that what we do around here?18:28
efriedSome of us shouldn't.18:28
jaypipesefried: yep. that's pretty close. I don't like the pct versus using bytes_per_sec but yeah.18:29
jaypipesefried: in fact, that's pretty close to what I had written on the ML, no?18:29
efriedjaypipes okay, so help me fill in the gaps here.18:29
efriedIRL I'll have multiple PF-y RPs, and let's say they each have both of those RC inventories defined.18:30
jaypipesk18:30
efriedWhen I make a request for, say, SRIOV_VFS=1,EGRESS_BW_PCT=20 -- what's to stop placement from allocating the VF inventory from one RP and the egress bandwidth inventory from another??18:31
*** rajathagasthya has quit IRC18:31
openstackgerritMateusz Kowalski proposed openstack/nova stable/pike: Handle keypair not found from metadata server using cells  https://review.openstack.org/50095318:32
openstackgerritMateusz Kowalski proposed openstack/nova stable/ocata: Handle keypair not found from metadata server using cells  https://review.openstack.org/50095418:32
*** crushil has quit IRC18:34
* efried is hoping jaypipes is (a) composing an eloquent but incredibly clear response; or (b) temporarily distracted by real work but eagerly looking forward to getting to (a); but not (c) scraping skull fragments and bits of brain off the walls.18:36
jaypipesefried: actually currently stressing out trying to figure out how to deal with this hurricane that is going to hit us.18:36
efriedjaypipes Been there, done that.  Where you at?18:37
jaypipesefried: and getting my girls to safety and my wife to her plane flight to Italy on Sunday :(18:37
jaypipesefried: Sarasota18:37
efriedTotally counts as (b)18:38
jaypipesefried: the answer to your question is: nothing would stop placement from doing so.18:40
efriedjaypipes Then... "eek".18:40
jaypipesefried: yeah18:40
*** ijw has quit IRC18:41
efriedThe followup, of course, is what about SRIOV_VFS=4,EGRESS_BW_PCT=20 ?18:41
*** crushil has joined #openstack-nova18:41
jaypipesefried: we would need to add some mechanism to the request that says "make sure the thing providing EGRESS_BW_PCT and SRIOV_VF is the same provider.18:42
efriedjaypipes Rojah dat.  Any thoughts been assayed in that regard to this point?18:42
*** sridharg has quit IRC18:42
melwittmriedem: I'm gonna sign up for that nova project update redhat interview thing at the PTG18:43
jaypipesefried: resource_constraints=same_provider:SRIOV_NET_VF,NET_EGRESS_BYTES_SEC&resources=SRIOV_NET_VF:1&NET_EGRESS_BYTES_SEC:2000018:44
mriedemmelwitt: awesome18:44
openstackgerritMerged openstack/nova master: Replace dd with shred for zeroing lvm volumes.  https://review.openstack.org/49553218:44
*** ijw has joined #openstack-nova18:46
efriedjaypipes What stage is that semantic in?  Just popped out of your head, in a spec somewhere, implemented, released?18:46
*** Apoorva_ has quit IRC18:47
*** Apoorva has joined #openstack-nova18:47
*** moshele has joined #openstack-nova18:47
*** tinwood has quit IRC18:48
jaypipesefried: popped off the top of my thick, oh so thick, head of hair.18:48
melwittmriedem: let me know if there's anything else you'd like me to highlight other than cells and placement. I was gonna go through the rel notes and dev ML announcements to see what else to mention18:48
*** pcaruana has quit IRC18:49
melwittand then I'll use the nova PTG etherpad to summarize what's coming up in queens18:49
efriedjaypipes Cool, will add it to discussion points.18:49
efriedI still need to complete my reading, but presumably there's a syntax for requesting multiple different resources of the same class with different traits?18:49
*** tinwood has joined #openstack-nova18:49
*** moshele has quit IRC18:51
efriedjaypipes So like, pursuant to the anti-affinity grouping conversation avolkov and I were having earlier, I want to be able to say gimme (SRIOV_NET_VF:1&NET_EGRESS_BYTES_SET:2000&traits=CUSTOM_PF_HA_GROUP_1; SRIOV_NET_VF:1&NET_EGRESS_BYTES_SET:2000&traits=CUSTOM_PF_HA_GROUP_2)18:51
mriedemmelwitt: i can send you my list that i sent internally18:51
*** suresh12 has quit IRC18:51
melwittmriedem: cool, I think that would be helpful. thanks18:52
*** suresh12 has joined #openstack-nova18:53
*** prometheanfire has joined #openstack-nova18:54
jaypipesefried: lemme pastebin something for that18:54
prometheanfirethis look like an error with the os-xenapi bump? http://logs.openstack.org/70/500770/3/check/gate-cross-nova-python27-ubuntu-xenial/1305547/testr_results.html.gz18:54
prometheanfirefrom https://review.openstack.org/50077018:54
*** ociuhandu has joined #openstack-nova18:54
mriedemprometheanfire: looking18:55
openstackgerritMichael Still proposed openstack/nova master: Move nbd commands to privsep.  https://review.openstack.org/50035118:56
openstackgerritMichael Still proposed openstack/nova master: Move lvm handling to privsep.  https://review.openstack.org/49551618:56
openstackgerritMichael Still proposed openstack/nova master: Move xend existence probes to privsep.  https://review.openstack.org/49553818:56
openstackgerritMichael Still proposed openstack/nova master: Move shred to privsep.  https://review.openstack.org/49553718:56
openstackgerritMichael Still proposed openstack/nova master: Cleanup mount / umount and associated rmdir calls  https://review.openstack.org/49442318:56
openstackgerritMichael Still proposed openstack/nova master: WIP / Aspirational: we don't need rootwrap any more.  https://review.openstack.org/49554218:56
openstackgerritMichael Still proposed openstack/nova master: Move loopback setup and removal to privsep.  https://review.openstack.org/49566418:56
openstackgerritMichael Still proposed openstack/nova master: Move libvirt usages of chown to privsep.  https://review.openstack.org/47197218:56
openstackgerritMichael Still proposed openstack/nova master: Don't shell out to mkdir, use ensure_tree()  https://review.openstack.org/49232618:56
openstackgerritMichael Still proposed openstack/nova master: Move the idmapshift binary into privsep.  https://review.openstack.org/49554118:56
openstackgerritMichael Still proposed openstack/nova master: Move ploop commands to privsep.  https://review.openstack.org/49232518:56
openstackgerritMichael Still proposed openstack/nova master: Read from console ptys using privsep.  https://review.openstack.org/48948618:56
openstackgerritMichael Still proposed openstack/nova master: Move kpartx calls to privsep.  https://review.openstack.org/50035418:56
openstackgerritMichael Still proposed openstack/nova master: Avoid chowning console logs in libvirt  https://review.openstack.org/47222918:56
openstackgerritMichael Still proposed openstack/nova master: First attempt at adding a privsep user to nova itself.  https://review.openstack.org/45916618:56
openstackgerritMichael Still proposed openstack/nova master: Move execs of touch to privsep.  https://review.openstack.org/48919018:56
prometheanfiremriedem: that's a quick git-review you have there (or rebase maybe)18:56
openstackgerritMichael Still proposed openstack/nova master: Move libvirts dmcrypt support to privsep.  https://review.openstack.org/49073718:56
openstackgerritMichael Still proposed openstack/nova master: Move blkid calls to privsep.  https://review.openstack.org/50039818:56
openstackgerritMichael Still proposed openstack/nova master: Move execs of tee to privsep.  https://review.openstack.org/48943818:56
prometheanfirebah, meant that for michael18:56
openstackgerritMerged openstack/nova master: Updated from global requirements  https://review.openstack.org/50001118:57
efriedprometheanfire git restack, yo.18:57
prometheanfirewhat that come from?18:58
efriedIt's a thing, hold on...18:58
*** ijw has quit IRC18:58
*** penick has quit IRC18:58
*** penick has joined #openstack-nova18:59
efriedprometheanfire I think you install it with `pip install git-restack`18:59
*** thorst_afk has quit IRC18:59
* prometheanfire is gonna see if that should be packaged or not18:59
efriedIt's a git plugin maintained by stackers18:59
*** thorst_afk has joined #openstack-nova18:59
mriedemprometheanfire: looks like this is the regression https://github.com/openstack/os-xenapi/commit/755876c19f7c47eaa773f835a68dcf93c3d6b50d19:00
efriedprometheanfire You say `git restack <commit-before-the-bottom-of-the-pile>`.  Then you can choose to edit whichever ones in the chain via an edit file that looks kinda like when you rebase -i.  It auto rebases everything in the pile.  Then when you're done, you can `git review` and it pushes the whole pile (anything that has been changed, including rebases)19:01
prometheanfiremriedem: k, so nova needs to update it's tests?19:01
prometheanfireefried: I'll probably just stick to the classic rebase then19:02
mriedemprometheanfire: not sure if it's that or if os-xenapi is regressed19:02
mriedemi can start with reporting a bug19:03
prometheanfirek19:03
prometheanfireI'll hold that back for now then19:03
mriedemthanks19:03
*** ociuhandu_ has joined #openstack-nova19:04
*** yangyapeng has quit IRC19:04
*** thorst_afk has quit IRC19:04
*** ociuhandu has quit IRC19:05
efriedjaypipes I'll have the same question about the "multiple resources, same class, different traits" syntax (in what state of maturity is this idea?)19:05
mriedemprometheanfire: https://bugs.launchpad.net/nova/+bug/171521719:08
openstackLaunchpad bug 1715217 in OpenStack Compute (nova) "nova xenapi unit tests fail with os-xenapi 0.3.0" [Undecided,New]19:08
*** moshele has joined #openstack-nova19:08
prometheanfirethanks19:09
*** abhi89 has quit IRC19:09
*** moshele has quit IRC19:10
*** thorst_afk has joined #openstack-nova19:11
*** gbarros has quit IRC19:12
openstackgerritJackie Truong proposed openstack/nova master: Add trusted_certs to instance_extra  https://review.openstack.org/45771119:13
*** priteau has quit IRC19:15
*** thorst_afk has quit IRC19:15
*** gbarros has joined #openstack-nova19:16
artomHow are our man pages generated? Am I understanding correctly that https://review.openstack.org/#/c/475810/ has nothing to do with man pages?19:17
artomstephenfin ^^, since you're the patch author :)19:17
*** gbarros has quit IRC19:18
*** slaweq_ has joined #openstack-nova19:21
*** rajathagasthya has joined #openstack-nova19:24
mriedemartom: https://github.com/openstack/nova/blob/master/doc/source/conf.py#L11319:24
mriedempart of the sphinx build19:24
mriedemand yes https://review.openstack.org/#/c/475810/ has nothing to do with man pages19:24
artommriedem, and those all come from the doc/source/cli directory?19:24
mriedemyeah19:25
*** gbarros has joined #openstack-nova19:25
artomThanks :)19:25
mriedemdid i win?19:25
artomMy eternal indifference19:25
artom(It's 2 steps up from seething hatred)19:26
*** thorst has joined #openstack-nova19:27
*** gvrangan has quit IRC19:28
*** tonygunk has joined #openstack-nova19:32
*** cdent has quit IRC19:34
*** slaweq_ has quit IRC19:34
*** slaweq_ has joined #openstack-nova19:35
*** itlinux has quit IRC19:35
*** priteau has joined #openstack-nova19:37
*** priteau has quit IRC19:41
*** ijw has joined #openstack-nova19:45
*** suresh12 has quit IRC19:47
*** kristia__ has quit IRC19:48
openstackgerritLee Yarwood proposed openstack/nova-specs master: Libvirt: Native LUKS file and host device decryption by QEMU  https://review.openstack.org/49082419:49
*** suresh12 has joined #openstack-nova19:49
*** esberglu has quit IRC19:50
*** esberglu has joined #openstack-nova19:50
*** egonzalez has joined #openstack-nova19:52
jaypipesefried: I don't know how to structure a request that would impart the required information for this query :(19:53
efriedjaypipes Well, shit, if YOU can't do it....19:54
efriedAdding to list.19:54
jaypipesefried: we would essentially need to replicate child-parent information in the request for resources. in other words, the requestor must know that a VF is a child of a PF is a child of a compute host.19:54
jaypipesefried: and we can't ask the user to know that relationship...19:55
*** esberglu has quit IRC19:55
efriedjaypipes But the alternative is making them separate resource classes.  Which doesn't seem right at all.19:55
jaypipesefried: no, that doesn't work either...19:55
jaypipesefried: because their not separate resource classes. they're separate providers.19:56
jaypipesefried: just imagine for a second how one might ask AWS for such a thing.19:56
* efried doesn't know from AWS19:56
jaypipesefried: you can't.19:56
efrieduhm19:57
jaypipesefried: you need a more complicated DSL like CloudFormation or TOSCA19:57
efriedSo how are we planning to model e.g. asking for more than one cinder volume?19:57
jaypipesefried: and an orchestrator that would take one of those request templates and produce multiple requests to EC2 APIs.19:57
jaypipesefried: we don't. that's the very reason why we've pushed back on having the compute API be an orchestration system.19:58
mriedemprometheanfire: i think i've got these xenapi unit tests fixed19:58
mriedemshould have a patch up shortly19:58
prometheanfirecool19:58
jaypipesefried: you want >1 cinder volumes? then create them in cinder and attach them to your compute instance.19:58
*** suresh12 has quit IRC19:58
prometheanfireif that merges today then the xenapi change can go in tomorrow via bot update19:58
jaypipesefried: there is absolutely no "atomically create 10 volumes in Cinder" command.19:59
*** tidwellr has left #openstack-nova19:59
*** priteau has joined #openstack-nova19:59
mriedemthere isn't?!19:59
jaypipesefried: and these kinds of requests that the VNFM would be making are essentially that: requests for a set of related resources to be created as an atomic unit.19:59
efriedjaypipes Seems like there should be a way to specify multiple `resources=` keys in a single request, kind of thing.20:00
mriedemhow about i request 10 VMs with block_device_mapping_v2 in the request, of size 10, for each entry with different device names so nova creates the volumes!20:00
jaypipesincidentally, this is why there's no atomicity guarantees that *any* orchestrator provides. not k8s, not heat, not IBM "smart" cloud orchestrator. not any of them.20:00
mriedemdoes sco still exist?20:00
jaypipesheh, no idea.20:00
smcginnismriedem: I hear they own the copyright to OpenStack.20:01
efriedonly as a lawsuit troller20:01
*** yangyapeng has joined #openstack-nova20:01
mriedemthey do have a snapshot api for vmware instances20:01
mriedemwhich is different from os-createImage20:01
mriedemdifferent, and superior20:01
efriedYeah, less concerned about atomicity at the moment.20:02
efriedI mean, what if I want two different GPUs with different specialties?20:02
efried / capabilities20:03
mriedemask cyborg20:03
*** esberglu has joined #openstack-nova20:03
efriedI don't know what that means20:03
mriedemhttps://wiki.openstack.org/wiki/Cyborg20:04
mriedemhttps://review.openstack.org/#/c/448228/20:04
mriedemjaypipes: is Roman Dobosz still around?20:04
mriedemoh nvm20:05
mriedemno20:05
*** ijw has quit IRC20:05
jaypipesmriedem: no20:05
mriedemhe was osic?20:05
jaypipesno20:05
jaypipesjust got moved to a super-special-secret internal Intel project20:05
*** ijw has joined #openstack-nova20:05
efriedOkay, so IIRC, it's legal in HTTP for a query param key to be repeated, and show up on the server side as a list of values.20:06
jaypipesefried: show me an EC2, GCE, or Azure ability to request an instance that has multiple GPUs that are different.20:06
jaypipesefried: yes.20:06
efriedWhat, because they can't do it, we shouldn't?20:06
efriedI mean, I'm at a clear disadvantage here, having no experience with any of those things.20:07
jaypipesefried: no, because they can't do it is a pretty good indication that it's not something we should spend a shit-ton of time trying to do ;)20:07
openstackgerritMatt Riedemann proposed openstack/nova master: Make xen unit tests work with os-xenapi>=0.3.0  https://review.openstack.org/50096820:07
efriedWhat if it's not a shit-ton of time?20:07
jaypipesefried: if it wasn't, you'd have done it already.20:07
*** esberglu has quit IRC20:07
mriedemprometheanfire: https://review.openstack.org/50096820:08
efriedMebbe I will.20:08
efriedBut - okay - will put this down for now as "stated acceptable limitation".20:08
jaypipesefried: all of these feature requests are basically for NFV use cases, anyway... which is hardware-defined software as I've said before. It's not cloud in as much as it's not abstraction. It's basically just automating the installation of \a very specific hardware environment.20:09
efriedjaypipes So can I have a VM on more than one network?20:10
jaypipesefried: you can do that *now*...20:11
efriedjaypipes Right, but when everything's placement, how am I gonna say "give me one VF from physnet A and one VF from physnet B" ?20:11
jaypipesefried: I don't know.20:12
openstackgerritLee Yarwood proposed openstack/nova master: libvirt: Refactor encryptor attach and detach calls  https://review.openstack.org/46024320:12
jaypipesefried: I've been staring at a pastebin for 2 hours trying to think of how to represent that request.20:12
efriedI mean, per earlier conversation with sean-k-mooney, I'll create one neutron port on each physnet and stuff 'em both into the spawn request; but somebody's gonna have to get both of those guys into placement somehow.20:12
*** Swami_ has joined #openstack-nova20:13
*** Swami_ has quit IRC20:13
jaypipesefried: without inventing YET ANOTHER orchestration DSL ala Kubernetes pod templates, Heat templates, TOSCA, and CloudFormation.20:13
jaypipesefried: which... oh wait! are orchestration frameworks, not compute infrastructure services. :)20:13
*** smatzek has quit IRC20:14
*** efried is now known as efried_bbiab20:15
*** abalutoiu has quit IRC20:15
jaypipesefried_bbiab, edleafe, dansmith: I'm getting close to saying "fuck it, let's add another placement REST endpoint called POST /crazypants that accepts a JSON blob representing the innumerable requests for related resources that an orchestrator has"20:18
mriedemmmm JsonFilter20:18
mriedemv220:18
dansmithjaypipes: maybe we should finish several of the things we started with baseline gains before we freak out about not being able to request two different types of gpus20:20
openstackgerritMerged openstack/nova master: Add video type virtio for AArch64  https://review.openstack.org/49382220:20
jaypipesdansmith: that sounds like an excellent idea.20:21
openstackgerritMerged openstack/nova master: Add uuid to migration table  https://review.openstack.org/49693320:21
*** suresh12 has joined #openstack-nova20:22
mriedemdansmith: when is https://review.openstack.org/#/c/498510/ not a WPI?20:23
mriedem*WIP20:23
mriedemgiven patches are merging20:23
dansmithmriedem: meant to remove it after the last round but ... didn't20:23
*** ijw has quit IRC20:24
openstackgerritDan Smith proposed openstack/nova-specs master: Add migration-allocations spec  https://review.openstack.org/49851020:24
dansmithther go20:24
*** ijw has joined #openstack-nova20:24
*** cdent has joined #openstack-nova20:28
openstackgerritJackie Truong proposed openstack/nova master: Add trusted_certs to instance_extra  https://review.openstack.org/45771120:29
openstackgerritChris Dent proposed openstack/nova master: WIP: [placement] POST /allocations to set allocations for >1 consumers  https://review.openstack.org/50007320:29
openstackgerritChris Dent proposed openstack/nova master: Move project_id and user_id to Allocation object  https://review.openstack.org/50041020:29
*** tonygunk has quit IRC20:29
openstackgerritJackie Truong proposed openstack/nova master: Add trusted_certs to Instance object  https://review.openstack.org/48940820:31
*** marst has quit IRC20:33
*** tbachman has quit IRC20:36
melwittcdent: heh, I think we all noticed the issues with project_id/user_id on the List object at the time but nobody was sure we would need them per allocation yet20:36
*** artom has quit IRC20:36
cdentmelwitt: tru20:36
openstackgerritmelanie witt proposed openstack/nova-specs master: Convert consoles code to use objects framework  https://review.openstack.org/50097520:36
*** edmondsw has quit IRC20:36
*** edmondsw has joined #openstack-nova20:37
*** edmondsw has quit IRC20:42
*** cleong has quit IRC20:42
*** rcernin has joined #openstack-nova20:44
*** pchavva has quit IRC20:45
*** gbarros has quit IRC20:46
*** shan7 has joined #openstack-nova20:46
*** lucasxu has quit IRC20:48
*** shan has quit IRC20:50
*** efried_bbiab is now known as efried20:52
efriedjaypipes Maybe different types of GPUs is crazypants, but somebody's gonna object to not being able to put a VM on more than one network.20:54
jaypipesefried: again, you can already do that.20:54
efriedjaypipes With placement?20:54
efriedMaybe I misunderstood the previous conversation.  But I thought that was exactly my point: you can do it today, but you won't be able to do it tomorrow.20:55
jaypipesefried: no, not with placementy.20:55
jaypipesefried: you can currently do it with the physnet tag hack in the pci_passthrough_whitelist thing.20:56
jaypipesefried: and pre-creating Neutron ports with matching physnet tags20:56
jaypipesefried: and passing those ports in to the Nova boot request20:57
*** slaweq_ has quit IRC20:57
*** slaweq_ has joined #openstack-nova20:58
efriedjaypipes Right.  And I *thought* part of what we were trying to move toward is getting rid of the current PCI setup in favor of having device (incl. PCI) management revolving around placement.20:58
jaypipesefried: what you're asking for here is combining the PCI device manager and PCIPassthroughFilter's behaviour of selecting a specific device based on arbitrary tags in the pci_device_request into the placement API.20:58
efriedjaypipes Well.... yes.20:58
*** tbachman has joined #openstack-nova20:59
efriedI'm asking what's the answer to that ^ gonna be when we've gotten rid of the PCI device manager and moved to Placement nirvana.20:59
jaypipesefried: I'd like to be storing structurally-correct data in the placement DB, yes. that means nested resource providers, support for traits, and linking the (generic) device manager with support for both setting traits and inventory on a tree of provider records.20:59
dansmithefried: the people that want to attach multiple physical networks to vms are the same people that ultimately keep most of us employed you know21:00
jaypipesefried: what I *don't* see a way to do -- again, without crazypants complex DSLs -- is a way to reproduce the PciPassthroughFilter and NUMATopologyFilters as REST API requests to placement21:00
dansmithefried: I don't think we'll deprecate or remove legacy structures from nova before we have a way to replicate critical behavior like that using something else.. not sure where you got that idea21:00
jaypipesefried: it's the "how do I request all these related things from the placement REST API" part that has me stumped, not the "please store this structured data in the placement DB" part.21:01
efriedjaypipes Right, I can see how to get the structure/inventory data into placement.21:02
*** Apoorva_ has joined #openstack-nova21:02
jaypipesefried: yes. we're both A-OK on that front.21:02
*** smatzek has joined #openstack-nova21:02
efrieddansmith Sorry it came across that way; I misunderstood some stuff.21:03
jaypipesefried: however, I still don't know a way to make a request of the placement API without essentially reproducing a domain-specific YAML/JSON language to deal with these complex topology requests.21:03
*** jheroux has quit IRC21:04
*** eharney has quit IRC21:04
efrieddansmith When jaypipes was venting about nova not being a cloud orchestration thingy, I thought he was saying being able to request multiple networks was a cloud orchestration thingy behavior, and that nova shouldn't be in that business.21:04
*** gouthamr has quit IRC21:05
efried...Which may indeed be what he was saying - just not suggesting that that actually *happen* :)21:05
*** crushil has quit IRC21:05
efriedjaypipes Right, so go with me on this "multiple instances of the `resources=` key" thing for a sec.21:05
*** Apoorva has quit IRC21:06
dansmithefried: I think what he was saying was that expecting nova to do lots of steps for you (i.e. determine and reserve multiple resources) as part of a single boot request is really getting into orchestration21:06
*** egonzalez has quit IRC21:06
openstackgerritBrianna Poulos proposed openstack/nova master: Add trusted_certificates to REST API  https://review.openstack.org/48620421:07
efriedSo I'm confused as to how VCPU+MEM_MB+DISK_GB isn't determining and reserving multiple resources.21:07
dansmithefried: are you just being sarcastic and difficult now?21:07
dansmithobviously that's not21:07
*** penick has quit IRC21:07
efriedNo, dansmith, I'm actually this obtuse I'm afraid.  Mostly from lack of experience (and a disproportionate lack of inhibition to speak up and ask questions).21:08
efriedBut again, apologies, I think I understand what you mean now.21:08
efriedwhen you said "multiple resources"21:08
efriedyou meant "multiple disparate resources of the same class".21:09
efriedmahbad.21:09
jaypipesefried: hold up... I just thought of something... gimme a minute to flesh it out in my brain.21:09
efriedbtw jaypipes I realized as I started typing it why the 'multiple querystring keys' thing is a nonstarter if traits is its own qs key...21:09
dansmithefried: I mean things like nova going to cinder to create, image, and attach a volume, and to neutron to create multiple ports for a complex network layout, and then to some other service to arrange for party balloons to be sent in ten minutes, and then, finally, to boot the instance21:10
efrieddansmith Rightright.  And I think again the reason I'm confused as to why we wouldn't want that is because that (at least the neutron & cinder stuff) is part and parcel of what nova does today, and therefore what I think of as being in nova's purview.21:11
efriedand if we're not taking away at least the neutron &/| cinder stuff, then presumably there's going to have to be an answer for it in the placement world.21:12
efriedwhich solution, if we're gonna solve it for neutron & cinder, would seem like it oughtta work for whatever.21:12
efriedalthough I'm *not* suggesting it should go talk to just any external service.21:13
*** harlowja has quit IRC21:13
*** itlinux has joined #openstack-nova21:13
dansmithI don't follow21:14
efriedIn the case of neutron, the model we have today for VFs is that you create your ports in neutron and then some gizmo in nova knows to associate that with the physnet tags from the [pci]passthrough_whitelist (which is one of jaypipes's bugbears)21:14
dansmithwe're not talking about getting rid of neutron or our talking to it, but just not trying to build requests for complex things into nova's API, IMHO21:15
dansmithI think I've lost track of why this is coming up in the context of placement21:15
*** edmondsw has joined #openstack-nova21:16
jaypipesI'm still pastebinning. :)21:17
efrieddansmith Well, the premise - which I *think* started with jaypipes (see comments here https://review.openstack.org/#/c/497965/) - is that we want to phase out the PCI device management gorp that's been frankensteined over the years.21:17
*** ijw has quit IRC21:17
jaypipesguys, can I hit pause on this conversation for 5 minutes so I can finish my braindump?21:17
*** tbachman has quit IRC21:17
efried...with some kind of "generic device manager" which talks to Placement21:17
efriedsure.21:17
*** thorst has quit IRC21:18
dansmithefried: definitely, to the extent we can21:19
*** smatzek has quit IRC21:19
openstackgerritDan Smith proposed openstack/nova-specs master: Add migration-allocations spec  https://review.openstack.org/49851021:20
*** shan7 has quit IRC21:24
*** thorst has joined #openstack-nova21:37
*** thorst has quit IRC21:42
*** catintheroof has quit IRC21:43
*** crushil has joined #openstack-nova21:43
*** kbaegis has joined #openstack-nova21:46
*** suresh12 has quit IRC21:48
*** kbaegis has quit IRC21:52
*** rcernin has quit IRC21:53
*** slaweq_ has quit IRC21:57
cfriesen__when calling a remotable object function, does nova-conductor do a keystone token validation?21:59
dansmithno22:01
*** thorst has joined #openstack-nova22:07
*** thorst has quit IRC22:10
*** burt has quit IRC22:10
*** annegentle has quit IRC22:10
*** annegentle has joined #openstack-nova22:11
*** ijw has joined #openstack-nova22:13
*** priteau has quit IRC22:15
*** annegentle has quit IRC22:16
*** ijw has quit IRC22:21
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Spec for flavor description  https://review.openstack.org/50101722:21
mriedemKevin_Zheng: ^22:21
*** felipemonteiro_ has quit IRC22:22
*** tidwellr has joined #openstack-nova22:23
jaypipesefried, dansmith: sorry, dinner got in the way..22:23
jaypipesefried, dansmith: dumped some thoughts here: http://paste.openstack.org/show/620456/22:23
efriedjaypipes ...22:24
jaypipesefried: yes?22:25
efriedjaypipes Sorry, that's "Message received, processing..."22:26
jaypipesefried: ack22:26
*** sdague has quit IRC22:26
*** lyan has quit IRC22:27
*** tidwellr has quit IRC22:27
efriedjaypipes Yes, just so.  But I thought this was the part we were all in sync with.  The part we hadn't yet come to grips with was the hand-waving on L35-6.22:29
*** baoli has quit IRC22:30
jaypipesefried: no, I can come up with an *internal* representation for the request. what I can't figure out is how to map that to a *single* REST API call.22:30
efriedRight.22:30
efriedjaypipes Don't kill me don't kill me but... what if I numbered the query param keys?22:31
efriedresources1=...&traits1=...&resources2=...&traits2=...22:32
jaypipesefried: uhm, eww? :)22:32
efriedWell, yeah it's eww, that's a given.  But it's clear that it could work.22:32
efriedIt could also conceivably answer the thing where it matters what order we attach devices in...22:33
efried...which some people care about.22:33
jaypipesefried: not sure I follow why the attachment order matters to the placement API.22:33
efriedIt doesn't, but when the request comes in, don't those keys come through?  Mebbe not, sorry.22:33
efriedAnyway, for the general case, non-numbered querystring keys work just fine; in fact they don't even have to be numbers - we just parse the prefix and group by the suffix, whatever it is.22:35
jaypipesefried: the problem with adding this to the placement REST API is that then we're adding a bunch of orchestration-like logic into the placement service.22:36
jaypipesefried: instead of keeping that out of placement and relying on the caller to placement understanding that the request contains a number of "subrequests" that are for specific complex types.22:36
efriedjaypipes Yeah, I admit I don't understand what is meant by "orchestration" and where that line is drawn.22:37
jaypipesefried: dealing with lots of resources as a group is orchestration.22:37
jaypipesefried: where the relationship between the resources, the dependencies between them, the constraints that each imposes on each other, etc. that's orchestration.22:38
jaypipesefried: whereas placement is designed to be a fast, efficient method of determining providers of resources for a given simple request for capacity.22:38
*** tbachman has joined #openstack-nova22:40
cdentjaypipes: can you clarify something for me: I’m not fully grokking why, in your paste, we need to make multiple requests to /a_c ? Is it is because at the point we don’t have a good way to express (in one request) what we want or is there more than that?22:41
efriedjaypipes I'm probably being obtuse again, but I still don't really see how what we're talking about here doesn't still fall into that description.  Placement is designed to grab resources from multiple resource providers.  From a way-zoomed-out view, saying "you can only get stuff from a given resource class from a single provider" seems like an arbitrary limitation.  Zoom back in, and it's one that seems imposed because we22:42
efried're having trouble expressing it under the current design, not because it inherently crosses the line to "orchestration".22:42
cdentjaypipes: on line 50 it is GROUP_A on the first go round and GROUP_B on the second?22:42
*** claudiub|2 has quit IRC22:43
efriedcdent Yeah; and/or L49 could be different egress bandwidth numbers22:43
cdentthanks22:43
jaypipescdent: a couple reasons for that. the first is that it's difficult for me to map the concept of related sub-requests in a single REST API call (again, without resorting to some DSL-ish request payload) and b) because I suspect these types of use cases are just the tip of the iceberg and that the logic that relates various things with each other (GPUs, FPGAs, NIC HA groups, etc) will be different and not possible to cleanly express with simple22:44
jaypipesquery parameters.22:44
* cdent nods22:44
jaypipescdent: and yes, it would be GROUP_A on the first go around and GROUP_B on the second.22:44
cdentjaypipes: next question: step 4 sounds like a pretty big step backwards for the goals we originally expressed for allocation_candidates22:45
jaypipescdent: could also have different amounts of egress bandwidth, different affinity policies, different all sorts of things, frnakly22:45
jaypipescdent: Yupppp!22:45
cdentwhy can’t we have a complete allocation_requests (just to be explicit)22:45
*** Apoorva_ has quit IRC22:45
jaypipescdent: it removes the whole opaqueness aspect of the allocation request :()22:45
cdentyes much :(22:45
efriedIs it because the allocation request is keyed by resource class?22:46
efried(haven't looked at that guy yet)22:46
*** Apoorva has joined #openstack-nova22:46
jaypipescdent: we can't have a complete allocation_requests unless placement is passed all of the logic about relationship between sub-resources22:46
cdentI thought that’s what nested was providing us?22:47
jaypipesefried: the allocation request is not keyed by resource class, no.22:47
jaypipesefried: the allocation request is essentially the request payload to PUT /allocations/{consumer_uuid}22:47
openstackgerritMichael Still proposed openstack/nova master: Add release note for requiring shred 8.22 or above.  https://review.openstack.org/50102222:47
*** edmondsw has quit IRC22:47
cdentjaypipes: related, have you yet seen: http://lists.openstack.org/pipermail/openstack-dev/2017-September/121824.html from avolkov ?22:48
efriedjaypipes And it must be able to contain resources from different RPs.  So why would there be a limitation that RCs therein be unique?22:48
efriedcdent That's what started this whole thing :)22:48
*** edmondsw has joined #openstack-nova22:48
cdentah, good22:48
efriedcdent Back around http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-09-05.log.html#t2017-09-05T15:37:3922:48
cdentpresumably the response to option 2 is “no”22:49
cdentas that’s not "real"22:49
jaypipescdent: nested resource providers allows the placement API to understand whether, say, a PF that provides some VFs is on a particular compute node. Nested providers doesn't, however, solve the problem of how do we model the *request* for resources when the user doesn't know that there is a nested relationship between things.22:49
jaypipesefried: there is no such limitation. I'm not sure what you're getting at.22:49
mikalmriedem: I am a bad man and realized once that shred patch had merged that it probably should have had a reno, so I've added one in https://review.openstack.org/#/c/501022/22:50
*** esberglu has joined #openstack-nova22:50
efriedjaypipes What you and cdent were saying about breaking opaqueness?  And a step backwards for original goals of allocation_candidates.  I didn't catch where that came from.22:51
cdentjaypipes: I get that the request modeling is a limitation, but if were to set that aside for a moment and we could express the request well then the we could present a complete set of allocations in response, right? The limitation as described in your paste is because the current request doesn’t have all the state.22:51
cdentefried: ideally it would be possible to take the first item in the allocation_request list and send that to /allocations/{consumer_uuid} without modifications to make a “claim”22:52
efriedcdent Why doesn't that still work in this scenario?22:52
jaypipesefried: the items in the "allocation_requests" part of the HTTP response for the GET /allocation_candidates placement API call is intended to be able to pass as-is (i.e. opaquely without the caller needing to know the structure of the HTTP payload) to the PUT /allocations/{consumer_uuid} call.'22:52
*** edmondsw has quit IRC22:52
cdentbut if you’ve used multple requests to construct the set of rps, we don’t have enough info to construction all the pieces of the allocation22:52
jaypipescdent: correct.22:53
cdentfeh22:53
efriedOkay, I don't understand that, but I'm sure it's because I haven't read everything yet.22:53
cdentefried: if you haven’t got it after some cogitation, ask me again a bit later and I can try to explain it using different words22:54
cdentwe’re making some shortcuts in our explanations that aren’t really helping matters22:54
jaypipescdent: thus my earlier comment that "fuck it..." we will probably end up needing yet another REST API call to placement that takes as a payload some crazypants HOT template|TOSCA YAML|CloudFormation template thing that describes all the various components of the instance that the user wants Nova to atomically claim and spawn.22:54
efriedcdent Thanks - I don't think it's words; it's background.22:54
*** esberglu has quit IRC22:55
cdentjaypipes: i believe that’s where I feel like borrowing dansmith’s gun22:55
jaypipescdent: yup. and the reason I keep bringing up that I hate Nova being an orchestrator.22:55
dansmithcdent: what kind you want? semi-auto? large bore? hollow points?22:55
*** itlinux has quit IRC22:55
* dansmith opens his trenchcoat22:56
cdentdansmith: I’m away for home, so would feel bad for making a mess22:56
cdentfrom22:56
efriedEvery time this happens, though, I go away and study some more, and next time I come back and read the eavesdrop or whatever, I actually get it.  I'm hoping to be good enough by the PTG not to get lost when this stuff is being discussed live.22:56
dansmithcdent: okay so hollow-points then22:56
jaypipesdansmith: shotty. it's got a "good spread".22:56
jaypipesefried: no worries, man. these conversations are important to have.22:56
cfriesen__.700 nitro express22:56
*** cfriesen__ is now known as cfriesen22:56
openstackgerritDan Smith proposed openstack/nova master: Split out the core of the ironic flavor migration  https://review.openstack.org/50102422:56
openstackgerritDan Smith proposed openstack/nova master: Add nova-manage db command for ironic flavor migrations  https://review.openstack.org/50102522:56
dansmithmriedem: dtantsur|afk ^22:57
jaypipesefried: as much as they just inevitably end up reinforcing my annoyance with orchestration.22:57
dansmithneeds a reno but I'm out of brain power and the smoke is cutting my oxygen supply22:57
efriedcdent jaypipes So what we're talking about here is that we made an architectural call to be able to take a chunk of the placement response and just blat it into a (single) allocation request; but if we've made multiple calls to placement we'll have multiple such chunks, and there's currently no semantic for "combining" them into a single allocation request.22:57
efriedDid I get that right?22:58
cdentjaypipes: sadly, somewhere is going to have to have a model for that tosca thing for an instance doign nested rp stuff and it is going to need to land on a compute (so the instance can build correctly). we planned ourselves into this corner, is just the way the world is for now :(22:59
cdentefried: yes, pretty much. we’d need to build that “reassembler” in the scheduler and in a perfect world wouldn’t have to22:59
efriedIn practical terms, the "opaque" allocation request is just a list of things, and we would just append those lists together and be fine.  We just didn't wanna have to do that.23:00
cdentwe now need to be smart in at least two spots23:00
cdentefried: not exactly.23:00
cdentIf we are lisp coders and are talking about this problem, then yes, we building lists23:01
cdentbut the selection of pieces is not just reassambling a sequence23:01
efriedjaypipes cdent I gotta run.  FYI, I've been assembling notes which I eventually planned to link off of the main PTG etherpad once they were in a state where they were sanely readable by someone other than me.  I'm not sure if we've reached that point yet, but... https://etherpad.openstack.org/p/nova-ptg-queens-generic-device-management23:03
cdentthanks for doing that efried, you want annotations in the realm of “nowish” or “laterish”?23:04
efriedcdent I guess any-time-ish is fine, thanks.  I didn't think I was done with it for sure, but I believe I've at least removed most of my horribly-misinformed early thoughts/ideas.23:06
cdent23:06
efriedThanks as always for talking through this with me jaypipes cdent dansmith sean-k-mooney23:07
*** efried is now known as efried_zzz23:07
jaypipesciao23:09
*** thorst has joined #openstack-nova23:11
*** hongbin has quit IRC23:12
*** kairo_ has joined #openstack-nova23:13
*** kairo has quit IRC23:15
*** thorst has quit IRC23:16
*** gouthamr has joined #openstack-nova23:16
*** hongbin has joined #openstack-nova23:21
*** thorst has joined #openstack-nova23:21
*** hongbin has quit IRC23:22
*** thorst has quit IRC23:25
*** catintheroof has joined #openstack-nova23:26
gmannmriedem, +1, i overlooked23:28
gmannmriedem, can we have a specless BP for index schema chages - https://review.openstack.org/#/c/500347/ https://review.openstack.org/#/c/499091/ etc23:30
gmannmriedem, that will be basically continuation of this - https://blueprints.launchpad.net/nova/+spec/consistent-query-parameters-validation23:30
gmannit will be easy to track and capture any accidental API changes23:30
*** catintheroof has quit IRC23:31
gmannmriedem, created one, check if it looks fine - https://blueprints.launchpad.net/nova/+spec/json-schema-validation-for-index-query-param23:37
gmannalex_xu, ^^23:37
alex_xugmann: thanks, that's great23:39
*** kairo_ has quit IRC23:40
*** markvoelker has quit IRC23:43
*** kairo has joined #openstack-nova23:44
*** crushil has quit IRC23:46
openstackgerritChris Dent proposed openstack/nova-specs master: Add a spec for POST /allocations in placement  https://review.openstack.org/49925923:47
*** suresh12 has joined #openstack-nova23:48
openstackgerritDan Smith proposed openstack/nova master: Add nova-manage db command for ironic flavor migrations  https://review.openstack.org/50102523:50
openstackgerritMerged openstack/nova master: Add recreate test for forced host evacuate not setting dest allocations  https://review.openstack.org/49967823:51
*** crushil has joined #openstack-nova23:52
*** artom has joined #openstack-nova23:56

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