Wednesday, 2013-08-14

*** IlyaE has joined #openstack-meeting-alt00:09
*** sarob_ has joined #openstack-meeting-alt00:10
*** sarob has quit IRC00:14
*** sarob_ has quit IRC00:14
*** tanisdl has quit IRC00:19
*** IlyaE has quit IRC00:21
*** colinmcnamara has joined #openstack-meeting-alt00:36
*** colinmcnamara1 has joined #openstack-meeting-alt00:37
*** colinmcnamara has quit IRC00:41
*** sacharya has quit IRC00:42
*** IlyaE has joined #openstack-meeting-alt00:44
*** IlyaE has quit IRC00:46
*** dina_belova has joined #openstack-meeting-alt00:51
*** dina_belova has quit IRC00:57
*** enikanorov-w has quit IRC00:57
*** enikanorov-w_ has joined #openstack-meeting-alt01:03
*** colinmcnamara1 has left #openstack-meeting-alt01:06
*** dina_belova has joined #openstack-meeting-alt01:51
*** dina_belova has quit IRC01:56
*** vkmc has quit IRC02:10
*** anteaya has quit IRC02:40
*** dina_belova has joined #openstack-meeting-alt02:52
*** dina_belova has quit IRC02:57
*** bdpayne has quit IRC03:14
*** betsy has quit IRC03:15
*** vipul is now known as vipul-away03:30
*** vipul-away is now known as vipul03:30
*** bdpayne has joined #openstack-meeting-alt03:32
*** bdpayne has quit IRC03:33
*** vipul is now known as vipul-away03:33
*** vipul-away is now known as vipul03:33
*** SergeyLukjanov has joined #openstack-meeting-alt03:43
*** dina_belova has joined #openstack-meeting-alt03:53
*** dina_belova has quit IRC03:58
*** esp1 has joined #openstack-meeting-alt04:47
*** esp1 has left #openstack-meeting-alt04:47
*** dina_belova has joined #openstack-meeting-alt04:53
*** dina_belova has quit IRC04:58
*** akuznetsov has joined #openstack-meeting-alt05:01
*** vipul is now known as vipul-away05:02
*** vipul-away is now known as vipul05:02
*** esp has joined #openstack-meeting-alt05:46
*** betsy has joined #openstack-meeting-alt05:51
*** SergeyLukjanov has quit IRC05:55
*** SergeyLukjanov has joined #openstack-meeting-alt05:56
*** esp has quit IRC05:58
*** SergeyLukjanov has quit IRC06:02
*** IlyaE has joined #openstack-meeting-alt06:24
*** markmcclain has quit IRC06:27
*** ruhe has joined #openstack-meeting-alt06:33
*** IlyaE has quit IRC06:38
*** dina_belova has joined #openstack-meeting-alt06:54
*** ruhe has quit IRC06:57
*** dina_belova has quit IRC06:58
*** dina_belova has joined #openstack-meeting-alt06:58
*** dina_belova has quit IRC07:03
*** amytron has joined #openstack-meeting-alt07:43
*** dina_belova has joined #openstack-meeting-alt07:59
*** dina_belova has quit IRC08:03
*** SergeyLukjanov has joined #openstack-meeting-alt08:04
*** akuznetsov has quit IRC08:09
*** dina_belova has joined #openstack-meeting-alt08:09
*** dina_belova has quit IRC08:14
*** dosaboy has joined #openstack-meeting-alt08:15
*** ruhe has joined #openstack-meeting-alt08:29
*** SergeyLukjanov has quit IRC08:44
*** akuznetsov has joined #openstack-meeting-alt08:48
*** SergeyLukjanov has joined #openstack-meeting-alt08:49
*** dkoryavov has joined #openstack-meeting-alt09:11
*** amytron has quit IRC09:55
*** enikanorov has quit IRC10:00
*** akuznetsov has quit IRC10:08
*** dina_belova has joined #openstack-meeting-alt10:10
*** dina_belova has quit IRC10:15
*** dkoryavov has quit IRC10:28
*** akuznetsov has joined #openstack-meeting-alt10:36
*** pcm__ has joined #openstack-meeting-alt10:36
*** pcm__ has quit IRC10:44
*** pcm__ has joined #openstack-meeting-alt10:44
*** dina_belova has joined #openstack-meeting-alt10:55
*** enikanorov has joined #openstack-meeting-alt10:57
*** ben_duyujie has joined #openstack-meeting-alt10:58
*** ben_duyujie has quit IRC10:59
*** tedross has joined #openstack-meeting-alt11:11
*** boris-42 has joined #openstack-meeting-alt11:31
*** dkoryavov has joined #openstack-meeting-alt11:35
*** dkoryavov__ has joined #openstack-meeting-alt11:41
*** dkoryavov has quit IRC11:41
*** dkoryavov__ has quit IRC11:43
*** dkoryavov__ has joined #openstack-meeting-alt11:44
*** tedross has left #openstack-meeting-alt11:50
*** HenryG has quit IRC12:11
*** dkoryavov__ has quit IRC12:15
*** kevinconway has quit IRC12:18
*** dkoryavov__ has joined #openstack-meeting-alt12:19
*** HenryG has joined #openstack-meeting-alt12:23
*** dosaboy has quit IRC12:27
*** pdmars has joined #openstack-meeting-alt12:30
*** SergeyLukjanov has quit IRC12:33
*** dosaboy has joined #openstack-meeting-alt12:44
*** kevinconway has joined #openstack-meeting-alt12:47
*** dina_belova has quit IRC12:51
*** dina_belova has joined #openstack-meeting-alt12:54
*** SergeyLukjanov has joined #openstack-meeting-alt12:59
*** dosaboy has quit IRC13:02
*** dkoryavov__ has quit IRC13:02
*** dkoryavov__ has joined #openstack-meeting-alt13:04
*** dosaboy has joined #openstack-meeting-alt13:06
*** pdmars has quit IRC13:28
*** pdmars has joined #openstack-meeting-alt13:29
*** rnirmal has joined #openstack-meeting-alt13:29
*** dina_belova has quit IRC13:32
*** mestery_ has joined #openstack-meeting-alt13:43
*** mestery has quit IRC13:46
*** mestery_ is now known as mestery13:57
*** tanisdl has joined #openstack-meeting-alt14:00
*** dina_belova has joined #openstack-meeting-alt14:01
*** markmcclain has joined #openstack-meeting-alt14:01
*** aignatov has quit IRC14:10
*** aignatov has joined #openstack-meeting-alt14:11
*** isviridov has joined #openstack-meeting-alt14:14
*** ruhe has quit IRC14:16
*** anteaya has joined #openstack-meeting-alt14:22
*** dkoryavov__ has quit IRC14:23
*** betsy has quit IRC14:24
*** IlyaE has joined #openstack-meeting-alt14:26
*** SergeyLukjanov has quit IRC14:28
*** akuznetsov has quit IRC14:28
*** SergeyLukjanov has joined #openstack-meeting-alt14:29
*** amytron has joined #openstack-meeting-alt14:32
*** amytron has quit IRC14:32
*** amytron has joined #openstack-meeting-alt14:33
*** esker has joined #openstack-meeting-alt14:38
*** jmontemayor has joined #openstack-meeting-alt14:44
*** dkoryavov__ has joined #openstack-meeting-alt14:52
*** dina_belova has quit IRC14:52
*** markmcclain has quit IRC14:53
*** dkoryavov__ has quit IRC14:58
*** dina_belova has joined #openstack-meeting-alt14:58
*** SergeyLukjanov has quit IRC15:01
*** akuznetsov has joined #openstack-meeting-alt15:02
*** dkoryavov__ has joined #openstack-meeting-alt15:02
*** SergeyLukjanov has joined #openstack-meeting-alt15:03
*** sacharya has joined #openstack-meeting-alt15:03
*** ruhe has joined #openstack-meeting-alt15:03
*** vkmc has joined #openstack-meeting-alt15:07
*** vkmc has joined #openstack-meeting-alt15:07
*** markmcclain has joined #openstack-meeting-alt15:13
*** dkoryavov__ has quit IRC15:17
*** dkoryavov__ has joined #openstack-meeting-alt15:18
*** Riddhi has joined #openstack-meeting-alt15:23
*** dosaboy has quit IRC15:24
*** dosaboy has joined #openstack-meeting-alt15:26
*** betsy has joined #openstack-meeting-alt15:28
*** dkoryavov__ has quit IRC15:29
*** ruhe has quit IRC15:43
*** akuznetsov has quit IRC15:43
*** bdpayne has joined #openstack-meeting-alt15:45
*** Riddhi has quit IRC15:47
*** jergerber has joined #openstack-meeting-alt15:51
*** esp1 has joined #openstack-meeting-alt15:54
*** betsy is now known as bluzader15:55
*** esp1 has quit IRC15:55
*** vkmc has quit IRC16:09
*** IlyaE has quit IRC16:11
*** dina_belova has quit IRC16:19
*** dina_belova has joined #openstack-meeting-alt16:22
*** markmcclain has left #openstack-meeting-alt16:22
*** markmcclain has joined #openstack-meeting-alt16:23
*** SergeyLukjanov has quit IRC16:26
*** dina_belova has quit IRC16:26
*** esp1 has joined #openstack-meeting-alt16:33
*** esp1 has left #openstack-meeting-alt16:35
*** akuznetsov has joined #openstack-meeting-alt16:35
*** tsimmons has joined #openstack-meeting-alt16:38
*** dina_belova has joined #openstack-meeting-alt16:53
* simonmcc twiddles thumbs…16:54
*** mugsie has joined #openstack-meeting-alt16:54
*** boris-42 has quit IRC16:57
*** eankutse has joined #openstack-meeting-alt16:57
*** markmcclain has quit IRC16:58
*** vinodmr has joined #openstack-meeting-alt16:58
*** SergeyLukjanov has joined #openstack-meeting-alt16:58
kiall#startmeeting17:00
openstackkiall: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'17:00
kiall#startmeeting designate17:00
openstackMeeting started Wed Aug 14 17:00:26 2013 UTC and is due to finish in 60 minutes.  The chair is kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: designate)"17:00
openstackThe meeting name has been set to 'designate'17:00
kialland - I just broke my chair. heh. 2 sec17:00
bluzader:O17:00
eankutse:-)17:00
kiallOkay :)17:01
*** dina_belova has quit IRC17:01
simonmccmugsie get's 2 broken chairs on his first dat17:01
kiallHeyas! Who's about for the Designate/DNSaaS meeting?17:01
simonmcco/17:01
vinodmrvinod here17:01
bluzaderme17:01
mugsieo/17:01
eankutseeankutse17:01
tsimmonsMe :D17:01
kiallAgenda is short - Another round of APIv2.. Unless anyone has an item?17:02
kiall#topic APIv217:02
*** openstack changes topic to "APIv2 (Meeting topic: designate)"17:02
eankutseAPv2 is good17:02
kiallSo - over the last few days, a discussion has started on the openstack-dev mailing list around pagination in the openstack APIs17:02
kiall#link http://lists.openstack.org/pipermail/openstack-dev/2013-August/013493.html17:03
kiallFirst email in the thread ^17:03
*** CaptTofu has joined #openstack-meeting-alt17:03
kiallI'll summarize though..17:03
* CaptTofu is here17:03
kiallSo - page/per_page is being removed from the Keystone V3 API, in favor of marker/limit17:03
kiallThe thread tends to go 1 of 2 ways.. either people say marker/limit is higher performance, or the Horizon guys say it's next to impossible to use in a UI17:04
eankutseso Designate will confirm - right?17:04
eankutse*conform*17:04
kiallI've no real preference for anything other than conforming to the standards that the other projects set..17:04
vinodmrOne of the objections cited in favor of page/per_page was that any page can be accessed rather than moving in the forward direction and accessing just the previous page.17:05
mugsiesame17:05
kiallDoes anyone have a good reason why we shouldn't conform?17:05
eankutseSemantically both are the same17:05
bluzaderI don't think any of us are UI guys17:05
eankutseyes?17:05
kiallI think UI's are painful with limit/marker.. And traditional pagination controls are out..  BUT Horizon etc will get the necessary parts to make it work17:05
eankutseso conforming to the parameter name is fine with me17:06
kiallmugsie does lots of UI work :)17:06
mugsiefor the next week ;)17:06
*** msisk_ has joined #openstack-meeting-alt17:06
kialleankutse: well, it's much more than the param name17:06
kiallso page=1&per_page=1017:06
simonmccI was going to say that UI is probably the most likely consumer of our customer facing DNS solutions - so should help direct a choice in favour of UI friendly pagination17:06
kiallvs marker=<UUID of last item on previous page>&limit=1017:06
bluzaderI would lean more towards making the UI easier rather than conforming for no reason17:07
kialland to go backwards, marker=<UUID of last item on previous page>&limit=10&sort_dir=DESC17:07
*** markmcclain has joined #openstack-meeting-alt17:07
vinodmrWould the marker in designate be a UUID that is randomly generated or that keeps increasing as time progresses?17:07
kiallbluzader: Yea - I tend to agree, but the "offical" UI, and any other copropate custom UIs are going to have to deal with limit/marker anyway17:07
*** sarob has joined #openstack-meeting-alt17:07
ekarlso-ello folks17:08
kiallvinodmr: it would be the ID of the last domain/record/etc on the page your looking at17:08
kiallcorporate*17:08
mugsieUIs can store the previous markers, as pointed out in the thread17:08
tsimmonsJust doesn't seem as clean to me, but conforming is probably the right thing to do especially if other people are going to have to figure out UI's before us.17:08
kialltsimmons: yea.. I know the feeling :)17:09
kiallAnyway - I think the UIs that deal with nova/glance/keystone/designate will support this style of pagination.. So, I argue we conform17:09
bluzaderttsimmons: true17:09
kiallSo - Does anyone think we should stick with page/per_page (or page/limit) ?17:10
vinodmrHas Horizon already done pagination with nova/glance/keystone etc?17:10
CaptTofuconforming would also bode well for things like incubation17:10
kiallvinodmr: ehh - I don't think so to be honest17:10
kiallCaptTofu: yea.. good point.17:10
kiallI've never noticed pagination in horizon anyway...17:11
kiallSo ..17:11
bluzaderAre all OpenStack projects going to change?17:11
bluzaderDoes Keystone set the standard?17:11
kiallbluzader: I believe glance and nova already do it this way17:12
bluzaderAh. Then it makes sense that we change17:12
kiall#startvote Should we conform to the limit/marker pagination pattern in the V2 API? yes, no, maybe17:12
openstackBegin voting on: Should we conform to the limit/marker pagination pattern in the V2 API? Valid vote options are yes, no, maybe.17:12
openstackVote using '#vote OPTION'. Only your last vote counts.17:12
kiall#vote yes17:12
kiallso - lets get a show of hands!17:12
vinodmr#vote yes17:12
mugsie#vote yes17:12
bluzader#vote yes17:12
tsimmons#vote yes17:13
eankutse#vote yes17:13
msisk_#vote yes17:13
kiallAny stragglers? simonmcc / CaptTofu ?17:13
simonmcc#vote yes17:13
CaptTofu#vote yes17:13
kiall5 ... 4 ... 3...17:13
kiall#endvote17:13
openstackVoted on "Should we conform to the limit/marker pagination pattern in the V2 API?" Results are17:13
openstackyes (9): eankutse, simonmcc, bluzader, CaptTofu, tsimmons, vinodmr, mugsie, msisk_, kiall17:14
kiallSo .. that's a yes. I'll update the spec.17:14
bluzaderI've got a quick question on v2API17:14
bluzaderDo the RecordSets replace Records, or are there Records and RecordSets17:14
kiallbluzader: So, yes and no .. RecordSets brings our model closer to the various DNS specs, and makes it MUCH easier to prevent out-of-spec values.17:15
*** IlyaE has joined #openstack-meeting-alt17:15
kiallThere won't be a separate /records API endpoint, but there is an array of records which belong to a RecordSet in the /recordsets/1234 response17:16
kiallMake sense?17:16
bluzaderI'm not sure. It makes a big change from the way we're currently doing our DNS17:17
eankutseBut the spec also indicates that all records in a RecordSet should have the same TTL and that seems to be too much of a restriction17:17
bluzaderI, obviously, need to read the spec more17:17
bluzadereankutse: I agree17:17
bluzaderThat part doesn't make sense to me at all17:18
kialleankutse: all good DNS servers will pick the lowest TTL from all the records wit the same (rclass, rtype, rname) tuple and serve it17:18
kiallSo - If you have 2 A records at "www.example.org.", one with TTL 3600 and one with TTL 300, both will be served with 30017:18
kialland if they don't..17:18
kiallthey the load balancing you are expecting will fail.17:19
*** sarob has quit IRC17:19
kiallafter 300 seconds, resolvers will discard the 300 one, and keep the 3600 one..17:19
kiallfor the next 3300 seconds, it's as if you only have 1 A record for "www.example.org."17:19
*** sarob has joined #openstack-meeting-alt17:19
bluzaderhmm17:19
bluzaderAs I said, I, obviously, need to spend more time in the spec to fully understand the pros and cons17:20
kiallThe original specs allowed for differing TTL for a given (rclass, rtype, rname). But it proved to be broken and was depreciated in rfc218117:20
bluzaderAh. I didn't realize that17:20
bluzaderNow RecordSets are making more sense to me17:21
kiallYea - I was surprised the first time I read that RFC too.. It gives a good explanation of the issues from memory.17:21
vinodmrkiall: So in your eg. when you do a get recordset, you would get both the A records, but only 1 TTL value of 300.  Is that right?17:21
kiall#link http://www.ietf.org/rfc/rfc2181.txt17:22
bluzadervinodmr: that's right17:22
kiallvinodmr: correct, you would get back {"ttl": 300, "records": [<record 1>, <record 2>], ...}17:22
bluzadervinodmr: the only thing that varies in a recordset are the IP addresses17:23
kialland your DNS server will spit out both records, with the same TTL (which it should do anyway, even if you configure 2 different TTLs)17:23
*** markmcclain has quit IRC17:23
kiallwell - the rdata differs. SO for a A, that's just the IP address17:23
kiallfor SRV, it's priority, port, weight, target17:23
kialletc17:23
bluzaderkiall: right. I was thinking of only A records17:24
kialland for MX priority+exchange differ :)17:24
bluzaderIt's only the "data" that varies17:24
*** sarob has quit IRC17:24
kiallAlso - as another datapoint .. Amazon's Route53 went the RecordSet route from memory17:24
kiall(That's wasn't a deciding factor in any way!P17:25
kiall..)*17:25
*** markwash has joined #openstack-meeting-alt17:25
bluzaderkiall: Thx for explanation. It's making more sense to me now17:25
kiallSo - Any lingering concerns over the use of RecordSet's?17:25
bluzaderkiall: Not from me at this point.17:26
vinodmrIs there any way to know the acutal TTL values that are configured using the API?17:26
*** IlyaE has quit IRC17:26
kiallvinodmr: yea, the RecordSet will include the configured TTL for all records which are part of that RecordSet (or null, if the recordset inherits the default TTL from the parent domain)17:27
kiallhttp://pastie.org/private/dke2mocexwilfwpqcmvivg <-- Route53's XML representation of a RecordSet17:27
kiallConceptually, that's very similar to what we propose for the V2 API17:28
kiallOkay .. Next up :)17:28
kiallwe wanted to get any final feedback on the V2 API conventions, and if there is nothing else, we'll start merging framework code ASAP. I'll likely merge the base framework tomorrow. i.e. this one -> https://review.openstack.org/#/c/39077/17:29
kiallThen, over the next week or two finalize any core changes needed to make the conventions work.17:29
kiall#action Kiall to update spec for limit/marker/sort_dir/sort_key17:30
kiall(Forgot to add ^ earlier)17:30
kiallAnybody have any more comments/suggestions/issues with the conventions used in the APIv2 spec? :)17:31
simonmccI have no issues at this stage17:31
eankutsenone17:32
kiallOkay .. I'll take that as a no from everyone! :)17:32
kiall#topic Any other business? Ask away.17:32
*** openstack changes topic to "Any other business? Ask away. (Meeting topic: designate)"17:32
eankutseI'll read up on the updates of the doc again17:32
kiallSo - Anything else from anyone at all? Doesn't have to be APIv2 related :)17:32
eankutseHow's progress on State Machine17:32
simonmccState Machine?17:33
kiallsimonmcc: the domain/record "status" field.. e.g PENDING, ACTIVE etc17:33
kialleankutse: I've not began writing any code - Before that gets added, backends need to become async capable.17:34
eankutseyes. Kiall was coming up with one for zones the other day17:34
kiallOtherwise, the status are always just "ACTIVE" and there are no transitions really :)17:34
eankutsek17:34
kiallThe current plan is - each of the backend methods will return a dict with a couple of keys in it, for status stuff, there will be "complete" = True/False key17:35
eankutsek17:35
kiallif complete = True, we'll do what we do today, and return a synchronous status code with status=ACTIVE17:35
bluzaderkiall: that sounds cool. Have you written a blueprint for it?17:36
kialland if complete = False, we'll return the async status code.. and expect the backend to update the record/domain status whenever it's completed it's change17:36
kiallbluzader: semi :) https://blueprints.launchpad.net/designate/+spec/domain-status17:36
kiallit's expanded from there though17:36
kialleankutse: do you have the link to the state machine graphic I sent you?17:37
eankutseI can find it17:38
kiall#link https://dl.dropboxusercontent.com/u/1400487/graphviz-fd80799c9423325e8616080d6ae7d1af8a96b5f6.png17:39
kiall#link https://dl.dropboxusercontent.com/u/1400487/graphviz-9c55129fd4d85273bcd3c6dc6fdae2471124e420.png17:39
kiallone for domains, one for recordsets17:39
eankutseThx17:39
*** sballe has joined #openstack-meeting-alt17:39
kiallNo problem :)17:39
kiallSo, the domain status and async backend stuff really ties into each other.. and the async backend stuff needs to come first17:40
*** rnirmal has quit IRC17:40
eankutseyes17:40
kiallOkay - Any more questions/comments before we call it a day?17:41
eankutsenot me17:41
vinodmrnone from me either17:41
mugsienope17:41
simonmccany progress on a designate face to face before HK?17:41
kiallOkay - That's all :) Hopefully we'll have some of this V2 API stuff merged and ready to play with before next weeks meeting.17:41
kiallsimonmcc: I think there was budget issues on the HP side ..17:42
simonmcc:-)17:42
kiallHK has pushed the travel budget pretty far this year :(17:42
*** RajeshMohan has quit IRC17:42
CaptTofu@simonmcc I need to re-ask17:43
mugsieall the more reason we should all go to HK ;)17:43
simonmccI don't think RAX are planning on going to HK?17:43
kiallOkay - Thanks everyone :) Speak in #openstack-dns later!17:43
CaptTofu@simonmcc I think management was thinking of possibly some place a bit inbetween Ireland and TX17:43
kiall#endmeeting17:43
*** openstack changes topic to "OpenStack meetings (alternate)"17:43
openstackMeeting ended Wed Aug 14 17:43:49 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-08-14-17.00.html17:43
simonmcccya, tahnks17:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-08-14-17.00.txt17:43
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-08-14-17.00.log.html17:43
kiallHP + RAX discussion should really be outside the meeting :P17:44
*** RajeshMohan has joined #openstack-meeting-alt17:44
*** sarob has joined #openstack-meeting-alt17:47
*** vinodmr has left #openstack-meeting-alt17:48
*** msisk_ has quit IRC17:58
*** msisk has joined #openstack-meeting-alt18:00
*** dina_belova has joined #openstack-meeting-alt18:01
*** dina_belova has quit IRC18:02
*** dina_bel_ has joined #openstack-meeting-alt18:02
*** Riddhi has joined #openstack-meeting-alt18:08
*** dosaboy has quit IRC18:08
*** akuznetsov has quit IRC18:15
*** tsimmons has quit IRC18:15
*** akuznetsov has joined #openstack-meeting-alt18:18
*** eankutse has quit IRC18:19
*** dosaboy_1 has joined #openstack-meeting-alt18:23
*** dosaboy__ has quit IRC18:25
*** lifeless has quit IRC18:28
*** markmcclain has joined #openstack-meeting-alt18:39
*** eankutse has joined #openstack-meeting-alt18:46
*** sacharya1 has joined #openstack-meeting-alt18:58
*** sacharya has quit IRC19:00
*** tsimmons has joined #openstack-meeting-alt19:03
*** _crobertsrh has quit IRC19:05
*** crobertsrh has joined #openstack-meeting-alt19:07
*** bdpayne has quit IRC19:09
*** IlyaE has joined #openstack-meeting-alt19:17
*** jasonb365 has joined #openstack-meeting-alt19:21
*** rnirmal has joined #openstack-meeting-alt19:23
*** dosaboy_1 is now known as dosaboy19:23
*** ruhe has joined #openstack-meeting-alt19:24
*** vipul is now known as vipul-away19:24
*** vipul-away is now known as vipul19:28
*** vipul is now known as vipul-away19:32
*** key2 has joined #openstack-meeting-alt19:32
*** lifeless has joined #openstack-meeting-alt19:39
*** ruhe has quit IRC19:39
*** bdpayne has joined #openstack-meeting-alt19:45
*** yidclare has joined #openstack-meeting-alt19:45
*** hub_cap has joined #openstack-meeting-alt19:45
*** vipul-away is now known as vipul19:45
*** akuznetsov has quit IRC19:48
*** dukhlov has joined #openstack-meeting-alt19:48
*** IlyaE has quit IRC19:50
*** KennethWilke has joined #openstack-meeting-alt19:53
*** SergeyLukjanov has quit IRC19:58
cweidKennethWilke: I CHOOSE YOU.19:58
KennethWilkeo/19:58
*** sacharya1 has quit IRC19:58
SlickNik\o19:59
hub_caplol19:59
*** datsun180b has joined #openstack-meeting-alt19:59
*** esp1 has joined #openstack-meeting-alt19:59
vipulo/19:59
cweido/19:59
*** jcru has joined #openstack-meeting-alt19:59
cp16netword19:59
*** grapex has joined #openstack-meeting-alt19:59
*** robertmyers has joined #openstack-meeting-alt19:59
esp1o/19:59
*** imsplitbit has joined #openstack-meeting-alt19:59
datsun180bhello19:59
cp16net0/20:00
konetzed\o20:00
hub_cap#startmeeting trove20:00
openstackMeeting started Wed Aug 14 20:00:08 2013 UTC and is due to finish in 60 minutes.  The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: trove)"20:00
openstackThe meeting name has been set to 'trove'20:00
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting20:00
grapexo/20:00
vipulhub_cap: refresh if you haven't20:00
kevinconway\\o//20:00
*** NehaV1 has joined #openstack-meeting-alt20:00
djohnstoneo/20:00
vipulwoah kevinconway20:00
hub_capok there was only 1 action item called DOC DOC DOC20:01
*** NehaV1 has left #openstack-meeting-alt20:01
hub_capkevinconway: are you doc oc?20:01
imsplitbito/20:01
*** sacharya has joined #openstack-meeting-alt20:01
*** NehaV1 has joined #openstack-meeting-alt20:01
cp16neto^/20:01
pdmarso/20:01
hub_capi think we are still being kinda lax on the doc standards we proposed20:01
SlickNikI haven't seen that many more docstrings.20:01
amytrono/20:01
hub_capbut thats ok, we will get better at screaming at people in gerrit20:01
grapexSlickNik: Is there a way to get Gerrit to enforce that?20:02
hub_capya SlickNik ive approved reviews w/o even looking...20:02
grapexI'll try to keep that in mind20:02
grapexHonestly I forgot all about it... :(20:02
SlickNikgrapex: not that I know of.20:02
hub_capno grapex.. gerrit enfoces nothing...20:02
hub_capwed have to write someting custom to get zuul / jenkins to enfoce it20:02
grapexThat's the problem with Gerrit, the lack of sentient thought20:02
SlickNikYeah, I'm going to start pushing back on code reviews because of it.20:02
hub_capya we should SlickNik20:02
*** yogesh_ has joined #openstack-meeting-alt20:02
hub_capok so lets skip to the next item20:02
kevinconwayhub_cap: pylint has an option to error if missing a doctstring. it would be retroactive for all code though20:02
juiceo/20:02
* KennethWilke takes note... add sentience to gerrit20:02
hub_capkevinconway ;)20:02
grapexkevinconway: I wonder if Zul has some trick where pylint would just apply to the diff20:03
*** saurabhs has joined #openstack-meeting-alt20:03
hub_caplets not worry about it. Core team... do our job ;)20:03
hub_capwe will enforce it manually20:03
datsun180bthat's a great way to lock away old code in a vault forever to keep from risking having to add docstrings20:03
hub_capHAH20:03
hub_cap#topic clustering api update20:03
*** openstack changes topic to "clustering api update (Meeting topic: trove)"20:03
hub_capimsplitbit: tag20:03
grapexdatsun180b: Then you have to add docstrings explaining why it's broken :)20:03
imsplitbitok20:04
imsplitbit#link https://review.openstack.org/#/c/41993/20:04
imsplitbit#link https://review.openstack.org/#/c/41995/20:04
imsplitbitclustertypes api20:04
datsun180bi say turn on the firehose and deal with the mess once instead of incrementally forever20:04
imsplitbitand support for it in troveclient20:04
imsplitbitplease review20:04
vipulwoah nice.. didn't see these before20:04
imsplitbitcause they just went up :)20:04
SlickNikthey appeared recently :)20:04
cweidimsplitbit: do they have docstrings?20:05
cweid=)20:05
imsplitbitof course20:05
imsplitbitI'll be working on the cluster api tonight20:05
imsplitbithopefully it won't take as long20:05
imsplitbitI think I got the api stuff figured out20:05
imsplitbitthis was my first foray into the world of the api20:05
vipulyou survived20:05
imsplitbityep20:06
vipulso are you going to submit the cluster api without impl?20:06
imsplitbityes20:06
vipulis it cool to return no-op?20:06
imsplitbitthen I'll submit an impl20:06
hub_capwoo we got our first reviews to not make the Havana release ;)20:06
hub_capbut srsly good work imsplitbit20:06
* hub_cap thinks u might need to abandon those to put them on a feature branch tho20:06
hub_capcan you talk to openstack-infra to see if there is a way to move a review to a feature branch in gerrit via git review?20:06
hub_cap#action imsplitbit to move his clustering reviews to a feature branch20:06
hub_cap#link https://wiki.openstack.org/wiki/Gerrit_Workflow#Long-lived_Topic_Branches20:06
imsplitbitI think if I submit the cluster api with an impl you guys will hate me for submitting a several thousand line review20:06
imsplitbit:)20:06
vipulyup, agreed20:06
imsplitbitthats all I got to say about that20:07
hub_capya hes gonna push them to a feature branch and the 2nd review will cover that part20:07
hub_capcool great work20:07
hub_capMANY people are interested in clustering20:07
SlickNikAgreed on the feature branch piece. (And the non-havana part too)20:07
hub_capok so moving on20:08
hub_cap#topic h3 update20:08
*** openstack changes topic to "h3 update (Meeting topic: trove)"20:08
hub_cap#link https://launchpad.net/trove/+milestone/havana-320:08
hub_capwe are looking good for h3 still20:08
hub_caponly 1 bug thats not fixed20:08
hub_capand 0 bps that are _not_ in progress20:08
vipulnice20:09
SlickNikhttps://bugs.launchpad.net/trove/+bug/1199507 is not assigned to anyone yet.20:09
hub_capand for some reason its only a "medium"20:09
hub_capinteresting20:09
SlickNikLooks fairly straightforward though.20:09
vipulwhat happens between H-3 (9/5) and summit20:09
hub_capvipul: we go on break20:09
vipulwoohoo!20:09
hub_capever seen summer school?20:09
SlickNikholiday!20:09
juicehub_cap there says there is a review for it20:10
hub_capwe are the guy whos zipper got stuck20:10
juice507 that is and you are the one who worked on it20:10
hub_capjuice: thats VERRRRY odd20:10
vipulhub_cap: why is this a bug though20:10
vipuli did'nt think trove supported reset_password20:10
hub_cap#action hub_cap to review https://bugs.launchpad.net/trove/+bug/119950720:10
vipulyou just enable root multiple times20:10
hub_capwait this should be in troveclient20:11
SlickNikvipul, I think it should be a cli bug20:11
SlickNikyup20:11
hub_capAvailable actions for 'instance' cmd:20:11
hub_cap reset_password Reset the root user Password20:11
SlickNikmoved to python-troveclient20:11
hub_capseems like its missplaced20:11
hub_capthx SlickNik20:11
hub_cap#undo20:11
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x2544910>20:11
SlickNiksounds good, carry on20:11
hub_capdef20:11
hub_capmoving on20:11
hub_capok feature freeze info is gonna be fun20:12
hub_cap#topic feature freeze20:12
*** openstack changes topic to "feature freeze (Meeting topic: trove)"20:12
hub_cap#link https://wiki.openstack.org/wiki/FeatureProposalFreeze20:12
hub_cap#link https://wiki.openstack.org/wiki/FeatureFreeze20:12
hub_capwe have a tentative feature freeze for Sep4, just liek the other projects20:12
hub_capthe feature proposal freeze should happen sooner, but no date is set20:13
hub_capthis is a dry run20:13
hub_capwe are not 100% solid on this20:13
hub_capwe can have stuff slip in20:13
hub_capfor instance, heat support _has_ to get in, and it wont make the FPF20:13
hub_capso real quick20:13
hub_capFPF means if its not on review.openstack.org, its not going in h320:13
hub_capFF means if its not a bug, its not going in 2013.120:14
hub_capFF also means h3 gets cut20:14
vipulso we are officially in FPF now20:14
hub_capand then we go into the cycle of RC's to determine our "bug free (lol)" 2013.1 releas20:14
hub_capwe havent set the date vipul... so we are in FPF limbo20:14
hub_capi still want to see those items in h3 impl'd20:14
hub_capso i think we are going to be lax on FPF this go-round20:15
*** tsimmons has left #openstack-meeting-alt20:15
SlickNikit says one or two weeks ahead of FF20:15
hub_capbut yes, if we were 100% obeying, sometime next wk would be FPF20:15
*** arborism has joined #openstack-meeting-alt20:15
vipulkk20:15
hub_capmeaning if its not already proposed on gerrit, its not going into h320:15
hub_capunless its a bug of course20:15
hub_capthen we hit FF and NOTHING thats not a bug goes in till we get 2013.1 cut20:16
hub_capso when i joked about imsplitbit's feature eariler its because he would be a good candidate for the FF20:16
hub_capand we can leave it unmerged20:16
vipulman so nothing until Nov.20:16
hub_cap#action hub_cap to find out what happens w/ reviews that land after FF20:16
hub_cap#undo20:17
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x24c5310>20:17
hub_cap#action hub_cap to find out what happens w/ feature based reviews that land after FF20:17
hub_capdoes that make sense to everyone?20:17
hub_capany questions?20:17
SlickNikyes, that makes sense.20:17
hub_capim giong to be strict on some things, but not everything20:17
KennethWilkesounds good20:17
amytronmakes sense20:17
hub_capcool. if no one has any Qs then we can move on20:18
kevinconwaythe freeze sounds… ice20:18
kevinconway*nice20:18
hub_capif you think you are wrongly FF'd then plz talk to me 1x120:18
hub_capits ice too kevinconway20:18
amytron:)20:18
key2what about teally big features like Cassandra support?20:18
hub_capid like to not affect any of the teams this go-round if possible. i knwo we are all trying to deal w/ a real product currently20:18
key2*really20:19
hub_capkey2: id LOVE to see cassandra support ;) but not in Havana20:19
hub_capwe are way to far along for cassandra now20:19
hub_capbut if you are going to work on it, then propose the BP and lets get it done for icehouse20:19
* hub_cap thinks itll depend greatly on the clustering api too which is still in the works20:20
vipulkinda sucks it's 2 months!20:20
hub_capwell its not vipul20:20
vipulfrom H3 -> 2013.120:20
key2it would be interesting20:20
hub_caponce we cut a 2013.1 release20:20
hub_capkey2: hell ya it will. /me wants some cassandra!20:20
key2))20:20
hub_caplisp?20:20
hub_capif we deem there are no critical bugs in the code we can decide to cut 2013.1 vipul20:21
key2smile :)20:21
hub_capwe can cut early20:21
hub_cap key2 :P20:21
vipulhub_cap: oh ok.. then that's coo20:21
* hub_cap assumes vipul ;)20:21
hub_capi doubt we have 2 mo of bugs to work out20:21
SlickNikwe can figure that out once we get closer to that date.20:21
hub_capunless i push puro crap up for heat support20:22
hub_capexactly SlickNik20:22
hub_capmoving on?20:22
vipulyessir20:22
SlickNiksounds good20:22
hub_cap#topic redstack vs devstack users20:22
*** openstack changes topic to "redstack vs devstack users (Meeting topic: trove)"20:22
hub_capso real quick let me splain20:22
hub_capwe have a set of users (radmin for sure) that we use in redstack20:22
hub_capthis is different from the ones that devstack uses20:23
hub_capso when i ./redstack rd-client instance create20:23
hub_capthen20:23
hub_cap. ~/devstack/openrc && nova list20:23
hub_capi see nothing20:23
hub_capbecause they are on different tenants20:23
hub_caprobertmyers: has mentioned issues as well w/ horizon integration wrt our users vs devstack users20:23
hub_capso im going to rip out the extra users and use the devstack users in redstack20:23
hub_capand hopefully including the tests (on pass one)20:24
datsun180bour tests for the most part should be selecting different users for tests via the Requirements filter, so changing the list of users ideally shouldn't hurt us so long as the set still spans all the different kinds of users we need20:24
datsun180band our tests aren't trying to call the users by name deliberately20:24
hub_capif the tests end up failing miserably im going to push a WIP review up for someone else to finish20:24
grapexhub_cap: Sounds good enough20:24
vipulisn't there a requirement to have a role added?20:24
vipulor will existing users just work with trove20:24
hub_capyup thats the hope datsun180b that it doesnt fail miserably20:25
hub_capi think boss/chunk will still be created/used for specific tests20:25
hub_capthis is for the main user thats run thru20:25
hub_capvipul: is there a req?20:25
datsun180bhub_cap: i said "i agree" but i took two lines to do it20:25
vipulthought so.. i could be wrong20:25
SlickNikyes, vipul is right.20:25
SlickNikYou'd have to add the trove role to the existing devstack users, I think20:25
hub_caphttps://gist.github.com/hub-cap/623521020:26
hub_capthats the list of roles i have currently in my devstack+redstack install20:26
datsun180bi think we need at least one, maybe two admin users, and at least two non-admin users20:26
hub_capdatsun180b: we can let redstack deal w/ those20:26
SlickNikIt might work for admin, but wouldn't work for guest.20:27
hub_capbut those arent the ones that ./redstack rd-client uses20:27
hub_capthe primary reasoning was to align the cli calls between us and devstack20:27
hub_capwhen you source openrc20:27
grapexhub_cap: So really, it's just getting rid of radmin and replacing it in the tests with the demo user?20:27
vipulhub_cap: the bug you linked is something different though20:27
SlickNikWe can just add the role to the devstack users though. They will _always_ exist.20:27
hub_capit is, i havent created a bug for this yet vipul20:27
vipulah ok20:27
hub_capthis is another thing that needs knocking out tho20:27
hub_capyou can do a heat stack-list and its different from ./redstack rd-client20:28
hub_capso when i get to testing (and when robertmyers is testing horizon) its teh suck20:28
hub_capim not sure exactly waht it entails grapex but i think the answer is yes20:28
vipulas part of our devstack patch.. SlickNik do we assign the role ot any existing?20:28
grapexYeah- keep in mind the tests round-robin the users they select; it's kind of a coincidence rd-client uses the same user used by most of the test20:28
robertmyersyes, it is a little silly to have our own special users20:28
grapexI don't think we need to fix this yet, but it'd be kind of cool if rd-client picked the user-20:29
SlickNikvipul: only the ones we create (not the default devstack ones)20:29
grapexbut I agree that the devstack created demo user should be used for the tests.20:29
SlickNikvipul: same behavior in redstack20:29
vipulSlickNik: ok, cool..20:29
vipulso now that we'll be official devstack.. safe to change existing users i'd imagine20:30
hub_capyes20:30
hub_capfor now ill just mirror what devstack is using20:30
hub_capfrankly, all the projects use demo20:30
hub_capthats what the openrc sets20:30
cp16netyes20:30
vipulthat works20:30
hub_cap:)20:31
grapexhub_cap: +120:31
SlickNikI like the idea of removing radmin, and adding the "trove" role to admin and demo.20:31
hub_capwe can let SlickNik figure out the nuances w/ his devstack review ;)20:31
SlickNikthat I can do. :)20:31
hub_capcool SlickNik maybe just do that in the devstack review now20:31
hub_capso its not merged w/ radmin20:31
hub_capgood everyone?20:31
SlickNiksounds good.20:31
hub_cap#topic blueprints20:32
*** openstack changes topic to "blueprints (Meeting topic: trove)"20:32
SlickNik#action SlickNik update devstack review to add role to default devstack users.20:32
hub_cap#link https://blueprints.launchpad.net/trove/+spec/pluggable-db-implementations20:32
yogesh_This is on further abstraction of guestagent for implementing specific database managers...20:32
hub_capyogesh_: around?20:32
hub_capcool20:32
yogesh_yes..20:32
hub_capcan u explain a bit?20:32
hub_capi guess answer this20:33
hub_caphow do we not do that today?20:33
hub_captoday we have a generic api + XXX.py impl. coudl be redis, could be mysql, could be cassandra ;)20:33
yogesh_the idea is to separate the manager implementations from trove20:33
hub_caphow does that not work20:33
vipulIf i read correctly, it seems we need the ability to load a different package?20:33
hub_capwe have that already yogesh_20:33
SlickNikhub_cap: You need to be part of a registry today.20:33
yogesh_we can not plug any db implementation of the manager in...20:34
yogesh_if the design goes like, having the contracts sty in trove..20:34
hub_capSlickNik: ok so this is to turn teh registry into a config?20:34
yogesh_but the implementaitons are driven with config...20:34
SlickNikIf I'm understanding this correctly, this is to have a plugin model, so you can just specify the python module for a new implementation of a completely different service_type.20:34
vipulseems like if we extracted the registry out to a conf or something like that you could load any arbitrary class20:34
hub_capthats what i think too vipul20:35
yogesh_that was the first step vipul20:35
grapexyogesh_: Is that we load an image with one single guest agent, on, on loading itself up, it determines what type of agent it should be and loads an arbitrary class by talking back to Trove somehow?20:35
vipulyogesh_: ok.. how that class gets into the instance probably doesn't have to be a Trove concern20:35
yogesh_yes...20:35
hub_capno i think this is for a impl that stays out of the mainline codebase, right?20:35
yogesh_trove doesn't need to contain the implementations as suc20:36
yogesh_true...20:36
yogesh_that is the final point around this blueprint20:36
vipulhub_cap: Yes, assuming you can't put the manager impl in codebase.. how do we allow someone to plug in a manager20:36
*** briancli1e is now known as briancline20:36
yogesh_to start with, we move the registry into config...20:36
hub_capi think im ok w that20:36
yogesh_and make it directly addressable20:36
hub_capid like to see how it works out in the code itself but i dont think thts a bad idea20:37
yogesh_yeah, step-120:37
yogesh_:20:37
hub_capid like to _not_ support every impl for everythign if possible20:37
hub_capthen we can remove percona (i kid i kid)20:37
yogesh_extracting the base contracts out from mysql implementations into generic base classes20:37
* vipul stabs hub_cap20:37
SlickNik I'm for the idea of a plugin model as well.20:37
hub_capHAHAHAHAHA20:37
yogesh_:-)20:37
* SlickNik gets out of the way20:37
*** ashestakov has joined #openstack-meeting-alt20:38
hub_capok thats fine. i think this will not make havana tho20:38
hub_capit seems somewhat complicated20:38
hub_capis that ok for the parties involved?20:38
yogesh_the first step is not20:38
vipullet's do a simpnle thing in Havana20:38
grapexHonestly I'm a bit confused...20:38
vipultake out the registry into conf20:38
vipulso we can load arbitrary managers20:38
yogesh_which per me will be to extract the bases classes out...20:38
grapexI probably will need to see the code to get this. My guess is it's just a refactor to make things more flexible?20:38
yogesh_and have a mysql package, right with the existing code20:38
* cp16net confused as well20:38
yogesh_which has extended implementations..20:39
vipulgrapex: Mysql manager contains stuff other managers might need20:39
*** dina_bel_ has quit IRC20:39
yogesh_thats correct20:39
grapexvipul: Ok, so the idea is make that code reusable, right? I'm for that.20:39
yogesh_if we can structure it in the first go...20:39
vipulright, but the thing reusing it, might be out of repo20:39
yogesh_then brakingit into a pluggable component can be taken up in parts...20:40
hub_capsimple way to put it20:40
hub_capturn20:40
hub_caphttps://github.com/openstack/trove/blob/master/trove/guestagent/dbaas.py#L3420:40
hub_capconf values20:40
hub_capinto20:40
key2yogesh_: do you have any code or proof of concept to review? it would help to understand20:40
cp16netok i think it just cliked for me...20:40
yogesh_i am working on it...almost done...20:40
yogesh_i can share...20:40
vipulok... i think we can push out the refactor stuff to past H320:40
hub_caphehe ya20:40
vipulunless we have something concrete ready to go20:40
vipulbut let's get what hub_cap pointed out done20:41
vipulin H320:41
hub_capif we can easily im all for that20:41
yogesh_slightly confused... :-)20:41
hub_capyogesh_: take it offline w vipul20:41
hub_caphe knows whats going on20:41
vipulpush out REGISTRY to conf today..20:41
hub_capsoudn good?20:41
vipulwe can take it offline20:41
yogesh_how about the base classes...20:42
hub_cap#link https://blueprints.launchpad.net/trove/+spec/support-schema-queries20:42
yogesh_thats jsut some refactor..20:42
vipulunless we have something ready to go.. we have to defer that til later yogesh_20:42
hub_capis sushil here?20:42
yogesh_i am on this bp as well20:42
hub_capok20:42
yogesh_this is for the vertica implementation we are working on20:42
hub_capyogesh_: after the meeting tell me your launchpad id20:42
hub_capand ill assign you20:42
yogesh_sure...thanks20:43
yogesh_ok20:43
SlickNikSo what's the bp about?20:43
hub_capso here is my issue w/ things that are specific for a impl that wont be in mainline20:43
yogesh_for vertica, the stratgey is to have the create database api map to the schema creations..20:43
hub_capif we dont use the code, its not gonna go in the code. period20:43
yogesh_ok...20:43
hub_capif you push this magical vertica impl up, we can add teh code then20:44
yogesh_since the code was dependent on the first bp...20:44
yogesh_we did not put it in as yet..20:44
dukhlov#link https://blueprints.launchpad.net/trove/+spec/configuration-driven-changes20:45
yogesh_generally...schema related ops are generic...20:45
SlickNikyogesh_: since all of this is being called from your manager impl anyway, what's preventing you from overriding it in your manager impl?20:45
vipulany objection to modifying existing 'create database' call to 'create schema'?20:45
vipulhub_cap: grapex ^20:45
dukhlovbleprint related to moving some db specific parts into configuration20:45
hub_capsure20:45
grapexvipul: Just the RPC call?20:46
vipulno, the actual SQL command20:46
hub_capbut what i mean is20:46
hub_capif you need code in a file, thats depending on a impl that you will not be pushing into the mainline code base20:46
hub_capthen you wont be needing that code anywhere as far as im concernd20:46
hub_capand then i will be rejecting that code20:46
hub_capif the mysql code uses that new schema code, then sure it would make sense20:46
hub_capbut if only vertica is gonna use it then it doesnt make sense for me to maintain it20:46
hub_capsince i dont own vertica impl20:46
* grapex sounds the horn of summoning for Daniel Morris20:46
yogesh_sure...20:46
hub_caphahah grapex20:46
hub_capif it doesnt affect the way we work today then its ok20:46
vipulyogesh_ let's put up a review modifying existing CREATE DATABSE -> CREATE SCHEMA20:46
hub_capie, if it looks the same to the end user20:46
vipulthen you can use that in your manager20:46
yogesh_yes...20:46
hub_capbut if this changes anything fundamentally in the way the schemas/dbs are created20:47
grapexvipul: I'd rather now- it would break users. Maybe for the next iteration?20:47
hub_capthen we are modifing the user experience and, no,20:47
datsun180bwhy rename it in the mysql flavor20:47
vipulin mysql it don't break a thing20:47
vipulsince they are ==20:47
hub_capif thats the case then im a-ok w it20:47
jdbarrywe are working on getting the vertica implementation upstream, fwiw20:47
vipuljdbarry ++20:47
datsun180boh well if you want to bring relevant research and test cases to strengthen your argument like that20:47
SlickNikjdbarry: that would help resolve a lot of confusion20:48
yidclarelol20:48
yogesh_by the way, the api still stays same...20:48
grapexvipul: Oh, I get it- I misread you, sorry20:48
hub_capyes yogesh_ not worried about the api20:48
yogesh_no modifications/changes in user ex for mysql20:48
vipuldatsun180b: i think if it passes exisitng tests.. we are ok no?20:48
hub_capvipul: likely yes20:48
vipuleverythin i've heard is it's a synonym20:48
hub_capunless we missed somethign in the tests20:48
vipulin mysql20:48
datsun180bvipul: hard to convey sarcasm in text, i'm with you already20:48
hub_capimsplitbit: around20:48
vipuldatsun180b: :D20:49
hub_capCREATE SCHEMA vs CREATE DATABASE in mysql imsplitbit, differences or no?20:49
* hub_cap waits for imsplitbit20:49
SlickNik#link http://dev.mysql.com/doc/refman/5.0/en/create-database.html20:49
imsplitbit:)20:49
SlickNik"http://dev.mysql.com/doc/refman/5.0/en/create-database.html is a synonym for http://dev.mysql.com/doc/refman/5.0/en/create-database.html as of MySQL 5.0.2."20:50
hub_capthe docs say "CREATE SCHEMA is a synonym for CREATE DATABASE as of MySQL 5.0.2." imsplitbit20:50
imsplitbitschema is the same as database in mysql 5+20:50
hub_capok then we are good. feel free to change to use20:50
vipulok.. the thing is 'some databases' require you to call CREATE SCHEMA.. which is why yogesh_ needs this20:50
yogesh_ok..20:50
grapexvipul: That sounds fine.20:50
vipulcool20:50
SlickNikI'm comfortable with changing this.20:50
hub_capsome rdms's ya vipul ;)20:50
hub_cap*rdbms20:50
hub_capie vertica lulz20:50
SlickNikhub_cap: watch out or you'll get stabbed again :P20:51
yogesh_:-)20:51
hub_capHAHAHA SlickNik20:51
imsplitbitI'm fine with it20:51
hub_capmoving on20:51
hub_capwe are runnin out of time20:51
hub_cap#topic Upgrade GA20:51
*** openstack changes topic to "Upgrade GA (Meeting topic: trove)"20:51
hub_cap#link https://bugs.launchpad.net/trove/+bug/121241320:52
vipuloh yea that was me20:52
vipulor saurabhs20:52
vipulbut we have upgrade() in guest_api20:52
vipulbut no Impl20:52
hub_capcp16net: ummmm why didnt u add your topic to the meeting!?!?!?!!?!??!?!?!?!?!?!20:52
vipulso the proposal is to add an impl... where it's sort of pluggable how you upgrade20:52
* cp16net shrugs20:52
cp16neti figured we would talk about it in the open discussion...20:52
hub_capSMH20:53
vipulessentially defer the actual upgrade to a script or something that you can place on the instance20:53
hub_capvipul: plugable upgrade is good by me20:53
vipulany objections? or any good suggestions on how to do it in public impl?20:53
* hub_cap thinks this is more than a bug tho20:53
vipulin the upstream version, just invoking rsync and service restart?20:54
hub_caprsync?20:54
SlickNikno objections.20:54
hub_capya that makes sense20:54
vipulok20:54
SlickNikThat would be an okay upstream impl, imho20:54
saurabhssounds good20:54
vipulok i'm done20:55
hub_capid like to see an apt based one too20:55
hub_capbut i dont think that needs to be done for the first impl20:55
hub_caplet someone using apt/rpm do that work20:55
hub_capbut plz create a BP for pluggable upgrades20:55
hub_capw/ this info in it20:55
arborismisn't the key regen'd after initial rsync, making that an impossibility?20:55
vipularborism: which key? ssh?20:56
arborismsi'20:56
hub_capshouldnt be arborism20:56
SlickNikarborism: I don't think we regen the key.20:56
vipulnot sure it is20:56
hub_capif thats happening /me thinks its a bug20:56
arborismah, i thought it was, my bad. I'll double-check.20:56
hub_capplz do20:56
hub_caplog a bug if so20:56
hub_cap<320:56
hub_cap#topic Flavors per Service Type20:56
*** openstack changes topic to "Flavors per Service Type (Meeting topic: trove)"20:56
hub_capwe have 4 min20:56
vipulcrap that's me too20:56
hub_capi like this idea20:56
hub_capfwiw20:56
vipulwe discussed this yesterday20:56
vipulso /flavors?service_tyep=xx20:57
SlickNikYeah, read it over.20:57
vipulis that good?20:57
SlickNikI think it's a good idea.20:57
jdbarryi discussed this with myself yesterday (bot issue)20:57
KennethWilkemakes sense to me20:57
hub_capya i think thats the only thing for v1 that'd work20:57
datsun180bproposed was adding a ?service_type= filter to the flavors list call IIRC20:57
hub_capjdbarry: lol20:57
hub_capim all for it20:57
datsun180boh vipul's a minute ahead of me20:57
vipuldatsun180b: correct20:57
yogesh_vipu: do u see any change in the api with this20:57
yogesh_vipul*20:58
hub_capid like to see us hold more info about the flavors too20:58
hub_capso that we can _not_ go to nova every time we list em20:58
vipulprobalby just a change to client really.. and some changes to aceept the filter on api side20:58
vipulhub_cap: yes!20:58
hub_capand jsut link the name back to the nova flavor20:58
SlickNikhub_cap: probably a diff work-item though.20:58
*** briancline has quit IRC20:58
vipulkinda sucks we list all the ones found in nova20:58
yogesh_can't the falvor taxonomy stays same but they map internally to separate config items20:58
hub_cappossibly SlickNik could all be one fell swoop tho20:58
SlickNikbtw, is this for h3 as well?20:58
vipulyogesh_: not really since the flavor contains details about disk size, etc20:59
SlickNikI think so, but want to clarify20:59
hub_capok real quick20:59
vipulif we can get it done20:59
hub_capwe like this20:59
hub_capblueprint it20:59
yogesh_will discuss offline..20:59
hub_capdo it20:59
hub_capdone20:59
vipulok20:59
vipulwill do20:59
hub_cap#topic open discussion20:59
*** openstack changes topic to "open discussion (Meeting topic: trove)"20:59
hub_capcp16net: link your wiki pager20:59
*** jasonb365 has quit IRC20:59
vipulwhat's a wiki pager20:59
hub_cap#homework go over cp16net's wiki page20:59
vipuloh20:59
vipulduh20:59
cp16nethere is some autmated backup design20:59
cp16nethttps://wiki.openstack.org/wiki/Trove/automated-backup-design20:59
hub_capvipul: cp16net is a wiki drug dealer from 198721:00
vipulheh always had tha suspicion21:00
cp16netits an overview and i will continue to add to this21:00
hub_capautomated backup design == maintainence window == guest update during maint21:00
cp16net:-P21:00
hub_capall that kinda goes together in my mind21:00
lifelessDoes trove use diskimage-builder's first-boot feature?21:00
hub_capSlickNik: ^ ^21:00
vipullifeless: yes we do21:00
hub_capis it being removed lifeless?21:00
juiceyes21:00
SlickNiklifeless: yes, we do21:00
lifelessWe want to remove it yes.21:00
vipulno!21:00
vipullol21:01
lifelessidempotent os-refresh-config scripts are much better21:01
SlickNikwhat's the alternative?21:01
hub_capheh cool. im sure we can work aroudn it w orc21:01
vipulwe don't need it after we get user-data patch in21:01
grapexSorry guys, I've got to go to a meeting scheduled at 4:0021:01
hub_capyes we are done21:01
grapextalk to you all later21:01
lifelessthey run equally early21:01
hub_cap#endmeeting21:01
*** openstack changes topic to "OpenStack meetings (alternate)"21:01
imsplitbitkthxbai!21:01
openstackMeeting ended Wed Aug 14 21:01:44 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
vipulcp16net: great work.. like it21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-08-14-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-08-14-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-08-14-20.00.log.html21:01
*** imsplitbit has left #openstack-meeting-alt21:01
hub_capthank you for the heads up lifeless21:01
lifelessSlickNik: should I file a bug on trove?21:01
hub_capmove to #openstack-trove plz21:02
SlickNikYes, please.21:02
lifelesskk21:02
lifelessthanks21:02
SlickNikLet's talk on openstack-trove21:02
cp16netthx vipul21:02
yogesh_thanks...21:02
*** dukhlov has left #openstack-meeting-alt21:02
*** crobertsrh is now known as _crobertsrh21:02
*** datsun180b has left #openstack-meeting-alt21:03
*** esp1 has left #openstack-meeting-alt21:03
*** robertmyers has quit IRC21:04
*** ashestakov_ has joined #openstack-meeting-alt21:04
*** ashestakov has quit IRC21:05
*** NehaV1 has quit IRC21:09
*** NehaV has joined #openstack-meeting-alt21:09
*** key2 has quit IRC21:15
*** KennethWilke has left #openstack-meeting-alt21:16
*** ashestakov_ has left #openstack-meeting-alt21:17
*** pcm__ has quit IRC21:20
*** pdmars has quit IRC21:22
*** djohnstone has quit IRC21:30
*** betsy has joined #openstack-meeting-alt21:31
*** jasonb365 has joined #openstack-meeting-alt21:33
*** bluzader has quit IRC21:34
*** IlyaE has joined #openstack-meeting-alt21:37
*** sarob has quit IRC21:37
*** sarob has joined #openstack-meeting-alt21:38
*** dina_belova has joined #openstack-meeting-alt21:40
*** arborism has left #openstack-meeting-alt21:40
*** sarob has quit IRC21:42
*** dina_belova has quit IRC21:44
*** dina_belova has joined #openstack-meeting-alt21:50
*** sarob has joined #openstack-meeting-alt21:52
*** jasonb365 has quit IRC21:53
*** dina_belova has quit IRC21:55
*** msisk has quit IRC21:56
*** rnirmal has quit IRC21:56
*** anteaya has quit IRC22:00
*** vipul is now known as vipul-away22:03
*** jasonb365 has joined #openstack-meeting-alt22:03
*** Riddhi_ has joined #openstack-meeting-alt22:09
*** vipul-away is now known as vipul22:09
*** jasonb365 has quit IRC22:11
*** Riddhi has quit IRC22:12
*** Riddhi_ is now known as Riddhi22:12
*** kevinconway has quit IRC22:13
*** sacharya has quit IRC22:19
*** sarob_ has joined #openstack-meeting-alt22:20
*** sarob has quit IRC22:24
*** sarob_ has quit IRC22:24
*** jasonb365 has joined #openstack-meeting-alt22:29
*** vipul is now known as vipul-away22:31
*** jasonb365 has quit IRC22:35
*** markmcclain has quit IRC22:36
*** markmcclain has joined #openstack-meeting-alt22:36
*** eankutse has quit IRC22:37
*** vipul-away is now known as vipul22:41
*** amytron has quit IRC22:46
*** NehaV has quit IRC22:46
*** dina_belova has joined #openstack-meeting-alt22:50
*** sarob has joined #openstack-meeting-alt22:52
*** sarob has quit IRC22:54
*** sarob has joined #openstack-meeting-alt22:54
*** dina_belova has quit IRC22:55
*** yogesh_ has quit IRC23:02
*** dhellmann is now known as dhellmann_23:10
*** jmontemayor has quit IRC23:11
*** Riddhi_ has joined #openstack-meeting-alt23:13
*** Riddhi has quit IRC23:15
*** Riddhi_ is now known as Riddhi23:15
*** jcru has quit IRC23:17
*** tanisdl has quit IRC23:24
*** sam_f_ has joined #openstack-meeting-alt23:39
*** sacharya has joined #openstack-meeting-alt23:40
*** sacharya has quit IRC23:40
*** sam_f_ has quit IRC23:40
*** vipul is now known as vipul-away23:43
*** vipul-away is now known as vipul23:43
*** vipul is now known as vipul-away23:45
*** jmaron has left #openstack-meeting-alt23:47
*** markwash has quit IRC23:48
*** IlyaE has quit IRC23:49
*** dina_belova has joined #openstack-meeting-alt23:50
*** grapex has quit IRC23:55
*** dina_belova has quit IRC23:55
*** sarob has quit IRC23:56

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