Monday, 2013-10-21

*** IlyaE has joined #openstack-meeting-alt00:03
*** jmaron has joined #openstack-meeting-alt00:52
*** nosnos has joined #openstack-meeting-alt00:56
*** jmaron has quit IRC00:57
*** nosnos has quit IRC01:10
*** nosnos has joined #openstack-meeting-alt01:11
*** ozstacker has quit IRC01:15
*** ozstacker has joined #openstack-meeting-alt01:16
*** juice has quit IRC01:23
*** juice has joined #openstack-meeting-alt01:23
*** juice has quit IRC01:23
*** juice has joined #openstack-meeting-alt01:24
*** juice has quit IRC01:24
*** juice has joined #openstack-meeting-alt01:24
*** juice has quit IRC01:24
*** juice has joined #openstack-meeting-alt01:25
*** juice has quit IRC01:25
*** juice has joined #openstack-meeting-alt01:26
*** juice has quit IRC01:26
*** juice has joined #openstack-meeting-alt01:26
*** ozstacker has quit IRC01:33
*** ozstacker has joined #openstack-meeting-alt01:38
*** ozstacker has quit IRC01:38
*** ozstacker has joined #openstack-meeting-alt01:40
*** ozstacker has quit IRC01:48
*** IlyaE has quit IRC01:48
*** ozstacker has joined #openstack-meeting-alt01:50
*** jmaron has joined #openstack-meeting-alt01:52
*** SergeyLukjanov has joined #openstack-meeting-alt01:53
*** jmaron has quit IRC01:57
*** wdennis has joined #openstack-meeting-alt02:05
*** wdennis has quit IRC02:20
*** simonmcc has quit IRC02:36
*** simonmcc has joined #openstack-meeting-alt02:37
*** SergeyLukjanov has quit IRC02:45
*** jmaron has joined #openstack-meeting-alt02:53
*** IlyaE has joined #openstack-meeting-alt02:57
*** jmaron has quit IRC02:58
*** colinmcnamara has quit IRC03:04
*** colinmcnamara has joined #openstack-meeting-alt03:05
*** colinmcnamara has quit IRC03:09
*** IlyaE has quit IRC03:11
*** rakhmerov has joined #openstack-meeting-alt03:33
*** jmaron has joined #openstack-meeting-alt03:54
*** jmaron has quit IRC03:58
*** basha has joined #openstack-meeting-alt04:11
*** IlyaE has joined #openstack-meeting-alt04:26
*** basha has quit IRC04:28
*** jmaron has joined #openstack-meeting-alt04:54
*** jmaron has quit IRC04:59
*** dmakogon has joined #openstack-meeting-alt05:03
*** yamahata has joined #openstack-meeting-alt05:12
*** basha has joined #openstack-meeting-alt05:43
*** akuznetsov has joined #openstack-meeting-alt05:50
*** boris-42 has joined #openstack-meeting-alt05:52
*** SergeyLukjanov has joined #openstack-meeting-alt06:00
*** nosnos has quit IRC06:00
*** nosnos_ has joined #openstack-meeting-alt06:00
*** akuznetsov has quit IRC06:10
*** akuznetsov has joined #openstack-meeting-alt06:12
*** akuznetsov has quit IRC06:15
*** jcoufal has joined #openstack-meeting-alt06:16
*** IlyaE has quit IRC06:23
*** jmaron has joined #openstack-meeting-alt06:25
*** jmaron has quit IRC06:30
*** IlyaE has joined #openstack-meeting-alt06:30
*** akuznetsov has joined #openstack-meeting-alt06:34
*** yamahata has quit IRC06:36
*** nosnos has joined #openstack-meeting-alt06:47
*** boris-42 has quit IRC06:48
*** nosnos_ has quit IRC06:48
*** basha has quit IRC07:00
*** IlyaE has quit IRC07:05
*** lsmola has joined #openstack-meeting-alt07:05
*** basha has joined #openstack-meeting-alt07:11
*** flaper87|afk is now known as flaper8707:13
*** rakhmerov has quit IRC07:13
*** basha has quit IRC07:21
*** jmaron has joined #openstack-meeting-alt07:26
*** basha has joined #openstack-meeting-alt07:26
*** basha has quit IRC07:27
*** jmaron has quit IRC07:31
*** dmakogon is now known as away_guy07:31
*** akuznetsov has quit IRC07:34
*** away_guy has quit IRC07:36
*** SergeyLukjanov is now known as _SergeyLukjanov07:37
*** _SergeyLukjanov has quit IRC07:38
*** SergeyLukjanov has joined #openstack-meeting-alt07:44
*** SergeyLukjanov has quit IRC07:49
*** rakhmerov has joined #openstack-meeting-alt07:52
*** jtomasek has joined #openstack-meeting-alt07:56
*** katyafervent has joined #openstack-meeting-alt07:57
*** derekh has joined #openstack-meeting-alt08:11
*** akuznetsov has joined #openstack-meeting-alt08:19
*** basha has joined #openstack-meeting-alt08:26
*** jmaron has joined #openstack-meeting-alt08:26
*** jmaron has quit IRC08:31
*** basha has quit IRC08:48
*** boris-42 has joined #openstack-meeting-alt08:53
*** HenryG_ has joined #openstack-meeting-alt08:59
*** basha has joined #openstack-meeting-alt08:59
*** nosnos has quit IRC09:01
*** nosnos has joined #openstack-meeting-alt09:01
*** HenryG has quit IRC09:01
*** basha has quit IRC09:07
*** basha has joined #openstack-meeting-alt09:12
*** jmaron has joined #openstack-meeting-alt09:27
*** jmaron has quit IRC09:31
*** aignatov has joined #openstack-meeting-alt09:43
*** akuznetsov has quit IRC10:02
*** basha has quit IRC10:09
*** sergmelikyan has quit IRC10:24
*** jmaron has joined #openstack-meeting-alt10:28
*** lpabon has joined #openstack-meeting-alt10:31
*** jmaron has quit IRC10:32
*** flaper87 is now known as flaper87|afk10:33
*** akuznetsov has joined #openstack-meeting-alt10:42
*** HenryG_ has quit IRC10:45
*** HenryG has joined #openstack-meeting-alt10:46
*** flaper87|afk is now known as flaper8711:24
*** jmaron has joined #openstack-meeting-alt11:28
*** jmaron has quit IRC11:31
*** ruhe has joined #openstack-meeting-alt11:48
*** jcoufal has quit IRC11:53
*** jcoufal has joined #openstack-meeting-alt11:53
*** jcoufal has quit IRC11:56
*** jcoufal has joined #openstack-meeting-alt11:56
*** pdmars has joined #openstack-meeting-alt12:04
*** pdmars has quit IRC12:05
*** lpabon has quit IRC12:14
*** rakhmerov has quit IRC12:17
*** ruhe has quit IRC12:22
*** ruhe has joined #openstack-meeting-alt12:29
*** ruhe has quit IRC12:29
*** pdmars has joined #openstack-meeting-alt12:31
*** rakhmerov has joined #openstack-meeting-alt12:31
*** anteaya has joined #openstack-meeting-alt12:32
*** rakhmerov has quit IRC12:33
*** rakhmerov has joined #openstack-meeting-alt12:33
*** ruhe has joined #openstack-meeting-alt12:48
*** dprince has joined #openstack-meeting-alt12:51
*** jmaron has joined #openstack-meeting-alt12:59
*** demorris has joined #openstack-meeting-alt12:59
*** nosnos has quit IRC13:09
*** julim has joined #openstack-meeting-alt13:09
*** julim has quit IRC13:09
*** nosnos has joined #openstack-meeting-alt13:10
*** julim has joined #openstack-meeting-alt13:11
*** sergmelikyan has joined #openstack-meeting-alt13:12
*** nosnos has quit IRC13:14
*** sergmelikyan has quit IRC13:15
*** sergmelikyan has joined #openstack-meeting-alt13:18
*** eankutse has joined #openstack-meeting-alt13:18
*** eankutse has quit IRC13:19
*** eankutse has joined #openstack-meeting-alt13:19
*** enikanorov__ has joined #openstack-meeting-alt13:20
*** sergmelikyan has quit IRC13:21
*** lblanchard has joined #openstack-meeting-alt13:30
*** lblanchard has quit IRC13:30
*** lblanchard has joined #openstack-meeting-alt13:31
*** rakhmerov has quit IRC13:36
*** sergmelikyan has joined #openstack-meeting-alt13:47
*** ruhe has quit IRC13:48
*** eankutse1 has joined #openstack-meeting-alt13:52
*** eankutse1 has quit IRC13:52
*** eankutse1 has joined #openstack-meeting-alt13:53
*** eankutse has quit IRC13:53
*** kevinconway has quit IRC13:57
*** IlyaE has joined #openstack-meeting-alt14:01
*** demorris has quit IRC14:04
*** ruhe has joined #openstack-meeting-alt14:04
*** demorris has joined #openstack-meeting-alt14:05
*** kevinconway has joined #openstack-meeting-alt14:07
*** bill_az_ has joined #openstack-meeting-alt14:24
*** rakhmerov has joined #openstack-meeting-alt14:26
*** jcoufal has quit IRC14:33
*** rnirmal has joined #openstack-meeting-alt14:37
*** fungi has quit IRC14:41
*** noslzzp has joined #openstack-meeting-alt14:42
*** Barker has joined #openstack-meeting-alt14:44
*** gokrokve has joined #openstack-meeting-alt14:51
*** Barker has quit IRC14:52
*** colinmcnamara has joined #openstack-meeting-alt14:52
*** vkmc has joined #openstack-meeting-alt14:55
*** vkmc has joined #openstack-meeting-alt14:55
*** ativelkov has joined #openstack-meeting-alt14:56
*** akuznetsova has joined #openstack-meeting-alt14:58
*** tnurlygayanov has joined #openstack-meeting-alt14:59
ativelkovHi folks14:59
rakhmerovhi there15:00
ativelkovLet's start the meeting15:00
ativelkov#startmetting Murano15:00
ativelkov#startmeeting Murano15:00
openstackMeeting started Mon Oct 21 15:00:43 2013 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: Murano)"15:00
gokrokveHi Alex15:00
openstackThe meeting name has been set to 'murano'15:00
*** stanlagun has joined #openstack-meeting-alt15:00
katyaferventHi guys!15:00
akuznetsovaHello15:00
sergmelikyanHi!15:00
tsufievhi there15:01
ativelkovCool, lot's of people )15:01
stanlagunhi all!15:01
ativelkovWe have an agenda here: https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda15:01
ogelbukho/15:02
*** fungi has joined #openstack-meeting-alt15:02
ativelkovSo, let's start with the review of the previous week's AIs15:02
ativelkov#topic AI review15:02
*** openstack changes topic to "AI review (Meeting topic: Murano)"15:02
ativelkovHere we have this list: http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-10-14-15.01.html15:02
ativelkovSo, about backporting of our Heat patches: according to Heat team, these were not bugs, but rather features, so backporting of them to grizzly branch is forbidden15:03
ativelkovso, we will not be able to commit our backports to official grizzly branch15:04
*** IgorYozhikov has joined #openstack-meeting-alt15:04
ativelkovThat is why we will have to distribute release 0.3 either without quantum support at all, or include patches to Heat with our distribution15:05
*** Barker has joined #openstack-meeting-alt15:05
katyaferventDoes this fix present in havana? Do we fully support it?15:06
ativelkovOf course, we may use custom for of Heat repository for this as well, but this is not a good practice and should be avoided for public releases15:06
ativelkovkatyafervent, Most of them are present, yes15:06
ogelbukheltn15:06
ogelbukhoh15:06
*** joel_c has joined #openstack-meeting-alt15:07
ativelkovhowever, there was one fix (made by sergmelikyan) which did not get accepted before the check-in gate was closed, so it will get only to icehouse branch15:07
*** betsy has joined #openstack-meeting-alt15:08
gokrokveCan we offer quantum as optional for release 0.3?15:08
ativelkovgokrokve, yes, I think so15:08
gokrokveI mean on the code level are there any hard dependencies for Quantum?15:08
ativelkovNot on the code level15:08
ativelkovAnd the question is not quantum itself15:09
ativelkovquestion is limited support for quantum in Heat15:09
tnurlygayanovso, we will not support nova network in release-0.3....15:10
ativelkovfor example, grizzly Quantum support security groups on the port level, but grizzly Heat does not fully support this feature15:10
ativelkovtnurlygayanov, I would suggest to support it "out-of-the-box"15:10
ativelkovI mean, the default templates which we distribute with Murano should be targeting Nova Network15:11
tnurlygayanovativelkov: but we should have prepared patch for this15:11
ativelkovbut we should include an archive with the quantum-ready templates15:11
tnurlygayanovyes15:11
ativelkovand include a manual how to a) substitute the NN templates with the Quantum ones b) patch Heat15:12
ativelkovby the way, NN templates will work with Quantum as well, but the set of functionality will be different15:12
tnurlygayanovit is should be 'one magic command', not complex document )15:13
gokrokveStill it should be documented in installation guide.15:13
ativelkov#info  The default templates which we distribute with Murano should be targeting Nova Network,  but we will include an archive with the quantum-ready templates and ways to migrate and patch the Heat15:13
*** lpabon has joined #openstack-meeting-alt15:13
ativelkovgokrokve, yes, we should provide a detailed explanation15:14
ativelkovpatching an infrustructure-level component should not be done blindly15:14
ativelkovbut an easy-to-use authomation script is also a good idea15:15
akuznetsovabtw I created task in jira that we need to update our documentation before release15:15
*** jprovazn has joined #openstack-meeting-alt15:15
ativelkovThanks, akuznetsova15:15
ativelkovTwo other action items are related to r0.3 task synchronization. sergmelikyan, can you provide an update on the release status and what is going to be included there?15:16
sergmelikyanWe had synchronized all tasks for 0.315:17
ativelkovwhat about Murano Panel? Have you decided if it should be part of 0.3 or not?15:18
sergmelikyanWe have several major features: Support for Managing Linux Instances, Usage of Quantum and ability to mark images in glance via UI15:19
sergmelikyanPanel (actually Dashboard in terms of Horizon) not going to be introduced in 0.315:19
tsufievativelkov: it is simple to implement on its own, but can potentially break many things in 0.315:20
ativelkovso, we'll have the same UI layout for 0.3?15:20
tsufievativelkov: yes15:20
*** yidclare has quit IRC15:20
ativelkov#info new leyout of Murano Dashboard will not be included with the release 0.3 and is postponed till 0.415:21
ativelkovOK, next AI (we have quite a lot of them btw)15:21
ativelkovtnurlygayanov, what about the test plan for release-0.3?15:22
tnurlygayanovativelkov: we are working on it...15:23
ativelkovany estimations?15:23
tnurlygayanovand also on automated testing for all services and new workflows with automated testing inside the workflows.15:23
tnurlygayanovyes, I plan to finish for 2 days.15:24
tnurlygayanovand it will not only for release-0.3 test plan, also for 0.4 too.15:24
ativelkov#info Release 0.3 test plan is in progress, as well as updated automation testing scenarios. The ETA is 2 days15:24
ativelkovgood, thanks15:24
ativelkovLast AI is on me15:25
ativelkovI asked Boris to do some follow up on Mistral announcement15:26
ativelkovIt turns out that he didn't get enough time for this, as he is quite busy with his own releases15:26
ativelkovBut we still get some community responses to the announcement15:27
rakhmerovcan we ask him provide some feedback on the tech docs we have?15:27
ativelkovI asked, but he said that he is too busy now, probably later15:28
rakhmerovhis opinion should be valuable due to his specific experience15:28
ativelkovAs far as I understood he is interested in Taskflow library, so he should probably have some attention to Mistral as well15:28
rakhmerovyes, I know but I meant ask him to do that before the next meeting or so15:28
ativelkovI'll try15:28
rakhmerovok, thanks15:28
ativelkovSo, seems like we are done with AIs15:29
*** jprovazn has quit IRC15:29
gokrokveDid we test Linux Agent?15:29
gokrokveIs it ready for delivery?15:29
ativelkovYes15:29
ativelkovBut with quite a simple scenario by now15:29
gokrokveDo we have example workflow for it?15:30
*** tanisdl has joined #openstack-meeting-alt15:30
ativelkovwe simply deploy telnet15:30
ativelkov#topic Release-0.315:30
*** openstack changes topic to "Release-0.3 (Meeting topic: Murano)"15:30
ativelkov#info LinuxAgent is ready to be delivered in Release-0.3, with simplest possible deployment workflow15:31
ativelkovsergmelikyan, do we have anything important to discuss about 0.3?15:31
ativelkovwhat are the open issues there, etc?15:32
*** ruhe has quit IRC15:32
*** dmakogon has joined #openstack-meeting-alt15:32
rakhmerovsorry, a quick note/question: as for LinuxAgent, should we start calling it PythonAgent meaning it can be used not on Linux only?15:33
gokrokveYes.15:33
rakhmerovor it's already been discussed and approved?15:33
*** ruhe has joined #openstack-meeting-alt15:33
ativelkovwell, we were calling it Unified (vNext) Agent15:33
gokrokveLinuxAgent is not an official name. We use it just to highlight that it works on Linux.15:33
gokrokveremove vNext. Nobody understands that.15:34
rakhmerovright, however it may get people confused15:34
rakhmerovwho is right here, ha :)15:34
rakhmerovUnified Agent seems to be ok15:35
sergmelikyanativelkov, right now we don't have any outstanding issues15:35
rakhmerovsorry for interrupting, back to open issues15:35
ativelkovsergmelikyan, what are our estimation on release date?15:36
katyaferventSo we just selected official  name - Unified Agent?15:36
rakhmerovI would suggest so15:36
stanlagunI guess official name for Murano Agent is Murano Agent :)15:36
ativelkovkatyafervent, the idea is that we have a unified agent specification (the one which is available at https://wiki.openstack.org/wiki/Murano/UnifiedAgent)15:37
ativelkovthe name of the exact implementation does not matter much, as we expect that other implementations may appear15:38
sergmelikyanativelkov, end of October, first days of November15:38
ativelkovsergmelikyan, thanks15:38
ativelkov#info Release0.3 is on its way, no outstanding issues, release planned to end of October-beginning of November15:38
ativelkovOk15:39
ativelkov#topic Networking Changes for 0.415:39
*** openstack changes topic to "Networking Changes for 0.4 (Meeting topic: Murano)"15:39
ativelkovSo, we have an important question to discuss15:40
ativelkovIt turns oput that we will to introduce a new major feature in Release 0.415:40
ativelkovturns out*15:40
ativelkovIn quantum-enabled version of 0.3 we have isolated each environment into is own L2-segment15:41
ativelkovI.e. each env creates its own network with its own subnet, then creates a router and then plugs this router to some external network15:42
gokrokveDid you test that with Quantum VM still able to communicate with RabbitMQ?15:42
ativelkovYes, sure15:42
ativelkovthe deployments are successfull15:43
ativelkovThe problem is with the IP range of the external network15:43
ativelkovOur approach means one router per environment15:43
ativelkovand each router in external network obviously consumes 1 IP address from its range15:43
ativelkovAnd these IP{ addresses are quite a valuable resource15:44
ativelkovThe proper way of doing these should be different15:44
ativelkovwe should have a single Router per tenant15:44
ativelkovand plug all the Networks of this tenant into this router15:45
*** alcabrera has joined #openstack-meeting-alt15:45
ativelkovBut to do this we will have to define non-overlapping subnets15:45
tnurlygayanovprobably we can configure some 'murano' router and assign all networks to this router15:46
ativelkovtnurlygayanov, the proper solution should be more complex15:46
tnurlygayanovand user will select new network range for new environment15:46
tnurlygayanovok) need to describe arch in images15:46
tnurlygayanovit will more clear for everyone15:47
*** kgriffs has joined #openstack-meeting-alt15:47
ativelkovYes. I am writing a new document on this topic right now15:47
gokrokveok. We need to document this. It is not self obvious about Quantum networking topologies.15:47
ativelkov#action ativelkov to complete the "Per Environment Network Management" document15:48
rakhmerovso we should have something like subnet booking mechanism?15:48
ativelkovrakhmerov, yes15:48
rakhmerovgotcha15:48
ativelkovAlso, we should allow the user to select an existing network for the new environment15:48
ativelkov(we had similar blueprint for security groups)15:49
ativelkovbut this should be an advanced option15:49
rakhmerovprobably we could provide two options and let the users make a choice15:49
ativelkovyup15:49
rakhmerovone the options is by default15:49
ativelkovbut the default should be simple and secure15:49
rakhmerovright15:49
*** malini has joined #openstack-meeting-alt15:50
ativelkove.g. by default, a new network is created per environment, as subnet is allocated accordign to the existing subnets, and the network is plugged to some default router15:50
ativelkovand in advanced scenarios user will be able to override any of these defaults (i.e. choose existing network, or modify the ip range, or choose the router, etc)15:50
ativelkovAs I said, I will complete the spec and will submit the blueprint15:51
rakhmerovok15:51
ativelkovSeems like we are done with this topic, let's move on15:51
ativelkov#topic Open Discussion15:51
*** openstack changes topic to "Open Discussion (Meeting topic: Murano)"15:51
ativelkov:)15:51
rakhmerovthe most pleasant one :)15:52
ativelkovyeah. So, any questions, guys?15:52
katyaferventNope, thanks for making all questions clear15:53
*** ruhe has quit IRC15:53
ativelkovAlright, so we are probably done15:54
ativelkovJust do not forget that we have a Mistral meeting in 6 minutes15:54
rakhmerovyes, sure15:54
ativelkovIt's in different channel, #openstack-meeting15:54
tnurlygayanovok ) got to the next meeting )15:54
sergmelikyanAnd in another channel ;)15:54
*** tnurlygayanov has quit IRC15:55
ativelkovso, thanks for joining and see you soon15:55
ativelkov#endmeeting15:55
*** openstack changes topic to "OpenStack meetings (alternate)"15:55
openstackMeeting ended Mon Oct 21 15:55:12 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
rakhmerovyep, thank you15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-10-21-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-10-21-15.00.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-10-21-15.00.log.html15:55
*** akuznetsova has left #openstack-meeting-alt15:55
*** ruhe has joined #openstack-meeting-alt15:55
*** zyuan has joined #openstack-meeting-alt15:57
alcabrerao/16:00
*** jmontemayor has joined #openstack-meeting-alt16:00
kgriffsMarconi time16:00
malinio/16:01
flaper87\o/16:01
*** amitgandhi has joined #openstack-meeting-alt16:01
*** ativelkov has left #openstack-meeting-alt16:02
kgriffsok, looks like we've got a good crew together16:03
kgriffs#startmeeting marconi16:03
openstackMeeting started Mon Oct 21 16:03:26 2013 UTC and is due to finish in 60 minutes.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: marconi)"16:03
openstackThe meeting name has been set to 'marconi'16:03
flaper87<o/ \o>16:03
kgriffs#link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda16:03
kgriffs#topic Review teh actionz from teh last timez16:03
*** openstack changes topic to "Review teh actionz from teh last timez (Meeting topic: marconi)"16:04
flaper87:D16:04
kgriffs#link http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-07-16.03.html16:04
*** ruhe has quit IRC16:04
kgriffsso, looks like flaper87 was the only one with anything to do this past week.16:04
kgriffs;)16:04
alcabreralol16:04
flaper87erm, mmh, erm erm mmhh16:05
flaper87I totally failed on that but I got feedback on the devstack patch16:05
flaper87does that count?16:05
flaper87:D16:05
kgriffsheh16:05
flaper87I'll get to it this week16:05
flaper87promissed16:05
kgriffs#action flaper87 to research heat16:06
kgriffsok16:06
kgriffsotherwise16:06
kgriffsquick not regarding API freeze16:06
*** boris-42 has quit IRC16:06
kgriffsas Murphy's Law dictates, immediately after freezing the API we started getting people complaining about certain aspects of it16:06
kgriffsSo, i started a page to track feedback. We will need to review it at some point.16:07
kgriffshttps://wiki.openstack.org/wiki/Marconi/specs/api/next16:07
zyuan:)16:07
alcabrera#link https://wiki.openstack.org/wiki/Marconi/specs/api/next16:07
alcabrera#info Now tracking API feedback for future versions.16:07
*** yidclare has joined #openstack-meeting-alt16:08
flaper87interesting notes16:08
*** akuznetsov has quit IRC16:08
flaper87I would like us to break them down on an etherpad / bugs and comment there16:08
flaper87I can help with bugs creation16:08
kgriffsyeah, let's hold off for a bit and see what else comes in16:09
flaper87sure, I'd say we should start putting them in an etherpad then16:09
zyuani think we need to discuss them first16:09
kgriffsfwiw, I thought this post was pretty relevant. ;)16:09
flaper87and add some comments16:09
kgriffshttp://sethgodin.typepad.com/seths_blog/2013/09/when-to-speak-up.html16:09
flaper87heheh16:10
kgriffsflaper87: let me set that up for next week. We've got sharding to focus on for now.16:10
alcabrerayup - speak up before it is done, though getting people to break the inertia before use is tough. :P16:10
flaper87yeah, I meant to do it off-line16:10
flaper87not right now16:10
flaper87sorry for not being explicit enough :D16:10
kgriffsok, feel free to set up etherpadz or whateverz16:10
flaper87okeyz16:11
flaper87neeeext topicz16:11
flaper87:D16:11
kgriffs#topic teh updatez on teh shardzes16:11
*** openstack changes topic to "teh updatez on teh shardzes (Meeting topic: marconi)"16:11
alcabreralol16:11
alcabrerayeah, there's a lot going on there~16:12
* flaper87 didn't know kgriffs knows french16:12
alcabreraSo, with a link to summarize the state of things16:12
alcabrera#link https://etherpad.openstack.org/p/sharding-merge-strategy16:12
alcabreraWr've gotten a lot of the foundational stuff down.16:12
alcabrera*We've16:12
alcabreraPipeline enhancements, a sharding driver stubbed out16:13
alcabreraIt's been a load of development towards making sharding a real thing.16:13
alcabrera(for marconi)16:13
*** jtomasek has quit IRC16:13
alcabrerathe proposed admin API is currently under review16:13
alcabreraonce that's merged, we'll have a sharding and a catalogue queues storage driver for controlling shard registration16:14
kgriffsok, any big questions or concerns or blockers?16:15
zyuanrequires_mongodb16:15
flaper87not from me!16:15
zyuandoes not work T_T16:15
alcabrerathe only blocker is already being addressed - let's keep reviewing the admin API branch and get those storage drivers in. :)16:15
flaper87The whole idea and work looks good16:15
flaper87zyuan: mmh, it does work for here :(16:15
*** rnirmal_ has joined #openstack-meeting-alt16:15
kgriffsok, rock on16:16
zyuanjust not on jenkins with py26. discuss latter.16:16
kgriffswe'll continue working through those patches in #openstack-marconi16:16
alcabreraawesome16:16
kgriffs#topic The future of the proxy16:16
*** openstack changes topic to "The future of the proxy (Meeting topic: marconi)"16:16
* alcabrera notes how serious the tone suddenly became - 90% fewer z's16:17
alcabrera*100%16:17
* kgriffs has to budget his z's - doesn't want to run out early16:18
alcabrerakgriffs: want to lead the discussion on this one?16:18
kgriffssure16:18
kgriffsso, given that we will have storage-layer sharding16:18
kgriffshow far will that allow Marconi to scale?16:18
kgriffs(without any proxy thingy)16:19
flaper87Far enough, imho!16:19
alcabrerait seems like it would go for some time. Some potential bottlenecks are CPU/connections|node, but those seem far off atm.16:19
flaper87I was also thinking that Marconi it'sef could be use as a shard in case of more partitions are needed16:20
*** rnirmal_ has quit IRC16:20
*** rnirmal has quit IRC16:20
*** rnirmal has joined #openstack-meeting-alt16:20
flaper87meaning, we coul have a Marconi storage backend that talks to a remote Marconi server16:20
flaper87in case that's ever needed16:20
kgriffsmy mind just exploded16:20
flaper87LOL16:21
kgriffscool idea16:21
alcabreralol16:21
alcabreraThat's like nova in docker in nova in...16:21
flaper87:D16:21
flaper87I'll create a bp for that then :D16:21
amitgandhiso a marconi storage backend would talk to another marconi transport?16:22
kgriffsok, so the proposal is to stamp a big-ole YAGNI on the proxy?16:22
alcabreraThat's my favored outcome for the proxy.16:22
flaper87I'd say so16:22
flaper87amitgandhi: yeah, it'd talk to another Marconi16:22
flaper87that bp will obviously depend on the client being ready16:23
alcabreraThat'd be -2372 LOC for removing the proxy - easier to manage.16:23
flaper87shall we vote?16:23
amitgandhibiggest fear there for me is the latency of it16:23
alcabreraflaper87: good idea16:23
*** markwash has quit IRC16:23
kgriffs#startvote Remove the proxy, salvaging what we can for the sharding feature? Yes, No, Abstain16:23
openstackBegin voting on: Remove the proxy, salvaging what we can for the sharding feature? Valid vote options are Yes, No, Abstain.16:23
openstackVote using '#vote OPTION'. Only your last vote counts.16:23
flaper87amitgandhi: yeah, that needs to be examined a lot!16:23
alcabrera#vote yes16:23
flaper87#vote yes16:23
amitgandhi#vote yes16:23
zyuan#vote Abstain16:24
kgriffs#vote yez16:24
openstackkgriffs: yez is not a valid option. Valid options are Yes, No, Abstain.16:24
alcabreralol16:24
zyuan...16:24
* kgriffs bots have no humor16:24
kgriffs#vote yes16:24
kgriffsgoing once...16:25
kgriffstwice...16:25
zyuanwhen?16:25
kgriffs#endvote16:25
openstackVoted on "Remove the proxy, salvaging what we can for the sharding feature?" Results are16:25
openstackYes (4): amitgandhi, alcabrera, kgriffs, flaper8716:25
openstackAbstain (1): zyuan16:25
*** markwash has joined #openstack-meeting-alt16:25
kgriffsok, once sharding is packaged up with a pretty bow, we can nuke the proxy code16:25
zyuanok16:25
kgriffslet's leave it around until then for reference16:25
zyuan+116:26
alcabreraI've already started the salvaging process.16:26
kgriffsanything else on that topic?16:26
alcabrerathe admin API feature branch used many of the idioms and storage patterns I put together while working on the proxy.16:26
alcabrera*uses16:26
alcabreraPlus, it has pagination. :P16:26
alcabreraAnyway, that's it from me on the proxy.16:27
alcabrera(nuke it from orbit)16:27
kgriffs#topic API Spec server sidez16:27
*** openstack changes topic to "API Spec server sidez (Meeting topic: marconi)"16:27
*** IlyaE has quit IRC16:27
alcabreramore zzzzs16:27
flaper87o/16:27
flaper87o/16:27
kgriffsflaper87: go for it16:27
flaper87o/16:27
* flaper87 runs towards it16:27
* flaper87 is still running16:27
* flaper87 is getting tired16:27
* flaper87 fainted16:27
flaper87ok16:27
flaper87seriously16:28
zyuanthat's the first issue?16:28
flaper87The idea there is to have something similar to what we have in the client but adapted a bit for the server16:28
flaper87it all starts from the thought that we don't have a good way to version our server-side API16:28
flaper87... yet.16:28
flaper87so, this is what we've in the client16:28
flaper87#link https://review.openstack.org/#/c/50638/7/marconiclient/queues/v1/api.py16:29
flaper87In that JSON, I'm specifying the API that can be validated with json schema.16:29
flaper87(if needed)16:29
flaper87although it seems a bit HTTP tight, it actually isn't.16:30
flaper87The whole point is that HTTP is the most partitioned protocol we have right now16:30
flaper87other protocols can simple translate that to something they need16:30
flaper87and can use16:30
flaper87so, hope that explains a bit the idea16:31
*** derekh has quit IRC16:31
flaper87thoughts so far?16:31
alcabrerait's true - zmq is just data + Maybe framing16:31
alcabreraHTTP is a bit more enveloped16:31
alcabreraI don;t know about websockets16:31
alcabreraAnd I'm pretty sure nanomsg is similar to zmq (data + Maybe frames)16:31
flaper87For example, current wsgi controllers would register routes based on that dict16:31
zyuanzmq's frame is invisible16:31
alcabrerazyuan: it's invisible as long as you don't use the XSUB/XPUB patterns16:32
zyuan:(16:32
alcabreraflaper87: as for the idea in general, I'm pretty positive towards it.16:32
alcabreraIt seems like it would greatly reduce the effort required to add a new transport.16:32
* flaper87 is pretty sure it'll need tweaked a bit16:33
flaper87need to be*16:33
alcabreraInstead of implementing each of the resources for each protocol, it seems like only the low-level transport.api.py.thing would have to be implemented16:33
flaper87but, yeah, the idea is to have a well defined API schema16:33
alcabreraand the resources just use the appropriate lower-level to forward/serialize data.16:33
alcabreraI'm +2 on the API schema16:34
kgriffshmm16:34
flaper87that would also give us a home endpoint for free and eventually help us a lot with API discovery16:35
flaper87also, it will unified the API definition throughout transports16:35
flaper87as for now, we basically need to 'define' it for each transport16:36
kgriffsso, the proposal is to define the API using json-schema16:36
flaper87kgriffs: ish, the idea is to have an API schema. Jsonschema has proven to be good for the job16:36
flaper87it can be validated but it doesn't "have to" plus, it is flexible enough16:37
kgriffsso, one schema that all the transports are based on?16:37
*** markwash has quit IRC16:37
flaper87kgriffs: yup16:37
flaper87Transport would get an 'Api' instance that they'll use to 'register' endpoints16:38
flaper87that Api instance contains the API version, schema and other things related to the API16:38
flaper87this is what the base API looks like in the client https://github.com/openstack/python-marconiclient/blob/master/marconiclient/transport/api.py16:39
flaper87#link https://github.com/openstack/python-marconiclient/blob/master/marconiclient/transport/api.py16:39
flaper87I can work on a POC for it16:39
flaper87and we can discuss it a bit further based on that16:40
alcabreraflaper87: To some extent, the client impl. is a pre-POC. :D16:40
flaper87alcabrera: good point :D16:40
kgriffsyeah, let's do that16:40
* flaper87 takes that back16:40
flaper87damn16:40
alcabreralol16:40
* flaper87 facepalm16:40
kgriffs?16:40
flaper87:P16:40
flaper87kgriffs: just kidding!16:40
flaper87I'll do some experiments on marconi-queues16:41
flaper87and show the results16:41
flaper87but I'd like to get a general thought now about the whole idea16:41
*** ruhe has joined #openstack-meeting-alt16:41
flaper87if you guys see some limitations16:41
flaper87etc16:41
kgriffsdo you see this complicating, simplifying, or keeping the WSGI driver code the same?16:42
kgriffs(keeping roughly same in complexity, I mean)16:42
flaper87I see this simplifying the WSGI code16:42
kgriffsin what ways?16:42
flaper871) The way routes are being defined, 2) We could reuse Controller classes in different versions16:44
flaper87Number 2 obviously depends on the changes between versions16:44
flaper87but what it definitely improves is API's consistency between transports16:45
flaper87let me work on a POC16:45
flaper87I think that will make this clearer16:45
kgriffs#action flaper87 to work on a POC for server API schema thingy16:46
alcabreraawesome. That'll be good to see growing. :)16:46
flaper87cool16:46
kgriffsflaper87: i think I see where you are headed16:46
kgriffsbtw, could you also consider the question of api extensions?16:47
*** rnirmal_ has joined #openstack-meeting-alt16:47
flaper87kgriffs: yes, will do!16:47
kgriffsjust want to make sure whatever we implement takes that into consideration16:47
kgriffsok16:47
flaper87any thoughts so far?16:47
flaper87like "WTF are you planning?" or "Yup, that could work"16:47
kgriffsso, I like the idea of defining the API in code, rather than on a wiki page16:47
alcabrerakgriffs: +116:48
flaper87+116:48
flaper87we can generate Wiki pages out of it16:48
flaper87:D16:48
flaper87ok, cool!16:48
alcabreraIt gives us the opportunity to - yes, that16:48
alcabrera^16:48
flaper87lets move on16:48
flaper87there are other topics to talk about16:48
alcabreranext topic?16:48
kgriffsyeah, the basic idea is good, I just want to make sure it doesn't unnecessarily complicate the transport drivers16:48
kgriffs#topic API versioning strategy?16:49
*** openstack changes topic to "API versioning strategy? (Meeting topic: marconi)"16:49
kgriffsso, I put out some feelers re api versioning a few weeks back16:49
kgriffsit sounds like the community prefers extensions and major api revs over media type versioning16:49
kgriffsdoes that sound about right?16:50
zyuanonly media type?16:50
zyuanwithout url?16:50
*** rnirmal has quit IRC16:50
*** rnirmal_ is now known as rnirmal16:50
kgriffslike, if a client requests queues/my-queue/messages with16:50
kgriffsaccept: application/vnd.openstack.marconi.messages.v216:50
kgriffsthen we return a different representation of the messages resource16:51
zyuan:( that will be curl un-friendly16:51
alcabrerahmmm...16:51
kgriffsso, this is the recommended approach instead - http://www.infoq.com/presentations/OpenStack-Extensions16:52
kgriffs(from what I could gather)16:52
kgriffsthat's my first thought16:52
alcabreraCool, I'll check that out.16:52
kgriffssecond is whether to target v2 API for Havana, or stick with v1 plus maybe some extensions16:52
kgriffs#link http://www.infoq.com/presentations/OpenStack-Extensions16:52
flaper87kgriffs: Icehouse, you mena16:53
flaper87mena16:53
flaper87mean16:53
kgriffsoops, yeah16:53
kgriffsIcehouse16:53
* alcabrera kgriffs is a time traveler16:53
alcabrera**notices16:53
zyuankgriffs: can briefly introduce the link above?16:53
kgriffsthe idea being, we start out with a polished API for our first integrated release16:53
kgriffszyuan: basically, you allow api extensions by introducing new resources (with new URLs), new headers, etc.16:53
alcabreraIcehouse is expected for 2014-04-0416:53
flaper87kgriffs: we could also target some minor releases for v1 depending on what needs to be changed16:54
alcabrera#info Icehouse is expected for 2014-04-0416:54
flaper87lets note that our client doens't fully support v1 yet16:54
kgriffsyou also provide a way for clients to discover said extensions16:54
flaper87it'd be a bit ackward to release API v2 and leave the client behind16:54
flaper87although that clients have a different release cycle16:54
kgriffsyes, i agree16:54
zyuanwhat an api extension looks like?16:54
kgriffswell, v2 would be a minor bump i suppose16:55
kgriffsi guess we could just do v1.1 instead16:55
* flaper87 votes for 1.116:55
flaper871 -> 2 will create a LOT of confussion16:55
alcabrerav1.1 works for me, given the changes requested are rather small atm16:55
*** ruhe has quit IRC16:55
alcabrerav2.0 makes me think of routing/exchanges and tags/topics16:56
kgriffsthat would be more open-stacky, although the RESTafarian in me screams our in agony16:56
kgriffsflaper87: noted16:56
kgriffsok, so let's think about doing a v1.1 for Icehouse16:56
zyuan/v1.1/ ?16:56
zyuanif so, LGTM16:57
kgriffsthen 2.0 stuff we want to start working on we can have first as extensions - that will force us to start making extensions work for 3rd-parties16:57
kgriffszyuan: right16:57
zyuanactually, i think we can provide extension between releases16:58
flaper87plus, the summit is 2 weeks from tomorrow, we'll definitely get a lot of feedback tehre16:58
flaper87there16:58
zyuanand merge them to new releases16:58
flaper87we should also wait on that before taking any final decission16:58
kgriffsyeah, that is one of the purposes of extensions in general16:58
zyuangreat16:58
kgriffsPOCs16:58
zyuanwe don't have much time left; can we discuss the object size / json doc length stuff?16:59
kgriffsyeah, just one moment16:59
kgriffs#info Target v1.1 for Icehouse16:59
kgriffs#topic Updates on bugs17:00
*** openstack changes topic to "Updates on bugs (Meeting topic: marconi)"17:00
kgriffszyuan: go for it17:00
zyuancurrently, we define document limit in terms of JSON char count17:00
zyuanbut obviously that does not work for other content like msgpack17:00
flaper87zyuan: just a comment about that review. I'm ok with marking WIP in the summary but lets also use the WIP button in gerrit, pls! I didn't notice it was a WIP and reviewed it17:00
zyuanLOL, ok...17:01
flaper87:P17:01
zyuanin addition, currently the code run in production does not perform real JSON char count checking17:01
zyuanI short cut it with content-length checking17:02
zyuanbut if we enable the JSON char count checking.... that would be not just a little slow17:02
zyuanso my proposal is to redefine "document size"17:02
zyuan-- in terms of the total size of sub obejcts17:02
zyuanfor example, int and double has size 817:03
zyuanempty array, {} has size 817:03
zyuanetc.17:03
zyuanso that any type of media type can have same size17:03
zyuanand the checking is cheaper than JSON char count (unless we have a sizing parser in C)17:03
*** sarob has joined #openstack-meeting-alt17:04
zyuanprototype: https://review.openstack.org/#/c/51921/17:04
*** colinmcnamara has quit IRC17:04
zyuancomment?17:04
flaper87I like the idea overall, I'm a bit worried about the iteration cost (I mean, going deeper on nested objects) but I think that's still cheaper than counting chars17:05
kgriffsI think it would be helpful to have a python sizing parser as a baseline17:05
alcabreraThe recursion is elegant, and I don't expect it to be too expensive CPU-wise.17:05
kgriffsgiven a dict, it walks it and counts up JSON chars17:05
alcabreraIf this becomes a CPU-bound task, then pypy would likely shine here.17:06
alcabreraGiven it's pure Python.17:06
zyuanthen you pretty much need N iteration, where N is JSON char counts...17:06
kgriffsI am still concerned about confusion on the part of the users/library developers when they get back an error response and they have to figure out why their message was too large.17:06
alcabreraErr, becomes a CPU bottleneck17:06
zyuanit has to be done in C17:06
flaper87alcabrera: yeah, but we can't expect all deployments to use pypy17:06
*** rnirmal has quit IRC17:06
alcabreraflaper87: true. :)17:06
*** rnirmal has joined #openstack-meeting-alt17:06
zyuani implemented it with recusion just because i don't how to do it without17:07
flaper87kgriffs: that also had me thinking17:07
kgriffsalso, we don't have much data on average message complexity17:07
kgriffsonly what we can extrapolate from Rackspace's use of the internal precursor to Marconi17:07
zyuan... and i suspect a manual recursion to be even slower...17:07
*** ruhe has joined #openstack-meeting-alt17:07
zyuankgriffs: i hope so?17:08
*** colinmcnamara has joined #openstack-meeting-alt17:08
kgriffsi mean, if messages are usually not very complex, then we may be doing premature optimization here17:08
kgriffsbut we are still speculating17:08
ekarlsois RAX using marconi or ?17:08
flaper87I guess we could examine this a bit further and re-schedule the discussion17:09
kgriffswe use a primitive sort of Marconi called RSE (really simple events)17:09
flaper87like I said, I like the idea overall17:09
kgriffsso, requirements17:09
kgriffs1. Users must not be confused17:10
kgriffs2. It needs to be fast for the common case17:10
zyuan(as a numerical anaysis user, i feel *really* confused with JSON char counts)17:10
zyuan(i agree, performance improvement, hopefully)17:11
kgriffs3. Don't optimize prematurely; a naive python character counter may be good enough, for example17:11
kgriffsanyway, we are out of time17:11
kgriffslet's keep discussing17:11
flaper87lets re-schedule this for next week17:11
* flaper87 gtg now17:11
* kgriffs has to go too17:12
kgriffs#endmeeting17:12
*** openstack changes topic to "OpenStack meetings (alternate)"17:12
openstackMeeting ended Mon Oct 21 17:12:06 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:12
kgriffsthanks!17:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-21-16.03.html17:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-21-16.03.txt17:12
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-21-16.03.log.html17:12
*** zyuan has left #openstack-meeting-alt17:12
*** flaper87 is now known as flaper87|afk17:13
*** boris-42 has joined #openstack-meeting-alt17:13
*** alcabrera has left #openstack-meeting-alt17:14
*** SergeyLukjanov has joined #openstack-meeting-alt17:15
*** markwash has joined #openstack-meeting-alt17:18
*** IlyaE has joined #openstack-meeting-alt17:20
*** kgriffs is now known as kgriffs_afk17:25
*** akuznetsov has joined #openstack-meeting-alt17:27
*** esker has joined #openstack-meeting-alt17:27
*** sacharya has joined #openstack-meeting-alt17:29
*** rnirmal has quit IRC17:30
*** rnirmal has joined #openstack-meeting-alt17:31
*** SergeyLukjanov is now known as _SergeyLukjanov17:35
*** _SergeyLukjanov has quit IRC17:35
*** colinmcnamara has quit IRC17:45
*** sreshetnyak1 has joined #openstack-meeting-alt17:45
*** eankutse1 has quit IRC17:45
*** demorris has quit IRC17:45
*** ruhe has quit IRC17:45
*** kgriffs_afk is now known as kgriffs17:46
*** eankutse has joined #openstack-meeting-alt17:48
*** rakhmerov has quit IRC17:49
*** rakhmerov has joined #openstack-meeting-alt17:50
*** rakhmerov has quit IRC17:50
*** gokrokve has quit IRC17:50
*** gokrokve has joined #openstack-meeting-alt17:51
*** SergeyLukjanov has joined #openstack-meeting-alt17:52
*** colinmcnamara has joined #openstack-meeting-alt17:52
*** SergeyLukjanov has quit IRC17:53
*** SergeyLukjanov has joined #openstack-meeting-alt17:54
*** gokrokve has quit IRC17:55
*** vkmc has quit IRC17:55
*** dmakogon is now known as away_dude17:55
*** ruhe has joined #openstack-meeting-alt17:57
*** jprovazn has joined #openstack-meeting-alt17:58
*** kgriffs is now known as kgriffs_afk17:59
*** ruhe has quit IRC18:00
*** markmcclain has joined #openstack-meeting-alt18:00
*** sarob has quit IRC18:01
*** sarob has joined #openstack-meeting-alt18:01
*** dkehn is now known as dkehn_lunch18:05
*** sarob has quit IRC18:06
*** rnirmal has quit IRC18:12
*** rnirmal has joined #openstack-meeting-alt18:12
*** colinmcnamara has quit IRC18:18
*** markmcclain has quit IRC18:20
*** rakhmerov has joined #openstack-meeting-alt18:20
*** sarob has joined #openstack-meeting-alt18:22
*** sarob has quit IRC18:22
*** sarob has joined #openstack-meeting-alt18:23
*** sarob has quit IRC18:24
*** julim has quit IRC18:24
*** sarob has joined #openstack-meeting-alt18:24
*** rakhmerov has quit IRC18:25
*** dprince has quit IRC18:25
*** jcoufal has joined #openstack-meeting-alt18:27
*** SergeyLukjanov is now known as _SergeyLukjanov18:27
*** _SergeyLukjanov has quit IRC18:28
*** kgriffs_afk is now known as kgriffs18:28
*** sarob has quit IRC18:29
*** SergeyLukjanov has joined #openstack-meeting-alt18:32
*** Barker has quit IRC18:32
*** nadya has joined #openstack-meeting-alt18:34
*** lpabon has quit IRC18:36
*** lpabon has joined #openstack-meeting-alt18:38
*** ruhe has joined #openstack-meeting-alt18:38
*** Barker has joined #openstack-meeting-alt18:38
*** rnirmal has quit IRC18:41
*** rnirmal has joined #openstack-meeting-alt18:41
*** jprovazn has quit IRC18:41
*** ruhe has quit IRC18:43
*** dkehn_lunch is now known as dkehn18:43
*** lblanchard has quit IRC18:49
*** lblanchard has joined #openstack-meeting-alt18:53
*** sarob has joined #openstack-meeting-alt18:55
*** sarob has quit IRC18:56
*** sarob has joined #openstack-meeting-alt18:56
*** stanlagun has left #openstack-meeting-alt19:00
*** rnirmal_ has joined #openstack-meeting-alt19:02
*** rnirmal_ has quit IRC19:03
*** rnirmal_ has joined #openstack-meeting-alt19:03
*** rnirmal has quit IRC19:03
*** rnirmal_ is now known as rnirmal19:03
*** away_guy has joined #openstack-meeting-alt19:03
*** away_guy is now known as dmakogon19:07
*** gokrokve has joined #openstack-meeting-alt19:11
*** demorris has joined #openstack-meeting-alt19:17
*** rakhmerov has joined #openstack-meeting-alt19:21
*** pdmars_ has joined #openstack-meeting-alt19:22
*** yamahata has joined #openstack-meeting-alt19:23
*** pdmars has quit IRC19:25
*** rakhmerov has quit IRC19:25
*** malini is now known as malini_afk19:38
*** jcoufal has quit IRC19:50
*** nadya has quit IRC19:52
*** eankutse has quit IRC19:59
*** eankutse has joined #openstack-meeting-alt20:00
*** vkmc has joined #openstack-meeting-alt20:05
*** tanisdl has quit IRC20:06
*** lblanchard has quit IRC20:06
*** demorris_ has joined #openstack-meeting-alt20:07
*** demorris has quit IRC20:08
*** demorris_ is now known as demorris20:08
*** nadya has joined #openstack-meeting-alt20:09
*** eankutse has quit IRC20:10
*** eankutse has joined #openstack-meeting-alt20:10
*** vipul is now known as vipul-away20:10
*** vipul-away is now known as vipul20:10
*** nadya has quit IRC20:17
*** colinmcnamara has joined #openstack-meeting-alt20:18
*** steven-weston has joined #openstack-meeting-alt20:18
*** colinmcnamara has quit IRC20:19
*** rakhmerov has joined #openstack-meeting-alt20:21
*** akuznetsov has quit IRC20:24
*** vipul is now known as vipul-away20:25
*** rakhmerov has quit IRC20:26
*** tanisdl has joined #openstack-meeting-alt20:26
*** sreshetnyak1 has quit IRC20:30
*** jmontemayor has quit IRC20:33
*** Barker has quit IRC20:34
*** yamahata has quit IRC20:35
*** jmontemayor has joined #openstack-meeting-alt20:36
*** Barker has joined #openstack-meeting-alt20:37
*** colinmcnamara has joined #openstack-meeting-alt20:41
*** Barker has quit IRC20:47
*** Barker has joined #openstack-meeting-alt20:49
*** vipul-away is now known as vipul20:50
*** yamahata has joined #openstack-meeting-alt20:52
*** gokrokve has quit IRC20:52
*** gokrokve has joined #openstack-meeting-alt20:53
*** gokrokve_ has joined #openstack-meeting-alt20:57
*** jtomasek has joined #openstack-meeting-alt20:57
*** gokrokve has quit IRC20:58
*** markmcclain has joined #openstack-meeting-alt21:00
*** markmcclain has quit IRC21:01
*** markmcclain has joined #openstack-meeting-alt21:02
*** yamahata has quit IRC21:03
*** anteaya_ has joined #openstack-meeting-alt21:03
*** jrodom has joined #openstack-meeting-alt21:03
*** yamahata has joined #openstack-meeting-alt21:03
*** jtomasek has quit IRC21:03
*** yidclare has quit IRC21:03
*** pdmars_ has quit IRC21:05
*** yidclare has joined #openstack-meeting-alt21:06
*** anteaya has quit IRC21:06
*** yamahata has quit IRC21:08
*** noslzzp has quit IRC21:09
*** malini_afk is now known as malini21:17
*** yidclare has quit IRC21:20
*** rakhmerov has joined #openstack-meeting-alt21:22
*** yamahata has joined #openstack-meeting-alt21:24
*** malini is now known as malini_afk21:26
*** rakhmerov has quit IRC21:27
*** vipul is now known as vipul-away21:39
*** vipul-away is now known as vipul21:40
*** sarob has quit IRC21:41
*** sarob has joined #openstack-meeting-alt21:41
*** eankutse has quit IRC21:45
*** sarob has quit IRC21:46
*** jmaron has quit IRC21:48
*** dmakogon has quit IRC21:50
*** betsy has quit IRC21:55
*** yamahata has quit IRC21:58
*** anteaya_ has quit IRC22:12
*** Barker has quit IRC22:14
*** SergeyLukjanov is now known as _SergeyLukjanov22:15
*** _SergeyLukjanov is now known as SergeyLukjanov22:15
*** noslzzp has joined #openstack-meeting-alt22:17
*** demorris has quit IRC22:18
*** rakhmerov has joined #openstack-meeting-alt22:22
*** sarob has joined #openstack-meeting-alt22:24
*** rakhmerov has quit IRC22:27
*** esker has quit IRC22:28
*** SergeyLukjanov is now known as _SergeyLukjanov22:28
*** _SergeyLukjanov is now known as SergeyLukjanov22:28
*** sarob has quit IRC22:29
*** amitgandhi has quit IRC22:33
*** markmcclain has quit IRC22:34
*** IlyaE has quit IRC22:35
*** kgriffs is now known as kgriffs_afk22:35
*** IlyaE has joined #openstack-meeting-alt22:39
*** dhellmann is now known as dhellmann-afk22:41
*** tanisdl has quit IRC22:41
*** vkmc has quit IRC22:42
*** dhellmann-afk is now known as dhellmann22:44
*** SergeyLukjanov has quit IRC22:45
*** SergeyLukjanov has joined #openstack-meeting-alt22:46
*** dhellmann is now known as dhellmann-afk22:46
*** colinmcnamara has quit IRC22:46
*** SergeyLukjanov is now known as _SergeyLukjanov22:46
*** _SergeyLukjanov has quit IRC22:48
*** jmaron has joined #openstack-meeting-alt22:48
*** tanisdl has joined #openstack-meeting-alt22:54
*** jmaron has quit IRC22:56
*** rnirmal has quit IRC23:01
*** jodom has joined #openstack-meeting-alt23:03
*** jodom has quit IRC23:03
*** steven-weston has quit IRC23:04
*** yamahata has joined #openstack-meeting-alt23:04
*** jmontemayor has quit IRC23:04
*** vipul is now known as vipul-away23:06
*** jrodom has quit IRC23:07
*** colinmcnamara has joined #openstack-meeting-alt23:07
*** SergeyLukjanov has joined #openstack-meeting-alt23:10
*** vipul-away is now known as vipul23:20
*** gokrokve_ has quit IRC23:23
*** gokrokve has joined #openstack-meeting-alt23:23
*** rakhmerov has joined #openstack-meeting-alt23:25
*** sarob has joined #openstack-meeting-alt23:25
*** gokrokve has quit IRC23:28
*** rakhmerov has quit IRC23:29
*** sarob has quit IRC23:30
*** noslzzp has quit IRC23:30
*** boris-42 has quit IRC23:30
*** markmcclain has joined #openstack-meeting-alt23:33
*** SergeyLukjanov is now known as _SergeyLukjanov23:33
*** _SergeyLukjanov is now known as SergeyLukjanov23:33
*** jmaron has joined #openstack-meeting-alt23:33
*** SergeyLukjanov is now known as _SergeyLukjanov23:34
*** _SergeyLukjanov is now known as SergeyLukjanov23:34
*** colinmcnamara has quit IRC23:35
*** jrodom has joined #openstack-meeting-alt23:42
*** markmcclain has quit IRC23:43
*** gokrokve has joined #openstack-meeting-alt23:46
*** vipul is now known as vipul-away23:52

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