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