Friday, 2019-10-04

*** brinzhang has joined #openstack-meeting00:01
*** tetsuro has joined #openstack-meeting00:15
*** gyee has quit IRC00:21
*** yamamoto has joined #openstack-meeting00:23
*** yamamoto has quit IRC00:27
*** markvoelker has joined #openstack-meeting00:31
*** jbadiapa has joined #openstack-meeting00:33
*** markvoelker has quit IRC00:35
*** yamamoto has joined #openstack-meeting00:47
*** armax has joined #openstack-meeting00:48
*** brinzhang_ has joined #openstack-meeting01:00
*** brinzhang has quit IRC01:04
*** panda|off has quit IRC01:12
*** panda has joined #openstack-meeting01:12
*** tetsuro has quit IRC01:19
*** rfolco has quit IRC01:19
*** brinzhang has joined #openstack-meeting01:25
*** markvoelker has joined #openstack-meeting01:26
*** dklyle has quit IRC01:27
*** rfolco has joined #openstack-meeting01:27
*** _pewp_ has quit IRC01:28
*** dklyle has joined #openstack-meeting01:28
*** _pewp_ has joined #openstack-meeting01:29
*** brinzhang_ has quit IRC01:29
*** d34dh0r53 has quit IRC01:30
*** aloga has quit IRC01:30
*** markvoelker has quit IRC01:30
*** aloga has joined #openstack-meeting01:31
*** d34dh0r53 has joined #openstack-meeting01:32
*** yamamoto has quit IRC01:42
*** markvoelker has joined #openstack-meeting01:54
*** brinzhang_ has joined #openstack-meeting01:54
*** brinzhang has quit IRC01:58
*** markvoelker has quit IRC01:58
*** markvoelker has joined #openstack-meeting02:05
*** whoami-rajat has joined #openstack-meeting02:09
*** jamesmcarthur has joined #openstack-meeting02:13
*** yamamoto has joined #openstack-meeting02:13
*** yamamoto has quit IRC02:19
*** yamamoto has joined #openstack-meeting02:20
*** ricolin has joined #openstack-meeting02:27
*** donghao has joined #openstack-meeting02:31
*** markvoelker has quit IRC02:35
*** donghao has quit IRC02:36
*** rfolco has quit IRC02:45
*** markvoelker has joined #openstack-meeting03:06
*** dviroel has quit IRC03:15
*** rbudden has joined #openstack-meeting03:27
*** jamesmcarthur has quit IRC03:34
*** jamesmcarthur has joined #openstack-meeting03:35
*** markvoelker has quit IRC03:36
*** markvoelker has joined #openstack-meeting03:36
*** jamesmcarthur has quit IRC03:39
*** artom has quit IRC03:51
*** jamesmcarthur has joined #openstack-meeting04:05
*** markvoelker has quit IRC04:07
*** jamesmcarthur has quit IRC04:12
*** ekcs has quit IRC04:14
*** gouthamr has quit IRC04:15
*** gouthamr has joined #openstack-meeting04:16
*** donghao has joined #openstack-meeting04:33
*** markvoelker has joined #openstack-meeting04:35
*** donghao has quit IRC04:37
*** markvoelker has quit IRC04:39
*** jbadiapa has quit IRC04:52
*** rbudden has quit IRC04:55
*** Luzi has joined #openstack-meeting04:58
*** jamesmcarthur has joined #openstack-meeting05:08
*** tetsuro has joined #openstack-meeting05:11
*** jamesmcarthur has quit IRC05:13
*** markvoelker has joined #openstack-meeting05:19
*** markvoelker has quit IRC05:24
*** markvoelker has joined #openstack-meeting05:28
*** markvoelker has quit IRC05:33
*** tssurya has quit IRC05:36
*** markvoelker has joined #openstack-meeting05:37
*** markvoelker has quit IRC05:42
*** markvoelker has joined #openstack-meeting05:47
*** markvoelker has quit IRC05:51
*** markvoelker has joined #openstack-meeting05:56
*** links has joined #openstack-meeting05:57
*** markvoelker has quit IRC06:01
*** markvoelker has joined #openstack-meeting06:05
*** jamesmcarthur has joined #openstack-meeting06:09
*** markvoelker has quit IRC06:10
*** markvoelker has joined #openstack-meeting06:14
*** jamesmcarthur has quit IRC06:15
*** markvoelker has quit IRC06:19
*** markvoelker has joined #openstack-meeting06:23
*** markvoelker has quit IRC06:28
*** markvoelker has joined #openstack-meeting06:33
*** donghao has joined #openstack-meeting06:35
*** slaweq has joined #openstack-meeting06:37
*** markvoelker has quit IRC06:38
*** donghao has quit IRC06:40
*** markvoelker has joined #openstack-meeting06:42
*** markvoelker has quit IRC06:46
*** brinzhang has joined #openstack-meeting06:50
*** markvoelker has joined #openstack-meeting06:52
*** brinzhang_ has quit IRC06:53
*** markvoelker has quit IRC06:56
*** markvoelker has joined #openstack-meeting07:01
*** ttsiouts has joined #openstack-meeting07:03
*** markvoelker has quit IRC07:06
*** tetsuro has quit IRC07:09
*** brinzhang_ has joined #openstack-meeting07:10
*** rpittau|afk is now known as rpittau07:10
*** markvoelker has joined #openstack-meeting07:11
*** jamesmcarthur has joined #openstack-meeting07:11
*** brinzhang has quit IRC07:13
*** pcaruana has joined #openstack-meeting07:15
*** markvoelker has quit IRC07:15
*** jamesmcarthur has quit IRC07:16
*** markvoelker has joined #openstack-meeting07:20
*** links has quit IRC07:20
*** e0ne has joined #openstack-meeting07:22
*** e0ne has quit IRC07:22
*** markvoelker has quit IRC07:24
*** links has joined #openstack-meeting07:25
*** ttsiouts has quit IRC07:26
*** ttsiouts has joined #openstack-meeting07:26
*** ttsiouts has quit IRC07:31
*** links has quit IRC07:34
*** donghao has joined #openstack-meeting07:36
*** links has joined #openstack-meeting07:36
*** donghao has quit IRC07:41
*** markvoelker has joined #openstack-meeting07:47
*** baojg has joined #openstack-meeting07:50
*** brinzhang has joined #openstack-meeting07:51
*** markvoelker has quit IRC07:52
*** hyunsikyang has joined #openstack-meeting07:53
*** brinzhang_ has quit IRC07:55
*** ttsiouts has joined #openstack-meeting07:56
*** hyunsikyang__ has quit IRC07:57
*** markvoelker has joined #openstack-meeting07:57
*** hyunsikyang__ has joined #openstack-meeting07:58
*** hyunsikyang has quit IRC07:58
*** markvoelker has quit IRC08:01
*** brinzhang has quit IRC08:09
*** ttsiouts has quit IRC08:10
*** ttsiouts has joined #openstack-meeting08:11
*** jamesmcarthur has joined #openstack-meeting08:13
*** ttsiouts_ has joined #openstack-meeting08:14
*** ttsiouts has quit IRC08:15
*** rcernin has quit IRC08:15
*** markvoelker has joined #openstack-meeting08:15
*** baojg has quit IRC08:17
*** jamesmcarthur has quit IRC08:18
*** markvoelker has quit IRC08:20
*** tssurya has joined #openstack-meeting08:21
*** zbr is now known as zbr|ruck08:23
*** lpetrut has joined #openstack-meeting08:25
*** tetsuro has joined #openstack-meeting08:31
*** yamamoto has quit IRC08:35
*** ociuhandu has joined #openstack-meeting08:37
*** yamamoto has joined #openstack-meeting08:37
*** hyunsikyang has joined #openstack-meeting08:41
*** markvoelker has joined #openstack-meeting08:43
*** hyunsikyang__ has quit IRC08:45
*** markvoelker has quit IRC08:48
*** ociuhandu has quit IRC08:54
*** ociuhandu has joined #openstack-meeting08:54
*** ociuhandu has quit IRC08:59
*** ociuhandu has joined #openstack-meeting08:59
*** e0ne has joined #openstack-meeting08:59
*** markvoelker has joined #openstack-meeting09:02
*** markvoelker has quit IRC09:07
*** jamesmcarthur has joined #openstack-meeting09:14
*** jamesmcarthur has quit IRC09:19
*** markvoelker has joined #openstack-meeting09:21
*** rfolco has joined #openstack-meeting09:23
*** panda is now known as panda|bbl09:25
*** markvoelker has quit IRC09:25
*** yamamoto has quit IRC09:26
*** yamamoto has joined #openstack-meeting09:30
*** yamamoto has quit IRC09:35
*** markvoelker has joined #openstack-meeting09:39
*** donghao has joined #openstack-meeting09:39
*** yamamoto has joined #openstack-meeting09:41
*** jbadiapa has joined #openstack-meeting09:42
*** SergeyLukjanov has quit IRC09:44
*** donghao has quit IRC09:45
*** markvoelker has quit IRC09:45
*** SergeyLukjanov has joined #openstack-meeting09:51
*** markvoelker has joined #openstack-meeting09:58
*** markvoelker has quit IRC10:02
*** mugsie has quit IRC10:03
*** mugsie has joined #openstack-meeting10:05
*** markvoelker has joined #openstack-meeting10:07
*** yamamoto has quit IRC10:08
*** markvoelker has quit IRC10:12
*** yamamoto has joined #openstack-meeting10:12
*** ttsiouts_ has quit IRC10:12
*** ttsiouts has joined #openstack-meeting10:13
*** yamamoto has quit IRC10:13
*** jamesmcarthur has joined #openstack-meeting10:15
*** ttsiouts has quit IRC10:17
*** jamesmcarthur has quit IRC10:19
*** ociuhandu has quit IRC10:22
*** ociuhandu has joined #openstack-meeting10:22
*** markvoelker has joined #openstack-meeting10:35
*** markvoelker has quit IRC10:39
*** panda|bbl is now known as panda10:39
*** yamamoto has joined #openstack-meeting10:41
*** yamamoto has quit IRC10:43
*** jamesmcarthur has joined #openstack-meeting10:47
*** ociuhandu has quit IRC10:47
*** ociuhandu has joined #openstack-meeting10:48
*** jamesmcarthur has quit IRC10:51
*** ociuhandu has quit IRC10:52
*** ociuhandu has joined #openstack-meeting10:52
*** markvoelker has joined #openstack-meeting10:53
*** yamamoto has joined #openstack-meeting10:54
*** markvoelker has quit IRC10:57
*** yamamoto has quit IRC11:00
*** markvoelker has joined #openstack-meeting11:02
*** yamamoto has joined #openstack-meeting11:03
*** markvoelker has quit IRC11:06
*** ociuhandu has quit IRC11:07
*** ociuhandu has joined #openstack-meeting11:08
*** jbadiapa has quit IRC11:09
*** markvoelker has joined #openstack-meeting11:11
*** ttsiouts has joined #openstack-meeting11:12
*** ociuhandu has quit IRC11:12
*** ociuhandu has joined #openstack-meeting11:14
*** zbr|ruck is now known as zbr|lunch11:15
*** markvoelker has quit IRC11:16
*** ociuhandu has quit IRC11:18
*** markvoelker has joined #openstack-meeting11:21
*** ociuhandu has joined #openstack-meeting11:25
*** markvoelker has quit IRC11:25
*** yamamoto has quit IRC11:36
*** markvoelker has joined #openstack-meeting11:39
*** panda is now known as panda|eat11:43
*** markvoelker has quit IRC11:44
*** jamesmcarthur has joined #openstack-meeting11:48
*** markvoelker has joined #openstack-meeting11:48
*** markvoelker has quit IRC11:49
*** markvoelker has joined #openstack-meeting11:49
*** hyunsikyang__ has joined #openstack-meeting11:50
*** yamamoto has joined #openstack-meeting11:51
*** EmilienM has quit IRC11:53
*** jamesmcarthur has quit IRC11:53
*** EmilienM has joined #openstack-meeting11:54
*** hyunsikyang has quit IRC11:54
*** ociuhandu has quit IRC11:55
*** ociuhandu has joined #openstack-meeting11:57
*** ociuhandu has quit IRC11:59
*** ociuhandu has joined #openstack-meeting11:59
*** yamamoto has quit IRC12:00
*** enriquetaso has joined #openstack-meeting12:01
*** ociuhandu has quit IRC12:03
*** ociuhandu has joined #openstack-meeting12:04
*** kukacz has joined #openstack-meeting12:09
*** ociuhandu has quit IRC12:09
*** lseki has joined #openstack-meeting12:14
*** jamesmcarthur has joined #openstack-meeting12:15
*** dviroel has joined #openstack-meeting12:16
*** rfolco has quit IRC12:24
*** rfolco has joined #openstack-meeting12:25
*** ileixe_ has joined #openstack-meeting12:29
*** yamamoto has joined #openstack-meeting12:30
*** ociuhandu has joined #openstack-meeting12:34
*** panda|eat is now known as panda12:37
*** whoami-rajat has quit IRC12:38
*** ociuhandu has quit IRC12:40
*** markvoelker has quit IRC12:41
*** whoami-rajat has joined #openstack-meeting12:42
*** kukacz has quit IRC12:44
*** kukacz has joined #openstack-meeting12:45
*** jamesmcarthur has quit IRC12:47
*** jamesmcarthur has joined #openstack-meeting12:47
*** yamamoto has quit IRC12:50
*** vesper11 has quit IRC12:53
*** vesper11 has joined #openstack-meeting12:54
*** Luzi has quit IRC12:55
*** markvoelker has joined #openstack-meeting12:58
*** vesper11 has quit IRC12:59
*** ociuhandu has joined #openstack-meeting13:03
*** ociuhandu has quit IRC13:09
*** psachin has joined #openstack-meeting13:10
*** hyunsikyang has joined #openstack-meeting13:10
*** hyunsikyang__ has quit IRC13:14
*** raildo has joined #openstack-meeting13:17
*** mriedem has joined #openstack-meeting13:18
*** zbr|lunch is now known as zbr|ruck13:25
*** yamamoto has joined #openstack-meeting13:26
*** vesper11 has joined #openstack-meeting13:27
*** vesper11 has quit IRC13:31
*** vesper11 has joined #openstack-meeting13:32
*** pescobar has quit IRC13:35
*** pescobar has joined #openstack-meeting13:36
*** yamamoto has quit IRC13:36
*** ttsiouts has quit IRC13:44
*** ttsiouts has joined #openstack-meeting13:45
*** ttsiouts has quit IRC13:46
*** ttsiouts has joined #openstack-meeting13:46
*** mlavalle has joined #openstack-meeting13:56
*** yamamoto has joined #openstack-meeting13:57
*** gmann_afk is now known as gmann13:58
*** gregoiremahe has joined #openstack-meeting13:59
gregoiremaheHello :) Is that here neutron-driver meeting ?13:59
mlavallegregoiremahe: yes, alothough it hasn't started13:59
mlavallehang on 1 minute13:59
gregoiremaheOk, good, just wanted to know if I was at the right place14:00
slaweq#startmeeting neutron_drivers14:00
openstackMeeting started Fri Oct  4 14:00:59 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_drivers)"14:01
openstackThe meeting name has been set to 'neutron_drivers'14:01
mlavalleo/14:01
yamamotohi14:01
slaweqhi14:01
gregoiremaheHello14:01
slaweqhi gregoiremahe14:01
amotokihi14:02
slaweqok, I think we have quorum now so we can start :)14:02
*** ociuhandu has joined #openstack-meeting14:02
slaweq#topic RFEs14:03
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)"14:03
slaweqfirst on my list is one from last week:14:03
slaweqhttps://bugs.launchpad.net/neutron/+bug/184321114:03
openstackLaunchpad bug 1843211 in neutron "network-ip-availabilities' result is not correct when the subnet has no allocation-pool" [Wishlist,In progress] - Assigned to yangjianfeng (yangjianfeng)14:03
slaweqthx mlavalle for Your input about that14:03
*** davidsha has joined #openstack-meeting14:03
njohnstono/14:04
slaweqand thx amotoki for Your comment there too14:05
ileixe_o/14:06
slaweqpersonally I agree with Your comments - I first though about this as a bug because IMO we shouldn't use one attribute to provide 2 different informations conditionaly14:07
slaweqbut if You are saying that it is like that by design and we should keep it like that, than I'm ok with this14:07
slaweqso IMO we should just update api-ref information about "total_ips" to reflect this conditional change of meaning for this attribute14:08
mlavallewell, if you look at the code, that was clearly the intent of the developers and revieiwers who approved it14:08
slaweqmlavalle: yes, I saw Your links :)14:08
slaweqIMO it's more like "broken by design" but I can definitely live with it :)14:08
amotokiI see two things: (1) the current API behavior looks intended (2) the current API response looks confusing and there is a room to add more information to provide detail information.14:08
*** munimeha1 has joined #openstack-meeting14:09
amotokiso I agree not to change the current behavior based on (1).14:09
mlavalleyeah, even though the code is doing its original intent, I agree that that intent is a little confusing14:09
amotokiwhat do you think about adding more attributes?14:09
slaweqamotoki: with change proposed by You in last comment we would change current behaviour of "total_ips" value, right?14:10
slaweqso we would do something what mlavalle didn't want to do14:10
mlavallein principle I'm open to it, but to be honest, I haven't seen yet a use case properly articulated14:10
amotokislaweq: what I think is not to touch "total_ips".14:10
amotokiI am thinking to introduce new attributes in the response.14:11
njohnstonamotoki++ yes that is the only way to deal with developers that depend on the current behavior; Hyrum's Law strikes again14:11
slaweqamotoki: but do You still want to keep current behaviour of total_ips, so if there is allocation pool it will have number of ips from allocation pools, and if not, number of ips based on cidr?14:11
amotokitotal_ips keep the current conditional behavior. subnet_total_ips and allocation_pools_total_ips can provide more information.14:13
slaweqamotoki: because IIUC Your comment, first 2 proposed values from Your comment are in fact now covered by "total_ips", depends if allocation pools exists or not in subnet14:13
slaweqahh, ok14:13
amotokiif allocation_pools exist total_ips will equal to allocation_pools_total_ips14:13
slaweqamotoki: I understand now14:13
amotoki:)14:14
slaweqso You propose to keep total_ips as it is now, and add 2 new "total_ips_something" attributes14:14
slaweqcorrect?14:14
amotokiyes (on "total_ips" things)14:14
slaweqok, IMO it's very good idea14:15
amotokiIf we go to this route, "used_ips" can be improved too.14:15
slaweqyes, I agree14:16
*** amorin has joined #openstack-meeting14:16
slaweqso in fact we would need to add 3 new attributes according to Your proposal:14:16
slaweq"subnet_total_ips"14:17
slaweq"allocation_pool_total_ips"14:17
slaweqand14:17
slaweq"allocation_pool_used_ips"14:17
amotokiyes14:17
slaweqand we already have "used_ips" which is something like "subnet_used_ips"14:17
slaweqI'm ok with this proposal14:18
slaweqwhat do You all things?14:18
slaweq*thinks14:18
amotokiI am not sure we need "subnet_used_ips". if we need more consistent naming of attributes, "subnet_used_ips" makes sense even though it is dupicate to "used_ips".14:18
slaweqyes, I also though that maybe we can add "subnet_used_ips" as duplicate of "used_ips" just to have more consistent naming of new attributes14:19
mlavalleso, "total_ips" and "used_ips" refer to the entire network, eight?14:19
mlavalleright^^^^14:19
slaweqmlavalle: not exactly14:19
slaweqmlavalle: total_ips would still be conditional14:20
slaweqas it is now14:20
mlavalleyeah, I understand that, but refer to the aggregation of the subnets in the network14:20
mlavallewhether they have allocation pools or not14:20
amotokiah.. good point14:21
slaweqyes, but I think that new attributes would also refer to aggregation of subnets in the network but would be non conditional14:21
mlavalleI am looking at these lines: https://github.com/openstack/neutron/blob/92f7484d2a59f0ee900eca7280f92f6c1c0de35e/neutron/db/network_ip_availability_db.py#L110-L11114:22
slaweqthis whole extension is to indicate number of IPs in the network, so it aggregate values from subnets14:22
mlavalleso yes, we are saying the same thing14:22
mlavalleso say a network mixes subnets with allocation pools and no allocation pools14:23
slaweqyes14:24
mlavallethe current behavior captures correctly the total-ips and the used-ips14:24
mlavalleat the network level14:24
amotokimlavalle: yes, as long as IP address outside of allocation pools are not used14:25
mlavallenow, if we want to do this at the subnet level, I think it is a completely different extension14:25
mlavalleotherwise we are going to make a mess of this extension14:25
*** ricolin_ has joined #openstack-meeting14:25
slaweqbut do we want to do it "per subnet"? I thought that those new values would be also "per network"14:26
amotokimlavalle: what I think is to add new attributes both to network-level and subnet-level (as a new API extension)14:26
*** ricolin has quit IRC14:26
mlavalleand I'm ok with that. do we have the use case to justify that new extension, though?14:27
mlavallehere's how I see the current situation:14:27
slaweqso, to be clear, do You want to have now new API like:14:28
slaweq/v2.0/network-ip-availabilities/{subnet_id}14:28
slaweqalso?14:28
slaweqwhich will provide those ip availabilities info per subnet14:28
mlavalle1) We have an extension that is slightly confusing because, IMO, after looking at the history, it was developed to suit the needs of a particluar operator14:28
mlavalle2) Since current extension is slightly confusing, we can think of ways to improve it here14:29
mlavalle3) But if we lack the evidence of a strong use case, aren't we risking to add to the confusion in the enitre "ip availability realm", whether at the network or the subnet level14:30
mlavalle?14:30
slaweqI'm really not sure about this ip availaibility per subnet - what would be the use case for that?14:30
mlavalleI am not opposing improving the API, but I would like to do it based on a solid use case14:31
amotokion 3), at least I know a few cases where operators implemented custom tools due to the confusing behavior of the current API.14:31
slaweqPer network it may tell operator that he is going to be out of IP addresses which users can use so should add new subnet to the network14:31
mlavallewhich so far this RFE hasn't articulated14:31
amotokiin that cases, the reason was due to "used_ips". I can add an RFE on that if you want.14:31
mlavalleamotoki: if you have the operator level evidence, I trust you. Let's just be careful articulating it14:32
amotokimlavalle: okay, let me add cases I know on "used_ips".14:32
yamamotoamotoki: does the tool query db directly?14:32
amotokiyamamoto: no, it was thru the API but we need more query on API.14:33
amotokilike listing ports :p14:33
mlavallewhat if we start a spec and "cook it" slowly all the way to "well done" with the community assistance?14:35
slaweqmlavalle +114:35
*** jbadiapa has joined #openstack-meeting14:35
amotoki+114:35
slaweqI thnink that this becoming more and more "complicated" :)14:35
slaweqso spec would be good probably14:35
njohnston+114:36
yamamoto+114:36
slaweqmlavalle: will You propose such spec?14:36
mlavalleyeah I can push an inital patch. Not necessarilly by neext week, but soon14:36
slaweqmlavalle: great, thx14:37
slaweqso I will write comment with summary of our discussion about it in bug report14:37
slaweqok, I think we can move on to the next one on the list14:37
mlavallein the comment, ask submitter for a better articulated use case14:37
slaweqmlavalle: sure, I will ask14:38
mlavallewe want to know the why, not the how14:38
slaweqyes, I agree14:38
slaweqhow is quite easy in this case IMO :)14:38
mlavalleyeah, just read the damn code14:38
slaweqok, next rfe now :)14:38
slaweqhttps://bugs.launchpad.net/neutron/+bug/184321814:38
openstackLaunchpad bug 1843218 in neutron "[RFE] allow to create record on default zone from tenants" [Wishlist,Triaged] - Assigned to Gregoire Mahe (gregoiremahe)14:38
slaweqgregoiremahe: Your turn :)14:39
gregoiremaheOk, so today at OVH we have many users, and we want to enable default zone for them14:40
gregoiremaheSo basically, we just want to parse domain setup on network, and replace <tenantid> by the user tenant14:41
mlavalleI have interacted with gregoiremahe over the past few weeks over this RFE14:41
mlavalleand it identifies correctly, IMO, a gap in the current DNS integration extension14:42
mlavallethe current functionality was geared to tenants who have their onw networks14:43
mlavalleand want to publish DNS records of ports and VMs in that tennt network14:43
mlavallegregoiremahe's use case referes to a ituation where the network is shared by all the users / tenants14:44
mlavalleone big network or a limited number of them14:44
mlavalleright gregoiremahe?14:44
gregoiremaheyes, that's right, so we would like to setup <tenantid>.defaultzone.com. on the network with openstack network set --dns-domain14:45
*** donghao has joined #openstack-meeting14:45
mlavalle--dns_domain == defaulzone.com, right?14:45
gregoiremaheeither this, either <tenantid>.defaultzone.com., and just parsing and replace <tenantid> in dns integration14:46
gregoiremaheThat's will create a better flexibility to do so14:46
mlavallein fact, at my employer, we have a downstream implementation that does just that14:46
mlavallefor example, my zone is 'mlavalle01-home.bf2.ows.oath.cloud.'14:47
mlavalleand the dns_domain attribute of the share network is 'bf2.ows.oath.cloud.'14:48
mlavalleso I've seen it work and makes sense to me :-)14:48
amotokido you mean to pass some format string as "dns_domain" like <tenantid>.example.net?14:48
amotokior is <tenantid> part added automatically?14:49
*** ricolin_ has quit IRC14:49
amotokianyway the use case makes sense to me.14:49
gregoiremaheamotoki : I implemented the fact to have <tenantid> in dns_domain to replace by the tenantid, but both might be okay14:49
slaweqthis makes sense for me too14:50
slaweqone question14:50
*** donghao has quit IRC14:50
slaweqif You want to implement replacement of <tenant_id> with tenant_id, why not add also some other "keywords" like "user_id", or "user_name" for example?14:50
*** ociuhandu has quit IRC14:51
gregoiremaheYea, I already though about that, but the tenantid variable was directly accessible, so I first implemented a feature this way14:51
*** ociuhandu has joined #openstack-meeting14:52
slaweqahh, ok14:52
slaweqother values would require api calls to e.g. keysone14:52
gregoiremaheyep right14:52
amotokiperhaps we can support replacements for fields which are availabel in neutron.context.14:52
slaweqok, so <tenant_id> as for now makes sense14:52
slaweqand we can always extend this list of "keywords" in the future if that will be needed14:53
yamamotomlavalle: where is the "mlavalle01-home" part?14:53
yamamotowhat's14:53
mlavallegregoiremahe: fwiw, this is an example of the A record of one of my VMs: 8e871e12.mlavalle01-home.bf2.ows.oath.cloud.14:53
*** bnemec is now known as beekneemech14:54
mlavalleyamamoto: mlavalle01-home is associated to my certificate14:54
gregoiremahemlavalle : And what is 8e871e12 ? Is that your server name ?14:54
mlavallex.509 certificate that we use internally to authenticate14:55
mlavalleand yes 8e871e12 is just a VM name14:55
*** ociuhandu has quit IRC14:56
mlavallesince this is for upstream, the 'mlavalle01-home' may be changed to the project id14:56
mlavalleor tenant id, whatever your naming preference is14:56
amotokiI think we can use these keywords https://github.com/openstack/neutron-lib/blob/master/neutron_lib/context.py#L74-L8514:57
amotokithey looks enough for our need discussed here.14:57
slaweqamotoki: ohh, if we have all of that available in context, that would be nice IMO :)14:57
*** armstrong has joined #openstack-meeting14:58
*** artom has joined #openstack-meeting14:58
slaweqanyway, we are almost on time with this meeting14:58
slaweqIMO we can approve this RFE14:59
mlavalle+114:59
amotokiit looks good to me to approve this and the next step would be to write a spec on this14:59
*** armstrong has quit IRC14:59
mlavalleyeap, a spec would be good14:59
slaweqwith either using only project_id for now, or using all those keywords pointed by amotoki if that is possible to get in extension14:59
yamamoto+1 to have a spec14:59
slaweqok, so let's approve that rfe for now15:00
*** links has quit IRC15:00
slaweqgregoiremahe: will You write spec for this?15:00
amotokijust in time :)15:00
slaweqok, thx for attending and have a great weekend15:00
yamamotogood night15:00
gregoiremaheYep, just need to know how to do this and what format cause that will be my first one15:00
slaweqwe have to finish for today15:00
njohnston\o15:00
slaweq#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
slaweqo/15:00
openstackMeeting ended Fri Oct  4 15:00:41 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-10-04-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-10-04-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-10-04-14.00.log.html15:00
slaweqgregoiremahe: I will write summary in comment and will link You some examples of specs15:01
mlavalleo/15:01
*** ileixe_ has quit IRC15:01
gregoiremaheslaweq : Ok good, thanks :)15:01
*** mlavalle has left #openstack-meeting15:02
*** ociuhandu has joined #openstack-meeting15:04
*** tidwellr has joined #openstack-meeting15:07
*** jamesmcarthur has quit IRC15:09
*** ociuhandu has quit IRC15:09
*** jamesmcarthur has joined #openstack-meeting15:11
*** donnyd is now known as donnyd_afk15:19
*** gyee has joined #openstack-meeting15:22
*** mattw4 has joined #openstack-meeting15:22
*** ociuhandu has joined #openstack-meeting15:23
*** kopecmartin is now known as kopecmartin|off15:30
*** dviroel has quit IRC15:36
*** ttsiouts has quit IRC15:37
*** ttsiouts has joined #openstack-meeting15:38
*** ttsiouts has quit IRC15:42
*** tssurya has quit IRC15:44
*** rpittau is now known as rpittau|afk15:45
*** ociuhandu has quit IRC15:47
*** ociuhandu has joined #openstack-meeting15:48
*** macz has joined #openstack-meeting15:55
*** ociuhandu has quit IRC15:56
*** ekcs has joined #openstack-meeting15:58
*** donnyd_afk is now known as donnyd16:01
*** cmurphy is now known as cmorpheus16:01
*** dviroel has joined #openstack-meeting16:03
*** jamesmcarthur has quit IRC16:06
*** jamesmcarthur has joined #openstack-meeting16:11
*** mriedem is now known as mriedem_lunch16:14
*** yamamoto has quit IRC16:15
*** jbadiapa has quit IRC16:21
*** davidsha has quit IRC16:28
*** sapna_ has joined #openstack-meeting16:29
*** e0ne has quit IRC16:32
*** links has joined #openstack-meeting16:38
*** zbr|ruck has quit IRC16:39
*** lpetrut has quit IRC16:41
*** sapna_ has quit IRC16:46
*** donghao has joined #openstack-meeting16:50
*** zbr has joined #openstack-meeting16:51
*** yamamoto has joined #openstack-meeting16:51
*** links has quit IRC16:53
*** donghao has quit IRC16:55
*** yamamoto has quit IRC17:02
*** ociuhandu has joined #openstack-meeting17:09
*** lpetrut has joined #openstack-meeting17:15
*** psachin has quit IRC17:36
*** lpetrut has quit IRC17:49
*** mriedem_lunch is now known as mriedem17:51
*** ociuhandu has quit IRC18:08
*** ociuhandu has joined #openstack-meeting18:08
*** rfolco is now known as rfolco|bbl18:12
*** jamesmcarthur has quit IRC18:25
*** jamesmcarthur has joined #openstack-meeting18:40
*** pcaruana has quit IRC18:51
*** ociuhandu has quit IRC18:51
*** ociuhandu has joined #openstack-meeting18:52
*** donghao has joined #openstack-meeting18:53
*** ociuhandu has quit IRC18:56
*** donghao has quit IRC18:57
*** jamesmcarthur has quit IRC19:14
*** panda is now known as panda|off19:38
*** munimeha1 has quit IRC19:46
*** zbr has quit IRC19:46
*** ekcs has quit IRC19:46
*** e0ne has joined #openstack-meeting19:50
*** thgcorrea has joined #openstack-meeting19:53
*** donghao has joined #openstack-meeting19:54
*** markvoelker has quit IRC19:55
*** donghao has quit IRC19:59
*** e0ne has quit IRC20:09
*** artom has quit IRC20:17
*** EmilienM is now known as EvilienM20:18
*** EvilienM is now known as containerizes_hi20:19
*** containerizes_hi is now known as containerized20:19
*** containerized is now known as EvilienM20:19
*** jamesmcarthur has joined #openstack-meeting20:33
*** jamesmcarthur has quit IRC20:44
*** jamesmcarthur has joined #openstack-meeting20:46
*** raildo has quit IRC20:56
*** slaweq has quit IRC20:59
*** njohnston is now known as njohnston|off21:01
*** enriquetaso has quit IRC21:01
*** ekcs has joined #openstack-meeting21:07
*** whoami-rajat has quit IRC21:18
*** jamesmcarthur has quit IRC21:34
*** mriedem has quit IRC21:47
*** jbadiapa has joined #openstack-meeting21:50
*** EvilienM is now known as EmilienM21:52
*** slaweq has joined #openstack-meeting22:11
*** slaweq has quit IRC22:16
*** mattw4 has quit IRC22:53
*** ekcs has quit IRC22:53
*** rfolco|bbl has quit IRC22:54
*** macz has quit IRC22:59
*** yamamoto has joined #openstack-meeting23:00
*** yamamoto has quit IRC23:05
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:16
*** ekcs has joined #openstack-meeting23:19
*** ekcs has quit IRC23:29

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