Wednesday, 2013-09-04

*** IlyaE has joined #openstack-meeting-alt00:03
*** IlyaE has quit IRC00:06
*** colinmcnamara has joined #openstack-meeting-alt00:14
*** esp2 has joined #openstack-meeting-alt00:19
*** NikitaKonovalov has joined #openstack-meeting-alt00:22
*** NikitaKonovalov has quit IRC00:26
*** amytron has joined #openstack-meeting-alt00:26
*** kebray has joined #openstack-meeting-alt00:27
*** esp2 has left #openstack-meeting-alt00:29
*** IlyaE has joined #openstack-meeting-alt00:30
*** esker has joined #openstack-meeting-alt00:39
*** sacharya has quit IRC00:44
*** NikitaKonovalov has joined #openstack-meeting-alt00:53
*** nos_ has joined #openstack-meeting-alt00:54
*** nos_ has quit IRC00:54
*** nosnos has joined #openstack-meeting-alt00:55
*** NikitaKonovalov has quit IRC00:57
*** esp2 has joined #openstack-meeting-alt01:02
*** colinmcnamara has quit IRC01:07
*** sacharya has joined #openstack-meeting-alt01:10
*** NikitaKonovalov has joined #openstack-meeting-alt01:23
*** NikitaKonovalov has quit IRC01:28
*** esker has quit IRC01:32
*** markwash has joined #openstack-meeting-alt01:33
*** HenryG has joined #openstack-meeting-alt01:42
*** NikitaKonovalov has joined #openstack-meeting-alt01:54
*** NikitaKonovalov has quit IRC01:59
*** colinmcnamara has joined #openstack-meeting-alt02:04
*** markmcclain has joined #openstack-meeting-alt02:23
*** NikitaKonovalov has joined #openstack-meeting-alt02:25
*** colinmcnamara has quit IRC02:29
*** NikitaKonovalov has quit IRC02:30
*** amytron has quit IRC02:43
*** nosnos_ has joined #openstack-meeting-alt02:47
*** nosnos has quit IRC02:49
*** nosnos_ has quit IRC02:55
*** nosnos has joined #openstack-meeting-alt02:55
*** NikitaKonovalov has joined #openstack-meeting-alt02:56
*** anteaya has quit IRC02:58
*** NikitaKonovalov has quit IRC03:01
*** kiall has quit IRC03:07
*** esp2 has left #openstack-meeting-alt03:14
*** NikitaKonovalov has joined #openstack-meeting-alt03:27
*** kiall has joined #openstack-meeting-alt03:29
*** NikitaKonovalov has quit IRC03:31
*** NikitaKonovalov has joined #openstack-meeting-alt03:58
*** clarkb has quit IRC03:59
*** clarkb has joined #openstack-meeting-alt03:59
*** NikitaKonovalov has quit IRC04:03
*** IlyaE has quit IRC04:07
*** markmcclain has quit IRC04:11
*** esp1 has joined #openstack-meeting-alt04:17
*** esp1 has joined #openstack-meeting-alt04:18
*** IlyaE has joined #openstack-meeting-alt04:21
*** SergeyLukjanov has joined #openstack-meeting-alt04:25
*** NikitaKonovalov has joined #openstack-meeting-alt04:29
*** NikitaKonovalov has quit IRC04:33
*** esp1 has quit IRC04:34
*** sacharya has quit IRC04:38
*** nadya has joined #openstack-meeting-alt04:43
*** vipul is now known as vipul-away04:44
*** vipul-away is now known as vipul04:50
*** boris-42 has joined #openstack-meeting-alt04:51
*** akuznetsov has joined #openstack-meeting-alt04:57
*** nadya has quit IRC04:58
*** NikitaKonovalov has joined #openstack-meeting-alt05:00
*** amytron has joined #openstack-meeting-alt05:00
*** amytron has quit IRC05:02
*** amytron has joined #openstack-meeting-alt05:03
*** NikitaKonovalov has quit IRC05:04
*** IlyaE has quit IRC05:05
*** dmakogon_ has joined #openstack-meeting-alt05:20
*** amytron has quit IRC05:20
*** amytron has joined #openstack-meeting-alt05:20
*** nadya has joined #openstack-meeting-alt05:25
*** akuznetsov has quit IRC05:26
*** amytron has quit IRC05:26
*** amytron has joined #openstack-meeting-alt05:27
*** akuznetsov has joined #openstack-meeting-alt05:29
*** amytron has quit IRC05:29
*** vipul is now known as vipul-away05:29
*** amytron has joined #openstack-meeting-alt05:30
*** NikitaKonovalov has joined #openstack-meeting-alt05:30
*** amytron has quit IRC05:32
*** amytron has joined #openstack-meeting-alt05:33
*** colinmcnamara has joined #openstack-meeting-alt05:35
*** NikitaKonovalov has quit IRC05:36
*** openstack has joined #openstack-meeting-alt14:53
*** ChanServ sets mode: +o openstack14:53
*** jmontemayor has quit IRC14:56
*** IlyaE has joined #openstack-meeting-alt15:00
*** jmontemayor has joined #openstack-meeting-alt15:01
*** demorris has joined #openstack-meeting-alt15:06
*** bdpayne has joined #openstack-meeting-alt15:07
*** bdpayne has quit IRC15:11
*** jtomasek has quit IRC15:12
*** bdpayne has joined #openstack-meeting-alt15:16
*** kebray has joined #openstack-meeting-alt15:20
*** sacharya has joined #openstack-meeting-alt15:23
*** kiall has quit IRC15:24
*** jtomasek has joined #openstack-meeting-alt15:27
*** ruhe has joined #openstack-meeting-alt15:31
*** mestery_ has joined #openstack-meeting-alt15:37
*** mestery has quit IRC15:40
*** mestery_ is now known as mestery15:43
*** vipul is now known as vipul-away15:44
*** kiall has joined #openstack-meeting-alt15:44
*** bdpayne has quit IRC15:49
*** vipul-away is now known as vipul15:50
*** dhellmann is now known as dhellmann_15:55
*** markwash has quit IRC15:59
*** jmontemayor has quit IRC16:00
*** dina_belova has quit IRC16:00
*** jcoufal has quit IRC16:00
*** SergeyLukjanov has quit IRC16:08
*** dkoryavov has joined #openstack-meeting-alt16:11
*** NikitaKonovalov has quit IRC16:13
*** boris-42 has quit IRC16:14
*** IlyaE has quit IRC16:15
*** ruhe has quit IRC16:21
*** esp2 has joined #openstack-meeting-alt16:23
*** esp2 has left #openstack-meeting-alt16:25
*** kiall has quit IRC16:30
*** IlyaE has joined #openstack-meeting-alt16:34
*** kiall has joined #openstack-meeting-alt16:41
*** kiall has quit IRC16:41
*** kiall has joined #openstack-meeting-alt16:41
*** IlyaE has quit IRC16:41
*** colinmcnamara has joined #openstack-meeting-alt16:42
*** vinodmr has joined #openstack-meeting-alt16:46
*** demorris has quit IRC16:48
*** asavu has joined #openstack-meeting-alt16:48
*** kiall has quit IRC16:52
*** ruhe has joined #openstack-meeting-alt16:54
*** kiall has joined #openstack-meeting-alt16:55
*** colinmcnamara has quit IRC16:57
kiallHeya16:58
eankutseeankutse here16:58
*** mugsie has joined #openstack-meeting-alt16:58
vinodmrvinod here16:59
*** colinmcnamara has joined #openstack-meeting-alt16:59
kiall#startmeeting Designate16:59
openstackMeeting started Wed Sep  4 16:59:33 2013 UTC and is due to finish in 60 minutes.  The chair is kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** openstack changes topic to " (Meeting topic: Designate)"16:59
openstackThe meeting name has been set to 'designate'16:59
kiallHeya16:59
kiallWho's about? :)16:59
*** markwash has joined #openstack-meeting-alt16:59
*** ruhe has quit IRC17:00
mugsieo/17:00
betsyo/17:00
kiallOkay - so a few of us :) simonmcc / capttofu are AFK at the moment, not sure if they'll be joining us today17:01
kiallLet's get started so..17:01
kiall#topic API v2.0 Progress17:01
*** openstack changes topic to "API v2.0 Progress (Meeting topic: Designate)"17:01
*** CaptTofu has joined #openstack-meeting-alt17:02
kiallProgress here has stalled - We've been dealing with lots of internal stuff over the last week or so ... Much more than usual!17:02
*** msisk has joined #openstack-meeting-alt17:02
* CaptTofu o17:02
kiallI've not had enough hours in the day to get the records side of the V2 API done (or even started)17:03
eankutse:-)17:03
kiallBut - It's on my list for this week.17:03
kiallmugsie has been working on some V2 related stuff, which we can get to in a bit!17:03
kiallAnyway - Just wanted to give a quick update on that...17:03
kiall#topic Async State Transitions17:03
*** openstack changes topic to "Async State Transitions (Meeting topic: Designate)"17:03
eankutsethx17:04
kiallSo - This is what mugsie has been working on since he started with HP last week, and it ties in with both the API v2 and Async-Backends17:04
kiallmugsie: want to give an intro to the current plan/progress?17:04
mugsieI am currently working on the design of the async backends17:04
mugsieI should have some docs up on a wiki page fairly soon, but i will give a quick overview17:05
*** jmcbride has joined #openstack-meeting-alt17:05
mugsieThe idea is, that when a back end operation happens, the back end is given a ticket17:05
mugsieand when the operation is complete we send the ticket back to central, and mark it as complete in the designate DB17:06
eankutseineresting...17:06
mugsienow there is some flow issues, an trying to make sure we dont edn up with inconsistant data17:06
mugsiebut that is the genral gist17:06
mugsienow, these tickets are completely internal to designate17:07
mugsieso theuser just sees a 202 Accepted responce17:07
eankutsemugsie: so what are examples of backend ops?17:07
mugsieand when they query designate, it will show pending until it is active,at which piint the status will change17:07
mugsiecreation / update / delete of domains / record17:08
*** ruhe has joined #openstack-meeting-alt17:08
*** boris-42 has joined #openstack-meeting-alt17:08
mugsierecords*17:08
kiallAny operation which changes something you query on port 53 basically ;)17:08
betsyIs any of this on any of the blueprints on launcpad?17:08
vinodmrWhat is the response that the user sees with a 202 - how do they get the link to query for status?17:08
mugsiebetsy: not yet, but should be by beginning of next week17:09
betsycool17:09
mugsiemaybe then end of this one17:09
kiallvinodmr: so, the "ticket" is more for intenal tracking of the operation within designate.. and end-user will never see the ticket ID etc, only "status = PENDING" vs "status = ACTIVE" in the API17:09
betsybut will the user receive a link to check status?17:10
mugsievinodmr: the link will be the "self" item in the responce17:10
mugsieand when they get that link it will have a status field17:10
betsyok17:10
vinodmrI am trying to understand why we need a separate ticket id.17:10
mugsiehttps://review.openstack.org/#/c/44730/ is the beginning work of this17:10
vinodmrCan we not use the self link to communicate the status?17:11
mugsievinodmr: this is for when a backend is not doing the operations instantly17:11
kiallvinodmr: well, the status would be included alongside the self link, and re-querying the self link would return the full resource, again, including the status field17:12
kiallSimilar to how while booting a Nova instance, it will go to "BUILD", then eventually "ACTIVE"17:12
vinodmri meant can we use the domain/record it itself to communicate status between the backend and central?17:12
vinodmr*id17:13
*** jcoufal has joined #openstack-meeting-alt17:13
vinodmrat any given time, can there be multiple operations outstanding for the same domain/record id?17:14
mugsievinodmr: this allows for multiple operations to be used17:14
mugsieso say creating a record and domain17:14
mugsieso both need to be done in the right order17:14
*** kiall_ has joined #openstack-meeting-alt17:15
*** kiall_ has quit IRC17:15
*** kiall_ has joined #openstack-meeting-alt17:15
betsybut isn't there a domain id and a record id already?17:15
mugsieyeap, but we could have multiple operations happening on a single item17:15
mugsieso the domain should not go to active untillall have completed17:16
kiall_So, the "ticket" helps tie things like - 5x create records in a row, and only when all tickets for the domain are complete, should it move back to "ACTIVE"17:16
kiall_even though those 5 records themselves would go to ACTIVE as soon as they are pushed out17:16
*** IlyaE has joined #openstack-meeting-alt17:17
kiall_Anyway! Graham is still working through the docs for how this ties together, hopefully things will be clearer once they get pushed to the wiki/a blueprint17:17
*** IlyaE has quit IRC17:18
mugsieyeah, we can talk about it when the docs go up17:18
betsylooking forward to the docs17:18
eankutsemugsie: thx17:19
vinodmrone last question - so in this e.g. would the user first send a create request for a domain and then a create request for 5 records or would it be one request with a create for a domain and 5 records?17:19
kiall_#action mugsie to finish+publish docs on async backends/tickets/etc17:19
kiall_vinodmr: so, with the v2 API as is today, create domain can't contain any RecordSets17:20
kiall_But.. They could create the 5 records in 1 create RRSet request, or maybe 2 in one RRSet, and the rest in another etc..17:20
kiall_But - even if it could, all the RRSets/Records in a zone should be live before the zone swiches back to ACTIVE...17:21
kiall_Okay :) Well - Things should get clearer once the docs go out.. We can discuss again once they go up in #openstack-dns :)17:22
vinodmrThanks kiall and mugsie, I will wait for the docs for further clarification and I will look at the changeset that mugsie pointed to17:22
kiall_#topic "Verifing" Domain Ownership17:23
*** kiall has quit IRC17:23
*** kiall_ is now known as Kiall17:23
Kiall#topic "Verifing" Domain Ownership17:23
KiallUgh17:23
KiallOkay - so justinsb suggested this, and I17:23
Kiallwanted to get your opinions on it17:23
KiallDoes RAX have any requirement for verifying ownership of a domain before accepting/serving a domain?17:24
*** Kiall is now known as kiall17:24
kiall#topic "Verifing" Domain Ownership17:24
*** openstack changes topic to ""Verifing" Domain Ownership (Meeting topic: Designate)"17:24
kiallThere we go :)17:24
*** jmontemayor has joined #openstack-meeting-alt17:25
CaptTofuheh17:25
simonmccso this is a larger DNS hosting issue - how does it affect Designate?17:25
vinodmrhow big/common of a problem is this?17:26
simonmccother than providing tooling to support a decision process or correction process?17:26
kiallvinodmr: well, I don't personally see it as a major issue.. To me, it's something for support teams to handle.17:26
jmcbrideIn a multi tenant environment, we think it is important that if a customer creates "microsoft.com", another customer can not create "hijack.microsft.com"17:26
kiallIf Yahoo! registers google.com in one of our services, and Google decides that one of us is the best for DNS, we have a problem... The Q is, should be be providing for automation of this conflict resolution?17:27
*** tsimmons has joined #openstack-meeting-alt17:27
kialljmcbride: absolutely - we prevent that scenario today17:27
simonmcchow do you prevent it?17:28
kiallBut.. I think we have a bug that if someone reghisters bla.example.com, another tenant can nab example.com ..17:28
simonmccconflict resolution involves somebody making a decision & then deleting the 'illegal zones'17:28
kiallI've yet to validate if that's actually an issue though17:28
vinodmrfrom what i saw in the chat yesterday, this looks to be very involved and the best thing at this point would be to resolve this issues through support17:28
mugsiesimonmcc: for some of them they ask you to create a cname record, then test if its there17:29
simonmcccreate a came for a zone you're trying to get hosted?  or create the came in the parent?17:29
kiallvinodmr: I tend to agree, there are ways of making it work 100% automated.. But I'm not sure there something we could "force" on everyone..17:29
betsyyeah or a txt record17:29
kiall#link http://blog.cloudflare.com/whats-the-story-behind-the-names-of-cloudflares-name-servers17:29
mugsiesimonmcc: in the parent zone, unless you use an inbuilt registrar17:30
kiall^ that was a really interesting approach, but 100% somthing we can't bake into designate as a requirement17:30
kiallbetsy: well, the issue with a TXT record is brand new domains don't have existing DNS :)17:30
*** yogesh has joined #openstack-meeting-alt17:30
kiallAnyway - It sounds like you guys agree, this is out of scope17:30
*** kiall_ has joined #openstack-meeting-alt17:31
*** kiall_ has quit IRC17:31
*** kiall_ has joined #openstack-meeting-alt17:31
simonmccagreed, out of scope17:32
vinodmr#agreed17:32
*** bdpayne has joined #openstack-meeting-alt17:32
msiskYep. Big can of worms. ;)17:32
betsyagreed17:32
kiallOkay - Well, lets call that out of scope and move on so :)17:33
jmcbrideagreed, the yahoo/google scenario is out of scope.  However, we should consider the super domain scenario you described (bla.example.com and example.com).17:33
*** jcoufal has quit IRC17:33
kialljmcbride: yea, I believe that is already covered - at least in one direction - I'll validate after this and file a bug if necessary17:33
kiall#topic Migration tools17:33
*** openstack changes topic to "Migration tools (Meeting topic: Designate)"17:33
kialljmcbride: you added this item :)17:34
jmcbrideyes, I was curious if any tools exist today that allow a customer to easily grab zone files and migrate to Designate.17:34
kiallAh - So.. At the moment, no. I have a proof on concept zone import/export17:35
*** yogesh has quit IRC17:35
kiall#link https://blueprints.launchpad.net/designate/+spec/domain-import-export17:35
kiallBut - It's full of holes!17:35
*** bdpayne_ has joined #openstack-meeting-alt17:36
kiallThe blueprint ^ would cover feeling in, and exporting out BIND style config files..17:36
kiallfeeding*17:36
*** bdpayne has quit IRC17:36
kiall(It's open for the taking BTW :P)17:37
kiallI'd also love to be able to handle inbound AXFR's, allowing us to create "slave" zones that pull from a customers existing DNS servers17:37
simonmcchas anybody gone through cloud flare's process?  do they just pick off www/mail/blog etc from your domain?17:38
kiallThe CF "sucking existing records" process is awful IMO - it's grabbing only the well known names.. The interesting part is their conflict resolution/verification of ownership :)17:39
simonmccinbound axfr would be a very nice feature, but I'm unsure how much use it would get?  depends on your customer base, I suppose the bigger the customer, with more sophisticated users, it's more likely17:39
kiallIt does probably attempt an AXFR against your DNS servers, but any well configured DNS server will reject that when it comes from $random IP :)17:40
msiskyeah, I haven't used AXFR in a long time -- it's blocked everywhere nowadays.17:40
jmcbrideSounds like AXFR should be a separate blueprint17:41
mugsiejmcbride: yup17:41
kiallsimonmcc: yea, I see it as 2 things.. 1) A way to "import" and them, flip the "slave" -> "master" switch on the zone.. and 2) to allow for the bigger guys who might want to use  HP DNS, or RAX DNS as a "DNS CDN" .. simply taking advantage of our POPs17:41
simonmccyep17:41
kialljmcbride: yea.. It's not happening anytime soon - unless you guys have the resources to handle it :)17:41
CaptTofuagreed17:42
kiallI've barely got bast the "That would be a useful thing" thoughts on it :)17:42
kiallI'm only mentioning it, as it semi-relates to importing of data :)17:42
kiallThe other import option, is something in the client, rather than an API endpoint, that reads and creates the zone.17:42
kiallAnyway - The short answer is, no, we have no easy 1 step import at the moment.. But we do have a BP for 1 method :)17:44
tsimmonsCool, that would be useful.17:44
kiallOkay moving on :)17:44
kiall#topic Open Discussion17:44
*** openstack changes topic to "Open Discussion (Meeting topic: Designate)"17:44
kialli.e. the "Anyone got anything else?" part of the meeting :)17:45
kiallI think eankutse had some Q's earlier?17:45
msiskBTW, my proposal to do a presentation at http://openstack.onales.com on Designate has been accepted. ;)17:45
simonmcccongrats msisk!17:46
kiallExcellent!17:46
msiskMight need you folks to help me out once I get working on the slide deck. Guess I should start soon. ;)17:46
kiallSure - Anytime :)17:46
msiskkiall: Thanks!17:47
kiallSo .. Last call? :)17:48
eankutseNothing from me17:48
simonmccnothing from me17:49
mugsieditto17:49
betsysame for me17:49
kiallOkay - Thanks all :)17:49
eankutse:-)17:49
CaptTofuthanks!17:50
kiallWill talk during the week, once mugsie gets the docs  up17:50
mugsieo/17:50
kiallprobably before the next meet?17:50
tsimmonsGood stuff17:50
mugsieyeah17:50
kiall#endmeeting17:50
*** openstack changes topic to "OpenStack meetings (alternate)"17:50
openstackMeeting ended Wed Sep  4 17:50:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-09-04-16.59.html17:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-09-04-16.59.txt17:50
eankutseGreat! Looking forward to it17:50
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-09-04-16.59.log.html17:50
*** demorris has joined #openstack-meeting-alt17:51
*** ruhe has quit IRC17:53
*** jtomasek has quit IRC17:55
*** vinodmr has left #openstack-meeting-alt17:56
*** akuznetsov has quit IRC18:04
*** jmcbride has left #openstack-meeting-alt18:05
*** kiall has quit IRC18:05
*** tsimmons has left #openstack-meeting-alt18:08
*** dina_belova has joined #openstack-meeting-alt18:11
*** SergeyLukjanov has joined #openstack-meeting-alt18:11
*** dina_belova has quit IRC18:16
*** dmakogon_ has joined #openstack-meeting-alt18:18
*** asavu has quit IRC18:26
*** bdpayne_ has quit IRC18:33
*** nadya has joined #openstack-meeting-alt18:35
*** kiall_ has quit IRC18:35
*** kiall has joined #openstack-meeting-alt18:38
*** sarob has joined #openstack-meeting-alt18:40
*** jcoufal has joined #openstack-meeting-alt18:41
*** yogesh has joined #openstack-meeting-alt18:44
*** dhellmann_ is now known as dhellmann18:46
*** colinmcnamara has quit IRC18:52
*** nadya_ has joined #openstack-meeting-alt18:54
*** yogesh has quit IRC18:57
*** nadya has quit IRC18:57
*** yogesh has joined #openstack-meeting-alt18:58
*** nadya_ has quit IRC19:07
*** SergeyLukjanov has quit IRC19:07
*** NikitaKonovalov has joined #openstack-meeting-alt19:10
*** dina_belova has joined #openstack-meeting-alt19:11
*** kiall has quit IRC19:12
*** vipul is now known as vipul-away19:14
*** vipul-away is now known as vipul19:14
*** NikitaKonovalov has quit IRC19:14
*** dina_belova has quit IRC19:16
*** dkoryavov has quit IRC19:28
*** vipul is now known as vipul-away19:29
*** SnowDust has joined #openstack-meeting-alt19:29
*** jcru has joined #openstack-meeting-alt19:30
*** vipul-away is now known as vipul19:34
*** yogesh has quit IRC19:37
*** yogesh has joined #openstack-meeting-alt19:40
*** IlyaE has joined #openstack-meeting-alt19:40
*** dosaboy_ has joined #openstack-meeting-alt19:40
*** asavu has joined #openstack-meeting-alt19:41
*** yogesh has quit IRC19:42
*** dosaboy has quit IRC19:42
*** kiall has joined #openstack-meeting-alt19:43
*** yogesh has joined #openstack-meeting-alt19:43
*** arborism has joined #openstack-meeting-alt19:43
*** grapex has joined #openstack-meeting-alt19:44
*** jcoufal has quit IRC19:46
*** ashestakov has joined #openstack-meeting-alt19:47
arborismdoes rax or hp have some customization (not public) regarding security groups in trove? There's some odd inconsistencies in the code, making it difficult to fix a bug.19:48
arborismwhoops, wrong channel19:48
*** _ozstacker_ has joined #openstack-meeting-alt19:52
*** yogesh has quit IRC19:53
*** saurabhs has joined #openstack-meeting-alt19:53
*** ozstacker has quit IRC19:54
*** colinmcnamara has joined #openstack-meeting-alt19:55
*** robertmyers has joined #openstack-meeting-alt19:58
*** imsplitbit has joined #openstack-meeting-alt19:58
dmakogon_+20:01
*** SlickNik has joined #openstack-meeting-alt20:01
imsplitbito/20:01
grapexo/20:02
dmakogon_0/20:02
robertmyerso/20:02
dmakogon_o/20:02
SlickNik#startmeeting trove20:02
openstackMeeting started Wed Sep  4 20:02:15 2013 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: trove)"20:02
openstackThe meeting name has been set to 'trove'20:02
vipul;/20:02
robertmyerso/20:02
vipulugh20:02
dmakogon_what is the topic ?20:02
SlickNikHello all20:02
dmakogon_hi20:02
imsplitbithola!20:02
SlickNikAgenda is at https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Agenda_for_the_next_meeting20:02
kevinconway70720:02
*** dukhlov_ has joined #openstack-meeting-alt20:03
SlickNikPlease update it if you have a topic you want to discuss.20:03
pdmarso/20:03
*** jrodom has joined #openstack-meeting-alt20:03
dmakogon_already20:03
arborismo/20:03
*** jasonb365 has joined #openstack-meeting-alt20:03
SlickNik#topic Update to Action items20:03
*** openstack changes topic to "Update to Action items (Meeting topic: trove)"20:03
SlickNik#link http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-08-28-20.02.html20:03
*** isviridov_ has joined #openstack-meeting-alt20:03
dmakogon_isviridov: hi20:03
isviridov_hi, everybody20:04
ashestakovhi20:04
SlickNikhub_cap to find out what happens w/ feature based reviews that land after FF20:04
imsplitbithai20:04
dukhlov_hi20:04
imsplitbithub_cap is currently flying20:04
imsplitbitin an aeroplane20:04
SlickNikYeah. He told me to cover for this one.20:04
dmakogon_trove, guys, let's talk about it))20:04
*** datsun180b has joined #openstack-meeting-alt20:05
SlickNikSo after FF the branch remains frozen until we cut our first release candidate (RC1)20:05
dmakogon_yeah, that is how it works)20:05
SlickNikWhich should happen in about a week or so.20:05
dmakogon_friday - H320:06
dmakogon_next friday RC20:06
SlickNikOnce we have RC1 cut, we open the branch again for icehouse submissions.20:06
*** cweid has joined #openstack-meeting-alt20:06
SlickNikany questions?20:07
SlickNikokay, moving on...20:07
vipulworks for me20:07
SlickNikSlickNik to leave current patch as is and investigate adding trove role to default devstack users in another patch.20:07
SlickNikSo that's what most of the other projects are doing.20:08
SlickNikSo I will be adding a follow up patch once the devstack patch lands.20:08
*** lpabon has quit IRC20:08
SlickNik#link https://review.openstack.org/#/c/38169/20:08
*** yogeshmehra has joined #openstack-meeting-alt20:08
*** yogesh has joined #openstack-meeting-alt20:08
SlickNikdatsun180b: you're up.20:09
SlickNiktrove-conductor update.20:09
datsun180bWorking on submitting my wip for trove-conductor now.20:09
datsun180bIt's not complete, but I have a daemon listening to a queue, and a guestagent that speaks to a queue20:10
SlickNikSweet. Looking forward to the review.20:10
dmakogon_any updates about Conductor ?20:11
datsun180bWell, it's not complete. I need to hand it off, as I'll be gone all of next week20:11
*** cp16net has joined #openstack-meeting-alt20:11
*** NikitaKonovalov has joined #openstack-meeting-alt20:11
datsun180bHence a WIP review20:11
cp16nethello sorry i'm late20:11
*** esp2 has joined #openstack-meeting-alt20:11
grapexdatsun180b: I'll try to pick that up (then I may pawn if off later though)20:11
* grapex laughs sinisterly 20:11
datsun180bFine by me, it'll be in good hands20:11
dmakogon_any blocking stuff for Conductor ?20:11
SlickNikheh, gotcha datsun180b20:12
*** dina_belova has joined #openstack-meeting-alt20:12
datsun180bdmakogon_: mostly configuration woes as i'm green to rabbit20:12
datsun180bthat's all for me, you'll see the reviews when i submit them20:12
grapexWith Rabbit it always seems like nothing works, until you get the last config tweaked perfectly20:13
SlickNikThanks datsun180b. Sounds good, let's move on…20:13
dmakogon_datsun180b: ok20:13
isviridov_datsun180b, any link to code?20:13
SlickNikOkay, next: team needs to discuss and come up with a consistent JSON notation across API20:13
dmakogon_datsun180b: could you paste any code or specification of Conductor ?20:14
kevinconwaydatsun180b: code plox?20:14
juicein the review guys20:14
SlickNikdmakogon_ /isviridov: datsun180b's in the process of posting his WIP review.20:14
juiceyou'll seeit all20:14
dmakogon_ok20:15
SlickNikSo we still need to discuss having a consistent JSON notation.20:15
SlickNikAnd haven't had a chance to do it so far.20:15
grapexSlickNik: consistent JSON spec for the REST API?20:15
*** NikitaKonovalov has quit IRC20:15
dmakogon_about JSON: lets formalize notation and present it OpenStack community20:15
dmakogon_present to20:15
kevinconwayi thought hub_cap already did that20:16
vipuldmakogon_: i think that's been done in the past, but gone nowhere.. no harm in trying again i suppose20:16
SlickNikgrapex: yes. right now we have some variable using under_scores and others using camelCase...20:16
grapexSlickNik: hub_cap made a wiki article on the next version of the API20:16
vipulwhat was the decision?20:16
SlickNikSo the idea was we should formalize a consistent spec  for Trove.20:16
grapexone feature of the wishlist was to have consistent JSON stuff20:16
dmakogon_vipul: lets formalize JSON notation for trove and use it like standard20:16
SlickNikAt least for the next version of the API.20:16
isviridov_I would suggest camelCase, as well as w3c uses it http://www.w3schools.com/json/20:17
kevinconwayi'm pretty sure hub_cap was for the underscored notation20:17
*** dina_belova has quit IRC20:17
juiceit appears as the general rule is to follow python notation more so than any generic standard20:17
dmakogon_vipul: agree with isviridov20:17
juicethis being the case, we should use underscores20:17
SlickNikit seems like other openstack projects are divided and inconsistent regarding this as well.20:18
SlickNikWhich sucks.20:18
kevinconwayisviridov: w3schools is not w320:18
vipul#link https://wiki.openstack.org/wiki/Trove/NextAPI20:18
jrodomi'd love to see general consensus across openstack programs ideally.20:18
isviridov_kevinconway, but they really follows w3c20:18
juicedoes one lend itself to dynamic binding more than the other?20:19
vipuli don't believe so, since it's all dicts20:19
*** yogesh has quit IRC20:19
arborism+1 on under_score. also, I agree w/ Jay's comments on the current JSON schema (which is not mentioned in that aforementioned wiki)20:19
juicethat is, if I were to run our api through several code generator or object binding frameworks which one works more consistently?20:19
*** yogesh has joined #openstack-meeting-alt20:20
SlickNikI don't think we need to arrive at a consensus this very moment. I'd like to read up on it a bit more and revisit this when hub_cap is around as well.20:20
imsplitbit+1 arborism20:20
imsplitbitand +1 jay's comment20:20
vipulwhat comment?20:21
vipuloh recall a email thread...20:21
dmakogon_what is the next topic ?20:21
dmakogon_#topic MongoDB support20:22
SlickNikWe're still doing action items, dmakogon_20:22
vipul#link http://lists.openstack.org/pipermail/openstack/2013-August/000850.html20:22
SlickNikthanks vipul20:22
arborism(thanks for the assist on that link vipul, you beat me ;) )20:22
SlickNikokay let's move on to the next action item20:23
SlickNikcp16net add the database model to the scheduled_task wiki20:23
cp16neti've yet to do that...20:23
cp16neti have it on my list20:24
SlickNikokay, do you want to re-action it?20:24
cp16netyes plz20:24
vipul#action cp16net add the database model to the scheduled_task wiki20:25
cp16netty vipul20:25
SlickNikthanks vipul20:25
SlickNik#action team still needs to discuss and come up with a consistent JSON notation across API (hub_cap / grapex / vipul / SlickNik)20:25
SlickNikOkay that's all for action items.20:25
SlickNikLet's move on20:25
grapexSlickNik: Ok, who has a coin to flip? :)20:25
cp16netsouds good20:25
vipulgrapex: likely going to come to that lol20:26
SlickNik#topic Update on h3/rc1/icehouse20:26
*** openstack changes topic to "Update on h3/rc1/icehouse (Meeting topic: trove)"20:26
datsun180bgrapex: http://www.random.org/coins/20:26
SlickNiktouched on that earlier.20:26
SlickNikNothing more to add.20:26
SlickNik#topic MongoDB support https://blueprints.launchpad.net/trove/+spec/mongodb-support (needs approvement)20:26
*** openstack changes topic to "MongoDB support https://blueprints.launchpad.net/trove/+spec/mongodb-support (needs approvement) (Meeting topic: trove)"20:26
SlickNikdmakogon_: that's you I believe.20:27
vipulwoah MongoDB eh20:27
dmakogon_trove should support MongoDB is popular enough20:27
SlickNikor isviridov20:27
isviridov_MongoDB is pretty common DB in NoSQL world, would like to see it in trove20:27
dmakogon_and mongo has very interesting data storing schema20:28
isviridov_need your approve20:28
arborismisn't a mongodb blueprint jumping the gun considering the clustering api isn't finalized, region support isn't finalized, parameter groups aren't finalized, etc?20:28
vipulI guess you could do a single instance mongo20:28
vipulnot sure how useful that will be20:28
demorrisno more than adding any other datastores20:28
isviridov_arborism, you are right, it is one more reason to think about cluster-api better20:28
SlickNikdmakogon_: I think we need some more info in the blueprint, about the idea and design.20:29
demorrislooking at support for it is a great set of data points to help shape all those features20:29
vipuldemorris: good point20:29
dmakogon_SlickNik: we'll do that20:29
*** yogesh has quit IRC20:29
demorriswe run the risk of under delivering on those features if we don't include it in the discussions, so I seem them as able to run in parallel20:29
vipulsince Trove is approved to support no-sql, I don't see why this would be an issue20:30
vipuljust would be a single instance thing until clusters are fully baked20:30
dmakogon_vupil: yes, why not ?20:30
dmakogon_good point20:30
cweidRather than having * number of blueprints of what other sql or no sql services we want to support why don't we work on making it a trivial task to add in new db engines..20:31
dmakogon_for now we could tweak trove for provisioning single instance of anything20:31
ashestakovcweid: +120:31
vipulcweid: I think some of those things only get easier when you actually attempt to add another datastore20:31
cweidCorrect20:32
grapexcweid: http://www.codinghorror.com/blog/2013/07/rule-of-three.html20:32
cweidbut right now we have 3 pending.20:32
SlickNikdmakogon_: I'm not sure what you mean by "tweak" trove. Trove already supports multiple managers for the guest agent.20:32
dmakogon_after cluster api will be finished, we'll try to do specification for mongo cluster20:32
arborismcweid/vipul: agreed, but the existing clustering api mail thread is already discussing 3+ datastores20:32
arborismi was just pointing out that some final consensus is needed there first, before a super-detailed mongodb spec is written20:32
grapexcweid: Well I think for now we do blue prints on new data stores, and as they come in, things in Trove should naturally become easier to reuse and more flexible (unless we screw up)20:33
vipulSure, it's not just about clustering, i think there is room for improvement in guest agent and taskmanger for example..20:33
dmakogon_grapex: +120:33
isviridov_arborism, with analizing other dbs we are getting cleare vision of cluster api also20:33
arborismcorrect, yes.20:34
dmakogon_isviridov +120:34
*** yogesh has joined #openstack-meeting-alt20:34
isviridov_there is demand of HA cluster, not just set of engines20:34
SlickNikvipul: I agree with you. I'd like to take those improvements to trove, but as part of being able to support "n" implementations, not specifically MongoDB, for example...20:34
vipulSlickNik: sure, but we have no other implementation of another engine happening in Public Trove.. (at least i have not seen much code)20:35
vipulI know we're talking about implementing Redis, and we are doing Vertica, etc..20:35
vipulbut there isn't much refactoring, pluggability work going on currently to support those20:36
kevinconwaycouldn't we just make db engines some kind of extension that we plug in?20:36
arborismsince it seems like there's quite a bit of interest in this, i'd ask that people who haven't read that mail thread do so, because it's trying to address all of the topics being brought up, at least from a generic api perspective. I'd love to see comments about guest/taskmanager refactorings as well.20:36
cp16netvipul: yeah i agree and that leads to me to thinkin not much *needs* to change now20:36
cweidvipul: here is Trove sertup to support Redis. https://github.com/cweidenkeller/trove20:37
demorristhat work is already in progress, types/version blueprint is a step in that direction20:37
grapexvipul: As people do new db types, I think we should gate them on making sure the code is refactored enough that they don't stick out like a sore thumb or create issues, naturally putting pressure on keeping the code clean and making it more pluggable as the implementation count increases.20:37
kevinconwayarborism: link to thread?20:37
vipulcweid: thanks20:37
SlickNikI'm totally good with this, but I'd like to see more details on what  changes are needed added to the blueprint. Things like "We need to support X for better multi-engine support in trove", and not necessarily "We need to support Y because MongoDB"20:37
vipulgrapex: +120:37
SlickNikyup agree with grapex as well.20:38
vipulSlickNik: agreed, let's use the Mongo BP as a place to do this20:38
arborismkevinconway: http://lists.openstack.org/pipermail/openstack/2013-August/000719.html20:38
demorrisSlickNik: agree, this is step one to that - https://wiki.openstack.org/wiki/Trove/trove-versions-types20:39
arborismspecifically the gist I provided, talking about how to generically support cassandra + mongo + mysql + regions20:39
vipulcweid, cp16net: lookign at https://github.com/cweidenkeller/trove/blob/master/trove/guestagent/manager/redis.py -- i see a lot of duplication between that and mysql.py20:39
vipulseems like that would be a perfect opportunity to create some sort of an interface..20:39
demorrisright now sure you can make whatever run in Trove, but you can't actually run multiple DB engines and types on the same install20:39
grapexdemorris: Maybe we do need to do some bare minimum work to make running multiple DB engines (aka service_types) at once possible- and just make which ones are enabled configurable. Then we should all agree to be a bit lax with these new db types-20:40
arborism+1 grapex20:40
*** msisk has quit IRC20:41
isviridov_grapex, +120:41
cp16neti agree we need to be able to (dis)(en)able service types20:41
SlickNikagreed grapex.20:41
grapexand let code for them get checked in without being 100% done. I don't like that, but there will need to be changes to make Trove more flexible while the Mongo and Redis guys add there work, so we'll need to gate a bit less than usual (i.e. features for these types won't have to work 100% before a commit)20:41
vipulsure, grapex.  I'd welcome changes that really make it pluggable20:42
* grapex wishes he'd spelled "there" "their"20:42
datsun180bgrapex: forty lashes20:42
vipulto be continued?20:43
grapexvipul: So the issue is, will these changes be led by the veterans or the people making new DB types? I think the pressures of what everyone's boss wants them to do will mean the new DB implementers may need to make it pluggable, but the friction is they may not always know the greatest way to do that since they're a bit new to the project.20:43
SlickNikLooking like one to me.20:44
SlickNikSo with the bp in question though; I'd like to see a bit more definition in what this entails and how much of the trove-core code needs to change for it.20:45
vipulgrapex: sure, it could be the vets.. I doubt we'd be abel to refactor everythign necessary for anothre service type20:45
grapexPlus, we don't really always know what it would take to add Redis or Mongo since we're not adding them ourselves, so I guess my point is we should allow some limited Redis and Mongo code to get in early on.20:45
grapexAnd lax our standards to jump start the conversation- just for a bit, and just so long as nothing that's working today breaks.20:45
*** yogesh has quit IRC20:45
vipulgrapex: i'm cool with that20:45
SlickNikSo I'd love for it to drive other changes in trove-core to make it more pluggable.20:46
vipulit's gonna have to be a combination of us going in there and refactoring, and also code review suggestions20:46
grapexvipul: I think so.20:46
*** isviridov_ has quit IRC20:46
*** yogesh has joined #openstack-meeting-alt20:47
vipultime check :)20:47
SlickNikSo what I'm hearing is approve the bp for an initial stab at adding mongo20:47
SlickNikWhoops.20:47
dmakogon_i thinks we've done with Mongo BP20:47
SlickNikokay move on for now...20:48
SlickNikto be continued.20:48
SlickNik#topic virgo based guest-agent (https://github.com/racker/virgo, https://github.com/racker/virgo-base)20:48
*** openstack changes topic to "virgo based guest-agent (https://github.com/racker/virgo, https://github.com/racker/virgo-base) (Meeting topic: trove)"20:48
*** arborism has left #openstack-meeting-alt20:48
dmakogon_who want to tell us about this client >20:48
dmakogon_?20:48
SlickNikWho added this to the agenda?20:48
*** isviridov_ has joined #openstack-meeting-alt20:48
vipulskip20:49
SlickNikhmm…okay.20:49
SlickNikmoving on.20:49
isviridov_was in open discussion20:49
demorriswhy not discuss it20:49
vipulwho knows about it20:49
SlickNikdemorris: who's the right person to discuss it?20:50
vipuli heard it for the first time yesterday20:50
dmakogon_anyone have something to tell? discuss ?20:50
ashestakovi tried to research virgo today, where is server part for it?20:50
vipulI think it would be just the agent20:50
cp16netits just an agent20:50
isviridov_it was mentioned as on of possible implementation for guest-agent, any info about it?20:50
ashestakovto where it reporting?20:50
grapexVirgo is the guest agent used by Rackspace monitoring20:50
demorrisit is a lightweight C-based agent with extensible Lua scripting for agent logic20:51
ashestakovcan it receive rpc calls?20:51
grapexIf whoever raised it isn't here to talk about it I think we should move on- its basically an agent framework of sorts written on top of luvit, which is NodeJS for Lua20:51
SlickNikI think this discussion might be best suited for #openstack-trove after the meeting (since it's more of a knowledge sharing one)20:51
isviridov_let us move  on20:51
SlickNik#topic trove refactoring: guestagent main issues (dmakogon)20:51
*** openstack changes topic to "trove refactoring: guestagent main issues (dmakogon) (Meeting topic: trove)"20:51
dmakogon_my point20:52
dmakogon_GA issues20:52
dmakogon_Weaken trove.guestagent.manager.mysql & .mysql_service dependency on trove.instance.models -- actually only small set of constants and one simple persistent model is required, not the whole bunch of code20:52
dmakogon_Same with trove.guestagent.backup vs trove.backup.models20:52
dmakogon_trove.guestagent.strategies should not use trove.common.remote. The latter pulls lots of stuff but only trivial one-line call is actually needed20:52
dmakogon_Check trove.guestagent.manager.mysql.mysql_service dependency on trove.extensions.mysql.models (may be not so easy/important)20:53
vipuldmakogon_: nice! with conductor, the models dependencies are gone20:53
dmakogon_vipul: thanks20:53
SlickNikdmakogon_: There's also another bp out to separate the guest agent into it's own repo / package to decouple it further.20:53
SlickNikSo this is all goodness.20:53
SlickNikAnd if you opened a bug and fixed some of these issues, I'm sure no-one here would object :)20:54
vipulplease add these to that bp, just to track them20:54
*** jcoufal has joined #openstack-meeting-alt20:54
dmakogon_SlickNick: we don't wont to extract GA to separate repo20:54
dmakogon_SlickNik: we want to break dependencies20:55
dmakogon_this is the main goal20:55
grapexdmakogon_: If it got its own repo it would become skinny quick.20:55
vipuldmakogon_: at some point, for packaging pusposes we should also consider moving it to a spearate repo20:55
grapexI know the two goals can be made seperate20:55
grapexbut one would help the other.20:55
vipulgrapex: +120:55
SlickNikI'm totally fine with tackling the two separately.20:55
SlickNikBut they're related.20:55
dmakogon_vipul: i thinks, not20:55
dmakogon_we should break deps and keep project together20:56
isviridov_what about common code for both projects?20:56
vipuloslo?20:56
robertmyersdmakogon_: that is not allowed20:56
isviridov_constants, so on20:56
robertmyersonly one setup.py per git repo20:56
cp16netthere is common agent code in oslo20:56
grapexdmakogon_: I would like fewer repos myself, but alas, tis not the way of OpenStack.20:56
vipulok we need to revist this i think20:57
SlickNikthis seems like a tangent.20:57
vipul3 mins..20:57
kevinconwaywe could put each daemon in it's own repo!20:57
SlickNikLet's revisit this and keep going20:57
isviridov_seems better to keep it in one repo, or api should be defined20:58
SlickNik#topic versions / service_types20:58
*** openstack changes topic to "versions / service_types (Meeting topic: trove)"20:58
ashestakovits mine20:58
ashestakovlets see this one again https://gist.github.com/andreyshestakov/b1f1b06fd4aef18011ea20:58
SlickNiktake it away, ashestakov20:58
isviridov_also affects cluster api20:58
vipulashestakov: why separate the service_type_id and verstion_id?20:59
vipulshoudln't they be grouped (on instance create)20:59
ashestakovvipul: we disscussed this on previos meeting20:59
vipulok missed that then21:00
ashestakovversion_id is optional, you should specify it only you have multiple active versions21:00
ashestakovthere another issue21:00
vipultehy could still be grouped, since they are related things21:00
*** NikitaKonovalov has joined #openstack-meeting-alt21:01
ashestakovin that spec, once we eliminated service_type as it is now (eg, mysql and percona), we should add same parameter21:01
grapexvipul: I agree, it optimizes the case with no multiple versions but it less organized if you do have them.21:01
*** jodom has joined #openstack-meeting-alt21:01
*** asavu has quit IRC21:01
vipulashestakov: how about talking about it in openstack-trove later21:02
ashestakovvipul: after this meeting?21:02
vipulsoem folks might be leaving21:02
SlickNikyup, let's talk about it immediately after this meeting.21:03
vipulok we can do that too21:03
kevinconwayif it's a meeting time you should probably reschedule it for next time as well21:03
SlickNikOr we can pick another time if folks are leaving.21:03
*** jodom has quit IRC21:03
kevinconwaytime = item21:03
SlickNikLet's move on for now21:03
SlickNik#topic guest_agent service registry (dict_opt vs single opt)21:03
*** openstack changes topic to "guest_agent service registry (dict_opt vs single opt) (Meeting topic: trove)"21:03
SlickNikwho's got this one?21:04
grapexSo I'll comment21:04
vipulplease do21:04
grapexIs this about the guest config file having both a dictionary of managers, and a key to which of those managers to use?21:04
vipulyes21:04
grapexI don't get the utility of it, as it appears the dictionary isn't used out of the bin script21:05
grapexMaybe I missed something?21:05
vipulI think the idea is if we want to suppot a single package of guest agent that support >1 service types21:05
*** IlyaE has quit IRC21:05
vipulhow do we dynamically load the 'manager'21:05
vipulbased on the service type of the instance21:05
*** jrodom has quit IRC21:05
grapexI guess my issue is the manager could be as easily loaded by specifying the class name21:05
vipulas a single conf entry?21:06
grapexYes21:06
vipulyes you could do that..21:06
*** pcm_ has quit IRC21:06
vipulmeans you have different confs for different service types21:06
vipuli guess there is a bit my dynamicism if you go with dict21:06
vipulbecause the same conf can be resued21:06
SnowDust+1 vipul on that21:06
isviridov_+1 vipul21:07
grapexHow? To change which manager is loaded, you have to still change the conf21:07
dmakogon_vipul: i thinks we could do dynamic module deliveries21:07
vipulthe conf would contain all possible managers21:07
dmakogon_vipul: yes21:07
vipulservie_type (hopefully in the future) is something that will be passed into guest_info21:07
dmakogon_than we do dymamic load21:07
grapexAh21:07
SlickNikgrapex: I think the idea would be to have all managers in the conf, and the pick the manager based on the service_type (in the rpc call?)21:07
*** kiall has quit IRC21:07
ashestakovvipul: backup/restore strategies still using mysql impl21:07
vipulrpc call would be too late21:07
grapexSlickNik: Ok- I thought that maybe that was the plan.21:08
vipulyea, we wnat to gradually configure the backup / restore strategies as well21:08
vipulthis is step #1 to getting the right manager loaded21:08
grapexOk, I feel it could be YAGNI but I'm ok if we're all on board with making use of the dictionary very soon21:08
dmakogon_about automated backups21:09
*** bdpayne has joined #openstack-meeting-alt21:09
dmakogon_Automated backup design: 1. Define limits for backups per tenant. 2. Define storing strategy. 3. Define timing strategy. 4. Define cluster backup strategy than 1-3 for cluster21:09
SlickNikYeah, this is the same thing with backup / restore.21:09
*** NikitaKonovalov has quit IRC21:09
dmakogon_what do you say ?21:10
SlickNikdmakogon_: You might want to talk to cp16net about that as feedback for him.21:10
SlickNikI'm fine with the dict_opt21:10
dmakogon_SlickNic: ok21:10
SlickNikanything else to add, vipul?21:10
vipulno i'm good...21:10
dmakogon_about registry, cool with dict21:10
SlickNikOkay, #topic open discussion21:11
kevinconwaydatsun180b: Conductor code?21:11
SlickNik#topic Open Discussion21:11
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"21:11
juiceJust one closing note - I did a bit of JSON API comparison - of 13 sites: 8 use _ (underscore); 3 use camelCase; 1 uses - (dash); and the last one was all lowercase21:11
vipuljuice: nice!21:11
datsun180bkevinconway: pay attention, both reviews are up21:11
vipulwe shoudl look at things like jackson too, see if they expect a certain type21:12
vipulmy guess is probably not21:12
SlickNikGood info juice.  I'm leaning towards _ too. (mostly because it's what we already use in the majority of situations)21:12
juicejackson you can specify what ever field name you like21:12
juice@XMLElement("my_dogs_name") or something like that21:12
*** kebray has quit IRC21:12
*** dina_belova has joined #openstack-meeting-alt21:12
SlickNikOkay, I think we're good with the meeting. Let's take further discussion to #openstack-trove21:12
SlickNikThanks all, and sorry for the OT.21:13
SlickNik#endmeeting21:13
*** openstack changes topic to "OpenStack meetings (alternate)"21:13
openstackMeeting ended Wed Sep  4 21:13:09 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-04-20.02.html21:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-04-20.02.txt21:13
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-04-20.02.log.html21:13
grapexNo problem. Thanks SlickNik!21:13
vipulcoo21:13
*** esp2 has left #openstack-meeting-alt21:15
*** ashestakov has left #openstack-meeting-alt21:15
*** dina_belova has quit IRC21:17
*** isviridov_ has quit IRC21:17
*** robertmyers has left #openstack-meeting-alt21:18
*** SnowDust has left #openstack-meeting-alt21:18
*** kebray has joined #openstack-meeting-alt21:19
*** eankutse has quit IRC21:21
*** jcoufal has quit IRC21:25
*** sarob has quit IRC21:34
*** sarob has joined #openstack-meeting-alt21:35
*** NikitaKonovalov has joined #openstack-meeting-alt21:35
*** sarob has quit IRC21:39
*** kiall has joined #openstack-meeting-alt21:40
*** NikitaKonovalov has quit IRC21:40
*** yogesh has quit IRC21:40
*** yogesh has joined #openstack-meeting-alt21:46
*** yogesh has quit IRC21:47
*** dmakogon_ has quit IRC21:53
*** datsun180b has quit IRC21:54
*** jcru has quit IRC21:54
*** sacharya has quit IRC21:54
*** jmcbride has joined #openstack-meeting-alt21:58
*** yogesh has joined #openstack-meeting-alt21:59
*** yogesh has quit IRC22:01
*** jmcbride has quit IRC22:05
*** NikitaKonovalov has joined #openstack-meeting-alt22:06
*** asavu has joined #openstack-meeting-alt22:10
*** NikitaKonovalov has quit IRC22:11
*** dina_belova has joined #openstack-meeting-alt22:13
*** demorris has quit IRC22:14
*** dina_belova has quit IRC22:18
*** boris-42 has quit IRC22:19
*** boris-42 has joined #openstack-meeting-alt22:19
*** jmontemayor has quit IRC22:19
*** pdmars has quit IRC22:20
*** yogesh has joined #openstack-meeting-alt22:25
*** sarob has joined #openstack-meeting-alt22:25
*** sarob has quit IRC22:30
*** yogesh has quit IRC22:31
*** sarob has joined #openstack-meeting-alt22:33
*** yogesh has joined #openstack-meeting-alt22:36
*** eankutse has joined #openstack-meeting-alt22:36
*** jasonb365 has quit IRC22:37
*** NikitaKonovalov has joined #openstack-meeting-alt22:37
*** sarob has quit IRC22:41
*** sarob has joined #openstack-meeting-alt22:41
*** yogesh has quit IRC22:41
*** NikitaKonovalov has quit IRC22:42
*** dhellmann is now known as dhellmann_22:43
*** sarob has quit IRC22:45
*** yogeshmehra has quit IRC22:46
*** yogesh has joined #openstack-meeting-alt22:46
*** bdpayne has quit IRC22:51
*** yogesh has quit IRC22:51
*** sarob has joined #openstack-meeting-alt22:53
*** asavu has quit IRC22:54
*** sarob_ has joined #openstack-meeting-alt22:56
*** sarob has quit IRC22:59
*** dukhlov_ has quit IRC22:59
*** sarob_ is now known as sarob23:02
*** saurabhs has quit IRC23:05
*** NikitaKonovalov has joined #openstack-meeting-alt23:08
*** NikitaKonovalov has quit IRC23:13
*** dina_belova has joined #openstack-meeting-alt23:13
*** eankutse has quit IRC23:18
*** dina_belova has quit IRC23:18
*** eankutse has joined #openstack-meeting-alt23:20
*** IlyaE has joined #openstack-meeting-alt23:26
*** esp2 has joined #openstack-meeting-alt23:38
*** NikitaKonovalov has joined #openstack-meeting-alt23:39
*** amytron has quit IRC23:42
*** NikitaKonovalov has quit IRC23:43
*** sacharya has joined #openstack-meeting-alt23:48
*** grapex has quit IRC23:53
*** kebray has quit IRC23:57

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