Tuesday, 2020-05-19

*** mlavalle has quit IRC00:04
*** jamesmcarthur has joined #openstack-meeting00:09
*** dmacpher has joined #openstack-meeting00:14
*** dmacpher__ has quit IRC00:15
*** dmacpher_ has joined #openstack-meeting00:18
*** dmacpher has quit IRC00:20
*** jmasud has joined #openstack-meeting00:21
*** brinzhang has joined #openstack-meeting00:23
*** slaweq has quit IRC00:26
*** slaweq has joined #openstack-meeting00:37
*** jmasud has quit IRC00:38
*** slaweq has quit IRC00:42
*** EmilienM|off is now known as EmilienM00:46
*** evrardjp has quit IRC00:52
*** jhesketh has joined #openstack-meeting00:52
*** jmasud has joined #openstack-meeting00:54
*** jamesmcarthur has quit IRC00:58
*** andrebeltrami has quit IRC00:58
*** brinzhang_ has joined #openstack-meeting01:11
*** brinzhang has quit IRC01:14
*** yaawang has quit IRC01:22
*** jamesmcarthur has joined #openstack-meeting01:23
*** kevinz has joined #openstack-meeting01:23
*** yasufum has joined #openstack-meeting01:25
*** yaawang has joined #openstack-meeting01:25
*** yasufum has quit IRC01:29
*** jmasud has quit IRC01:42
*** rmcall has quit IRC01:53
*** hongbin has joined #openstack-meeting03:00
*** jmasud has joined #openstack-meeting03:08
*** jamesmcarthur has quit IRC03:09
*** jamesmcarthur has joined #openstack-meeting03:10
*** gyee has quit IRC03:23
*** jamesmcarthur has quit IRC03:24
*** armax has quit IRC03:26
*** jamesmcarthur has joined #openstack-meeting03:26
*** jamesmcarthur has quit IRC03:27
*** jamesmcarthur has joined #openstack-meeting03:28
*** psachin has joined #openstack-meeting03:39
*** tetsuro has quit IRC03:45
*** tpatil has joined #openstack-meeting03:55
*** suzhengwei has joined #openstack-meeting04:00
*** noonedeadpunk has joined #openstack-meeting04:01
tpatil#startmeeting Masakari04:02
openstackMeeting started Tue May 19 04:02:54 2020 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.04:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:02
*** openstack changes topic to " (Meeting topic: Masakari)"04:02
tpatilHi All04:02
openstackThe meeting name has been set to 'masakari'04:02
*** jmasud has quit IRC04:03
tpatilSampath san should be joining any time04:03
tpatilRoll call?04:03
*** samP has joined #openstack-meeting04:03
suzhengweihi04:03
samPHi all, sorry Im late04:03
tpatilsuzhengwei: Hi04:04
tpatilsamP: Hi04:04
noonedeadpunko/04:04
samPmeeting started, right?04:05
tpatilsamP: Yes04:05
samPtpatil: Thanks04:05
tpatilsamP: Please go ahead and start the topic discussions04:06
samPsure04:06
samP#topic Victoria work items04:06
samPFirst let's take a look at what left for victoria04:07
tpatil#link : https://etherpad.opendev.org/p/masakari-victoria-workitems04:07
tpatilI have moved the work items from Ussuri to above etherpad04:07
samPtpatil: thanks04:07
suzhengweinice04:08
suzhengweiI have add "promotion for large scale host failure".04:09
samPspec: Evacuate non-recovery (’HA_enabled = False’) instances in shutoff status at host failure except specified tenant04:10
noonedeadpunkThis looks https://review.opendev.org/#/c/714615/1 pretty usefull one04:10
samPspec lgtm. I think we can review and merge the code soon.04:11
samPnoonedeadpunk: thanks, that is the code for above spec. right?04:11
noonedeadpunkyep04:11
tpatilsamP: I will review the spec and code in this week04:12
samPsuzhengwei: Thanks for adding promotion for large scale host failure. Is this a feature or problem statement? Could please add more details on this.04:12
*** suzhengwei_ has joined #openstack-meeting04:13
*** brinzhang has joined #openstack-meeting04:14
suzhengwei_I will give a spec about it later.04:14
samPsuzhengwei_: Thanks..04:14
samP(2) Modify masakari-hostmonitor in order to run it inside container04:14
*** tetsuro has joined #openstack-meeting04:15
tpatilThere is one finding about systemctl command that's used in corosync command as well04:15
*** suzhengwei has quit IRC04:16
noonedeadpunksorry for small offtopic, I think I just missed a feature, but how failed host goes to reserved state after recovery? by setting post in host_rh_failure_recovery_tasks?04:16
*** brinzhang_ has quit IRC04:17
tpatilnoonedeadpunk: Are you asking how does recovery_method='reserved_host' works?04:18
hyunsikyangkst04:18
noonedeadpunknot really. just in spec there is "When a failed host goes back to system as a reserved host"04:19
samPnoonedeadpunk: your question is, how a failed host become a reserved host?04:19
noonedeadpunkyep. as by default it do not become reserved one after recovery04:19
*** ociuhandu has joined #openstack-meeting04:20
suzhengwei_It should have finished recovery workflow and rejion the compute resource pool, then it can be update to reserved by api.04:21
noonedeadpunkOk, but it's not smth masakari does at the moment?04:22
samPmasakari dont have that feature now.04:22
suzhengwei_reserved hosts is set by operator.04:22
noonedeadpunkah, ok I see. Just out of spec it seemed that it has one04:23
suzhengwei_yes04:23
noonedeadpunkBtw it might be pretty useful and not really hard to implement I think..04:23
tpatilYou are allowed to set on_maintenance and reserved of the failed host. Once the VMs are evacuated from the failed host. You can update host to change on_maintenance and reserved parameters.04:24
tpatilThis doesn't happen automatically, operator will need to do it manually.04:24
*** ociuhandu has quit IRC04:24
tpatilAre you saying this procedure should be automated?04:25
noonedeadpunkoh, I see your point now. Like as you need to update on_maintenance manually anyway it's useless to set it to reserved04:25
samPIt is a nice feature to have. However, before you bring back the failed host to cluster again, you have make sure it worn't break again.04:25
noonedeadpunkyeah, ok, it's fair04:26
samPIn current operations. we leave that part to operator.04:26
tpatilMoving back to run hostmonitor inside container04:27
samPnoonedeadpunk: if you have comments or questions, please feel free to add them to spec04:27
tpatilcorosync itself uses systemctl command. I'm not able to find the link of the source code.04:27
samPtpatil: sure04:27
tpatilI will add it to the etherpad after this meeting04:27
samPtpatil: sure, thanks04:28
samPwe do not have any bug or gerrit code review related to this, right?04:28
tpatilNo04:29
samPtpatil: OK thanks. Let's see how we can proceed this in next meetings.04:31
samPAbout, Command parameter support to segment list command to filter out segments based on host input parameter04:31
tpatilsamP: Sure.I will post all details in etherpad in this week.04:31
samPwe discussed about this in past meetings and agree on how to proceed.04:31
samPEnable/Disable evacuation segment wise04:33
samPsuzhengwei_: Thanks, and sorry for the review delay.04:34
tpatilso we should add a new REST API Get /hosts?host=xyz which shouldn't include segment_id, is it correct?04:34
suzhengwei_I would like to move this spec to victoria.04:34
samPtpatil: correct.04:34
tpatilsamP: Ok04:34
suzhengwei_Add victoria cycle spec firstly. https://review.opendev.org/#/c/723297/04:35
samPsuzhengwei_: sure, let's do the review and merge this on early Victoria. Then hopefully we can finish this feature in V04:35
samPsuzhengwei_: Thanks, I will merge this first..04:36
suzhengwei_OK04:36
tpatilI have one question, what value should be set to "state"?04:36
suzhengwei_I want to split the implent commit for easy review.04:37
*** hongbin has quit IRC04:37
samPsuzhengwei_That would be really helpful.04:37
tpatilIMO, it should be either ENABLED/DISABLED or ACTIVATED/DEACTIVATED, instead of False/True?04:37
suzhengwei_we use 'enable' already. If use 'state', we would have a update problem.04:37
noonedeadpunkimo boolean is better as a value04:38
noonedeadpunksince it would have only 2 states04:38
suzhengwei_yes, a boolean value.04:38
tpatilsorry, it's enable not state.04:39
tpatilshould it be called as state/status and value can be as stated above04:40
noonedeadpunkLike I really see no reason here to invent some naming for really boolean value. Also bool takes less space in db storage comparing to varchar :p04:42
suzhengwei_this is not important conflict. But to me, if changed to 'state', my cloud have to change its api and db table.04:42
suzhengwei_I would have to do some extra meaningless work.04:43
tpatilenable should be changed to enabled atleast04:43
noonedeadpunk+104:44
tpatilAnyway, I will post this comment on the spec and later you guys can comment on it.04:44
suzhengwei_ok04:45
samPboth options are good for me. Let's discuss further on spec.04:47
samPsuzhengwei_: please add more details for "promotion for large scale host failure". So we can discuss this on up coming meetings.04:48
suzhengwei_ok.04:48
samP#topic List of patches waiting for Victoria04:49
samPPlease add any patches you need to get merge in V.04:50
tpatilI have reviewed couple of patches and posted my comments04:50
noonedeadpunkSo I originaly joined meeting to talk about https://review.opendev.org/#/c/728629/04:50
tpatilToday I have posted my comments. did you check these comments?04:51
noonedeadpunkI read your comment tpatil just during the meeting04:51
tpatilok04:51
samPnoonedeadpunk: thanks for the patch04:51
suzhengwei_I will review it later.04:51
noonedeadpunkSo the thing is, that hypervisors are used in the code only once and for checking hosts while adding them04:51
noonedeadpunkAnd all futher operations are provided with compute api04:52
*** vishalmanchanda has joined #openstack-meeting04:52
noonedeadpunkSo like even if ppl configure pacemaker to use hypervisor names and add them to masakari - masakari would just faile while completing action04:53
noonedeadpunkAs won't be able to find corresponding service to disable and evacuate04:54
tpatilnoonedeadpunk: I'm ok with your changes. just that, we need a migration command in masakari-manage to update the host from hypervisor_name to host04:54
tpatilthis is required for operators who was already using masakari in production env.04:54
noonedeadpunkYeah, I see, was just answering first comment:)04:54
noonedeadpunks/comment/question04:55
suzhengwei_time is running out, let's be quick.04:55
tpatilnoonedeadpunk: So operators basically use nova.services.host when they add a node in pacemaker cluster, is it correct?04:55
noonedeadpunkJust might need some help with writing migration thing04:56
noonedeadpunktpatil: they are supposed so at least04:56
noonedeadpunkotherwise things do not work out of my experience04:56
samPnoonedeadpunk: sounds reasonable to me.  Let's discuss further on the gerrit.04:56
noonedeadpunkok04:56
tpatilnoonedeadpunk: Ok, I will help you to write a migration command in masakari-manage tool.04:56
*** samP has quit IRC04:57
noonedeadpunktpatil: like let me try doing it:) IF I got stuck I'll ping you?:)04:57
tpatilnoonedeadpunk: Sure04:57
*** suzhengwei__ has joined #openstack-meeting04:57
*** samP has joined #openstack-meeting04:57
samPsorry I was disconnected..04:58
suzhengwei__me, too.04:58
noonedeadpunkSo I originaly tried to not touch much code to make patch backportable04:59
noonedeadpunkbut yeah04:59
suzhengwei__Samp: not wait when instance evacuate error, I have read your comment.04:59
samPnoonedeadpunk: i will review and add my comments on the patch. You will get the help you need for migtaion scripts05:00
samPsuzhengwei_ I think that it tpatil's comment, right?05:01
*** suzhengwei_ has quit IRC05:01
samPAnyway no more time left.05:01
tpatilsuzhengwei_: yes05:01
suzhengwei__sorry :)05:01
samPLet's discuss further on ML and gerrit. Thank you all for joining for the meeting today05:01
samPtpatil: could you please end the meeting.05:01
tpatilsuzhengwei_: NP, if you have any questions, I'm available on openstack-masakari IRC05:02
tpatilsamP: Sure05:02
tpatilThank you all for joining this meeting05:02
*** jmasud has joined #openstack-meeting05:02
tpatilTake care, Bye05:02
tpatil#endmeeting05:02
samPbye05:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"05:02
suzhengwei__Bye05:02
openstackMeeting ended Tue May 19 05:02:31 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-05-19-04.02.html05:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-05-19-04.02.txt05:02
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-05-19-04.02.log.html05:02
*** samP has quit IRC05:02
*** suzhengwei__ has quit IRC05:02
*** njohnston has quit IRC05:10
*** JangwonLee__ has joined #openstack-meeting05:15
*** JangwonLee has joined #openstack-meeting05:17
*** JangwonLee_ has quit IRC05:18
*** links has joined #openstack-meeting05:19
*** JangwonLee__ has quit IRC05:21
*** tpatil has quit IRC05:21
*** jmasud has quit IRC05:25
*** jmasud has joined #openstack-meeting05:29
*** JangwonLee_ has joined #openstack-meeting05:29
*** JangwonLee has quit IRC05:34
*** JangwonLee_ has quit IRC05:36
*** jmasud has quit IRC05:40
*** JangwonLee has joined #openstack-meeting05:47
*** JangwonLee has quit IRC05:57
*** JangwonLee_ has joined #openstack-meeting05:57
*** jmasud has joined #openstack-meeting05:58
*** yasufum has joined #openstack-meeting06:00
*** JangwonLee__ has joined #openstack-meeting06:04
*** JangwonLee_ has quit IRC06:08
*** hyunsikyang__ has joined #openstack-meeting06:09
*** JangwonLee has joined #openstack-meeting06:09
*** JangwonLee__ has quit IRC06:12
*** hyunsikyang has quit IRC06:12
*** jmasud has quit IRC06:18
*** jmasud has joined #openstack-meeting06:19
*** keiko-k has joined #openstack-meeting06:25
*** jmasud has quit IRC06:45
*** slaweq has joined #openstack-meeting06:46
*** belmoreira has joined #openstack-meeting06:47
*** ircuser-1 has joined #openstack-meeting06:49
*** jamesmcarthur has quit IRC06:49
*** jamesmcarthur has joined #openstack-meeting06:50
*** rpittau|afk is now known as rpittau06:51
*** jamesmcarthur has quit IRC06:55
*** tetsuro_ has joined #openstack-meeting07:01
*** tetsuro has quit IRC07:04
*** maciejjozefczyk has joined #openstack-meeting07:10
*** jamesmcarthur has joined #openstack-meeting07:14
*** jamesmcarthur has quit IRC07:16
*** jamesmcarthur has joined #openstack-meeting07:17
*** ttsiouts has joined #openstack-meeting07:18
*** jamesmcarthur has quit IRC07:22
*** jamesmcarthur has joined #openstack-meeting07:23
*** TheJulia has quit IRC07:24
*** mnasiadka has quit IRC07:25
*** mnasiadka has joined #openstack-meeting07:27
*** TheJulia has joined #openstack-meeting07:29
*** evrardjp has joined #openstack-meeting07:31
*** ykatabam has quit IRC07:31
*** evrardjp has quit IRC07:32
*** ralonsoh has joined #openstack-meeting07:33
*** evrardjp has joined #openstack-meeting07:34
*** witek has joined #openstack-meeting07:35
*** ociuhandu has joined #openstack-meeting07:38
*** vishalmanchanda has quit IRC07:39
*** ykatabam has joined #openstack-meeting07:42
*** JangwonLee_ has joined #openstack-meeting07:51
*** masazumi-ota has joined #openstack-meeting07:54
*** JangwonLee has quit IRC07:54
*** ueha has joined #openstack-meeting08:00
*** lpetrut has joined #openstack-meeting08:01
*** jaeeeun has joined #openstack-meeting08:01
*** Hiep_mq has joined #openstack-meeting08:02
*** yoshito-ito has joined #openstack-meeting08:02
*** Donghun has joined #openstack-meeting08:02
*** Liang has joined #openstack-meeting08:03
*** ociuhandu has quit IRC08:03
yasufumhi08:03
*** ttsiouts has quit IRC08:03
*** ociuhandu has joined #openstack-meeting08:04
masazumi-otaHello08:04
yoshito-itohi08:04
*** ttsiouts has joined #openstack-meeting08:04
uehaHi08:04
Lianghi08:05
hyunsikyang__Hi all08:06
*** e0ne has joined #openstack-meeting08:06
JangwonLee_hi08:06
*** ociuhandu has quit IRC08:06
jaeeeunhi08:06
*** ociuhandu has joined #openstack-meeting08:06
keiko-k #startmeeting Tacker08:06
hyunsikyang__OK08:07
keiko-kyasufum could you start Tacker meeting?08:07
yasufumsure08:07
keiko-kseems irc command does not work for me08:07
hyunsikyang__oh.08:07
yasufumreally?08:07
keiko-kplz try08:07
hyunsikyang__#startmeeting Tacker08:07
yasufum#startmeeting tacker08:07
openstackMeeting started Tue May 19 08:07:56 2020 UTC and is due to finish in 60 minutes.  The chair is hyunsikyang__. Information about MeetBot at http://wiki.debian.org/MeetBot.08:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:07
*** openstack changes topic to " (Meeting topic: Tacker)"08:07
openstackThe meeting name has been set to 'tacker'08:07
*** yaawang has quit IRC08:08
openstackyasufum: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.08:08
keiko-kThanks08:08
hyunsikyang__sorry I just try test it..08:08
keiko-kthat's okay08:08
yasufumthanks08:08
hyunsikyang__What is the today's topic?08:09
*** yaawang has joined #openstack-meeting08:09
yasufumI would like to continue discussion for networking-sfc today08:09
hyunsikyang__can we discuss about networing-sfc?08:09
hyunsikyang__ok08:09
hyunsikyang__#topic networking-sfc08:09
yasufumalthough takahashi-san does not join yet08:09
*** openstack changes topic to "networking-sfc (Meeting topic: Tacker)"08:09
yasufum#link https://etherpad.opendev.org/p/tacker-meeting08:09
hyunsikyang__Our team try to cover networking-sfc part:)08:10
amotokihi08:10
amotokiI am here from the neutron perspective. I originally raised networking-sfc topic to takahashi-san internally.08:10
hyunsikyang__Hi amotoki08:11
yasufumhi08:11
keiko-khello08:11
hyunsikyang__hi08:11
masazumi-otahi08:11
uehahi08:11
amotokigo ahead :)08:11
hyunsikyang__So, we will start it from the current status of networking sfc in tacker.08:12
hyunsikyang__As a perspective of tacker, it is important features. So, I want to maintain it.08:13
yasufumDo you mean as a core reviwer?08:14
hyunsikyang__yes.08:15
yasufumI can contribute as a +1 reviwer.08:16
hyunsikyang__thx. It is good feature for tacker. We will start to check networking sfc feature in tacker internally.08:16
yasufumamotoki, do you know how many contributers required for maintaining the project roughly?08:17
*** ociuhandu has quit IRC08:17
amotokiyasufum: roughly speaking, there is NO contirbutors specific to networking-sfc.08:17
amotokineutron core team is helping the sfc reviews from the maintenance perspectivve08:18
amotokibut the neutron core team have no good knowledge on sfc features.08:18
*** ociuhandu has joined #openstack-meeting08:18
amotokiit just covers gate failures and topics which are neutron-wide.08:18
amotokithat's the current status.08:18
*** yaawang has quit IRC08:19
amotokiso it would be nice if folks from tacker team can be involved in reviews in networkng-sfc.08:19
amotokiyasufum: sorry. I misunderstood your question.08:20
amotokiyour question was how many contributors are required.08:20
yasufumyes08:20
amotokiI am not sure the right number08:20
amotokiI think we can do small start just by checking reviews and so on together.08:21
*** yaawang has joined #openstack-meeting08:21
hyunsikyang__right08:21
amotokiperhaps what we need is volunteers for reviewing/triaging bugs from feature perspective.08:22
yasufumneuron cores continue add +2 for merging, right?08:22
*** ykatabam has quit IRC08:23
*** ociuhandu has quit IRC08:23
hyunsikyang__amotoki, If you know the feature link, please update it here.08:23
amotokiyasufum: what do you mean by "add +2"?08:23
yasufumI wonder how we check and merge patches08:23
yasufumMerging patch requires one or two +2 basically, right?08:24
amotokiyasufum: yes, +W right is needed.08:24
amotokithere are several options to start.08:24
amotokithe one is to consider +1 from folks familiar with sfc (like tacker team) as +2 and merge patches by the neutron team08:25
amotokithe other is to add tacker team to the netwokring-sfc core team.08:25
yasufumI see08:26
yasufumI though second one, but I understand it can be flexible.08:26
amotokithe first one would be a step to networking-sfc core reviewers.08:27
amotokithe second option sounds like a co-maintenance of netwokring-sfc by neutron and tacker team together.08:27
amotokiI have no strong option on this.08:28
amotokico-maintenace sounds a good option.08:29
amotokifor example, the horizon team do similar for horizon plugins.08:29
*** takahashi-tsc has joined #openstack-meeting08:30
takahashi-tscSorry for late...08:30
yasufumhi08:30
hyunsikyang__Hi08:30
yasufumI am not sure about scheme of co-maintenance, but it seems good.08:32
amotokiwhat are unclear? for example, what roles are expected?08:34
yasufumyes, that’s right08:34
yasufumbut I can learn from08:35
*** jamesmcarthur has quit IRC08:35
amotokifrom the neutron governance perspective, we have point of contacts per sub project like networking-sfc08:36
amotokihttps://docs.openstack.org/neutron/latest/contributor/policies/neutron-teams.html#sub-project-lieutenants08:36
amotokiit is called as "Lieutenants " in the neutron team08:37
yasufumthanks08:38
hyunsikyang__Like a before, why don't you take a role of lieutenant? yasufum?08:38
amotokithe reason I raised this topic this time is we didn't do it officially.08:39
amotokiI talked with dharmendra directly and he said he could be a contact for netwokring-sfc in Ussuri cycle.08:39
hyunsikyang__ah.08:39
amotokiI think it is better to disucss it as a team.08:40
hyunsikyang__OK. I thought he left this team:)08:40
amotokiyeah, he changed companies during ussuri cycle.08:40
yasufumhyunsikyang: I am not sure to make a time for the role now.08:41
yasufumpls continue to talk on next meeting or tacker IRC.08:42
amotokipersonally (from my hat of neutron) it would be great if the tacker team is involved in development of networking-sfc.08:42
yasufumI think so08:42
hyunsikyang__thanks amotoki, we are trying to join for that.08:42
hyunsikyang__if dharmendra can do it continueously, just leave it.08:43
hyunsikyang__and tacker team just support it.08:44
amotokilet me summarize what the neutron team do on a stadium project. I think it helps better understanding.08:45
hyunsikyang__Anyway, now tacker team have a consensus about joining networking-sfc, let's decide concrete plan for that.08:45
hyunsikyang__yes08:45
hyunsikyang__If you have a time, please share it anytime in tacker IRC.08:45
amotokihyunsikyang__: sure. what is better?08:46
amotokihyunsikyang__: I am usually not there, so I can join when needed.08:46
amotokis/what/when/08:47
hyunsikyang__ok.08:47
amotokiI think you have more topics in this meeting. let's cover it later.08:48
hyunsikyang__OK:)08:48
yasufumthanks, amotoki08:48
hyunsikyang__let's make a list for that later and decide it during the vPTG.08:48
hyunsikyang__thanks.08:49
hyunsikyang__yasufum, do we have more topic, today?08:50
yasufumyes,08:50
yasufumdo you some other topics, everyone?08:50
yasufumfor next PTG, or patch review08:51
yasufumor so08:51
hyunsikyang__I don't have it. today.08:51
yoshito-itolet me ask about C-VNF topic in vPTG08:51
yasufum#link https://etherpad.opendev.org/p/Tacker-PTG-Victoria08:52
hyunsikyang__ok:)08:52
yoshito-itoI'm preparing a spec for CNF operation based on ETSI specifications08:52
hyunsikyang__you mean that CISM?08:53
hyunsikyang__we are also prepare it. if CISM is right.08:53
yoshito-itoYes08:53
yoshito-itoI assume we can extend the existing Kubernete infra driver to support vnflcm related operation as VNF08:54
hyunsikyang__right08:54
hyunsikyang__So we are preparing it.08:54
hyunsikyang__Now, kubernetes in tacker is not scalable, and not correspond to ETSI spec.08:55
hyunsikyang__So, It needs it.08:55
yoshito-itothen how about sharing the specs before vPTG?08:55
hyunsikyang__what is the mean of spec?08:55
hyunsikyang__blueprint?08:55
yoshito-itoblueprint and spec for V cycle08:56
hyunsikyang__okie:) good.08:56
yoshito-itoI'll talk to yasufum how to share our specs and let me discuss at IRC or next meeting08:57
hyunsikyang__ok08:58
yoshito-itothanks08:58
amotokidoes anyone add the networking-sfc topic to the vPTG etherpad?08:59
yasufumI think it is OK to share your draft on etherpad if possible08:59
amotokiIf so I can add my note there.08:59
amotokisorry for interrupt....09:00
takahashi-tscOK, I add it amotoki09:00
yasufumno problem. it is welcome09:00
amotokitakahashi-tsc: thanks09:00
hyunsikyang__thanks all09:00
yasufumcan we wrap up because it is the end of the time?09:01
hyunsikyang__ok Let's finish it.09:01
yasufumif anyone has a topic09:01
yasufumdoes not has a topic,sorry09:02
yasufumthanks hyunsikyang09:02
hyunsikyang__ok. let's finish it and if someone has a topic,let's talk in tacker IRC09:02
hyunsikyang__#endmeeting09:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:02
openstackMeeting ended Tue May 19 09:02:36 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-05-19-08.07.html09:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-05-19-08.07.txt09:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-05-19-08.07.log.html09:02
yasufumbye09:02
*** noonedeadpunk has left #openstack-meeting09:03
*** ociuhandu has joined #openstack-meeting09:07
*** masahito has joined #openstack-meeting09:08
*** jaeeeun has quit IRC09:11
*** masazumi-ota has quit IRC09:14
*** takahashi-tsc has quit IRC09:15
*** Donghun has quit IRC09:15
*** vishalmanchanda has joined #openstack-meeting09:24
*** ociuhandu has quit IRC09:25
*** ttsiouts has quit IRC09:25
*** ociuhandu has joined #openstack-meeting09:26
*** ykatabam has joined #openstack-meeting09:27
*** links has quit IRC09:33
*** ttsiouts has joined #openstack-meeting09:35
*** ttsiouts has quit IRC10:10
*** ueha has quit IRC10:14
*** tetsuro_ has quit IRC10:17
*** rpittau is now known as rpittau|bbl10:31
*** ttsiouts has joined #openstack-meeting10:34
*** jamesmcarthur has joined #openstack-meeting10:36
*** yasufum has quit IRC10:38
*** jamesmcarthur has quit IRC10:40
*** masahito has quit IRC10:56
*** ueha has joined #openstack-meeting11:01
*** keiko-k has quit IRC11:09
*** ykatabam has quit IRC11:33
*** eharney has quit IRC11:39
*** ociuhandu has quit IRC11:40
*** rfolco|rover|off has joined #openstack-meeting11:42
*** ociuhandu has joined #openstack-meeting11:42
*** rfolco|rover|off is now known as rfolco|rover11:44
*** ociuhandu has quit IRC11:47
*** njohnston_ has joined #openstack-meeting11:54
*** raildo has joined #openstack-meeting11:57
*** rpittau|bbl is now known as rpittau12:04
*** jawad_axd has joined #openstack-meeting12:05
*** ueha has quit IRC12:21
*** TrevorV has joined #openstack-meeting12:30
*** ttsiouts has quit IRC12:42
*** ttsiouts has joined #openstack-meeting12:43
*** ociuhandu has joined #openstack-meeting12:57
*** ttsiouts has quit IRC13:06
*** ociuhandu has quit IRC13:06
*** vishalmanchanda has quit IRC13:09
*** ttsiouts has joined #openstack-meeting13:10
*** eharney has joined #openstack-meeting13:13
*** munimeha1 has joined #openstack-meeting13:23
*** dklyle has quit IRC13:25
*** david-lyle has joined #openstack-meeting13:25
*** david-lyle is now known as dklyle13:25
*** ociuhandu has joined #openstack-meeting13:26
*** ociuhandu has quit IRC13:31
*** psachin has quit IRC13:35
*** Hiep_mq has quit IRC13:41
*** ociuhandu has joined #openstack-meeting13:48
*** lpetrut has quit IRC13:52
*** tetsuro has joined #openstack-meeting13:52
*** ociuhandu has quit IRC13:54
*** lajoskatona has joined #openstack-meeting13:56
*** mlavalle has joined #openstack-meeting13:57
slaweq#startmeeting networking14:00
openstackMeeting started Tue May 19 14:00:13 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
slaweqhi14:00
njohnston_o/14:00
rubasovo/14:00
lajoskatonao/14:00
*** njohnston_ is now known as njohnston14:00
mlavalleo/14:00
amotokio/14:01
slaweqok, lets start the meeting14:01
slaweq#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
slaweqfirst, the most important one:14:01
*** shintaro has joined #openstack-meeting14:02
slaweqWe released Ussuri version! Congrats everyone and thanks for Your hard work!14:02
slaweqhttps://releases.openstack.org/ussuri/14:02
bcafarelo/14:02
njohnston\o/14:02
bcafarel(and \o/ too)14:02
*** jlibosva has joined #openstack-meeting14:02
mlavalle++14:03
slaweqand the second one is related to this14:03
slaweqwe are now in the Victoria cycle https://releases.openstack.org/victoria/schedule.html14:03
slaweqVictoria-1 milestone is in the week of Jun 15th so in 4 weeks14:03
*** tetsuro has quit IRC14:04
slaweqand the Victoria release is planned for 16th October14:04
ralonsohhi (sorry)14:05
slaweqand the next one, related to the previous one14:05
slaweqVictoria PTG (virtual) is in 2 weeks14:05
slaweqplanning etherpad: https://etherpad.openstack.org/p/neutron-victoria-ptg - next week I will start planning sessions so would be good to have list of topics more or less finalized,14:05
slaweqRegistration is live: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014649.html - if You didn't yet, please register :)14:06
slaweqwe will have nova-neutron session on Friday 13:00 UTC - and also we will discuss on this session some topics related to Nova and Cyborg together14:07
slaweqif You are interested in some topics related to the FPGA and smartNICs, You should mark this slot in Your calendar :)14:08
slaweqand that's all announcements which I have for You today14:09
slaweqanything else You want to announce now maybe?14:09
slaweqok, so lets move on14:10
slaweqnext topic14:10
slaweq#topic Blueprints14:10
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:10
slaweqBPs for Victoria-1 are here: https://launchpad.net/neutron/+milestone/victoria-114:11
slaweqI have questions about 2 of them14:11
slaweqhttps://blueprints.launchpad.net/neutron/+spec/dns-records-in-neutron - mlavalle, can You be approver of this one?14:11
mlavalleyes14:11
slaweqthx a lot14:11
slaweqand I have the same question for amotoki regarding https://blueprints.launchpad.net/neutron/+spec/sg-sharing-as-readonly14:12
*** jawad_axd has quit IRC14:12
slaweqamotoki: would You mind if I would set You as approver of this one?14:12
amotokiI am fine with that14:12
slaweqit's related to the RBAC and You are an expert in this area IMO14:12
slaweqthx a lot14:12
*** jawad_axd has joined #openstack-meeting14:12
slaweqany other updates about BPs do You have for today maybe?14:13
slaweqamotoki, for this sharing as readonly BP we already merged spec https://review.opendev.org/#/c/724207/14:14
slaweqjust FYI if You somehow missed that :)14:14
amotokislaweq: yeah, I noticed it a couple of days ago14:15
slaweqamotoki: ok :)14:15
slaweqmlavalle: and we also have proposed spec for https://blueprints.launchpad.net/neutron/+spec/dns-records-in-neutron14:16
slaweqhttps://review.opendev.org/#/c/726904/14:16
*** shintaro has quit IRC14:16
slaweqbut I didn't have time yet to look at it14:16
mlavallethere yes14:16
mlavalleI'll review it today14:16
slaweqthx14:17
*** jawad_axd has quit IRC14:18
slaweqok, so if there is nothing else related to BPs today, lets move on to the next topic14:18
slaweq#topic Community goals14:18
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:19
slaweqany updates on Migrate to zuulv3 ?14:19
njohnstonFor Zuulv3, aside from the work still needed on networking-midonet, the main thing is the work lajoskatona has been doing with tosky on https://review.opendev.org/#/c/725647/14:19
njohnstonfor networking-odl grenade migration14:19
njohnstonAFAIK that is it for the goal14:20
lajoskatonayeah tosky is kind enough yo guide me through grenade depths14:20
slaweqok, thx lajoskatona for working on that14:21
slaweqas for midonet I looked into it briefly this week14:21
slaweqbut there are 2 problems with that:14:21
slaweq1. all those legacy jobs are scenario jobs which are disabled since long time as they were broken14:22
slaweq2. I'm not sure how networking-midonet will work e.g. on Centos8 now, I know there were some problems with running it on Ubuntu 18.0414:22
slaweqand also14:22
slaweq3. I really don't have time to focus on networking-midonet jobs too much  :/14:23
slaweqso my plan is to maybe try to do migration of the jobs and compare if they are failing in same/similar way like the legacy ones14:24
slaweqI will for sure not spent too much time on fixing those jobs14:24
slaweq*existing failures in those jobs14:25
slaweqok, lets move on to the next topic14:26
slaweq#topic Bugs14:26
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:26
slaweqrubasov was our bug deputy last week14:26
slaweqReport http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014913.html14:26
rubasovyep14:26
slaweqrubasov: do You want to discuss some of bugs today?14:26
rubasovI'd like to call your attention to the two unassigned bugs in the report14:27
rubasovboth medium14:27
rubasovand there's another in the report as incomplete, but I should go back and triage it better: https://bugs.launchpad.net/neutron/+bug/187900914:28
openstackLaunchpad bug 1879009 in neutron "attaching extra port to server raise duplicate dns-name error" [Undecided,Incomplete]14:28
rubasovthe unassigned:14:28
rubasovhttps://bugs.launchpad.net/neutron/+bug/187797714:29
openstackLaunchpad bug 1877977 in neutron "[DVR] Recovery from openvswitch restart fails when veth are used for bridges interconnection" [Medium,Confirmed]14:29
rubasovhttps://bugs.launchpad.net/neutron/+bug/187829914:29
openstackLaunchpad bug 1878299 in neutron "[floatingip port_forwarding] changing external port to used value hangs with retriable exception" [Medium,Confirmed]14:29
slaweqrubasov: thx, I had the same bugs on my list too :)14:29
rubasovall others have people working on them14:29
rubasovI guess that's all14:30
slaweqand actually I wanted to discuss about https://bugs.launchpad.net/neutron/+bug/1877977 - do we really need to keep veth interconnection still?14:30
openstackLaunchpad bug 1877977 in neutron "[DVR] Recovery from openvswitch restart fails when veth are used for bridges interconnection" [Medium,Confirmed]14:30
slaweqsorry for maybe stupid question but what is the usecase for it?14:30
ralonsohI see no reason for this14:30
slaweqwe don't test it in u/s gate at all14:30
ralonsohthere is no use case14:30
rubasovat some point in the past didn't veth and patch ports behave differently regarding to namespaces?14:31
ralonsohbut this is to link bridges14:31
ralonsohthe patch port is this logical way14:31
slaweqyes, this is to connect bridges together, eg. br-int and br-ex14:31
*** andrebeltrami has joined #openstack-meeting14:31
rubasovralonsoh: you're right that's irrelevant here14:31
slaweqI'm not talking about using veth in the e.g. L3 agent - that's different story14:32
slaweqdo You think we can add topic about deprecation of this option to the PTG agenda?14:34
ralonsoh+114:34
njohnston+114:34
amotoki+1 for the PTG topic. i see the reason for ovs_use_veth, but I am not sure about use_veth_interconnection.14:34
slaweqok, thx I will add it to the etherpad14:35
*** jamesmcarthur has joined #openstack-meeting14:36
slaweqok, regarding https://bugs.launchpad.net/neutron/+bug/1878299 I think this should be raised on L3 subteam meeting14:37
openstackLaunchpad bug 1878299 in neutron "[floatingip port_forwarding] changing external port to used value hangs with retriable exception" [Medium,Confirmed]14:37
slaweqany other bugs You want to discuss today?14:38
slaweqok, so lets move on14:40
slaweqour bug deputy this week is maciejjozefczyk and I already ensure that he is aware of it :)14:40
slaweqand next week will be ralonsoh's time14:41
maciejjozefczyk\o/14:41
ralonsohups...14:41
slaweqralonsoh: why "ups..."? :D14:41
ralonsohmy first time!14:41
slaweqYou should say "YAY"14:41
ralonsohno no14:41
slaweq;)14:41
bcafarelyou heard it everybody, fill as many launchpad bugs as possible next week!14:42
slaweqLOL14:42
ralonsohhahaha14:42
maciejjozefczykbcafarel, but not this week :D14:42
slaweqok, last topic for today14:42
slaweq#topic On Demand Agenda14:43
*** openstack changes topic to "On Demand Agenda (Meeting topic: networking)"14:43
slaweqI see one small topic there14:43
slaweqReview https://review.opendev.org/#/c/66546714:43
slaweq    please review this and provide feedback so it can be merged.14:43
slaweqI guess it's added by the owner of the patch14:43
ralonsohok14:44
slaweqI think that would be great if ralonsoh and rubasov could take a look into it especially14:44
slaweqralonsoh: as an SR-IOV and Intel expert14:44
slaweqand rubasov as trunks expert14:44
ralonsohI still have some concerns about the shell commands calls14:44
ralonsohI'll comment on gerrit14:44
slaweqand of course any other reviews are welcome :)14:44
slaweqthx ralonsoh14:45
rubasovit's huge but I'll digest it in pieces14:45
slaweqrubasov: yes, it is huge :)14:45
*** ociuhandu has joined #openstack-meeting14:46
slaweqany other on demand topics?14:46
maciejjozefczykyes :)14:46
maciejjozefczyk#link https://review.opendev.org/#/c/720464/14:46
maciejjozefczyk#link https://review.opendev.org/#/c/715157/14:47
maciejjozefczykCan I ask you folks to review those patches? There are already a few iterations of reviews but looks like its a bit stuck14:47
ralonsohsure14:47
maciejjozefczykFlavio pointed a few nits I'm going to update soon, but I feel it still needs some eyes :)14:47
slaweqsure maciejjozefczyk14:47
maciejjozefczykIt is needed to have a basic support for routed provider networks with OVN :)14:48
maciejjozefczykthanks :)14:48
slaweqmlavalle: please take a look at this as routed networks expert :)14:48
*** Liang has quit IRC14:48
mlavallewill do14:48
slaweqThank You14:48
maciejjozefczykthanks :) mlavalle14:49
*** jawad_axd has joined #openstack-meeting14:49
mlavallein my pile14:49
bcafareloops looks like one was already in my pile14:49
bcafarelI will move them up higher in the pile :/14:50
maciejjozefczykthanks guys :)14:51
slaweqanything else for today?14:51
slaweqok, if not then thx for attending and have a great week14:52
slaweqo/14:52
bcafarelo/14:52
slaweq#endmeeting14:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:53
openstackMeeting ended Tue May 19 14:53:00 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-05-19-14.00.html14:53
lajoskatonabye14:53
rubasovbye14:53
ralonsohbye14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-05-19-14.00.txt14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-05-19-14.00.log.html14:53
njohnstono/14:53
amotokio/14:53
maciejjozefczyk\o14:53
*** jawad_axd has quit IRC14:54
*** lajoskatona has left #openstack-meeting14:55
ralonsohsorry I'm very late!15:09
ralonsoh#startmeeting neutron_qos15:10
openstackMeeting started Tue May 19 15:10:03 2020 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:10
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:10
openstackThe meeting name has been set to 'neutron_qos'15:10
ralonsohactually there is no agenda15:10
ralonsohif someone lurking the meeting wants to add something, she/he is welcome15:10
ralonsoh#topic Open Discussion15:10
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:10
ralonsohnow I'm here, I'll comment that https://review.opendev.org/#/c/722415/ is almost finished (just need to bump ovsdbapp version)15:11
ralonsohbut the logic is there15:11
ralonsohok, if there are no comments in the next minute, I'll end the meeting15:12
ralonsohok, thank you and see you in two weeks15:13
ralonsoh#endmeeting15:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:13
openstackMeeting ended Tue May 19 15:13:55 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-05-19-15.10.html15:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-05-19-15.10.txt15:14
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-05-19-15.10.log.html15:14
*** jawad_axd has joined #openstack-meeting15:20
*** armax has joined #openstack-meeting15:23
*** ttsiouts has quit IRC15:27
*** gyee has joined #openstack-meeting15:46
*** ociuhandu has quit IRC15:55
*** ociuhandu has joined #openstack-meeting15:55
*** jawad_axd has quit IRC15:56
*** ociuhandu has quit IRC15:59
*** ociuhandu has joined #openstack-meeting16:00
*** lpetrut has joined #openstack-meeting16:02
*** jawad_axd has joined #openstack-meeting16:02
*** ttsiouts has joined #openstack-meeting16:04
*** ttsiouts has quit IRC16:10
*** jmasud has joined #openstack-meeting16:12
*** witek has quit IRC16:16
*** jlibosva has quit IRC16:21
*** rpittau is now known as rpittau|afk16:22
*** jmasud has quit IRC16:26
*** jmasud has joined #openstack-meeting16:31
*** yasufum has joined #openstack-meeting16:34
*** yasufum_ has joined #openstack-meeting16:37
*** yasufum has quit IRC16:38
*** yasufum_ is now known as yasufum16:38
*** lpetrut has quit IRC16:50
*** ayoung has joined #openstack-meeting16:50
*** jmasud has quit IRC16:51
*** ociuhandu has quit IRC17:01
*** ociuhandu has joined #openstack-meeting17:02
*** alistarle has joined #openstack-meeting17:04
*** ociuhandu has quit IRC17:04
*** ociuhandu has joined #openstack-meeting17:04
*** jamesmcarthur has quit IRC17:04
*** ttsiouts has joined #openstack-meeting17:08
*** ttsiouts has quit IRC17:09
*** jamesmcarthur has joined #openstack-meeting17:09
*** jawad_ax_ has joined #openstack-meeting17:23
*** jamesmcarthur has quit IRC17:24
*** jawad_axd has quit IRC17:27
*** ociuhandu has quit IRC17:28
*** ociuhandu has joined #openstack-meeting17:29
*** jmasud has joined #openstack-meeting17:29
*** jmasud has quit IRC17:31
*** evrardjp has quit IRC17:32
*** jmasud has joined #openstack-meeting17:32
*** evrardjp has joined #openstack-meeting17:34
*** ociuhandu has quit IRC17:41
*** jawad_ax_ has quit IRC17:45
*** jawad_axd has joined #openstack-meeting17:45
*** ayoung has quit IRC17:47
*** jamesmcarthur has joined #openstack-meeting17:50
*** ayoung has joined #openstack-meeting17:51
*** alistarle has quit IRC17:58
*** yasufum has quit IRC18:00
*** e0ne has quit IRC18:02
*** ayoung has quit IRC18:06
*** e0ne has joined #openstack-meeting18:07
*** ayoung has joined #openstack-meeting18:10
*** jamesmcarthur has quit IRC18:12
*** jamesmcarthur has joined #openstack-meeting18:14
*** jamesmcarthur has quit IRC18:17
*** munimeha1 has quit IRC18:17
*** jamesmcarthur has joined #openstack-meeting18:17
*** belmoreira has quit IRC18:24
*** jamesmcarthur has quit IRC18:29
*** jamesmcarthur has joined #openstack-meeting18:30
*** ociuhandu has joined #openstack-meeting18:31
*** ayoung has quit IRC18:31
*** ayoung has joined #openstack-meeting18:33
*** rcernin has quit IRC18:34
*** diablo_rojo has joined #openstack-meeting18:53
*** jawad_axd has quit IRC18:53
*** ralonsoh has quit IRC18:58
*** jmasud has quit IRC19:03
*** raildo has quit IRC19:04
*** jmasud has joined #openstack-meeting19:04
*** ociuhandu has quit IRC19:09
*** ociuhandu has joined #openstack-meeting19:09
*** ociuhandu has quit IRC19:15
*** raildo has joined #openstack-meeting19:19
*** ayoung has quit IRC19:25
*** ayoung has joined #openstack-meeting19:29
*** jawad_axd has joined #openstack-meeting19:50
*** ayoung has quit IRC19:55
*** TrevorV has quit IRC20:01
*** moguimar has quit IRC20:39
*** moguimar has joined #openstack-meeting20:39
*** jawad_axd has quit IRC20:44
*** jmasud has quit IRC20:53
*** jmasud has joined #openstack-meeting21:00
*** jmasud has quit IRC21:12
*** jamesmcarthur has quit IRC21:20
*** jamesmcarthur has joined #openstack-meeting21:24
*** raildo has quit IRC21:24
*** jamesmcarthur has quit IRC21:31
*** maciejjozefczyk has quit IRC21:31
*** jamesmcarthur has joined #openstack-meeting21:32
*** jamesmcarthur has quit IRC21:34
*** jamesmcarthur has joined #openstack-meeting21:34
*** jamesmcarthur has quit IRC21:37
*** jamesmcarthur has joined #openstack-meeting21:39
*** slaweq has quit IRC21:41
*** jamesmcarthur has quit IRC21:41
*** jamesmcarthur has joined #openstack-meeting21:41
*** ykatabam has joined #openstack-meeting21:44
*** jmasud has joined #openstack-meeting22:21
*** jmasud has quit IRC22:24
*** jamesmcarthur has quit IRC22:33
*** jamesmcarthur has joined #openstack-meeting22:33
*** jamesmcarthur_ has joined #openstack-meeting22:40
*** jamesmcarthur has quit IRC22:44
*** ykatabam has quit IRC22:47
*** rcernin has joined #openstack-meeting22:56
*** jmasud has joined #openstack-meeting23:00
*** jamesmcarthur_ has quit IRC23:05
*** jamesmcarthur has joined #openstack-meeting23:12
*** ykatabam has joined #openstack-meeting23:19
*** andrebeltrami has quit IRC23:19
*** jamesmcarthur has quit IRC23:56
*** jamesmcarthur has joined #openstack-meeting23:57

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!