Wednesday, 2017-04-19

*** topol has quit IRC00:54
*** iceyao has joined #openstack-meeting-501:31
*** iceyao has quit IRC01:45
*** iceyao has joined #openstack-meeting-502:01
*** ricolin has joined #openstack-meeting-502:11
*** HelenYao has quit IRC02:57
*** iceyao has quit IRC03:10
*** iceyao has joined #openstack-meeting-503:37
*** iceyao has quit IRC03:42
*** iceyao has joined #openstack-meeting-504:21
*** iceyao has quit IRC04:26
*** zenirc369 has joined #openstack-meeting-504:37
*** iceyao has joined #openstack-meeting-505:01
*** iceyao has quit IRC05:06
*** markvoelker has quit IRC05:29
*** zenirc369 has quit IRC05:44
*** iceyao has joined #openstack-meeting-505:46
*** iceyao has quit IRC05:51
*** zenirc369 has joined #openstack-meeting-505:57
*** iceyao has joined #openstack-meeting-506:28
*** markvoelker has joined #openstack-meeting-506:29
*** iceyao has quit IRC06:33
*** markvoelker has quit IRC06:35
*** ralonsoh has joined #openstack-meeting-506:44
*** matrohon has joined #openstack-meeting-507:02
*** matrohon has quit IRC07:08
*** iceyao has joined #openstack-meeting-507:12
*** skazi has joined #openstack-meeting-507:16
*** markvoelker has joined #openstack-meeting-507:30
*** markvoelker has quit IRC07:35
*** racedo has joined #openstack-meeting-507:36
*** matrohon has joined #openstack-meeting-507:53
*** iceyao has quit IRC07:56
*** matrohon_ has joined #openstack-meeting-508:03
*** matrohon has quit IRC08:05
*** rarcea has joined #openstack-meeting-508:09
*** zenirc369 has quit IRC08:29
*** zenirc369 has joined #openstack-meeting-509:17
*** HelenYao has joined #openstack-meeting-509:23
*** zenirc369 has quit IRC09:45
*** aarefiev_afk is now known as aarefiev09:45
*** zenirc369 has joined #openstack-meeting-510:01
*** ralonsoh_ has joined #openstack-meeting-512:01
*** ralonsoh has quit IRC12:04
*** markvoelker has joined #openstack-meeting-512:19
*** iceyao has joined #openstack-meeting-512:31
*** zenirc369 has quit IRC12:49
*** ralonsoh__ has joined #openstack-meeting-513:01
*** ralonsoh__ is now known as ralonsoh13:01
*** ralonsoh_ has quit IRC13:04
*** topol has joined #openstack-meeting-513:40
*** mnaser has joined #openstack-meeting-513:50
*** HelenYao_ has joined #openstack-meeting-513:51
*** ksumit has joined #openstack-meeting-513:57
*** zhipeng has joined #openstack-meeting-513:59
topol#startmeeting interop_challenge14:01
openstackMeeting started Wed Apr 19 14:01:30 2017 UTC and is due to finish in 60 minutes.  The chair is topol. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: interop_challenge)"14:01
openstackThe meeting name has been set to 'interop_challenge'14:01
topolHi everyone, who is here for the interop challenge meeting today?14:01
ksumitHere!14:02
skazi_o/14:02
HelenYao_o/14:02
rarceao/14:02
vkmco/14:02
mnasero/14:02
dmelladoo/14:02
zhipengo/14:02
topolTong Li is in China today and not able to connect to IRC so I'm running the meeting today14:02
topolThe agenda for today can be found at:14:03
topol#link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-04-1914:03
topolWe can use this same etherpad to take notes14:03
zhipengTong is in Beijing ?14:03
topolYes I believe so.  The big Open Source conference being held there14:04
zhipengyeah i'm here as well14:04
zhipenglol14:04
dmelladozhipeng: just grab him along xD14:05
topolLook for him!14:05
zhipenggotta do that tmr14:05
* topol tongli needs to learn zhipeng magic tricks for conencting to irc from China14:05
zhipengtopol will Mark be here today ?14:05
topolzhipeng not sure. I dont think so14:05
topolAgenda:14:06
topol    #topic Review last meeting action items14:06
topol     #link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-12-14.01.html14:06
zhipengi think last week Mark said he could review the demo this week ?14:06
topolzhipeng which demo?14:06
topolNFV one?14:06
zhipengyep14:07
topolK, will have to take an action item on that unless Mark shows up14:07
topolsparkcollier?14:07
topolsparkycollier14:07
topolso here is what  I have14:08
zhipengsparkycollier_14:08
topolplease required information on the boston onstage etherpad.14:08
topolIdentify if your cloud is public or private on the boston onstage etherpad.14:08
topolIdentify if your cloud will be able to allow access on port 2625714:08
topolRemember to identify phase 1 only folks so they get screen time as well14:08
beisnero/14:08
dmelladoo/ hey topol, check the etherpad, I've added some topics there too14:08
dmellado;)14:09
dmelladoshould we go quickly over the in-review patches14:09
dmellado?14:09
topoldmellado sure.14:09
mnaserfyi anyone who wants to put that information - https://etherpad.openstack.org/p/interop-challenge-boston-onstage14:09
topolthe only thing Iwanted to mention is #link https://etherpad.openstack.org/p/interop-challenge-boston-onstage14:09
topolonly has 13 folks. we are missing 3. Tamara wants those added ASAP14:10
dmelladotopol: pls do note that basically vkmc and me are each other backup14:10
topolbut demallado go ahead with the in-review patches14:10
dmelladobut we'd love to make it so both of us have access and so ;)14:10
dmelladoso on the patches14:10
dmellado#link https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z14:11
topoldmellado noted.  so you won't both be on stage/14:11
dmelladofrom my side I'd love to have some eyes on https://review.openstack.org/#/c/457199/14:11
dmelladotopol: yep, exactly, but we'd need access granted for both of us, just in case14:11
topol#action all please review #link  https://review.openstack.org/#/c/457199/14:12
dmelladoon the NFV from zhipeng, could you please rebase it? a recent change has put it on merge conflict ;)14:12
dmelladohttps://review.openstack.org/#/c/439492/14:12
topol#action dmellado and vkmc please email tamara and let her know your alls intentions and cc topol and tongli14:13
dmelladowill do ;)14:13
zhipenghelen could do it14:13
vkmc:)14:13
HelenYao_dmellado: sure, I will solve the conflict14:13
*** iceyao has quit IRC14:13
*** daniela_ebert has joined #openstack-meeting-514:14
dmelladotopol: on your side I'm not sure if you'd like to make some comments on here14:14
dmelladohttps://review.openstack.org/#/c/456446/14:14
dmelladoI guess phase2 would depend on it, isn't it?14:14
topoldmellado I'll take a look14:14
dmelladoAnyone wants to comment any another patches?14:15
dmelladotopol: thanks!14:15
topoldmellado why was centOS support needed?14:15
mnasera silly randomness... https://review.openstack.org/#/c/454711/14:15
dmelladotopol: I wanted to add that on top of only having ubuntu/coreOS14:15
topolthe cockroach guys need it?14:15
mnaser(which i really really had to fix because i cant stand messed up rst links :D)14:15
dmelladobasically to mimic what's on the upstream openstack CI14:16
dmelladorarcea: I'm not sure if you'd be interested on adding opensuse there too14:16
topoldmellado do you plan to run centos on stage?14:16
dmelladotopol: well, I guess we'll all have to agree on the same image, but wanted to discuss that too14:16
rarceadmellado: might be a good idea, but short on time14:17
topolrarcea +++14:17
mnaserrarcea ++14:17
topolshort on time is correct14:17
topolI will do a review14:17
dmelladothanks topol14:17
mnaserwe need to make sure this is as stable as it gets and freeze it to avoid on-stage embarassements :X14:17
topolhoping the patch doesnt break what we have :-)14:18
dmelladowell, documentation should be good, and we have at least CI for it xD14:18
topolmnaser. yes exactly.  Need to goto critical fix only very soon14:18
dmelladoshould we go to the next topic?14:19
topoltongli and I fly to Austin next week for rehearsal.  Will be hard to get us to add anything new after that14:19
topoldmellado. sure14:19
dmelladogotcha14:19
dmellado#topic     Issues with cockroachdb container image14:19
dmelladoI sent an email to tongli about this14:19
dmelladobut it seems that there's a bug on the cockroach image14:19
vkmcso everything that is going to be on the summit has to be merged before next week?14:19
dmellado#link https://hub.docker.com/r/cockroachdb/cockroach-k8s-init/14:20
vkmcthis includes tongli's patch on having a multicluster cockroach db deploy14:20
topolvkmc that would be my preference14:20
topolbut I may get outvoted if need be14:20
dmelladohmm maybe we'll be short on time for that...14:20
dmelladoso, on here I propose to deprecate the var of custom domain name14:20
topolI'll check with Tongli to see what he's comfortable with14:20
dmelladoas it makes the cockroachdb unable to deploy14:20
mnaserif the multicluster doesnt get merged, it means phase 2 of the demo doesn't happen14:20
dmelladoidk if anyone tried that14:20
topolmnaser then we need to merge that14:21
dmellado#action review phase 2 patch (all)14:21
sparkycollier_Sorry I'm late y'all14:21
topolobviously anything needed for phase 2 we will need to get merged14:21
topolhi sparkycollier_14:21
dmelladoo/14:21
topolsome folks thought they were going to show you a demo today?14:22
sparkycollier_Oh I'm sorry14:22
dmelladotopol: if it's going to be like that maybe we should send a FF email to the ml, with the agreed date14:22
sparkycollier_I am in a car14:22
topoldmellado are we not close?14:22
mnaserdmellado ++14:23
dmelladowe are totally close14:23
topolsparkycollier. maybe demo next week then?14:23
mnaseri think having a hard cutoff would be good14:23
dmelladobut IMHO it'd be cool to have this done so folks are aware14:23
topolwhats a cutoff date everyone finds reasonable?14:23
sparkycollier_Sure next week is good14:24
topolTong and I have rehersals next Tuesday14:24
sparkycollier_We can just view it next week in Austin during rehearsal14:24
sparkycollier_I will be there14:24
*** zhipeng_ has joined #openstack-meeting-514:24
dmelladoso let's assume 1 week14:24
dmelladoat least14:24
*** zhipeng has quit IRC14:25
dmelladodoes this sound reasonable to all?14:25
mnaserso that means that on the next meeting14:25
mnaserwe close things out and dont touch the code anymore (barring major issues)14:25
mnaseri think that's reasonable. it gives us one more meeting before the event as well to run through things14:25
topolmnaser lets try and freeze stuff by next meeting14:25
dmellado+114:26
vkmcI think that's reasonable14:26
dmelladotopol: will you be sending the email then?14:26
ksumit+114:26
dmellado;)14:26
topoldmellado sure14:26
mnaserand then for the may 3rd meeting, it would be nice if everyone ran the workload after the 26th freeze14:26
mnaserso that on the 3rd, we can discuss any bugs anyone ran into14:26
mnaserand then on the 3rd hopefully we have no bugs and everything is 100% frozen till the demo date14:27
topol#action topol to send we freeze demo on the 26th email to the list  and on the 3rd discuss any bugs14:27
dmelladoshould we go ahead?14:27
mnaseri think it makes sense14:27
topolwho wanted to demo NFV to sparkycollier_14:27
HelenYao_topol: me14:28
zhipeng_me and helen I think14:28
sparkycollier_Ah ok I forgot it was for nfv14:28
sparkycollier_I'll be at a computer in about 10 minutes if that's not too late14:28
sparkycollier_Or we can do it next week14:28
topolI rather do that in 10 minutes14:29
zhipeng_agree14:29
topolnext week I think will be packed14:29
sparkycollier_Ok great14:29
topolping us when you are at a computer14:29
sparkycollier_K14:29
topolnext item14:29
dmellado#topic     Make sure all folks who plan to demo are on the onstage etherpad.  we should have 16 listed.14:30
dmelladoI guess you asked for this before, topol14:30
dmelladobut pls anyone who still hasn't signed up there, do so14:30
topolyes. yes I did. we are missing 4 I think14:30
dmellado#topic     Identify which cloud can demo phase 2.14:30
topolsince you and vkmc are one really14:30
dmelladowe've got this tracked on the etherpad14:31
topolK14:31
dmelladobut it'd be cool to identify which public clouds are around14:31
*** iceyao has joined #openstack-meeting-514:31
dmelladoand regarding this idk if we'll be in a rush14:31
mnasero/ public cloud14:31
topol#topic Clouds should start record their workload run results.14:31
*** openstack changes topic to "Clouds should start record their workload run results. (Meeting topic: interop_challenge)"14:31
topolmnaser fdid you putthat on the etherpad14:32
mnaseryep :)14:32
topolmnaser gold star! awesome14:32
daniela_ebertalready done and recorded at the etherpad ;)14:32
dmelladoso, on this topic I guess you refer to the wiki14:32
topoleveryone please start trying to runt he workloads. we always hit surprieses14:32
topoldmellado ++14:33
dmelladohttps://wiki.openstack.org/wiki/Interop_Challenge14:33
mnaseron that note, do we have a 'backup' plan at all for if things go wrong?14:33
mnaser(murphy's law)14:33
dmelladomnaser: we just go for beers14:33
dmelladoxD14:33
mnaserlol!14:33
sparkycollier_I'll just have the beers brought out14:33
mnaseri dont know what everyone thinks but i was thinking that we have 2 tenants on clouds14:34
vkmctopol, dmellado and I are two different engineers, he is not my alter ego14:34
mnaserwe do a deploy beforehand and leave it, then do one live14:34
mnaserif the live works, great, if not, then we can just show the already deployed14:34
dmelladolol14:34
dmelladovkmc: what he meant by that is that we won't be both of us at the stage14:34
dmelladounless you want to join the fun xD14:34
vkmcdmellado, oh yes, that would be awkward14:34
topolof course I like vkmc.  I can just barely tolerate dmellado :-)14:34
dmelladolol14:34
topolj/k14:35
vkmclol14:35
zhipeng_for nfv demo, please join https://zoom.us/j/33340831914:35
mnaserso any input on the "backup environment" idea or everyone's 100% confident?14:35
*** iceyao has quit IRC14:35
topolso where did folks add public? I dont see it on the wiki14:35
dmelladotopol: it's on the etherpad, I assume that anyone listed there for phase2 should be count as 'public'14:36
mnaseroh i dont see it on the wiki but i see it on the interop challenge etherpad14:36
topolok lets all make sure we update in the same place. which is?14:36
mnaserhttps://etherpad.openstack.org/p/interop-challenge-boston-onstage14:36
topolmnaser YES! #link https://etherpad.openstack.org/p/interop-challenge-boston-onstage14:37
topolput it there14:37
topolI need to go thru and find the 3 folks on the wiki that arent on https://etherpad.openstack.org/p/interop-challenge-boston-onstage14:37
topolwith my diff skills that could only take an hour or two :-014:38
mnasersilly question but how come there's two people from redhat?14:38
dmelladomnaser: scroll up14:38
dmelladowe're not two of us at the same time14:38
topolmnaser I think they are worried one wont make the prep meeting?14:38
dmelladowe put our details as vkmc will be backing me up in case ;)14:39
* mnaser totally knew that14:39
mnaserjust testing everyone's attention, onto the rest14:39
vkmcI'm the backup!14:39
topolthey will flip a coin to see who gets on stage.  its like the preshow14:39
vkmchaha14:39
topolHere was the note from Tamara and then I think we should do the demo14:39
topolthat was my last topic14:40
dmelladoHere I added another one14:40
topolHi Tong -14:40
topolI’d like to schedule the Interop Demo Tech on Sunday, May 7th as follows:14:40
topolArrive: 3:15pm14:40
topolTech 3:25-3:55pm14:40
topolIf there are a few people who cannot arrive right at 3:15pm, that will be fine since it takes some time to get everyone plugged in & up / running in our system.14:40
topolDecision we have made during the meeting:14:40
topol 14:40
topol1. phase 1 of the demo is to stand up kubernetes cluster on top of openstack. every cloud can participate.14:40
topol2. phase 2 of the demo is to create a cockroachdb cluster on top of k8s across multiple clouds, hope all clouds can join.14:40
topol3. work on the app so that running cockroachdb cluster will have some load to show actitivites on the cockroachdb dashboard.14:40
topol4. create a simple app for clouds to get the IP information about the first cockroachdb node so that they can join.14:40
topol5. that simple app will be started before the demo so that that IP can be used in all cloud workload configuration14:40
dmelladoI'm concerned about how log would this last if we need to run both phase 1 and 2 taking into consideration that this lasts for around 10' each14:41
dmelladoshouldn't we settle for phase1 and check on the demo day if phase2 would be feasible14:41
dmellado?14:41
topolTong and I will be with sparkycollier next week testing out the flow14:41
topolthere are ways we can speed up phase 214:42
topolcan do cooking show if necessary14:42
mnasertopol ++14:42
dmelladomybe just not respawning the whole k8s cluster but deploying an additional pod14:42
dmelladofor the phase 214:42
topolsparkycollier_ you in front of a computer yet?14:42
sparkycollier_i'm on a computer now14:43
zhipeng_please join https://zoom.us/j/33340831914:43
topolK, lets all switch to  zoom14:43
*** ramishra has joined #openstack-meeting-514:45
*** cwolferh has joined #openstack-meeting-514:57
topol#endmeeting14:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:58
openstackMeeting ended Wed Apr 19 14:58:30 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-19-14.01.html14:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-19-14.01.txt14:58
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-19-14.01.log.html14:58
*** tiantian has joined #openstack-meeting-514:59
*** mnaser has left #openstack-meeting-515:00
ricolin#startmeeting heat15:00
openstackMeeting started Wed Apr 19 15:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is ricolin. 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: heat)"15:00
openstackThe meeting name has been set to 'heat'15:00
ricolin#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: heat)"15:00
*** daniela_ebert has quit IRC15:00
ramishrahi15:00
ricolinhi:)15:01
*** therve has joined #openstack-meeting-515:01
cwolferhhi15:01
zanebhola15:01
tiantianhi15:01
ricolinramishra thx for mark that deprecated bug, not notice there is a similar one15:02
ricolins/deprecate/duplicate/15:02
ramishraricolin: yeah, but the user has some strange issue though;)15:03
ricolin#topic adding items to agenda15:03
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:03
ricolin#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-04-19_1500_UTC.2915:03
ricolinpilgrimstack1 around?15:04
ricolindose anyone know what's the floating ip provider issue pilgrimstack1 was referring to?15:05
ricolinI think we can skip the floating ip topic, since he seems not here to tell:)15:07
*** HelenYao_ has quit IRC15:07
ricolin#topic force delete resource15:07
*** openstack changes topic to "force delete resource (Meeting topic: heat)"15:07
ricolin#link https://review.openstack.org/#/c/454941/15:07
zanebick15:08
ricolinthe code looks fine, just would like to know how we want to do force delete in heat15:08
ricolincurrent propose is to add a property in server for `force_delete`15:09
zanebwhat's the difference between force_delete() and delete() in Nova?15:09
zaneband wth were they thinking15:10
ramishraAnyway the server is gone right? Though reclaimed later by nova?15:10
*** iceyao has joined #openstack-meeting-515:10
ricolinto force detach I think?15:10
tiantianthere is a config option15:10
ricolin`reclaim_instance_interval`15:11
ricolinin Nova :)15:11
ramishraoh it's for bdm boot disk15:11
zaneb#link http://www.stillhq.com/openstack/000018.html15:11
tiantianyes, if the config set then the delete is not really execute15:11
*** topol_ has joined #openstack-meeting-515:11
ricolinramishra yes15:12
zanebmy first thought is that we should just call force_delete all of the time15:12
*** topol has quit IRC15:13
therveIt's probably not backward compatible15:13
ricolinzaneb not it is not:)15:13
ricolinSo what is the best way to introduce this feature15:14
*** iceyao has quit IRC15:15
ricolinadding properties in server for force?15:15
therveThat patch looks okay to me15:15
tiantiananyway I gave my +2 ;)15:15
therveIt sucks, but because nova sucks15:15
zanebdeletion_policy: half-a**15:15
therveWe don't have to hide the suckiness all the time15:15
ramishraWe still have number of issues with bdm, when replaced during update, it fails15:16
ramishrawhen bdm is used to boot15:17
zanebwhy are we counting the SOFT_DELETE state as deleted?15:17
ricolinzaneb a deletion_policy sounds nice15:17
ricolinzaneb Not getting what you mean, why not?15:18
tiantianif `reclaim_instance_interval` is set in nova, then the status of server is SOFT_DELETED after delete15:18
zanebricolin: could we always force_delete except when there's a deletion_policy: soft_delete? or would that still not be backwards-compat enough?15:19
tiantiandeletion_policy is for 'all' resources15:19
zanebricolin: what tiantian said15:19
zanebtiantian: yeah, that is the downside of deletion_policy15:19
ricolinI see15:20
zanebricolin: if it's not DELETED, as in, it's safe to go ahead and delete the stuff that it depends on, then we should consider it DELETE_IN_PROGRESS imho15:20
therve? deletion_policy is a resource attribute? You mean we would have a value that's specific to server?15:21
*** tiantian has left #openstack-meeting-515:21
zanebliterally the entire point of Heat is that we don't delete(/create/update) stuff in the wrong order15:21
thervereclaim_instance_interval is just some crappy pet support15:22
*** tiantian has joined #openstack-meeting-515:22
tiantiansorry15:22
zanebtherve: yeah, I'm starting to go off the deletion_policy idea15:23
tiantianI mean adding property 'force_delete' for server is enough15:23
zanebto me this is like adding a "not_broken" property and defaulting it to False15:24
therveBut only a few people are going to use that option15:25
ricolinIt might be weird to mention but what should we do with force delete for cinder volume? or other force delete able resource?15:25
zanebtherve: so why are we worried about backwards compat with their already-broken stuff?15:26
thervezaneb, Well presumably if you didn't use anything like network and volume you could have a working template?15:26
therveBut maybe I worry too much, no one uses that thing15:27
therveWe're already wasting too much time on that :)15:27
ricolinanyway, feel free to put your idea on top of that review15:29
ricolin#topic releasenote scope15:30
*** openstack changes topic to "releasenote scope (Meeting topic: heat)"15:30
*** iceyao has joined #openstack-meeting-515:30
ricolinI would like to propose to add releasenot in the feature bugs at least for some high Importance bugs15:32
tiantian+115:32
ricolinour releasenote seems not cover `bug fix` much15:33
ricolin#link https://docs.openstack.org/releasenotes/heat/ocata.html15:34
zanebthat seems reasonable for major bugs15:34
ramishrayeah, if that makes sense to the user not for high importance gate issues;)15:35
zanebheh, the one "Bug Fix" on there is actually a new feature and not a bug15:35
*** iceyao has quit IRC15:35
ricolinramishra I think it might depends on cores to decide if that's something user should notice about15:37
ramishraricolin: sure, let's add more release notes:)15:37
ricolinzaneb exactly!15:37
ricolinokey, solved:)15:38
ricolin#topic Open discussion15:38
*** openstack changes topic to "Open discussion (Meeting topic: heat)"15:38
zanebso this happened https://governance.openstack.org/tc/resolutions/20170317-cloud-applications-mission.html15:38
ramishrazaneb: cool15:38
ricolinzaneb so is there will be a room for all to working on that in summit?15:39
zanebricolin: likely yes, working on getting it on the schedule now15:39
ramishraAre we ok to make the py35 dsvm job voting now?15:40
zanebI mena, not *now* now cuz of this meeting ;)15:40
ramishrahttps://review.openstack.org/#/c/456253/, I can unblock it15:40
ricolinramishra I do feel it's okey to vote:)15:42
ramishrasilence means 'no'? therve?15:43
* zaneb hasn't been watching the gate for a couple of weeks15:44
ricolinzaneb basically green15:44
zanebramishra: according to the official OpenStack rule of lazy consensus, silence means yes :)15:44
ramishrazaneb: ok:)15:44
ricolinwe can always make it non vote again if a good reason comes up:)15:45
ramishraI've not seen any failures since it's been green though, other than normal issues that affects other jobs too.15:45
zaneb+1 for make it voting then15:46
ricolin+115:47
ricolinIf no against shall we make it vote?15:47
ramishraok done15:47
ricolinnice:)15:48
ricolin#action ramishra make py35 vote15:48
ricolinanything would like to discuss?15:49
ricolincool15:50
therveramishra, I'm a bit afraid to be broken by other projects for no reason, but that's like the other gates :)15:50
ramishraI think the server bdm stuff is already a mess. We can make even more broken;)15:51
ricolinramishra but to add properties means the property stay there for almost ever15:51
*** matrohon_ has quit IRC15:52
ricolinanyway hope we can make more discussion on that review and think it through before we land it:)15:53
ricolinokey, if no other stuff, shall we back to heat:)15:54
ramishra+115:54
ricolinthx all15:54
ricolin#endmeeting15:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Wed Apr 19 15:54:59 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-19-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-19-15.00.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-19-15.00.log.html15:55
*** therve has left #openstack-meeting-516:00
*** Rockyg has joined #openstack-meeting-516:00
*** aarefiev is now known as aarefiev_afk16:35
*** ricolin has quit IRC16:39
*** ksumit has left #openstack-meeting-516:54
*** ksumit has quit IRC16:54
*** zhipeng_ has quit IRC17:02
*** ralonsoh has quit IRC17:02
*** racedo has quit IRC17:30
*** iceyao has joined #openstack-meeting-517:37
*** iceyao has quit IRC17:41
*** iceyao has joined #openstack-meeting-519:44
*** iceyao has quit IRC19:48
*** iceyao has joined #openstack-meeting-520:03
*** iceyao has quit IRC20:08
*** iceyao has joined #openstack-meeting-520:24
*** iceyao has quit IRC20:29
*** topol_ has quit IRC21:09
*** ramishra has quit IRC21:27
*** ramishra has joined #openstack-meeting-521:29
*** cwolferh has quit IRC21:50
*** topol has joined #openstack-meeting-523:09
*** topol has quit IRC23:16
*** rarcea has quit IRC23:36

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