13:01:32 #startmeeting tricircle 13:01:34 Meeting started Wed Mar 1 13:01:32 2017 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:37 The meeting name has been set to 'tricircle' 13:01:54 #topic rollcall 13:01:56 #info joehuang 13:02:04 #info ronghui 13:02:05 #info Yipei 13:02:06 #info dongfeng 13:02:14 #info zhiyuan 13:02:24 info xiulin 13:02:57 #topic pike release schedule 13:03:13 hello, pike release schedule has been published 13:03:37 #info pike release schedule: https://releases.openstack.org/pike/schedule.html 13:03:52 for milestone pike-1 13:04:16 we have defined our own milestone on Mar.23 13:04:30 #info tricircle milestone pike-1 on Mar.23 13:04:55 for pike-2 and pike-3, we will follow community's plan 13:05:00 that is 13:05:21 #pike-2 jun.9 13:06:15 #info pike-2 Jun.9, pike-3 Jul. 28 13:06:45 any question? 13:07:00 no 13:07:04 no 13:07:07 no 13:07:07 no 13:07:16 no 13:07:18 good 13:11:54 hello 13:12:10 you are offline 13:12:12 #topic Launch pad blueprint registration and spec 13:12:17 yes 13:12:36 there are several specs in review 13:12:54 need to register blueprint too 13:13:06 and link the spec to the blueprint 13:14:21 #link https://blueprints.launchpad.net/tricircle 13:15:39 any question on blueprint 13:15:46 oh, I will register a BP for cross neutron VxLAN network tomorrow 13:16:05 will the async job management API need a BP? 13:16:18 #action register a BP for cross neutron VxLAN network 13:16:24 to dongfeng, yes 13:16:33 ok, will do that. 13:16:52 #action blueprint for async job management API 13:18:10 to ronghui, QoS need a bp too 13:18:26 ok 13:18:47 to Yipei, and same for LBaaS 13:19:01 ok, i will register a BP for LBaaS, too. 13:19:06 #actopn blueprint for QoS 13:19:20 #action blueprint for LBaaS 13:19:37 ok 13:19:41 next topic 13:19:55 #topic Pike features development 13:20:51 do you have any topic or challenge to be disucssed for feature development 13:21:35 for LBaaS, already enable allowed pair address in central neutron, and success in creating lb, listener, pool, as well as members 13:21:51 via central neutron 13:21:59 o, this is a great progress 13:22:02 however 13:22:41 i find that the vms reside in one subnet cannot communicate with each other 13:23:04 this is caused by security group 13:23:17 are they in the same host or different hosts? 13:23:24 in the same host 13:24:21 i try to login the vm through ssh under its network namespace, it fails 13:24:41 when I run LBaaS in lab, you need to create security group rule to allow ssh and icmp for ping 13:24:42 but vnc works 13:24:54 oh, i see 13:25:44 openstack security group rule create default --protocol icmp 13:25:44 openstack security group rule create default --protocol tcp --dst-port 22:22 13:25:47 openstack security group rule create default --protocol tcp --dst-port 80:80 13:25:54 #link https://docs.openstack.org/developer/devstack/guides/devstack-with-lbaas-v2.html 13:26:08 you can refer to the guide I just pasted 13:26:13 ok, got it. i will try 13:26:20 so if it works 13:26:46 i think the LBaaS among vms in the same region can work 13:26:48 there are several default seg, you may have to remmove some unused "default" 13:26:52 oh, I think we don't support updating defaulg sg currently 13:27:43 there is one action item for default rule update, may be it's time to do it 13:28:31 i want to have a try, since it is related to LBaaS 13:28:49 we need to figure out what rule can be added to default sg 13:29:00 to Yipei, is the address pair sync-ed to the local Neutron? 13:30:47 how to check? in DB? 13:31:11 to zhiyuan, but if there is not under LBaaS, VMs is ping-able? 13:31:29 oh, when installing octavia 13:31:39 it will create many security rules 13:31:59 maybe they are created by octavia 13:32:17 query in local neutron 13:32:32 not from external network 13:32:54 for the port which should have addressed pair 13:32:56 user needs to create a new sg that allow external access then update the VM port 13:33:25 default sg only allows communication between VMs 13:34:21 remote ip prefix is the cidr 13:34:46 otherwise not allowed 13:36:43 and we need to tell users that once the original remote-seg-group rule is deleted, they cannot add them back 13:37:13 then there's no differences between default sg update and normal sg update 13:40:10 ok. we can discuss this in more detail in #openstack-tricircle 13:40:23 other topics to be discussed? 13:40:48 #info default seg rule update 13:40:55 i checked. the info of allowed address pair is synced in local neutorn 13:41:01 do we have a plan of what features should be landed in pike-1 ? 13:41:32 follow the schedule we discussed in the meetup? 13:41:59 yes, we have marked features in meetup 13:42:08 ok, fine 13:42:21 #info features to be landed in pike-1 is in https://etherpad.openstack.org/p/tricircle-pike-design-topics 13:42:25 for the new meeting time? 13:42:42 yes, a poll was sent today 13:42:52 in the maillist there is no info about it 13:43:11 you can click the doodle poll link 13:43:39 http://doodle.com/poll/hz436r6wm99h4eka#table 13:43:45 here is the link 13:44:06 ok 13:44:15 thank~ 13:44:16 #info new weekly meeing poll http://doodle.com/poll/hz436r6wm99h4ekazx455iy5 13:44:21 welcome 13:44:59 other topic? 13:45:05 oh, joe, your link is not effective 13:45:12 sorry 13:45:24 how to undo 13:45:54 #info new weekly meeing poll (this one is correct) http://doodle.com/poll/hz436r6wm99h4eka#table 13:46:42 i find a "#undo topic" command 13:47:04 not topic, undo #info :( 13:48:44 ok, if no other topic, let's end the meeting 13:49:05 ok 13:49:07 ok 13:49:12 ok 13:49:13 thank you attending the meeting 13:49:20 #endmeeting