| *** yamamoto has quit IRC | 00:00 | |
| *** salv-orl_ has quit IRC | 00:03 | |
| *** harshs has quit IRC | 00:06 | |
| *** galstrom_zzz is now known as galstrom | 00:07 | |
| *** puranamr has quit IRC | 00:07 | |
| *** puranamr has joined #openstack-meeting-4 | 00:08 | |
| *** baoli has quit IRC | 00:10 | |
| *** galstrom is now known as galstrom_zzz | 00:12 | |
| *** banix has joined #openstack-meeting-4 | 00:15 | |
| *** markvoelker has joined #openstack-meeting-4 | 00:15 | |
| *** vishwanathj has quit IRC | 00:16 | |
| *** markvoelker has quit IRC | 00:21 | |
| *** sankarshan is now known as sankarshan_away | 00:21 | |
| *** jckasper has joined #openstack-meeting-4 | 00:23 | |
| *** xingchao_ has joined #openstack-meeting-4 | 00:24 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 00:32 | |
| *** galstrom_zzz is now known as galstrom | 00:35 | |
| *** bharath has quit IRC | 00:37 | |
| *** Rockyg has joined #openstack-meeting-4 | 00:43 | |
| *** baoli has joined #openstack-meeting-4 | 00:43 | |
| *** galstrom is now known as galstrom_zzz | 00:44 | |
| *** wshao has joined #openstack-meeting-4 | 00:46 | |
| *** Grace has joined #openstack-meeting-4 | 00:54 | |
| *** Grace is now known as Guest44162 | 00:55 | |
| *** xingchao_ has quit IRC | 00:55 | |
| *** Guest44162 has left #openstack-meeting-4 | 00:55 | |
| *** grace-yu has joined #openstack-meeting-4 | 00:55 | |
| *** xicheng has joined #openstack-meeting-4 | 00:55 | |
| xicheng | #info | 00:56 |
|---|---|---|
| *** ChiZhang has joined #openstack-meeting-4 | 00:57 | |
| *** ChiZhang has left #openstack-meeting-4 | 00:58 | |
| *** baoli has quit IRC | 00:58 | |
| *** xingchao_ has joined #openstack-meeting-4 | 00:58 | |
| *** sbog has quit IRC | 00:58 | |
| *** sankarshan_away has quit IRC | 00:58 | |
| Rockyg | o/ | 00:59 |
| *** ChiZhang has joined #openstack-meeting-4 | 00:59 | |
| * xicheng waves hello | 01:00 | |
| *** chenshuai has joined #openstack-meeting-4 | 01:00 | |
| grace-yu | hi xicheng, how are you? | 01:00 |
| wshao | #startmeeting Weekly Compass team meeting | 01:00 |
| 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:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 01:01 |
| *** openstack changes topic to " (Meeting topic: Weekly Compass team meeting)" | 01:01 | |
| * xicheng waves hello to grace-yu | 01:01 | |
| openstack | The meeting name has been set to 'weekly_compass_team_meeting' | 01:01 |
| wshao | #info Tentative agenda is 1) Ansible playbook and upstream repo 2) Blueprint review | 01:02 |
| wshao | xicheng any update on this topic? Ansible upstream? | 01:02 |
| xicheng | #topic Ansible playbook and upstream repo | 01:02 |
| *** syang has joined #openstack-meeting-4 | 01:03 | |
| xicheng | https://github.com/stackforge/os-ansible-deployment | 01:03 |
| *** chigang has joined #openstack-meeting-4 | 01:03 | |
| xicheng | will be the repo we will adopt from now on | 01:03 |
| chigang | #info chigang | 01:03 |
| xicheng | and https://github.com/stackforge/compass-adapters will be deprecated | 01:04 |
| *** baigk has joined #openstack-meeting-4 | 01:04 | |
| *** sbog has joined #openstack-meeting-4 | 01:04 | |
| chenshuai | #info chenshuai | 01:04 |
| wshao | There was a recent announcement from the mailing list for Release: Kilo 11.1.0 | 01:04 |
| Rockyg | xicheng, I'm not sure, but you may want to use git.openstack.org/stackforge.... | 01:04 |
| wshao | have you looked at it? | 01:04 |
| xicheng | will use git.openstack.org instead | 01:06 |
| *** xingchao_ has quit IRC | 01:06 | |
| 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 |
| 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 |
| *** xuhan has joined #openstack-meeting-4 | 01:06 | |
| xicheng | yes i was aware of that. | 01:06 |
| jerryz | o/ | 01:07 |
| wshao | is it true that by default it assumes bare metal? | 01:07 |
| Rockyg | hi, jerryz ! | 01:07 |
| *** kun_huang has joined #openstack-meeting-4 | 01:07 | |
| chigang | jerryz: hi jerry | 01:07 |
| *** meimei has joined #openstack-meeting-4 | 01:08 | |
| jerryz | hi everybody, the meeting time is perfect | 01:08 |
| xicheng | if lxc support was added in the playbook. i would assume the hosts are bare metal | 01:08 |
| wshao | cool, welcome jerryz. | 01:08 |
| *** echoingumesh has quit IRC | 01:09 | |
| wshao | xicheng: ok. Please try it out and come up with an estimate on the integration efforts | 01:09 |
| meimei | nice to see jerry | 01:09 |
| *** echoingumesh has joined #openstack-meeting-4 | 01:09 | |
| xicheng | will do | 01:09 |
| wshao | will chigang/meimei have bandwidth to also look into this upstream Ansible (for Kilo release)? | 01:10 |
| * xicheng wave hello to jerryz | 01:10 | |
| wshao | https://github.com/stackforge/os-ansible-deployment | 01:10 |
| chigang | wshao: I think we will try in next week | 01:10 |
| *** Brian_ has joined #openstack-meeting-4 | 01:10 | |
| wshao | #action xicheng and chigang coordinate on upstream Ansible evaluation and work estimate. | 01:11 |
| *** salv-orlando has joined #openstack-meeting-4 | 01:11 | |
| wshao | shall we move on to blueprints? | 01:11 |
| xicheng | #agreed | 01:11 |
| *** docaedo has joined #openstack-meeting-4 | 01:11 | |
| wshao | #topic recent blueprint review | 01:12 |
| *** openstack changes topic to "recent blueprint review (Meeting topic: Weekly Compass team meeting)" | 01:12 | |
| wshao | https://blueprints.launchpad.net/compass/ | 01:12 |
| *** MatthewL3 has joined #openstack-meeting-4 | 01:12 | |
| MatthewL3 | #info Jun Li | 01:12 |
| wshao | There is one on supporting Puppet. this is because many other installers are puppet based | 01:13 |
| *** echoingumesh has quit IRC | 01:13 | |
| xuhan | #info Han Xu | 01:13 |
| *** echoingumesh has joined #openstack-meeting-4 | 01:13 | |
| wshao | shall we postpone this? https://blueprints.launchpad.net/compass/+spec/research-on-upstream-puppet-repo | 01:13 |
| wshao | I feel that we do not have bandwidth on it. | 01:14 |
| xicheng | that is the least important bp i guess | 01:14 |
| wshao | ok move on. | 01:14 |
| wshao | https://blueprints.launchpad.net/compass/+spec/ironic-support | 01:15 |
| wshao | grace-yu: you tried the stand-alone ironic but ran into issues? | 01:15 |
| grace-yu | i haven't tried ironic so far | 01:15 |
| wshao | ok. | 01:16 |
| chigang | wshao: maybe xuhan can take it | 01:16 |
| wshao | chigang: ok | 01:16 |
| wshao | will assign it to xuhan | 01:16 |
| grace-yu | sure | 01:16 |
| wshao | chigang: could you do that assignment on launchpad | 01:17 |
| chigang | sure | 01:17 |
| wshao | next one: https://blueprints.launchpad.net/compass/+spec/use-keystone-as-user-mgmt | 01:17 |
| wshao | this was from the TC review feedback that we have our own user management, and that we should use Keystone instead | 01:18 |
| *** salv-orlando has quit IRC | 01:18 | |
| xicheng | sdake did not mention this in his email | 01:18 |
| jerryz | i think it is out of a misunderstanding | 01:18 |
| wshao | personally, I'd argue that the user in Installer may be different than cloud admin or users. | 01:18 |
| wshao | jerryz: I believe so. | 01:18 |
| sdake | sorry about that, I didn't catch that you didn't use keystone | 01:18 |
| jerryz | compass is not a component of openstack | 01:19 |
| grace-yu | right | 01:19 |
| sdake | ya its a deployment tool | 01:19 |
| sdake | I think not using keystone is ok | 01:19 |
| sdake | the argumentbeing keystone needs t o be installed to be used | 01:19 |
| 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 |
| sdake | keystone is for multitenancy, installer is for single tenant auth | 01:19 |
| grace-yu | using keystone will make compass installation more complicated | 01:20 |
| jerryz | we are not tripleo | 01:20 |
| wshao | ok. I will communicate with the review on this point. | 01:20 |
| wshao | #action wshao: address the review comments on Keystone | 01:20 |
| sdake | compass installs keystone, how could compass use keystone :) | 01:20 |
| *** kun_huang has left #openstack-meeting-4 | 01:21 | |
| wshao | yes, there may be some misunderstanding on this, I guess. | 01:21 |
| Rockyg | Well, lots of chicken/egg stories already in OpenStack ;-) | 01:21 |
| xicheng | should i obsolete this bg in launchpad? | 01:21 |
| Rockyg | Don't need to increase circular dependencies | 01:21 |
| xicheng | *bp | 01:22 |
| wshao | ok. cool. I think we can move to the next one. | 01:22 |
| wshao | https://blueprints.launchpad.net/compass/+spec/openstack-ha-support | 01:22 |
| Rockyg | Should file the comment about installer, etc, then you can abandon/close/whatever it. | 01:22 |
| wshao | H/A support. Currently, we support haproxy+keepalived for controllers. but do not support active active MQ and Mysql H/A | 01:22 |
| wshao | Rockyg: yes, will do | 01:23 |
| grace-yu | correct | 01:23 |
| xicheng | is this an ongoing effort? | 01:23 |
| *** jpeeler has quit IRC | 01:23 | |
| xicheng | supporting of active/active queue and db H/A | 01:23 |
| chenshuai | wshao: is active active MQ and Mysql H/A same as compass4nfv? | 01:23 |
| jerryz | if we use upstream OSAD, will it depend on them? | 01:23 |
| wshao | on H/A. we had Mysql Master+Replication for IceHouse, I believe | 01:23 |
| wshao | jerryz: yes, this is related to that one. | 01:24 |
| grace-yu | I don't think we have mysql HA for icehouse | 01:24 |
| grace-yu | I never did that test before | 01:24 |
| chigang | we need improvement in MQ and Mysql HA. | 01:24 |
| wshao | chenshuai: yes, it would be the same. | 01:24 |
| 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 |
| wshao | mainly, on Mysql and Message queue. | 01:25 |
| xicheng | active/active rabbitmq configuration is fairly easy, one of our old chef cookbook(i guess it was grizzly) used to support it. | 01:25 |
| wshao | sdake: I am curious the level of support from Kolla. would appraciate if you share your experience. | 01:26 |
| sdake | level of support of what | 01:26 |
| sdake | ha? | 01:26 |
| wshao | yes, on h/a | 01:26 |
| sdake | we use rabbitmq with replicated queues and keepalived/haproxy | 01:26 |
| wshao | #action xicheng chigang to eval the current status of H/A support in upstream os-ansible-deployment | 01:27 |
| sdake | use also use percona's db thing which is mariadb+galera | 01:27 |
| sdake | so we have full ha, although it is unclear how well tested it is | 01:27 |
| sdake | it scales rom 1 node on up with the addition of nodes - automatically figures it out | 01:27 |
| sdake | of control nodes that is | 01:27 |
| wshao | sdake: cool. that is a good reference pointers. btw, do you use percona's mysql package rather than os default package repo? | 01:27 |
| sdake | yes percona repo | 01:28 |
| sdake | we use repos from all over the place | 01:28 |
| sdake | I find it irritating but necssary | 01:28 |
| wshao | I used percona mysql distro in another project. I think we will look into yours and maybe adopt percona also. | 01:28 |
| chigang | sdake: yes, we use mariabb+galera, but we meet up some problem | 01:29 |
| wshao | sure, we pick what is the best for the resulting Openstack | 01:29 |
| sdake | there is a bug in nova and neutron with mariadb+galera | 01:29 |
| sdake | i dont know the details | 01:29 |
| sdake | but it basically causes teh db to lock up | 01:29 |
| sdake | there is some workaround, again don't know the details | 01:29 |
| wshao | sdake: thanks for the info. it is very useful. | 01:29 |
| sdake | if you want to know ask [kolla] openstack-dev | 01:29 |
| wshao | sure, will do. | 01:30 |
| wshao | #action wshao: to look into percona for mysql distro and take Kolla project as a reference | 01:30 |
| *** dannywilson has quit IRC | 01:31 | |
| wshao | move to the next? | 01:31 |
| wshao | https://blueprints.launchpad.net/compass/+spec/adapter-conf-refactoring | 01:31 |
| chenshuai | agreed | 01:31 |
| wshao | #info Refactor adapter's config files structure and parsing functionality | 01:31 |
| wshao | this is an effort to make it easier for other developers to add plugins to Compass core. | 01:32 |
| wshao | xicheng: what is the current status? | 01:32 |
| xicheng | i am not sure if this is very curcial | 01:32 |
| wshao | ok. agreed. | 01:32 |
| wshao | this is assigned to you, and I will let you handle it. | 01:32 |
| xicheng | i'll partially wrap this up by checking in the config files. | 01:33 |
| wshao | chigang: do you have blueprints to discuss > | 01:33 |
| wshao | ? | 01:33 |
| grace-yu | I help xicheng if he needs | 01:33 |
| grace-yu | can | 01:33 |
| chigang | we will raise today, so we can talk it next meeting | 01:34 |
| wshao | ok sounds good. I think that's all the blueprint I'd like to discuss today. | 01:34 |
| wshao | the rest is open topics, if anyone has questions or other topics to discuss | 01:35 |
| xicheng | grace-yu i'll see what/when we should work on that. | 01:35 |
| wshao | if not, we can wrap up for today | 01:36 |
| grace-yu | sure | 01:36 |
| sdake | say did my emai hit the regular opentack-dev ml? | 01:37 |
| xuhan | I have idea， can we separate Compass-client from compass-core | 01:37 |
| sdake | i think wshao said he was going to cc it to there | 01:37 |
| wshao | I believe so. did you see mine? | 01:37 |
| sdake | havnet looked- was there any followup from anyone? | 01:38 |
| sdake | did you post with a [compass] tag? | 01:38 |
| wshao | sdake on your thread, no followup. But I did another one to call for contributors. | 01:38 |
| *** vivek-ebay has quit IRC | 01:39 | |
| wshao | jay pipes welcomed the action. | 01:39 |
| sdake | cool well good luck | 01:39 |
| wshao | thanks! | 01:39 |
| Rockyg | Thanks sdake! | 01:39 |
| wshao | yes, I add [Compass] tag | 01:39 |
| Rockyg | Oh, are there any bugs to discuss? | 01:39 |
| sdake | wierd it turns up nothing in my search | 01:39 |
| sdake | openstack-dev@lists.openstack.org? | 01:40 |
| 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 |
| wshao | xuhan: yes, it is a good idea to separate the client out | 01:40 |
| *** echoingumesh has quit IRC | 01:40 | |
| sdake | i sort openstack-dev into a different folder | 01:40 |
| wshao | xuhan: could you create a bug or blueprint | 01:41 |
| xuhan | OK | 01:41 |
| *** echoingumesh has joined #openstack-meeting-4 | 01:41 | |
| xicheng | regarding xuhan's separating compass-client from compass-core, could you first come up with a spec? | 01:41 |
| xicheng | or blueprint? | 01:41 |
| xicheng | spec examples are here http://specs.openstack.org/openstack/nova-specs/specs/kilo/template.html | 01:41 |
| wshao | sdake: the subject is "[Compass] Regarding Ansible Playbook vs upstream repo" | 01:41 |
| wshao | I replied to your message. so you should be in To: line | 01:42 |
| wshao | ok. any other topics? | 01:43 |
| Rockyg | sdake, you should have 3 [Compass] emails. all in around1600-1715 UTC | 01:43 |
| sdake | no idea where they are :) | 01:43 |
| sdake | I have alot of folkds | 01:43 |
| sdake | folkders | 01:43 |
| sdake | i'll check the ml archive | 01:43 |
| sdake | thanks | 01:43 |
| wshao | sdake: a sign that it is not gmail :) | 01:44 |
| sdake | ya lookout | 01:44 |
| sdake | our outlook as microsoft calls it | 01:44 |
| wshao | haha lookout | 01:44 |
| *** grace-yu has quit IRC | 01:45 | |
| wshao | all right, let's wrap up. | 01:45 |
| wshao | thanks to everyone | 01:45 |
| *** echoingumesh has quit IRC | 01:45 | |
| wshao | #endmeeting | 01:46 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 01:46 | |
| openstack | Meeting ended Thu Aug 13 01:46:06 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 01:46 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/weekly_compass_team_meeting/2015/weekly_compass_team_meeting.2015-08-13-01.00.html | 01:46 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/weekly_compass_team_meeting/2015/weekly_compass_team_meeting.2015-08-13-01.00.txt | 01:46 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/weekly_compass_team_meeting/2015/weekly_compass_team_meeting.2015-08-13-01.00.log.html | 01:46 |
| *** ChiZhang has quit IRC | 01:46 | |
| *** xicheng has quit IRC | 01:46 | |
| *** syang has quit IRC | 01:48 | |
| *** wshao has quit IRC | 01:49 | |
| *** Rockyg has quit IRC | 01:50 | |
| *** jmcbride has joined #openstack-meeting-4 | 01:59 | |
| *** jmcbride has quit IRC | 01:59 | |
| *** baoli has joined #openstack-meeting-4 | 02:01 | |
| *** markvoelker has joined #openstack-meeting-4 | 02:05 | |
| *** vivek-ebay has joined #openstack-meeting-4 | 02:06 | |
| *** xuhan has quit IRC | 02:07 | |
| *** sankarshan has joined #openstack-meeting-4 | 02:11 | |
| *** padkrish_ has quit IRC | 02:14 | |
| *** padkrish has joined #openstack-meeting-4 | 02:14 | |
| *** padkrish has quit IRC | 02:18 | |
| *** salv-orl_ has joined #openstack-meeting-4 | 02:23 | |
| *** salv-orl_ has quit IRC | 02:31 | |
| *** baoli has quit IRC | 02:34 | |
| *** baoli has joined #openstack-meeting-4 | 02:34 | |
| *** vivek-ebay has quit IRC | 02:55 | |
| *** vivek-ebay has joined #openstack-meeting-4 | 02:56 | |
| *** KunalGandhi has quit IRC | 03:00 | |
| *** yamamoto has joined #openstack-meeting-4 | 03:03 | |
| *** baoli has quit IRC | 03:04 | |
| *** baoli has joined #openstack-meeting-4 | 03:15 | |
| *** galstrom_zzz is now known as galstrom | 03:26 | |
| *** salv-orlando has joined #openstack-meeting-4 | 03:33 | |
| *** Brian_ has quit IRC | 03:34 | |
| *** bharath has joined #openstack-meeting-4 | 03:38 | |
| *** Brian has joined #openstack-meeting-4 | 03:42 | |
| *** Brian is now known as Guest93870 | 03:42 | |
| *** bharath has quit IRC | 03:42 | |
| *** jerryz has quit IRC | 03:45 | |
| *** salv-orlando has quit IRC | 03:45 | |
| *** puranamr has quit IRC | 03:53 | |
| *** puranamr has joined #openstack-meeting-4 | 03:54 | |
| *** padkrish has joined #openstack-meeting-4 | 04:01 | |
| *** puranamr has quit IRC | 04:03 | |
| *** puranamr has joined #openstack-meeting-4 | 04:03 | |
| *** Guest93870 has quit IRC | 04:04 | |
| *** nhairston has joined #openstack-meeting-4 | 04:09 | |
| *** vivek-ebay has quit IRC | 04:12 | |
| *** padkrish has quit IRC | 04:14 | |
| *** padkrish has joined #openstack-meeting-4 | 04:15 | |
| *** galstrom is now known as galstrom_zzz | 04:15 | |
| *** vivek-ebay has joined #openstack-meeting-4 | 04:21 | |
| *** ivar-lazzaro has quit IRC | 04:24 | |
| *** padkrish has quit IRC | 04:25 | |
| *** padkrish has joined #openstack-meeting-4 | 04:26 | |
| *** harshs has joined #openstack-meeting-4 | 04:30 | |
| *** baoli has quit IRC | 04:31 | |
| *** fawadkhaliq has joined #openstack-meeting-4 | 04:32 | |
| *** fawadkhaliq has quit IRC | 04:39 | |
| *** fawadkhaliq has joined #openstack-meeting-4 | 04:39 | |
| *** salv-orlando has joined #openstack-meeting-4 | 04:47 | |
| *** banix has quit IRC | 04:52 | |
| *** Brian has joined #openstack-meeting-4 | 04:53 | |
| *** Brian is now known as Guest50430 | 04:53 | |
| *** harshs has quit IRC | 04:56 | |
| *** fawadkhaliq has quit IRC | 04:57 | |
| *** chenshuai has quit IRC | 04:59 | |
| *** salv-orlando has quit IRC | 04:59 | |
| *** harshs has joined #openstack-meeting-4 | 05:03 | |
| *** fawadkhaliq has joined #openstack-meeting-4 | 05:06 | |
| *** jpekkari has joined #openstack-meeting-4 | 05:06 | |
| *** cdelatte has quit IRC | 05:13 | |
| *** cdelatte has joined #openstack-meeting-4 | 05:13 | |
| *** vivek-ebay has quit IRC | 05:15 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 05:27 | |
| *** armax has quit IRC | 05:30 | |
| *** cdelatte has quit IRC | 05:33 | |
| *** nhairston has quit IRC | 05:33 | |
| *** markvoelker has quit IRC | 05:41 | |
| *** delattec has joined #openstack-meeting-4 | 05:41 | |
| *** med_ has quit IRC | 05:50 | |
| *** yamamoto has quit IRC | 05:50 | |
| *** yamamoto has joined #openstack-meeting-4 | 05:50 | |
| *** delattec has quit IRC | 06:02 | |
| *** padkrish has quit IRC | 06:03 | |
| *** salv-orlando has joined #openstack-meeting-4 | 06:04 | |
| *** sdake has quit IRC | 06:07 | |
| *** cdelatte has joined #openstack-meeting-4 | 06:07 | |
| *** bharath_ has joined #openstack-meeting-4 | 06:09 | |
| *** chenshuai has joined #openstack-meeting-4 | 06:13 | |
| *** salv-orlando has quit IRC | 06:13 | |
| *** bharath_ has quit IRC | 06:14 | |
| *** med_ has joined #openstack-meeting-4 | 06:23 | |
| *** med_ is now known as Guest471 | 06:23 | |
| *** ramanjaneya_ has joined #openstack-meeting-4 | 06:30 | |
| *** ramanjaneya_ has quit IRC | 06:35 | |
| *** yamahata has joined #openstack-meeting-4 | 06:36 | |
| *** FallenPegasus has joined #openstack-meeting-4 | 06:40 | |
| *** markvoelker has joined #openstack-meeting-4 | 06:41 | |
| *** Guest471 has quit IRC | 06:44 | |
| *** padkrish has joined #openstack-meeting-4 | 06:44 | |
| *** coolsvap_ has joined #openstack-meeting-4 | 06:45 | |
| *** nkrinner has joined #openstack-meeting-4 | 06:45 | |
| *** coolsvap_ has quit IRC | 06:46 | |
| *** markvoelker has quit IRC | 06:46 | |
| *** ivar-lazzaro has quit IRC | 06:56 | |
| *** vivek-ebay has joined #openstack-meeting-4 | 06:58 | |
| *** vivek-ebay has quit IRC | 07:02 | |
| *** chenshuai has quit IRC | 07:05 | |
| *** chenshuai has joined #openstack-meeting-4 | 07:05 | |
| *** FallenPegasus has quit IRC | 07:10 | |
| *** salv-orlando has joined #openstack-meeting-4 | 07:11 | |
| *** zeih has joined #openstack-meeting-4 | 07:13 | |
| *** med_ has joined #openstack-meeting-4 | 07:15 | |
| *** med_ is now known as Guest61394 | 07:15 | |
| *** zeih has quit IRC | 07:15 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 07:17 | |
| *** britthou_ has quit IRC | 07:41 | |
| *** hogepodge has quit IRC | 07:41 | |
| *** csd has quit IRC | 07:41 | |
| *** bogdando has quit IRC | 07:41 | |
| *** ttx has quit IRC | 07:41 | |
| *** crinkle has quit IRC | 07:41 | |
| *** _fortis has quit IRC | 07:41 | |
| *** Kiall has quit IRC | 07:41 | |
| *** egon has quit IRC | 07:41 | |
| *** devananda has quit IRC | 07:41 | |
| *** hughsaunders has quit IRC | 07:42 | |
| *** britthou_ has joined #openstack-meeting-4 | 07:42 | |
| *** hogepodge has joined #openstack-meeting-4 | 07:42 | |
| *** csd has joined #openstack-meeting-4 | 07:42 | |
| *** bogdando has joined #openstack-meeting-4 | 07:42 | |
| *** ttx has joined #openstack-meeting-4 | 07:42 | |
| *** Kiall has joined #openstack-meeting-4 | 07:42 | |
| *** crinkle has joined #openstack-meeting-4 | 07:42 | |
| *** _fortis has joined #openstack-meeting-4 | 07:42 | |
| *** egon has joined #openstack-meeting-4 | 07:42 | |
| *** devananda has joined #openstack-meeting-4 | 07:42 | |
| *** britthouser has joined #openstack-meeting-4 | 07:43 | |
| *** _fortis has quit IRC | 07:44 | |
| *** crinkle_ has joined #openstack-meeting-4 | 07:44 | |
| *** csd has quit IRC | 07:45 | |
| *** britthou_ has quit IRC | 07:45 | |
| *** ttx has quit IRC | 07:45 | |
| *** egon has quit IRC | 07:45 | |
| *** devananda has quit IRC | 07:45 | |
| *** hughsaunders has joined #openstack-meeting-4 | 07:46 | |
| *** hogepodge has quit IRC | 07:46 | |
| *** bogdando has quit IRC | 07:46 | |
| *** crinkle has quit IRC | 07:46 | |
| *** Kiall has quit IRC | 07:46 | |
| *** devananda has joined #openstack-meeting-4 | 07:47 | |
| *** egon has joined #openstack-meeting-4 | 07:47 | |
| *** Kiall has joined #openstack-meeting-4 | 07:48 | |
| *** ttx has joined #openstack-meeting-4 | 07:50 | |
| *** ashtokolov has joined #openstack-meeting-4 | 07:52 | |
| *** csd has joined #openstack-meeting-4 | 07:52 | |
| *** ttx has quit IRC | 07:52 | |
| *** ttx has joined #openstack-meeting-4 | 07:52 | |
| *** ashtokolov has quit IRC | 07:56 | |
| *** bharath has joined #openstack-meeting-4 | 07:58 | |
| *** bogdando has joined #openstack-meeting-4 | 08:00 | |
| *** _fortis has joined #openstack-meeting-4 | 08:03 | |
| *** bharath has quit IRC | 08:03 | |
| *** ivar-lazzaro has quit IRC | 08:04 | |
| *** padkrish has quit IRC | 08:08 | |
| *** tfukushima has joined #openstack-meeting-4 | 08:12 | |
| *** MatthewL3 has quit IRC | 08:16 | |
| *** yamahata has quit IRC | 08:17 | |
| *** akwasnie has joined #openstack-meeting-4 | 08:19 | |
| *** jokke_ has quit IRC | 08:20 | |
| *** numan has joined #openstack-meeting-4 | 08:23 | |
| *** numan has quit IRC | 08:23 | |
| *** numan has joined #openstack-meeting-4 | 08:23 | |
| *** matrohon has joined #openstack-meeting-4 | 08:25 | |
| *** yamamoto has quit IRC | 08:27 | |
| *** yamamoto has joined #openstack-meeting-4 | 08:28 | |
| *** harshs has quit IRC | 08:34 | |
| *** crinkle_ is now known as crinkle | 08:41 | |
| *** markvoelker has joined #openstack-meeting-4 | 08:43 | |
| *** hogepodge has joined #openstack-meeting-4 | 08:43 | |
| *** markvoelker has quit IRC | 08:47 | |
| *** tfukushima has quit IRC | 09:13 | |
| *** rodrigods has quit IRC | 09:13 | |
| *** rodrigods has joined #openstack-meeting-4 | 09:13 | |
| *** tfukushima has joined #openstack-meeting-4 | 09:14 | |
| *** tfukushima has quit IRC | 09:14 | |
| *** tfukushima has joined #openstack-meeting-4 | 09:14 | |
| *** jmckind_ has joined #openstack-meeting-4 | 09:17 | |
| *** jmckind has quit IRC | 09:19 | |
| *** ashtokolov has joined #openstack-meeting-4 | 09:20 | |
| *** jokke_ has joined #openstack-meeting-4 | 09:30 | |
| *** ashtokolov has quit IRC | 09:33 | |
| *** Guest50430 has quit IRC | 09:35 | |
| *** Brian has joined #openstack-meeting-4 | 09:38 | |
| *** Brian is now known as Guest85053 | 09:38 | |
| *** yamamoto has quit IRC | 09:42 | |
| *** yamamoto has joined #openstack-meeting-4 | 09:44 | |
| *** bharath__ has joined #openstack-meeting-4 | 09:47 | |
| *** bharath__ has quit IRC | 09:51 | |
| *** ashtokolov has joined #openstack-meeting-4 | 09:55 | |
| *** ashtokolov has quit IRC | 09:59 | |
| *** ashtokolov has joined #openstack-meeting-4 | 09:59 | |
| *** chenshuai has quit IRC | 10:01 | |
| *** yamamoto has quit IRC | 10:21 | |
| *** yamamoto has joined #openstack-meeting-4 | 10:28 | |
| *** yamamoto has quit IRC | 10:28 | |
| *** yamamoto has joined #openstack-meeting-4 | 10:28 | |
| *** tfukushima has quit IRC | 10:43 | |
| *** markvoelker has joined #openstack-meeting-4 | 10:43 | |
| *** tfukushima has joined #openstack-meeting-4 | 10:44 | |
| *** tfukushima has quit IRC | 10:44 | |
| *** tfukushima has joined #openstack-meeting-4 | 10:45 | |
| *** yamamoto has quit IRC | 10:46 | |
| *** markvoelker has quit IRC | 10:48 | |
| *** xingchao has joined #openstack-meeting-4 | 10:54 | |
| *** tfukushima has quit IRC | 11:09 | |
| *** Guest85053 has quit IRC | 11:13 | |
| *** ashtokolov has quit IRC | 11:16 | |
| *** yamamoto has joined #openstack-meeting-4 | 11:34 | |
| *** bharath has joined #openstack-meeting-4 | 11:35 | |
| *** bharath has quit IRC | 11:40 | |
| *** markvoelker has joined #openstack-meeting-4 | 11:44 | |
| *** baoli has joined #openstack-meeting-4 | 11:46 | |
| *** markvoelker has quit IRC | 11:49 | |
| *** jpekkari has quit IRC | 11:49 | |
| *** markvoelker has joined #openstack-meeting-4 | 11:53 | |
| *** ashtokolov has joined #openstack-meeting-4 | 11:55 | |
| *** Brian has joined #openstack-meeting-4 | 11:58 | |
| *** Brian is now known as Guest41493 | 11:58 | |
| *** ashtokolov has quit IRC | 12:00 | |
| *** yamamoto has quit IRC | 12:07 | |
| *** tfukushima has joined #openstack-meeting-4 | 12:09 | |
| *** klamath has joined #openstack-meeting-4 | 12:09 | |
| *** evgenyf has joined #openstack-meeting-4 | 12:10 | |
| *** ashtokolov has joined #openstack-meeting-4 | 12:11 | |
| *** tfukushima has quit IRC | 12:14 | |
| *** xingchao has quit IRC | 12:19 | |
| *** xingchao has joined #openstack-meeting-4 | 12:20 | |
| *** xingchao has quit IRC | 12:25 | |
| *** Guest41493 has quit IRC | 12:27 | |
| *** tfukushima has joined #openstack-meeting-4 | 12:31 | |
| *** chenshuai has joined #openstack-meeting-4 | 12:31 | |
| *** ajmiller has quit IRC | 12:33 | |
| *** bnemec has joined #openstack-meeting-4 | 12:34 | |
| *** VW_ has joined #openstack-meeting-4 | 12:41 | |
| *** fawadkhaliq has quit IRC | 12:52 | |
| *** sdake has joined #openstack-meeting-4 | 12:53 | |
| *** sdake_ has joined #openstack-meeting-4 | 12:54 | |
| *** rfolco has joined #openstack-meeting-4 | 12:55 | |
| *** sdake has quit IRC | 12:57 | |
| *** VW_ has quit IRC | 12:58 | |
| *** VW_ has joined #openstack-meeting-4 | 12:58 | |
| *** galstrom_zzz is now known as galstrom | 13:01 | |
| *** baoli_ has joined #openstack-meeting-4 | 13:02 | |
| *** VW_ has quit IRC | 13:03 | |
| *** aventerav has joined #openstack-meeting-4 | 13:03 | |
| *** mestery has quit IRC | 13:03 | |
| *** ashtokolov has quit IRC | 13:03 | |
| *** ashtokolov has joined #openstack-meeting-4 | 13:04 | |
| *** ashtokolov has quit IRC | 13:04 | |
| *** baoli has quit IRC | 13:04 | |
| *** ashtokolov has joined #openstack-meeting-4 | 13:05 | |
| *** yamamoto has joined #openstack-meeting-4 | 13:07 | |
| *** ashtokolov has quit IRC | 13:09 | |
| *** galstrom is now known as galstrom_zzz | 13:11 | |
| *** mestery has joined #openstack-meeting-4 | 13:11 | |
| *** yamamoto has quit IRC | 13:12 | |
| *** fawadkhaliq has joined #openstack-meeting-4 | 13:13 | |
| *** ajmiller has joined #openstack-meeting-4 | 13:14 | |
| *** ashtokolov has joined #openstack-meeting-4 | 13:19 | |
| *** chenshuai has quit IRC | 13:21 | |
| *** tfukushima has quit IRC | 13:23 | |
| *** bharath has joined #openstack-meeting-4 | 13:24 | |
| *** tfukushima has joined #openstack-meeting-4 | 13:24 | |
| *** bharath has quit IRC | 13:28 | |
| *** singlethink has joined #openstack-meeting-4 | 13:31 | |
| *** VW_ has joined #openstack-meeting-4 | 13:36 | |
| *** nhairston has joined #openstack-meeting-4 | 13:38 | |
| *** nhairston has quit IRC | 13:39 | |
| *** singleth_ has joined #openstack-meeting-4 | 13:40 | |
| *** jckasper has quit IRC | 13:41 | |
| *** bpoulos has joined #openstack-meeting-4 | 13:42 | |
| *** singlethink has quit IRC | 13:43 | |
| *** ajmiller has quit IRC | 13:43 | |
| *** puranamr has quit IRC | 13:44 | |
| *** puranamr has joined #openstack-meeting-4 | 13:44 | |
| *** bunting has joined #openstack-meeting-4 | 13:45 | |
| *** jmckind_ has quit IRC | 13:49 | |
| *** dzamboni has joined #openstack-meeting-4 | 13:53 | |
| nikhil_k | Courtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting | 13:59 |
| flaper87 | o/ | 14:00 |
| *** dshakhray has joined #openstack-meeting-4 | 14:00 | |
| nikhil_k | #startmeeting glance | 14:01 |
| openstack | Meeting started Thu Aug 13 14:01:23 2015 UTC and is due to finish in 60 minutes. The chair is nikhil_k. 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: glance)" | 14:01 | |
| openstack | The meeting name has been set to 'glance' | 14:01 |
| nikhil_k | #topic agenda and roll call | 14:01 |
| *** openstack changes topic to "agenda and roll call (Meeting topic: glance)" | 14:01 | |
| nikhil_k | o/ | 14:01 |
| bunting | o/ | 14:01 |
| dshakhray | o/ | 14:01 |
| flaper87 | o/ | 14:01 |
| *** wokuma has joined #openstack-meeting-4 | 14:01 | |
| rosmaita | o/ | 14:01 |
| *** jmckind has joined #openstack-meeting-4 | 14:02 | |
| bpoulos | o/ | 14:02 |
| nikhil_k | As we are in the liberty-3 and trying to wrap things up with features and stability of Glance, guess we should give some time for that discussion. And we have a small agenda today | 14:02 |
| nikhil_k | #link https://etherpad.openstack.org/p/glance-team-meeting-agenda | 14:02 |
| *** ashtokolov has quit IRC | 14:02 | |
| *** ashtokolov has joined #openstack-meeting-4 | 14:03 | |
| nikhil_k | ativelkov: dshakhray : any one available for quick update on artifacts meeting notes? if anything important to be brought up now? | 14:03 |
| *** mclaren has joined #openstack-meeting-4 | 14:03 | |
| bunting | I think there wasnt many people at it, so there wasnt much of a meeting | 14:04 |
| ativelkov | nikhil_k: here, sorry for delay | 14:04 |
| ativelkov | The meeting on monday didn't get much attendance | 14:04 |
| *** evgenyf has quit IRC | 14:04 | |
| ativelkov | General update: we have a bunch of bugs related to artifacts list filtering | 14:05 |
| nikhil_k | Ah I see, can find 3 people on the list here: #link http://eavesdrop.openstack.org/meetings/glance_artifacts/2015/glance_artifacts.2015-08-10-14.03.html | 14:05 |
| * flaper87 wonders if meetbot can parse in-line tags | 14:05 | |
| ativelkov | nikhil_k: thanks for the link | 14:06 |
| ativelkov | So, that minutes contain a list of open bugs I was talking about | 14:06 |
| *** evgenyf has joined #openstack-meeting-4 | 14:06 | |
| ativelkov | I am working on these bugs, some are already fixed and are waiting for more functional tests to be written | 14:07 |
| ativelkov | mfedosin will be back from his PTO next week, will join us as well | 14:07 |
| *** ashtokolov has quit IRC | 14:07 | |
| nikhil_k | ativelkov: I think we need triage on at least one of them. you got reviewers working with you on them? | 14:07 |
| nikhil_k | cool, guess that answers it | 14:07 |
| ativelkov | Yeah, I expect dshakhray to help me with that as well | 14:08 |
| jokke_ | o/ sry for being late | 14:08 |
| nikhil_k | nice | 14:08 |
| *** krtaylor has joined #openstack-meeting-4 | 14:08 | |
| ativelkov | That's all from artifacts side | 14:09 |
| nikhil_k | So, I had to be offline/afk on Tuesday as well but guessing we skipped the drivers meeting as I see no logs | 14:09 |
| flaper87 | nikhil_k: yeah | 14:09 |
| nikhil_k | rosmaita: please correct me if I am wrong. I missed your ping and didn't get to it until late yday | 14:09 |
| nikhil_k | thanks flaper87 | 14:09 |
| rosmaita | nikhil_k: you are correct | 14:10 |
| nikhil_k | Thanks | 14:10 |
| *** sigmavirus24_awa is now known as sigmavirus24 | 14:10 | |
| nikhil_k | Moving on. | 14:10 |
| flaper87 | I guess we could do a quick sync after the meeting or just wait till next week's | 14:10 |
| nikhil_k | #topic changes still being accepted for V1? | 14:10 |
| *** openstack changes topic to "changes still being accepted for V1? (Meeting topic: glance)" | 14:10 | |
| nikhil_k | flaper87: sure, after this meeting sg | 14:10 |
| nikhil_k | bunting: guess, that's you? | 14:11 |
| *** kairat has joined #openstack-meeting-4 | 14:11 | |
| nikhil_k | #link https://review.openstack.org/#/c/211636/ | 14:11 |
| nikhil_k | #link https://review.openstack.org/#/c/203948 | 14:11 |
| bunting | Yeah, the patch i put up there has diffrent opinions on what should be allowed to change v1 | 14:11 |
| hemanthm | I've seen some of us giving -1 for v1 changes and others not | 14:11 |
| flaper87 | I was looking at those patches and I'm leaning towards generalizing the answer to that question as: We accept fixes for bugs with severity >=high | 14:11 |
| flaper87 | or prob medium? | 14:11 |
| sigmavirus24 | flaper87: I'd say >= high | 14:12 |
| rosmaita | sigmavirus24: +1 | 14:12 |
| sigmavirus24 | here's the thing, changing 200 to 403 doesn't seem acceptable | 14:12 |
| flaper87 | And I'm not saying just CVEs because I believe we can't do that until Nova moves to v2 | 14:12 |
| flaper87 | sigmavirus24: +1 | 14:12 |
| sigmavirus24 | fixing a 500 is fine | 14:12 |
| sigmavirus24 | Fixing a 500 probably shouldn't break other services | 14:12 |
| sigmavirus24 | Changing 200 to 403 seems more likely to have that affect | 14:12 |
| nikhil_k | I think there is a bigger problem here | 14:13 |
| jokke_ | that's my view to it as well ... leaving known condition leading to 500 is not really acceptable as long as Nova is still relying on it, but that 200 ->403 is something we have blocked similars before | 14:13 |
| nikhil_k | Nova stores the image ref in the immutable sys meta and if id changes then base ref for the snapshot can become useless | 14:13 |
| mclaren | I think there's kind of two factors: impact of the bug and the risk/scope of the fix | 14:13 |
| jokke_ | mclaren: ++ | 14:14 |
| nikhil_k | So, it might be a catch22 if Nova needs this but other clients are affected in a way that 403 becomes unacceptable | 14:14 |
| flaper87 | While I agree with mclaren, I'd like us to not answer this with: "We'll evaluate on each bug" | 14:14 |
| flaper87 | because that creates confusion and we'll get back to this discussion later | 14:14 |
| flaper87 | if the bug has a reasonable impact, then lets set the severity to high and fix it regardless the impact of the fix | 14:15 |
| nikhil_k | Agree that this becomes subjective to each bug. | 14:15 |
| jokke_ | should we make modified list based on the stable branch rules of acceptable changes to Images v1 API? | 14:15 |
| flaper87 | note that we're talking about master v1 here, not stable branches | 14:15 |
| sigmavirus24 | jokke_: yeah a good policy seems like something we need for v1 | 14:15 |
| sigmavirus24 | especially since v1 is no longer current, but "supported" | 14:15 |
| jokke_ | flaper87: yes, that's why I said modified, but we seem to agree pretty close to stable ruleset on the v1 api already | 14:16 |
| flaper87 | jokke_: yeah, my message was supposed to arrive before yours | 14:16 |
| flaper87 | damnyou | 14:16 |
| *** TravT has joined #openstack-meeting-4 | 14:16 | |
| mclaren | yeah, something akin to 'stable' seams reasonable | 14:16 |
| jokke_ | no backwards incompatibilities, no big risky changes, no new functionalities | 14:16 |
| flaper87 | and properly triaged bugs | 14:16 |
| flaper87 | with severity >= high | 14:16 |
| jokke_ | I'm not sure if severity high is really reasonable | 14:17 |
| jokke_ | it is after all unfortunately still in Liberty our main production api | 14:17 |
| nikhil_k | All this is subject to discussion per bug. Severity can be incresed or decreased as per requirement and they can be flexible per deployer. | 14:18 |
| flaper87 | nikhil_k: agreed but I'd like us to have a policy. Even stable backports are subject per patch/bug but we still have some guidelines | 14:18 |
| nikhil_k | But agree that having a set of guidelines can be helpful | 14:18 |
| flaper87 | damn it, I should've waited | 14:18 |
| flaper87 | :P | 14:18 |
| *** harshs has joined #openstack-meeting-4 | 14:18 | |
| nikhil_k | I guess we can take this review as a starting point for drafting one | 14:19 |
| sigmavirus24 | yes please | 14:19 |
| jokke_ | nikhil_k: that's kind of why I'd like to leave that severity req away from there. I don't want us triaging the bug severity just based on that some bug happens to affect us and we want the fix in. If it can be flexible, lets just leave it away from requirements | 14:19 |
| flaper87 | but I think severity could be an important factor | 14:20 |
| nikhil_k | #link https://etherpad.openstack.org/p/liberty-glance-v1-changes-policy | 14:20 |
| flaper87 | accepting a bug fix for a bug marked as low, as much as we don't want, could end up introducing a new bug | 14:20 |
| flaper87 | if we leave out wishlist/low/etc we reduce the chances to break v1 by fixing it | 14:21 |
| flaper87 | medium might be reasonable if we want it to be more flexible | 14:21 |
| jokke_ | flaper87: I'd like to see us finding the cycles to fix them mediums from the list first before we start worrying the low ones ;P | 14:21 |
| flaper87 | jokke_: we are not the only ones coding on Glance ;) | 14:22 |
| flaper87 | other contributors could pick bugs and work on them | 14:22 |
| flaper87 | if we leave low v1 bugs open, we're basically saying we're good with ppl fixing them | 14:22 |
| jokke_ | flaper87: I find hard time to prioritise them in my reviews and most probably it's really not low impact if someone has energy to bug me enough to review it :P | 14:23 |
| flaper87 | jokke_: and I have to disagree... *cough*patches give you free access to the summit*cough* | 14:24 |
| flaper87 | (just to mention one random case) | 14:24 |
| flaper87 | anyway... moving on | 14:24 |
| *** zeih has joined #openstack-meeting-4 | 14:25 | |
| nikhil_k | Okay, please add your coughs, oops I mean thoughts on the etherpad | 14:25 |
| flaper87 | rofl | 14:25 |
| nikhil_k | :) | 14:25 |
| nikhil_k | #topic Reviews, Bugs and Releases | 14:25 |
| *** openstack changes topic to "Reviews, Bugs and Releases (Meeting topic: glance)" | 14:25 | |
| flaper87 | may I go first? | 14:25 |
| flaper87 | I'll have to drop in a bit | 14:25 |
| flaper87 | erm, leave | 14:25 |
| flaper87 | you got it | 14:25 |
| nikhil_k | go ahead | 14:26 |
| flaper87 | thank you | 14:26 |
| jokke_ | flaper87: I think that's a good point, we perhaps should start clening the bugs out as well | 14:26 |
| *** thingee has joined #openstack-meeting-4 | 14:26 | |
| flaper87 | I just wanted to +1 what you said at the beginning of the meeting. lets focus on stabilizing and helping needed features to be completed. I'd like to bring to your attention the automatic task triggering spec: https://review.openstack.org/#/c/188388/ | 14:26 |
| flaper87 | rosmaita: dropped some interesting comments | 14:27 |
| rosmaita | ty | 14:27 |
| flaper87 | the reason I'm bringing it up again is because most the +1's on that spec, AFAICT, come from OPs | 14:27 |
| flaper87 | it's a needed feature and I believe we still have time | 14:27 |
| flaper87 | however, I'd love to hear your feedback on the impact and likelihood | 14:27 |
| flaper87 | that's it from me | 14:28 |
| flaper87 | and thanks :) | 14:28 |
| jokke_ | I think I need "Explain it to me like I'm five" run on that ... I have just really gard time to get grasp it | 14:28 |
| nikhil_k | oh yeah, I never added thoughts from irc to the review. thanks for the reminder. I think there has been some dilemma in terms of how this can impact the behavior of Glance. | 14:28 |
| jokke_ | "of it" | 14:28 |
| flaper87 | nikhil_k: yeah, I'm happy to talk more about it if that helps | 14:28 |
| nikhil_k | The main worry was we can establish the immutability clause but guess that is stil an open question on the feature | 14:28 |
| flaper87 | I don't think it'll change the way Glance operates but I might be missing something | 14:29 |
| nikhil_k | Otherwise, I think we may need something like this for singleton API effort | 14:29 |
| *** jpeeler has joined #openstack-meeting-4 | 14:29 | |
| *** jckasper has joined #openstack-meeting-4 | 14:29 | |
| rosmaita | flaper87: i'm not clear on what the workflow is for using the trigger tasks | 14:29 |
| flaper87 | I'll reply to rosmaita comments later today but before submitting a new version, I'd like to collect other folks' comments too | 14:29 |
| rosmaita | oops | 14:29 |
| flaper87 | :D | 14:30 |
| nikhil_k | :) | 14:30 |
| flaper87 | I don't want to take the meeting time but I'll explain all that soon | 14:30 |
| *** Bjoern_ has joined #openstack-meeting-4 | 14:30 | |
| *** Bjoern_ is now known as BjoernT | 14:30 | |
| flaper87 | at least what I've in mind, which could be completely wrong | 14:30 |
| flaper87 | :P | 14:30 |
| jokke_ | :D | 14:30 |
| rosmaita | can someone give me an objective assessment of the current state of tasks? | 14:30 |
| rosmaita | i am asking because | 14:30 |
| rosmaita | at the time of the DefCore stuff for Kilo | 14:30 |
| rosmaita | i was getting pushback from various non-glance people that tasks were not legitimate because they were "broken" | 14:31 |
| rosmaita | in unspecified ways | 14:31 |
| flaper87 | rosmaita: I think there was a HUGE misconception of what tasks are | 14:31 |
| flaper87 | and how they work | 14:31 |
| rosmaita | my concern is that the current tasks need to be solid before we extend the paradigm | 14:31 |
| flaper87 | and why we have them | 14:31 |
| flaper87 | and what Glance v2 is | 14:32 |
| flaper87 | and Glance | 14:32 |
| flaper87 | :P | 14:32 |
| rosmaita | no kidding! | 14:32 |
| mclaren | lol | 14:32 |
| flaper87 | I'm not kidding | 14:32 |
| rosmaita | i agreee | 14:32 |
| flaper87 | but it's still fun | 14:32 |
| flaper87 | :D | 14:32 |
| flaper87 | or sad | 14:32 |
| nikhil_k | I have been given the same response in a very specifically unspecific way - meaning the perspective is that Images API is immature. So, the decision on this spec is literally going to define the fate of tasks, glance and defcore | 14:32 |
| rosmaita | ok, i will file a bug that "tasks docs are missing" and get a patch up so we can clarify things | 14:33 |
| flaper87 | rosmaita: +1 | 14:33 |
| flaper87 | that sounds amazing | 14:33 |
| nikhil_k | the above line defcore == defcore take on "images" api | 14:33 |
| jokke_ | Well second hand info, but I'm bit worried that there is no way clearing tasks from the list, failed or finished. That alone leaves quite a flimsy feeling of them as whole even if it was just the one thing | 14:34 |
| hemanthm | jokke_: GB21 is working on that | 14:34 |
| rosmaita | jokke_: there's work being done on that as we speak! | 14:34 |
| flaper87 | yeah | 14:34 |
| hemanthm | https://review.openstack.org/#/c/209255/ | 14:34 |
| wokuma | I hate to bring up https://review.openstack.org/#/c/195820 again (like for the 4th time), but, this bug has become critical. | 14:35 |
| jokke_ | I know and it's great, that's just one of those things that might send bit harsh message out F.E. to defcore | 14:35 |
| wokuma | I think it should also be back ported to Kilo. | 14:35 |
| nikhil_k | ok, yes I think we need to give some time to wokuma | 14:35 |
| * flaper87 bows and thanks | 14:35 | |
| nikhil_k | I guess we can discussion more on this spec before drivers meeting next week to have few more comments. | 14:36 |
| nikhil_k | can have* | 14:36 |
| *** lakshmiS has joined #openstack-meeting-4 | 14:36 | |
| jokke_ | wokuma: I'd had approved that earlier today if the only other +2 wasn't from mclaren ;) | 14:36 |
| mclaren | anyone available to review wokuma's patch? | 14:36 |
| wokuma | The bug explains the issue, but, you just need to install it and make sure you can not enter duplicate namespaces, objects, properties, tags and resource-types. | 14:36 |
| nikhil_k | wokuma: the issue is prolly that it;s a scary big migration | 14:36 |
| wokuma | Yes. Sorry. | 14:37 |
| wokuma | It could/should be perhaps even bigger by one more constraint. | 14:37 |
| *** sbalukoff has quit IRC | 14:37 | |
| rosmaita | 549 lines of migration code, but +915 lines of tests, so kind of balances out | 14:38 |
| wokuma | I believe Eric Brown reported he had installed it and it works for him. | 14:38 |
| nikhil_k | what's the remnant constraint? | 14:39 |
| nikhil_k | and the upgrade of tags there kinda confused me | 14:39 |
| nikhil_k | if we have duplicate tags, it doesn't hurt unless it gives 500s | 14:39 |
| wokuma | a unique index on metadef_namespaces.display_name | 14:39 |
| mclaren | wokuma: this really mainly just touches the metadef models? | 14:40 |
| wokuma | Not sure if duplicate tags throws a 500 or not, will have to test that. | 14:40 |
| wokuma | yes. just the metadef_xxx tables. | 14:40 |
| mclaren | ie the chance of impacting 'images' is fairly non-existant? | 14:40 |
| sigmavirus24 | mclaren: right | 14:41 |
| nikhil_k | it is for non-shared deployers | 14:41 |
| wokuma | mclaren: I'm not touching any other tables than the metadef_xxx tables. | 14:41 |
| nikhil_k | non-shared = metadef separate from images | 14:41 |
| wokuma | mclaren: so i would say yes, pretty much non-existant. | 14:41 |
| mclaren | wokuma: ok, thanks. | 14:42 |
| wokuma | mclaren: np | 14:42 |
| mclaren | so anyone willing to review? even if it's just a 'I'm happy that this won't break images' kind of way? | 14:43 |
| wokuma | nikhil_k: should i add the metadef_namespaces.display_name unique index? | 14:44 |
| wokuma | It will wipe out all the +1 and +2's. | 14:44 |
| nikhil_k | thanks wokuma . I will try to allocate some time for this today if not sigmavirus24 has +Aed it that I don't mind being re-added EOB today | 14:44 |
| jokke_ | wokuma: if that's breaking something and needs to be fixed anyways, I'd say lets bite the bullet at once rather than you making another of these monsters for it :P | 14:45 |
| wokuma | jokke_: ok | 14:45 |
| nikhil_k | wokuma: does the index need to be added in the table properties? | 14:45 |
| *** tfukushima has quit IRC | 14:46 | |
| nikhil_k | btw, I think we need to give some more time for other reviews | 14:46 |
| wokuma | nikhil_k: The index could be added after. | 14:46 |
| nikhil_k | wokuma: if not as a part of the table args, may be it can be added later | 14:46 |
| nikhil_k | it should be fairly small operation | 14:46 |
| wokuma | I could add it in a subsequent script. | 14:47 |
| nikhil_k | thanks | 14:47 |
| nikhil_k | next are: | 14:47 |
| wokuma | np | 14:47 |
| nikhil_k | #link https://review.openstack.org/#/c/120866/ | 14:47 |
| nikhil_k | #link https://review.openstack.org/#/c/205632/ | 14:47 |
| *** zeih has quit IRC | 14:47 | |
| nikhil_k | rosmaita: hemanthm jcook : anyone of you added those? | 14:48 |
| hemanthm | those are bufferedreader spec and code | 14:48 |
| hemanthm | nikhil_k: I did | 14:48 |
| jcook | o/ | 14:48 |
| nikhil_k | thanks | 14:48 |
| *** tfukushima has joined #openstack-meeting-4 | 14:48 | |
| hemanthm | we chatted about this at the mid-cycle | 14:48 |
| *** radez_g0n3 is now known as radez | 14:48 | |
| nikhil_k | just needs reivews? | 14:49 |
| hemanthm | there was agreement that this looked like a decent way to fix retries | 14:49 |
| hemanthm | just wanted to get more input from folks | 14:49 |
| *** jmckind has quit IRC | 14:50 | |
| jcook | I think the patch looks good, just a minor nit by Erno and few questions myself | 14:50 |
| *** vivek-ebay has joined #openstack-meeting-4 | 14:50 | |
| hemanthm | Yeah, I'll fix the config option today. | 14:50 |
| nikhil_k | Thanks | 14:51 |
| mclaren | we talked about continuing to stream if the local cache is full, but that can be an add on... | 14:51 |
| hemanthm | mclaren: yeah, I added that to the spec. | 14:51 |
| mclaren | ah, nice | 14:52 |
| *** blahRus has joined #openstack-meeting-4 | 14:52 | |
| nikhil_k | Who added the next link to agenda? | 14:52 |
| mclaren | I added 1482371, it's not publically viewable yet | 14:52 |
| jokke_ | thanks hemanthm | 14:52 |
| nikhil_k | :) | 14:53 |
| *** ajmiller has joined #openstack-meeting-4 | 14:53 | |
| hemanthm | jokke_: thanks for the review :) | 14:53 |
| nikhil_k | mclaren: and you want to make it so? | 14:53 |
| mclaren | Just wondering what the next step is? | 14:53 |
| *** vikram_ has joined #openstack-meeting-4 | 14:53 | |
| mclaren | Do we wait for some security paperwork, or just push up the fix? | 14:54 |
| nikhil_k | mclaren: oops, I missed the proposed .patch. Will take a look and review. I think we need at least +2s before making a public review as a part of the workflow | 14:55 |
| jokke_ | mclaren: iiuc the paperwork needs to be ready and the patches will be pushed in at the moment of time specified in the paperwork | 14:55 |
| sigmavirus24 | mclaren: we shouldn't be talking about it in a public meeting then | 14:55 |
| sigmavirus24 | we shouldn't be referencing the bug number even if its not publicly viewable | 14:55 |
| *** carl_baldwin has joined #openstack-meeting-4 | 14:56 | |
| nikhil_k | agree | 14:56 |
| mclaren | ok, my bad | 14:56 |
| jokke_ | as part of the process the patch will be provided to vendors so they can have their versions fixed around the time it becomes public | 14:56 |
| nikhil_k | sigmavirus24: I think this needs to be public asap now. we also have a patch ready so should be good | 14:56 |
| sigmavirus24 | nikhil_k: are y'all coordinating with the VMT? | 14:56 |
| *** sdake_ is now known as sdake | 14:56 | |
| sigmavirus24 | If so, they'll be setting a public disclosure date | 14:56 |
| jokke_ | ^^ | 14:57 |
| nikhil_k | btw, whoever added subscribers to the bug -- please don't unless you get a approval from the openstack vulnerability team | 14:57 |
| sigmavirus24 | ^^ | 14:57 |
| sigmavirus24 | I think our team needs to seriously review the guidelines the VMT has set forth | 14:57 |
| hemanthm | nikhil_k: I added the first few | 14:57 |
| sigmavirus24 | No discussion in public logged channels | 14:57 |
| sigmavirus24 | Preferably no discussion on IRC | 14:57 |
| sigmavirus24 | Patch review on the bug report | 14:57 |
| nikhil_k | please that notes in mind for all the private bugs | 14:57 |
| nikhil_k | note* | 14:57 |
| sigmavirus24 | Only add trusted security cores | 14:57 |
| nikhil_k | ++ | 14:58 |
| nikhil_k | sigmavirus24: I will | 14:58 |
| *** puranamr has quit IRC | 14:58 | |
| nikhil_k | #action nikhil_k to talk to vmt about the bug | 14:58 |
| nikhil_k | jokke_: we have a couple mins left :) | 14:58 |
| *** puranamr has joined #openstack-meeting-4 | 14:58 | |
| wokuma | one last question, what about back port of https://review.openstack.org/#/c/195820 to Kilo. I feel it needs to be done. | 14:58 |
| sigmavirus24 | jokke_: ^? | 14:59 |
| jokke_ | yes so I'd like to get that already public one patched down | 14:59 |
| *** vivek-ebay has quit IRC | 14:59 | |
| jokke_ | we provided the functionality with Liberty-1 & -2 | 14:59 |
| *** zeih has joined #openstack-meeting-4 | 14:59 | |
| jokke_ | and that vulnerability was already disclosed last weeks meeting | 14:59 |
| nikhil_k | ok, lessons learnt from/by all. summary email coming on ml. | 15:00 |
| *** armax has joined #openstack-meeting-4 | 15:00 | |
| *** sjmc7 has joined #openstack-meeting-4 | 15:00 | |
| nikhil_k | we are out of time. | 15:01 |
| nikhil_k | Thanks all! | 15:01 |
| nikhil_k | #endmeeting | 15:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:01 | |
| openstack | Meeting ended Thu Aug 13 15:01:10 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-13-14.01.html | 15:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-13-14.01.txt | 15:01 |
| mclaren | thanks nikhil_k | 15:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-13-14.01.log.html | 15:01 |
| *** bpoulos has left #openstack-meeting-4 | 15:01 | |
| *** mclaren has quit IRC | 15:01 | |
| TravT | #startmeeting openstack search | 15:01 |
| nikhil_k | TravT: hi | 15:01 |
| openstack | Meeting started Thu Aug 13 15:01:32 2015 UTC and is due to finish in 60 minutes. The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| david-lyle | o/ | 15:01 |
| *** openstack changes topic to " (Meeting topic: openstack search)" | 15:01 | |
| openstack | The meeting name has been set to 'openstack_search' | 15:01 |
| sjmc7 | hi! | 15:01 |
| lakshmiS | o/ | 15:01 |
| *** kairat has left #openstack-meeting-4 | 15:01 | |
| TravT | o/ | 15:01 |
| nikhil_k | o/ | 15:01 |
| TravT | How is everybody this fine day | 15:02 |
| TravT | ? | 15:02 |
| *** bunting has left #openstack-meeting-4 | 15:02 | |
| sigmavirus24 | o/ | 15:02 |
| rosmaita | o/ | 15:02 |
| sjmc7 | enjoying the airshow practice | 15:02 |
| TravT | Sounds interesting | 15:02 |
| TravT | Okay, here's the meeting agenda. Please add any topics that you see fit. | 15:02 |
| TravT | https://etherpad.openstack.org/p/search-team-meeting-agenda | 15:02 |
| TravT | I don't have any general status updates today. | 15:03 |
| TravT | #topic Testing - python 3 | 15:03 |
| *** openstack changes topic to "Testing - python 3 (Meeting topic: openstack search)" | 15:03 | |
| TravT | This patch merged: Patch Merged (Thanks Sergey!): https://review.openstack.org/#/c/209939/ | 15:03 |
| sjmc7 | yeah, that's awesome | 15:03 |
| TravT | So, I went ahead and put up a patch for zuul gate jobs | 15:03 |
| TravT | to add py3 tests | 15:04 |
| TravT | Gate Jobs review up: https://review.openstack.org/#/c/212103/ | 15:04 |
| wokuma | o/ | 15:04 |
| TravT | if there is any reason we shouldn't do that, speak now or forever hold your peace. | 15:04 |
| *** LimorStotland_ has joined #openstack-meeting-4 | 15:04 | |
| *** sbalukoff has joined #openstack-meeting-4 | 15:04 | |
| lakshmiS | only reason we didnt do before was to keep it simple when we started searchlight code merge | 15:05 |
| nikhil_k | +1 to that | 15:05 |
| TravT | that's what I remember as well. | 15:05 |
| sjmc7 | yeah, go for it | 15:05 |
| TravT | and moving py 3.4 is a priority from the cross project meetings | 15:05 |
| *** yamahata has joined #openstack-meeting-4 | 15:05 | |
| *** LimorStotland_ has quit IRC | 15:05 | |
| nikhil_k | TravT: umm, for may be 1 year more :) | 15:06 |
| nikhil_k | but +1 to avoid regression! | 15:06 |
| TravT | that's like nothing in openstack time | 15:06 |
| TravT | :) | 15:06 |
| *** singlethink has joined #openstack-meeting-4 | 15:07 | |
| TravT | #topic Planning a liberty 3 prioritization discussion | 15:07 |
| *** openstack changes topic to "Planning a liberty 3 prioritization discussion (Meeting topic: openstack search)" | 15:07 | |
| nikhil_k | ha :) | 15:07 |
| TravT | As you might have seen, I put up a doodle poll | 15:07 |
| TravT | http://doodle.com/99kzigdbmed57g7s | 15:07 |
| *** singleth_ has quit IRC | 15:08 | |
| lakshmiS | seems like there's only one option left :) | 15:08 |
| TravT | Current responses point to tomorrow at 8 AM pactific | 15:08 |
| sigmavirus24 | hah | 15:08 |
| sigmavirus24 | works for me | 15:08 |
| rosmaita | works for me | 15:08 |
| sjmc7 | yep | 15:08 |
| TravT | So, next question is should we just do it in the IRC room or do it via a video call. | 15:09 |
| sigmavirus24 | IRC | 15:09 |
| sigmavirus24 | (is my vote) | 15:09 |
| sigmavirus24 | I'll probably be on a separate video call all day tomorrow | 15:09 |
| nikhil_k | either works for me | 15:10 |
| sjmc7 | irc has the advantage of being logged automatically | 15:10 |
| *** sankarshan is now known as sankarshan_away | 15:10 | |
| lakshmiS | sigmavirus24: all day video call sounds boring | 15:10 |
| sigmavirus24 | lakshmiS: it is | 15:10 |
| *** LimorStotland has joined #openstack-meeting-4 | 15:11 | |
| lakshmiS | irc+1 | 15:12 |
| *** bharath has joined #openstack-meeting-4 | 15:13 | |
| *** TravT has quit IRC | 15:14 | |
| *** TravT has joined #openstack-meeting-4 | 15:14 | |
| lakshmiS | i guess TravT doesnt want IRC | 15:14 |
| TravT | well, that was fun | 15:14 |
| TravT | what'd i miss? | 15:15 |
| sjmc7 | :D | 15:15 |
| nikhil_k | :D | 15:15 |
| TravT | sorry, i got disconnected | 15:15 |
| lakshmiS | fun was nothing happened | 15:15 |
| nikhil_k | TravT: we talked about your leaving irc just when we voted for irc meeting :P | 15:15 |
| nikhil_k | you* | 15:15 |
| TravT | Not sure if this sent or not. So re-pasting | 15:15 |
| TravT | either also works for me. i do like the rich-ness of verbal discussion, but i don't want to leave you out sigmavirus24, so let's go IRC | 15:16 |
| TravT | I don't think it'll take very long, TBH | 15:16 |
| sigmavirus24 | TravT: you can leave me out | 15:16 |
| sigmavirus24 | I leave myself out of things often | 15:16 |
| TravT | Sounds like everybody voted IRC | 15:16 |
| TravT | sigmavirus24: not going to let you off the hook that easy. | 15:16 |
| TravT | ;) | 15:16 |
| sigmavirus24 | damnit | 15:16 |
| *** LimorStotland has quit IRC | 15:16 | |
| nikhil_k | haha | 15:17 |
| TravT | okay, so tomorrow i'll put out a courtesy reminder | 15:17 |
| TravT | I'm adding a topic here | 15:17 |
| TravT | #topic discussing security bugs | 15:17 |
| *** openstack changes topic to "discussing security bugs (Meeting topic: openstack search)" | 15:18 | |
| *** bharath has quit IRC | 15:18 | |
| TravT | i was watching some of the discussion in the glance meeting just now | 15:18 |
| *** zeih has quit IRC | 15:18 | |
| TravT | sigmavirus24, you were talking about what we should and shouldn't discuss in meetings when it comes to vulnerabilities | 15:18 |
| TravT | would you or somebody else like to repeat that? | 15:19 |
| sigmavirus24 | certainly | 15:19 |
| sigmavirus24 | so | 15:19 |
| sigmavirus24 | talking about open bugs in meetings is fine | 15:19 |
| sigmavirus24 | if a bug has been privately reported though | 15:19 |
| sigmavirus24 | then we shouldn't | 15:19 |
| sigmavirus24 | A) Link to it | 15:19 |
| sigmavirus24 | B) Discuss the bug number | 15:19 |
| sigmavirus24 | C) Discuss the contents | 15:19 |
| sigmavirus24 | D) Discuss the patch | 15:20 |
| sigmavirus24 | E) Add random people to it unless they're vetted security cores | 15:20 |
| sigmavirus24 | Basically when something is reported, the only people on the bug should be teh VMT, the security liaison, the PTL | 15:20 |
| nikhil_k | F) Dates | 15:20 |
| sigmavirus24 | Right | 15:20 |
| sigmavirus24 | Patches are developed as attachments to the bug report | 15:21 |
| sigmavirus24 | Once a patch seems to fix the issue, a core or two are added to review it on the bug report | 15:21 |
| sigmavirus24 | Once they're satisfied, then a disclosure date is set, the stakeholders are emailed by a VMT member | 15:21 |
| sigmavirus24 | And then on teh disclosure date, the patch is proposed to gerrit the cores that were added auto-approve it | 15:21 |
| sigmavirus24 | And we have a successful security process | 15:21 |
| nikhil_k | \o/ | 15:22 |
| TravT | great synopsis | 15:22 |
| sigmavirus24 | There's a really good wiki page about all of this | 15:22 |
| sigmavirus24 | So that makes me wonder, do we have a security liaison? | 15:22 |
| sigmavirus24 | Or a security team? | 15:22 |
| TravT | now for reporting, there is a Information Type field. | 15:22 |
| *** padkrish has joined #openstack-meeting-4 | 15:22 | |
| david-lyle | TravT: and nikhil_k once we have a release, you will need a core-sec group | 15:22 |
| nikhil_k | david-lyle: good point | 15:22 |
| david-lyle | as sigmavirus24 was pointing out | 15:22 |
| *** xingchao has joined #openstack-meeting-4 | 15:23 | |
| nikhil_k | liaison(s) == core sec group | 15:23 |
| *** geoffarnold has joined #openstack-meeting-4 | 15:23 | |
| TravT | what if a security related bug is reported and is set as public? | 15:23 |
| david-lyle | then it stays open | 15:23 |
| sjmc7 | fix it quick! | 15:23 |
| nikhil_k | someone needs to take it up and fi it | 15:23 |
| david-lyle | it's already disclosed at that point | 15:23 |
| nikhil_k | usually the responsibility of the core sec group | 15:23 |
| david-lyle | no, undisclosing | 15:24 |
| nikhil_k | so they needs to be part of cores in general | 15:24 |
| nikhil_k | need* | 15:24 |
| nikhil_k | today is my un-grammar day | 15:24 |
| sigmavirus24 | So the other thing is, NEVER add the security group | 15:24 |
| TravT | everyday is my un-grammar day | 15:24 |
| * david-lyle doesn't limit to one day | 15:24 | |
| sigmavirus24 | the VMT and the OpenStack Security Group on Launchpad are two very different teams | 15:24 |
| sigmavirus24 | If you add the OSSG it's as good as publicly disclosing | 15:25 |
| lakshmiS | sigmavirus24: can you point to the wiki link | 15:25 |
| sigmavirus24 | lakshmiS: let me look | 15:25 |
| david-lyle | yes, when a bug is properly submitted the VMT is usually on it before the project tream | 15:25 |
| sigmavirus24 | #linkhttps://wiki.openstack.org/wiki/Vulnerability_Management | 15:26 |
| *** puranamr has quit IRC | 15:26 | |
| sigmavirus24 | #link https://wiki.openstack.org/wiki/Vulnerability_Management | 15:26 |
| sigmavirus24 | david-lyle: right | 15:26 |
| sigmavirus24 | That assumes the bug tracker is appropriately configured | 15:26 |
| nikhil_k | basically, as a practice you can add Tristan Cacqueray, ttx and (or) Jeremy Stanley | 15:26 |
| TravT | looks like it is moved here | 15:26 |
| sigmavirus24 | glance_store (was?) is not configured appropriately | 15:26 |
| TravT | #link https://security.openstack.org/vmt-process.html | 15:26 |
| sigmavirus24 | TravT: yeah, | 15:26 |
| sigmavirus24 | I think the links in the wiki (which comes up first on Google) are to that | 15:27 |
| TravT | Since we haven't done a release yet, I think we're okay. But we've already had a few security bugs reported as public. | 15:27 |
| TravT | But moving forward, we should follow that process. | 15:28 |
| nikhil_k | I think we are okay for now, given people would be deploying with a risk anyways | 15:28 |
| fungi | yep, please reach out to one of the vmt when you have time and we can clear it up | 15:28 |
| david-lyle | I think the suggestion is configure launchpad properly and have a team/individuals properly assigned by release time | 15:28 |
| sigmavirus24 | david-lyle: +1 | 15:29 |
| TravT | david-lyle, sounds good | 15:29 |
| sigmavirus24 | we should have this in place before searchlight 1.0.0 | 15:29 |
| sigmavirus24 | that way once we have 1.0.0, we don't need to scramble on the first report | 15:29 |
| *** vishwanathj has joined #openstack-meeting-4 | 15:29 | |
| TravT | so, i would nominate all cores on this meeting to be a part of sec-core group. | 15:29 |
| TravT | but how is that normally done? | 15:29 |
| sigmavirus24 | fungi: ? | 15:30 |
| nikhil_k | I think that's fair given the diverse set of focus/expertise | 15:30 |
| david-lyle | in Horizon it's a subset of core plus a non-core | 15:30 |
| sjmc7 | i'm very trustworthy | 15:30 |
| nikhil_k | basically if we see something in designate we need someone with domain k/w on that, if nova then so | 15:30 |
| * TravT never believes somebody who says that about themselves | 15:30 | |
| fungi | TravT: generally it depends on the size of your core reviewer group | 15:30 |
| fungi | if it's just a handful of people and they're familiar enough with the embargoed security patch proposal/review process such that they can successfully avoid accidentally leaking information prematurely, then that's fine | 15:31 |
| *** vivek-ebay has joined #openstack-meeting-4 | 15:32 | |
| nikhil_k | one idea: to start with we should ask 2 volunteer security liaisons. they can do the needed delegation once an intial pass is completed | 15:32 |
| fungi | for projects the size of, say, nova it doesn't make sense to have two dozen people automatically subscribed to a vulnerability report. might as well just be public at that point | 15:32 |
| fungi | but yeah, by default for repos in a governance deliverable tagged vulnerability:managed there is a vmt liaison (by default the ptl) and then some subset of the project-team's core reviewers identified with a projectname-coresec group in lp | 15:33 |
| sigmavirus24 | Also, I should point out that respected members of the larger sec community are turning against embargoed disclosures | 15:33 |
| *** dannywilson has joined #openstack-meeting-4 | 15:33 | |
| TravT | sigmavirus24, what does that mean? | 15:34 |
| sigmavirus24 | It doesn't affect us | 15:34 |
| fungi | for deliverables that are not officially vulnerability:managed you can mostly follow the same processes we publish, and we're happy to help you out in getting familiar with them | 15:34 |
| *** dshakhray has quit IRC | 15:34 | |
| sigmavirus24 | But, there would be no private disclosure of the bug in a private bug report | 15:34 |
| sigmavirus24 | Just food for thought is all | 15:34 |
| fungi | right, for any of you who attended my talk at oscon, i tried to underscore that our vmt is taking a pretty hard line on only embargoing things that really benefit from it (where the embargo effort is eclipsed by the potential impact of having the bug public without available fixes) | 15:35 |
| TravT | ok, well, i have about 6 people (including me) that I think are candidates for seccore group. | 15:35 |
| fungi | yeah, so you'd create a searchlight-coresec group in launchpad and invite them | 15:36 |
| TravT | Ok, that sounds like a good way to go about it. | 15:36 |
| TravT | nikhil_k, sigmavirus24, can we have a side discussion on this later, before I do that? | 15:37 |
| TravT | fungi: thanks for the info. | 15:38 |
| TravT | now that we've had that topic, let's move on. | 15:38 |
| TravT | #topic Bug review | 15:39 |
| *** openstack changes topic to "Bug review (Meeting topic: openstack search)" | 15:39 | |
| TravT | what helped prompt the above | 15:39 |
| TravT | is we have a security bug right now... | 15:39 |
| TravT | as it turns out, it is really just configuration. | 15:39 |
| sjmc7 | i'll test this today | 15:39 |
| TravT | so, documentation + devstack settings. | 15:39 |
| sjmc7 | yesterday exploded | 15:39 |
| TravT | Fix for Authentication not Happening: https://review.openstack.org/#/c/211047/ | 15:39 |
| TravT | thanks sjmc7 | 15:40 |
| TravT | if other could also take a look that'd be great. | 15:40 |
| *** nkrinner has quit IRC | 15:40 | |
| TravT | There is another related bug, which it appears sjmc7 has triaged | 15:42 |
| TravT | could use some reviews on his fix: | 15:42 |
| TravT | https://bugs.launchpad.net/searchlight/+bug/1484285 | 15:42 |
| openstack | Launchpad bug 1484285 in OpenStack Search (Searchlight) "Elasticsearch unable to parse query when using non-admin user" [Critical,In progress] - Assigned to Steve McLellan (sjmc7) | 15:42 |
| sigmavirus24 | TravT: no objection | 15:42 |
| TravT | lakshmiS: i had notified you of that one last night. | 15:42 |
| TravT | did you also look at it? | 15:43 |
| lakshmiS | yes i did, also looling through sjmc7 fix | 15:43 |
| lakshmiS | looking | 15:43 |
| TravT | ok, sounds good | 15:43 |
| lakshmiS | i am still not sure how it worked before. I will be spending more time on it | 15:44 |
| *** ashtokolov has joined #openstack-meeting-4 | 15:44 | |
| *** amotoki has joined #openstack-meeting-4 | 15:44 | |
| TravT | Fix for API root returns HTML instead of a list of versions: https://review.openstack.org/#/c/207864/ | 15:44 |
| sjmc7 | it worked as an admin user | 15:44 |
| TravT | the above ^ has several positive reviews. | 15:45 |
| sjmc7 | yeah, that one's good to go. even graham approved! | 15:45 |
| TravT | just needs another +2'er with +A | 15:45 |
| *** padkrish has quit IRC | 15:45 | |
| TravT | any other bugs specifically needing attention today? | 15:46 |
| TravT | if not, would like to move to next topic | 15:47 |
| sjmc7 | not from me, aside from the other reviews waiting | 15:47 |
| TravT | i had hoped to review more earlier this week, | 15:47 |
| TravT | but that authentication bug took most my attention | 15:47 |
| TravT | ok | 15:48 |
| TravT | #topic BP: Functional Tests https://blueprints.launchpad.net/searchlight/+spec/set-up-functional-tests | 15:48 |
| *** openstack changes topic to "BP: Functional Tests https://blueprints.launchpad.net/searchlight/+spec/set-up-functional-tests (Meeting topic: openstack search)" | 15:48 | |
| nikhil_k | lakshmiS: that patch fixes more then just HTML right? | 15:48 |
| nikhil_k | I mean, is intended to fix** | 15:48 |
| *** ashtokolov has quit IRC | 15:49 | |
| TravT | #undo | 15:49 |
| openstack | Removing item from minutes: <ircmeeting.items.Topic object at 0xa0a5d10> | 15:49 |
| lakshmiS | prevent HTML output and provide version info similar to glance | 15:49 |
| nikhil_k | lakshmiS: and the correct version listing in the discovery api response | 15:50 |
| lakshmiS | nikhil_k: yes and it only has one api version for searchlight which is v1 | 15:50 |
| nikhil_k | may be a updated commit message (using the webui) with APIImpact flag for historical purposed? | 15:50 |
| nikhil_k | purposes* | 15:50 |
| lakshmiS | nikhil_k: sure | 15:51 |
| nikhil_k | I can comment that on the patch | 15:51 |
| nikhil_k | thanks lakshmiS | 15:51 |
| sjmc7 | https://review.openstack.org/#/c/207672/ should also have an APIImpact flag in that case | 15:51 |
| sjmc7 | since it changes the /search/plugins response | 15:51 |
| nikhil_k | umm, yeah.. | 15:52 |
| TravT | sure, go ahead and add it. | 15:52 |
| TravT | #topic https://blueprints.launchpad.net/searchlight/+spec/set-up-functional-tests | 15:52 |
| *** openstack changes topic to "https://blueprints.launchpad.net/searchlight/+spec/set-up-functional-tests (Meeting topic: openstack search)" | 15:52 | |
| nikhil_k | we can do a quick grep at the end of the cycle and say this is how the API has evolved | 15:52 |
| nikhil_k | thanks TravT | 15:52 |
| *** puranamr has joined #openstack-meeting-4 | 15:53 | |
| lakshmiS | so ceilometer assumes JDK and ES is already installed and there is no other known solution | 15:53 |
| lakshmiS | https://github.com/openstack/ceilometer/blob/6f6f655766a1ab4a66e00ea7f95dabb56a654e8a/setup-test-env-es.sh | 15:53 |
| lakshmiS | for functional tests | 15:53 |
| sjmc7 | that's what i did too. because it's hard :) | 15:53 |
| lakshmiS | thats the same approach i am following unless anybody has something to say! | 15:53 |
| sjmc7 | i still think there's a lot of value in being able to run them locally even if integrating in CI is hard | 15:53 |
| *** tfukushima has quit IRC | 15:54 | |
| *** sdake_ has joined #openstack-meeting-4 | 15:54 | |
| TravT | I agree | 15:54 |
| nikhil_k | I see, it might be the only good solution for a bit | 15:54 |
| *** sbalukoff has quit IRC | 15:54 | |
| *** tfukushima has joined #openstack-meeting-4 | 15:55 | |
| lakshmiS | i will put the patch up for review then! | 15:55 |
| TravT | I am not a fan of creating mock back-ends for integration tests | 15:55 |
| *** singleth_ has joined #openstack-meeting-4 | 15:55 | |
| nikhil_k | lakshmiS: I would like to work with you or on the review. there are a few things like avoiding sys variables that we should do. it broke glance many a times | 15:56 |
| lakshmiS | nikhil_k: definetly | 15:56 |
| *** odyssey4me has joined #openstack-meeting-4 | 15:56 | |
| TravT | because above might be mis-interpretted by others following along at home, just want to be clear that i feel that testing elasticsearch integration should be against real elasticsearch. | 15:56 |
| sjmc7 | yes | 15:57 |
| sjmc7 | i agree | 15:57 |
| TravT | lakshmiS, that's great you have a patch ready | 15:57 |
| TravT | ok, we are almost out of time. | 15:57 |
| TravT | as usual, review what you can. | 15:58 |
| *** sdake has quit IRC | 15:58 | |
| *** singlethink has quit IRC | 15:58 | |
| nikhil_k | sjmc7: I think the nova plugin is failling silly | 15:58 |
| TravT | Tomorrow we'll have a BP prioritization review in the room | 15:58 |
| nikhil_k | https://review.openstack.org/#/c/198852/ | 15:58 |
| lakshmiS | which room? searchlight or meeting room? | 15:58 |
| *** evrardjp has joined #openstack-meeting-4 | 15:58 | |
| nikhil_k | sjmc7: may be a set() on the test should help | 15:58 |
| TravT | #openstack-searchlight | 15:58 |
| TravT | I'll send a courtesy reminder out | 15:59 |
| nikhil_k | because, currently it's looking at the order of values in resp | 15:59 |
| *** mattt has joined #openstack-meeting-4 | 15:59 | |
| wokuma | TravT, lakshmiS - don't forget the i18n meeting. | 16:00 |
| *** padkrish has joined #openstack-meeting-4 | 16:00 | |
| TravT | thanks everybody | 16:00 |
| lakshmiS | wokuma: thx for the reminder | 16:00 |
| *** stevelle has joined #openstack-meeting-4 | 16:00 | |
| TravT | #endmeeting | 16:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:00 | |
| openstack | Meeting ended Thu Aug 13 16:00:18 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-13-15.01.html | 16:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-13-15.01.txt | 16:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-13-15.01.log.html | 16:00 |
| *** svg has joined #openstack-meeting-4 | 16:00 | |
| *** ashtokolov has joined #openstack-meeting-4 | 16:00 | |
| odyssey4me | #startmeeting OpenStack Ansible Meeting | 16:00 |
| openstack | Meeting started Thu Aug 13 16:00:55 2015 UTC and is due to finish in 60 minutes. The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| *** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)" | 16:00 | |
| openstack | The meeting name has been set to 'openstack_ansible_meeting' | 16:01 |
| *** lakshmiS has left #openstack-meeting-4 | 16:01 | |
| *** TravT has left #openstack-meeting-4 | 16:01 | |
| dstanek | o/ | 16:01 |
| svg | o/ | 16:01 |
| sigmavirus24 | o/ | 16:01 |
| odyssey4me | #topic Agenda & rollcall | 16:01 |
| andymccr | o/ | 16:01 |
| *** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)" | 16:01 | |
| *** wokuma has left #openstack-meeting-4 | 16:01 | |
| odyssey4me | #link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting | 16:01 |
| *** sjmc7 has left #openstack-meeting-4 | 16:01 | |
| evrardjp | \o/ | 16:01 |
| odyssey4me | howdy all :) | 16:02 |
| stevelle | o/ | 16:02 |
| *** adityavajjha has joined #openstack-meeting-4 | 16:03 | |
| serverascode | o/ | 16:04 |
| BjoernT | Morning | 16:04 |
| palendae | hi | 16:04 |
| *** KLevenstein has joined #openstack-meeting-4 | 16:04 | |
| odyssey4me | #topic Review action items from last week | 16:05 |
| *** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)" | 16:05 | |
| odyssey4me | ACTION: sigmavirus24 and cloudnull to put together a POC for pip and epoch's | 16:05 |
| *** alextricity has joined #openstack-meeting-4 | 16:05 | |
| sigmavirus24 | ugh | 16:05 |
| sigmavirus24 | stuck in upgrade hell right now | 16:05 |
| sigmavirus24 | haven't had time for this | 16:05 |
| odyssey4me | sigmavirus24 I take it that will need to carry considering that cloudnull is still on leave? | 16:05 |
| *** prometheanfire has joined #openstack-meeting-4 | 16:05 | |
| odyssey4me | alright | 16:05 |
| sigmavirus24 | yeah that too | 16:05 |
| odyssey4me | #action sigmavirus24 and cloudnull to put together a POC for pip and epoch's | 16:05 |
| sigmavirus24 | The idea is on the ML | 16:05 |
| odyssey4me | ACTION: odyssey4me to release 11.1.0 on 7 Aug 2015, any blueprints not yet merged to be postponed to 11.2.0 | 16:06 |
| odyssey4me | so it was released on 10 Aug instead, but it was released with all the blueprints completed :) | 16:06 |
| odyssey4me | well done everyone for getting that done, even with our busy days! | 16:06 |
| odyssey4me | #link https://launchpad.net/openstack-ansible/kilo/11.1.0 | 16:07 |
| odyssey4me | there was a lot of work that went into there | 16:07 |
| odyssey4me | ACTION: odyssey4me to set 11.2.0 release date to the (tentative) date of 4 Sep | 16:07 |
| sigmavirus24 | Good job everyone | 16:08 |
| sigmavirus24 | :round of applause: | 16:08 |
| odyssey4me | I've set the date for 11.2.0 as 11 Sep to ensure that we have enough time to get two hotfix patches into 11.1.0, and another week for getting the 11.2.0 feature patches merged in. | 16:08 |
| odyssey4me | https://launchpad.net/openstack-ansible/+milestone/11.2.0 | 16:08 |
| odyssey4me | #link https://launchpad.net/openstack-ansible/+milestone/11.2.0 | 16:09 |
| svg | from me a big thanks on helping meon the Ceph patch | 16:09 |
| odyssey4me | thank you svg for doing that work and being patient with us in the reviews and testing | 16:09 |
| svg | I thought you guys were the ones being patient :) | 16:10 |
| odyssey4me | if any bugs are raised against that work, please target them to 11.2.0 for kilo so that we can track which ones need ot be backported | 16:10 |
| svg | ack | 16:10 |
| odyssey4me | alternatively patches can also be registered against the blueprint considering that it's still not released yet | 16:10 |
| *** harshs has quit IRC | 16:11 | |
| evrardjp | not master? | 16:11 |
| evrardjp | ok my bad | 16:11 |
| odyssey4me | evrardjp patches get initially added to master, but they won't be backported to kilo until the week before 11.2.0 | 16:11 |
| odyssey4me | so ceph patches into master are welcome | 16:11 |
| odyssey4me | :) | 16:11 |
| odyssey4me | is everyone happy with the dates for the milestones? | 16:12 |
| odyssey4me | alright, moving on | 16:13 |
| odyssey4me | #topic Blueprints | 16:13 |
| *** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)" | 16:13 | |
| odyssey4me | #link https://blueprints.launchpad.net/openstack-ansible | 16:13 |
| *** matrohon has quit IRC | 16:14 | |
| *** padkrish has quit IRC | 16:14 | |
| hughsaunders | <-- late | 16:14 |
| odyssey4me | I've added a liberty blueprint. For anything you see that may need follow up in liberty - whether it be an upstream bug, or perhaps settings that need changing due to deprecation - please associate them with that blueprint. | 16:14 |
| *** bknudson has joined #openstack-meeting-4 | 16:15 | |
| odyssey4me | I'd like to propose adding the upstream liberty-related milestones to trunk so that we can target specific things and also have an easy reference for the dates to help with planning. | 16:15 |
| odyssey4me | Are there any objections to that? | 16:16 |
| palendae | Nope | 16:16 |
| palendae | We need more structure around our Liberty stuff | 16:16 |
| palendae | Even though forward progress on that has been slow | 16:16 |
| odyssey4me | #link https://wiki.openstack.org/wiki/Liberty_Release_Schedule | 16:16 |
| odyssey4me | all we have left is liberty-3, then liberty-release | 16:17 |
| palendae | I have a feeling we'll miss liberty-release | 16:17 |
| palendae | At least any configuration changes | 16:17 |
| *** evgenyf has quit IRC | 16:17 | |
| odyssey4me | palendae I think it'll be easier than you think. :) | 16:17 |
| palendae | We'll see. I won't consider it working til we have working upgrades | 16:17 |
| hughsaunders | now you're moving the goalposts | 16:18 |
| odyssey4me | we will definitely have a functional release on the release day - we've been working through kinks as we've updated our sha's and have been fixing upstream bugs as we discover them | 16:18 |
| *** Brian has joined #openstack-meeting-4 | 16:18 | |
| palendae | hughsaunders: Nope, not at all | 16:19 |
| odyssey4me | palendae the upgrades will probably be a lot easier as we don't have as many structural changes as juno->kilo | 16:19 |
| *** Brian is now known as Guest96363 | 16:19 | |
| palendae | hughsaunders: Function upgrades are more important than greenfield deployments IMO | 16:19 |
| palendae | odyssey4me: Hopefully :) | 16:19 |
| odyssey4me | I'd like to ask everyone to take the time in the next week to look through the registered blueprints and to self assign where possible, also setting a goal milestone | 16:20 |
| odyssey4me | it'd also be a good idea to get a starting review uploaded so that the design discussions can happen | 16:20 |
| odyssey4me | palendae has a good one up already | 16:21 |
| odyssey4me | #link https://review.openstack.org/207713 | 16:21 |
| odyssey4me | personally I think this one is fine, and I believe it's important for adding RHEL support later | 16:22 |
| odyssey4me | #link https://review.openstack.org/203708 | 16:22 |
| odyssey4me | also if we could get some reviews on this patch to the specs repo so that we don't get so many merge conflicts, that'd be grand: https://review.openstack.org/208440 | 16:22 |
| *** Guest96363 has quit IRC | 16:23 | |
| odyssey4me | #action odyssey4me to add upstream liberty milestones to the trunk series | 16:23 |
| *** FallenPegasus has joined #openstack-meeting-4 | 16:23 | |
| odyssey4me | #action all to review blueprints, self-assign and target, then submit and review blueprints | 16:24 |
| odyssey4me | I'd like to suggest that we spend most of next week's meeting discussing our roadmap and breaking down some of the steps into easy pieces to chew on. | 16:24 |
| palendae | Sounds reasonable | 16:26 |
| *** padkrish has joined #openstack-meeting-4 | 16:26 | |
| sigmavirus24 | +1 | 16:26 |
| odyssey4me | part of the thought we need to put into it is how we can best serve our downstream consumers | 16:26 |
| odyssey4me | We have different types of consumers currently - RPC is an example of a consumer which embeds openstack-ansible wholesale into something bigger. | 16:27 |
| odyssey4me | Compass is a relatively new project building a UI around deployment, and is looking to consume our playbooks and roles. | 16:28 |
| odyssey4me | We also have deployers consuming the playbooks & roles as they are, and perhaps doing their own bits around or over the top. | 16:28 |
| odyssey4me | I'd like us to consider as part of our roadmap making the roles individually consumable, testable and reusable outside of our reference builds. | 16:29 |
| evrardjp | Do we have Compass contributors telling their opinion? | 16:30 |
| evrardjp | that could be nice | 16:30 |
| odyssey4me | It'll make it easier for SME's to get involved in adding functionality without having to get too involved in the entire stack. | 16:30 |
| evrardjp | (or even commiting/improving the product) | 16:30 |
| odyssey4me | #link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071892.html | 16:31 |
| odyssey4me | ^Compass call for contributors | 16:31 |
| *** Sukhdev has joined #openstack-meeting-4 | 16:32 | |
| odyssey4me | I've been having conversations with various parties to get feedback about what holds them back from getting involved. | 16:32 |
| odyssey4me | The feedback has been, so far: | 16:32 |
| odyssey4me | 1 - it'd be great if it was easier to get a dev/test environment going | 16:33 |
| svg | so they ask to make openstack easier? ⸮ | 16:34 |
| odyssey4me | 2 - there is no support for implementing on the platform I use (usually CentOS) | 16:34 |
| evrardjp | ok | 16:35 |
| hughsaunders | 1) curl | bash | 16:35 |
| odyssey4me | svg not openstack, but a dev/test environment to understand how to do operator things (add nodes, replicate a bug, etc) and also how to do dev things (add a role, feature or functionality to the stack) | 16:35 |
| stevelle | hughsaunders: I was perhaps reading 1 differently: as a multi-node environment which is not that simple. | 16:36 |
| hughsaunders | stevelle: fair | 16:36 |
| odyssey4me | stevelle yes, an AIO is relatively easy in a VM or Cloud - but not everyone has a VM environment or Cloud | 16:36 |
| odyssey4me | #link https://blueprints.launchpad.net/openstack-ansible/+spec/deploy-with-vagrant | 16:36 |
| palendae | So i'm not sure how we fix that | 16:36 |
| palendae | If they don't have access to VMs | 16:36 |
| odyssey4me | ^ has been added and I'm liaising with the guy to add his Vagrant conf and some docs into the repo | 16:37 |
| andymccr | maybe we make an installable iso, Apsu could you get working on that? | 16:37 |
| odyssey4me | this opens another door | 16:37 |
| palendae | Or I'm misunderstanding what you're saying, because you just linked to deploying with vagrant after you said not everyone has access to VMs :) | 16:37 |
| Apsu | andymccr: Right on it | 16:37 |
| odyssey4me | we could also do better at docs | 16:37 |
| andymccr | it could have like questions that stores vars like your public address range etc. | 16:38 |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 16:38 | |
| evrardjp | Compass handles the PXE booting so I guess it won't be hard to add osad on top of it when the management network is running | 16:38 |
| *** xingchao has quit IRC | 16:38 | |
| odyssey4me | anyway - part of getting more host OS platforms supported are these blueprints: | 16:38 |
| evrardjp | andymccr: this wizard could be done with or without the iso | 16:38 |
| odyssey4me | #link https://blueprints.launchpad.net/openstack-ansible/+spec/mariadb-upgrade-to-v10 | 16:38 |
| evrardjp | but we are getting far from original topic, right? | 16:38 |
| odyssey4me | #link https://blueprints.launchpad.net/openstack-ansible/+spec/add-support-for-systemd | 16:39 |
| *** ivar-lazzaro has quit IRC | 16:40 | |
| odyssey4me | evrardjp right, the point is not for us to change what we do which is deploy on existing hosts - the point is to make it easier for evaluators and developers to get to grips with how what we've built works and how they can contribute | 16:40 |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 16:41 | |
| *** sdake has joined #openstack-meeting-4 | 16:42 | |
| odyssey4me | most of the time when people raise their issues I find that they just don't know that we already do things that they thought we didn't | 16:42 |
| *** meteorfox has joined #openstack-meeting-4 | 16:42 | |
| odyssey4me | so I think we could also do better at sharing our successes and engaging with SME's in the various projects to assist when we're working on things that they could help with | 16:42 |
| stevelle | how much of the friction is from the particular way that we use Ansible? | 16:42 |
| stevelle | thinking of vars specifically | 16:43 |
| odyssey4me | stevelle the 3rd objection that they have is to do with the opinionation - we have a pretty rigid way of deploying | 16:43 |
| stevelle | though I know questions about inventory exist too | 16:43 |
| *** padkrish has quit IRC | 16:43 | |
| odyssey4me | stevelle I think that's more of an issue for us than others at this stage. No-one's mentioned that just yet. | 16:44 |
| odyssey4me | #link https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CCEQFjAAahUKEwiwivvewKbHAhUGF9sKHdx-B9U&url=https%3A%2F%2Fgithub.com%2Fopenstack-ansible%2Fopenstack-ansible&ei=YsnMVbDRDIau7Abc_Z2oDQ&usg=AFQjCNEdKMLeFRncUo1F0xilQ5svqPrfCA&sig2=trguuB1XtNTgs3jHgn3LTg&bvm=bv.99804247,d.ZGU | 16:44 |
| odyssey4me | #action odyssey4me to slap himself with a wet fish | 16:44 |
| odyssey4me | #link https://github.com/openstack-ansible/openstack-ansible | 16:44 |
| odyssey4me | ^ I've engaged with the guys who worked on these playbooks and roles. | 16:45 |
| palendae | odyssey4me: I've seen several questions from people about how the dynamic_inventory.py script works | 16:45 |
| *** KunalGandhi has joined #openstack-meeting-4 | 16:45 | |
| odyssey4me | They're currently on icehouse and have committed to evaluate the stack we have and provide feedback. It's early days though. | 16:45 |
| *** sdake_ has quit IRC | 16:45 | |
| evrardjp | I think variables handling could prevent adoption: I was afraid myself at first | 16:46 |
| odyssey4me | palendae agreed, those questions come from those who've actually deployed and tried doing hard things :) | 16:46 |
| odyssey4me | palendae has suggested that he'd like to write up some reference documentation about it all | 16:47 |
| palendae | Yep, I have some things sitting on my hard drive to get pushed up | 16:47 |
| *** jckasper has quit IRC | 16:47 | |
| odyssey4me | I'm of the opinion that we can break down a lot of barriers to adoption by making the roles independant units, consumable on their own. | 16:47 |
| palendae | Sure | 16:47 |
| odyssey4me | It will allow those interested to tackle broader OS support in a smaller unit. | 16:48 |
| evrardjp | I agree | 16:48 |
| odyssey4me | It will also allow people to deploy in whatever way they choose, instead of the way we've chosen. | 16:48 |
| odyssey4me | It will also make it easier to get to grips with the pieces that people are interested in, instead of the monolithic large pile of code we have now. | 16:49 |
| palendae | That's gonna be a very long term road map, fwiw | 16:49 |
| *** jckasper has joined #openstack-meeting-4 | 16:49 | |
| odyssey4me | well, maybe - but maybe not | 16:49 |
| palendae | I think Keystone's a great place to start, but this is not going to be all done by 12 | 16:49 |
| palendae | Some of our roles are very intertwined | 16:49 |
| odyssey4me | if we split the roles into their own repositories - which will be in the openstack namespace, then we use submodule references in os-ansible-deployment in order to handle a full cycle of deprecation, then it may be achievable | 16:50 |
| *** padkrish has joined #openstack-meeting-4 | 16:50 | |
| palendae | That's the high level, yeah.. | 16:50 |
| *** Mohankumar has joined #openstack-meeting-4 | 16:50 | |
| *** mitchjameson has joined #openstack-meeting-4 | 16:50 | |
| odyssey4me | during the M cycle we can work on making them more individually functional and individually tested | 16:50 |
| palendae | Though submodules everywhere...we were down that road with the chef stuff, no? | 16:51 |
| odyssey4me | yeah, not ideal - but after the one cycle we remove them and have them all as ansible galaxy roles | 16:51 |
| palendae | Ok, I think it's a reasonable high level plan. I just think the details may bog it down | 16:52 |
| odyssey4me | or shall we say the submodules stay in the branches they need to stay in, but in master we switch | 16:52 |
| odyssey4me | Anyway - let's put some thought into the future this week coming, and try to get our thoughts into specs. We can make the blueprints dependant on each other to help understand what follows what. | 16:53 |
| odyssey4me | Our time is just about up, so I'd like to open the floor for comments, questions, suggestions and general banter... | 16:54 |
| * odyssey4me slaps himself with a wet fish | 16:54 | |
| * odyssey4me ticks 'action complete' checkbox | 16:54 | |
| meteorfox | I have the Rally ansible role, ready to go, https://github.com/meteorfox/ansible-rally | 16:54 |
| meteorfox | well, you can say is the mvp version | 16:55 |
| odyssey4me | yep :) didn't realise you were here meteorfox | 16:55 |
| stevelle | it could use a bit of love in the readme :) | 16:55 |
| *** VW_ has quit IRC | 16:55 | |
| *** abhisriatt has joined #openstack-meeting-4 | 16:55 | |
| odyssey4me | I forgot about that - I'd like to submit the review to register our first role in the openstack namespace. | 16:56 |
| odyssey4me | We need to figure out a naming convention. | 16:56 |
| *** VW_ has joined #openstack-meeting-4 | 16:56 | |
| meteorfox | yes, I'm aware of that, and there a few directories which are 'empty' and could be deleted | 16:56 |
| odyssey4me | I was thinking something along the lines of 'openstack-ansible-<role name>' ? | 16:56 |
| odyssey4me | once we've registered it, meteorfox can submit his code as a first review and we can collaborate on improving it | 16:57 |
| odyssey4me | thoughts? | 16:57 |
| *** max_klyus has joined #openstack-meeting-4 | 16:57 | |
| meteorfox | I'm fine with the name convention | 16:57 |
| *** LouisF has joined #openstack-meeting-4 | 16:58 | |
| odyssey4me | palendae sigmavirus24 andymccr hughsaunders mattt ? | 16:58 |
| sigmavirus24 | yeah that works for me | 16:58 |
| palendae | you're submitting that for Liberty? Prior to the blueprint being finalized? | 16:58 |
| *** johnsom has joined #openstack-meeting-4 | 16:59 | |
| andymccr | so it would be the first role in its own repo? | 16:59 |
| *** VW__ has joined #openstack-meeting-4 | 16:59 | |
| *** FallenPegasus has quit IRC | 16:59 | |
| andymccr | with the expectation others follow the same pattern (are moved to that pattern) | 16:59 |
| odyssey4me | andymccr yep | 17:00 |
| odyssey4me | we're out of time - move to #openstack-ansible | 17:00 |
| odyssey4me | #endmeeting | 17:00 |
| *** VW_ has quit IRC | 17:00 | |
| andymccr | well if the bigger plan is to move to that model then sure it makes sense | 17:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:00 | |
| openstack | Meeting ended Thu Aug 13 17:00:17 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-13-16.00.html | 17:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-13-16.00.txt | 17:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-13-16.00.log.html | 17:00 |
| *** jay_s_b has joined #openstack-meeting-4 | 17:01 | |
| *** evrardjp has left #openstack-meeting-4 | 17:01 | |
| *** bharath has joined #openstack-meeting-4 | 17:02 | |
| LouisF | #startmeeting service-chaining | 17:02 |
| openstack | Meeting started Thu Aug 13 17:02:38 2015 UTC and is due to finish in 60 minutes. The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:02 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:02 |
| *** Brian__ has joined #openstack-meeting-4 | 17:02 | |
| *** openstack changes topic to " (Meeting topic: service-chaining)" | 17:02 | |
| openstack | The meeting name has been set to 'service_chaining' | 17:02 |
| *** george__ has joined #openstack-meeting-4 | 17:02 | |
| johnsom | o/ | 17:02 |
| LouisF | hi all | 17:02 |
| george__ | hi | 17:03 |
| *** akwasnie has quit IRC | 17:03 | |
| Brian__ | hi all | 17:03 |
| max_klyus | hi there | 17:03 |
| Mohankumar | hi | 17:03 |
| abhisriatt | hi | 17:03 |
| pcarver | hi | 17:03 |
| *** svg has left #openstack-meeting-4 | 17:03 | |
| *** jay_s_b has quit IRC | 17:04 | |
| LouisF | cathy will be joining shortly | 17:04 |
| vikram_ | hi | 17:05 |
| LouisF | I posted an update to the API https://review.openstack.org/#/c/204695/ | 17:05 |
| *** stevelle has left #openstack-meeting-4 | 17:05 | |
| LouisF | vikram_: hi | 17:05 |
| xgerman | hi | 17:05 |
| *** tfukushima has quit IRC | 17:06 | |
| *** bharath has quit IRC | 17:06 | |
| LouisF | vikram_: thanks for the review of the previous patch | 17:06 |
| *** FallenPegasus has joined #openstack-meeting-4 | 17:06 | |
| vikram_ | ++ | 17:06 |
| *** ashtokolov has quit IRC | 17:07 | |
| *** ashtokolov has joined #openstack-meeting-4 | 17:07 | |
| *** harshs has joined #openstack-meeting-4 | 17:07 | |
| *** cahty has joined #openstack-meeting-4 | 17:07 | |
| cahty | hi everyone | 17:07 |
| LouisF | cahty: hi | 17:07 |
| *** padkrish has quit IRC | 17:07 | |
| cahty | sorry for my Internet conneciton issue | 17:07 |
| *** ashtokolov has quit IRC | 17:08 | |
| *** ashtokolov has joined #openstack-meeting-4 | 17:08 | |
| *** cahty has quit IRC | 17:08 | |
| *** vivek-ebay has quit IRC | 17:08 | |
| *** cathy_ has joined #openstack-meeting-4 | 17:09 | |
| *** padkrish has joined #openstack-meeting-4 | 17:09 | |
| cathy_ | hi everyone | 17:09 |
| LouisF | cathy_: hi | 17:09 |
| cathy_ | sorry for my Internet connection issue | 17:09 |
| *** Mohankumar has quit IRC | 17:09 | |
| cathy_ | let's start | 17:09 |
| cathy_ | #topic port pair | 17:10 |
| cathy_ | We are thinking about creating a separate resource for port pair. | 17:10 |
| LouisF | i feel that having a separate port-pair resource is useful | 17:10 |
| LouisF | as we have in the latest API spec | 17:10 |
| *** odyssey4me has left #openstack-meeting-4 | 17:11 | |
| *** prometheanfire has left #openstack-meeting-4 | 17:11 | |
| cathy_ | This is because: we would need to attach different attributes to the port. For example, to support Load distribution among a group of SFs, we need to attach a weight to the port pair | 17:12 |
| pcarver | cathy_: That sounds like a reasonable use case | 17:12 |
| *** ashtokolov has quit IRC | 17:12 | |
| cathy_ | Also different SF could support different chain identification mechanism, such as chainID in the new chain header or VLAN. So we need the chain identification attribute attached to the port pair too. | 17:13 |
| *** jerryz has joined #openstack-meeting-4 | 17:13 | |
| LouisF | +1 | 17:14 |
| cathy_ | so that the vSwitch can forward the appropriate packet format to the SF VM | 17:14 |
| pcarver | Is there any argument against having it as a separate resource? (I'm afraid I haven't read everyone's comments on every review in my backlog) | 17:15 |
| *** vishwanathj has quit IRC | 17:15 | |
| cathy_ | Another attribute needed is the " SF type" since the processing on the Switch is different for L2 Type SF and L3 type SF | 17:15 |
| cathy_ | pcarver: I don't think so, but vikram_ is asking whether we need it or not. | 17:16 |
| vikram_ | cathy_: i feel port group is sufficient to handle | 17:16 |
| *** sbalukoff has joined #openstack-meeting-4 | 17:17 | |
| pcarver | I think we agree it's needed in the data model, but are questioning whether it needs to be directly manipulated by the API. Is that correct? | 17:17 |
| pcarver | Or are we questioning whether it needs to be in the database at all? | 17:17 |
| pcarver | Basically I'm asking whether this is an API discussion or a database normalization discussion or both | 17:18 |
| LouisF | vikram_: i think that having it in the api makes it easier to be able to add attributes to a port-pair resource if needed in the future | 17:18 |
| *** mohankumar_ has joined #openstack-meeting-4 | 17:18 | |
| cathy_ | vikram_: If we need to attach additional attributes to the port pairs, it seems better to have a separate entity for port pair so that we cna extend the port pair without changing the port group. What do you think? | 17:18 |
| cathy_ | pcarver: both | 17:19 |
| *** vikram has joined #openstack-meeting-4 | 17:19 | |
| pcarver | The reason I'm asking, is because my followup question is: What's the harm in not exposing it in the API until we add something to the API that requires it? | 17:19 |
| vikram | sorry got disconnected | 17:19 |
| pcarver | If it's part of the DB model, but we don't need to manipulate it now via API we can always add to the API later | 17:19 |
| max_klyus | I'm not sure if somebody saw my comments about tunnel redundancy/balancing across CNs. Does it make sense or such kind of things not in scope? | 17:19 |
| vikram | cathy_: What I feel is too many CLI's will confuse user | 17:20 |
| *** vikram_ has quit IRC | 17:20 | |
| vikram | if we feel port-pair is necessary then we can remove port-group | 17:20 |
| cathy_ | pcarver: the harm is that we will make the port group API too complicated. | 17:21 |
| pcarver | vikram: I agree, especially if the CLI (or API) exposes things that have no current function and are just part of a future use design | 17:21 |
| LouisF | pcarver: if we have a port-pair resource then the chnages will be localized to the port-pair resource itself and not affect the port group resource | 17:21 |
| abhisriatt | vikram: I’m already confused :) | 17:21 |
| vikram | :) | 17:21 |
| cathy_ | vikram: yes, I understand your concern. But having a port pair API is more modular in terms of API design and can be useful for other features | 17:22 |
| pcarver | I think if we agree it belongs in the data model, the question is whether it needs to be exposed by API | 17:22 |
| vikram | ++ | 17:22 |
| pcarver | If there's no current functionality that the user can do with it, we shouldn't expose it now | 17:22 |
| xgerman | +1 | 17:22 |
| *** ashtokolov has joined #openstack-meeting-4 | 17:22 | |
| cathy_ | pcarver: Actually It is needed now:-) | 17:22 |
| *** ashtokolov has quit IRC | 17:22 | |
| pcarver | When we add the new capability to manipulate it in a useful way we can add it to the API | 17:23 |
| abhisriatt | cathy_:what’s the use case? | 17:23 |
| pcarver | cathy_: Can you give a user story? | 17:23 |
| *** bharath has joined #openstack-meeting-4 | 17:23 | |
| cathy_ | Ok, let me describe it. | 17:23 |
| pcarver | What would the end user of the CLI or API do with it, given the initial release of the SFC functionality? | 17:23 |
| cathy_ | Let's take the weight example. If there are multiple SF associated with a group, then we need the weight of each SF to be passed down for the Switch to choose which SF to use | 17:25 |
| LouisF | each port-pair can potentially have a different encap mechanism such as nsh, or vlan, etc | 17:25 |
| *** amotoki has quit IRC | 17:25 | |
| cathy_ | what Louis gives is another usage example. | 17:26 |
| pcarver | but are we supporting that now or are you future-proofing? | 17:26 |
| cathy_ | now | 17:26 |
| LouisF | the weight can definitely be used right now | 17:26 |
| *** vikram_ has joined #openstack-meeting-4 | 17:26 | |
| cathy_ | let's take the SF encap mechanism. | 17:26 |
| abhisriatt | How is this use case different from load balancing? | 17:27 |
| cathy_ | We already know that different SF uses different encap mechansm | 17:27 |
| LouisF | openflow support weights on buckets within a group | 17:27 |
| pcarver | The SF encap mechanism is definitely future use, though isn't it? We said that NSH would be dependent on future support from OvS | 17:27 |
| *** nhairston has joined #openstack-meeting-4 | 17:27 | |
| *** vikram has quit IRC | 17:28 | |
| pcarver | I'm not really opposed to including it in the API as long as the knob does something. | 17:28 |
| pcarver | But we shouldn't expect users to set a setting that can only be set one way | 17:28 |
| LouisF | and the OF bucket weight can be used for load distribution for a port-group that consists of port-pairs having different weights | 17:29 |
| *** dshakhray has joined #openstack-meeting-4 | 17:29 | |
| *** sdake_ has joined #openstack-meeting-4 | 17:29 | |
| *** dshakhray has quit IRC | 17:29 | |
| cathy_ | Even OVS does not support NSH, the OVS still needs to figure out the packet format when it sends the flow to the SF VM and that packet format depends on what format is supported by the VM SF. It could be VLAN or something else | 17:29 |
| pcarver | Also, consider testing. The more knobs in the API the more scenarios that need test cases to make sure they all work and in all combinations. | 17:30 |
| vikram_ | pcarver: I agree... let's expose what really is really required | 17:30 |
| cathy_ | pcarver: yes, we will need to test them | 17:30 |
| *** padkrish has quit IRC | 17:31 | |
| pcarver | Maybe, a slightly different topic, but are we expecting fully functioning implementation in Liberty timeframe? | 17:31 |
| cathy_ | abhisriatt: adding the weight is for the use case of load balancing. | 17:31 |
| pcarver | I'd rather see a less featured implementation that is complete in Liberty timeframe then a more featured implementation that isn't finished | 17:31 |
| cathy_ | pcarver: Liberty is our goal. | 17:31 |
| *** vivek-ebay has joined #openstack-meeting-4 | 17:32 | |
| *** sdake has quit IRC | 17:32 | |
| pcarver | cathy_: That's what I though, but with time running short that's why I'm questioning how many features, and equally importantly how many test cases can be delivered in that timeframe | 17:32 |
| LouisF | pcarver: what features do you see as stretch features? | 17:32 |
| *** vivek-ebay has quit IRC | 17:32 | |
| *** asselin has joined #openstack-meeting-4 | 17:33 | |
| xgerman | Liberty code freeze is in about two weeks - just a reminder | 17:34 |
| pcarver | LouisF: I'm behind on reviewing all the code that's already up on Gerrit, so I can't quite judge. I'm just asking if this particular topic we're discussing is included. | 17:34 |
| pcarver | And I don't mean just a required hop in the API | 17:34 |
| cathy_ | pcarver: we think the base features should include the load balancing among SFs which needs the weight, the format the OVS uses to forward to the SF which needs the specifcation of the SF encap format | 17:35 |
| pcarver | I mean a knob in the API that you'd be able to use in multiple ways, and that there would be test coverage for all ways of using it. | 17:35 |
| vikram_ | LouisF, cathy_: why we can't remove port group.. it's just grouping port-pairs. | 17:35 |
| vikram_ | instead list of port-pairs could be passed directly | 17:36 |
| vikram_ | while creating chain | 17:37 |
| mohankumar_ | vikram_: i think to achive load balancing | 17:37 |
| *** carl_baldwin has quit IRC | 17:38 | |
| max_klyus | if port group will be removed load balancing will be impossible | 17:38 |
| abhisriatt | And policies can also be easily applied on port groups rather on individual port-pairs. | 17:38 |
| mohankumar_ | port group will be the better way than passing directly | 17:38 |
| LouisF | vikram_: that will cause work to remove port-groups and then test | 17:39 |
| *** xingchao has joined #openstack-meeting-4 | 17:39 | |
| vikram_ | LoiusF: ok | 17:39 |
| cathy_ | I think we should keep the port group for LB | 17:39 |
| *** KLevenstein has quit IRC | 17:40 | |
| vikram_ | i still don't understand why we can't achieve LB without port-group.. | 17:40 |
| pcarver | I'm ok with keeping it as long as it's an implemented, tested feature, not just extra work for the API user to always pass one legal value | 17:41 |
| vikram_ | may be i need to think more.. and lagging behind :( | 17:41 |
| *** VW__ is now known as VW_ | 17:41 | |
| *** fawadkhaliq has quit IRC | 17:42 | |
| *** xingchao has quit IRC | 17:43 | |
| cathy_ | So if we want to shoot for Liberty, we will probably not add these new attributes and we will keep existing APIs and CLIs. Please everyone go to the API patch to give your review and we need to merge this as soon as possible. | 17:45 |
| cathy_ | These APIs have been implemented and tested | 17:46 |
| vikram_ | cathy_: Once API is finalisied will correct CLI and horizon patch | 17:46 |
| pcarver | cathy_: "These" meaning with or without the port group and load balancing feature? | 17:46 |
| cathy_ | vikram_: good. Thanks. | 17:46 |
| vikram_ | quit | 17:46 |
| *** vikram_ has quit IRC | 17:47 | |
| cathy_ | pcarver: with port group and LB | 17:47 |
| LouisF | yes | 17:47 |
| pcarver | Ok, thanks | 17:47 |
| abhisriatt | Have we finalized on the tunneling solution? | 17:47 |
| cathy_ | But we will do a very simple LB with out weight | 17:47 |
| LouisF | abhisriatt: we should discuss that now | 17:47 |
| abhisriatt | LouisF: sure. | 17:48 |
| pcarver | cathy_: but that's what I meant, if we do it without weight, do we need the port group to do that? | 17:48 |
| pcarver | Or is the user being asked to make the port group API call even though they can't actually configure it more than one way? | 17:48 |
| LouisF | abhisriatt: what is your suggestion here? | 17:48 |
| abhisriatt | LouisF: The approach that we used internally, actually uses MAC rewriting at each hop inside OVS to steer flows through SFs. | 17:49 |
| cathy_ | abhisriatt: we are thinking about using "raw packet+VXLAN" or "raw packet+ether header+VXLAN". Both are compliant with the IETF standard | 17:49 |
| cathy_ | abhisriatt: what's your thought? | 17:49 |
| LouisF | abhisriatt: to rewrite the dst mac? | 17:49 |
| abhisriatt | LouisF: Yes. | 17:49 |
| cathy_ | pcarver: we need port group since it specifies how many and what SFs belong to the same group for LB. | 17:50 |
| abhisriatt | In the beginning, the packet will have src ip, port and dst ip, port. | 17:50 |
| LouisF | when the packet returns from the SF what fields are used to re-classify? | 17:50 |
| cathy_ | pcarver: without weight, we cna just use round robin to choose the SF out of the group | 17:51 |
| abhisriatt | however, at the source, the ovs replaces the dst mac with the first SF VM mac | 17:51 |
| abhisriatt | cathy_: do we have a provision of learning in the load balancing. | 17:51 |
| abhisriatt | cathy_: for security SFs, we need to maintain the session. Hence, the flows must travel to same set of SFs. | 17:52 |
| max_klyus | weight parameter also will be useful for "smart" balancing potentially we could know the load of each SF at the moment | 17:52 |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 17:52 | |
| *** ashtokolov has joined #openstack-meeting-4 | 17:52 | |
| LouisF | abhisriatt: right, but when the packet is reterned from the SF how is that packet identified as being part of a specific chain to steer it to the next hop SF? | 17:52 |
| cathy_ | max_klyus: yes, it is for that purpose. But given the time limit, we will add that in the next release | 17:53 |
| LouisF | max_klyus: +1 | 17:53 |
| abhisriatt | LouisF: we can use flow classifers. For example: if we apply the SF on UDP traffic, our OVS rules look for UDP traffic. We can go very fine-grained at the port level too. | 17:53 |
| *** george__ has quit IRC | 17:53 | |
| *** nhairston has quit IRC | 17:53 | |
| *** vivek-ebay has joined #openstack-meeting-4 | 17:53 | |
| *** FallenPegasus has quit IRC | 17:53 | |
| LouisF | abhisriatt: ok so you use per-SF re-classification | 17:53 |
| *** vivek-ebay has quit IRC | 17:54 | |
| LouisF | this is assuming transparent SF that do not modify the packet n-tuple | 17:54 |
| cathy_ | abhisriatt: are you talking about the forwarding between the OVS and its connecting SF or the forwarding between two OVS on two Compute node? | 17:54 |
| abhisriatt | LouisF:Yes, we assuming SFs as blackboxes. | 17:54 |
| *** nhairston has joined #openstack-meeting-4 | 17:54 | |
| abhisriatt | cath_: forwarding between two OVS on two Compute node | 17:55 |
| *** Brian has joined #openstack-meeting-4 | 17:55 | |
| pcarver | I believe the MAC rewriting has a lot in common with how Contrail does it too, although with Contrail there's an additional L3 component. | 17:55 |
| *** salv-orl_ has joined #openstack-meeting-4 | 17:55 | |
| *** mattymo_ has left #openstack-meeting-4 | 17:55 | |
| *** Brian is now known as Guest21136 | 17:55 | |
| LouisF | abhisriatt: meaning they are transparent and do not modify the packet's header? | 17:55 |
| *** fawadkhaliq has joined #openstack-meeting-4 | 17:56 | |
| pcarver | Contrail controls the sequence of hops by setting the L3 next hop vRouter (which as a side effect essentially changes the MAC too) | 17:56 |
| *** sc68cal has quit IRC | 17:56 | |
| cathy_ | abhisriatt: pcarver there are two aspects we need to consider when forwarding between two OVSs. One is the inner packet destination associated with the destination SF VM and the other is the outer packet destination associated with the destination OVS. | 17:57 |
| abhisriatt | LouisF: yes. even if they do, since our ovs rules remember the next hop for the packet. we can send them. | 17:57 |
| cathy_ | I guess we do not have time to finish this discussion in this meeting. We will need a diagram to show the data path format. | 17:58 |
| LouisF | abhisriatt: we should discuss further | 17:58 |
| *** galstrom_zzz is now known as galstrom | 17:58 | |
| abhisriatt | cathy_, LouisF:yes. | 17:58 |
| *** salv-orlando has quit IRC | 17:59 | |
| cathy_ | abhisriatt: could you write up the data path format which will be very helpful for our discussion? We can also write a datapath format option. | 17:59 |
| *** padkrish has joined #openstack-meeting-4 | 17:59 | |
| *** Guest21136 has quit IRC | 18:00 | |
| *** fawadkhaliq has quit IRC | 18:00 | |
| *** fawadkhaliq has joined #openstack-meeting-4 | 18:00 | |
| cathy_ | Ok, folks, time is up. Let's resume the discussion next week. abhisriatt could you post your data path format on the wiki page Paul created. We will do the same. | 18:00 |
| abhisriatt | cathy_: sure. | 18:00 |
| cathy_ | Thanks everyone. bye for now. | 18:00 |
| abhisriatt | bye | 18:00 |
| Brian__ | bye | 18:00 |
| max_klyus | bye | 18:00 |
| pcarver | bye | 18:00 |
| mohankumar_ | bye | 18:00 |
| LouisF | bye | 18:00 |
| *** carl_baldwin has joined #openstack-meeting-4 | 18:01 | |
| *** Brian__ has quit IRC | 18:01 | |
| *** CheKoLyN has joined #openstack-meeting-4 | 18:01 | |
| LouisF | #endmeeting | 18:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 18:01 | |
| openstack | Meeting ended Thu Aug 13 18:01:19 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-13-17.02.html | 18:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-13-17.02.txt | 18:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-13-17.02.log.html | 18:01 |
| *** salv-orl_ has quit IRC | 18:01 | |
| *** cathy_ has quit IRC | 18:01 | |
| *** salv-orl_ has joined #openstack-meeting-4 | 18:01 | |
| *** mitchjameson has quit IRC | 18:02 | |
| *** sc68cal has joined #openstack-meeting-4 | 18:02 | |
| *** sc68cal has quit IRC | 18:02 | |
| *** sc68cal has joined #openstack-meeting-4 | 18:02 | |
| *** salv-orl_ has quit IRC | 18:04 | |
| *** salv-orl_ has joined #openstack-meeting-4 | 18:05 | |
| *** mohankumar_ has quit IRC | 18:05 | |
| *** jwagner_away is now known as jwagner | 18:06 | |
| *** mitchjameson has joined #openstack-meeting-4 | 18:06 | |
| *** echoingumesh has joined #openstack-meeting-4 | 18:09 | |
| *** echoingumesh has quit IRC | 18:09 | |
| *** jmckind has joined #openstack-meeting-4 | 18:09 | |
| *** echoingumesh has joined #openstack-meeting-4 | 18:10 | |
| *** johnsom has left #openstack-meeting-4 | 18:10 | |
| *** salv-orlando has joined #openstack-meeting-4 | 18:10 | |
| *** salv-orl_ has quit IRC | 18:12 | |
| *** padkrish has quit IRC | 18:13 | |
| *** padkrish has joined #openstack-meeting-4 | 18:13 | |
| *** echoingumesh has quit IRC | 18:14 | |
| *** aventera_ has joined #openstack-meeting-4 | 18:15 | |
| *** fawadkhaliq has quit IRC | 18:16 | |
| *** padkrish_ has joined #openstack-meeting-4 | 18:17 | |
| *** padkrish_ has quit IRC | 18:17 | |
| *** padkrish has quit IRC | 18:17 | |
| *** aventerav has quit IRC | 18:18 | |
| *** padkrish has joined #openstack-meeting-4 | 18:19 | |
| *** padkrish has quit IRC | 18:19 | |
| *** padkrish has joined #openstack-meeting-4 | 18:20 | |
| *** padkrish has quit IRC | 18:24 | |
| *** aventera_ has quit IRC | 18:28 | |
| *** aventerav has joined #openstack-meeting-4 | 18:29 | |
| *** abhisriatt has quit IRC | 18:29 | |
| *** nhairston1 has joined #openstack-meeting-4 | 18:31 | |
| *** nhairston has quit IRC | 18:31 | |
| *** echoingumesh has joined #openstack-meeting-4 | 18:32 | |
| *** Sukhdev has quit IRC | 18:32 | |
| *** salv-orlando has quit IRC | 18:39 | |
| *** padkrish has joined #openstack-meeting-4 | 18:42 | |
| *** ashtokolov has quit IRC | 18:43 | |
| *** jwagner is now known as jwagner_away | 18:47 | |
| *** baoli_ has quit IRC | 18:48 | |
| *** baoli has joined #openstack-meeting-4 | 18:49 | |
| *** jwagner_away is now known as jwagner | 18:49 | |
| *** padkrish has quit IRC | 18:56 | |
| *** abhisriatt has joined #openstack-meeting-4 | 18:57 | |
| *** baoli has quit IRC | 18:58 | |
| *** baoli has joined #openstack-meeting-4 | 18:58 | |
| *** baoli has quit IRC | 18:58 | |
| *** abhisriatt has quit IRC | 18:59 | |
| *** fawadkhaliq has joined #openstack-meeting-4 | 19:01 | |
| *** bharath has quit IRC | 19:03 | |
| *** bharath has joined #openstack-meeting-4 | 19:04 | |
| *** fawadkhaliq has quit IRC | 19:06 | |
| *** bapalm_ is now known as bapalm | 19:07 | |
| *** bharath has quit IRC | 19:08 | |
| *** sdake has joined #openstack-meeting-4 | 19:09 | |
| *** sdake_ has quit IRC | 19:12 | |
| *** padkrish has joined #openstack-meeting-4 | 19:14 | |
| *** nhairston1 has quit IRC | 19:16 | |
| *** padkrish has quit IRC | 19:18 | |
| *** padkrish has joined #openstack-meeting-4 | 19:20 | |
| *** FallenPegasus has joined #openstack-meeting-4 | 19:21 | |
| *** KLevenstein has joined #openstack-meeting-4 | 19:21 | |
| *** armax has quit IRC | 19:23 | |
| *** max_klyus has quit IRC | 19:26 | |
| *** padkrish has quit IRC | 19:27 | |
| *** puranamr has quit IRC | 19:30 | |
| *** padkrish has joined #openstack-meeting-4 | 19:30 | |
| *** puranamr has joined #openstack-meeting-4 | 19:30 | |
| *** salv-orlando has joined #openstack-meeting-4 | 19:31 | |
| *** singleth_ has quit IRC | 19:31 | |
| *** bharath has joined #openstack-meeting-4 | 19:32 | |
| *** numan has quit IRC | 19:33 | |
| *** singlethink has joined #openstack-meeting-4 | 19:33 | |
| *** nhairston has joined #openstack-meeting-4 | 19:35 | |
| *** salv-orlando has quit IRC | 19:36 | |
| *** jmckind has quit IRC | 19:38 | |
| *** padkrish has quit IRC | 19:39 | |
| *** padkrish has joined #openstack-meeting-4 | 19:39 | |
| *** padkrish_ has joined #openstack-meeting-4 | 19:40 | |
| *** padkrish has quit IRC | 19:40 | |
| *** Brian has joined #openstack-meeting-4 | 19:43 | |
| *** Brian is now known as Guest27818 | 19:43 | |
| *** VW_ has quit IRC | 19:44 | |
| *** VW_ has joined #openstack-meeting-4 | 19:44 | |
| *** puranamr has quit IRC | 19:46 | |
| *** puranamr has joined #openstack-meeting-4 | 19:47 | |
| *** alextricity has quit IRC | 19:47 | |
| *** Sukhdev has joined #openstack-meeting-4 | 19:47 | |
| *** wojdev has joined #openstack-meeting-4 | 19:48 | |
| *** VW_ has quit IRC | 19:49 | |
| *** jwagner is now known as jwagner_away | 19:49 | |
| *** salv-orlando has joined #openstack-meeting-4 | 19:50 | |
| *** Guest27818 has quit IRC | 19:51 | |
| *** jwagner_away is now known as jwagner | 19:52 | |
| *** wojdev has quit IRC | 19:58 | |
| *** padkrish_ has quit IRC | 20:01 | |
| *** padkrish has joined #openstack-meeting-4 | 20:01 | |
| *** ashtokolov has joined #openstack-meeting-4 | 20:02 | |
| *** puranamr has quit IRC | 20:03 | |
| *** puranamr has joined #openstack-meeting-4 | 20:04 | |
| *** padkrish_ has joined #openstack-meeting-4 | 20:04 | |
| *** padkrish has quit IRC | 20:04 | |
| *** wojdev has joined #openstack-meeting-4 | 20:05 | |
| *** wojdev has quit IRC | 20:05 | |
| *** ivar-lazzaro has quit IRC | 20:06 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 20:06 | |
| *** puranamr has quit IRC | 20:07 | |
| *** puranamr has joined #openstack-meeting-4 | 20:07 | |
| *** jmckind has joined #openstack-meeting-4 | 20:08 | |
| *** ivar-lazzaro has quit IRC | 20:10 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 20:11 | |
| *** VW_ has joined #openstack-meeting-4 | 20:12 | |
| *** britthou_ has joined #openstack-meeting-4 | 20:15 | |
| *** jmckind has quit IRC | 20:17 | |
| *** Shamail has joined #openstack-meeting-4 | 20:17 | |
| *** britthouser has quit IRC | 20:18 | |
| *** ashtokolov has quit IRC | 20:18 | |
| *** britthou_ has quit IRC | 20:19 | |
| *** ashtokolov has joined #openstack-meeting-4 | 20:20 | |
| *** ivar-lazzaro has quit IRC | 20:24 | |
| *** mitchjameson has quit IRC | 20:25 | |
| *** nhairston has quit IRC | 20:27 | |
| *** adityavajjha has quit IRC | 20:27 | |
| *** baoli has joined #openstack-meeting-4 | 20:29 | |
| *** Shamail has quit IRC | 20:30 | |
| *** mitchjameson has joined #openstack-meeting-4 | 20:30 | |
| *** sdake_ has joined #openstack-meeting-4 | 20:32 | |
| *** baoli has quit IRC | 20:34 | |
| *** sdake has quit IRC | 20:36 | |
| *** krtaylor has quit IRC | 20:37 | |
| *** abhisriatt has joined #openstack-meeting-4 | 20:37 | |
| *** LouisF has quit IRC | 20:40 | |
| *** xingchao has joined #openstack-meeting-4 | 20:42 | |
| *** jwagner is now known as jwagner_away | 20:46 | |
| *** ashtokolov has quit IRC | 20:46 | |
| *** sbalukoff has quit IRC | 20:46 | |
| *** xingchao has quit IRC | 20:48 | |
| aventerav | yeah | 20:48 |
| *** aventerav has left #openstack-meeting-4 | 20:48 | |
| *** fawadkhaliq has joined #openstack-meeting-4 | 20:48 | |
| *** krtaylor has joined #openstack-meeting-4 | 20:49 | |
| *** Guest61394 is now known as med_ | 20:51 | |
| *** med_ has joined #openstack-meeting-4 | 20:51 | |
| *** VW_ has quit IRC | 20:58 | |
| *** sbalukoff has joined #openstack-meeting-4 | 20:58 | |
| *** VW_ has joined #openstack-meeting-4 | 20:58 | |
| *** abhisriatt has quit IRC | 21:01 | |
| *** VW_ has quit IRC | 21:03 | |
| *** jmcbride has joined #openstack-meeting-4 | 21:04 | |
| *** jmcbride has left #openstack-meeting-4 | 21:05 | |
| *** yamamoto has joined #openstack-meeting-4 | 21:10 | |
| *** jckasper has quit IRC | 21:11 | |
| *** VW_ has joined #openstack-meeting-4 | 21:14 | |
| *** rfolco has quit IRC | 21:14 | |
| *** ashtokolov has joined #openstack-meeting-4 | 21:15 | |
| *** vishwanathj has joined #openstack-meeting-4 | 21:17 | |
| *** VW_ has quit IRC | 21:19 | |
| *** yamamoto has quit IRC | 21:19 | |
| *** Sukhdev has quit IRC | 21:21 | |
| *** armax has joined #openstack-meeting-4 | 21:22 | |
| *** Sukhdev has joined #openstack-meeting-4 | 21:24 | |
| *** jwagner_away is now known as jwagner | 21:26 | |
| *** B_Smith has quit IRC | 21:31 | |
| *** dannywilson has left #openstack-meeting-4 | 21:36 | |
| *** ajmiller has quit IRC | 21:37 | |
| *** jmckind has joined #openstack-meeting-4 | 21:37 | |
| *** padkrish_ has quit IRC | 21:39 | |
| *** puranamr has quit IRC | 21:39 | |
| *** padkrish has joined #openstack-meeting-4 | 21:39 | |
| *** ajmiller has joined #openstack-meeting-4 | 21:40 | |
| *** VW_ has joined #openstack-meeting-4 | 21:40 | |
| *** padkrish_ has joined #openstack-meeting-4 | 21:41 | |
| *** nhairston has joined #openstack-meeting-4 | 21:41 | |
| *** padkrish has quit IRC | 21:41 | |
| *** puranamr has joined #openstack-meeting-4 | 21:43 | |
| *** jwagner is now known as jwagner[away] | 21:45 | |
| *** jwagner[away] is now known as jwagner | 21:45 | |
| *** B_Smith has joined #openstack-meeting-4 | 21:45 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 21:46 | |
| *** nhairston has quit IRC | 21:48 | |
| *** jmckind has quit IRC | 21:50 | |
| *** abhisriatt has joined #openstack-meeting-4 | 21:51 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 21:52 | |
| *** FallenPegasus has quit IRC | 21:53 | |
| *** BjoernT has quit IRC | 21:54 | |
| *** puranamr has quit IRC | 21:58 | |
| *** baoli has joined #openstack-meeting-4 | 22:00 | |
| *** abhisriatt has quit IRC | 22:01 | |
| *** armax has quit IRC | 22:04 | |
| *** klamath has quit IRC | 22:05 | |
| *** baoli has quit IRC | 22:05 | |
| *** padkrish_ has quit IRC | 22:06 | |
| *** padkrish has joined #openstack-meeting-4 | 22:07 | |
| *** dzamboni has quit IRC | 22:07 | |
| *** puranamr has joined #openstack-meeting-4 | 22:10 | |
| *** padkrish has quit IRC | 22:11 | |
| *** padkrish has joined #openstack-meeting-4 | 22:11 | |
| *** sdake has joined #openstack-meeting-4 | 22:12 | |
| *** KLevenstein has quit IRC | 22:14 | |
| *** sdake_ has quit IRC | 22:16 | |
| *** FallenPegasus has joined #openstack-meeting-4 | 22:17 | |
| *** VW_ has quit IRC | 22:18 | |
| *** VW_ has joined #openstack-meeting-4 | 22:18 | |
| *** puranamr has quit IRC | 22:19 | |
| *** bnemec has quit IRC | 22:20 | |
| *** VW_ has quit IRC | 22:23 | |
| *** CheKoLyN has quit IRC | 22:25 | |
| *** vivek-ebay has joined #openstack-meeting-4 | 22:26 | |
| *** galstrom is now known as galstrom_zzz | 22:35 | |
| *** jwagner is now known as jwagner[away] | 22:36 | |
| *** padkrish has quit IRC | 22:36 | |
| *** puranamr has joined #openstack-meeting-4 | 22:38 | |
| *** padkrish has joined #openstack-meeting-4 | 22:40 | |
| *** padkrish has quit IRC | 22:40 | |
| *** padkrish has joined #openstack-meeting-4 | 22:41 | |
| *** sdake_ has joined #openstack-meeting-4 | 22:42 | |
| *** ashtokolov has quit IRC | 22:43 | |
| *** ashtokolov has joined #openstack-meeting-4 | 22:44 | |
| *** sdake has quit IRC | 22:46 | |
| *** vivek-ebay has quit IRC | 22:46 | |
| *** vivek-ebay has joined #openstack-meeting-4 | 22:46 | |
| *** singlethink has quit IRC | 22:49 | |
| *** puranamr has quit IRC | 22:49 | |
| *** jwagner[away] is now known as jwagner_away | 22:50 | |
| *** puranamr has joined #openstack-meeting-4 | 22:52 | |
| *** padkrish has quit IRC | 23:01 | |
| *** padkrish has joined #openstack-meeting-4 | 23:01 | |
| *** padkrish has quit IRC | 23:02 | |
| *** padkrish has joined #openstack-meeting-4 | 23:02 | |
| *** FallenPegasus is now known as MarkAtwood | 23:02 | |
| *** ivar-lazzaro has quit IRC | 23:03 | |
| *** abhisriatt has joined #openstack-meeting-4 | 23:13 | |
| *** abhisriatt has quit IRC | 23:21 | |
| *** geoffarnold has quit IRC | 23:22 | |
| *** blahRus has quit IRC | 23:23 | |
| *** Sukhdev has quit IRC | 23:24 | |
| *** nhairston has joined #openstack-meeting-4 | 23:27 | |
| *** krtaylor has quit IRC | 23:32 | |
| *** geoffarnold has joined #openstack-meeting-4 | 23:32 | |
| *** carl_baldwin has quit IRC | 23:37 | |
| *** padkrish has quit IRC | 23:41 | |
| *** padkrish has joined #openstack-meeting-4 | 23:41 | |
| *** Sukhdev has joined #openstack-meeting-4 | 23:44 | |
| *** krtaylor has joined #openstack-meeting-4 | 23:45 | |
| *** padkrish has quit IRC | 23:45 | |
| *** jpekkari has joined #openstack-meeting-4 | 23:48 | |
| *** padkrish has joined #openstack-meeting-4 | 23:49 | |
| *** killer_prince has joined #openstack-meeting-4 | 23:50 | |
| *** harshs has quit IRC | 23:50 | |
| *** fawadkhaliq has quit IRC | 23:50 | |
| *** markvoelker has quit IRC | 23:50 | |
| *** padkrish has quit IRC | 23:54 | |
| *** xingchao has joined #openstack-meeting-4 | 23:57 | |
| *** padkrish has joined #openstack-meeting-4 | 23:58 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!