Friday, 2018-09-28

*** strigazi has quit IRC00:01
*** vabada has quit IRC00:01
*** strigazi has joined #openstack-meeting00:02
*** vabada has joined #openstack-meeting00:02
*** bobh has quit IRC00:04
*** erlon has quit IRC00:19
*** yamamoto has joined #openstack-meeting00:21
*** jamesmcarthur has quit IRC00:28
*** jamesmcarthur has joined #openstack-meeting00:29
*** bobh has joined #openstack-meeting00:33
*** jamesmcarthur has quit IRC00:34
*** longkb has joined #openstack-meeting00:34
*** erlon has joined #openstack-meeting00:36
*** gyee has quit IRC00:51
*** jamesmcarthur has joined #openstack-meeting00:55
*** jamesmcarthur has quit IRC00:59
*** diablo_rojo has quit IRC01:05
*** bobh has quit IRC01:10
*** felipemonteiro has joined #openstack-meeting01:15
*** erlon has quit IRC01:16
*** jamesmcarthur has joined #openstack-meeting01:28
*** bobh has joined #openstack-meeting01:31
*** dmacpher_ has joined #openstack-meeting01:33
*** dmacpher has quit IRC01:35
litao_whoami-rajat: thanks01:37
*** bobh has quit IRC01:42
*** bobh has joined #openstack-meeting01:49
*** bobh has quit IRC01:53
*** mschuppert has joined #openstack-meeting01:57
*** cloudrancher has quit IRC02:02
*** cloudrancher has joined #openstack-meeting02:03
*** yamamoto has quit IRC02:16
*** hongbin has joined #openstack-meeting02:20
*** tetsuro has joined #openstack-meeting02:45
*** imacdonn has quit IRC02:51
*** imacdonn has joined #openstack-meeting02:51
*** felipemonteiro has quit IRC03:00
*** yamamoto has joined #openstack-meeting03:24
*** psachin has joined #openstack-meeting03:29
*** hongbin has quit IRC03:38
*** akhil_jain has joined #openstack-meeting03:43
*** mbindlish has joined #openstack-meeting03:48
*** ekcs has joined #openstack-meeting03:49
*** yamamoto has quit IRC03:50
*** dkushwaha has joined #openstack-meeting03:52
ekcs#startmeeting congressteammeeting04:01
openstackMeeting started Fri Sep 28 04:01:04 2018 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: congressteammeeting)"04:01
openstackThe meeting name has been set to 'congressteammeeting'04:01
ekcshi all! topics kept here as usual. feel free to add your topics!04:02
*** njohnston has quit IRC04:02
akhil_jainekcs: Hi!04:02
ekcshi akhil_jain !04:03
akhil_jainI would like to introduce dkushwaha: PTL of tacker and mbindlish: active contributor in QA04:03
ekcshi dkushwaha !04:03
ekcshi mbindlish !04:03
ekcsbig thanks for joining us at this time.04:04
akhil_jainekcs:  So as discussed they will help us understand tacker-monasca-congress usecase04:06
*** Nel1x has quit IRC04:07
dkushwahaThanks akhil_jain ekcs04:07
dkushwahaLet me explain our use case.04:07
ekcsthat’s awesome. thanks akhil_jain ! yes definitely excited to learn more and see where I can help.04:07
dkushwahaekcs, please see
dkushwahaAs per the OPNFV Doctor fault management framework04:08
ekcsgot it!04:08
dkushwahawe are using congress as inspector, monasca as monitor, and Tacker as VNF manager04:08
dkushwahaFor automatic corrective actions depending on the monitor data evaluation Tacker execution driver needs to be supported in congress.04:09
ekcsthat makes sense.04:10
dkushwahawhich will poll VNF data from Tacker and can execute policy04:10
ekcsI see.04:11
ekcsSo here Congress’s role is to poll tacker data, combine with monasca webhook data, then send something back to tacker is the form of executions?04:12
dkushwahaAlthough, on Tacker side, we have one gap. We needs to have an interface which can list VNFs per comupte node(which is currently missing in Tacker side)04:12
dkushwahaekcs, yes04:12
ekcsgot it.04:14
ekcsso just to help me get a more concrete sense, what’s a typical action congress may execute on tacker?04:14
ekcsin these scenarios?04:14
dkushwahaekcs, the corrective action can be to fatch, VNFd id from Tacker VNF list, and re-spawn VNF.04:16
dkushwahathis was the one of action we looked for our PoC, but i think that can be explore for more04:17
ekcsgot it that makes sense! again just for my context, is there a specific tacker api call or a series of api calls that accomplish that?04:18
ekcsi’m looking through the tacker api reference here
ekcsnot most current though.04:19
ekcsis this a better place to look?
dkushwahaekcs, to re-spawn VNF we can use POST /v1.0/vnfs04:22
dkushwahawhich is nothing, but create the VNF with specified VNFD id04:22
ekcsgot it!04:23
dkushwahaekcs, and later improvement, more actions can be scaling etc.. too04:24
dkushwaha*VNF Scaling04:24
ekcsI see. That’s great.04:24
ekcsthat’s cool. I’m definitely excited about this work. Seems that with some work, all the pieces would fit great together.04:26
*** jaypipes has quit IRC04:27
ekcsdkushwaha: let me know if you have more to say before I continue with questions/response =)04:27
dkushwahaekcs, i think, i am done from my side.04:28
ekcsgot it thanks a lot for the clear overview dkushwaha !04:29
ekcsakhil_jain and mbindlish do you have anything to add?04:29
mbindlishekcs: I think dkushwaha explained completely!04:30
akhil_jainekcs: None from my side04:30
ekcscool cool. So yea like I said I think it’s a great vision overall. I wonder what the work items would be on Congress side.04:31
ekcsmonasca webhook integration and tacker data source driver obviously.04:32
ekcsI wonder if there are further requirements for the use case.04:32
ekcsfor example, if congress calls the api to respawn VNF but it fails, what would we like to happen?04:33
dkushwahaekcs, I think for now we can just retry for re-spawn, but further improvement definitely will be a great addition04:36
ekcsdkushwaha: got it!04:36
ekcson another note, akhil_jain and I were wonderingi if there may be a example policy for the use case.04:37
ekcsin particular, it’d help to understand whether the splitting of one monasca webhook update into multiple transactions would cause problems or not.04:38
dkushwahambindlish, do you have example policy right now? otherwise we can share it later04:39
ekcsI understand that not all the schemas are fixed yet, but even a rough sketch would be helpful.04:39
mbindlishCurrently not having for respawn, but for example: deleting VNF04:40
mbindlishopenstack congress policy rule create --name delete_vnf classification 'execute[tacker:delete_vnf("<VNF_ID>")]:- monasca:alarm_notification(state="ALARM")'04:40
mbindlisha rough idea to understand04:41
*** yamamoto has joined #openstack-meeting04:41
ekcsgot it!04:41
ekcsgreat. well if there’s more sample available to share in the future I’d love to see it.04:42
ekcsis there anything specific I can help with?04:43
ekcson the rules, I’m down to help create them together if there’s ever any difficulty.04:44
dkushwahaekcs, is there some patch already in fly for the same?04:44
akhil_jaindkushwaha: i have started working on it
ekcsyes. akhil_jain has a WIP patch for tacker data source driver. a version of monasca webhook integration is already in rocky.04:45
dkushwahagreat, I thinks we can further discuss on patch review04:46
akhil_jainbut maybe for deleting and respawning VNF I will have to look more into it04:46
ekcsone more question: roughly how many VMs and how many VNFs are we envisioning in a setup?04:47
ekcslike 10s or 100s or 1000s?04:47
*** toabctl has quit IRC04:48
ekcsor we can defer till later.04:48
dkushwahaduring our PoC, we used around 10s for this integration. mbindlish, correct me if i m wrong.04:49
mbindlishYes, correct but I think there were no limit defined04:50
ekcsgot it. what’s a typical scale envisioned in production?04:50
dkushwahaekcs, not sure, but i think, we can defer limit part for now04:51
ekcscool. not looking for limit per se, but hoping for a general sense to understand if we’ll run into scaling issues. but yes definitely can be discussed in future.04:52
ekcswell is there anything else to discuss on the topic for today?04:52
dkushwahaekcs, from my side, nothing for now04:53
mbindlishnothing from my side04:54
ekcsgot it! I think we can end then unless akhil_jain there’s something you want to discuss?04:54
ekcsthanks again so much dkushwaha and mbindlish for stopping by for the very helpful discussion.04:54
akhil_jainekcs: nothing for now. got direction to work on from this discussion04:55
dkushwahaekcs, thanks04:55
akhil_jainThanks dkushwaha and mbindlish04:55
mbindlishekcs: dkushwaha akhil_jain thanks04:55
ekcsawesomeness. looking forward to continuing to work together!04:55
ekcslet’s end meeting then.04:56
ekcshappy friday all!04:56
dkushwahaThanks folks :)04:56
akhil_jainHappy friday!04:56
ekcsbye all =)04:56
*** openstack changes topic to "OpenStack Meetings ||"04:56
openstackMeeting ended Fri Sep 28 04:56:33 2018 UTC.  Information about MeetBot at . (v 0.1.4)04:56
openstackMinutes (text):
*** jamesmcarthur has quit IRC04:57
*** dkushwaha has left #openstack-meeting05:01
*** jamesmcarthur has joined #openstack-meeting05:01
*** jamesmcarthur has quit IRC05:06
*** ekcs has quit IRC05:10
*** iyamahat has joined #openstack-meeting05:15
*** yamamoto has quit IRC05:21
*** yamamoto has joined #openstack-meeting05:29
*** tetsuro has quit IRC05:35
*** e0ne has joined #openstack-meeting05:52
*** pcaruana has joined #openstack-meeting06:11
*** verdurin has quit IRC06:23
*** e0ne has quit IRC06:24
*** mtreinish has quit IRC06:24
*** yamamoto has quit IRC06:27
*** jamesmcarthur has joined #openstack-meeting06:29
*** jamesmcarthur has quit IRC06:34
*** e0ne has joined #openstack-meeting06:51
*** Luzi has joined #openstack-meeting06:53
*** ralonsoh has joined #openstack-meeting07:00
*** yamamoto has joined #openstack-meeting07:04
*** jamesmcarthur has joined #openstack-meeting07:07
*** dtrainor has quit IRC07:09
*** jamesmcarthur has quit IRC07:11
*** ykatabam has quit IRC07:11
*** rcernin has quit IRC07:12
*** ssbarnea|bkp has quit IRC07:16
*** aojea has joined #openstack-meeting07:18
*** jamesmcarthur has joined #openstack-meeting07:29
*** jamesmcarthur has quit IRC07:34
*** shu-mutow has joined #openstack-meeting07:36
*** markvoelker has quit IRC07:36
*** markvoelker has joined #openstack-meeting07:37
*** gibi is now known as giblet07:38
*** markvoelker has quit IRC07:42
*** longkb has quit IRC07:44
*** longkb has joined #openstack-meeting07:55
*** jamesmcarthur has joined #openstack-meeting07:56
*** alexchadin has joined #openstack-meeting07:57
*** jamesmcarthur has quit IRC08:01
*** alexchadin has quit IRC08:01
*** rossella_s has joined #openstack-meeting08:01
*** bauzas is now known as PapaOurs08:03
*** rossella_s has quit IRC08:09
*** rossella_s has joined #openstack-meeting08:10
*** alexchadin has joined #openstack-meeting08:11
*** alexchadin has quit IRC08:16
*** alexchadin has joined #openstack-meeting08:18
*** a-pugachev has joined #openstack-meeting08:24
*** alexchadin has quit IRC08:25
*** stephenfin is now known as finucannot08:27
*** alexchadin has joined #openstack-meeting08:28
*** dtrainor has joined #openstack-meeting08:31
*** ttsiouts has joined #openstack-meeting08:32
*** markvoelker has joined #openstack-meeting08:37
*** markvoelker has quit IRC08:59
*** alexchadin has quit IRC09:10
*** rossella_s has quit IRC09:11
*** rossella_s has joined #openstack-meeting09:13
*** ttsiouts has quit IRC09:15
*** ttsiouts has joined #openstack-meeting09:18
*** alexchadin has joined #openstack-meeting09:25
*** armax has quit IRC09:31
*** toabctl has joined #openstack-meeting09:42
*** tssurya has joined #openstack-meeting09:46
*** markvoelker has joined #openstack-meeting09:57
*** longkb has quit IRC09:58
*** scroll is now known as hfjvjffju09:59
*** alexchadin has quit IRC10:05
*** jamesmcarthur has joined #openstack-meeting10:12
*** e0ne has quit IRC10:16
*** jamesmcarthur has quit IRC10:16
*** markvoelker has quit IRC10:18
*** alexchadin has joined #openstack-meeting10:22
*** e0ne has joined #openstack-meeting10:25
*** alexchadin has quit IRC10:29
*** yamamoto has quit IRC10:31
*** yamamoto has joined #openstack-meeting10:32
*** yamamoto has quit IRC10:38
*** alexchadin has joined #openstack-meeting10:39
*** njohnston has joined #openstack-meeting10:56
*** erlon has joined #openstack-meeting11:03
*** erlon has quit IRC11:05
*** erlon has joined #openstack-meeting11:06
*** rfolco has quit IRC11:07
*** erlon has quit IRC11:07
*** ssbarnea|bkp has joined #openstack-meeting11:08
*** erlon has joined #openstack-meeting11:08
*** alexchadin has quit IRC11:08
*** ttsiouts has quit IRC11:09
*** rossella_s has quit IRC11:21
*** rossella_s has joined #openstack-meeting11:22
*** rfolco has joined #openstack-meeting11:26
*** yamamoto has joined #openstack-meeting11:26
*** rossella_s has quit IRC11:26
*** rossella_s has joined #openstack-meeting11:27
*** rossella_s has quit IRC11:33
*** rossella_s has joined #openstack-meeting11:37
*** ssbarnea|bkp has quit IRC11:40
*** shu-mutow has quit IRC11:43
*** rossella_s has quit IRC11:53
*** mschuppert has quit IRC11:54
*** rossella_s has joined #openstack-meeting11:55
*** Bhujay has joined #openstack-meeting11:58
*** mmethot has joined #openstack-meeting12:00
*** EmilienM is now known as EvilienM12:00
*** rossella_s has quit IRC12:09
*** rossella_s has joined #openstack-meeting12:10
*** rossella_s has quit IRC12:14
*** rossella_s has joined #openstack-meeting12:15
*** yamamoto has quit IRC12:16
*** rfolco has quit IRC12:18
*** ttsiouts has joined #openstack-meeting12:21
*** mriedem has joined #openstack-meeting12:29
*** dustins has joined #openstack-meeting12:36
*** raildo has joined #openstack-meeting12:38
*** tpsilva has joined #openstack-meeting12:40
*** artom has quit IRC12:44
*** rossella_s has quit IRC12:45
*** jamesmcarthur has joined #openstack-meeting12:45
*** rossella_s has joined #openstack-meeting12:47
*** raildo has quit IRC12:47
*** rossella_s has quit IRC12:52
*** rossella_s has joined #openstack-meeting12:54
*** raildo has joined #openstack-meeting13:00
*** raildo_ has joined #openstack-meeting13:03
*** raildo has quit IRC13:05
*** rfolco has joined #openstack-meeting13:06
*** raildo_ has quit IRC13:08
*** raildo has joined #openstack-meeting13:08
*** psachin has quit IRC13:13
*** rbudden has joined #openstack-meeting13:13
*** felipemonteiro has joined #openstack-meeting13:17
*** yikun has quit IRC13:21
*** efried is now known as fried_rice13:25
*** artom has joined #openstack-meeting13:29
*** Luzi has quit IRC13:30
*** david-lyle has joined #openstack-meeting13:34
*** tidwellr_ has quit IRC13:34
*** dklyle has quit IRC13:37
*** artom has quit IRC13:43
*** artom has joined #openstack-meeting13:44
*** a-pugachev has quit IRC13:47
*** artom has quit IRC13:52
*** armstrong has joined #openstack-meeting13:54
*** yamamoto has joined #openstack-meeting13:55
*** Nel1x has joined #openstack-meeting13:56
*** awaugama has joined #openstack-meeting13:57
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting neutron_drivers14:00
openstackMeeting started Fri Sep 28 14:00:10 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_drivers)"14:00
openstackThe meeting name has been set to 'neutron_drivers'14:00
mlavallehi everyone14:00
mlavallelet's give a couple of minutes to others to show up14:00
mlavalleamotoki won't join, since he is off on vacation this week14:01
*** artom has joined #openstack-meeting14:01
mlavallehow was your month long vacation, yamamoto?14:01
mlavalleok, let's get going14:02
yamamotomlavalle: exausted playing with my son14:02
mlavalleyamamoto: yeap, that's what parenting is all about. They have endless energy, and we don't anymore ;-)14:02
*** felipemonteiro has quit IRC14:03
mlavalle#topic RFEs14:03
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)"14:03
mlavalleso let's pick up where we left off last time....14:03
openstackLaunchpad bug 1785213 in neutron "[RFE] Automatically allow incoming DHCP traffic for networks which uses external dhcp server" [Wishlist,Triaged] - Assigned to Slawek Kaplonski (slaweq)14:03
slaweqI added some comment today to it, if there are any questions I can try to answer them now :)14:04
njohnstonI commented on it: for customers that use fwaas, I was wondering if you see this as something that can be communicated to fwaas, or will it just be incompatible with fwaas?14:05
slaweqnjohnston: I think that it depends on fwaas - there can be same thing done there as in security groups driver if this flag is set for subnet14:06
*** longkb has joined #openstack-meeting14:08
mlavalleso really the attribute you propose has only effect on the "walls", be it security groups or fwaas. nothing else is changed14:08
slaweqmlavalle: yes14:09
slaweqall of that can be achieved now also14:09
mlavallebut manually14:09
slaweqbut I had such request that it would be more "user friendly" to have such additional flag to set14:09
mlavalleyou are proposing a shortcut14:09
slaweqexactly :)14:09
njohnstonOK.  So if this flag gets set for an existing subnet then that would generate an RPC message to the agent to adjust the fw rules.  That part of the code would need to include a notification to the fwaas plugin so it could generate an fwaas RPC message.14:10
*** rossella_s has quit IRC14:10
mlavallenjohnston: would that be too much of a problem in fwaas?14:10
njohnstonI think fwaas could handle it without any issue, it's just something that would need to be built in at the api server14:11
slaweqnjohnston: yes, so we have to keep it in mind that there is fwaas also, thx for pointing that14:12
yamamotois there a plan for "how to make external dhcp server aware of what IPs should be assigned to OS instances" part?14:12
slaweqyamamoto: no14:12
*** longkb has quit IRC14:12
slaweqyamamoto: basically this rfe assumes that operator knows what he is doing by using this14:13
slaweqand what can be consequences14:13
yamamotohaving only this shortcut seems a little strange for me. is this a scenario common enough to warrant the shortcut?14:14
*** rossella_s has joined #openstack-meeting14:14
slaweqI had such request from our customer, I don't know if that is very common use case, probably not14:15
mlavalleyeah, we cannot assume is very common14:15
yamamotoone customer?14:15
mlavallewe would have heard of it before, I would think14:15
mlavallemaybe it is too much just for one customer / user14:17
slaweqit may be like that14:17
mlavalleI propose one of two option (or a combination of both): leave this rfe pending until somone shows up. and / or ask in the ML14:17
slaweqso let's maybe postpone it for now and if there will be some new requests for this, we can return it14:17
njohnstonIs this something where it would be good to solicit feedback from the openstack-ops list?14:18
mlavalleyeah, ^^^^ that's what I meant by the ML14:18
*** jamesmcarthur has quit IRC14:18
slaweqok, I will send email about that to operators ML then14:18
mlavallelet's postpone it and ask the operators14:18
*** jamesmcarthur has joined #openstack-meeting14:18
* mlavalle leaving comment and marking rfe postponed14:19
*** hongbin has joined #openstack-meeting14:19
slaweqok, thx14:19
*** bnemec is now known as beekneemech14:20
njohnstonlast question on this: does turning things over to an external dhcp server assume disabling all ipam functionality for that subnet?14:21
*** jaypipes has joined #openstack-meeting14:21
slaweqnjohnston: no, I didn't think about that14:21
njohnstonnm, I'll ask on launchpad and if we reveve it we can figure it out then :-)14:21
slaweqnjohnston: but maybe we can think about it later14:22
mlavalleok, let's move on14:22
openstackLaunchpad bug 1784879 in neutron "Neutron doesn't update Designate with some use cases" [Wishlist,Triaged]14:22
slaweqso if I understood corectly last comments, it would be added to network and all ports from such network will have this option turned on, right?14:24
mlavallethat's what the suggestion is to hit a middleground in terms of not too little, not too much granularity14:25
*** edmondsw_ has joined #openstack-meeting14:26
slaweqIMO it sounds reasonable for the beginning, if later will be need to add it on port level, it can be added easily, right?14:26
*** mbindlish has quit IRC14:27
mlavalleI think so. At that point we wiull need to think about whose atribute overrides other attributes. Probabble, the more granular the resource, the higher the priority14:28
slaweqyes, but I think that doing (later) network and port level could be enough14:28
slaweqand then port attribute would override network attribute14:29
*** edleafe has quit IRC14:29
slaweqbecause problem with subnets is that one port can have more than one subnet so here it would be tricky14:29
*** edmondsw has quit IRC14:29
*** edmondsw_ is now known as edmondsw14:29
slaweqbut port and network should be easy (as it is in e.g. QoS now)14:29
mlavallethat was exactly my thinking14:29
mlavallethe way it is implemented today, we take all the ip addresses form the port and create a recordset for all of them14:30
*** edleafe has joined #openstack-meeting14:30
mlavallewell, one ipv4 recordset and one ipv6 recordsert14:30
yamamotoas it's about ip addresses, i tend to think subnet is a more natural choice than network14:30
*** davidsha has joined #openstack-meeting14:31
*** mjturek has joined #openstack-meeting14:32
*** bobh has joined #openstack-meeting14:32
mlavallefrom the tcp / ip layers logic point of view, you are right. ip addresses are a layer above network....14:33
mlavalleis that what you meant?14:33
yamamotoi even feel it has some correlations with service_types14:33
*** dustins has quit IRC14:34
*** electrofelix has quit IRC14:34
mlavallewould you elaborate?14:35
yamamotoi meant subnet is more natural for this specific feature14:35
mlavallewould you elaborate the service types idea?14:36
yamamotoas a user would set up a subnet routable from outside14:36
yamamotoservice_types describe the purpose of subnet. this new field does similar.14:37
mlavalleand that signals that we want that fixed ips from that range should be sent to the external DNS service14:37
*** jamesmcarthur has quit IRC14:38
*** jamesmcarthur has joined #openstack-meeting14:38
*** dustins has joined #openstack-meeting14:38
mlavalleIMO, it is an excellent proposal14:38
mlavallewhat do others think?14:39
slaweqso yamamoto You propose to use service_types field instead of adding new one somewhere?14:39
slaweqam I understand correctly?14:39
yamamotowell, i'm not suggesting to unify it with service types. (i'm not sure if it should)14:39
*** artom has quit IRC14:39
mlavalleyes, with a new service type14:39
yamamotoi'm suggesting it belongs to subnet14:39
mlavallebut that's exactly the purpose of service types14:40
mlavalleto indicate that a subnet has a special treatment14:40
mlavallegiven its service type14:40
slaweqok, but then how it would work if port would have IPs from two subnets and one would have this enabled and second no? we would need to change existing logic to create recordsets not for all IPs from port but only for some of them, right?14:40
mlavalleyes, but I don't think that is a big deal14:41
yamamotomaybe. but service type is just a string. it might not be descriptive enough for some use cases.14:41
slaweqI'm fine with it but just asking to understand correctly what will be to do14:41
*** jamesmcarthur has quit IRC14:41
*** jamesmcarthur has joined #openstack-meeting14:42
mlavallehaleyb, you are "mr service type". what do you think?14:42
haleybservice type is also a subset of device_owner values14:42
haleybyes, i was re-educating myself14:42
mlavalleso, do you think service type is appropriate for this rfe?14:43
haleybso i'm not sure how it would work given it's a device_owner, or empty14:43
*** felipemonteiro has joined #openstack-meeting14:44
haleybdoesn't seem to fit the model to me at least14:45
mlavallewell, any other potential attribute would be the same. either the user specifeid it or it is empty / NOne14:45
*** armax has joined #openstack-meeting14:45
mlavallefair enough14:45
*** jamesmcarthur has quit IRC14:46
mlavallebased on the discussion, I suggest go back to the rfe and propose dns_publish_fixed_ip at the subnet level....14:46
slaweqbut can't it be something like e.g. "compute:dns_publish_fixed_ip" as service type?14:47
haleybmlavalle: the service_type is a list, so can contain multiple things14:47
haleyband yes, it can be any string we want14:47
slaweqwhich would means that compute ports will have published IPs14:47
mlavallethat's what I understood^^^^^ when yamamoto originally brought up service types14:48
yamamotoi didn't know it was a list14:48
slaweq <-- here is validator of this attribute14:48
haleybthe intention was for IP allocation on a network based on ports getting attached14:48
haleybso startswith('compute') is all it's matching in most cases14:49
mlavallehaleyb: so we only refere to it in the IPAM code?14:50
haleybmlavalle: it's been a while, but yes from what i remember it's IPAM where we actually use the type14:51
yamamotoat this point i feel a separate boolean field in subnet would be simpler than overloading service types with a magic owner value14:53
haleybi'd have to think some more on implementation, the [] is a wildcard match and if it's ['compute:dns_publish'] what would break?14:53
mlavallefrom the docs: "Service subnets enable operators to define valid port types for each subnet on a network...."14:54
*** munimeha1 has joined #openstack-meeting14:54
mlavalleso based on this definition, I agree with yamamoto's latest statement14:54
munimeha1sorry got late14:54
slaweqwe can then break allocation of IPs from such subnet14:55
*** jamesmcarthur has joined #openstack-meeting14:55
haleyb"Creating a subnet with a service type requires administrative privileges." - that might also be a problem14:56
mlavalleso I propose I go back to the RFE, and propose dns_publish_fixed_ip at the subnet level14:57
mlavalleand we retake the discussion next meeting14:57
slaweqfine for me14:57
*** e0ne has quit IRC14:58
*** Bhujay has quit IRC14:58
*** macza has joined #openstack-meeting14:58
mlavallemunimeha1: We won't have time to discuss your RFE, we are 2 minutes away from end of meeting. slaweq and I left some comments in your new RFE. Let's discuss there over the next few days14:58
mlavalleThanks for attending guys. Have a very nice weekend!14:59
munimeha1thats fine  I opened the RFE
openstackLaunchpad bug 1794771 in neutron "SRIOV trunk port - multiple vlans on same VF" [Wishlist,New]14:59
slaweqthx, have a good weekend!14:59
mlavallemunimeha1: yes, that where we left comments / question14:59
*** jamesmcarthur has quit IRC14:59
*** openstack changes topic to "OpenStack Meetings ||"14:59
openstackMeeting ended Fri Sep 28 14:59:43 2018 UTC.  Information about MeetBot at . (v 0.1.4)14:59
openstackMinutes (text):
* mlavalle doesn't want to provoke smcginnis rage ;-)15:00
*** jamesmcarthur has joined #openstack-meeting15:00
smcginnis#startmeeting releaseteam15:00
openstackMeeting started Fri Sep 28 15:00:36 2018 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: releaseteam)"15:00
openstackThe meeting name has been set to 'releaseteam'15:00
smcginnisttx, dhellmann, fungi, armstrong, others.15:01
smcginnisWhew, didn't get spam blocked on that.15:01
smcginnisAround line 42.15:01
smcginnis#topic Release failures15:02
*** openstack changes topic to "Release failures (Meeting topic: releaseteam)"15:02
smcginnisMostly since I was out most of the week, I was hoping we could have a quick recap of the release failures.15:02
*** e0ne has joined #openstack-meeting15:02
smcginnisAnd just a quick sanity check that everything has been fixed up.15:02
* dhellmann clears his throat nervously15:02
smcginnisdhellmann: It was some package update?15:02
dhellmanntwine version 1.12.0 reported a failure even when it succeeded15:03
fungihad the fix15:03
smcginnisWell that doesn't sound like a good thing. :)15:03
dhellmannafter spending a bunch of time figuring that out, I decided to wait for the new twine release and re-tag all of the releases I had already approved15:04
smcginnisdhellmann: I saw you had the tracking etherpad for failures in the tracking etherpad. Anything we need to check in there?15:04
dhellmannbecause there were a lot of them, and some of the artifacts had been uploaded, so rerunning the existing tags would be a lot of work15:04
smcginnisYeah, good call.15:04
dhellmannwhen twine 1.12.1 was released I tested it with the release-test repo, and it worked fine15:04
dhellmannso I prepared a single patch to retag all of the deliverables we missed with new patch-level updates to their version  numbers15:05
dhellmannthose all went through OK15:05
smcginnisThanks for handling all of that.15:05
dhellmannI think I missed rally in that set, so we came back later and did a new release of rally separately15:05
dhellmannthat release actually included a fix or two, so it wasn't a direct retag15:05
dhellmannand I have now learned to test the release machinery before approving a bunch of things on a monday morning :-)15:05
*** jaypipes is now known as leakypipes15:06
smcginnisJust running a quick missing-releases report, there are some older rally ones missing, but otherwise everything looks fine.15:07
smcginnisAnd actually, just the one expected missing and a bunch of older asc files.15:07
dhellmannyeah, so we could comment out the missing one or just leave it15:08
smcginnisSo probably nothing we need to change or document with this whole situation other than maybe be cautious Monday mornings. :)15:08
*** artom has joined #openstack-meeting15:09
smcginnis#topic PTG proposed changes15:09
*** openstack changes topic to "PTG proposed changes (Meeting topic: releaseteam)"15:09
ttxthat's vague15:09
smcginnisI sent out the first part of the plan we discussed in Denver for dropping milestone releases.15:09
ttxah, THOSE15:09
smcginnisSurprisingly less of a reaction than I expected.15:09
ttxmine at least did trigger one answer15:10
smcginnisSo next step is probably to make the cycle-with-rc change.15:10
smcginnisShould we rename the existing model or introduce it as a new one? Probably just rename?15:10
fungii expect the forced tagging of cycle-with-intermediary will be the controversial one, of any15:11
smcginnisYeah, that one will be a bigger one.15:11
dhellmannsmcginnis : let's make a new one. it will mean fewer updates to existing deliverable files15:11
dhellmannwe can switch just the stein deliverables and set up validation to disallow the old name in new releases15:11
dhellmannor new series I should say15:11
ttxrename yes15:11
smcginnisI was thinking new one would be safer.15:12
ttxah hm15:12
ttxyour call15:13
dhellmannbackwards compatibility ftw?15:13
smcginnisOK, how about we start with introducing a new model, and if we find we want to later, we can convert exising -milestone ones over to -rc and get rid of it after the fact?15:14
dhellmannwell, we're going to want to convert the stein one over, and the older ones don't matter at this point15:15
ttxdhellmann: so the trick with a new one is that we'll have to lave old doc around ?15:15
dhellmannI just meant we would need fewer exceptions for checking the release model in those older files if we keep the old name15:15
dhellmannlet me look at the validation quickly, hang on15:15
dhellmannok, the validation relies on the schema.yaml file15:16
dhellmannso we can leave the old name in there and remove the docs for it15:16
smcginnisSounds reasonable to me.15:16
*** rossella_s has quit IRC15:16
dhellmannthen we can add a validation rule that says cycle-with-milestones can't be used in the current series15:17
dhellmannwe can do that in the validate_new_releases() function15:18
dhellmannthat's what that's for15:18
smcginnisLooks like enough of a plan.15:18
dhellmannthere are probably some tests to update, too, but it ought to be doable with 1 patch15:18
smcginnisThen next step - I can send out the cycle-with-intermediary post early next week.15:19
smcginnisThat will probably result in more discussion.15:19
*** rossella_s has joined #openstack-meeting15:19
smcginnisThose drafts again ^15:19
*** longkb has joined #openstack-meeting15:20
*** dtrainor has quit IRC15:21
dhellmannyes, I think that's the next step15:21
*** dtrainor has joined #openstack-meeting15:21
ttxI think email 2 can be sent next week15:21
ttxmaybe also email 315:22
smcginnisI'll shoot for Tuesday or Wednesday.15:22
armstrong@smcginnis: So cycle-with-milestones will no longer be use at all15:22
armstrongI missed the discussion at Denver15:23
smcginnisarmstrong: Correct. We're going to try dropping milestone releases for service projects and only require the RC and final releases.15:23
dhellmannarmstrong : right, cycle-with-rc is a variation on that one15:23
smcginnisThey can still do earlier beta releases if they have a need, but it isn't going to be something that we are going to enforce or necessarily encourage.15:23
ttxsmcginnis: we are dropping requirements to tag at milestones, so the name did not make that much sense anymore15:23
ttxerr armstrong ^15:24
armstrongOk.  Thanks15:24
smcginnis#topic Open discussion15:24
*** openstack changes topic to "Open discussion (Meeting topic: releaseteam)"15:24
smcginnisAnything else we should cover at this point?15:25
*** yamamoto has quit IRC15:25
fungiarmstrong: was the announcement15:25
ttxI don't have anything. Making good progress on other work lines15:25
dhellmannsince it's long, I wanted to make sure everyone noticed my planned 2 week vacation coming up in R-25 and R-2615:25
dhellmannsorry, 25 and 2415:26
lbragstadnice - enjoy the time off dhellmann :)15:26
armstrong@fungi: great! I will go through it15:26
ttxbeen engaging with teams that publish artifacts in external platforms to expose taht in the project navigator15:26
dhellmannlbragstad : thanks!15:26
smcginnisWow, two whole weeks!15:27
ttxI'll be heavily traveling (read: in China) over weeks -25 and -2615:27
smcginnisI think I have all my travel on the etherpad.15:27
ttx(and in Europe)15:27
smcginnisBut that reminds me, I will be on a plane next Friday at this time.15:27
smcginnisDoes someone want to run that meeting, or should we just cancel?15:28
dhellmanndo we have anything critical on the schedule?15:29
smcginnisNot really at this point.15:29
smcginnisWe're still a few weeks out to milestone 1.15:29
ttxyay long cycles15:29
smcginnisWe have a few tasks in progress, but nothing I think is critical for timing right now.15:29
dhellmannyeah, so we could just plan on office hours or one of us could run the meeting15:30
ttxdhellmann: a way to have perfect 6-month cycles would be to adopt something like
smcginnisLet's plan on office hours unless something comes up next week that warrants an actual meeting.15:30
dhellmannttx: sounds like UTC to me, frankly15:31
* fungi still remembers swatch beat time15:31
smcginnisOK, we can make a call next week on a meeting. That's all I had for this week's.15:32
ttxSummits should be on April 15 and October 15, and teh year and time shoudl organize around them to match when they actually occur15:32
dhellmannI keep saying we'd have less trouble coordinating with venues if we just bought one.15:32
dhellmannwe could rent it out to other foundations to cover the mortgage15:32
dhellmannand then they would have to schedule around us15:33
fungithe stackdrome15:33
smcginnisAre buildings in Detroit still cheap? :)15:33
fungidepends on if you need them to have walls and roofs15:33
dhellmannI saw a ton of buildings for sale in Glasgow a couple of months ago15:33
smcginnisfungi: "Open" source?15:33
fungiopen air15:34
fungithe fifth open15:34
smcginnisOK, I think this meeting was done awhile ago now. :)15:34
smcginnisThanks everyone.15:34
fungithanks smcginnis!15:34
*** openstack changes topic to "OpenStack Meetings ||"15:34
openstackMeeting ended Fri Sep 28 15:34:43 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:34
openstackMinutes (text):
*** cloudrancher has quit IRC15:36
*** cloudrancher has joined #openstack-meeting15:36
*** lbragstad is now known as elbragstad15:38
*** yamamoto has joined #openstack-meeting15:51
*** ttsiouts has quit IRC15:55
*** longkb has quit IRC15:57
*** finix has joined #openstack-meeting16:00
*** finix has quit IRC16:01
*** armstron_ has joined #openstack-meeting16:07
*** fried_rice is now known as fried_rolls16:15
*** manjeets has quit IRC16:17
*** aojea has quit IRC16:17
*** mriedem is now known as mriedem_lunch16:21
*** gyee has joined #openstack-meeting16:24
*** Leo_m has joined #openstack-meeting16:24
*** yamamoto has quit IRC16:31
*** davidsha has quit IRC16:38
*** ianychoi has quit IRC16:39
*** munimeha1 has quit IRC16:43
*** ianychoi has joined #openstack-meeting16:44
*** mlavalle has left #openstack-meeting16:47
*** geguileo is now known as geguileo_PTO16:51
*** rossella_s has quit IRC16:51
*** priteau has joined #openstack-meeting16:54
*** rossella_s has joined #openstack-meeting16:54
*** Nel1x has quit IRC17:04
*** bobh has quit IRC17:07
*** psachin has joined #openstack-meeting17:09
*** bobh has joined #openstack-meeting17:13
*** bobh has quit IRC17:21
*** macza has quit IRC17:24
*** macza has joined #openstack-meeting17:24
*** yamamoto has joined #openstack-meeting17:26
*** rossella_s has quit IRC17:27
*** macza has quit IRC17:29
*** rossella_s has joined #openstack-meeting17:30
*** tssurya has quit IRC17:31
*** armstrong has quit IRC17:43
*** e0ne has quit IRC17:44
*** cloudrancher has quit IRC17:47
*** jamesmcarthur has quit IRC17:48
*** cloudrancher has joined #openstack-meeting17:48
*** iyamahat has quit IRC17:49
*** mriedem_lunch has quit IRC17:52
*** diablo_rojo has joined #openstack-meeting17:52
*** mriedem has joined #openstack-meeting17:54
*** yamahata__ has quit IRC17:56
*** david-lyle has quit IRC17:56
*** mahatic has quit IRC17:56
*** e0ne has joined #openstack-meeting18:02
*** TheJulia is now known as needssleep18:02
*** yamahata__ has joined #openstack-meeting18:04
*** mahatic has joined #openstack-meeting18:04
*** iyamahat has joined #openstack-meeting18:05
*** e0ne has quit IRC18:05
*** yamahata has joined #openstack-meeting18:05
*** raildo has quit IRC18:06
*** raildo has joined #openstack-meeting18:06
*** macza has joined #openstack-meeting18:07
*** macza has quit IRC18:12
*** e0ne has joined #openstack-meeting18:25
*** bobh has joined #openstack-meeting18:26
*** cloudrancher has quit IRC18:27
*** cloudrancher has joined #openstack-meeting18:28
*** yamamoto has quit IRC18:28
*** macza has joined #openstack-meeting18:30
*** cloudrancher has quit IRC18:30
*** cloudrancher has joined #openstack-meeting18:31
*** bobh has quit IRC18:31
*** cloudrancher has quit IRC18:34
*** cloudrancher has joined #openstack-meeting18:35
*** bobh has joined #openstack-meeting18:38
*** rossella_s has quit IRC18:40
*** david-lyle has joined #openstack-meeting18:41
*** rossella_s has joined #openstack-meeting18:42
*** david-lyle is now known as dklyle18:42
*** bobh has quit IRC18:42
*** mriedem has quit IRC18:44
*** felipemonteiro has quit IRC18:47
*** cloudrancher has quit IRC18:48
*** e0ne has quit IRC18:50
*** rossella_s has quit IRC18:50
*** rossella_s has joined #openstack-meeting18:57
*** cloudrancher has joined #openstack-meeting19:01
*** rossella_s has quit IRC19:02
*** rossella_s has joined #openstack-meeting19:03
*** bobh has joined #openstack-meeting19:09
*** elbragstad has quit IRC19:10
*** elbragstad has joined #openstack-meeting19:10
*** armstron_ has quit IRC19:11
*** artom has quit IRC19:22
*** tssurya has joined #openstack-meeting19:22
*** bobh has quit IRC19:23
*** bobh has joined #openstack-meeting19:23
*** e0ne has joined #openstack-meeting19:29
*** artom has joined #openstack-meeting19:30
*** e0ne has quit IRC19:34
*** ralonsoh has quit IRC19:35
*** mriedem has joined #openstack-meeting19:50
*** Emine has quit IRC19:52
*** Emine has joined #openstack-meeting19:55
*** llu has quit IRC20:03
*** awaugama has quit IRC20:05
*** erlon has quit IRC20:07
*** rossella_s has quit IRC20:08
*** rossella_s has joined #openstack-meeting20:09
*** psachin has quit IRC20:10
*** mjturek has quit IRC20:18
*** yamamoto has joined #openstack-meeting20:26
*** rossella_s has quit IRC20:26
*** rossella_s has joined #openstack-meeting20:29
*** artom has quit IRC20:54
*** bobh has quit IRC20:54
*** mmethot has quit IRC21:00
*** mmethot has joined #openstack-meeting21:00
*** raildo has quit IRC21:04
*** mmethot has quit IRC21:05
*** PapaOurs is now known as bauzas21:05
*** dustins has quit IRC21:06
*** rbudden has quit IRC21:15
*** yamamoto has quit IRC21:15
*** rossella_s has quit IRC21:17
*** rfolco has quit IRC21:18
*** rossella_s has joined #openstack-meeting21:20
*** rbudden has joined #openstack-meeting21:21
*** dtrainor_ has joined #openstack-meeting21:22
*** dtrainor has quit IRC21:24
*** tssurya has quit IRC21:26
*** slaweq has quit IRC21:28
*** bobh has joined #openstack-meeting21:30
*** rossella_s has quit IRC21:31
*** rossella_s has joined #openstack-meeting21:31
*** mriedem has quit IRC21:37
*** priteau has quit IRC21:42
*** rossella_s has quit IRC21:49
*** bobh has quit IRC22:03
*** artom has joined #openstack-meeting22:13
*** EvilienM is now known as EmilienM22:20
*** fried_rolls is now known as efried22:20
*** rbudden has quit IRC22:29
*** jamesmcarthur has joined #openstack-meeting22:36
*** jamesmcarthur has quit IRC22:40
*** macza_ has joined #openstack-meeting22:40
*** macza has quit IRC22:42
*** rbudden has joined #openstack-meeting22:47
*** ijw has joined #openstack-meeting22:48
*** elbragstad has quit IRC22:48
*** tpsilva has quit IRC22:52
*** macza_ has quit IRC22:53
*** macza has joined #openstack-meeting22:53
*** macza has quit IRC22:58
*** felipemonteiro has joined #openstack-meeting23:00
*** elbragstad has joined #openstack-meeting23:01
*** hongbin has quit IRC23:02
*** elbragstad has quit IRC23:11
*** yamamoto has joined #openstack-meeting23:15
*** dtrainor__ has joined #openstack-meeting23:17
*** macza has joined #openstack-meeting23:17
*** dtrainor_ has quit IRC23:20
*** macza has quit IRC23:21
*** rbudden has quit IRC23:24
*** felipemonteiro has quit IRC23:26
*** gyee has quit IRC23:33
*** jamesmcarthur has joined #openstack-meeting23:34
*** jamesmcarthur has quit IRC23:39
*** yamamoto has quit IRC23:59

Generated by 2.15.3 by Marius Gedminas - find it at!