| *** tianquan has joined #openstack-meeting-5 | 00:47 | |
| *** tianquan has quit IRC | 01:21 | |
| *** tzm_ has joined #openstack-meeting-5 | 01:31 | |
| *** tzm_ has quit IRC | 01:32 | |
| *** tianquan has joined #openstack-meeting-5 | 02:16 | |
| *** tianquan has quit IRC | 04:20 | |
| *** tianquan has joined #openstack-meeting-5 | 05:21 | |
| *** ricolin has joined #openstack-meeting-5 | 05:25 | |
| *** ricolin_ has joined #openstack-meeting-5 | 05:25 | |
| *** ricolin_ has quit IRC | 05:25 | |
| *** tianquan has quit IRC | 05:25 | |
| *** tianquan has joined #openstack-meeting-5 | 05:49 | |
| *** tianquan has quit IRC | 06:17 | |
| *** tianquan has joined #openstack-meeting-5 | 06:18 | |
| *** sigmavirus has quit IRC | 06:52 | |
| *** sigmavirus has joined #openstack-meeting-5 | 06:53 | |
| *** sigmavirus is now known as Guest53153 | 06:54 | |
| *** tianquan has quit IRC | 07:14 | |
| *** tianquan has joined #openstack-meeting-5 | 07:15 | |
| *** ralonsoh has joined #openstack-meeting-5 | 07:55 | |
| *** HelenYao1 has joined #openstack-meeting-5 | 08:07 | |
| *** HelenYao has quit IRC | 08:08 | |
| *** HelenYao1 is now known as HelenYao | 08:08 | |
| *** ralonsoh has quit IRC | 09:01 | |
| *** matrohon has joined #openstack-meeting-5 | 09:23 | |
| *** ralonsoh has joined #openstack-meeting-5 | 10:20 | |
| *** ricolin has quit IRC | 10:22 | |
| *** tianquan has quit IRC | 10:40 | |
| *** matrohon has quit IRC | 10:53 | |
| *** tianquan has joined #openstack-meeting-5 | 11:18 | |
| *** Guest53153 is now known as sigmavirus | 12:10 | |
| *** sigmavirus has quit IRC | 12:10 | |
| *** sigmavirus has joined #openstack-meeting-5 | 12:10 | |
| *** ralonsoh_ has joined #openstack-meeting-5 | 12:58 | |
| *** ralonsoh has quit IRC | 13:01 | |
| *** ricolin has joined #openstack-meeting-5 | 13:11 | |
| *** tianquan has quit IRC | 13:40 | |
| *** HelenYao_ has joined #openstack-meeting-5 | 13:53 | |
| *** tianquan has joined #openstack-meeting-5 | 13:56 | |
| *** tongli has joined #openstack-meeting-5 | 13:59 | |
| topol | #startmeeting interop_challenge | 14:00 |
|---|---|---|
| openstack | Meeting started Wed Mar 1 14:00:35 2017 UTC and is due to finish in 60 minutes. The chair is topol. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: interop_challenge)" | 14:00 | |
| openstack | The meeting name has been set to 'interop_challenge' | 14:00 |
| tongli | o/ | 14:00 |
| topol | Hi everyone, who is here for the interop challenge meeting today? | 14:00 |
| eeiden | o/ | 14:01 |
| HelenYao_ | o/ | 14:01 |
| topol | Ping dmellado tongli gema zhipengh markvoelker daniela_ebert skazi luzC gcb hodgepodge yaohelan | 14:01 |
| skazi_ | o/ | 14:01 |
| markvoelker | o/ | 14:01 |
| HelenYao_ | topol: pong | 14:01 |
| topol | The agenda for today can be found at: | 14:01 |
| topol | #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-03-01 | 14:01 |
| topol | We can use this same etherpad to take notes | 14:01 |
| topol | we have a packed agenda today | 14:02 |
| topol | #topic Review last meeting action items | 14:02 |
| topol | #link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-15-14.00.html | 14:02 |
| topol | Also items from PTG | 14:02 |
| *** tongli has quit IRC | 14:03 | |
| topol | #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-02-21 | 14:03 |
| topol | so first item | 14:03 |
| topol | all please review patches #link https://review. openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z | 14:03 |
| topol | 14:03 | |
| *** tongli has joined #openstack-meeting-5 | 14:03 | |
| topol | several patches out there need review | 14:03 |
| topol | any that need discussion or do folks just need to find time to review? | 14:04 |
| tongli | Yes. we do. | 14:04 |
| topol | go ahead tongli | 14:04 |
| topol | any patches we need to discuss? | 14:05 |
| tongli | yes, I think we just need to review these patches. | 14:05 |
| topol | K, sounds good | 14:05 |
| topol | #action all please review #link https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z | 14:05 |
| topol | #topic PTG Updates and decisions | 14:06 |
| *** openstack changes topic to "PTG Updates and decisions (Meeting topic: interop_challenge)" | 14:06 | |
| *** tianquan has quit IRC | 14:06 | |
| topol | #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-02-21 | 14:06 |
| topol | so one item here is mine: | 14:06 |
| topol | #action topol to contact board members to increase participation | 14:07 |
| topol | I will contact platinum and gold board members starting today | 14:07 |
| topol | lets see what else we have from our ATL getaway | 14:07 |
| tongli | @topol, we have currently 5 companies signed up. | 14:07 |
| topol | tongli, yep and we need lots more | 14:08 |
| markvoelker | #link https://wiki.openstack.org/wiki/Interop_Challenge#Boston_Summit_On_Stage_Keynote_K8S_Demo_Commited_Parties Sign up page on the wiki | 14:09 |
| topol | #topic Boston Demo, signing up sheet on the wiki page. #link https://wiki.openstack.org/wiki/Interop_Challenge | 14:09 |
| topol | markvoelker had a beter version :-) | 14:09 |
| topol | another item we had from PTG: Lauren to help get user feedback on Kube apps to use | 14:10 |
| topol | so Mark Collier actually did this | 14:10 |
| topol | #topic Uodate from MarkCollier/ Alex Polvi of coreos Kube Workload Enhancements | 14:11 |
| *** openstack changes topic to "Uodate from MarkCollier/ Alex Polvi of coreos Kube Workload Enhancements (Meeting topic: interop_challenge)" | 14:11 | |
| topol | So I dont think we had enough runway to invite Alex Polvi to this weeks meeting but here is what I got from Mark Collier: | 14:12 |
| tongli | @topol, right. next week probably. | 14:13 |
| topol | So I had an interesting chat with Alex Polvi from CoreOS about cool use cases on top of Kubernetes for the interop challenge. He suggested we look at CockroachDB, which could be configured to replicate data ACROSS all of the openstack clouds. We could do something that shows off how data is replicating in real time across each of the clouds, even though they are different public and private clouds… It could | 14:13 |
| topol | demonstrate the power of a network of clouds where openstack’s diversity in geography and providers really shines. | 14:13 |
| topol | Also got the following from Mark: | 14:13 |
| topol | Another similar option would be to use Vitess which is what Youtube uses to scale their DB. Vitess is more of a MySQL inspired approach and CockRoach is more Postgress inspired. | 14:14 |
| * markvoelker is always game for a CockroachDB workload | 14:14 | |
| topol | And finally a third piece of input: | 14:14 |
| topol | Last, but not least, one thing that I think would benefit our efforts would be to find a way for CoreOS to be part of the challenge, showing that our ecosystem spans the app tools / container layer too. If we could get their help in installing and configuring the K8S bits and maybe use their “distro” of it, that would bring them into the tent. As luck would have it, they are in the process right now of te | 14:14 |
| topol | sting their K8S product on OpenStack to make that a supported cloud platform. So there might be a way to help them ensure k8s does in fact work smoothly on any openstack cloud while also showing it off to the world in Boston | 14:14 |
| *** tianquan has joined #openstack-meeting-5 | 14:14 | |
| topol | So a lot to read for everyone there. I'll take a pause | 14:14 |
| tongli | yeah, my concerns is the time to run such a workload. | 14:15 |
| tongli | it may take a lot longer than 10 minutes if the number of nodes is greater than 3, remember Mark said that the 3 nodes workload sounded too small. | 14:16 |
| markvoelker | IMHO the DB we deploy doesn't matter a whole lot, but CockroachDB is a neat piece of tech and one that's getting a lot of attention lately (particularly after Google's Spanner announcement a week or two ago). Seems like a good choice. | 14:16 |
| topol | tongli, well if he got the fancier workload Im guessing he would bend on the number of nodes | 14:17 |
| topol | tongli but I agree it is hard to think about a fancy workload until at least we have everyone running the basic Kube workload on their cloud | 14:17 |
| kgarloff | topol: Network connectivity between clouds for replication is something that might be difficult | 14:17 |
| kgarloff | Especally the private clouds ... | 14:18 |
| topol | kgarloff, very good points | 14:18 |
| tongli | @kgarloff, agreed, | 14:18 |
| skazi_ | topol: do I understand correctly that you want to make different vendors's clouds replicas of the same DB? | 14:18 |
| kgarloff | VERY nice showcase though ... | 14:18 |
| skazi_ | kgarloff: +1 | 14:18 |
| tongli | I think that is the idea. but if every replicates from public cloud, then it should be ok for private cloud as well. | 14:19 |
| *** tianquan has quit IRC | 14:19 | |
| topol | skazi_ I think the idea is a user is using two different clouds and so yes the users workload on the two diff clouds had replicas of the same DB | 14:19 |
| tongli | we are not going into private cloud, just pulling from public cloud, it may be doable, but again needs to get things going first. | 14:19 |
| tongli | I wonder if I should switch gears working on coreos. | 14:20 |
| tongli | the k9s workload has been on ubuntu. coreos is a bit different beast. | 14:20 |
| topol | so my view is this seems like a very cool demo but we are far from feeling comfortable about pulling it off. | 14:20 |
| markvoelker | I think a sufficient starting point would just be to get a workload developed that deploys CockroachDB atop Coreos on a single cloud. If we get that squared away we can move on to linking up clusters. | 14:20 |
| topol | the other suggestion about making coreos part ofthe challenge. IS that more doabke? | 14:20 |
| markvoelker | (whether that's on multiple clouds deployed by a vendor...e.g. two instances of VIO for example...or public-private, or whatever) | 14:21 |
| topol | markvoelker, I like how you try to break it down into manageable and palatable iterative steps | 14:21 |
| * topol it seems less scary when markvoelker describes it :-) | 14:22 | |
| topol | so first part, how tough to switch to a coreos image? tongli any ideas? | 14:22 |
| skazi_ | markvoelker: +1, we should get the base working first and check the other options once we have participants list | 14:22 |
| markvoelker | topol: I think using CoreOS for the base OS is doable. Needs some elbow grease, but the mechanics shouldn't be that hard. | 14:22 |
| topol | anyone else share markvoelkers confidence? | 14:23 |
| tongli | @topol, since coreos does not have anything that ansible needs, it is a bit challenge to get it going the way how ansible deals with other OSs like ubuntu or redhat. | 14:23 |
| kgarloff | topol: Last time we tried, it was not hard to get CoreOS to work on our cloud. But getting it officially supported was smth where the CoreOS folks asked for $$$ ... if they do this always, they'll be rich after we did the challenge :-) | 14:24 |
| topol | tongli and kgarloff sounds like you both have great questions for Alex Polvi. Let's see if we can get him to show up here next week. at the very least can everyone write up questions we should ask Alex and I can forward them on? | 14:25 |
| tongli | @kgarloff, I looked at it and by following some docs I can find by googling, it did not work, of course, I have no spend a lot of time on it, but in theory it should work. | 14:25 |
| tongli | @topol, right, we should talk to Alex. | 14:26 |
| kgarloff | +1 | 14:26 |
| topol | #action all, any questions on coreos please send to topol (btopol@us.ibm.com) | 14:26 |
| topol | #action topol, try to get Alex here next week | 14:26 |
| topol | K, so lots to think about there. let's move on to next item | 14:26 |
| topol | #topic Challenges to run k8s workload if outside of US, | 14:27 |
| topol | so who added this? | 14:27 |
| topol | I assume someone outside the US? :-) | 14:27 |
| tongli | @topol, I did. | 14:28 |
| topol | tongli, the floor is yours | 14:28 |
| tongli | haha, ok. | 14:28 |
| tongli | when I wrote the workload for ubuntu, I purposely made the repo to download k8s binaries and other dependencies configurable so that you can have a local repo for the workload to download things from. | 14:29 |
| topol | thats sounds helpful | 14:30 |
| tongli | but the issue is that when you start up pod with images for container, often the repository for these container images are from docker repo or google repo. | 14:30 |
| kgarloff | tongli: Is the concern bandwidth or firewall policies? | 14:30 |
| tongli | you know that gcr is blocked in China. | 14:30 |
| markvoelker | kgarloff: the latter I think. Sounds like we need a way to configure private registries? | 14:31 |
| tongli | so I was told that often these guys will have to setup a proxy to run the work load. | 14:31 |
| tongli | the proxy will be running somewhere in US, so that the workload can go on, | 14:31 |
| tongli | the problem of doing that is again the time, it will be quite slow, | 14:31 |
| kgarloff | tongli: for replicating the DB over the net, would this be a problem as well? | 14:31 |
| tongli | true. | 14:32 |
| tongli | @kgarloff, if the DB is not a google domain, then it should be ok. | 14:32 |
| kgarloff | ok | 14:32 |
| * markvoelker wonders if anyone is planning to deploy their OpenStack on GCE and hopes his head doesn't explode | 14:33 | |
| tongli | China blocks off anything related to google, facebook, twitter, etc. | 14:33 |
| tongli | the list is long | 14:33 |
| tongli | @markvoelker, not necessarily deploy OS on gce but pulling container images from gcr. | 14:33 |
| markvoelker | tongli: I was thinking of the DB replication thing. Shouldn't be an issue. | 14:34 |
| tongli | container images can be pulled often from docker repo or gcr. | 14:34 |
| tongli | such as the one we use k8s dashboard and dns. | 14:34 |
| markvoelker | tongli: So, for the registry problem: seems like the ask here is for an option to pull from a private registry? | 14:35 |
| topol | tongli, so extra configuration at our workload (ie Kube and above) would be necessary to have private container repos or to use a proxy? | 14:35 |
| markvoelker | tongli: Might make some operations faster for folks anyway since the registry could be colocated | 14:35 |
| tongli | but anyway, these are just some problems these guys may face. making run the workload a bit more challenge. | 14:35 |
| *** fengxia41103 has joined #openstack-meeting-5 | 14:35 | |
| tongli | @markvoelker, sure making it configurable is quite easy, just more variables in the config file. | 14:36 |
| tongli | so the runner can change it, I think that the effort is to setup the local/private repo for container images. | 14:37 |
| dmellado | o/ | 14:37 |
| tongli | I have not done it myself and do not know what is involved. | 14:37 |
| topol | tongli, looks like you found some ugly issues folks may run into. the sooner we get folks trying the worload on their cloud the better | 14:37 |
| tongli | @topol, yes, exactly and more testing and more patches can really help. | 14:38 |
| markvoelker | tongli: Right. I think if folks want a local registry that's outside the scope of the workload (E.g. let them set it up however they want, just give them a variable to point to it and default to using gcr/dockerhub/whatever) | 14:38 |
| tongli | @markvoelker, ok, I will add these variables. | 14:38 |
| topol | okay, sounds like some good safety tips on this topic. Any more we need to cover on this topic for now? | 14:39 |
| markvoelker | tongli: Cool. I may see if I can set up a private Harbor registry to help test. | 14:39 |
| tongli | I will start looking into the coreos workload. | 14:39 |
| topol | markvoelker +++ Thanks | 14:39 |
| topol | #action tongli to start looking at coreos workload | 14:40 |
| topol | K, next topic | 14:40 |
| topol | k8s on coreos we have covered thoroughly which brings us to.... | 14:40 |
| topol | #topic NFV workload updates | 14:41 |
| *** openstack changes topic to "NFV workload updates (Meeting topic: interop_challenge)" | 14:41 | |
| topol | any updates on NFV? | 14:41 |
| tongli | https://review.openstack.org/#/c/439492/ | 14:41 |
| tongli | we've got a WIP on the workload, you can see at the above link. | 14:41 |
| HelenYao_ | a new bp patch is submitted to address the comments that are given after the bp is merged | 14:41 |
| HelenYao_ | a patch is in progress which will include the script | 14:42 |
| dmellado | HelenYao_: cool, thanks | 14:42 |
| tongli | @HelenYao_, thanks for the patch and the patch to address comments on the blueprint. | 14:42 |
| *** zhipeng has joined #openstack-meeting-5 | 14:43 | |
| topol | HelenYao_ will a description be added on what this does and how to run it? | 14:43 |
| HelenYao_ | when is the target date for the nfv patch? | 14:43 |
| tongli | @HelenYao_, for the workload patch, please include a README.md file to help people follow the instructions to run it. | 14:43 |
| HelenYao_ | is there any rough schedule | 14:43 |
| topol | tongli+++ yes, my thoughts exactly | 14:44 |
| HelenYao_ | tongli: sure. I was thinking about it before the meeting | 14:44 |
| tongli | haha. | 14:44 |
| tongli | that will also help you developing the workload. | 14:44 |
| topol | ok excellent, very nice to see progress on this! | 14:44 |
| HelenYao_ | do we have any rough schedule for nfv workload? | 14:45 |
| topol | and more updates on NFV? | 14:45 |
| * topol 15 mins left | 14:45 | |
| tongli | @topol, Helen is asking for the schedule. you have a requirement on that? | 14:45 |
| topol | schedule for when it needs to be completed by? | 14:46 |
| HelenYao_ | yes | 14:46 |
| topol | well if we want Mark Collier to be able to mention it in the keynote before the Boston Summit is the most critical deadline | 14:46 |
| zhipeng | topol is it still possible that we showcase on the main stage ? | 14:47 |
| topol | but ideally the sooner the better so folks can try and run it and get confidence with it. | 14:47 |
| zhipeng | if we finish it on time | 14:47 |
| topol | zhipeng, so define on time. on time means workload is done and lots of folks are able to run it on their clouds | 14:47 |
| topol | zhipeng how soon until folks can try and run it the workload on their cloud? | 14:48 |
| zhipeng | we need the time to be defined | 14:48 |
| zhipeng | when is the deadline that we need to make this happen ? | 14:48 |
| topol | zhipeng, how much time d you think you need? | 14:48 |
| topol | Right now its March 1st | 14:49 |
| topol | can you get somehting for folks to run by March 14/ | 14:49 |
| tongli | I would say if we want time for people to run and test this, we need it to be done within March. | 14:49 |
| zhipeng | ok then we could set March 14 for the first target | 14:49 |
| kgarloff | tongli: +1 | 14:49 |
| zhipeng | the latest date to have everything running ok | 14:50 |
| topol | tongli, yes must be done in March. I mentioned March 14 :-). If they are a few days over that is still probably OK | 14:50 |
| zhipeng | and end of March as the second target that we could test show for interoperability | 14:50 |
| zhipeng | would that be ok ? | 14:50 |
| topol | zhipeng we need to leave lots of time for other folks to try on their cloud. we always hit interesting unknown issues when we try all the other clouds. | 14:50 |
| zhipeng | topol I know, that's why we need a ballpark figure on the timing | 14:51 |
| zhipeng | so that we know when to hit what target | 14:51 |
| zhipeng | so that people could do the testing on time | 14:51 |
| topol | zhipeng, how is March 14 for having something for others to try on their clouds and ideally everyone running it by March 31 | 14:51 |
| zhipeng | topol that is reasonable for me :) | 14:51 |
| topol | perfect. | 14:51 |
| topol | #agreed march 14 for NFV workload available for test and March 31 for all clouds running it | 14:52 |
| topol | zhipeng that leaves us time to go back to foundation and pitch what we think would look good on the keynote stage | 14:53 |
| zhipeng | topol understood | 14:53 |
| topol | OpenStack foundation wil always want to see what we deliver before they commit to what they want to show on stage | 14:53 |
| topol | k next topic | 14:53 |
| topol | #topic Update from China Chapter Meeting | 14:54 |
| topol | tongli any updates worth mentioning? | 14:54 |
| topol | #topic Updates from China Chapter meeting | 14:54 |
| *** openstack changes topic to "Updates from China Chapter meeting (Meeting topic: interop_challenge)" | 14:54 | |
| tongli | they are having a meeting from today to Friday. | 14:55 |
| * topol weird, copy paste and setting topic dont get along | 14:55 | |
| tongli | in Xiamen, Dasiy actually presents the k8s workload to the meeting there. | 14:55 |
| topol | tongli, great! | 14:55 |
| tongli | and companies have started running k8s workload as well. | 14:55 |
| topol | tongli are they running in the gcr issues you mentioned earlier | 14:56 |
| topol | err running into | 14:56 |
| *** tiantian has joined #openstack-meeting-5 | 14:56 | |
| tongli | I suspect that they have the issues, but they hit some other configuration issues first. | 14:56 |
| tongli | I know they will hit the gcr thing later. | 14:57 |
| topol | K, any other updates from the china chapter? | 14:57 |
| tongli | that is all. | 14:57 |
| tongli | they have bi-weekly meetings. | 14:57 |
| topol | #topic open discussion | 14:57 |
| *** openstack changes topic to "open discussion (Meeting topic: interop_challenge)" | 14:58 | |
| topol | any other topics, 2 mins left :-0 | 14:58 |
| topol | I guess we are good. GREAT MEETING and it was very nice seeing folks in ATL last week! | 14:59 |
| topol | we're done | 14:59 |
| *** cwolferh has joined #openstack-meeting-5 | 14:59 | |
| topol | #endmeeting | 14:59 |
| tongli | bye | 14:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:59 | |
| openstack | Meeting ended Wed Mar 1 14:59:43 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
| *** nilles has joined #openstack-meeting-5 | 14:59 | |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-01-14.00.html | 14:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-01-14.00.txt | 14:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-01-14.00.log.html | 14:59 |
| *** tongli has quit IRC | 15:00 | |
| ricolin | #startmeeting heat | 15:00 |
| openstack | Meeting started Wed Mar 1 15:00:37 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 | |
| cwolferh | hello | 15:01 |
| nilles | hi | 15:01 |
| ricolin | hi! | 15:01 |
| *** therve has joined #openstack-meeting-5 | 15:01 | |
| therve | Hey | 15:01 |
| *** zhipeng has quit IRC | 15:02 | |
| *** HelenYao_ has quit IRC | 15:02 | |
| tiantian | hi | 15:02 |
| ricolin | #topic adding items to agenda | 15: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-03-01_1500_UTC.29 | 15:03 |
| ricolin | Any topic would like to discuss? | 15:04 |
| ricolin | I don't have much for this week | 15:04 |
| *** ralonsoh__ has joined #openstack-meeting-5 | 15:05 | |
| ricolin | I will make a recap for heat team's discussion in PTG later this week | 15:05 |
| therve | ricolin, v2 API | 15:05 |
| zaneb | o/ | 15:06 |
| ricolin | #topic V2API | 15:06 |
| *** openstack changes topic to "V2API (Meeting topic: heat)" | 15:06 | |
| *** ralonsoh_ has quit IRC | 15:07 | |
| ricolin | therve: I think we have reach some agreement about v2 api, that we might not look forward to do it | 15:07 |
| therve | ricolin, I don't know. At least not everyone knows about it :) | 15:08 |
| ricolin | therve: you're right, I will make sure it will be mention and discussed through recap | 15:09 |
| therve | ricolin, Update https://wiki.openstack.org/wiki/Heat/Blueprints/V2API too | 15:09 |
| ricolin | tiantian: any through? | 15:09 |
| *** kgarloff has left #openstack-meeting-5 | 15:09 | |
| tiantian | ricolin, I have started for v2 api and proposed some patches | 15:09 |
| tiantian | now I don't know do we need the v2 api :) | 15:10 |
| ricolin | We might need to get more idea about it | 15:11 |
| *** tiantian has quit IRC | 15:11 | |
| ricolin | I think for long term we will need a microversion support | 15:12 |
| ricolin | it might be V1.1 or V2 | 15:12 |
| ricolin | Just have to figure it out whether it sould be implement in this cycle | 15:13 |
| ricolin | #link https://blueprints.launchpad.net/heat/+spec/v2-api | 15:13 |
| *** tiantian has joined #openstack-meeting-5 | 15:15 | |
| tiantian | sorry | 15:15 |
| tiantian | disconnected | 15:15 |
| ricolin | tiantian NP | 15:16 |
| ricolin | I said we I think for long term we will need a microversion support | 15:16 |
| ricolin | Just have to figure it out whether it sould be implement in this cycle | 15:16 |
| ricolin | and V1.1 or V2 ? | 15:16 |
| tiantian | not v2 api? | 15:16 |
| ricolin | V1.1 or V2 might be two option we can seek | 15:17 |
| therve | Before going anywhere, we need to see what's the benefit for our users | 15:18 |
| therve | removing the tenant id from the URL is not a good enough reason | 15:18 |
| ricolin | tiantian: your current patch is about refactor WSGI, which I think won't be affected, just have to figure it out firt | 15:18 |
| tiantian | ok | 15:19 |
| ricolin | I will send a mail out to dev and operators to seek any feedback:) | 15:19 |
| ricolin | tiantian: sounds good?:) | 15:19 |
| tiantian | sure | 15:20 |
| ricolin | sweet! | 15:20 |
| ricolin | #topic Open discussion | 15:21 |
| *** openstack changes topic to "Open discussion (Meeting topic: heat)" | 15:21 | |
| ricolin | Any topic would like to propose? | 15:21 |
| tiantian | about the combination alarm | 15:22 |
| ricolin | yes | 15:22 |
| ricolin | right | 15:22 |
| tiantian | now we plan to set the REMOVED status | 15:22 |
| tiantian | ? | 15:22 |
| ricolin | What we going to do for an resource which been completly removed from aodh? | 15:23 |
| tiantian | how to compatible with existing stacks? | 15:23 |
| zaneb | I liked therve's idea, if that works | 15:24 |
| ricolin | tiantain: I think that might be one option to add REMOVED status | 15:24 |
| zaneb | (remap it to OS::Heat::None) | 15:24 |
| ricolin | zaneb point to None? | 15:24 |
| zaneb | as long as it remains hidden in the docs | 15:24 |
| tiantian | which actions we support for None resource? | 15:24 |
| therve | zaneb, I don't think we document things in the environment | 15:25 |
| therve | tiantian, All, presumably | 15:25 |
| zaneb | therve: what about the resource type list API? | 15:25 |
| therve | zaneb, No idea | 15:26 |
| tiantian | we won't return the HIDDEN resource types | 15:26 |
| ricolin | For some resource in future, might do more work while delete it | 15:26 |
| ricolin | that's why I'm more looking forward a new status like removed | 15:27 |
| zaneb | what if we just change the impl to inherit from OS::Heat::None and delete all the rest of the code? | 15:27 |
| tiantian | IIUC we can operate the HIDDEN resources except resource type list apI | 15:27 |
| zaneb | that might be the easiest way | 15:27 |
| ricolin | #link https://review.openstack.org/#/c/439433/ | 15:27 |
| ricolin | What about those resource which already created in env? | 15:28 |
| therve | ricolin, Even deleting the resource won't work in this case though | 15:29 |
| therve | So I don't see the benefit of the removed status | 15:29 |
| tiantian | zaneb, how? if user update/delete the resource what we can do if aodh remove the related codes? | 15:29 |
| *** tianquan has joined #openstack-meeting-5 | 15:30 | |
| tiantian | can we translate the combination alarm to composite alarm? | 15:30 |
| therve | Why would we do that? | 15:30 |
| ricolin | if we assign None to that resource, isn't that will triger a update from old type to None type, which will triger an delete action from old resource | 15:30 |
| tiantian | just look for a good way for users:) | 15:31 |
| therve | ricolin, Test it? :) | 15:31 |
| ricolin | and inside that delete method might actually call client.alarm.delete() method which might not work | 15:31 |
| zaneb | tiantian: If the Aodh team don't care enough to transition people then it certainly isn't our job imho | 15:31 |
| therve | I think setting the env should be good enough, but someone has to test it | 15:31 |
| ricolin | therve: sure | 15:32 |
| zaneb | as long as the resource type is invisible to our users but people can still delete their existing stacks that contain it, I am happy | 15:32 |
| therve | Yep | 15:32 |
| tiantian | afaik, they provide tranlation tools in last two releases | 15:33 |
| *** tianquan has quit IRC | 15:34 | |
| ricolin | I will test it out if any of above method actually works | 15:36 |
| ricolin | I will be much easier if Aodh just leave the code there... | 15:37 |
| ricolin | s/I/It | 15:37 |
| ricolin | Okey, Any other topics? :) | 15:38 |
| nilles | Just a quick beginner question regarding with the spec process | 15:38 |
| nilles | After the Neutron Trunk PTG session, ricolin approved this blueprint on launchpad: | 15:38 |
| nilles | https://blueprints.launchpad.net/heat/+spec/support-trunk-port/ | 15:38 |
| nilles | but the blueprint itself has not merged to the heat-spec repo | 15:39 |
| ricolin | We still need to review the spec | 15:39 |
| nilles | ah, ok | 15:39 |
| nilles | I tough it will be approved after the blueprint is merged | 15:40 |
| nilles | my bad :) | 15:40 |
| ricolin | NP :) | 15:40 |
| ricolin | #link https://blueprints.launchpad.net/heat/+spec/support-trunk-port/ | 15:41 |
| ricolin | Any other topics? :) | 15:41 |
| zaneb | nilles: bp approved = agreed in principle. spec merged = no more bikeshedding ;) | 15:41 |
| *** huangtianhua has joined #openstack-meeting-5 | 15:42 | |
| nilles | ok, thanks for clarifying | 15:42 |
| ricolin | zaneb: nice! | 15:42 |
| ricolin | Okey if no other thing to discuss in meeting I think we can close it earlier | 15:43 |
| *** tiantian has quit IRC | 15:44 | |
| ricolin | It will be great if guys can help on review those spec and give your advise:) | 15:44 |
| ricolin | Thanks all:) | 15:44 |
| ricolin | #endmeeting | 15:44 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:44 | |
| openstack | Meeting ended Wed Mar 1 15:44:51 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:44 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-01-15.00.html | 15:44 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-01-15.00.txt | 15:44 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-01-15.00.log.html | 15:44 |
| *** ricolin has quit IRC | 15:57 | |
| *** zhipeng has joined #openstack-meeting-5 | 15:58 | |
| *** therve has left #openstack-meeting-5 | 16:00 | |
| *** matrohon has joined #openstack-meeting-5 | 16:00 | |
| *** ricolin has joined #openstack-meeting-5 | 16:06 | |
| *** nilles has left #openstack-meeting-5 | 16:18 | |
| *** jlwhite_ has joined #openstack-meeting-5 | 16:22 | |
| *** ricolin has quit IRC | 16:25 | |
| *** ralonsoh__ has quit IRC | 16:35 | |
| *** tianquan has joined #openstack-meeting-5 | 16:36 | |
| *** tianquan has quit IRC | 16:47 | |
| *** zhipeng has quit IRC | 16:51 | |
| *** fengxia41103 has quit IRC | 17:16 | |
| *** matrohon has quit IRC | 17:35 | |
| *** tianquan has joined #openstack-meeting-5 | 18:46 | |
| *** tianquan has quit IRC | 18:51 | |
| *** stream10 has joined #openstack-meeting-5 | 19:35 | |
| *** jrist has quit IRC | 20:29 | |
| *** jrist has joined #openstack-meeting-5 | 20:42 | |
| *** stream10 has quit IRC | 20:47 | |
| *** skazi__ has joined #openstack-meeting-5 | 20:52 | |
| *** skazi_ has quit IRC | 20:53 | |
| *** matrohon has joined #openstack-meeting-5 | 21:03 | |
| *** stream10 has joined #openstack-meeting-5 | 21:30 | |
| *** tianquan has joined #openstack-meeting-5 | 21:49 | |
| *** tianquan has quit IRC | 21:54 | |
| *** stream10 has quit IRC | 22:14 | |
| *** matrohon has quit IRC | 22:40 | |
| *** tianquan has joined #openstack-meeting-5 | 22:53 | |
| *** Guest27057 is now known as zigo | 23:57 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!