Wednesday, 2017-04-12

*** skazi has quit IRC00:06
*** skazi has joined #openstack-meeting-500:19
*** skazi has quit IRC00:26
*** skazi has joined #openstack-meeting-500:39
*** ricolin has joined #openstack-meeting-501:06
*** HelenYao has quit IRC02:20
*** krtaylor has quit IRC03:45
*** iceyao has joined #openstack-meeting-505:05
*** rarcea has joined #openstack-meeting-505:44
*** zenirc369 has joined #openstack-meeting-505:46
*** zenirc369 has quit IRC07:55
*** ralonsoh has joined #openstack-meeting-508:02
*** dmellado has joined #openstack-meeting-508:23
*** aarefiev_afk is now known as aarefiev08:24
*** zenirc369 has joined #openstack-meeting-508:34
*** iceyao has quit IRC09:16
*** HelenYao has joined #openstack-meeting-509:29
*** ricolin has quit IRC09:41
*** ricolin has joined #openstack-meeting-510:00
*** ricolin_ has joined #openstack-meeting-510:10
*** ricolin has quit IRC10:13
*** iceyao has joined #openstack-meeting-511:20
*** iceyao has quit IRC11:30
*** krtaylor has joined #openstack-meeting-512:11
*** markvoelker has joined #openstack-meeting-512:37
*** rarcea has quit IRC12:47
*** zenirc369 has quit IRC12:58
*** iceyao has joined #openstack-meeting-513:05
*** markvoelker has quit IRC13:37
*** markvoelker has joined #openstack-meeting-513:40
*** mnaser has joined #openstack-meeting-513:50
*** tongli has joined #openstack-meeting-513:57
*** ksumit has joined #openstack-meeting-513:58
*** Alex_____ has joined #openstack-meeting-513:58
*** ksumit has quit IRC13:58
*** zhipeng has joined #openstack-meeting-513:59
*** Alex_____ is now known as arobinson13:59
*** spencerkimball has joined #openstack-meeting-513:59
*** arobinson is now known as alexrobinson14:00
*** spencerkimball has left #openstack-meeting-514:00
tonglihello, guys14:01
topolo/14:01
mnasero/14:01
zhipengo/14:01
tongli#startmeeting interop_challenge14:01
openstackMeeting started Wed Apr 12 14:01:35 2017 UTC and is due to finish in 60 minutes.  The chair is tongli. 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
mnasero/14:01
*** pilgrimstack has joined #openstack-meeting-514:01
*** spencerkimball has joined #openstack-meeting-514:01
tonglican you please announce yourself again, sorry I am a bit late.14:01
pilgrimstackHi, Jean-Daniel from OVH14:02
*** iceyao has quit IRC14:02
tongli#link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-04-1214:02
sparkycollier_Hi it's mark collier, looking forward to working with everyone14:02
skazi_o/14:02
markvoelkero/14:02
alexrobinsonHi, Alex Robinson from Cockroach Labs14:02
mnasermohammed naser from vexxhost14:02
topolHi Alex14:02
*** daniela_ebert has joined #openstack-meeting-514:02
spencerkimballHi, Spencer Kimball from Cockroach Labs14:02
topolHi Spencer14:02
*** ksumit has joined #openstack-meeting-514:02
tongliplease see the etherpad for agenda.14:03
tonglifoundation has decided to have our show tech check on Sunday 5/7 at 3:15 to 3:55pm.14:03
hogepodgeo/14:04
daniela_ebertthats fine14:04
tonglithis is mandatory. you and your laptop and any other necessary things need to be there.14:04
vkmco/14:04
vkmchey14:04
mnasercool, i'll be arriving on sunday at 12pm so works for me.  is there any announced location yet (i know its early) to be at?14:04
tongliand if you can not be there at 3:15, 10 minutes late is fine because it takes time for everybody to hook up things.14:04
sparkycollier_main tech check purpose is to make sure all of the video outputs work from the laptops to our splitters14:05
mnaserand how do we work out what sort of inputs we need?  i have one of those new adapter-for-everything macbook, so hdmi? dvi?14:05
tonglibut you do have to show up to make sure things working.14:05
tonglihdmi is the default,14:05
mnasertongli okay, i'll make sure i have an adapter14:05
tongliif your laptop does not have hdmi, then you need to bring an adaptor.14:05
mnaserack14:05
pilgrimstackack14:06
tonglithen there will be another rehearsal on Monday, that time is TBD.14:06
tongligot to be in both to qualify to be on stage.14:06
vkmcthe demo will be on the second day keynote, right?14:06
vkmclike last time14:06
tongliand also please put your info on this pad.14:07
zhipengtongli this only applies to the k8s demo or nfv as well ?14:07
tongli#link https://etherpad.openstack.org/p/interop-challenge-boston-onstage14:07
sparkycollier_second day keynote, correct14:07
tongli#action, please required information on the boston onstage etherpad.14:07
sparkycollier_however unlike bcn, I will be the MC for day 2 so y'all are stuck with me this time14:07
tongli@zhipeng, right now, the k8s workload only.14:07
daniela_eberttongli: already put my info to the pad. Bu to whom to send the logo?14:07
zhipengtongli okey14:08
zhipengdo we have a Forum session so that we could demo the NFV Workload ?14:08
tongli@daniela_ebert, Maria, her info is on the etherpad.14:08
tongli@zhipeng, we do, let's talk offline.14:08
mnaserthanks for that link, useful info tongli14:08
sparkycollier_I think I need to get up to speed on the NFV workload and then I can see about a space/time for it14:08
zhipengokey-dokey14:08
tongli@sparkycollier_, we do have one action item from last week. the action is to schedule a demo session with you so that you can take a look at the demo and make decision if that can go on stage as well.14:09
tongli@sparkcollier_, do you have time next week?14:09
sparkycollier_yes let's take that offline and set it up14:10
daniela_eberttongli: thanks!!14:10
tongli@sparkcollier_, great. thanks.14:10
tongli#link https://etherpad.openstack.org/p/interop-challenge-boston-onstage14:10
tongliwe communicate and find information from that pad, please have your questions there so that we can track and answer also let other people know.14:11
tonglithat is the pad Tamara will be looking at and post requirement and other useful information such as date & time etc.14:11
tongliok. now, let's talk about the k8s workload.14:12
ksumit@tongli For the k8s workload, do we need a public cloud? My IT org isn't very friendly :) but I did manage to get the workload to run successfully in a private cloud (connected through VPN).14:12
tongli#topic k8s workload with cockroachdb cluster.14:12
*** openstack changes topic to "k8s workload with cockroachdb cluster. (Meeting topic: interop_challenge)"14:12
tongli@ksumit, great question, exactly what I like to discuss with mark, spencer next.14:13
tongliI think that the current thinking on the demo goes like this. @sparkcollier_, @spencerkimball@14:13
tonglieverybody run the current k8s workload (will remove the cockroachdb cluster setup)14:14
vkmcon this topic, I'd like to bring up (if this is not already on the agenda) the existence of this issue https://hub.docker.com/r/cockroachdb/cockroach-k8s-init/14:14
tonglithe result will be just a kubernetes cluster on your openstack cloud.14:14
*** jbryce has joined #openstack-meeting-514:15
*** ricolin_ has quit IRC14:15
vkmcwe ran this workload with dmellado and we found that the cockroachdb pods were not being launched correctly due to this14:15
tonglithen mark and the gangs will show Virtual Machines, and possibly k8s dashboards.14:15
sparkycollier_@vkmc we are looking at a different approach to provisining the cockroachDB which @tongli is explaining now14:15
vkmcsparkycollier_++14:15
vkmcthx14:15
alexrobinsonvkmc: thanks for bringing that up - I'll look into that separately, but we don't plan on using that configuration14:15
tongliafter we made sure that all the OS cloud can have kubernetes cluster running succesufully, we will move on to the second phase of the demo.14:15
tonglifirst, one cloud will start a single node (could be multiple nodes) cockroachdb cluster on the k8s cluster you just created.14:16
tonglithen some information will be sent(or pulled by each cloud), that information (most likely a first cockroachdb node info) will be used by other clouds14:17
tongliother clouds will start cockroachdb pods to start joining the first cockroachdb cluster.14:18
tonglithe end results will be a bigger cockroachdb cluster spread over multiple clouds.14:18
alexrobinsonwhat will we be doing for networking, again? public IP addresses? VPN?14:19
tongliif a node joined the cockroachdb cluster successfully, then that node will start run a script (or program) to generate data against the cockroachdb, the purpose of that app is to create some load,14:20
tongliso that the cockroachdb dashboard will show activities from the cluster.14:20
tongliI think that is the basic idea.14:20
tongliso two steps, first, getting k8s cluster up running live on your OS cloud. second, join the first cockroachdb cluster, run the app to adding data to the database.14:21
sparkycollier_so what's the networking approach so that the different clusters on each cloud can talk14:21
tonglimark and guys will talk and explain what we are doing.14:21
tonglithe key is how we connect nodes from various clouds.14:22
tongliespecially for the private cloud,14:22
mnaserfor networking, public cloud is easy mode.. the private is when things get tricky14:22
tongli@mnaser, that is what I was worried about.14:22
tonglimy understanding is that for private cloud, each company has their own way of going through the VPN.14:23
mnaser(also, i love to think people aren't evil but if there is some sort of "easy way" to enter the cluster during our demo when we do a multicloud thing, we'd have to worry about someone trying to do something slightly malicious)14:23
tongliit will be difficult to use many different ways (certificates, credentials) to connect these nodes over 16 clouds.14:23
vkmcmnaser++14:23
mnaserand if things are going to be over public ips, it'll be tricky to "hide" things from a huge keystone (that's also most likely livestreamed?)14:24
tongli@mnaser, that is a small issue, we can enable userid/password and other things on k8s cluster.14:24
tongliI started working on that already.14:24
sparkycollier_if we give enough info on screen to figure out how to access the clusters on public cloud, someone in the audience will do it14:24
tonglithe key is how to connect from public cloud to private cloud.14:24
jbryceCan any private cloud demo-ers describe how they're accessing their demo environments from the stage network? Is everyone using different vpns?14:24
topolsparkycollier_ +++14:24
sparkycollier_good point @tongli that is the harder problem14:24
*** zhipeng has quit IRC14:25
markvoelkerjbryce: Yes, I was planning to VPN from my laptop.14:25
tongli@jbryce, IBM use CiscoMobility to go through ibm firewall. each individual has a certificate and I have no way to share that with anyone.14:25
ksumit@jbryce I'd have to use the Cisco Any Connect client on my Mac to be able to connect.14:25
tonglinot even brad.14:25
topoltongli Ha Ha So true14:26
tongliI am pretty sure that other companies like VMWare, Huawei have their own way of doing things.14:26
mnaser(i apologize, i have to run to something at 10:30 in a few minutes, we're a public cloud so we should be okay regardless of what choice everyone proposes, i'll catch up on the agenda and logs, really sorry everyone)14:26
tonglithe demoer can use their own credential to connect to their own clouds, but these credentials can not be shared.14:27
vkmcshall we ask to the security council about this?14:27
vkmcI think we could get a better understanding on how risky would be to do this on stage14:27
mnaser(before i run, the only way i can imagine this working is if we all setup a vpn and connect all clouds together in advance)14:28
tongli@vkmv, who is secuirty council? we have both jonathan and mark here. haha.14:28
jbryceAnd your demo environments don't have any way to open up for just the port needed by cockroach?14:28
vkmcI agree that the final result would be great, but it's quite risky both in the sense that the networking configuration may fail and/or we may have security vulnerabilities14:28
mnaserthat way we can run it in a secure private network which is unaccessible by anyone except the clouds14:28
mnaseraaand it solves the inter-public/private concerns, but we need to plan it and run that vpn first14:28
vkmctongli, this team https://wiki.openstack.org/wiki/Security14:29
ksumit@jbryce Pretty sure my IT org won't do it.14:29
tongli@jbryce, I think that the issue is that private cloud runs inside company firewall, to go through that firewall, different company uses different means.14:30
markvoelkerjbryce: I'd have to get very creative. =)  I may be able to find an environment to run this on that has public addressing, or rig up a VPN+jumphost/router, but it'll be tricky given the short timeframe.14:30
skazi_how much time do we have for the complete demo?14:30
*** Labedz_ has joined #openstack-meeting-514:30
vkmctongli, I trust on Mark and Jonathan criteria, but if we have a team dedicated to security that we can ask in order to get an assessment, I don't see how that would hurt14:30
*** ricolin_ has joined #openstack-meeting-514:30
topolso what worries me is if you all have to jump through hoops to make this work how could folks in the audience view it as plausible?14:31
tongli@vkmc, so what do we do for private cloud?14:31
vkmctongli, I don't follow the question14:31
sparkycollier_We don't have a solution yet to vet with the security team, so I think that would be a good problem to have at this stage14:31
jbrycetopol: this is exactly what people in the audience are doing to run their multi-cloud workloads14:31
topoljbryce what is the best practice?14:32
* markvoelker notes that having said that, he may have just found something14:32
jbrycealexrobinson: how much network access does cockroach need to function?14:32
tonglieach private cloud create a new demo credential for this demo?14:33
jbryceAs in Barcelona, we won't have time to show everything from every demo14:33
spencerkimballeach cockroachdb node needs to be able to connect to every other node; that's the requirement from our side. But for the demo to make sense, we don't necessarily have to connect to every private cloud. If we could just run across 3, the point would be made. So we could use some public, some private, and limit ourselves to private clouds where there is a solution in place to allow external connections to a host/po14:33
jbryceSo perhaps we show k8s on private clouds that can't interconnect14:33
alexrobinsonjbryce: each cockroachdb process needs to be able to reach each other cockroachdb process on a single port (which, by default, is 26257)14:33
jbryceThen cockroach across a handful of public+ private that can interconnect14:33
jbryceBasically what spencerkimball just said = )14:34
tonglioh, so say we have one set of credentials/userid/password from each private cloud, that get that distributed to all clouds.14:34
markvoelkerspencerkimball: jbryce: Something that may make a differnece for a lot of folks is who sends the SYN.  E.g. for many corporate envs I can establish an outbound connection from within, but having something outside establish a connection to something behind the firewall is...hard.14:34
tonglievery cloud will have to know how to use these credentials?14:34
*** zhipeng has joined #openstack-meeting-514:35
tongli@markvoelker, I think cockroachdb needs two way communication.14:35
tongliin this case, all 16 clouds will have to be able to talk to each other.14:36
alexrobinsonyes, each node needs to be able to open a connection to each other node14:36
tonglithis is not a problem for IBM since we have bluebox which exposes accessible IPs.14:36
ksumitI think the point @spencerkimball is trying to make that not all private clouds need to be connected to the cluster. For the purpose of the demo, we only show the ones to the public that are able to connect, which can be a mix of public + those private clouds that find a solution and are able to connect to the cluster. Is my understanding correct?14:37
sparkycollier_I think the idea of having a subset as examples (some public, some private) could work.14:37
tongli@zhipeng, what do you think? will you run on Huawei public cloud or private cloud?14:37
jbryceSo basically all clouds can participate in the k8s deployments portion, then the k8s environments that have full access on :26257 can participate in the cockroach portion14:37
skazi_@tongli, can we add info on public/private cloud to the onstage etherpad? this would give as some idea on how many public/private clouds we'll have14:37
tongli@skazi_, great idea.14:38
zhipengtongli sorry my network just went down earlier14:38
jbryceksumit: yes14:38
spencerkimball@ksumit: exactly14:38
zhipengdo you mean for nfv workload ?14:38
topolskazi_ +++14:38
tongli#action, identify if your cloud is public or private on the boston onstage etherpad.14:38
ksumit@spencerkimball @jbryce I think I like this solution the most.14:38
tongli#link https://etherpad.openstack.org/p/interop-challenge-boston-onstage14:38
tongliwe go with public clouds first, then figure out if we can add few more private clouds?14:39
tongliwill that work?14:39
sparkycollier_I think so14:39
jbryce#action Identify if your cloud will be able to allow access on port 2625714:39
tongliwe can start with vexxhost and IBM.14:39
skazi_+1 for limited set of clouds for the second part of the demo14:39
jbryceI think this is makes sense. Again, we wouldn't have time to get to every single environment anyway14:40
tongliand of course any other public clouds who participate.14:40
sparkycollier_I can explain it from the stage14:40
topoljbryce exactly14:40
*** ricolin_ has quit IRC14:40
daniela_eberttongli: pick me :)14:40
*** ricolin has joined #openstack-meeting-514:40
tongligreat. I have created two k8s clusters using our workload on vexxhost and bluebox.14:41
tongliif you can also do the same, then send the info to spencer, that will be great14:41
tonglithat will make 3 for now.14:41
topolHopefully a nice balance can be made of showing off all the folks who can just do Kube (phase 1) so they get some screen time before you move to phase 2 where the Kube only folks kind of stand there with not much to do14:41
daniela_eberttongli: ok14:41
ksumit@topol +114:42
sparkycollier_will it be possible spencerkimball to show it working next week?14:42
sparkycollier_+114:42
jbrycetopol: yeah. We should remember to rehearse that14:42
sparkycollier_I can talk to tamara about how to arrange the participants so the flow works from the stage (for example we might have the ones that include cockroachdb sync on one side for second phase)14:43
topol#action remember to identify phase 1 only folks so they get screen time as wlel14:43
tongli@topol, wow, make sure everybody gets something. great leader!14:44
spencerkimball@sparkycollier_, @alexrobinson: I believe so, though alex needs to weigh in on timing14:44
alexrobinsontongli: a somewhat more specific question that we can take offline is how cockroachdb should learn its external IP address on the different clouds. on the ibm cluster you shared with me it doesn't appear to be configured on the machine14:45
tongliI will be traveling next week, won't be back until 4/21 (Friday night).14:45
tongli@alexrobinson, I suggested to develop a small app, which runs before demo starts.14:46
topolKey issue will be is there enough time to setup the cockroach stuff after the Kube stuff or do you do that using a cooking show technique and cut over to some subset of the participants with that part ready to be viewed14:46
tongliso that everybody knows that app IP.14:46
alexrobinson@sparkycollier_: yup, next week shouldn't be a problem. I hope to have things working today14:46
sparkycollier_woohoo14:46
tonglithat IP will be used by other clouds to get first node IP.14:46
tongliand other info if we need.14:46
topolGreat!!14:46
tongliso all these stuff is automatic.14:46
alexrobinsonI mean how can each node know its own IP address. we can follow up after the meeting though14:47
tongli@alexrobinson, oh, that is part of the k8s service, we can talk offline.14:47
tongliwell, I do not have any other topics for today. we still have 12 minutes left.14:48
tonglilet me try to summaries what we discussed today.14:48
tongli1. phase 1 of the demo is to stand up kubernetes cluster on top of openstack. every cloud can participate.14:49
tongli2. phase 2 of the demo is to create a cockroachdb cluster on top of k8s across multiple clouds, hope all clouds can join.14:49
tongli3. work on the app so that running cockroachdb cluster will have some load to show actitivites on the cockroachdb dashboard.14:50
tongli4. create a simple app for clouds to get the IP information about the first cockroachdb node so that they can join.14:51
tongli5. that simple app will be started before the demo so that that IP can be used in all cloud workload configuration.14:51
tonglilet me know if I missed anything?14:52
tonglidid I lose everybody?14:53
sparkycollier_is there any reason for the clouds that won't be in the cross-cloud phase2 piece to install cockroackdb? or should they skip that piece14:53
ksumit@tongli Does the provisioning method that's on GitHub today change in any way? I mean I tested last Friday by following the guide based around deployment through Ansible. Does that change in any way?14:53
tongli@ksumit, I am hoping whatever spencer create will be also part of our workload.14:53
tongliit will be just a new playbook. there will be changes to the workload for sure.14:54
tongliat least I have to remove the cockroachdb cluster deployment from the current workload.14:54
ksumitSo is Spencer working on the application?14:54
*** zhipeng has quit IRC14:54
tonglisince spencer is going to do that.14:54
ksumitOk14:54
vkmcso we have one month exactly to work on items 2-514:54
tongli@ksumit, yes spencer is working on the app to generate some load.14:54
sparkycollier_I think that answers my question14:54
*** ramishra has joined #openstack-meeting-514:55
tongliI will work on an app to expose the first node IP.14:55
tongliand add steps for workload to retrieve that IP and pass that to spencer so that his cockroachdb pods can join14:56
spencerkimball@ksumit, the app will be a standard load generator: the "kv" in https://github.com/cockroachdb/loadgen14:56
ksumitGot it. Thanks!14:56
spencerkimballone question I have is whether we'll be starting multiple nodes per cloud14:56
tongli@spencerkimball, I would like to pull that into our workload.14:56
tongli@spencerkimball, I think we use 3 (stack size 4).14:57
*** zhipeng has joined #openstack-meeting-514:57
*** jasond has joined #openstack-meeting-514:57
tongliso each cloud has 3 nodes to join.14:57
tongli3 pods actually.14:57
*** pilgrimstack1 has joined #openstack-meeting-514:57
tongli@sparkycollier_, you ok with what I just described?14:58
tongliI mean the flow and the content and how we are going to accomplish that?14:58
topol2 mins left14:58
*** cwolferh has joined #openstack-meeting-514:58
sparkycollier_yes sir14:59
spencerkimballOK, sounds good. So we'll have a ~9-15 nodes CockroachDB cluster depending on how many public/private clouds participate14:59
sparkycollier_in fact I'm very excited!14:59
tongli@sparkycollier_, that was a very long pause. haha.14:59
tongliyou got me a bit worried.14:59
topolAwesome progress! great work everyone14:59
sparkycollier_sorry doing too many things at once14:59
sparkycollier_:)14:59
tongliok. great. thanks everybody.14:59
alexrobinsonsounds good, thanks tongli!15:00
sparkycollier_woohoo15:00
tongli#endmeeting15:00
sparkycollier_thanks tongli15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Apr 12 15:00:20 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-12-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-12-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-12-14.01.log.html15:00
*** pilgrimstack has quit IRC15:00
ricolin#startmeeting heat15:00
openstackMeeting started Wed Apr 12 15:00:53 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:01
*** openstack changes topic to "roll call (Meeting topic: heat)"15:01
*** pbourke has joined #openstack-meeting-515:01
ramishrahi15:01
ricolinhi:)15:01
jasondo/15:01
cwolferhhello15:01
pbourkeo/15:01
*** alexrobinson has quit IRC15:02
ricolin#topic adding items to agenda15:02
*** ksumit has left #openstack-meeting-515:02
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:02
ricolin#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-04-12_1500_UTC.2915:02
*** spencerkimball has quit IRC15:03
ricolinokey first topic!15:04
ricolin#topic Announcement15:04
*** openstack changes topic to "Announcement (Meeting topic: heat)"15:04
ricolinso we have release heat pike-1!15:04
ricolinyeah!15:05
ramishraricolin: great15:05
ricolinall looks clean15:05
ricolinalso will release python-heatclient 1.9.015:05
ramishraI was hoping to land the translation patches before that but anyway it does not matter15:05
ricolinand heat-agents from 1.1.0 to 1.1.115:06
ricolinyeah, me to15:06
ricolinwill get it landed as soon as we can :)15:06
ramishrareg heat-agents, we did a release just a few days back right? do we need one more?15:06
ricolinthere actually only increase one commit between, so I'm free to release or not:)15:07
*** zhipeng has quit IRC15:08
ricolinthat's why I only jump from 1.1.0 to 1.1.115:08
ricolinwhat guys think about it?15:08
pilgrimstack1Sorry I have to leave, next time we should speak about non floating IP providers ;)15:08
ricolinpilgrimstack115:08
ricolinpilgrimstack1 ok15:08
ricolinpilgrimstack1 ok I will help to add to agenda next week:)15:09
ramishraThis was on 5th April https://review.openstack.org/#/c/452986/15:09
ramishraSo not sure if we want one more now15:10
ricolinsure, then I can abandon this one https://review.openstack.org/#/c/455876/15:10
ricolinramishra abandoned:)15:11
ramishraricolin: :)15:11
ricolinhow about python-heatclient?15:11
ricolin#link https://review.openstack.org/#/c/455873/15:11
ramishraI think that one was not done after ocata, so should be ok I think15:12
ricolinramishra thx:)15:12
ricolinAlso I have send goals response to release15:13
ricolin#link https://review.openstack.org/#/c/455121/15:13
*** therve has joined #openstack-meeting-515:13
ricolins/release/governance/15:13
ramishraricolin: yeah, I have seen that15:14
ricolinwould like guys can help to review and correct any mistake before it merged15:14
ramishradoes it mention about the py35 dsvm job?15:15
ricolinI think so15:15
ramishrabut anyway, it's just to agree that we're doing it this cycle15:15
ricolinI can update more words if it's not clear15:15
ricolinramishra yeah:)15:15
ricolinso on top of that15:16
ricolin#topic py35 gate jobs15:16
*** openstack changes topic to "py35 gate jobs (Meeting topic: heat)"15:16
ramishraSo it seems to green most of the time, I've not seen many failures15:16
ramishraI've the project-config patch ready to make it voting15:17
ricolinI think it's all green15:17
ramishrabut there are few things to consider15:17
ricolinlike what?:)15:17
ramishra1. We've disabled swift related tests15:17
ricolinyes15:17
ramishra2. There are some infra changes planned in this and next week15:18
ramishraSo may be we wait for some more time before enabling it15:18
ramishrabut If we all agree I can push that change though15:18
ricolinoh, I see what you talking about now15:18
ricolinagree with you15:18
ricolinalso can you share your patch about voting?15:19
ramishraI've not pushed it yet:)15:19
ricolinokey:)15:19
ramishraLet me do that with WIP15:19
ricolinjust like to make sure we do that with your patch15:20
ricolinok:)15:20
ricolin#action ramishra will send the voting patch for heat py35 test later15:20
ramishrahttps://review.openstack.org/#/c/456253/115:21
ramishradone:)15:21
ricolin#link https://review.openstack.org/#/c/45625315:21
ricolinnice:)15:21
ricolinalso I would like to propose about adding py35 job for python heat client and heat cfntools15:22
ricolinI already have patch wip, but would like to know what guys think about it15:22
ricolinbefore I send it out15:22
ramishrawe already have gate-python-heatclient-python35?15:23
ricolinright I mean heat-agents:)15:24
ramishraI think therve wanted to land https://review.openstack.org/#/c/425057/ before adding the py35 job for heat-agents15:25
ricolinThomas already have some py35 fix (https://review.openstack.org/#/c/425057/)15:25
ramishraSo that we can simply add a voting job15:25
therveYeah steve wasn't super nice15:26
ricolinyeah, I'm totally +1 with that:)15:26
ricolinlol15:26
therveBlocking my patch and not proposing the project-config patch is not cool15:26
ricolinthat's why I would like to make it a team's call to make it land first or not:)15:27
ramishraI'll check with stevebaker tomorrow morning if he can unblock it then:)15:27
ricolinramishra thx15:27
ricolinokey15:29
ricolin#topic Open discussion15:29
*** openstack changes topic to "Open discussion (Meeting topic: heat)"15:29
ricolintherve ramishra I would like to know is this the basic define test we talk about in PTG?15:30
ricolin#link https://review.openstack.org/#/c/454222/15:30
thervericolin, What does "define test" mean?15:30
ricolintherve we have agree about to give out a test list for refstack team for define if the environment contain `heat service`15:31
ricolinin the list we agree about basic api tests (which rabit implemented)15:32
ricolinand a basic sceniro test which use the basic core services(nova, cinder, neutron, etc)15:32
ricolinso I write that test for team to make sure if that's what we talking about15:34
ricolinas long as we can running all those test well in tempest command, I think refstack team is okey with it15:35
ricolinguys, any idea?15:36
therveI don't care15:36
ricolinokey!15:37
ramishraricolin: I'll check, but I'm not very clear about the refstack team expectations15:38
ricolinI think it's about to let them have something to propose to TC about making heat a core project15:38
ricolinthey actually don't might with the detail of tests as long as it's okey by heat15:39
ricolinAny other topic to discuss this week?:)15:40
*** Rockyg has joined #openstack-meeting-515:42
ricolinI think we can end the meeting if no other topic this week:)15:42
ramishra+115:43
ricolinthanks all:)15:43
ricolin#endmeeting15:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:43
openstackMeeting ended Wed Apr 12 15:43:10 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-12-15.00.html15:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-12-15.00.txt15:43
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-12-15.00.log.html15:43
*** jasond has left #openstack-meeting-515:44
*** rarcea has joined #openstack-meeting-515:54
*** mnaser has left #openstack-meeting-515:56
*** ralonsoh_ has joined #openstack-meeting-515:59
*** therve has left #openstack-meeting-515:59
*** ralonsoh has quit IRC16:01
*** aarefiev is now known as aarefiev_afk16:06
*** rarcea has quit IRC16:07
*** ramishra has left #openstack-meeting-516:13
*** rarcea has joined #openstack-meeting-516:20
*** mnaser has joined #openstack-meeting-516:20
*** mnaser has left #openstack-meeting-516:20
*** zenirc369 has joined #openstack-meeting-516:28
*** ricolin has quit IRC16:43
*** rarcea has quit IRC16:47
*** tongli has quit IRC16:52
*** rarcea has joined #openstack-meeting-517:00
*** ralonsoh_ has quit IRC17:36
*** rarcea has quit IRC17:43
*** krtaylor has quit IRC18:05
*** krtaylor has joined #openstack-meeting-518:49
*** iceyao has joined #openstack-meeting-519:01
*** iceyao has quit IRC19:06
*** zenirc369 has quit IRC19:17
*** rarcea has joined #openstack-meeting-519:41
*** rarcea has quit IRC20:37
*** krtaylor has quit IRC21:32

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