01:00:58 #startmeeting Weekly Compass team meeting 01:00:59 Meeting started Thu Aug 13 01:00:58 2015 UTC and is due to finish in 60 minutes. The chair is wshao. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:03 * xicheng waves hello to grace-yu 01:01:04 The meeting name has been set to 'weekly_compass_team_meeting' 01:02:04 #info Tentative agenda is 1) Ansible playbook and upstream repo 2) Blueprint review 01:02:32 xicheng any update on this topic? Ansible upstream? 01:02:48 #topic Ansible playbook and upstream repo 01:03:34 https://github.com/stackforge/os-ansible-deployment 01:03:46 will be the repo we will adopt from now on 01:03:58 #info chigang 01:04:00 and https://github.com/stackforge/compass-adapters will be deprecated 01:04:35 #info chenshuai 01:04:41 There was a recent announcement from the mailing list for Release: Kilo 11.1.0 01:04:48 xicheng, I'm not sure, but you may want to use git.openstack.org/stackforge.... 01:04:56 have you looked at it? 01:06:01 will use git.openstack.org instead 01:06:05 Also, everyone, if you type during the meeting, you will be added to the attendance list. and it will tally how many lines you typed during the meeting in the minutes 01:06:21 on the project pages, it says "The playbooks will enable LXC on hosts and provides the ability to deploy LXC containers for use within openstack" 01:06:39 yes i was aware of that. 01:07:05 o/ 01:07:25 is it true that by default it assumes bare metal? 01:07:30 hi, jerryz ! 01:07:46 jerryz: hi jerry 01:08:23 hi everybody, the meeting time is perfect 01:08:35 if lxc support was added in the playbook. i would assume the hosts are bare metal 01:08:46 cool, welcome jerryz. 01:09:28 xicheng: ok. Please try it out and come up with an estimate on the integration efforts 01:09:29 nice to see jerry 01:09:56 will do 01:10:07 will chigang/meimei have bandwidth to also look into this upstream Ansible (for Kilo release)? 01:10:17 * xicheng wave hello to jerryz 01:10:27 https://github.com/stackforge/os-ansible-deployment 01:10:41 wshao: I think we will try in next week 01:11:17 #action xicheng and chigang coordinate on upstream Ansible evaluation and work estimate. 01:11:42 shall we move on to blueprints? 01:11:49 #agreed 01:12:12 #topic recent blueprint review 01:12:15 https://blueprints.launchpad.net/compass/ 01:12:52 #info Jun Li 01:13:19 There is one on supporting Puppet. this is because many other installers are puppet based 01:13:34 #info Han Xu 01:13:38 shall we postpone this? https://blueprints.launchpad.net/compass/+spec/research-on-upstream-puppet-repo 01:14:08 I feel that we do not have bandwidth on it. 01:14:29 that is the least important bp i guess 01:14:44 ok move on. 01:15:02 https://blueprints.launchpad.net/compass/+spec/ironic-support 01:15:30 grace-yu: you tried the stand-alone ironic but ran into issues? 01:15:55 i haven't tried ironic so far 01:16:02 ok. 01:16:14 wshao: maybe xuhan can take it 01:16:34 chigang: ok 01:16:40 will assign it to xuhan 01:16:48 sure 01:17:14 chigang: could you do that assignment on launchpad 01:17:23 sure 01:17:37 next one: https://blueprints.launchpad.net/compass/+spec/use-keystone-as-user-mgmt 01:18:01 this was from the TC review feedback that we have our own user management, and that we should use Keystone instead 01:18:23 sdake did not mention this in his email 01:18:24 i think it is out of a misunderstanding 01:18:30 personally, I'd argue that the user in Installer may be different than cloud admin or users. 01:18:46 jerryz: I believe so. 01:18:56 sorry about that, I didn't catch that you didn't use keystone 01:19:07 compass is not a component of openstack 01:19:18 right 01:19:21 ya its a deployment tool 01:19:27 I think not using keystone is ok 01:19:37 the argumentbeing keystone needs t o be installed to be used 01:19:49 sdake: but the installer user was introduce to allow multiple clusters to be installed by different users. We are thinking the remove this feature 01:19:57 keystone is for multitenancy, installer is for single tenant auth 01:20:05 using keystone will make compass installation more complicated 01:20:19 we are not tripleo 01:20:20 ok. I will communicate with the review on this point. 01:20:42 #action wshao: address the review comments on Keystone 01:20:51 compass installs keystone, how could compass use keystone :) 01:21:24 yes, there may be some misunderstanding on this, I guess. 01:21:25 Well, lots of chicken/egg stories already in OpenStack ;-) 01:21:40 should i obsolete this bg in launchpad? 01:21:43 Don't need to increase circular dependencies 01:22:02 *bp 01:22:19 ok. cool. I think we can move to the next one. 01:22:28 https://blueprints.launchpad.net/compass/+spec/openstack-ha-support 01:22:40 Should file the comment about installer, etc, then you can abandon/close/whatever it. 01:22:55 H/A support. Currently, we support haproxy+keepalived for controllers. but do not support active active MQ and Mysql H/A 01:23:16 Rockyg: yes, will do 01:23:17 correct 01:23:25 is this an ongoing effort? 01:23:47 supporting of active/active queue and db H/A 01:23:47 wshao: is active active MQ and Mysql H/A same as compass4nfv? 01:23:48 if we use upstream OSAD, will it depend on them? 01:23:54 on H/A. we had Mysql Master+Replication for IceHouse, I believe 01:24:05 jerryz: yes, this is related to that one. 01:24:27 I don't think we have mysql HA for icehouse 01:24:34 I never did that test before 01:24:38 we need improvement in MQ and Mysql HA. 01:24:38 chenshuai: yes, it would be the same. 01:25:12 ok. chigang: xicheng: perhaps the first thing you can do on os-ansible-deployment is to figure out the current status on H/A support. 01:25:21 mainly, on Mysql and Message queue. 01:25:55 active/active rabbitmq configuration is fairly easy, one of our old chef cookbook(i guess it was grizzly) used to support it. 01:26:00 sdake: I am curious the level of support from Kolla. would appraciate if you share your experience. 01:26:30 level of support of what 01:26:31 ha? 01:26:42 yes, on h/a 01:26:57 we use rabbitmq with replicated queues and keepalived/haproxy 01:27:09 #action xicheng chigang to eval the current status of H/A support in upstream os-ansible-deployment 01:27:11 use also use percona's db thing which is mariadb+galera 01:27:28 so we have full ha, although it is unclear how well tested it is 01:27:40 it scales rom 1 node on up with the addition of nodes - automatically figures it out 01:27:51 of control nodes that is 01:27:59 sdake: cool. that is a good reference pointers. btw, do you use percona's mysql package rather than os default package repo? 01:28:09 yes percona repo 01:28:21 we use repos from all over the place 01:28:26 I find it irritating but necssary 01:28:59 I used percona mysql distro in another project. I think we will look into yours and maybe adopt percona also. 01:29:07 sdake: yes, we use mariabb+galera, but we meet up some problem 01:29:24 sure, we pick what is the best for the resulting Openstack 01:29:25 there is a bug in nova and neutron with mariadb+galera 01:29:27 i dont know the details 01:29:37 but it basically causes teh db to lock up 01:29:44 there is some workaround, again don't know the details 01:29:46 sdake: thanks for the info. it is very useful. 01:29:53 if you want to know ask [kolla] openstack-dev 01:30:03 sure, will do. 01:30:32 #action wshao: to look into percona for mysql distro and take Kolla project as a reference 01:31:17 move to the next? 01:31:22 https://blueprints.launchpad.net/compass/+spec/adapter-conf-refactoring 01:31:25 agreed 01:31:38 #info Refactor adapter's config files structure and parsing functionality 01:32:11 this is an effort to make it easier for other developers to add plugins to Compass core. 01:32:18 xicheng: what is the current status? 01:32:25 i am not sure if this is very curcial 01:32:37 ok. agreed. 01:32:57 this is assigned to you, and I will let you handle it. 01:33:08 i'll partially wrap this up by checking in the config files. 01:33:30 chigang: do you have blueprints to discuss > 01:33:31 ? 01:33:37 I help xicheng if he needs 01:33:50 can 01:34:01 we will raise today, so we can talk it next meeting 01:34:43 ok sounds good. I think that's all the blueprint I'd like to discuss today. 01:35:09 the rest is open topics, if anyone has questions or other topics to discuss 01:35:13 grace-yu i'll see what/when we should work on that. 01:36:43 if not, we can wrap up for today 01:36:45 sure 01:37:31 say did my emai hit the regular opentack-dev ml? 01:37:51 I have idea， can we separate Compass-client from compass-core 01:37:51 i think wshao said he was going to cc it to there 01:37:51 I believe so. did you see mine? 01:38:04 havnet looked- was there any followup from anyone? 01:38:26 did you post with a [compass] tag? 01:38:41 sdake on your thread, no followup. But I did another one to call for contributors. 01:39:09 jay pipes welcomed the action. 01:39:11 cool well good luck 01:39:17 thanks! 01:39:20 Thanks sdake! 01:39:39 yes, I add [Compass] tag 01:39:49 Oh, are there any bugs to discuss? 01:39:51 wierd it turns up nothing in my search 01:40:23 openstack-dev@lists.openstack.org? 01:40:26 sdake: btw, your email thread, I have modified the subject line. so it may appear as a separate thread in your mail client. 01:40:43 xuhan: yes, it is a good idea to separate the client out 01:40:51 i sort openstack-dev into a different folder 01:41:03 xuhan: could you create a bug or blueprint 01:41:07 OK 01:41:24 regarding xuhan's separating compass-client from compass-core, could you first come up with a spec? 01:41:28 or blueprint? 01:41:57 spec examples are here http://specs.openstack.org/openstack/nova-specs/specs/kilo/template.html 01:41:59 sdake: the subject is "[Compass] Regarding Ansible Playbook vs upstream repo" 01:42:13 I replied to your message. so you should be in To: line 01:43:09 ok. any other topics? 01:43:10 sdake, you should have 3 [Compass] emails. all in around1600-1715 UTC 01:43:27 no idea where they are :) 01:43:30 I have alot of folkds 01:43:33 folkders 01:43:45 i'll check the ml archive 01:43:51 thanks 01:44:05 sdake: a sign that it is not gmail :) 01:44:30 ya lookout 01:44:38 our outlook as microsoft calls it 01:44:56 haha lookout 01:45:33 all right, let's wrap up. 01:45:48 thanks to everyone 01:46:06 #endmeeting