Wednesday, 2013-12-11

*** jcooley_ has quit IRC00:02
*** jcooley_ has joined #openstack-meeting-alt00:02
*** adrian_otto has joined #openstack-meeting-alt00:03
*** yamahata_ has quit IRC00:04
*** gokrokve has quit IRC00:04
*** gokrokve has joined #openstack-meeting-alt00:05
*** jcooley_ has quit IRC00:07
*** lblanchard has quit IRC00:08
*** gokrokve has quit IRC00:09
*** lblanchard has joined #openstack-meeting-alt00:12
*** jcooley_ has joined #openstack-meeting-alt00:13
*** jcooley_ has quit IRC00:13
*** jcooley_ has joined #openstack-meeting-alt00:13
*** rudrarugge has joined #openstack-meeting-alt00:15
*** jcooley_ has quit IRC00:18
*** jergerber has quit IRC00:18
*** amytron has quit IRC00:22
*** rudrarug_ has joined #openstack-meeting-alt00:24
*** rudrarugge has quit IRC00:24
*** banix has quit IRC00:26
*** vkmc has quit IRC00:28
*** bdpayne has quit IRC00:30
*** bdpayne has joined #openstack-meeting-alt00:31
*** rudrarug_ has quit IRC00:33
*** sarob has joined #openstack-meeting-alt00:34
*** brents has quit IRC00:40
*** datsun180b has quit IRC00:44
*** _ozstacker_ has joined #openstack-meeting-alt00:45
*** sarob has quit IRC00:48
*** ozstacker has quit IRC00:49
*** sarob has joined #openstack-meeting-alt00:49
*** gokrokve has joined #openstack-meeting-alt00:49
*** brents has joined #openstack-meeting-alt00:50
*** electrichead has joined #openstack-meeting-alt00:52
*** sarob has quit IRC00:53
*** yamahata_ has joined #openstack-meeting-alt00:55
*** yamahata_ has quit IRC00:55
*** yamahata_ has joined #openstack-meeting-alt00:56
*** venkatesh has joined #openstack-meeting-alt01:04
*** flwang has joined #openstack-meeting-alt01:05
*** bdpayne has quit IRC01:05
*** julim has joined #openstack-meeting-alt01:09
*** amytron has joined #openstack-meeting-alt01:21
*** adrian_otto has left #openstack-meeting-alt01:22
*** sarob has joined #openstack-meeting-alt01:23
*** sarob has quit IRC01:28
*** nosnos has joined #openstack-meeting-alt01:29
*** Barker has joined #openstack-meeting-alt01:30
*** brents has quit IRC01:33
*** mozawa has joined #openstack-meeting-alt01:33
*** julim has quit IRC01:40
*** IlyaE has quit IRC01:43
*** dguitarbite has joined #openstack-meeting-alt01:44
*** sarob has joined #openstack-meeting-alt01:47
*** amcrn has quit IRC01:48
*** alazarev has quit IRC01:53
*** flwang has quit IRC01:55
*** banix has joined #openstack-meeting-alt01:58
*** mozawa has quit IRC02:00
*** rongze has joined #openstack-meeting-alt02:01
*** jcooley_ has joined #openstack-meeting-alt02:04
*** gokrokve has quit IRC02:08
*** gokrokve has joined #openstack-meeting-alt02:08
*** devkulkarni has quit IRC02:12
*** gokrokve has quit IRC02:13
*** banix has quit IRC02:19
*** colinmcnamara has quit IRC02:20
*** colinmcn_ has quit IRC02:20
*** gokrokve has joined #openstack-meeting-alt02:21
*** banix has joined #openstack-meeting-alt02:22
*** banix has quit IRC02:24
*** banix has joined #openstack-meeting-alt02:25
*** amytron has quit IRC02:25
*** hua has joined #openstack-meeting-alt02:29
*** sarob has quit IRC02:29
*** banix has quit IRC02:30
*** sarob has joined #openstack-meeting-alt02:30
*** rongze has quit IRC02:31
*** banix has joined #openstack-meeting-alt02:31
*** hua has left #openstack-meeting-alt02:33
*** radix_ has quit IRC02:33
*** sarob_ has joined #openstack-meeting-alt02:34
*** sarob has quit IRC02:35
*** venkatesh has quit IRC02:40
*** jcooley_ has quit IRC02:43
*** rongze has joined #openstack-meeting-alt02:46
*** sarob_ is now known as sarob02:51
*** _ozstacker_ has quit IRC02:53
*** nati_ueno has quit IRC02:54
*** ozstacker has joined #openstack-meeting-alt03:05
*** sarob has quit IRC03:06
*** sarob has joined #openstack-meeting-alt03:06
*** sballe has quit IRC03:06
*** sballe has joined #openstack-meeting-alt03:07
*** sarob has quit IRC03:11
*** coolsvap has joined #openstack-meeting-alt03:17
*** markwash has quit IRC03:21
*** lblanchard has quit IRC03:32
*** flwang has joined #openstack-meeting-alt03:35
*** brents has joined #openstack-meeting-alt03:43
*** devkulkarni has joined #openstack-meeting-alt03:53
*** brents has quit IRC03:56
*** brents has joined #openstack-meeting-alt04:07
*** SergeyLukjanov has joined #openstack-meeting-alt04:17
*** SergeyLukjanov has quit IRC04:21
*** brents_ has joined #openstack-meeting-alt04:24
*** aignatov has joined #openstack-meeting-alt04:24
*** brents has quit IRC04:24
*** markwash has joined #openstack-meeting-alt04:24
*** yamahata_ has quit IRC04:24
*** plomakin has quit IRC04:24
*** plomakin has joined #openstack-meeting-alt04:25
*** dguitarbite has quit IRC04:27
*** brents_ is now known as brents04:27
*** SergeyLukjanov has joined #openstack-meeting-alt04:27
*** yamahata_ has joined #openstack-meeting-alt04:28
*** aignatov has quit IRC04:28
*** Barker has quit IRC04:29
*** brents_ has joined #openstack-meeting-alt04:39
*** brents has quit IRC04:40
*** brents_ is now known as brents04:40
*** rongze has quit IRC04:50
*** brents has quit IRC05:04
*** SergeyLukjanov is now known as _SergeyLukjanov05:09
*** _SergeyLukjanov has quit IRC05:10
*** SergeyLukjanov has joined #openstack-meeting-alt05:14
*** jjmb1 has joined #openstack-meeting-alt05:15
*** jjmb has quit IRC05:17
*** brents has joined #openstack-meeting-alt05:17
*** boris-42 has joined #openstack-meeting-alt05:18
*** sc68cal has quit IRC05:18
*** sc68cal has joined #openstack-meeting-alt05:18
*** rongze has joined #openstack-meeting-alt05:20
*** devkulkarni has quit IRC05:21
*** nosnos_ has joined #openstack-meeting-alt05:31
*** jcooley_ has joined #openstack-meeting-alt05:33
*** nadya has joined #openstack-meeting-alt05:34
*** nosnos has quit IRC05:34
*** nadya is now known as Guest2471405:34
*** rongze has quit IRC05:35
*** banix has quit IRC05:54
*** venkatesh has joined #openstack-meeting-alt05:56
*** juice has quit IRC05:57
*** devananda has quit IRC05:57
*** devananda has joined #openstack-meeting-alt05:57
*** Ghe_HPDiscover has quit IRC05:57
*** vipuls has quit IRC05:58
*** Guest24714 has quit IRC05:59
*** IlyaE has joined #openstack-meeting-alt06:02
*** rongze has joined #openstack-meeting-alt06:03
*** juice has joined #openstack-meeting-alt06:03
*** nosnos_ has quit IRC06:04
*** nosnos has joined #openstack-meeting-alt06:05
*** vipul has joined #openstack-meeting-alt06:07
*** rongze has quit IRC06:07
*** venkatesh_ has joined #openstack-meeting-alt06:07
*** brents has quit IRC06:09
*** venkatesh has quit IRC06:10
*** rongze has joined #openstack-meeting-alt06:15
*** IlyaE has quit IRC06:18
*** SergeyLukjanov has quit IRC06:21
*** coolsvap has quit IRC06:25
*** Ghe_HPDiscover has joined #openstack-meeting-alt06:35
*** coolsvap has joined #openstack-meeting-alt06:38
*** jcooley_ has quit IRC06:39
*** aignatov has joined #openstack-meeting-alt06:40
*** denis_makogon has joined #openstack-meeting-alt06:42
*** gokrokve has quit IRC06:43
*** gokrokve has joined #openstack-meeting-alt06:43
*** SushilKM has joined #openstack-meeting-alt06:46
*** gokrokve has quit IRC06:48
*** skostiuchenko has quit IRC06:48
*** skostiuchenko has joined #openstack-meeting-alt06:49
*** lifeless has quit IRC07:05
*** akuznetsov has quit IRC07:08
*** jcooley_ has joined #openstack-meeting-alt07:09
*** jcooley_ has quit IRC07:15
*** IlyaE has joined #openstack-meeting-alt07:16
*** jtomasek has joined #openstack-meeting-alt07:20
*** IlyaE has quit IRC07:22
*** boris-42 has quit IRC07:22
*** venkatesh_ has quit IRC07:23
*** jtomasek has quit IRC07:26
*** jtomasek has joined #openstack-meeting-alt07:27
*** aignatov has quit IRC07:32
*** nati_ueno has joined #openstack-meeting-alt07:36
*** alazarev has joined #openstack-meeting-alt07:36
*** aignatov has joined #openstack-meeting-alt07:40
*** igormarnat has joined #openstack-meeting-alt07:44
*** coolsvap has quit IRC07:47
*** SergeyLukjanov has joined #openstack-meeting-alt07:49
*** alazarev has quit IRC07:49
*** mozawa has joined #openstack-meeting-alt07:49
*** sarob has joined #openstack-meeting-alt07:51
*** jcoufal has joined #openstack-meeting-alt08:04
*** jcoufal has quit IRC08:04
*** jcooley_ has joined #openstack-meeting-alt08:05
*** jcoufal has joined #openstack-meeting-alt08:05
*** jcooley_ has quit IRC08:09
*** flaper87|afk is now known as flaper8708:13
*** ruhe has joined #openstack-meeting-alt08:16
*** markwash has quit IRC08:21
*** ruhe has quit IRC08:21
*** ruhe has joined #openstack-meeting-alt08:22
*** ruhe has quit IRC08:25
*** yogesh has joined #openstack-meeting-alt08:26
*** akuznetsov has joined #openstack-meeting-alt08:31
*** markwash has joined #openstack-meeting-alt08:32
*** sergmelikyan has joined #openstack-meeting-alt08:32
*** radix_ has joined #openstack-meeting-alt08:36
*** nati_ueno has quit IRC08:38
*** sergmelikyan has quit IRC08:45
*** rongze has quit IRC08:46
*** rongze has joined #openstack-meeting-alt08:47
*** yogesh has quit IRC08:53
*** akuznetsov has quit IRC08:54
*** yogesh has joined #openstack-meeting-alt08:55
*** jcooley_ has joined #openstack-meeting-alt09:00
*** jcooley_ has quit IRC09:04
*** boris-42 has joined #openstack-meeting-alt09:06
*** akuznetsov has joined #openstack-meeting-alt09:14
*** markwash has quit IRC09:20
*** venkatesh has joined #openstack-meeting-alt09:21
*** derekh has joined #openstack-meeting-alt09:23
*** yogesh has quit IRC09:24
*** mozawa has quit IRC09:24
*** sergmelikyan has joined #openstack-meeting-alt09:26
*** yogesh_ has joined #openstack-meeting-alt09:27
*** yogesh has joined #openstack-meeting-alt09:29
*** akuznetsov has quit IRC09:31
*** yogesh_ has quit IRC09:32
*** nosnos_ has joined #openstack-meeting-alt09:36
*** yogesh has quit IRC09:37
*** flwang has quit IRC09:38
*** yogesh has joined #openstack-meeting-alt09:39
*** ativelkov has joined #openstack-meeting-alt09:39
*** nosnos has quit IRC09:40
*** ativelkov has left #openstack-meeting-alt09:40
*** yogesh_ has joined #openstack-meeting-alt09:41
*** denis_makogon has quit IRC09:42
*** lifeless has joined #openstack-meeting-alt09:43
*** yogesh has quit IRC09:44
*** jcoufal has quit IRC09:58
*** yogesh has joined #openstack-meeting-alt10:03
*** katyafervent has joined #openstack-meeting-alt10:03
*** yogesh__ has joined #openstack-meeting-alt10:04
*** yogesh_ has quit IRC10:05
*** yogesh has quit IRC10:08
*** heyongli has joined #openstack-meeting-alt10:10
*** dguitarbite has joined #openstack-meeting-alt10:13
*** rossella_s has joined #openstack-meeting-alt10:14
*** rsblendido has joined #openstack-meeting-alt10:14
*** aignatov has quit IRC10:14
*** SergeyLukjanov is now known as _SergeyLukjanov10:23
*** akuznetsov has joined #openstack-meeting-alt10:24
*** venkatesh has quit IRC10:25
*** sarob has quit IRC10:26
*** bot_bot is now known as denis_makogon10:34
*** venkatesh has joined #openstack-meeting-alt10:37
*** igormarnat has quit IRC10:45
*** akuznetsov has quit IRC10:45
*** aignatov has joined #openstack-meeting-alt10:46
*** akuznetsov has joined #openstack-meeting-alt10:48
*** igormarnat_ has joined #openstack-meeting-alt10:48
*** jjmb1 has quit IRC10:51
*** yogesh__ has quit IRC10:54
*** nosnos_ has quit IRC10:57
*** nosnos has joined #openstack-meeting-alt10:57
*** yhe_ has joined #openstack-meeting-alt11:04
*** heyongli has quit IRC11:06
*** akuznetsov has quit IRC11:07
*** akuznetsov has joined #openstack-meeting-alt11:09
*** sarob has joined #openstack-meeting-alt11:16
*** venkatesh has quit IRC11:20
*** rongze has quit IRC11:21
*** nati_ueno has joined #openstack-meeting-alt11:21
*** jcoufal has joined #openstack-meeting-alt11:24
*** yhe_ is now known as heyongli11:33
*** yamahata_ has quit IRC11:33
*** jcooley_ has joined #openstack-meeting-alt11:43
*** rongze has joined #openstack-meeting-alt11:44
*** jcooley_ has quit IRC11:47
*** sarob has quit IRC11:48
*** flwang has joined #openstack-meeting-alt11:55
*** yogesh has joined #openstack-meeting-alt12:05
*** vkmc has joined #openstack-meeting-alt12:08
*** yogesh has quit IRC12:10
*** SergeyLukjanov has joined #openstack-meeting-alt12:10
*** sarob has joined #openstack-meeting-alt12:13
*** jcoufal has quit IRC12:31
*** jjmb has joined #openstack-meeting-alt12:41
*** sarob has quit IRC12:45
*** jcoufal-mob has joined #openstack-meeting-alt12:56
*** pdmars has joined #openstack-meeting-alt13:01
*** slagle has quit IRC13:08
*** jcoufal-mob_ has joined #openstack-meeting-alt13:08
*** sarob has joined #openstack-meeting-alt13:10
*** dprince has joined #openstack-meeting-alt13:11
*** jcoufal-mob has quit IRC13:11
*** sballe has quit IRC13:14
*** lblanchard has joined #openstack-meeting-alt13:17
*** dukhlov has joined #openstack-meeting-alt13:26
*** jcooley_ has joined #openstack-meeting-alt13:30
*** igormarnat__ has joined #openstack-meeting-alt13:30
*** igormarnat_ has quit IRC13:33
*** sarob has quit IRC13:35
*** jdob has joined #openstack-meeting-alt13:35
*** jcooley_ has quit IRC13:35
*** mozawa has joined #openstack-meeting-alt13:40
*** banix has joined #openstack-meeting-alt13:44
*** krtaylor has joined #openstack-meeting-alt13:44
*** jjmb has quit IRC13:46
*** banix has quit IRC13:47
*** banix has joined #openstack-meeting-alt13:48
*** abramley has joined #openstack-meeting-alt13:49
*** igormarnat__ has quit IRC13:54
*** igormarnat_ has joined #openstack-meeting-alt13:58
*** NikitaKonovalov has joined #openstack-meeting-alt14:02
*** BrianB_ has joined #openstack-meeting-alt14:03
*** slagle has joined #openstack-meeting-alt14:05
*** sarob has joined #openstack-meeting-alt14:06
*** nosnos has quit IRC14:06
*** banix has quit IRC14:09
*** dguitarbite has quit IRC14:11
*** sarob has quit IRC14:14
*** jcoufal has joined #openstack-meeting-alt14:17
*** NikitaKonovalov has quit IRC14:19
*** eankutse has joined #openstack-meeting-alt14:20
*** eankutse has quit IRC14:21
*** eankutse has joined #openstack-meeting-alt14:21
*** lblanchard has quit IRC14:23
*** jcooley_ has joined #openstack-meeting-alt14:25
*** jergerber has joined #openstack-meeting-alt14:27
*** jcoufal-mob_ has quit IRC14:27
*** sarob has joined #openstack-meeting-alt14:27
*** jcooley_ has quit IRC14:29
*** sarob has quit IRC14:32
*** nati_ueno has quit IRC14:33
*** rnirmal has joined #openstack-meeting-alt14:34
*** dukhlov_ has joined #openstack-meeting-alt14:36
*** dukhlov has quit IRC14:36
*** HenryG has quit IRC14:36
*** kevinconway has joined #openstack-meeting-alt14:42
*** jjmb has joined #openstack-meeting-alt14:43
*** matrohon has joined #openstack-meeting-alt14:43
*** jergerber has quit IRC14:47
*** esker has joined #openstack-meeting-alt14:47
*** jergerber has joined #openstack-meeting-alt14:48
*** SushilKM has quit IRC14:50
*** dhellmann has joined #openstack-meeting-alt14:53
*** amytron has joined #openstack-meeting-alt14:56
*** jcoufal-mob has joined #openstack-meeting-alt14:59
*** flwang has left #openstack-meeting-alt15:00
*** jdob has quit IRC15:00
*** BrianB_ has quit IRC15:02
*** SergeyLukjanov_ has joined #openstack-meeting-alt15:03
*** jecarey has joined #openstack-meeting-alt15:04
*** jdob has joined #openstack-meeting-alt15:06
*** SergeyLukjanov has quit IRC15:06
*** Swami has joined #openstack-meeting-alt15:06
Swamihi15:06
SwamiRobin wang ping:15:07
SwamiJames Clark ping;15:07
Swami#startmeeting Distributed Virtual Router15:08
openstackMeeting started Wed Dec 11 15:08:01 2013 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:08
*** openstack changes topic to " (Meeting topic: Distributed Virtual Router)"15:08
openstackThe meeting name has been set to 'distributed_virtual_router'15:08
*** boris-42 has quit IRC15:08
*** jcoufal has quit IRC15:08
*** rkukura has joined #openstack-meeting-alt15:08
Swamihi Robin I got your email regarding your questions I will try to answer it and send you a reply by today15:09
Swami#topic L2-L3 data sync15:10
*** openstack changes topic to "L2-L3 data sync (Meeting topic: Distributed Virtual Router)"15:10
*** gokrokve has joined #openstack-meeting-alt15:10
*** jcoufal-mob has quit IRC15:10
*** SergeyLukjanov has joined #openstack-meeting-alt15:10
SwamiRobin I did go through your WIP code, that suggests that we need to add flows in the ml2-ovs file, but my concern was to do that activity from the L3-agent. Mean that it should originate from the L3 Agent when a VM port is being added to the routed network15:11
*** SergeyLukjanov_ has quit IRC15:12
*** HenryG has joined #openstack-meeting-alt15:13
SwamiRobin: you did mention in your email that we need a brain to store the data and push the data to all agents. I think in my view, it should be part of the L3-Plugin extension.15:13
*** Barker has joined #openstack-meeting-alt15:14
*** jcoufal has joined #openstack-meeting-alt15:15
SwamiSo the plan would be when an L2 event occurs, that is when a port is added to a VM, L2 agent or the ML2-L2 drivers will then communicate the information to L3 agent residing in that node. The L3 agent should take necessary action on the data and also communicate the data to the plugin. The plugin should intern be pushing or syncing the data with other L3 agents that have been registered.15:16
SwamiI have updated the google doc, with information on what data need to be stored in the L3-plugin extensions.15:17
SwamiMay be if you can spend some time how we can push the L2 data to L3 that would be great. Meanwhile I will also take a look at it.15:18
*** jcooley_ has joined #openstack-meeting-alt15:18
SwamiJames Clark are you there.15:18
SwamiMay be it might be too late for James to join the meeting.15:19
Swami#topic L3 Support for Distributed versus the Edge15:20
*** openstack changes topic to "L3 Support for Distributed versus the Edge (Meeting topic: Distributed Virtual Router)"15:20
SwamiI sent out an email couple of days back asking the community what would be right option from an API perspective to distinguish between a distributed router and an edge or centralized router.15:21
SwamiI was planning to use the "distributed" argument that is already in the router API.15:21
*** sarob has joined #openstack-meeting-alt15:21
SwamiBut I got some feedback on that, since L3 Plugin is also a service now, the community thinks that it should also behave like any other plugins to distinguish. So the community recommendation is to use the "provider" flag to distinguish the Routers.15:23
*** julim has joined #openstack-meeting-alt15:23
*** jcooley_ has quit IRC15:23
*** hemanthravi has joined #openstack-meeting-alt15:24
SwamiSome people also feel that why do we need to distinguish between a centralized router and distributed router. It is just implementation specific. Configuration wise it should be always a router.15:24
*** NikitaKonovalov has joined #openstack-meeting-alt15:24
SwamiSo we may have to close the loop on this issue.15:24
Swami#topic North-South Proposal15:25
*** openstack changes topic to "North-South Proposal (Meeting topic: Distributed Virtual Router)"15:25
hemanthraviIs the idea to use an option in  the config file for the plugin  implementing  the  L3 ext as opposed to specifying it in the API15:26
*** sarob has quit IRC15:26
SwamiHi hemanthravi15:26
hemanthravihi15:26
SwamiWe were planning initially to use both the options. We will have config.ini file for the L3 agent configuring that local L3 agent as Distributed L3 Agent and also can use the API flag to configure the router as distributed15:27
*** sarob has joined #openstack-meeting-alt15:27
SwamiBut this was with the idea of having a mixed environment where you have both the centralized router and distributed router.15:28
SwamiBut there may be some complications to it.15:29
SwamiSo for the North-South proposal2 in the google doc, we do have the EG added to the router inbetween the External network and the routers.15:30
*** IlyaE has joined #openstack-meeting-alt15:31
SwamiIn order to add the EG, the tenant need to run an API or cli command to configure the EG and attach it to the external net.15:31
SwamiBut it is slightly different than the current approach.15:32
*** sarob has quit IRC15:32
SwamiSo when we set a gateway to the router, today we only provide a external net id to the router, but in this proposal we might have to pass the EG id instead of the external net id.15:33
SwamiEach EG will be associated with an External net id.15:33
SwamiSo we were planning to add two new API to address this issue. "distributed-router-gateway-set", and "distributed-router-gateway-create".15:34
hemanthraviswami: will go through this in  the gdoc and comment if any15:34
Swamihemathravi:thanks15:35
SwamiI will also update the google doc with the CLI command proposal.15:35
Swamihemanthravi: sorry for ending the monday meeting quick. I need to run to another internal meeting, that's the reason15:36
hemanthraviswami: will catch up later15:37
Swamiok thanks15:37
*** demorris has joined #openstack-meeting-alt15:38
SwamiAlso the "distributed-router-gateway-set" command will accept a "list" or routers, Because there may be multiple routers associated with a single EG.15:38
SwamiSylvain had a proposal for the north-south, as Edge L3 and centralized L3, I was not sure how he was planning to distinguish between the two. I will have  a chat with him and update it.15:40
*** heyongli has quit IRC15:41
*** igormarnat_ has quit IRC15:41
*** igormarnat has joined #openstack-meeting-alt15:42
SwamiNow I do have some concerns towards the new API, will that be acceptable by the community or their expectation might be not to change anything from the current API perspective for the routers.15:42
SwamiIf anyone else have any ideas, please send me your comments.15:44
*** devkulkarni has joined #openstack-meeting-alt15:44
hemanthraviIf you go the config.ini option, will the APIs/cmds be the same as the current router15:45
Swamihemanthravi: Even if we go with the config.ini option, the current proposal to split the EG from the router will create some new commands.15:46
SwamiMeaning we need to include the two new commands shown above, or else modify one existing command for the "router-gateway-set" to accept "EGs" as argument and also modify it to accept a list of routers.15:47
Swami#topic services15:50
*** openstack changes topic to "services (Meeting topic: Distributed Virtual Router)"15:50
SwamiThe last topic would be the services.15:50
Swamiwe may have to consider our design to accomodate services. Certain services are distributable but certain services need to be centralized.15:50
SwamiWe may have to configure routers as service router and non service routers.15:52
SwamiService routers only should handle the services.15:52
SwamiStill more discussion need to happen in this area.15:52
Swami#topic open discussion15:53
*** openstack changes topic to "open discussion (Meeting topic: Distributed Virtual Router)"15:53
hemanthraviswami: should the distributed nature of the service be left to the service api/impl15:54
SwamiI will keep investigating the options and will also talk to sylvain about his proposal and priorities. He mentioned that he already discussed with Mark McClain about the roadmap and priorities15:54
*** julim has quit IRC15:54
hemanthravisimilar to how the router is being distributed15:54
*** coolsvap has joined #openstack-meeting-alt15:54
SwamiThe problem there is a tenant will not want to distribute the VPN feature. Since it is a singleton function15:55
*** devkulkarni has quit IRC15:55
*** BrianB_ has joined #openstack-meeting-alt15:56
SwamiYes it is possible that we can deligate the service work to the service team, but since it is currently tightly tied to the L3 agent, it should be addressed, If the service framework has the service insertion and service chaining framework nail down, then we can concentrate just on the L3.15:56
SwamiOk, I think we are at the last minute.15:57
*** banix has joined #openstack-meeting-alt15:57
SwamiThanks for attending the meeting. See you all next Monday. If you have any questions please feel free to shoot me an email.15:57
*** rcurran has joined #openstack-meeting-alt15:58
Swamibye15:58
Swami#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Wed Dec 11 15:58:10 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2013/distributed_virtual_router.2013-12-11-15.08.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2013/distributed_virtual_router.2013-12-11-15.08.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2013/distributed_virtual_router.2013-12-11-15.08.log.html15:58
*** devkulkarni has joined #openstack-meeting-alt15:59
asadoughihi15:59
rkukurahi ml2'ers!16:00
rcurranhi16:00
*** mestery has quit IRC16:00
banixhi16:00
rkukuramestery: I see you may be online - still want me to chair?16:01
asadoughirkukura: not online16:01
rkukura#startmeeting networking_ml216:01
openstackMeeting started Wed Dec 11 16:01:54 2013 UTC and is due to finish in 60 minutes.  The chair is rkukura. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:01
openstackThe meeting name has been set to 'networking_ml2'16:01
rkukura#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda16:02
rkukura#topic Action Items From Last Week16:02
*** openstack changes topic to "Action Items From Last Week (Meeting topic: networking_ml2)"16:02
*** demorris has quit IRC16:03
rkukuraI had the action item to move rcurrans discussion to the email list. He beat me to it!16:03
rkukuraWe'll cover that a bit later16:04
rcurranyeah sorry about that but i'd really like to close on this issue16:04
*** Sukhdev has joined #openstack-meeting-alt16:04
rkukurarcurran: Lets try to do that today16:05
*** SergeyLukjanov has quit IRC16:05
*** NikitaKonovalov has quit IRC16:05
rkukuramestery had an action to find a volunteer to verify/expand ml2 unit test coverage16:05
rkukuraIs anyone aware of any progress on that?16:05
*** sadasu has joined #openstack-meeting-alt16:06
rkukuraWould anyone like to volunteer to run the tox coverage tool on master and report a summary of where work is needed in ml2 coverage via email and/or next week's meeting?16:07
*** demorris has joined #openstack-meeting-alt16:08
rcurrani can look into it .... haven't used it yet16:08
rcurranbut others have here at cisco16:08
asadoughirkukura: tox -e cover neutron.tests.unit.ml2?16:08
SukhdevI have run tox several times - but, wonder how do you identify what is missing>16:09
rkukuraasadoughi: That's what I recall doing a while back16:09
asadoughiSukhdev: gives you a line coverage report16:09
asadoughirkukura: i'll do it16:09
rkukura#action asadoughi to run the tox coverage tool on master and report a summary of where work is needed in ml2 coverage via email and/or next week's meeting16:10
*** Swami has quit IRC16:10
rkukurarcurran: Feel free to collaborate with asadoughi on that action, but hopefully there will be unblocked on the port unbind/delete stuff16:11
rkukuramestery also had an action to start an etherpad for multi-node ml2 tempest testing16:11
rcurranok, already know that there will be issues w/ the cisco nexus md16:11
rkukuraDo we know if that has been created?16:12
matrohonthere a link on the agenda16:12
*** brents has joined #openstack-meeting-alt16:12
rkukuramatrohon: Thanks. I had seen that, but forgot16:12
matrohonbut multi-node part is not filled16:12
rkukura#link https://etherpad.openstack.org/p/multi-node-neutron-tempest16:13
*** jjmb has quit IRC16:13
*** safchain has joined #openstack-meeting-alt16:14
rkukuraI started looking into how my employer's internal multi-node OpenStack CI testing is done, and will add whatever I find to the etherpad. Its based mainly on packages installed by packstack rather than devstack, but is integrated with jenkins.16:14
rkukuralast action from last week was mestery organizing a meeting around multi-node tempest testing and 3rd party testing16:15
*** jcooley_ has joined #openstack-meeting-alt16:15
rkukuraI've seen emails on this, and believe a meeting is scheduled.for tomorrow16:16
matrohonit was on the mailing list?16:17
rkukuraIt sounds like the agenda covers multi-node testing internal to OpenStack jenkins as well as 3rd party, so I'd encourage all to attend.16:17
rkukuraThe discussion of the meeting was on openstack-dev with the [neutron] tag16:17
*** ozstacker has quit IRC16:17
asadoughimatrohon: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021772.html16:17
*** s3wong has joined #openstack-meeting-alt16:17
rkukuraasadoughi: Thanks16:18
matrohonthanks, i missed it16:18
rkukuraAnything else on previous action items?16:18
*** ozstacker has joined #openstack-meeting-alt16:19
Sukhdevi missed it as well. thanks for sharing the info16:20
SukhdevI have a question on the third party testing -16:20
*** jcooley_ has quit IRC16:20
rkukuraSukhdev: sure16:20
SukhdevAre we testing every patchset-created? regardless of its impact?16:21
Sukhdevor patchset-merged only?16:21
rkukuraSukhdev: I think the intent was for the reports to trigger on proposed patches so the results could be considered in the review16:22
banixIt can't be patchset-merged; need to vote on the patch.16:22
matrohonthere has been a discussion about that on the ML16:23
SukhdevAh OK - thanks for clarification16:23
*** doude has joined #openstack-meeting-alt16:23
rkukuraSukhdev: I asked the same thing last week16:23
rkukuraI think there has been email regarding triggering the 3rd party tests16:23
rkukuraI recall someone saying nova 3rd party tests run on all nova patches, not filtered to changes to the driver16:24
banixI would think a 3rd party site can be setup for patches on a particular directory ?16:24
SukhdevI saw one email, it did not really clarify which triggers to use - I was concerned about the amount of traffic and wanted to design the back-end accordingly16:24
*** julim has joined #openstack-meeting-alt16:25
banixA 3rd party from a given company may be used to only vote on the corresponding plugin16:25
banixThat is my understanding; may be wrong.16:25
Sukhdev<rkukura>: I saw that email - and it concerned me about the traffic it will generate16:26
rkukuraSeems some sort of filtering will likely be needed.16:26
rkukuraThis seems like a topic for tomorrow's meeting.16:26
banixAssuming that the 3rd party site may need to use the 3rd party controller not available to others.16:26
rkukurabanix: Exactly - that may be a very scarce resource, and multi-node tests are likely to take longer to run.16:27
*** shivh has joined #openstack-meeting-alt16:27
rkukuraLets move on, and cover the testing in tomorrow's meeting, since its not really specific to ML2 drivers16:27
*** boris-42 has joined #openstack-meeting-alt16:28
*** akuznetsov has quit IRC16:28
*** jcoufal has quit IRC16:28
rkukuraThe agenda lists the ovs-firewall-driver development discussion, but I'd also like to cover ZangMingJie's TypeDriver patch and rcurran's MechanismDriver discussion16:29
rkukuraWho wants to kick off the ovs-firewall-driver discussion?16:30
rkukura#topic ovs-firewall-driver16:30
*** openstack changes topic to "ovs-firewall-driver (Meeting topic: networking_ml2)"16:30
asadoughiok16:30
asadoughiso i outlined what iwanted to talk about on https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_Dec_11.2C_201316:30
asadoughifirst i wanted to clarify purpose of the blueprint to make sure we're all on the same page16:31
rkukuraasadoughi: Good idea16:31
asadoughii'll also update the blueprint page with the following statement16:31
*** venkatesh has joined #openstack-meeting-alt16:31
*** mozawa has quit IRC16:31
asadoughiTo support the security groups extension in the OVS neutron agent through OVS flows using the existing OVS library with feature parity to the existing iptables-based implementations. In Icehouse, the existing openvswitch plugin is being deprecated, so the blueprint is compatible with the ML2 plugin with the openvswitch mechanism driver.16:31
asadoughiComments? Questions?16:31
*** cody-somerville has joined #openstack-meeting-alt16:32
*** cody-somerville has quit IRC16:32
*** cody-somerville has joined #openstack-meeting-alt16:32
rkukuraasadoughi: Nicely scoped!16:32
matrohondid you review the patch from  nachi :16:32
matrohonhttps://review.openstack.org/#/c/21946/16:32
asadoughimatrohon: not yet. i was asking for comments and questions on the purpose statement16:33
matrohonbecause it's quite the same topic, and maybe a good idea woulld be to let the firewall driver to implement the security group extension16:33
*** jcooley_ has joined #openstack-meeting-alt16:33
rkukuramatrohon: Lets see if we can get consensus about ovs-firewall-driver, then consider that in review nachi's patch16:34
hemanthraviasadoughi: will the fw impl be stateful like the iptables impl16:34
asadoughihemanthravi: good segue. that's my next mini-topic16:35
*** sacharya has joined #openstack-meeting-alt16:35
asadoughiwhich is openvswitch statelessness and security groups frontend API and DB16:35
*** pcm_ has joined #openstack-meeting-alt16:35
asadoughiso openvswitch is stateless in that it doesn't keep track of both sides of one connection16:35
*** ryu25 has joined #openstack-meeting-alt16:35
asadoughiso listed in this etherpad https://etherpad.openstack.org/p/ovs-firewall-driver-stateless-2 are four flows of two types of connections16:35
*** igormarnat has quit IRC16:36
asadoughiso, for openvswitch we'll need one security group rule per flow instead of one rule per connection16:37
asadoughithis will require changes to the security groups frontend api and additional values to the db16:38
*** venkatesh has quit IRC16:38
asadoughithe rpc api is already compatible with this possibility, thus does not need to be changed16:38
*** colinmcnamara has joined #openstack-meeting-alt16:38
*** colinmcn_ has joined #openstack-meeting-alt16:38
asadoughii was referred to openvswitch/nicira-ext.h NXAST_LEARN for a possible, magical stateful unicorn but i haven't grokked it yet16:39
rkukuraasadoughi: I'm OK with adding to the API, but am concerned about behavioural parity for the existing API16:39
*** SushilKM has joined #openstack-meeting-alt16:39
asadoughirkukura: ok16:39
rkukuraMaybe this is a silly question, but would the typical existing SG rule allowing TCP port 22 from everywhere still be sufficient, or would additional rules be needed with this driver?16:40
asadoughino, it's a good question16:41
asadoughianswer is it depends16:41
rkukuraThis is reminding my of configuring linux firewalls before iptables connection tracking16:42
asadoughiso, if you allow all egress adding ingress on 22 will work as expected16:42
asadoughirkukura: yeah, it will be similar i suppose16:42
rkukuraI seem to recall setting up firewalls to reject only SYN packets from TCP ports that were not open, but allowing packets in both directions for existing connections16:43
hemanthravisome possible security-holes will be to allow egress pkts to any port form 2216:43
asadoughione that will not be the same: if you allow all egress, for example instance ssh client to remote ssh server, you'll have to still add the reverse flow of remote ssh server serving to instance ssh client16:43
hemanthraviand to allow egress pkts after a connection is closed16:44
*** igormarnat has joined #openstack-meeting-alt16:44
ryu25I don't want to interrupt the work that has already started, and maybe this is a crazy idea, but how do you all feel about implementing security group as a service type framework (just like L3 router service)?16:44
asadoughiryu25: FWaaS already exists16:45
matrohonhow does your api evolution will behave with ipablesfirewalldriver?16:45
rkukuraryu25: I was hoping this new ovs-firewall-driver would be purely a new driver in the L2 agent, not a new API/DB/RPC in the server16:46
asadoughimatrohon: i don't understand your question. eventually when ovs has connection tracking it will be behaviourally one-to-one16:46
asadoughimatrohon: i think statelessness will be a first step, so when statefulness is implemented in ovs neutron users can rejoice16:46
asadoughi..in not having to wait for an implementation16:47
matrohonmy concern is if you introduce an API evolution, it must compatible with other existing driver16:47
asadoughimatrohon: oh, are you talking about the security groups api change as evolution?16:48
matrohonasadoughi: yes16:48
asadoughimatrohon: so the iptables firewall driver already handles source-port-min source-port-max as expected in the rpc api16:48
asadoughimatrohon: so only the frontend api has to change16:48
asadoughimatrohon: and db16:48
matrohonasadoughi: oh ok, sorry about that16:49
rkukuraSome good discussion here, but we should reserve a couple minutes for each of the other topics as well. Are there any other meetings scheduled regarding ovs-firewall-driver?16:50
ryu25rkukura:  understood.  I guess what I'm wondering is, if a vendor wants to migrate to ML2 and wants to implement the SG features without relying on the agents running on the compute hosts, how could it achieve it?16:50
asadoughinothing with high priority to discuss. see more on the agenda page. we could start another meeting or more mailing list discussions if that's worthy?16:51
*** SushilKM has quit IRC16:51
*** rongze_ has joined #openstack-meeting-alt16:51
rkukuraryu25: I would hope that's where nachi's VIF patch ties in - so the bound mechanism driver can influence what happens on the compute node16:51
rkukuraif the bound MD handles security groups itself without an L2 agent, no RPC-based driver would be used, right?16:52
ryu25right, no RPC needed16:52
*** rongze__ has joined #openstack-meeting-alt16:52
*** rongze has quit IRC16:52
ryu25ok I will have to look into that proposal to get better understanding16:53
rkukuraSeems we need to continue discussion of SGs with ML2 - do we need a separate meeting, or just use the mailing list?16:53
asadoughirkukura: i can rehash my agenda on the mailing list to coordinate an additional irc meeting16:54
rkukuraasadoughi: Sounds good16:54
rkukura#action asadoughi to discuss ovs-firewall-driver on email list and schedule IRC meeting on ML2+SG16:54
rkukura#topic port unbindi/delete segment info availability16:55
*** openstack changes topic to "port unbindi/delete segment info availability (Meeting topic: networking_ml2)"16:55
rkukurarcurran: Where do we stand on this?16:55
*** SushilKM has joined #openstack-meeting-alt16:56
*** mestery has joined #openstack-meeting-alt16:56
*** rongze_ has quit IRC16:56
rcurranif you don't mind i think that i can come up w/ a code change for the crux of the issue and put out for a private review (bobk, kylem, l2pop, arista engs) and resolve this quicker that way16:56
shivhplease add brocade in the mix. thx16:57
rkukurarcurran: Are you leaning towards one of the options discussed in your email?16:57
matrohonplease add me too16:57
rcurranyes, i still believe that the crux of the issue is that our deletes are in the wrong order16:57
Sukhdevrcurran: I started the reply to your email, got distracted and never came back to it...sorry16:57
rkukuraWe've only got two minutes left16:58
rcurrancreate_port_postcommit() is the last call in create_port() therefore it has the most (or could) dependencies; therefore it should be one of the first methods called on delete16:58
*** SushilKM has quit IRC16:58
*** SushilKM has joined #openstack-meeting-alt16:59
HenryGrcurran, looks like it might be better to push the review and mark it WIP, rather than cherry-pick who gets to see it16:59
rkukuraLets follwup on rcurran's email thread ASAP, and any kind of WIP patch to review would be great. I don't see a need to necessarily make it private - WIP might be sufficient16:59
rkukuraZangMingJie: Any update on the TypeDriver refactor?16:59
rcurranyeah, sorry wrong terminology16:59
rkukura#topic open discussion17:00
*** openstack changes topic to "open discussion (Meeting topic: networking_ml2)"17:00
rkukuraAnything else anyone?17:00
shivhZang's discussion on ML?17:00
doudeWhat about the summit discussion ML2 RPC Handling ? https://docs.google.com/document/d/1ZHb2zzPmkSOpM6PR8M9sx2SJOJPHblaP5eVXHr5zOFg/edit#heading=h.fybml652slvq17:00
rkukurashivh: Yes - I posted a followup last night.17:01
shivhwill take a look. thx17:01
rkukurashivh: Might not be tagged [ml2]17:01
rkukuradoude: Lets get that on the agenda for next week17:01
rkukuraNeed to wrap up - thanks everyone!17:01
douderkukura: k17:01
rkukura#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:02
openstackMeeting ended Wed Dec 11 17:01:58 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-12-11-16.01.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-12-11-16.01.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-12-11-16.01.log.html17:02
shivhbye all17:02
asadoughi\o17:02
Sukhdevbye17:02
ryu25bye!17:02
matrohonbye17:02
*** shivh has quit IRC17:04
*** HenryG has quit IRC17:04
*** jjmb has joined #openstack-meeting-alt17:04
*** markwash has joined #openstack-meeting-alt17:05
*** HenryG has joined #openstack-meeting-alt17:05
*** hemanthravi has quit IRC17:06
*** doude has left #openstack-meeting-alt17:06
*** electrichead has left #openstack-meeting-alt17:06
*** jjmb has quit IRC17:08
*** slagle has quit IRC17:09
*** igormarnat has quit IRC17:09
*** jjmb has joined #openstack-meeting-alt17:09
*** rongze__ has quit IRC17:11
*** safchain has quit IRC17:11
*** rcurran has quit IRC17:12
*** akuznetsov has joined #openstack-meeting-alt17:13
*** resker has joined #openstack-meeting-alt17:14
*** esker has quit IRC17:15
*** dougshelley66 has joined #openstack-meeting-alt17:15
*** rongze has joined #openstack-meeting-alt17:17
*** aignatov has quit IRC17:18
*** SergeyLukjanov has joined #openstack-meeting-alt17:20
*** SushilKM has quit IRC17:28
*** ryu25 has quit IRC17:33
*** alazarev has joined #openstack-meeting-alt17:35
*** brents has quit IRC17:35
*** coolsvap has quit IRC17:37
*** akuznetsov has quit IRC17:39
*** IlyaE has quit IRC17:43
*** datsun180b has joined #openstack-meeting-alt17:45
*** brents has joined #openstack-meeting-alt17:45
*** joel_c has left #openstack-meeting-alt17:51
*** alazarev has quit IRC17:51
*** vkmc has quit IRC17:54
*** SushilKM has joined #openstack-meeting-alt17:56
*** SlickNik has joined #openstack-meeting-alt17:56
*** derekh has quit IRC17:57
*** alazarev has joined #openstack-meeting-alt17:57
*** alazarev has quit IRC17:59
*** jcru has joined #openstack-meeting-alt17:59
hub_capready for some meeting fun!17:59
*** robertmyers has joined #openstack-meeting-alt17:59
*** grapex has joined #openstack-meeting-alt17:59
*** beyounn has joined #openstack-meeting-alt18:00
hub_cap#startmeeting trove18:00
openstackMeeting started Wed Dec 11 18:00:27 2013 UTC and is due to finish in 60 minutes.  The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: trove)"18:00
openstackThe meeting name has been set to 'trove'18:00
SlickNikhere18:00
pdmarspresent18:00
datsun180bhello18:00
*** beyounn has left #openstack-meeting-alt18:00
hub_caphello all18:00
robertmyerso/18:01
*** jjmb has quit IRC18:01
grapexo/18:01
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:01
cp16neto//18:01
kevinconway7o718:01
juiceo/18:01
hub_capso lets start w/ the fun one18:01
*** yisun has joined #openstack-meeting-alt18:01
juice\o\ <ho>18:01
esmuteo/18:02
hub_cap#topic datastore_types before tempest18:02
*** openstack changes topic to "datastore_types before tempest (Meeting topic: trove)"18:02
cp16net<hey> ?18:02
esmutejuice: Doing aerobics?18:02
hub_capjulim: hip hop horray?18:02
hub_capjuice: ^ ^18:02
juiceyup18:02
*** glucas has joined #openstack-meeting-alt18:02
juicehub_cap wins18:02
vipulo/18:02
hub_capjuice: do i win cuz i said it to someone random instead of u?18:02
annashen o/18:02
hub_capok so back to the topic at hand18:03
hub_capi think that we should allow the existing 3 in before we get around to tempest testing18:03
hub_capcassandra, mongo, and redis18:03
cp16net+118:03
hub_capill be running them today and taking a look at all 3 of them to make sure they are quite similar18:03
demorris+118:03
kevinconwayhub_cap: do we just not gate on them?18:03
hub_capid like others to do that as well18:03
*** Sackmann has joined #openstack-meeting-alt18:04
SlickNikSo what about tests for them?18:04
*** devkulkarni has quit IRC18:04
SlickNikDo we gate on them to make sure they're not broken?18:04
*** NehaV has joined #openstack-meeting-alt18:04
hub_capkevinconway: we will once we get tempest tests a-goin18:04
vipulWe do have datastore_types support now, so we could potentially add to our existing gate and spin up the differnt types18:05
vipulit would add time to our builds..18:05
denis_makogono/18:05
hub_capthe risk we run is that something changes that doesnt properly get tested on all our impls18:05
*** cweid has joined #openstack-meeting-alt18:05
cweido/18:05
*** Sukhdev has quit IRC18:05
*** devlaps has joined #openstack-meeting-alt18:06
hub_capvipul: we can parallelise it w/ tempest (honestly we probably could w/ the present stuff too i just not sure we should spend too much time on it now)18:06
kevinconwaywouldn't the new data stores fail the current integration tests though?18:06
kevinconwaywill there be a way to choose tests based on datastore?18:06
datsun180bi don't think the extra test time should be considered as a deal-breaker18:06
denis_makogonwe need image elements asap !18:06
cp16netkevinconway: if you ran *all* tests i'm sure they would because some tests do not apply to all datastores18:07
hub_capkevinconway: w/ the tempest tests we will make sure teh different datatypes dont run all the same tests18:07
denis_makogoncp16net, kevinconway that why we have test groups18:07
esmuteif resource/time is a factor, we can just gate on one datastore type... maybe one for sql and one for no-sql18:07
hub_capdenis_makogon: SlickNik is working on that18:07
cp16netdenis_makogon: yup18:07
denis_makogonSlickNik, any statuses on that ?18:07
hub_capdenis_makogon: thats not what we are talking about right now :)18:08
hub_capthere is a topic for that later in the meeting18:08
denis_makogonsorry18:08
kevinconwayso if we merge the new types would we release them before the tempests tests are going?18:08
hub_capnp18:08
SlickNikdenis_makogon: still working on cleaning up the elements before moving to tripleo18:08
SlickNikdenis_makogon: you can get started writing the tempest tests, though.18:08
*** cody-somerville has quit IRC18:08
hub_capok so, anyone opposed to merging in these impls?18:08
SlickNikdenis_makogon: Shouldn't be a blocker until the final integration point.18:08
kevinconwayhub_cap: ^^ question18:09
denis_makogonSlickNik, Dmitriy Iakunchikov already doing that18:09
hub_capkevinconway: go head18:09
kevinconwaykevinconway: so if we merge the new types would we release them before the tempests tests are going?18:09
SlickNikdenis_makogon: any update on that?18:09
denis_makogonSlickNik, lets talk after meeting, ok ?18:09
grapexkevinconway: What do you mean by release?18:09
SlickNikWhat's his IRC handle? I can ask him too.18:09
grapexI think having them in as not 100% supported features is ok18:09
SlickNiksure.18:09
denis_makogonSlickNik, he's out18:09
grapexthe alternative is to have them decaying in reviews forever18:10
kevinconwaygrapex: as in would they go out in an icehouse release before we tested them18:10
hub_capkevinconway: define release them18:10
grapexkevinconway: Yes, I think we should- just tell people not to use them18:10
vipulthey are released when they land basically18:10
vipuluse at your own risk18:10
datsun180b"We stand behind the completeness and correctness of this feature--just don't use it!" what?18:10
hub_capmerged code != fully baked, supported code i think18:10
denis_makogoncould we add reddwarf job into trove ?18:10
hub_capi dont think its necessary sicne its just a subset of the functionality denis_makogon18:11
grapexdatsun180b: Well, part of this is happening because we do have tests, but we don't want to add to them for these features since we're trying to get Tempest up and running first.18:11
hub_capwe should push forward on tempest and the tasks it takes to get it running18:11
denis_makogonhub_cap, but we'll be able to modify it18:11
datsun180bgotcha, i'm on the right page now18:11
vipulso as part of each Datastore review, we should be requiring that the README be updated18:11
vipuli don't know where else we document this sort of stuff18:12
denis_makogonvipul, Wiki ?18:12
*** akuznetsov has joined #openstack-meeting-alt18:12
SlickNikAlso, we need to make sure that they _work_ at the very least.18:12
denis_makogonSlickNik, hup_cap testing them18:12
hub_capmaybe we need a functionality matrix18:12
hub_capon the wiki somewhere18:12
cp16netthats a good idea18:13
denis_makogonhub_cap, elaborate18:13
cp16netshowing what is supported for each datastore18:13
demorrishub_cap: +1 to functionaility matrix18:13
denis_makogoncp16net, oh, yes, agreed +10050018:13
demorrisas well as well defined API docs that detail it18:13
demorris:)18:13
cp16netand showing what is not fully supported yet18:13
demorrisanne gentle and mike a. are ready to help there as soon as you are18:14
denis_makogondemorris, also how to manage trove to run it18:14
vipulkinda like https://wiki.openstack.org/wiki/HypervisorSupportMatrix18:14
denis_makogonvipul, +118:14
demorriscorrect, and operators guide would be good18:14
SlickNikvipul: agreed.18:14
cp16netyup18:14
*** olkonami has joined #openstack-meeting-alt18:15
denis_makogon#action Functional Matrix for Datastores18:15
*** slagle has joined #openstack-meeting-alt18:15
grapexOh man... updating a matrix like that seems pretty gross.18:15
grapexWhy not just say "as of Icehouse, no assurances are given for the non-MySQL datastore types"18:15
grapexthen make sure we have tests for all the datastore types after that18:15
vipuleven then some things wont' be supported long term right18:16
grapexwritten in Tempest or whatever18:16
vipulusers? backups?18:16
denis_makogongrapex, sound like they are not working, but we let it land to codebase18:16
grapexvipul: Could you go into some more detail on that?18:16
vipulgrapex: the User API for redis will never work18:17
datsun180blike hub_cap said before, merged code isn't necessarily a release in itself18:17
vipulgrapex: some nosql thing may never support taking backups18:17
datsun180bnot even a nightly or something like that18:17
SlickNikSo, let me ask you a question. Are there certain sub-teams specifically working on certain implementations? The reason I ask is because, if we're allowing these implementations without tests (or docs), I want to have at least someone responsible for following through on writing these.18:17
denis_makogonvipul, same with users in Cassandra18:17
grapexvipul: I see what you mean18:17
datsun180bwell that's an extension anyway18:18
SlickNikI'd hate to have code/doc in trove for an impl that's half baked and not fully tested long-tern.18:18
denis_makogonSlickNik, submitter is a guy who response for docs18:18
*** dark_knight_ita has joined #openstack-meeting-alt18:18
grapexvipul: Then I think for the different types, it makes sense to say something will never be supported.18:18
hub_capSlickNik: if the code is not maintained, its removed18:18
hub_capthats always been my stance18:18
grapexOk... n/m. I agree with you on that vipul.18:18
grapexI thought we were concocting a matrix to list test IOUs.18:19
hub_capn+1, if no one ponies up to "fix"  issues, then it doesnt need to stay in the code18:19
vipulgrapex: sure, i just think the support matrix woudl be good for that18:19
denis_makogonhub_cap, vipul +118:19
hub_capok so, this i taking a while18:19
hub_cap*is18:19
hub_capdo we feel like we can move on now? is there more to this besides, yes, lets do this18:19
hub_capand some docs18:19
vipulok who's doing the matrix18:19
SlickNikhub_cap: okay, if that's the stance, I'm okay with it.18:19
*** sadasu has quit IRC18:19
hub_capill start the matrix today vipul w/ just mysql18:20
denis_makogonhub_cap, nice =)18:20
denis_makogonhub_cap, <318:20
hub_capand the maintainers of the code for each service can add what they have18:20
vipulsounds good18:20
denis_makogonsound like perfect plan18:20
hub_capwe will have to make sure thats updated each time things are added to the code18:20
hub_capok moving on18:20
grapexhub_cap: I wonder if we can generate the matrix from the code somehow.18:20
denis_makogongrapex, that would be not easy ...18:21
hub_cap#topic mount_point and storage directory dependency18:21
*** openstack changes topic to "mount_point and storage directory dependency (Meeting topic: trove)"18:21
datsun180buntil then the wiki better state that no one can be told what the matrix is18:21
hub_capgrapex: im not that worried about it  :)18:21
denis_makogonSlickNik, it's our turn18:21
hub_capgo go go guys18:21
hub_capput up your #links too :)18:21
grapexdatsun180b: No one can be told what the working feature matrix is... they have to run the code for themselves.18:21
SlickNikOkay, so this one is based on a discussion I was having with denis_makogon18:21
denis_makogon#link https://review.openstack.org/#/c/57189/18:22
SlickNik#link https://review.openstack.org/#/c/5718918:22
SlickNikfor context.18:22
denis_makogonwe need to brink dependency between mount_point and datastore18:22
denis_makogoni mean database data_dir18:22
SlickNikI'm not sure I like forcing the mount_point and the data_dir to be the same, and this might limit some configurations (where data_dir is not the mount point, but a directory contained within it for example).18:22
denis_makogonfor now trove allows to make next misconfiguration18:22
vipulwhen do we start taking a stance on backwards-incompatible changes to the RPC api18:23
denis_makogonmount_point = /mnt/ , data_dir = /var/lib/mysql18:23
SlickNikvipul: That's another reason I don't like this change.18:23
SlickNikyou might want to store both the database, and the binlogs on the volume for instance.18:24
grapexvipul SlickNik: Are you referring to the RPC API or the trove/guestagent/api methods?18:24
denis_makogonthat is why i suggested ikhudoshyn to make such patch18:24
vipulgrapex: trove/guestagent/aip18:24
denis_makogonwhich retrieves data_dir from my.cnf and mounts volume into it18:24
vipulmaybe we can wait for that conversation grapex18:24
vipullet denis_makogon and SlickNik do their thing18:25
grapexvipul SlickNik: I say we keep allowing it to change wily-nilly until the reference guest moves to its own repo.18:25
* grapex evil laugh18:25
denis_makogoni suggest to make strict dependency between mount point and database data directory18:25
SlickNikAnother reason I don't like this change is because it would mean that the guestagent now has to understand how to parse every datastore config file, and know what value corresponds to the equivalent of a mount_point.18:25
denis_makogonSlickNik, it's already knows how to do that18:26
denis_makogonexample: admin password18:26
grapexvipul SlickNik: No, I guess it could cause some pain. We should probably discuss this soon- what I'd like to see is for guestagent/api.py to support calling older versions of the agent within reason. There should be an expectation that the agents can eventually update themselves though, so for instance they'd never be more than a week or so out of date.18:26
SlickNikfor mysql it does. What's the corresponding data_dir value for redis/cassandra?18:26
grapexSlickNik: In theory, the data_dir for redis and caddandra could come from config values.18:26
denis_makogonSlickNik, it's very easy18:27
cweiddata_dir in redis is currently hard coded to /var/lib/redis18:27
grapexSlickNik: Though I agree the data dir and mount directory should not have to be the same.18:27
cp16netit doesnt parse the config file it just appends18:27
cp16nettheres a differnce18:27
denis_makogonfor cassandra /var/lib/cassandra/data18:27
vipuldoes every datastore have a data_dir setting?18:27
denis_makogonvipul, yes18:27
denis_makogonvipul, everyone has18:27
grapexMy point though is that the app, which has the get_data_dir() method, could have subclasses for different datastore types.18:27
denis_makogoncp16net, not only appends18:27
denis_makogoncp16net, somewhere in code it reads admin pass from my.cnf18:28
vipulyea i don't think you should limit what you mount to18:28
vipulyou may have >1 things you want to mount in the future as well18:28
denis_makogonvipul, but it need to be chained18:28
grapexSounds like everyone agrees that mount_point doesn't necessarily have to be the same as the data dir, right?18:28
vipulgrapex: +118:28
*** amcrn has joined #openstack-meeting-alt18:28
hub_caplol in redi sits just called "dir"18:28
SlickNikgrapex: yes, I think  so.18:28
hub_capdir /var/lib/redis18:29
grapexLet's just make a it a config value. Would there be some case where that wouldn't work?18:29
denis_makogonvipul, how to be if mount_point is /dev/null and data_dir = /var/lib/mysql18:29
denis_makogonvipul, try to backup it18:29
vipuldenis_makogon: that's a bad configuration then18:29
denis_makogonvipul, because of bad design18:29
datsun180bi think if you've got enough bullets and point the gun earthward, shooting yourself in the foot is your fault18:29
SlickNikdenis_makogon: That's bad configuration18:29
hub_capSlickNik: vipul do you have a specific reason to have data_dir != mount point?18:29
vipul tha'ts /dev/null as a service18:29
vipulanother datastore we will supoprt18:29
datsun180bvipul: write-only memory. there's an ancient joke RFC for it18:30
*** nadya has joined #openstack-meeting-alt18:30
cp16netthats the fastest18:30
cp16netand sharded18:30
*** nadya is now known as Guest6481618:30
denis_makogoni dont like whole idea of keeping 2 values for writing data18:30
hub_capif there is no good reason to have a different directory right now then im not sure why we'd keep 2 values18:30
denis_makogoni see a wayout - mysql/config.template : {{mount_point}}/data_dir18:31
SlickNikhub_cap: 1. you lose the flexibility of possibly storing > 1 type of object on your volume.18:31
denis_makogonanother: reading from conf file18:31
SlickNik(for example if you want your volume to store databases as well as something like binlogs, for example)18:31
hub_capbut do we ever watn to do that SlickNik ?18:31
denis_makogonSlickNik, {{mount_point}}/data_dir18:31
denis_makogonroot directory18:32
vipulhub_cap: I could see potntially trove having a secondary volume for some things that are not data18:32
grapexReal quick question for vipul / SlickNik: When we're talking about "mount_point", are you guys mixing that up with the "data_dir" variable used throughout the backup code too?18:32
SlickNikYes, you probably don't want to store it on the root partition, because it will grow (you might need them for incremental backups say).18:32
denis_makogondata_dir and mount_point __should__ be dependent18:32
grapexBecause previously that "data_dir" var was named "mount_point"18:32
denis_makogonvipul, why do we need more then one volume ??18:32
SlickNikdenis_makogon: They are _dependent_. They are just not the same value.18:32
hub_capya i think thats a fair point SlickNik18:33
denis_makogonSlickNik, now they are not dependent18:33
vipulgrapex: No, i think currently we're consistent that mount piont = data_dir for the most part18:33
vipuli just don't think it's a good limitation to impose18:33
*** imsplitbit has joined #openstack-meeting-alt18:33
imsplitbito/18:34
cp16netwelcome imsplitbit18:34
imsplitbitsorry I'm late18:34
denis_makogontry to run trove with mount_point /var/lib18:34
*** d0ugal has quit IRC18:34
denis_makogonor another way - we need N sections in trove-taskmanager.conf where different datastore will have it's own mount_point18:35
hub_capso i think we can make it optional, to send the value in a conf if it exists18:35
grapexOk- so I'm game to just change line 97 of this review to say "mount_point = some config value" and then replace the proceeding instances of "data_dir" in the prepare function to "mount_point": https://review.openstack.org/#/c/57189/16/trove/guestagent/datastore/mysql/manager.py18:35
grapexWith the exception that before doing a restore18:35
grapexOn line 112, we need to actually pass the _perform_restore function the data_dir, and not the mount_point18:36
hub_capso lets do this, make it optional denis_makogon, if they want to declare a mount_point they can18:36
hub_capand maybe its time we start thinking about putting these things into [cassandra][mysql] sections18:36
denis_makogonhub_cap, so then we need N oslo parameters groups18:36
vipulthe second issue with this patch.. why change the signature of the prepare() API18:37
hub_capvipul: if somethign is not being used...18:37
denis_makogonhub_cap, +118:37
vipulwe need ot have a deprecation strategy or some way to version18:37
SlickNikhub_cap / grapex: I'd be okay with either of your suggestions.18:37
hub_capi know it is sucky for deployment, so i suggest we fix versioned messages18:37
vipulthis doesn't work when you have and old version18:37
denis_makogon#action Start delivering more oslo.config parameters groups18:37
*** colinmcn_ has quit IRC18:38
*** colinmcnamara has quit IRC18:38
hub_capvipul: yup, and i think we need to fix it in production.. iirc rax deals w/ this every deploy too :)18:38
*** simonmcc has quit IRC18:38
SlickNikdenis_makogon: we're still talking about the guest API change, hold your horses.18:38
vipulhub_cap: trove should deal with this.. like every other openstack project is trying to do18:38
vipuldon't just break compatibility18:38
denis_makogonSlickNik, API would be never changed in this case18:38
hub_capvipul: i agree trove should handle it :)18:38
SlickNikdenis_makogon: That patch out there changes the API18:39
denis_makogonSlickNik, i'm talking about multiple oslo groups18:39
hub_capwe cant say "no one can make the code better until we deal w/ versioned messages" and then no one deal w/ versioned messages18:39
denis_makogonhub_cap, agreed18:39
*** nati_ueno has joined #openstack-meeting-alt18:40
*** IlyaE has joined #openstack-meeting-alt18:40
denis_makogonlets do not touch API18:40
denis_makogonlets make inner code better18:40
vipulsure i get that.. but there are ways of doing this w/o breaking compat.. allow the param to be passed in and overridden by guest.conf18:40
SlickNikhub_cap: the question is - do we take breaking changes to the API before we have a method to deal with versioned messages?18:40
hub_capdenis_makogon: the guest api _is_ an api though18:40
*** rkukura has left #openstack-meeting-alt18:40
hub_capSlickNik: weve done it many times before :)18:40
grapexSo I want to point out we've had to deal with breaking changes in the RPC calls for a long time now.18:41
hub_capbut we are really bogged down w/ this18:41
grapexI think we should fix it, but this problem is hardly new.18:41
*** greghill has joined #openstack-meeting-alt18:41
SlickNikAnd felt the pain many times before too. :)18:41
hub_capyes rax deals w/ it every release hahah18:41
datsun180bgosh, when's the last time i broke some rpc calls everywhere, when was it...18:41
*** d0ugal has joined #openstack-meeting-alt18:41
vipulgrapex: not saying it's new.. jsut something we need to start getting better at gating on18:41
imsplitbit+118:41
datsun180bsomething about backing... maybe hiccups? can't recall18:41
hub_capyes but we need someoene to pony up and do the work too18:41
hub_capthat'd be like us not allowing cassandra until tempest hehe18:42
* imsplitbit points at hub_cap 18:42
grapexvipul: Agreed- I just wonder if its a good reason to hold up this particular pull request.18:42
hub_capbut srsly we need to mvoe on18:42
denis_makogonmoving on18:42
hub_capwe will not get thru this meeting hehe18:42
denis_makogonhub_cap, not even once18:42
*** simonmcc has joined #openstack-meeting-alt18:42
*** SushilKM has quit IRC18:42
vipulgrapex: based on what we talke about .. we could probably not break api and get this in with a little rewuire18:42
*** yogesh has joined #openstack-meeting-alt18:42
vipulrewrite18:42
hub_caplets table this until after the meeting is over though vipul grapex SlickNik denis_makogon18:42
vipulok move on18:43
hub_capvipul: in golang?18:43
hub_caprewrite?18:43
hub_cap:)18:43
hub_cap#topic guidestyle18:43
*** openstack changes topic to "guidestyle (Meeting topic: trove)"18:43
hub_capgo denis_makogon18:43
SlickNiksounds good. Let's come back to this later.18:43
denis_makogon#link https://review.openstack.org/#/c/60277/18:43
denis_makogon#link https://review.openstack.org/#/c/60276/18:43
denis_makogonwe need to deal with this, both18:43
grapexI'm cool with it18:44
denis_makogon__init__.py - hacking already had rules for that18:44
*** aignatov has joined #openstack-meeting-alt18:44
vipulthe vim guys might freak18:44
hub_capdenis_makogon: im ok w this too, the openstack mailing list has talked about this too18:44
kevinconwayi vote we add jslint validation to our code18:44
denis_makogon#vim - reason, i can edit code without vim, why do i need #vim lines in code18:44
datsun180bvipul: i'm a vim guy, idgaf18:44
hub_capvipul: only if they code in goofy vim spacing18:44
vipulok then!18:44
datsun180bi have my own settings18:44
denis_makogon#link http://openstack-dev.markmail.org/search/?q=modeline#query:modeline+page:1+mid:2a55it3usuqsfsif+state:results18:44
imsplitbitdatsun180b: you're doing it wrong18:45
hub_capok good moving on then!18:45
*** rsblendido has quit IRC18:45
imsplitbitgo go go18:45
hub_capno emacs vs vim imsplitbit18:45
kevinconwayjslint will hurt your feelings18:45
SlickNikI'm good18:45
imsplitbit:)18:45
imsplitbitI wasn't gonna start18:45
hub_cap#topic updating requirements18:45
*** openstack changes topic to "updating requirements (Meeting topic: trove)"18:45
hub_capimsplitbit: ;)18:45
datsun180bimsplitbit: i don't judge. i leave that for vengeful Bram Moolenaar18:45
imsplitbitjust a friendly jab18:45
denis_makogonmoving one18:45
hub_capdenis_makogon: gogogogo18:45
*** yidclare has joined #openstack-meeting-alt18:45
*** rossella_s has quit IRC18:45
denis_makogon#link https://bugs.launchpad.net/trove/+bug/125993818:45
grapexI feel like this bug is too general18:45
denis_makogonwhat are you think about dropping mockito out ?18:45
imsplitbit+10000000000018:46
amcrn+1 w/ grapex18:46
grapexI don't know if something like this should be a bug.18:46
hub_capso lets first talk about dropping mockito18:46
grapexI marked it as incomplete18:46
hub_capthats a simple one, lets drop it18:46
grapexhub_cap: Ok18:46
datsun180b+four18:46
robertmyers+118:46
cweid+500018:46
cp16net+118:46
denis_makogongrapex, trove unit tests have more than 1000 incorrect assertions18:46
hub_cap+infinity18:46
cp16net+18:46
*** igormarnat_ has joined #openstack-meeting-alt18:46
datsun180b'incorrect'18:46
SlickNiklol18:46
hub_capdenis_makogon: ?18:46
imsplitbitdo we have an official replacement?18:46
robertmyersdenis_makogon: How so?18:46
cweidimsplitbit: Mock?18:46
grapexdenis_makogon: Can you give some examples?18:46
imsplitbitmox?18:46
denis_makogonmox, mock18:46
robertmyersno mox18:47
*** gokrokve has quit IRC18:47
SlickNikdenis_makogon: no moc18:47
esmutelol that was fast18:47
robertmyersyes mock18:47
SlickNikmox*18:47
juiceplease let me take this up with lifeless and openstack18:47
grapexI propose we write a Trove specific mock framework and call it Taquito.18:47
imsplitbitba dum dum18:47
kevinconwaygrapex: i'll start on the bash code18:47
vipuljuice: do it!18:47
juiceyum18:47
denis_makogon#link https://github.com/openstack/trove/search?q=assertEqual&ref=cmdform - huge part of all assertions are wrong18:47
esmutejuice: Our mockito evangelist18:48
juiceindeed18:48
SlickNikI say we table the mocking framework discussion until juice has a conversation with lifeless / ML18:48
imsplitbitwhy?18:48
denis_makogonSlickNik, agreed18:48
grapexSlickNik: Sure, agreed.18:48
denis_makogonthat is why i putted it into agenda18:48
* imsplitbit is curious18:48
datsun180bwhat's wrong with testcase.assertEqual?18:48
grapexI don't get why it matters- how much pain is there really to adding it.18:48
vipulyea i'm confused why these are 'wrong'18:48
denis_makogondatsun180b, incorrect parameters order18:49
juicei personally like the assertThat matchers but I wouldn't go back and change anything18:49
denis_makogonwe should not use Is, KeysEqual, Not etc18:49
datsun180bwhat's the correct form then?18:49
grapexdenis_makogon: I feel like in JUnit the order being wrong could really screw up the error messages18:49
robertmyersdenis_makogon: http://docs.python.org/2/library/unittest.html#unittest.TestCase.assertEqual18:49
grapexbut in Python I feel like if if you mismatch "expected" and "actual" it doesn't affect anything18:50
datsun180bohh it's just expected/actual18:50
denis_makogongrapex, but it's not correct18:50
robertmyersthere is no expected actual18:50
juicejust the error message grapex18:50
grapexrobertmyers: Great find18:50
kevinconwayhow about just use 'assert thing1 == thing2, "ITS NOT THE SAME!!!!"'18:51
denis_makogoni'd like to make call _correct_ assertions18:51
robertmyersdenis_makogon: define correct18:51
cp16netthat doesnt change anything18:51
hub_capdenis_makogon: are you proposing to change assert(a, b) to assert(b, a) ?18:51
grapexI don't know if I want to make a big deal out of this18:51
*** colinmcnamara has joined #openstack-meeting-alt18:51
hub_capin 1000 places?18:51
*** colinmcn_ has joined #openstack-meeting-alt18:51
denis_makogontesttools allow as to use assertIn, assertIs, assertIsInstance18:51
lifelessgrapex: in testtools there is actually expected, observed18:52
SlickNikgrapex: I'm still confused if there's anything to make any sort of deal about.18:52
denis_makogonbut a lot of tests uses assertEqual(type({}), dict)18:52
lifelessgrapex: but as you say, it doesn't really matter for any of the simple equality relations18:52
*** colinmcn_ has quit IRC18:52
datsun180b^^18:52
greghillthis seems like a colossal waste of time to argue about18:52
hub_capok we shoudl move on18:52
*** colinmcnamara has quit IRC18:52
hub_capther is no reason to do that work denis_makogon18:52
hub_capyes to remove mockito18:52
cp16net+118:52
kevinconwaycan we remove all test tools asserts for regular asserts18:52
datsun180bbut i love having three mocking frameworks to juggle18:53
robertmyershub_cap: +118:53
*** brents has quit IRC18:53
hub_cap#topic tempest18:53
*** Guest64816 has quit IRC18:53
*** openstack changes topic to "tempest (Meeting topic: trove)"18:53
grapexkevinconway: We should just use the python assert keyword everywhere18:53
*** colinmcnamara has joined #openstack-meeting-alt18:53
*** colinmcn_ has joined #openstack-meeting-alt18:53
denis_makogonhub_cap, all project fixing incorrect assertions, take a look at heat18:53
hub_capdiakunchikov__: its all you!18:53
grapexIt kind of sucks, but it is more pythnoic18:53
denis_makogonhub_cap, Dima is out18:53
denis_makogoni'm for him18:53
hub_capdenis_makogon: you can sway our opinions if we can see all the other projects doing it18:53
denis_makogonSlickNik, describe, please last status fro image elements18:53
* imsplitbit wonders if all the other projects are waiting for all the other projects to do it18:54
hub_capimsplitbit: i dont have a /slap anymore18:54
imsplitbit:)18:54
hub_capyes SlickNik lets talk status here18:54
hub_capwe have 6 min18:54
datsun180bi'll say it, it seems like it's a really convenient way to widen someone's pie slice and it seems like our contribution efforts would serve trove directed elsewhere18:54
SlickNikdenis_makogon: like I mentioned earlier, I'm still cleaning out some of the elements before I push them up to the tripleo-elements repo.18:55
SlickNikI plan to have that patch out by end of this week.18:55
denis_makogonnice18:55
denis_makogonthanks18:55
denis_makogonmoving on18:55
hub_capwell that was easy!18:55
SlickNikBut like I mentioned, the tempest tests are independent and you can work on it without that happening.18:55
SlickNikSo I'm not sure why you keep coming back to ask me about the status of that. :)18:56
hub_capcp16net: do u have time to discuss your stuff or do u want to tal about that in the meeting room after?18:56
hub_capgo cp16net go18:56
cp16netlet do it quick18:56
hub_cap#topic configurations18:56
*** openstack changes topic to "configurations (Meeting topic: trove)"18:56
cp16net#link trove - https://review.openstack.org/#/c/53168/18:56
cp16net#link python-troveclient - https://review.openstack.org/#/c/53169/18:56
cp16net#link trove-integration - https://review.openstack.org/#/c/58445/18:56
hub_capBAM18:56
cp16netgive this a spin and test out configuraitons18:56
SlickNiknice cp16net18:56
SlickNikWill try it out18:57
cp16netsweet18:57
hub_capis that it cp16net ?18:57
cp16netso config groups and datastores are associated with datastore versions and not the datastore type18:57
hub_capi was oh so hping demorris was gonna talk18:57
* imsplitbit wasn't18:57
demorrisalright, so I have a question about this one18:58
vipulcp16net: yea why is that?  don't config options generally apply to a datastore type18:58
hub_capimsplitbit: good!18:58
demorrisGiven the nature of how the datastore / types code has been implemented in that it is highly configurable, I believe that we we need to adjust the way in which we are associating configuration groups with datastore types and versions.  The main use case that I am considering here is that as a user of the API, I want to be able to associate configurations with a specific datastore type so that I can easily return a list of the18:58
demorrisconfigurations that are valid for that database type (Example: Get me a list of configurations for MySQL 5.6).18:58
demorrisWe know that configurations will vary across types (MySQL vs. Redis) as well as across major versions (MySQL 5.1 vs MySQL 5.6).   Presently, the code only keys off the datastore version, and consequently, if I were to set up my datastore type as MySQL X.X and datastore versions as X.X.X, then you would be potentially associating a configuration with a specific minor version such as MySQL 5.1.63.18:58
hub_capomg18:58
hub_capwhy dont u send us a link18:58
cweid...18:59
hub_capto that ML entry18:59
hub_capfail18:59
hub_cap;)18:59
grapexEveryone you have 60 seconds to say if you agree or not with demorris.18:59
demorrisGiven that, I am thinking that it makes more sense to allow a configuration to be associated with both a datastore type AND and datastore version with precedence given to the datastore type (where both attributes are either optional – or at least one is required).  This would give the most flexibility to associate configurations with either the type, version, or both and would allow it to work across providers given that they are likely18:59
demorristo configure types/versions differently.18:59
hub_capomt18:59
hub_capomg18:59
imsplitbithly crap18:59
cp16netwell instance was associated with an instance so this made it seem good18:59
hub_cap:)18:59
cp16net#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/021945.html18:59
cp16netftw18:59
demorrisI don't know how to do all the fancy stuff18:59
hub_capcp16net: <318:59
greghillI concur!18:59
cp16net:-P18:59
* amcrn throws on the bean boots, there's a flood happening18:59
demorrisjust read it18:59
cp16netwow18:59
hub_capamcrn: lollll18:59
demorris:)18:59
cp16netreply on the ML about this topic :)19:00
cp16netwe done19:00
hub_cap#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Wed Dec 11 19:00:17 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-12-11-18.00.html19:00
demorrisyeah, craig already put my thoughts in his ML thread19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-12-11-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-12-11-18.00.log.html19:00
demorrisyou can continue tehre19:00
*** imsplitbit has left #openstack-meeting-alt19:00
SlickNiksounds good.19:00
SlickNikThanks guys!19:00
cp16netthanks! :)19:00
cp16nettl;dr19:00
*** brents has joined #openstack-meeting-alt19:01
*** yisun has left #openstack-meeting-alt19:01
*** jcru has left #openstack-meeting-alt19:01
*** jdob has quit IRC19:03
*** jdob has joined #openstack-meeting-alt19:03
*** hemanthravi has joined #openstack-meeting-alt19:04
*** nati_uen_ has joined #openstack-meeting-alt19:05
*** RajeshMohan has joined #openstack-meeting-alt19:05
*** nati_ueno has quit IRC19:08
*** glucas has left #openstack-meeting-alt19:08
*** Sackmann has left #openstack-meeting-alt19:10
*** dark_knight_ita has quit IRC19:11
*** hemanthravi has quit IRC19:12
*** rongze has quit IRC19:13
*** colinmcn_ has quit IRC19:15
*** colinmcnamara has quit IRC19:15
*** rongze has joined #openstack-meeting-alt19:15
*** colinmcnamara has joined #openstack-meeting-alt19:15
*** vkmc has joined #openstack-meeting-alt19:15
*** colinmcn_ has joined #openstack-meeting-alt19:15
*** hemanthravi has joined #openstack-meeting-alt19:18
*** hemanthravi has quit IRC19:19
*** rongze has quit IRC19:22
*** resker has quit IRC19:23
*** esker has joined #openstack-meeting-alt19:23
*** robertmyers has left #openstack-meeting-alt19:28
*** lblanchard has joined #openstack-meeting-alt19:29
*** nati_uen_ has quit IRC19:30
*** BrianB_ has quit IRC19:31
*** alazarev has joined #openstack-meeting-alt19:32
*** eankutse has quit IRC19:32
*** colinmcn_ has quit IRC19:33
*** colinmcnamara has quit IRC19:33
*** 21WABWJ1B has joined #openstack-meeting-alt19:33
*** colinmcnamara has joined #openstack-meeting-alt19:33
*** rnirmal has quit IRC19:36
*** nati_ueno has joined #openstack-meeting-alt19:40
*** yogesh has quit IRC19:49
*** greghill has left #openstack-meeting-alt19:57
*** eankutse has joined #openstack-meeting-alt20:00
*** yogesh has joined #openstack-meeting-alt20:00
*** Barker has quit IRC20:00
*** jecarey has quit IRC20:00
*** jecarey has joined #openstack-meeting-alt20:02
*** SergeyLukjanov has quit IRC20:02
*** igormarnat_ has quit IRC20:02
*** 21WABWJ1B has quit IRC20:03
*** colinmcnamara has quit IRC20:03
*** colinmcnamara has joined #openstack-meeting-alt20:03
*** colinmcn_ has joined #openstack-meeting-alt20:03
*** Barker has joined #openstack-meeting-alt20:04
*** yogesh has quit IRC20:17
*** yogesh has joined #openstack-meeting-alt20:19
*** eankutse has quit IRC20:20
*** eankutse has joined #openstack-meeting-alt20:21
*** vipul is now known as vipul-away20:21
*** vipul-away is now known as vipul20:21
*** brents has quit IRC20:22
*** yogesh has quit IRC20:31
*** akuznetsov has quit IRC20:32
*** akuznetsov has joined #openstack-meeting-alt20:32
*** markvoelker1 has joined #openstack-meeting-alt20:34
*** devlaps has quit IRC20:35
*** vipul is now known as vipul-away20:37
*** akuznetsov has quit IRC20:38
*** dprince has quit IRC20:38
*** jecarey has quit IRC20:43
*** jecarey has joined #openstack-meeting-alt20:45
*** devkulkarni has joined #openstack-meeting-alt20:47
*** s3wong has quit IRC20:51
*** datsun180b has left #openstack-meeting-alt20:52
*** IlyaE has quit IRC20:59
*** demorris has quit IRC21:01
*** denis_makogon_ has joined #openstack-meeting-alt21:02
*** denis_makogon has quit IRC21:10
*** denis_makogon has joined #openstack-meeting-alt21:10
*** denis_makogon has quit IRC21:11
*** denis_makogon_ is now known as denis_makogon21:11
*** dmakogon_ has joined #openstack-meeting-alt21:11
*** slagle has quit IRC21:15
*** jasonb365 has joined #openstack-meeting-alt21:16
*** olkonami has left #openstack-meeting-alt21:18
*** colinmcn_ has quit IRC21:22
*** colinmcnamara has quit IRC21:22
*** brents has joined #openstack-meeting-alt21:22
*** vipul-away is now known as vipul21:25
*** yogesh has joined #openstack-meeting-alt21:26
*** jecarey has quit IRC21:29
*** jtomasek has quit IRC21:32
*** jcooley_ has quit IRC21:34
*** jcooley_ has joined #openstack-meeting-alt21:39
*** lblanchard has quit IRC21:51
*** jdob has quit IRC22:03
*** IlyaE has joined #openstack-meeting-alt22:05
*** demorris has joined #openstack-meeting-alt22:06
*** pdmars has quit IRC22:07
*** esker has quit IRC22:08
*** aignatov has quit IRC22:11
*** esker has joined #openstack-meeting-alt22:18
*** eankutse has quit IRC22:18
*** esker has quit IRC22:19
*** resker has joined #openstack-meeting-alt22:22
*** alazarev has quit IRC22:23
*** esker has joined #openstack-meeting-alt22:27
*** esker has quit IRC22:28
*** resker has quit IRC22:28
*** grapex has quit IRC22:31
*** NehaV has quit IRC22:37
*** brents has quit IRC22:43
*** enikanorov__ has quit IRC22:49
*** brents has joined #openstack-meeting-alt22:51
*** alazarev has joined #openstack-meeting-alt22:55
*** demorris has quit IRC22:57
*** jmontemayor has joined #openstack-meeting-alt22:59
*** demorris has joined #openstack-meeting-alt23:01
*** colinmcn_ has joined #openstack-meeting-alt23:02
*** colinmcnamara has joined #openstack-meeting-alt23:02
*** amytron has quit IRC23:05
*** NehaV has joined #openstack-meeting-alt23:07
*** yogesh has quit IRC23:10
*** Barker has quit IRC23:12
*** demorris has quit IRC23:13
*** NehaV has quit IRC23:14
*** NehaV has joined #openstack-meeting-alt23:14
*** yogesh has joined #openstack-meeting-alt23:16
*** flaper87 is now known as flaper87|afk23:17
*** yogesh has quit IRC23:17
*** jasonb365 has quit IRC23:17
*** kevinconway has quit IRC23:19
*** ozstacker has quit IRC23:22
*** ozstacker has joined #openstack-meeting-alt23:22
*** sergmelikyan has quit IRC23:24
*** sacharya has quit IRC23:26
*** abramley has quit IRC23:28
*** abramley has joined #openstack-meeting-alt23:29
*** abramley has quit IRC23:31
*** jbrendel has joined #openstack-meeting-alt23:40
*** dougshelley66 has quit IRC23:41
*** eankutse has joined #openstack-meeting-alt23:50
*** vipul is now known as vipul-away23:52
*** colinmcnamara has quit IRC23:59
*** colinmcn_ has quit IRC23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!