Tuesday, 2017-08-01

*** yamamoto has quit IRC00:01
*** https_GK1wmSU has joined #openstack-meeting-500:04
*** yamamoto has joined #openstack-meeting-500:05
*** https_GK1wmSU has left #openstack-meeting-500:07
*** ricolin has joined #openstack-meeting-500:14
*** iceyao has joined #openstack-meeting-501:09
*** yamamoto has quit IRC01:25
*** yamamoto has joined #openstack-meeting-501:29
*** ricolin has quit IRC01:34
*** yamamoto has quit IRC01:51
*** yamamoto has joined #openstack-meeting-501:56
*** yamamoto has quit IRC02:07
*** yamahata has quit IRC02:08
*** yamamoto has joined #openstack-meeting-502:19
*** https_GK1wmSU has joined #openstack-meeting-502:30
*** https_GK1wmSU has left #openstack-meeting-502:32
*** ricolin has joined #openstack-meeting-502:42
*** raddaoui has quit IRC02:54
*** yamamoto has quit IRC03:01
*** yamamoto has joined #openstack-meeting-503:06
*** yamamoto has quit IRC03:21
*** yamamoto has joined #openstack-meeting-503:24
*** yamamoto has quit IRC03:36
*** marst has joined #openstack-meeting-503:36
*** yamamoto has joined #openstack-meeting-503:44
*** iceyao has quit IRC03:56
*** yamamoto has quit IRC04:04
*** yamamoto has joined #openstack-meeting-504:09
*** iceyao has joined #openstack-meeting-504:21
*** iceyao has quit IRC04:26
*** iceyao has joined #openstack-meeting-504:39
*** iceyao has quit IRC04:44
*** iceyao has joined #openstack-meeting-504:45
*** iceyao has quit IRC05:08
*** iceyao has joined #openstack-meeting-505:35
*** iceyao has quit IRC05:40
*** yamahata has joined #openstack-meeting-506:01
*** iceyao has joined #openstack-meeting-506:03
*** iceyao has quit IRC06:08
*** iceyao has joined #openstack-meeting-506:12
*** korzen has joined #openstack-meeting-506:30
*** ralonsoh has joined #openstack-meeting-506:52
*** aarefiev_afk is now known as aarefiev07:28
*** markvoelker has quit IRC08:30
*** markvoelker has joined #openstack-meeting-508:31
*** markvoelker has quit IRC08:35
*** ricolin has quit IRC08:51
*** ralonsoh has quit IRC09:10
*** ralonsoh has joined #openstack-meeting-509:11
*** yamahata has quit IRC09:17
*** yamamoto has quit IRC09:37
*** marst_ has joined #openstack-meeting-509:38
*** marst has quit IRC09:38
*** yamamoto has joined #openstack-meeting-509:57
*** yamamoto has quit IRC10:08
*** yamamoto has joined #openstack-meeting-510:25
*** markvoelker has joined #openstack-meeting-510:31
*** iceyao has quit IRC10:52
*** iceyao has joined #openstack-meeting-510:55
*** iceyao has quit IRC11:00
*** markvoelker has quit IRC11:05
*** yamamoto has quit IRC11:17
*** markvoelker has joined #openstack-meeting-511:30
*** yamamoto has joined #openstack-meeting-511:32
*** yamamoto has quit IRC11:49
*** yamamoto has joined #openstack-meeting-512:49
*** yamamoto has quit IRC12:59
*** iceyao has joined #openstack-meeting-513:09
*** korzen has quit IRC13:31
*** marst_ has quit IRC14:28
*** marst has joined #openstack-meeting-514:35
*** kiennt has joined #openstack-meeting-514:44
*** korzen has joined #openstack-meeting-514:51
*** alraddarla has joined #openstack-meeting-514:57
srwilkers#startmeeting openstack-helm15:00
openstackMeeting started Tue Aug  1 15:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is srwilkers. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
korzenhello15:00
srwilkershello everyone o/15:00
alraddarlao/15:00
srwilkersgot the link out late -- here's the etherpad for today.  let's take about 5 minutes and add any agenda items we'd like to discuss today:  https://etherpad.openstack.org/p/openstack-helm-meeting-2017-08-0115:00
*** lrensing has joined #openstack-meeting-515:01
lrensingo/15:01
jayahno/15:01
*** felipemonteiro has joined #openstack-meeting-515:02
srwilkersnice :) let's get to it then15:05
srwilkers#topic release schedule15:05
*** openstack changes topic to "release schedule (Meeting topic: openstack-helm)"15:05
srwilkersv1k0d3n: floors yours15:05
*** grantd_ecg has joined #openstack-meeting-515:06
srwilkersportdirect: ill defer to you since i've seen you've left comments here15:07
v1k0d3nhey all o/15:07
srwilkershey dude :)15:07
srwilkersfloors yours15:07
v1k0d3ncrazy morning, sorry for being late.15:07
portdirectoh - its started -lol15:07
v1k0d3nso i see that this is a topic at PTG too...15:07
v1k0d3nbut can we at least get the ball rolling a bit on RC releases?15:08
*** StaceyF has joined #openstack-meeting-515:08
portdirectI think we need to define what we mean by a release15:08
portdirectand what that entails15:08
portdirectfrom my perspective there are two criteria:15:08
portdirect1) we work :D15:08
*** felipemonteiro has quit IRC15:08
v1k0d3nit would help first with point in time releases, and it would also help with getting vendors involved...because they can reliably say "use this rc release with our code". contrail is a good example of this, who is currently using tiller v2.4.2. as we keep moving forward...they are left behind, and this can be frustrating.15:09
portdirect2) we are locking in a version of our format/layout of charts15:09
portdirectv1k0d3n: they are using tiller 2.5 on their master15:09
portdirecti"ll push them to update their public code15:10
v1k0d3nyes...working is good. i think identifying _what_ works is good enough for RC releases though. and of course documenting what we know _doesn't_ work.15:10
v1k0d3nwould that be ok?15:10
v1k0d3ni thought i was using master when attempting to package. i will check again.15:10
v1k0d3ni am starting to work with them here as well. also folks on the ODL side.15:11
v1k0d3nthanks for the extra push portdirect  :)15:11
portdirectnice - we have a bm lab that we are working with juniper here15:11
v1k0d3nbut would RC releases be acceptable for the team?15:11
v1k0d3nunder the conditions that we document what does/doesn't work for that RC?15:12
portdirectI'd be more comfortble defining the criteria for a release before pushing for one15:12
portdirectcan we make this a topic at ptg15:12
jayahn+1 on portdirect15:12
srwilkersthere are some things that need tied up before i think setting releases is appropriate15:12
v1k0d3nthat works too. but to be fair, we've had a few releases that were mostly working at one point...and ever really branched/tagged anything. it would be nice to capture those when we hit a milestone.15:12
portdirectcurrently master always works :D15:13
v1k0d3nwith conditions ;)15:13
jayahnshould make that way. :D15:13
jayahni also would like to discuss what "dependencies" we would like to present with our release/tag policy. for exmpale, openstack version info.15:14
*** korzen has quit IRC15:14
portdirectif you were abloe to start working n the code again v1k0d3n it would be awesome - would help us get there quicker15:14
*** korzen has joined #openstack-meeting-515:14
portdirect*able15:14
v1k0d3nas a user explores openstack-helm...there's no real snapshot view of what works and what doesn't.15:14
v1k0d3ni am trying portdirect. changing jobs is pretty....disruptive. :)15:15
v1k0d3nso, i guess no on the RC releases is what i'm hearing.15:15
v1k0d3nwhich is fine...but how do we proceed. what is expected or what is the schedule, besides AT&T's 1710 and 1802?15:15
srwilkersi think it'd be appropriate to discuss this more in detail during the PTG -- i think timeboxing that decision to part of a weekly meeting is difficult15:15
korzenin order to reliably release anything, the gates and functional tests should be improved15:16
korzento make sure that ceph, ingress or any OpenStack project is working correctly15:16
v1k0d3nok, well i guess it will have to wait until PTG.15:17
srwilkersany other points of discussion here?15:18
*** makowals has quit IRC15:19
srwilkers#topic list of reviews15:19
*** openstack changes topic to "list of reviews (Meeting topic: openstack-helm)"15:19
srwilkerskorzen: floors yours to start :)15:19
korzenok, so I like I have told you last meeting15:20
korzenI have prepared the specs for the Neutron multi-SDN approach15:20
korzenI would like to have some review there15:20
korzenif everybody is on the same page15:21
srwilkerskorzen: glanced at it this morning.  looking good :)15:21
korzenthere are general approach captured:15:21
*** iceyao has quit IRC15:21
korzen#link https://review.openstack.org/#/c/487427/1    spec: Neutron multiple SDNs design15:21
korzen#link  https://review.openstack.org/#/c/489580/2    spec: Add linux bridge to Neutron chart15:21
korzenas well as detailed implementation:15:22
korzen#link https://review.openstack.org/#/c/481225       Neutron: Enable decomposition of chart into descrete manifests15:22
korzen#link  https://review.openstack.org/#/c/466293/14  Neutron: add linuxbridge daemonset and config script15:22
korzenfor those specs15:22
korzenso you can take a look at general idea15:22
korzenas well as the implementation details15:22
portdirectI need to review the working of the 1st two - but am totally happy with the direction.15:22
portdirectwe should get infra to provide another three node gate for lb15:23
portdirectand reture the two node i think15:23
portdirect*retire15:23
srwilkersyeah, two node can go as far as im concerned15:23
*** makowals has joined #openstack-meeting-515:23
korzenthanks jayahn for updating the SONA chart15:23
korzen#link  https://review.openstack.org/#/c/489500/ SONA15:23
korzenin that link, you can see how external SDN integration would look like15:24
jayahnnot me, it is siri. :)15:24
portdirect^^ lets get that in the gate too :)15:24
portdirectas without its hard for many people to review15:24
korzenyes15:25
srwilkers+115:25
jayahnany thing we need to follow up to do "lets get that in the gate too"?15:25
korzenand the docs15:25
korzen#link https://review.openstack.org/#/c/47032615:25
korzendocs: Neutron multiple SDN approach design15:25
portdirectjayahn: i'll ask for a three node for osh infra as well15:26
korzenthis is my old documentation around15:26
korzenI would need to rewrite it15:26
korzenand it should contain the overall information about networking inside OSH15:27
portdirectkorzen: if you could that would be awesome - thanks for really moving this forward15:27
srwilkerskorzen: nice15:28
korzenok, I guess I'm doen here15:28
korzendone*15:28
korzenreally hoping for the review15:28
korzen:)15:28
srwilkersany other review related topics from anyone?15:29
korzenI do not see dulek around, but his fernet tokens?15:29
korzen#link https://review.openstack.org/#/c/463730/15:30
korzenAdd support for Keystone's fernet tokens15:30
portdirectI kinda dropped the ball there15:31
portdirectreally want it15:32
portdirectbut also want it in the gate properly15:32
portdirectif dulek could add support and the docs for cron jobs then we should merge asap15:32
portdirectbut I'll try to find a window to complete my ps there15:32
korzenok15:32
portdirecthttps://review.openstack.org/#/c/484958/15:33
portdirectthough if anyone wanted to take that over I'd be greatful :)15:33
srwilkers#topic open discussion15:35
*** openstack changes topic to "open discussion (Meeting topic: openstack-helm)"15:35
srwilkersany other topics not listed to cover?15:35
jayahnnot from me15:36
jayahnah.15:36
jayahnone question about liveness check15:37
jayahnwhat is the current status on implementing liveness check?15:37
jayahnfor each service? i was following up, then it seems like ended with "we need operator feedback on this". correct?15:38
srwilkersi think the takeaway was that we'd tie that in to some of the prometheus work that was targeted15:39
*** raymaika has joined #openstack-meeting-515:40
srwilkersanything else?15:42
korzenwe agreed that the liveness should be reproted via log analyzing15:43
korzenthus the work on LMA15:44
srwilkersyep. there's been some feedback left on the LMA spec in flight.  I'll get that updated accordingly today15:44
jayahnsetting up liveness probe on each pod, that should be reported via log analyzing?15:44
korzenwe have the first idea that we should check DB connection, rabbitmq15:45
korzenand service reporting in the server, like nova-manage service list15:45
korzenas liveness check15:46
korzenbut then the conclusion was, if service is not able to connect to the DB/rabbit/nova api - can we restart the pod and expect to fix the situation?15:46
korzenso second idea is to report that some service has issues as alarms15:47
jayahnokay, i got the idea on how discussion went. :) I will also think about this more.15:48
portdirectyeah its a tricky one15:48
srwilkersyeah, feedback would be awesome. :)  can adjust as necessary15:48
jayahncan be very service / case specific.15:48
portdirectpersonally I'm very worried about restarting the pod if a dep goes down15:49
portdirectas I have nightmares of a situation cascading out of control15:49
lrensing++ portdirect15:49
portdirectin the event of a small outage of say rabbitmq15:49
lrensingdomino effect15:49
korzentrue15:49
jayahnyeah, true.15:50
korzenso we are currently working on LMA infra15:51
korzenprometheus, fluentd15:51
korzento be able to support such use-case15:51
*** grantd_ecg has quit IRC15:53
*** iceyao has joined #openstack-meeting-515:54
jayahnokay, we can end this one now, only 7min left. obviously, this requires more thinking.15:54
srwilkerssounds good :)15:54
srwilkersill go ahead and close out the meeting.  we can carry over any remaining conversation to openstack-helm.  see you there :)15:55
srwilkers#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Tue Aug  1 15:55:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-08-01-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-08-01-15.00.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-08-01-15.00.log.html15:55
korzenthanks, bye15:55
*** alraddarla has left #openstack-meeting-515:55
*** raymaika has quit IRC15:56
*** iceyao has quit IRC15:58
*** makowals has quit IRC16:07
*** kiennt has quit IRC16:07
*** makowals has joined #openstack-meeting-516:09
*** korzen has quit IRC16:16
*** ricolin has joined #openstack-meeting-516:17
*** aarefiev is now known as aarefiev_afk16:23
*** ksumit has joined #openstack-meeting-516:30
*** yamahata has joined #openstack-meeting-516:31
*** sshank has joined #openstack-meeting-516:40
*** sshank has quit IRC16:50
*** sshank has joined #openstack-meeting-516:55
*** ralonsoh has quit IRC17:02
*** yamahata has quit IRC17:43
*** markvoelker has quit IRC18:02
*** markvoelker has joined #openstack-meeting-518:02
*** yamahata has joined #openstack-meeting-518:20
*** korzen has joined #openstack-meeting-518:27
*** korzen has quit IRC18:34
*** sshank has quit IRC18:52
*** ksumit has quit IRC19:04
*** sshank has joined #openstack-meeting-519:07
*** sshank has quit IRC19:12
*** beisner_ is now known as beisner19:12
*** sshank has joined #openstack-meeting-519:48
*** marst has quit IRC21:09
*** yamamoto has joined #openstack-meeting-521:17
*** yamamoto has quit IRC21:21
*** yamamoto has joined #openstack-meeting-521:21
*** yamamoto has quit IRC21:26
*** sshank has quit IRC21:29
*** sshank has joined #openstack-meeting-521:37
*** yamamoto has joined #openstack-meeting-522:23
*** yamamoto has quit IRC22:25
*** yamamoto has joined #openstack-meeting-522:25
*** sshank has quit IRC22:57
*** sshank has joined #openstack-meeting-523:13
*** sshank has quit IRC23:17
*** markvoelker has quit IRC23:53

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