| *** iceyao has joined #openstack-meeting-5 | 00:32 | |
| *** iceyao has quit IRC | 00:36 | |
| *** iceyao has joined #openstack-meeting-5 | 00:53 | |
| *** dmellado has quit IRC | 01:00 | |
| *** jlvillal has quit IRC | 01:01 | |
| *** dmellado has joined #openstack-meeting-5 | 01:02 | |
| *** jlvillal has joined #openstack-meeting-5 | 01:06 | |
| *** zbitter has joined #openstack-meeting-5 | 01:14 | |
| *** zaneb has quit IRC | 01:14 | |
| *** tdasilva has quit IRC | 01:21 | |
| *** tdasilva has joined #openstack-meeting-5 | 01:25 | |
| *** ricolin has joined #openstack-meeting-5 | 02:34 | |
| *** iceyao has quit IRC | 04:05 | |
| *** eeiden has quit IRC | 04:09 | |
| *** iceyao has joined #openstack-meeting-5 | 04:13 | |
| *** iceyao has quit IRC | 04:18 | |
| *** zenirc369 has joined #openstack-meeting-5 | 04:22 | |
| *** iceyao has joined #openstack-meeting-5 | 04:41 | |
| *** eeiden has joined #openstack-meeting-5 | 04:51 | |
| *** iceyao has quit IRC | 05:14 | |
| *** iceyao has joined #openstack-meeting-5 | 05:33 | |
| *** iceyao has quit IRC | 05:37 | |
| *** dixiaoli_ has joined #openstack-meeting-5 | 05:59 | |
| *** dixiaoli_ has quit IRC | 06:00 | |
| *** dixiaoli has joined #openstack-meeting-5 | 06:01 | |
| *** rarcea has joined #openstack-meeting-5 | 06:07 | |
| *** iceyao has joined #openstack-meeting-5 | 06:09 | |
| *** zenirc369 has quit IRC | 06:16 | |
| *** makowals has quit IRC | 06:44 | |
| *** makowals has joined #openstack-meeting-5 | 06:45 | |
| *** matrohon has joined #openstack-meeting-5 | 06:52 | |
| *** ralonsoh has joined #openstack-meeting-5 | 07:36 | |
| *** dixiaoli has quit IRC | 09:19 | |
| *** skazi_ has quit IRC | 09:21 | |
| *** skazi_ has joined #openstack-meeting-5 | 09:24 | |
| *** dixiaoli has joined #openstack-meeting-5 | 09:25 | |
| *** HelenYao has quit IRC | 09:32 | |
| *** dixiaoli_ has joined #openstack-meeting-5 | 09:40 | |
| *** dixiaoli_ has quit IRC | 09:42 | |
| *** dixiaoli has quit IRC | 09:44 | |
| *** iceyao has quit IRC | 10:18 | |
| *** iceyao has joined #openstack-meeting-5 | 10:33 | |
| *** eeiden has quit IRC | 10:37 | |
| *** iceyao has quit IRC | 10:38 | |
| *** eeiden has joined #openstack-meeting-5 | 10:52 | |
| *** iceyao has joined #openstack-meeting-5 | 10:59 | |
| *** ricolin has quit IRC | 12:09 | |
| *** zbitter is now known as zaneb | 12:14 | |
| *** ricolin has joined #openstack-meeting-5 | 12:16 | |
| *** ricolin_ has joined #openstack-meeting-5 | 12:24 | |
| *** ricolin has quit IRC | 12:27 | |
| *** ricolin_ has quit IRC | 12:27 | |
| *** ricolin has joined #openstack-meeting-5 | 12:28 | |
| *** iceyao has quit IRC | 12:29 | |
| *** iceyao has joined #openstack-meeting-5 | 12:30 | |
| *** iceyao has quit IRC | 12:35 | |
| *** iceyao has joined #openstack-meeting-5 | 12:36 | |
| *** iceyao has quit IRC | 12:40 | |
| *** iceyao has joined #openstack-meeting-5 | 12:47 | |
| *** tongli has joined #openstack-meeting-5 | 13:20 | |
| *** zhipeng has joined #openstack-meeting-5 | 13:48 | |
| *** dmellado_ has joined #openstack-meeting-5 | 13:59 | |
| *** ksumit has joined #openstack-meeting-5 | 13:59 | |
| *** kongwei has joined #openstack-meeting-5 | 14:00 | |
| tongli | #startmeeting interop_challenge | 14:01 |
|---|---|---|
| openstack | Meeting started Wed Apr 26 14:01:52 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
| *** openstack changes topic to " (Meeting topic: interop_challenge)" | 14:01 | |
| openstack | The meeting name has been set to 'interop_challenge' | 14:01 |
| markvoelker | o/ | 14:02 |
| skazi_ | o/ | 14:02 |
| tongli | Hi everyone, who is here for the interop challenge meeting today? | 14:02 |
| vkmc | o/ | 14:02 |
| ksumit | o/ | 14:02 |
| vkmc | hi all! | 14:02 |
| topol | o/ | 14:02 |
| zhipeng | o/ | 14:02 |
| *** dmellado_ has quit IRC | 14:02 | |
| dmellado | o/ | 14:02 |
| kongwei | o/ | 14:02 |
| tongli | glad to see a lot of folks here. | 14:03 |
| tongli | #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-04-26 | 14:03 |
| tongli | that is the etherpad with today's agenda. | 14:03 |
| tongli | before I start with that, I would like to give you some updates on the rehearsal Brad and I did with Mark in Austin yesterday | 14:04 |
| tongli | many people from foundation who play various roles for the summit were there while brad and I showed the demo. | 14:04 |
| tongli | the demo went well. here is how we are going to do this. | 14:05 |
| *** daniela_ebert has joined #openstack-meeting-5 | 14:05 | |
| tongli | Mark and cockroachdb and coreos guys will start a session on coreos/cockroachdb for about 5 minutes. | 14:05 |
| tongli | that is like a prelude for our session. | 14:05 |
| tongli | during that session they will create the first cockroachdb cluster. | 14:06 |
| tongli | then the show will move on to ours, mark will call out the long tables (two this time) and all the demoers to be on stage. | 14:07 |
| *** HelenYao_ has joined #openstack-meeting-5 | 14:07 | |
| tongli | then he will give a signal for everybody to start the workload, at this time, you only suppose to setup k8s cluster on your openstack cloud. while you are doing that, Brad and Mark will start talking | 14:08 |
| tongli | this is the called the first phase of the demo. | 14:08 |
| tongli | while you are running the workload, Mark and Brad probably will ask you some questions about the workload such as what it is doing at present. | 14:09 |
| tongli | your screen will be shown to the audience. | 14:09 |
| tongli | you suppose to talk about what is going on with the workload. | 14:09 |
| tongli | possibly showing the console which has the workload running and scrolling. | 14:10 |
| tongli | possibly the openstack dashboard, showing created security groups, rules, vms, volumes. | 14:10 |
| tongli | etc. | 14:10 |
| tongli | Once the workload is complete, you may be asked to show the k8s dashboard, | 14:11 |
| tongli | show the pods, services, nodes etc. it is to show that the k8s is indeed up running on openstack cloud. | 14:11 |
| beisner | o/ | 14:12 |
| tongli | once this part is done, Mark will ask one demoer at a time to do the second phase which is to join the cockroachdb cluster that was created in the prelude. | 14:13 |
| tongli | hopefully that an IP address is reserved so that everybody will have that IP address before the summit get started. | 14:13 |
| topol | one small fix. Brad and Mark will talk about whats new in this Interop Challenge for about a minute before Mark tells everyone to start the challenge (kick off their Ansible scripts) | 14:14 |
| tongli | it is possible that Mark may ask up to 4 or 5 clouds to join in. | 14:14 |
| tongli | @topol, thanks Brad for the correction. | 14:14 |
| tongli | if you are private cloud, most likely you will be asked during the first phase. | 14:15 |
| daniela_ebert | tongli: and mark will show in 5 minutes, how th join the cluster, right? | 14:15 |
| tongli | if you are public cloud, most likely you will be asked to join the cockroachdb cluster created in the prelude. | 14:15 |
| tongli | that will be the entire show. | 14:16 |
| tongli | @daniela_ebert, I do not think I understand your question. | 14:16 |
| topol | at the end the cockroachdb guys will show the public clouds joining their cockroachdb cluster | 14:16 |
| *** kongwei has quit IRC | 14:17 | |
| tongli | Mark will ask one demoer at a time to join the first cockroachdb cluster which gets created before our segment. | 14:17 |
| daniela_ebert | @tongli: are there instructions, how to join the cluster? | 14:18 |
| tongli | when he asks, demoer will simply run a command ansible-playbook with tags | 14:18 |
| tongli | that part should complete within 20 seconds. | 14:18 |
| daniela_ebert | tongli: got it | 14:18 |
| *** kongwei has joined #openstack-meeting-5 | 14:18 | |
| tongli | then mark and the cockroachdb guys will show the cockroachdb dashboard while your screen is also displayed. | 14:18 |
| tongli | the cockroachdb dashboard will display increased number of nodes in its cluster. | 14:19 |
| skazi_ | tongli: are you going to put some data on the initial cluster? | 14:19 |
| tongli | @skazi_, that is up to the prelude session. | 14:19 |
| tongli | when our node join the first cluster, we have one container in the cockroachdb pod which generate loads. | 14:20 |
| dmellado | tongli: | 14:20 |
| dmellado | in any case, I would've liked to have been aware of all these plans beforehand | 14:20 |
| tongli | the initial cluster gets created by cockroachdb guys before our show, we can careless what is there already. | 14:21 |
| dmellado | and discussed them... | 14:21 |
| dmellado | the multi cluster patch's still on review... | 14:21 |
| dmellado | https://review.openstack.org/#/c/456446/ | 14:21 |
| tongli | yes, it is. wished more people review them and run them and commented on. | 14:21 |
| tongli | but that was the code I showed to Mark and foundation yesterday. | 14:22 |
| tongli | Any other questions on the flow of the show? | 14:22 |
| ksumit | Will we be rehearsing beforehand to point to Mark who has a private cloud (phase 1) and public cloud (phase 2) ? | 14:22 |
| tongli | @ksumit, we will have rehersal Monday afternoon. | 14:23 |
| dmellado | wasn't on Sun afternoon too? | 14:23 |
| vkmc | it feels wrong that the patch for the phase 2 haven't been merged yet and we are considering it to show on stage | 14:23 |
| tongli | Sunday afternoon is just tech check. | 14:23 |
| dmellado | I mean, I get the feeling that we're been to rush on this | 14:23 |
| dmellado | to/too | 14:24 |
| tongli | making sure that the equipment all work like your laptop can show on the big screen. connection, etc. | 14:24 |
| * dmellado blames his keyboard... | 14:24 | |
| tongli | @vkmc, summit is in exactly two weeks. | 14:24 |
| vkmc | I'm aware | 14:25 |
| tongli | well actually one day less than two weeks. | 14:25 |
| tongli | we just need to get things done. | 14:25 |
| dmellado | @tongli that's quite rushed for me, if you take bank holidays also into consideration... | 14:25 |
| tongli | start running the workload and review the workload. | 14:25 |
| tongli | @dmellado, I know. | 14:25 |
| dmellado | + we set a FF for *today* actually | 14:25 |
| markvoelker | tomgli: so for the second part of the demo, are we only doing public clouds? Just wondering if I should still be planning to execute this in an environment w/external access. | 14:26 |
| vkmc | I agree, but we cannot show something that is not ready | 14:26 |
| tongli | @markvoelker, as long as you have a way to make sure that the pods can communicate with external world, then you are ok. | 14:26 |
| markvoelker | tongli: ok, thanks. I'll continue planning for such an environment then. | 14:27 |
| dmellado | @tongi, overall, besides what vkmc said, my concern is that there are quite a few plans that have been set up without taking all the participants into consideration | 14:27 |
| tongli | like the pod can hit other cloud and other cloud can hit your pods. | 14:27 |
| dmellado | I mean, all that stuff about cockroachdb guys and so | 14:27 |
| dmellado | cool, but we shoul've discussed it as a part of a meeting | 14:27 |
| dmellado | should've | 14:27 |
| topol | dmellado, the cockroach stuff was Mark Colliers vision | 14:28 |
| tongli | @dmellado, yeah, I know. many things came quite late. | 14:28 |
| topol | if we want on his keynote stage we have to make him happy | 14:28 |
| *** iceyao has quit IRC | 14:28 | |
| markvoelker | dmellado: I feel like we've been talking about the technical part of the demo for quite some time. The flow tongli laid out is pretty much what I had pictured really. Just my opinion though. | 14:28 |
| dmellado | topol: but who knew this? who discussed it? basically you and the foundation, leaving us aside... | 14:28 |
| dmellado | I mean, I can live with it but would've loved to set the things in a more open way | 14:29 |
| topol | thats not true. check the meeting notes. we have even had the cockroach guys at our irc meetings | 14:29 |
| dmellado | topol: I'll check | 14:29 |
| *** iceyao has joined #openstack-meeting-5 | 14:29 | |
| dmellado | I couldn't make it for a few meetings so that could've been it | 14:29 |
| tongli | @dmellado, please do, the cockroachdb patch has been in for quite some time. | 14:30 |
| tongli | ok. if no other question on the flow of the show, we should go into our agenda. | 14:30 |
| tongli | #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-04-26 | 14:30 |
| tongli | that link again. | 14:30 |
| topol | in any case the cockroach piece is a phase two that does a wrap up. none of our screens are shown. they will show the cockroachdb display from the cockroach guys | 14:30 |
| tongli | @topol, that is not true. | 14:31 |
| tongli | remember we talked about the screen in screen. | 14:31 |
| topol | tongl thats true. | 14:31 |
| tongli | both demoer's screen and cockroachdb guys dashboard will be shown at the same time. | 14:31 |
| tongli | and you can be asked for questions. | 14:31 |
| topol | but my point is the focus will be on seeing the public clouds show up on the cockroach display | 14:32 |
| tongli | @topol, true. | 14:32 |
| tongli | ok. action items | 14:32 |
| topol | I think it will mostly be Mark pointing at folks and saying "now you join" | 14:32 |
| tongli | #topic action items from last meeting. | 14:32 |
| *** openstack changes topic to "action items from last meeting. (Meeting topic: interop_challenge)" | 14:32 | |
| tongli | #link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-19-14.01.html | 14:33 |
| tongli | there is an action for dmellado and vkmc. | 14:33 |
| tongli | any update on that @dmellado and @vkmc? | 14:33 |
| dmellado | oh, to contact the foundation about the backup status | 14:33 |
| *** iceyao has quit IRC | 14:34 | |
| dmellado | will do that today | 14:34 |
| dmellado | shouldn't be affecting the demo in any case ;) | 14:34 |
| tongli | ok. good. I was in China and had no idea what that is about. | 14:34 |
| tongli | I wonder who has not sent the high definition company logo to Maria yet. | 14:34 |
| tongli | if yours is still missing, I am not sure if foundation has time to make a logo for you. so please double check with Maria. | 14:35 |
| tongli | other actions are for reviewing patches and freeze the code. | 14:35 |
| tongli | seems conflicting each other. | 14:36 |
| dmellado | tongli: totally, well, originally we were speaking about having a Code Freeze today | 14:36 |
| dmellado | but obviously that can't be done if your patch's on review | 14:36 |
| tongli | well, any way, let's look at the patch sets to be reviewed. | 14:36 |
| topol | at this only essential bug fixes and what we need to support the cockroach phase 2 should go in | 14:36 |
| topol | defer the rest til after the challenge | 14:36 |
| tongli | #topic patch set review | 14:37 |
| *** openstack changes topic to "patch set review (Meeting topic: interop_challenge)" | 14:37 | |
| tongli | @topol, I am ok with that. | 14:37 |
| tongli | #link https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z | 14:37 |
| vkmc | we have sent RH logo already, so that is done | 14:37 |
| dmellado | https://review.openstack.org/#/q/project:openstack/interop-workloads+status:open | 14:38 |
| tongli | I have reviewed most of these patch sets. cores please review and at least let the author know what you think. | 14:38 |
| dmellado | I wanted to discuss on what to do with the NFV workload too | 14:39 |
| tongli | the main one is this one | 14:39 |
| tongli | #link https://review.openstack.org/#/c/456446/ | 14:39 |
| tongli | only daniel and Mark reviewed it. need everybody start running it. | 14:40 |
| dmellado | zhipeng: I can live with it merged, but I'd love to have a follow up patch on some stuff ;) | 14:40 |
| tongli | @markvolker, please get some errors, I can take a look when I get back. still in Austin now, will be home tonight. | 14:40 |
| markvoelker | tongli: I was picking through this a little more last night. I have a two-or-three liner that would swap this back to using the private address for the k8s cluster | 14:40 |
| tongli | @markvoelker, using floating IP should work even in standalone case. | 14:41 |
| markvoelker | tongli: The basic problem is that in many setups nodes on the same private subnet need to use private addresses for communication with each other due to either port security or the way SNAT is setup w/various networking plugins | 14:41 |
| tongli | I've also tested that many times. | 14:41 |
| zhipeng | dmellado no problem :) | 14:41 |
| dmellado | tongli: markvoelker btw, do you know if we addressed OVH issues with non-FIP? | 14:42 |
| dmellado | zhipeng: thanks! | 14:42 |
| markvoelker | I actually only ran into this b/c I happened to run it in an environment that happened to have such a SNAT issue with an older version of SDN plugin | 14:42 |
| tongli | @markvoelker, are you saying that the floating IP can not be used to talk to machines on the same tenant network? | 14:42 |
| markvoelker | tongli: Yes. | 14:42 |
| tongli | @markvoelker, I do not know if that is a good thing. probably should be considered an issue with the cloud? | 14:43 |
| markvoelker | (not in all setups, but in many...this is very dependent on the network plugin and topology) | 14:43 |
| markvoelker | tongli: It's often associated with security decisions. From an interoperability point of view, I think it's a risk. | 14:43 |
| markvoelker | tongli: to be clear, I can personally make this work, but I think from a broader perspective it's a bit risky from an interop perspective. | 14:44 |
| *** iceyao has joined #openstack-meeting-5 | 14:44 | |
| tongli | @markvolker, so in this case, you would rather use private IPs? | 14:45 |
| markvoelker | It's also kind of undesirable from a networking perspective in that in many topologies you'll be hairpinning traffic through a router and NAT unnecessarily | 14:45 |
| tongli | that can be done easily, just a bit more code. I was thinking about that and actually did that in earlier patch set. | 14:45 |
| markvoelker | tongli: I think it would be more interoperable if we did use private IP's. It's quite simple to do (like I said: a couple lines of code). | 14:46 |
| markvoelker | I'd like to test that with phase 2 though | 14:46 |
| tongli | @markvoelker, my concern is that when you setup the first cluster (which is standalone), then you have others join in. | 14:46 |
| tongli | in that case, if your first cluster is using the private IP, the whole thing breaks down. | 14:47 |
| markvoelker | tongli: Ah. To be clear, I'm talking about using private IP's for the K8s cluster, not the cockroach bits. | 14:47 |
| markvoelker | This might be clearer if I just sent you some code once I test it this afternoon. =) | 14:47 |
| tongli | hmmm. I thought the issue was for the cockroachdb cluster. | 14:48 |
| tongli | ok. we can talk offline. | 14:48 |
| tongli | we run out time. | 14:48 |
| dmellado | tongli: besides that I put a comment on the etherpad | 14:48 |
| dmellado | on the proposed dates for checking in May | 14:48 |
| tongli | the bank holiday? @dmellado? | 14:49 |
| *** iceyao has quit IRC | 14:49 | |
| dmellado | yep | 14:49 |
| markvoelker | YEah, basically later today I'll have two separate environemnts set up that I can test the changes with for phase 2 and I'll ping you after. | 14:49 |
| tongli | I am planning to have a one hour window that all of us get on irc channel and start running the workload. | 14:49 |
| dmellado | I'd be easier if we could move that maybe to 5/4 and 5/4 | 14:49 |
| tongli | that will be the only time we can actually do this together. | 14:49 |
| dmellado | 5/3 and 5/4 | 14:49 |
| tongli | if we do it Monday, we may get a bit of time to fix issues. | 14:49 |
| tongli | the early next week will be the only time for us to do this unless we want to do it on Friday. | 14:50 |
| dmellado | I get your point, but a ton of folks, me included, won't be working | 14:50 |
| tongli | 5/1? | 14:50 |
| dmellado | 5/1 and 5/2 are bank holidays | 14:50 |
| tongli | ah, both days? | 14:50 |
| dmellado | yep | 14:51 |
| tongli | I should move to europe. | 14:51 |
| dmellado | worst case if you want, keep one day there and move another one to have US / EMEA | 14:51 |
| dmellado | xD | 14:51 |
| markvoelker | Hmm...personally I'm not sure I'll have an externally-facing environment on 5/1-2 actually, but I'll check. | 14:51 |
| tongli | how about others? | 14:51 |
| vkmc | I can make it on 5/2, but 5/1 is a holiday for me too | 14:52 |
| tongli | @dmellado, I am thinking doing once, | 14:52 |
| dmellado | tongli: then how about 5/3 | 14:52 |
| markvoelker | tongli: actually, is it possible that we could just get the first cluster up and let people try connecting to it on their own time next week rather than trying to all get together and do it at once? | 14:52 |
| tongli | so 5/3 then? | 14:52 |
| daniela_ebert | 5/1 is a bank holiday in germany too. I could make it at 5/2 | 14:52 |
| markvoelker | Would be a lot easier than coordinating across timezones... | 14:52 |
| dmellado | +1 on markvoelker approach | 14:52 |
| dmellado | and maybe set a meeting on 5/3 | 14:53 |
| dmellado | for checking issues | 14:53 |
| tongli | having a time everybody can get on is to communicate better when you have issues. | 14:53 |
| tongli | I can setup the first cluster and send out an email so that you can join. | 14:53 |
| dmellado | tongli: that'd work for me, and we can keep 5/3 to check stuff in any case | 14:53 |
| tongli | so 5/3 1400 UTC? that will be our meeting time as well for next week. | 14:54 |
| dmellado | +1 | 14:54 |
| vkmc | +1 | 14:54 |
| daniela_ebert | +1 | 14:54 |
| markvoelker | tongli: How about both? Folks that can get together 5/3 do so, but leave the cluster up so others can try throughout the week and report back? | 14:54 |
| dmellado | markvoelker: that was my suggestion ;) | 14:54 |
| tongli | @markvoelker, I will setup a cluster so that anyone can join. | 14:54 |
| tongli | I will get that up running as soon as I get home tonight. | 14:55 |
| markvoelker | tongli: Excellent, thanks! | 14:55 |
| tongli | ok, one last thing, please get yourself familiar with workload, openstack dashboard, | 14:55 |
| tongli | k8s dashboard and cockroachdb dashboard. | 14:56 |
| tongli | k8s dashboard will be at port 30000, you can hit any node floating IP. | 14:56 |
| tongli | cockroachdb dashboard is at port 8090 and also you can hit any cockroachdb node. | 14:56 |
| tongli | in stand alone mode, cockroachdb first node is on master. | 14:57 |
| * topol 3 mins left | 14:57 | |
| tongli | in non stand alone mode, corkroachdb is only on worker node. | 14:57 |
| *** ramishra has joined #openstack-meeting-5 | 14:57 | |
| tongli | so stack size 3 means only two worker nodes for cockroachdb. | 14:57 |
| *** cwolferh has joined #openstack-meeting-5 | 14:58 | |
| tongli | anything else? | 14:58 |
| tongli | if not, I need to head to airport. | 14:58 |
| dmellado | let's close it off for today | 14:58 |
| ksumit | Safe travels @tongli! | 14:58 |
| dmellado | and sync next week ;) | 14:58 |
| markvoelker | Safe travels tongli--thanks for all the work on this! | 14:58 |
| dmellado | safe travels! | 14:59 |
| tongli | #agreed, work together and create big cockroachdb cluster on 5/3 1400 UTC. | 14:59 |
| vkmc | safe travels! | 14:59 |
| vkmc | thx for your work | 14:59 |
| vkmc | o/ | 14:59 |
| tongli | great. thanks guys, this will be great. | 14:59 |
| tongli | #endmeeting | 14:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:59 | |
| openstack | Meeting ended Wed Apr 26 14:59:38 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-26-14.01.html | 14:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-26-14.01.txt | 14:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-04-26-14.01.log.html | 14:59 |
| *** daniela_ebert has quit IRC | 14:59 | |
| *** tongli has quit IRC | 15:00 | |
| *** ksumit has left #openstack-meeting-5 | 15:00 | |
| ricolin | #startmeeting heat | 15:00 |
| openstack | Meeting started Wed Apr 26 15:00:17 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: heat)" | 15:00 | |
| openstack | The meeting name has been set to 'heat' | 15:00 |
| ricolin | #topic roll call | 15:00 |
| *** openstack changes topic to "roll call (Meeting topic: heat)" | 15:00 | |
| *** therve has joined #openstack-meeting-5 | 15:00 | |
| zaneb | o/ | 15:00 |
| therve | Hi | 15:00 |
| cwolferh | hello | 15:01 |
| ramishra | hi | 15:01 |
| ricolin | hi guys:) | 15:01 |
| ricolin | #topic adding items to agenda | 15: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-26_1500_UTC.29 | 15:02 |
| ricolin | pilgrimstack1 around for floating ip? | 15:02 |
| ricolin | #topic Announce | 15:04 |
| *** openstack changes topic to "Announce (Meeting topic: heat)" | 15:04 | |
| ricolin | So we have release newton and ocata | 15:04 |
| ricolin | and the very last version of Mitaka | 15:04 |
| ramishra | ricolin, Is mitaka eol tagged yet? | 15:05 |
| ricolin | not yet | 15:05 |
| ricolin | but I think it's soon | 15:05 |
| ramishra | ok | 15:05 |
| ricolin | If more patch land in we can try to hurry another version | 15:05 |
| zaneb | iirc there weren't many left for mitaka | 15:06 |
| *** kongwei has quit IRC | 15:06 | |
| zaneb | #link https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:stable/mitaka | 15:06 |
| zaneb | those all have -1s | 15:07 |
| ricolin | zaneb yeah, and most of it get conflict advice from stable maint core | 15:07 |
| ramishra | We should abandon those then and be ready for eol tagging | 15:07 |
| zaneb | +1 | 15:07 |
| ricolin | Okey I can do that | 15:08 |
| ricolin | also there is one high bug this week | 15:08 |
| ricolin | which therve just send patch for it | 15:09 |
| ricolin | which cause by translate patch I reviewed;/ | 15:11 |
| ricolin | that's all I have for announcement | 15:11 |
| ricolin | #topic Glare integrate | 15:12 |
| *** openstack changes topic to "Glare integrate (Meeting topic: heat)" | 15:12 | |
| zaneb | if that's the worst bug we get from the translation changes we are in good shape | 15:12 |
| ricolin | zaneb try to review the entire and hope it's the worst | 15:13 |
| ricolin | So Glare! | 15:13 |
| ricolin | the spec work seems stuck | 15:14 |
| ramishra | there can be more though, Not sure if StackValidationFailed messages were like that before https://bugs.launchpad.net/heat/+bug/1686360 | 15:14 |
| openstack | Launchpad bug 1686360 in heat "unclear validation error mesage for nested stacks" [Medium,New] - Assigned to Rabi Mishra (rabi) | 15:14 |
| *** HelenYao_ has quit IRC | 15:14 | |
| ramishra | seems to be another one from that patch series | 15:14 |
| zaneb | ramishra: I wouldn't be surprised if they were always that bad | 15:15 |
| ramishra | zaneb: yeah may be | 15:16 |
| zaneb | is glare still alive? | 15:16 |
| ricolin | ramishra good timing to fix it:) | 15:16 |
| ricolin | zaneb interesting question! | 15:16 |
| ricolin | anyone interesting in finding it out?:) | 15:17 |
| ramishra | Is there a need for us doing anything with it? | 15:18 |
| ricolin | template? | 15:18 |
| zaneb | 17 reviews so far in Pike http://stackalytics.com/?module=glare&metric=marks | 15:18 |
| ramishra | oh, we had that bp, ok | 15:18 |
| ricolin | #link https://review.openstack.org/#/c/315439/ | 15:19 |
| ricolin | ramishra yep, this one | 15:19 |
| therve | ricolin, You put the glare topic? | 15:19 |
| ricolin | yes | 15:19 |
| therve | Sounds like you want to work on it | 15:20 |
| ramishra | lol | 15:20 |
| ricolin | My question to the team is, do we still need it done | 15:20 |
| therve | I mean, if it existed, it'd be a nice to have | 15:20 |
| therve | I don't think it exists, so the point is moot | 15:20 |
| zaneb | if someone wants to work on it, I think it's a Good Thing | 15:21 |
| ricolin | therve you mean exists in glare or heat:) | 15:21 |
| zaneb | but if nobody wants to work on it, that's probably because not many people are working on glare at all | 15:22 |
| therve | ricolin, I mean if glare exists | 15:22 |
| ricolin | lol | 15:22 |
| ricolin | therve zaneb point taken... | 15:22 |
| ricolin | move on:) | 15:23 |
| ricolin | #topic gerrit review dashboard | 15:23 |
| *** openstack changes topic to "gerrit review dashboard (Meeting topic: heat)" | 15:23 | |
| *** iceyao has joined #openstack-meeting-5 | 15:23 | |
| ricolin | #link https://review.openstack.org/#/c/459685/ | 15:23 |
| ricolin | this just a small tool for help on making URI for reviewing heat | 15:24 |
| ricolin | the output of the URI will looks like this | 15:24 |
| ricolin | #link goo.gl/LvYg8X | 15:24 |
| ricolin | I think It might be great if those patches can get more attention on:) | 15:26 |
| ricolin | so feel free to add the link to your review menu :) | 15:27 |
| ricolin | #topic Open discussion | 15:27 |
| *** openstack changes topic to "Open discussion (Meeting topic: heat)" | 15:27 | |
| *** iceyao has quit IRC | 15:28 | |
| ricolin | #link https://review.openstack.org/#/c/454222/ | 15:28 |
| ricolin | the heat define test | 15:28 |
| ramishra | I wanted to remove this from the config http://git.openstack.org/cgit/openstack/heat/tree/heat/common/config.py#n189 | 15:28 |
| ramishra | This does not work yet, users enable it(knowingly and unknowingly) and come with some weird errors. | 15:29 |
| therve | At least improve the doc | 15:30 |
| ramishra | Anyway, we discussed about adding a flag to stack-update command | 15:30 |
| ricolin | you propose to deprecate and remove it? | 15:30 |
| ramishra | remove it, it does not work and we anyway decided earlier to add a flag to 'stack update' | 15:31 |
| ricolin | ramishra right, which I already done but forget to upload to gerrit | 15:31 |
| ricolin | will do it tomorrow:) | 15:32 |
| ramishra | ok, we agree on removing it then | 15:33 |
| ricolin | +1 | 15:33 |
| ricolin | therve, zaneb? | 15:33 |
| zaneb | deprecate, then remove | 15:33 |
| ramishra | zaneb: it does not work, it's purely experimental all the time | 15:34 |
| ramishra | we still have patches for it https://review.openstack.org/#/c/255287/ | 15:34 |
| zaneb | right, but we can't break people's configs without warning | 15:34 |
| therve | zaneb, I don't think it breaks anything | 15:34 |
| therve | You can put whatever, we ignore unknown options | 15:35 |
| ramishra | yeah, it would not break anything | 15:35 |
| zaneb | do we? | 15:35 |
| zaneb | ok then | 15:35 |
| therve | Well "we" as oslo.config | 15:35 |
| zaneb | I thought just removing options was a big no-no for upgrades | 15:35 |
| therve | Yeah I thought so too | 15:36 |
| therve | Maybe worth asking around | 15:36 |
| ricolin | on mailing list?:) | 15:37 |
| zaneb | oh great, the project navigator is busted | 15:37 |
| therve | Wherever really | 15:37 |
| ramishra | Anyway, I will check with oslo guys | 15:37 |
| zaneb | https://governance.openstack.org/tc/reference/tags/assert_follows-standard-deprecation.html#requirements | 15:38 |
| ramishra | it would not change the software behaviour | 15:39 |
| ricolin | so `if` we have to deprecated before remove, how short we can make the process? | 15:40 |
| therve | Yeah it doesn't talk about not removing | 15:40 |
| therve | Just forward compatible | 15:40 |
| zaneb | ricolin: if we have to then deprecate in Pike, remove in Queens | 15:40 |
| therve | It's kind of the opposite, you can't add a required config option | 15:40 |
| zaneb | so if somebody can have "observe_on_update = False" in their config and that won't break when we remove it, just remove it | 15:41 |
| ramishra | yep, it would not | 15:42 |
| ricolin | IIRC it won't? | 15:42 |
| ricolin | sounds like we have agreement on that:) | 15:44 |
| ricolin | anything would like to discuss about? | 15:44 |
| therve | About to make the amqp gate voting | 15:45 |
| therve | I fixed the last slowness, so we should be good to go | 15:45 |
| *** Rockyg has joined #openstack-meeting-5 | 15:45 | |
| ramishra | therve: it still takes 10 odd mins more than the other jobs | 15:46 |
| therve | ramishra, It shouldn't since yesterday night-ish | 15:46 |
| ramishra | ok | 15:46 |
| therve | It's possible I missed something, so let me know :) | 15:47 |
| ricolin | still wait for http://status.openstack.org/openstack-health/ to show me something... | 15:48 |
| ramishra | therve: I've not checked it in the last few days | 15:48 |
| therve | ricolin, It won't show anything for that gate though | 15:48 |
| ramishra | so should be ok, if you've fixed it | 15:49 |
| therve | ramishra, Yeah the devstack change was recently merged | 15:49 |
| ricolin | therve oh, don't know that. thx | 15:49 |
| therve | ricolin, health only works on gate, not check jobs | 15:49 |
| ramishra | btw, I wanted to talk about e other thing I wanted to talk about https://review.openstack.org/#/c/407328/ | 15:49 |
| ramishra | there is something called auto_allocate_topology in neutron | 15:50 |
| ramishra | that creates a network/subnet/router, the whole set | 15:51 |
| therve | What? I thought nova handled those options? | 15:51 |
| ramishra | if you set networks=auto for server | 15:51 |
| ramishra | therve: it handles in server create | 15:52 |
| ramishra | but the issue I've is these resources would not be managed by heat | 15:52 |
| ramishra | Is that ok for us? | 15:52 |
| therve | ramishra, I don't get it, why do we need to call .get_auto_allocated_topology? | 15:53 |
| ramishra | if someone changes to auto for a server from none during an update? | 15:53 |
| ricolin | in a part that if we try to delete a stack, those extra resources won't block us right? | 15:53 |
| therve | ramishra, So that means we are re-implementing the meaning of auto inside heat? | 15:54 |
| therve | Instead of passing the flag to nova? | 15:54 |
| ramishra | therve: yeah, to some extent | 15:54 |
| therve | Giant -2 then from me | 15:54 |
| zaneb | it feels like that's what we're doing if we allow updates of that property | 15:54 |
| therve | Yeah let's just not allow update on that | 15:54 |
| therve | We're going to have other issues otherwise anyway | 15:55 |
| ramishra | Again, I don't know if nova would delete these neutron resources when you delete the server | 15:55 |
| therve | Well then that's a nova bug | 15:55 |
| zaneb | therve: having your server replaced because you wanted to add a network to it also sucks though :/ | 15:55 |
| ramishra | so those may be left behind after the stack is deleted | 15:55 |
| therve | zaneb, Ah yeah I guess there is no way to not go into a FAILED state? | 15:56 |
| therve | Like fail at validation or something | 15:56 |
| therve | We need to do less network garbage in the nova resource, not more | 15:57 |
| zaneb | ramishra: IIUC leaving the network + router behind is OK/expected. the port should get cleaned up by Nova | 15:57 |
| therve | This is already a giant mess in needs of refactoring | 15:57 |
| zaneb | it may not be so bad | 15:57 |
| zaneb | therve: if a resource is FAILED it's just going to get replaced on the next update | 15:57 |
| therve | Yeah that I know :) | 15:58 |
| zaneb | therve: whoops, missed the 'not' in there | 15:58 |
| therve | Ah right | 15:58 |
| zaneb | there's an 'immutable | 15:58 |
| zaneb | property thing | 15:58 |
| zaneb | can never remember what that does | 15:59 |
| ramishra | zaneb: why do you think leaving the resources behind which were created by the stack(read nova) would be OK? | 16:00 |
| therve | ramishra, Because that happens when you do nova boot? | 16:00 |
| therve | ricolin, eom! | 16:00 |
| ricolin | going back to heat!:) | 16:01 |
| zaneb | ramishra: so it sounds like the idea is that if you're using 'auto' in the tenant, then the first server will create a network, router, & subnets and everything will just use that | 16:01 |
| ricolin | #endmeeting | 16:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:01 | |
| openstack | Meeting ended Wed Apr 26 16:01:33 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-26-15.00.html | 16:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-26-15.00.txt | 16:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-04-26-15.00.log.html | 16:01 |
| *** iceyao has joined #openstack-meeting-5 | 16:04 | |
| *** iceyao has quit IRC | 16:09 | |
| *** matrohon has quit IRC | 16:19 | |
| *** aarefiev is now known as aarefiev_afk | 16:30 | |
| *** zhipeng has quit IRC | 16:55 | |
| *** ksumit has joined #openstack-meeting-5 | 17:15 | |
| *** ksumit has quit IRC | 17:17 | |
| *** Rockyg has quit IRC | 17:26 | |
| *** ricolin has quit IRC | 17:30 | |
| *** makowals_ has joined #openstack-meeting-5 | 17:32 | |
| *** makowals has quit IRC | 17:34 | |
| *** ralonsoh has quit IRC | 18:17 | |
| *** rarcea has quit IRC | 18:56 | |
| *** ramishra has quit IRC | 19:08 | |
| *** ramishra has joined #openstack-meeting-5 | 19:10 | |
| *** ramishra has quit IRC | 19:36 | |
| *** ramishra has joined #openstack-meeting-5 | 19:38 | |
| *** ramishra has quit IRC | 19:43 | |
| *** ramishra has joined #openstack-meeting-5 | 19:45 | |
| *** ramishra has quit IRC | 19:51 | |
| *** ramishra has joined #openstack-meeting-5 | 19:51 | |
| *** ramishra has quit IRC | 19:56 | |
| *** iceyao has joined #openstack-meeting-5 | 19:57 | |
| *** iceyao has quit IRC | 20:01 | |
| *** ramishra has joined #openstack-meeting-5 | 20:03 | |
| *** ramishra has quit IRC | 20:08 | |
| *** ramishra has joined #openstack-meeting-5 | 20:12 | |
| *** matrohon has joined #openstack-meeting-5 | 20:15 | |
| *** ramishra has quit IRC | 20:22 | |
| *** ramishra has joined #openstack-meeting-5 | 20:29 | |
| *** ramishra has quit IRC | 20:39 | |
| *** ramishra has joined #openstack-meeting-5 | 20:41 | |
| *** dixiaoli has joined #openstack-meeting-5 | 20:43 | |
| *** iceyao has joined #openstack-meeting-5 | 20:46 | |
| *** dixiaoli has quit IRC | 20:47 | |
| *** ramishra has quit IRC | 20:48 | |
| *** iceyao has quit IRC | 20:51 | |
| *** ramishra has joined #openstack-meeting-5 | 20:55 | |
| *** wxy has quit IRC | 20:58 | |
| *** therve has left #openstack-meeting-5 | 21:15 | |
| *** ramishra has quit IRC | 21:15 | |
| *** ramishra has joined #openstack-meeting-5 | 21:17 | |
| *** matrohon has quit IRC | 21:21 | |
| *** ramishra has quit IRC | 21:21 | |
| *** ramishra has joined #openstack-meeting-5 | 21:22 | |
| *** iceyao has joined #openstack-meeting-5 | 21:31 | |
| *** ramishra has quit IRC | 21:35 | |
| *** iceyao has quit IRC | 21:36 | |
| *** ramishra has joined #openstack-meeting-5 | 21:38 | |
| *** ramishra has quit IRC | 21:43 | |
| *** ramishra has joined #openstack-meeting-5 | 21:44 | |
| *** ramishra has quit IRC | 21:52 | |
| *** ramishra has joined #openstack-meeting-5 | 21:53 | |
| *** ramishra has quit IRC | 22:04 | |
| *** ramishra has joined #openstack-meeting-5 | 22:06 | |
| *** ramishra has quit IRC | 22:12 | |
| *** iceyao has joined #openstack-meeting-5 | 22:13 | |
| *** ramishra has joined #openstack-meeting-5 | 22:13 | |
| *** iceyao has quit IRC | 22:18 | |
| *** ramishra has quit IRC | 23:21 | |
| *** ramishra has joined #openstack-meeting-5 | 23:23 | |
| *** ramishra has quit IRC | 23:28 | |
| *** ramishra has joined #openstack-meeting-5 | 23:36 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!