Wednesday, 2013-07-24

*** gokrokve has quit IRC00:05
*** sballe has quit IRC00:15
*** nkonoval_ has joined #openstack-meeting-alt00:35
*** nkonoval_ has quit IRC00:40
*** HenryG has joined #openstack-meeting-alt00:44
*** jcru has quit IRC01:16
*** markwash has joined #openstack-meeting-alt01:18
*** markwash has quit IRC01:33
*** nkonoval_ has joined #openstack-meeting-alt01:36
*** rnirmal has quit IRC01:38
*** nkonoval_ has quit IRC01:40
*** qwerty_nor has quit IRC01:42
*** tanisdl has quit IRC01:42
*** rnirmal has joined #openstack-meeting-alt01:45
*** demorris has joined #openstack-meeting-alt01:59
*** venkatesh has joined #openstack-meeting-alt02:09
*** venkatesh has quit IRC02:16
*** akuznetsov has joined #openstack-meeting-alt02:17
*** nkonoval_ has joined #openstack-meeting-alt02:37
*** vkmc has quit IRC02:40
*** nkonoval_ has quit IRC02:41
*** jcru has joined #openstack-meeting-alt03:09
*** jcru is now known as jcru|away03:09
*** jrodom has quit IRC03:22
*** nkonoval_ has joined #openstack-meeting-alt03:37
*** akuznetsov has quit IRC03:39
*** nkonoval_ has quit IRC03:42
*** jcru|away is now known as jcru03:43
*** demorris has quit IRC03:45
*** jrodom has joined #openstack-meeting-alt03:49
*** jrodom has quit IRC03:50
*** jrodom has joined #openstack-meeting-alt03:50
*** vipul is now known as vipul-away03:55
*** mestery has joined #openstack-meeting-alt04:00
*** SergeyLukjanov has joined #openstack-meeting-alt04:03
*** akuznetsov has joined #openstack-meeting-alt04:04
*** vipul-away is now known as vipul04:13
*** akuznetsov has quit IRC04:15
*** akuznetsov has joined #openstack-meeting-alt04:31
*** westmaas_ has joined #openstack-meeting-alt04:33
*** westmaas has quit IRC04:34
*** westmaas_ is now known as wesstmaas04:34
*** wesstmaas is now known as westmaas04:35
*** nkonoval_ has joined #openstack-meeting-alt04:38
*** nkonoval_ has quit IRC04:43
*** abaron_ has quit IRC04:52
*** vipul is now known as vipul-away05:04
*** nkonoval_ has joined #openstack-meeting-alt05:04
*** colinmcnamara has joined #openstack-meeting-alt05:05
*** colinmcnamara has quit IRC05:07
*** vipul-away is now known as vipul05:08
*** lastidiot has quit IRC05:09
*** nkonoval_ has quit IRC05:19
*** akuznetsov has quit IRC05:20
*** nkonoval_ has joined #openstack-meeting-alt05:26
*** SergeyLukjanov has quit IRC05:36
*** jcru has quit IRC05:39
*** bdpayne has quit IRC05:40
*** akuznetsov has joined #openstack-meeting-alt05:55
*** abaron_ has joined #openstack-meeting-alt05:59
*** jrodom has quit IRC06:04
*** akuznetsov has quit IRC06:04
*** esp has joined #openstack-meeting-alt06:07
*** abaron_ has quit IRC06:19
*** nkonoval_ has joined #openstack-meeting-alt06:20
*** abaron_ has joined #openstack-meeting-alt06:42
*** esp has left #openstack-meeting-alt06:42
*** plomakin has joined #openstack-meeting-alt07:04
*** SergeyLukjanov has joined #openstack-meeting-alt07:06
*** abaron_ has quit IRC07:08
*** jrodom has joined #openstack-meeting-alt07:30
*** nkonoval_ has quit IRC07:35
*** nkonoval_ has joined #openstack-meeting-alt07:35
*** jrodom has quit IRC07:43
*** jrodom has joined #openstack-meeting-alt07:44
*** abaron_ has joined #openstack-meeting-alt08:09
*** abaron_ has quit IRC08:19
*** nkonoval_ has quit IRC08:20
*** abaron_ has joined #openstack-meeting-alt08:21
*** nkonoval_ has joined #openstack-meeting-alt08:23
*** nkonoval_ has joined #openstack-meeting-alt08:24
*** dhellmann_ has joined #openstack-meeting-alt08:27
*** jeblair_ has joined #openstack-meeting-alt08:28
*** pleia2_ has joined #openstack-meeting-alt08:29
*** dhellmann has quit IRC08:29
*** pleia2 has quit IRC08:29
*** jeblair has quit IRC08:29
*** dhellmann_ is now known as dhellmann08:30
*** SergeyLukjanov has quit IRC08:49
*** SergeyLukjanov has joined #openstack-meeting-alt08:55
*** abaron_ has quit IRC09:06
*** nkonoval_ has quit IRC09:23
*** abaron has joined #openstack-meeting-alt09:26
*** abaron has quit IRC09:39
*** abaron has joined #openstack-meeting-alt09:52
*** jrodom has quit IRC10:05
*** pcm_ has joined #openstack-meeting-alt10:09
*** pcm_ has joined #openstack-meeting-alt10:09
*** nkonoval_ has joined #openstack-meeting-alt10:11
*** demorris has joined #openstack-meeting-alt10:13
*** nkonoval_ has quit IRC10:21
*** nkonoval_ has joined #openstack-meeting-alt10:22
*** demorris has quit IRC11:02
*** akuznetsov has joined #openstack-meeting-alt11:08
*** nkonova__ has joined #openstack-meeting-alt11:48
*** nkonoval_ has quit IRC11:48
*** nkonova__ has quit IRC12:14
*** vkmc has joined #openstack-meeting-alt12:19
*** vkmc has joined #openstack-meeting-alt12:19
*** pdmars has joined #openstack-meeting-alt12:39
*** nkonoval_ has joined #openstack-meeting-alt12:48
*** demorris has joined #openstack-meeting-alt13:06
*** pdmars has quit IRC13:17
*** pdmars has joined #openstack-meeting-alt13:23
*** nkonoval_ has quit IRC13:35
*** djohnstone has joined #openstack-meeting-alt13:54
*** jrodom has joined #openstack-meeting-alt13:55
*** jrodom has quit IRC13:55
*** jrodom has joined #openstack-meeting-alt13:56
*** cp16net is now known as cp16net|away13:56
*** cp16net|away is now known as cp16net13:56
*** lifeless has quit IRC13:57
*** nkonoval_ has joined #openstack-meeting-alt13:59
*** Riddhi has joined #openstack-meeting-alt14:04
*** lifeless has joined #openstack-meeting-alt14:04
*** kevinconway has quit IRC14:06
*** kevinconway has joined #openstack-meeting-alt14:07
*** kevinconway has left #openstack-meeting-alt14:08
*** kevinconway has joined #openstack-meeting-alt14:08
*** kevinconway has quit IRC14:08
*** megan_w has joined #openstack-meeting-alt14:08
*** kevinconway has joined #openstack-meeting-alt14:10
*** rnirmal has joined #openstack-meeting-alt14:11
*** lastidiot has joined #openstack-meeting-alt14:15
*** markmcclain has joined #openstack-meeting-alt14:15
*** lastidiot has quit IRC14:28
*** sballe has joined #openstack-meeting-alt14:39
*** ashestakov has joined #openstack-meeting-alt14:45
*** ashestakov has left #openstack-meeting-alt14:45
*** Serge has joined #openstack-meeting-alt14:46
*** ashestakov has joined #openstack-meeting-alt14:46
*** nkonoval_ has quit IRC14:53
*** tanisdl has joined #openstack-meeting-alt15:01
*** lastidiot has joined #openstack-meeting-alt15:03
*** jcru has joined #openstack-meeting-alt15:07
*** pleia2_ is now known as pleia215:09
*** tanisdl has quit IRC15:14
*** yidclare has joined #openstack-meeting-alt15:16
*** tanisdl has joined #openstack-meeting-alt15:17
*** nkonoval_ has joined #openstack-meeting-alt15:23
*** nkonoval_ has quit IRC15:31
*** colinmcnamara has joined #openstack-meeting-alt15:43
*** jergerber has joined #openstack-meeting-alt15:46
*** bdpayne has joined #openstack-meeting-alt15:48
*** nkonoval_ has joined #openstack-meeting-alt15:49
*** colinmcnamara has quit IRC15:57
*** colinmcnamara has joined #openstack-meeting-alt15:58
*** nkonova__ has joined #openstack-meeting-alt16:01
*** akuznetsov has quit IRC16:04
*** nkonoval_ has quit IRC16:05
*** vinodmr has joined #openstack-meeting-alt16:08
*** nkonova__ has quit IRC16:11
*** Riddhi_ has joined #openstack-meeting-alt16:11
*** Riddhi has quit IRC16:13
*** Riddhi_ is now known as Riddhi16:13
*** jcru is now known as jcru|away16:18
*** CaptTofu has joined #openstack-meeting-alt16:19
*** kiall has joined #openstack-meeting-alt16:20
*** jeblair_ is now known as jeblair16:22
*** tsimmons has joined #openstack-meeting-alt16:22
*** jcru|away is now known as jcru16:36
*** jergerber has quit IRC16:36
*** vinodmr has left #openstack-meeting-alt16:37
*** sarob has joined #openstack-meeting-alt16:38
*** gokrokve has joined #openstack-meeting-alt16:44
*** SergeyLukjanov has quit IRC16:45
*** esp has joined #openstack-meeting-alt16:46
*** akuznetsov has joined #openstack-meeting-alt16:47
*** sarob has quit IRC16:47
*** sarob has joined #openstack-meeting-alt16:47
*** kevinconway has quit IRC16:48
*** qwerty_nor has joined #openstack-meeting-alt16:49
*** kevinconway has joined #openstack-meeting-alt16:49
*** esp has quit IRC16:49
*** esp has joined #openstack-meeting-alt16:50
*** gokrokve has quit IRC16:50
*** esp has left #openstack-meeting-alt16:51
*** akuznetsov has quit IRC16:51
*** simonmcc has joined #openstack-meeting-alt16:53
*** gcheng has joined #openstack-meeting-alt16:53
*** tsimmons has quit IRC16:55
*** jmcbride has joined #openstack-meeting-alt16:58
*** tsimmons has joined #openstack-meeting-alt16:59
*** betsy has joined #openstack-meeting-alt17:00
*** vinodmr has joined #openstack-meeting-alt17:00
*** msisk has joined #openstack-meeting-alt17:00
kiallHeya17:00
kiallWho's about for the DNS meet?17:00
kiall#startmeeting designate17:00
openstackMeeting started Wed Jul 24 17:00:57 2013 UTC.  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:01
openstackThe meeting name has been set to 'designate'17:01
*** eankutse has joined #openstack-meeting-alt17:01
kiallNobody? ;)17:01
betsyI'm here17:01
vinodmrI am here for the DNS meet17:01
tsimmonsAs am I17:01
simonmccb17:02
kiallCool :) Wanted to make sure you guys were around :)17:02
*** zane has joined #openstack-meeting-alt17:02
vinodmrIs there a # tag for recording attendees17:02
kiallNope .. Just say something and it's logged :)17:02
gchenghere17:02
kiall#link https://wiki.openstack.org/wiki/Meetings/DNSaaS17:02
jmcbrideHowdy from Austin17:02
msiskHere. ;)17:02
kiallAgeana ^17:02
kiallAgenda*17:02
CaptTofuI'm here17:03
kiallOkay .. Let's get started :)17:03
kiall#topic Intro of some of the RackSpace folks getting involved17:03
*** openstack changes topic to "Intro of some of the RackSpace folks getting involved (Meeting topic: designate)"17:03
kialljmcbride suggested this topic :) So I'll let you guys take over!17:03
zaneHi Zane here QE on Dnsaas17:03
jmcbridecool17:03
eankutseEmmanuel (eankutse)17:03
jmcbrideso, as you know, some of our team had a chance for a phone meeting with the HP'ers about 2 weeks ago.17:04
CaptTofuglad to have Rackspace onboard!17:04
*** SergeyLukjanov has joined #openstack-meeting-alt17:04
*** mugsie has joined #openstack-meeting-alt17:04
jmcbrideIn that meeting, we briefly introduced part of our team.  Since then, you have probably seen a few other handles.17:04
kiallYup - We've noticed a few RS folks hanging around :)17:05
jmcbrideso, without further ado...17:05
*** sarob has quit IRC17:06
jmcbrideeankutse, tsimmons, betsy, vinodmr are developers17:06
*** sarob has joined #openstack-meeting-alt17:06
jmcbridemsisk is dev ops17:06
*** eankutse has quit IRC17:06
jmcbridezane is test automation17:06
jmcbrideI am Dev manager17:07
jmcbrideAnd Nicole (who is on vacation at the moment in rainy arizona) is Product Manager.17:07
jmcbrideWe are all ramping up at the moment, while also juggling managing our current Rackspace DNS solution.17:08
kiallExcellent :) May as well re-introduce our team while we're at at.. CaptTofu (Patrick Galbraith) is Team Lead, simonmcc (Simon McCartney) is a developer, I'm a developer, and mugsie is joining our team next month as a developer17:09
kialljdbarry (he's AFK at the moment) is Josh Barry, our product manager17:09
jmcbrideSo although we are bringing a lot of team members to the party, not everyone is 100% involved.17:09
kiallYea - That's totally understandable.. the existing service doesn't run itself!17:10
jmcbrideAwesome.  So that covers Rackspace and HP.  Are there any other frequent operators/developers we should mention?17:10
CaptTofufuture feather.17:11
CaptTofufeature :)17:11
kiallNot really, we've got the likes of Ryan_Lane in wikimedia who's always bugging us about incubation etc.. :)17:11
kiallOkay! Any more intros before I move on?17:11
*** jcru is now known as jcru|away17:11
*** eankutse has joined #openstack-meeting-alt17:11
kiallI guess not :)17:11
kiall#topic API v2.0 Discussion/Feedback17:12
*** openstack changes topic to "API v2.0 Discussion/Feedback (Meeting topic: designate)"17:12
kiall#link  https://wiki.openstack.org/wiki/Designate/APIv217:12
kiallSo, we've been drafting a version two API spec, and before we call anything final - I wanted to get your opinions on the current draft17:12
kiallI believe it was betsy who gave me some initial feedback17:13
jmcbridekiall: can you send the link to the draft for reference?17:13
kialljmcbride: Yup - It's about 5 lines up :)17:13
kiall https://wiki.openstack.org/wiki/Designate/APIv217:13
eankutseeankutse(Emmanuel) gave some feedback in irc as well17:14
vinodmrSome of the create requests - for .e.g Create RecordSet returns a Location in the response but not all of them do.  Would it be good for all the create/update requests to return a location in the response17:14
kiallvinodmr: absolutly.. The are some inconsistencies in the draft, and in general it needs more TLC before we expand it to cover other resources17:15
kiallAll "create" calls should be returning a Location header.17:15
kiallI'll make sure that get's cleaned up tonight/tomorrow17:16
kiall#action kiall Ensure draft API spec is consistent in it's use of Headers and status codes17:16
kiallOne of the other pieces of feedback I got from you guys was around batch operations17:16
zane Kiall if you remember we had talked about the get recordset call17:16
kiallI've been struggling to understand what these batch calls should look like, anything I've mocked up "felt awful"17:17
zaneSorry List record set17:17
kiallDo you guys have any opinions on what these should look like?17:17
kiallzane: Yes - that's another one to remove from the List RecordSet's response17:18
kiall#action kiall to remove "records" array from List RecordSets API response17:18
zanejust list the ids of recordsets and then we can call indvidual records set17:18
mugsiejust ID's?17:19
*** nkonoval_ has joined #openstack-meeting-alt17:19
mugsieit might be usefull to have partial metadata17:19
mugsielike name, and type17:19
kiallWe were thinking of removing just the "records" array from the List RecordSet response, leaving all the other fields like name/type/etc17:20
jmcbrideis there a performance concern of providing more metadata?17:20
kiall(This is related to this API call BTW https://wiki.openstack.org/wiki/Designate/APIv2#List_RecordSets )17:20
*** nkonoval_ has left #openstack-meeting-alt17:20
eankutsename/type/id sounds good17:21
kiallI can see the "records" array as being a large enough performance hit to be worth removing it from that call, but I can't see any of the other fields providing a hit17:21
*** sarob has quit IRC17:21
zaneagreed17:22
kiallthe records get pulled from another table (potentially table(s)), so getting all that data together would be quite expensive17:22
zaneand we do have gett records call in v117:22
jmcbride#agreed on name/type/id and performance17:22
*** sarob has joined #openstack-meeting-alt17:22
betsy#agreed17:22
vinodmrIt would be good to have consistency between List Zones (https://wiki.openstack.org/wiki/Designate/APIv2#List_Zones) and Records although the zones returned could vary a lot from the number of records returned17:22
kiallvinodmr: is this to do with pagination etc?17:22
CaptTofu#agreed17:22
vinodmrYes - pagination etc17:22
betsyI like the pagination on List Zones17:23
kiallYea, pagination and filtering would exist on all "list" API calls, So far it's only be "mocked" on 1 API call to decide if that pattern is suitable17:23
vinodmrSince list zones accepts filtering, it would be good if list records also accepts filtering17:24
kiallYea - I actually think List RRsets requires it even more than List Zones does!17:25
kiallPreviously, I was thinking that using the RFC defined "Link" headers, rather than adding the links into the JSON response17:25
kiallBut - I'm now thinking that, "Average End User" will never see or notice them, and not understand why they are not getting all data17:25
kiall#link https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3.md17:26
kiallThat's the Keystone V3 API spec ^17:26
kiallYou should see lots of similarities between Designate V2, and Keystone V317:26
kiallhttps://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3.md#list-entities17:26
kiallThat section shows where they place "links" which includes pagination17:27
mugsiei like the idea of a "links" section17:27
mugsiethe "self" attrib can be very usefull17:27
kiallPersonally, I'm thinking we "just go with that" and stay as consistent as possible to Keystone V3/Glance V2 (the newest openstack APIs)17:27
kiallThoughts?17:28
*** sarob has quit IRC17:28
CaptTofukeystone is a good reference17:28
*** pdmars has quit IRC17:28
simonmccI agree - following the Keystone & Glance links for pagination model works for me17:28
vinodmrIs the keystone API final or are there changes still being proposed/discussed?17:29
kiallvinodmr: it's final, and a released part of Grizzly as far as I remember!17:29
kiall#link https://github.com/openstack/image-api/blob/master/openstack-image-service-api/src/markdown/image-api-v2.0.md17:30
kiallGlance V2 API ^17:30
kiallGlance V2 and Keystone V3 have lots of little inconsistencies with each other, I think out draft take the best parts of each, while staying closer to Keystone V317:31
kialls/out/our/17:31
jmcbride#agreed on pagination links in json response17:32
eankutselinks in response is what I am used to seeing17:32
tsimmonsHaving that in a header would be confusing for folks. Having a simple links section in the JSON seems better. Might as well stay consistent with Keystone.17:32
betsy#agreed we should stay consistent with Keystone17:32
kiallAnyway - I had planned to do updates to the API spec earlier this week, but other priorities bumped it. I'd like to get the draft in better shape this week, is there anyone on the RS team who is particularly interested in the API? I'd love to try and get things worked, then decide if the spec is final or not next week.17:33
kiallAfter that, port it from the wiki to the format that keystone/glance etc use17:33
eankutseI am17:33
jmcbridekiall: we actually have some questions/concerns about handling async actions.17:34
kialljmcbride: sure - what are you thinking?17:34
CaptTofu#agreed on modeling/inspiration from keystone API17:35
kiall#link http://docs.rackspace.com/cdns/api/v1.0/cdns-devguide/content/overview.html17:36
kiallRackSpace DNS API ^17:36
jmcbrideAs I understand it, a user gets a 202 when performing a Create/Update/Delete action, right?17:36
tsimmons^in V217:37
kiallmugsie pointed out some inconsistencies in the return codes for create/update/delete API calls yesterday17:37
kiallBased on that conversation, I've been eyeing up allowing the API to return either 201 Created or 202 Accepted (for create calls)17:38
kiallWhere, 202 Accepted would be unused until we introduce a "status" field on records and domains17:39
kialla new record would start with status=PENDING, and change to status=ACTIVE once it's been published to the DNS servers17:39
kiallThe backend in use (powerdns driver, akamai driver etc etc) would be responsible for making the PENDING->ACTIVE change on the records17:40
vinodmrIf you return a 201 created would that call be sync or async?17:40
simonmccand you query status just using the regular record-get?17:40
betsyor provide a callback?17:40
kiall201 Created would be sync, and would indicate the new record should be visible on the DNS server immediately17:40
eankutseSo how does the user find the status of a long running 202 job?17:40
kialleankutse, by querying the URL and inspecting the status field.17:41
kiallThat would follow the pattern set by Nova etc for async actions, like booting a VM17:41
kiallA new VM starts in the "BUILDING" state, and progresses over time to the "ACTIVE" state17:41
jmcbridekiall: So I assume we provide a unique endpoint for the user to query for status?17:43
kiallWell, even with the async call, we already know the new resources ID, so I don't think a dedicated async-status endpoint is necessary17:43
kiallAnd, a dedicated async-status endpoint would be counter to what we see other OpenStack projects doing - Nova is the prime example for async calls17:44
kiallAs an example, if if POST /v2/records17:44
kiallYou will get a Location: /v2/records/{record-uuid} header, and a body that looks something like {"id": "..", "status": "PENDING"} in response17:45
kiall(with a 202 Accepted status)17:45
kiallFrom there, you can query /v2/records/{record-uuid} and check if status has changed to ACTIVE17:45
CaptTofuthat sounds logical17:46
vinodmr#agreed on returning status similar to Nova17:46
kiallOn the other hand, some backends might not be aync. In which case, a 201 Created would be returned along with {"id": "..", "status": "ACTIVE"}17:46
CaptTofu#agreed on returning status similar to Nova17:46
CaptTofuleaves room ...17:46
jmcbrideAgreed, seems like extra overhead to have an additional asyc call.  Can we support providing a unique ID on each request?17:47
kiallThe async parts are going to require some changes in how out backends are implemented, but I wan't to make sure the spec covers what we need17:47
*** zane has quit IRC17:47
*** zane has joined #openstack-meeting-alt17:47
kialljmcbride: I'm not sure I follow? Let's say a record is updated twice in a row, one of those updates has to "win" (or the changes need to be "merged" e.g. ttl and rdata change can be merged)17:48
kiallThe record has a unique ID, and a "status" field17:48
kiallonce all pending changes are live, status will change to "ACTIVE"17:49
kiallAlso, we do have a unique request ID already, which gets dropped into error response bodies, and the X-Dns-Request-Id response header17:50
*** markwash has joined #openstack-meeting-alt17:50
kiallBut - that's intended for debugging rather than end users17:50
jmcbridekiall: I think we are coming around.  Basically, RAX DNS' current async approach works around some internal challenges… but the approach you specify probably better handles it.17:50
jmcbridetime check - we have 10 more minutes17:51
kialljmcbride: yea, Maybe eankutse and myself can go through some of the challenges you guys have over the next few days, that will help ensure we get something that works for everyone17:51
CaptTofuwhen should be discuss openstack in Hong Kong?17:51
jmcbride#agreed17:51
kiallOkay! So ..17:51
jmcbrideCaptTofu - I would like to discuss that next as well (skip the documentation topic)17:52
kiall#action kiall and eankutse to discuss API over the next few days17:52
kiall#topic Identify opportunities to maximize collaboration17:52
*** openstack changes topic to "Identify opportunities to maximize collaboration (Meeting topic: designate)"17:52
kiallMoving on quickly :)17:52
eankutsekiall: ok17:52
jmcbrideso, in proposing this item, I feel our project interim goals are a little different from other official and incubated projects.17:53
kialljmcbride: so, are you guys going to make it to Hong Kong?17:53
CaptTofuI have yet to submit a talk but was going to base it off our last talk17:53
CaptTofuthough you guys are now involved so...17:54
jmcbrideit seems like designate would benefit more from an interim designate "summit".17:54
kialljmcbride: that sounds like it could be fun :) What did you have in mind?17:54
CaptTofuPrague?17:54
eankutse:-)17:54
jmcbrideI propose we come together before that17:54
jmcbridefor targetted and focused sessions to advance designate towards official Openstack project status.17:55
simonmcci like the sound of that17:55
CaptTofu#agreed on focus on official Openstack project status17:55
kiallYea, I think that's a great idea. (Travel budgets this year are going to be tight ;))17:56
jmcbrideBasically, we are still unsure about whether we should attend Hong Kong — because we thing a better return for our investment would be something before that with targets.17:56
jmcbrideHong Kong = $$$$$$$17:56
simonmccjmcbride did you have a location & month in mind?17:57
kiallYea, I would assuming EU <-> US is about the same though :)17:57
kialljmcbride: did you have a time/place in mind?17:57
kiallsimonmcc: beat me to it!17:57
jmcbrideAustin Tx (or something closer) = pennies :)17:57
jmcbridealthough I would LOVE to see Ireland!17:57
CaptTofuheheh17:57
simonmccmid-point for "us" would be new york, but if you can host in Austin, that might work too17:57
CaptTofuwell,17:57
CaptTofuwe are thinking internally as a team to go to Ireland mid Sept. possiby17:57
CaptTofupossibly, even17:58
jmcbrideYou can stay at my house, its right near the river (do you like canoing?)17:58
CaptTofuAustin has a good Whole Foods17:58
tsimmons#agree on Party at Joe's house17:58
jmcbrideOK, why don't we have an action for CaptTofu and I to chat details for a slumber party17:58
kiallHah - So, jmcbride let's sync up over the next few days before we agree anything ;) Would need to find out what we can do on our side etc17:59
CaptTofu#action figure out this meeting thing17:59
kiall#action jmcbride and CaptTofu to sync up on party17:59
jmcbridenice.17:59
kiall#topic How do we identify more small tasks that developers and testers can work on17:59
*** openstack changes topic to "How do we identify more small tasks that developers and testers can work on (Meeting topic: designate)"17:59
CaptTofuand how to involve other organizations17:59
jmcbrideI think that topic can be closed for now.17:59
kiall1 min to go ;)17:59
jmcbrideCaptTofu, good point!17:59
kiallSo .. We've been a bit overloaded on our side over the last week or so18:00
CaptTofukiall: what we have been doing - I think is a good start18:00
kiallAnd, filing small bugs that we didn't need fixed yesterday has been hard :)18:00
CaptTofufind a bug, find someone with the most expertise in that area18:00
*** colinmcnamara has quit IRC18:00
jmcbridekiall: regarding small bugs, we are finding that we simple need to get it deployed and start using it before we can provide real feedback on defects.18:01
kiallWe'll continue trying to get bugs filed rather than simply fixing non-critical things :) But I'm hoping you guys will get things up and running, then start noticing things we don't¬18:01
jmcbrideHey guys, I think we need to head to another commitment, shall we call it a day?18:01
kiallYea :)18:02
kiallLets18:02
simonmccthanks everybody18:02
kiallThanks all - and we'll sync up again tomorrow/the day after18:02
kiall#endmeeting18:02
eankutsebye18:02
*** openstack changes topic to "OpenStack meetings (alternate)"18:02
openstackMeeting ended Wed Jul 24 18:02:20 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-07-24-17.00.html18:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-07-24-17.00.txt18:02
betsybye18:02
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-07-24-17.00.log.html18:02
kiallMeeting logs ^18:02
jmcbridecheers all! See ya later.18:02
*** vinodmr has left #openstack-meeting-alt18:03
*** eankutse has left #openstack-meeting-alt18:03
*** tsimmons1 has joined #openstack-meeting-alt18:04
*** jergerber has joined #openstack-meeting-alt18:05
*** demorris has quit IRC18:06
*** jmcbride has quit IRC18:07
*** betsy has quit IRC18:07
*** betsy_ has joined #openstack-meeting-alt18:07
*** tsimmons1 has left #openstack-meeting-alt18:07
*** colinmcnamara has joined #openstack-meeting-alt18:07
*** tsimmons has quit IRC18:07
*** jmcbride has joined #openstack-meeting-alt18:09
*** zane has quit IRC18:10
*** zane has joined #openstack-meeting-alt18:12
gchengHi all,18:12
simonmccgcheng are you here for the DNS/Designate meeting?  You just missed it, we finished already18:14
gcheng@simonmcc, I'm here all the time with two ears. :)18:15
simonmccgcheng :-)18:15
gchengso is nova-dns will be, or already abandoned by Designate/Moniker?18:16
simonmccnova-dns is largely abandoned AFAIK18:17
*** demorris has joined #openstack-meeting-alt18:17
gchenggreat. I see latest code update to nova-dns was one year ago, but still like to confirm from your Captains.18:18
*** zane has quit IRC18:18
*** zane has joined #openstack-meeting-alt18:18
simonmccwe should move this back to #openstack-dns :-)18:19
simonmccit's not "ours" to abandon18:19
*** jcru|away is now known as jcru18:19
gcheng:)18:20
*** pdmars has joined #openstack-meeting-alt18:20
*** msisk has left #openstack-meeting-alt18:26
*** sarob has joined #openstack-meeting-alt18:39
*** mugsie has left #openstack-meeting-alt18:39
*** sarob has quit IRC18:42
*** sarob has joined #openstack-meeting-alt18:42
*** jergerber has quit IRC18:53
*** sarob has quit IRC18:56
*** sarob has joined #openstack-meeting-alt18:57
*** jergerber has joined #openstack-meeting-alt18:57
*** ashestakov__ has joined #openstack-meeting-alt19:01
*** sarob has quit IRC19:02
*** zane has quit IRC19:05
*** zane has joined #openstack-meeting-alt19:12
*** zane has quit IRC19:13
*** zane has joined #openstack-meeting-alt19:13
*** jergerber has quit IRC19:13
*** tsg has joined #openstack-meeting-alt19:13
*** jmcbride1 has joined #openstack-meeting-alt19:16
*** jmcbride has quit IRC19:16
*** jergerber has joined #openstack-meeting-alt19:20
*** gcheng has quit IRC19:27
*** sarob has joined #openstack-meeting-alt19:29
*** colinmcnamara has quit IRC19:39
*** sarob_ has joined #openstack-meeting-alt19:42
*** sarob has quit IRC19:46
*** sarob_ has quit IRC19:47
*** colinmcnamara has joined #openstack-meeting-alt19:54
*** KennethWilke has joined #openstack-meeting-alt19:55
*** DandyPandy has joined #openstack-meeting-alt19:57
*** robertmyers has joined #openstack-meeting-alt19:57
*** hub_cap has joined #openstack-meeting-alt19:59
*** jmontemayor has joined #openstack-meeting-alt19:59
*** earthpiper has joined #openstack-meeting-alt19:59
hub_cap#startmeeting trove20:00
openstackMeeting started Wed Jul 24 20:00:18 2013 UTC.  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
vipul\o/20:00
robertmyerso/20:00
pdmarso/20:00
hub_caplets give a min20:00
*** datsun180b has joined #openstack-meeting-alt20:00
*** esp has joined #openstack-meeting-alt20:00
KennethWilkehi20:01
earthpiperello20:01
*** TheRealBill has joined #openstack-meeting-alt20:01
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting20:01
datsun180bhello20:01
kevinconway7o20:01
*** grapex has joined #openstack-meeting-alt20:01
hub_cap#link http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-07-17-20.00.html20:01
hub_cap#topic action items20:01
*** openstack changes topic to "action items (Meeting topic: trove)"20:01
*** imsplitbit has joined #openstack-meeting-alt20:01
hub_capheh so AI's will be quick20:01
imsplitbito/20:01
hub_capvipul: any doc update on the wiki?20:01
grapexo/20:02
vipulhub_cap: done!20:02
hub_capive moved every page ive looked at20:02
imsplitbityay!20:02
vipulsee https://wiki.openstack.org/wiki/Trove20:02
hub_capdone?20:02
hub_capi moved two today20:02
*** SlickNik has joined #openstack-meeting-alt20:02
hub_capoh done w/ that page20:02
SlickNiko/20:02
*** amytron has joined #openstack-meeting-alt20:02
hub_capcool20:02
vipulare there more pages that got lost?20:02
hub_capoh ya vipul tons20:02
vipulmoved a bunch of them as well20:02
hub_capthe next one i think we covered eh?20:02
hub_capsearch reddwarf20:02
hub_capor red dwarf20:02
hub_capanyhoo we can just update as we see fit20:03
hub_capits for older stuff anyway20:03
hub_caplike i did configuration editing today cuz a mirantis guy asked me about it20:03
hub_capso i thikn the next AI is already taken care of eh?20:03
hub_capStop test and Unsuccessful Restart test thing20:03
hub_capwe decided to move it out of bb testsing20:03
cp16net\o20:03
grapexYep20:04
hub_cap=o= four arm me20:04
hub_capor my top gun pin20:04
hub_capok cool lets move on then20:04
hub_capim going ot leave the api discussion to last20:04
hub_capso ill skip to imsplitbits topic20:04
cp16net\^o20:04
cp16netmy muscles20:04
cp16netlol20:05
hub_caplol cp16net20:05
hub_cap#topic Replication API update20:05
*** openstack changes topic to "Replication API update (Meeting topic: trove)"20:05
hub_capso imsplitbit tell us about replication api20:05
imsplitbitwell we made the concensus20:05
imsplitbitthat we were going to use /clusters as a helper for cluster ops20:06
imsplitbitinstance ops stay in /instances20:06
djohnstoneo/20:06
imsplitbitI've begun work on the /clustertypes20:06
imsplitbitwhich is "flavors for clusters"20:06
hub_capcool20:06
imsplitbitthats about all I have at this point20:06
hub_capthats a good way to put it20:06
hub_capok great20:06
hub_capnow for the topic at hand20:06
hub_capthe hp guys dont know much about this yet so20:06
imsplitbitI HATE IT20:07
* hub_cap makes vipul read the Windows ME user guide20:07
imsplitbitlol20:07
imsplitbitwanted to start early :)20:07
* hub_cap pokes SlickNik20:07
vipulwindows fun!20:07
KennethWilke3.1 is better20:07
imsplitbitouch20:07
* SlickNik wakes up20:07
hub_capvipul: SlickNik take a minute to read20:07
imsplitbitME...20:07
hub_cap#topic capabilities20:07
*** openstack changes topic to "capabilities (Meeting topic: trove)"20:07
hub_cap#link https://wiki.openstack.org/wiki/Trove/extensionsrefactor20:07
hub_capi prefer to use the term capabilities to extension earthpiper20:07
hub_capfwiw20:07
earthpipersho nuff20:08
hub_caplets give till 20:10 to finish reading it and talk about the pro/con20:08
earthpiperbrb20:08
earthpiperthen20:08
kevinconwayhub_cap: 20:10 central standard time right?20:08
hub_capheh yes kevinconway20:08
hub_capnot utc20:08
KennethWilke...20:08
KennethWilkei only take epoch20:08
*** KennethWilke has left #openstack-meeting-alt20:08
kevinconwayso for the next five hours?20:08
hub_capWed Jul 24 20:08:27 UTC 201320:09
*** KennethWilke has joined #openstack-meeting-alt20:09
hub_capu have 1 1/2 minute to keep annoying me kevinconway20:09
hub_cap;)20:09
kevinconwayits 15:10 CST20:09
kevinconwaywhy is time so confusing?20:09
hub_capcuz in openstack u only speak in utc20:09
grapexhub_cap: Would it be bad form to add to that wiki article at this time?20:09
hub_capgrapex: ummm yes20:10
hub_capwell no20:10
KennethWilkei want integer epoch timestamps, or you do it right!20:10
hub_capbut no one would read it20:10
KennethWilke:)20:10
hub_capbut its ok grapex to do that because u wnt the information to persist20:10
hub_capso go for it20:10
hub_capu can always interject those points when relevant20:10
KennethWilkelink us your diff!20:11
hub_capLOL just click history20:11
hub_capok vipul SlickNik have a feel for whats going on?20:11
hub_capearthpiper: back?20:11
SlickNikyeah20:11
vipulkinda20:11
hub_capkevinconway: happy that we are in utc time?20:11
KennethWilkehub_cap: he is afk20:11
hub_capk20:12
vipulso we want to dynamically load a service.py based on service_type?20:12
hub_capso yes20:12
cp16neti'm never in utc time20:12
hub_capbut its more than that20:12
hub_capits dynamically load the api based on service_type20:12
KennethWilkei think we want to consider the impact to the api over implementation at this moment20:12
hub_capas in, /instances/id/users changes payload based on what type your instance is20:12
KennethWilkeif i understand correctly20:12
vipulhmm20:12
hub_capcorrect KennethWilke20:13
SlickNikso not just guestagent, but the trove-api as well.20:13
hub_caplets hold off on opinions till earthpiper gets back20:13
hub_capcorrect SlickNik20:13
earthpiperyeah20:13
hub_capthe arguments are 1) the user shuldnt care that he has a redis type, he should just pass info to /users (yes bad example)20:13
vipulSo .. isn't it kinda odd that the body would change based on a type of database?20:13
imsplitbityou cannot have an opinion unless earthpiper is present???20:13
hub_capno imsplitbit u cannot20:14
imsplitbitlol20:14
hub_caphe is driving this20:14
KennethWilkevipul: i think so20:14
hub_capgo earthpiper (pips)20:14
hub_capthe input/output can differ based on the capability20:14
SlickNikbtw, hello earthpiper!20:14
earthpiperHi I am Conrad at Rackspace.20:14
datsun180boh that makes sense now20:14
vipulhowdy20:14
earthpiperIf you don't know my net handle =)20:14
*** zane has quit IRC20:15
KennethWilkehello, i am kenneth at rackspace20:15
KennethWilkejust... in case20:15
imsplitbitgreetings20:15
imsplitbitok go20:15
hub_caphe is the only Kenneth at rackspace20:15
imsplitbitlol20:15
datsun180bwhat's the frequency20:15
kevinconwayHello, I am Inigo Montoya… You killed my father.20:16
hub_capLOL20:16
imsplitbitearthpiper: go20:16
hub_capsrsly GO20:16
hub_capGO GO GO20:16
hub_capweve burned 6 minutes on intros :)20:16
imsplitbitexactly20:16
earthpiperSo what do you guys think?20:16
hub_capno20:16
imsplitbitI think that sushi sounds great20:16
SlickNikhub_cap: trying to understand the motivation for this...20:16
hub_captell us what you think earthpiper20:16
earthpiperOh cool.20:16
earthpiperThanks20:16
hub_capSlickNik: earthpiper will explain20:16
hub_capwhat is the motivation earthpiper20:17
earthpiperSo.. the problem with current extensions is they load everything in that directory.20:17
earthpiperWe want Trove to support more Databases.20:17
earthpiperand right now the application is rather monolithic.20:17
*** demorris has quit IRC20:17
*** zane has joined #openstack-meeting-alt20:17
hub_caplets stick to the api earthpiper20:17
hub_capnot the impl20:17
hub_capthe why so to speak20:17
juicei have a high level question20:18
earthpiperYou get a routing conflict with current extensions if you have different requirements for instances functions.20:18
hub_capcorrect20:18
earthpiperSo like Users for postgres users for mysql etc.20:18
hub_capso /users doesnt make sense if you host > 1 database type in the same installation20:18
KennethWilkeor on my redis boxen20:19
hub_caphow do u differenciate between postgres' users and mysql users20:19
hub_capthe one u add users too KennethWilke ;)20:19
vipulare they really different types of users?  they are 'database' users20:19
hub_capjuice: this is irc, ask away20:19
imsplitbitassuming we will allow a redis and mysql install on one instance yes?20:19
juiceyeah I am formulating it :)20:19
hub_capone installation imsplitbit20:19
hub_capnot one instnace20:19
espregarding the bit about different POST body's in the API will the POST body's still follow the same structure even though they will be different?20:19
KennethWilkethey may have different parameters based on database implementation20:19
*** amytron has quit IRC20:19
KennethWilkeor requirements20:19
imsplitbitok one aggregated infrastructure to manage all dbs20:20
hub_capyes for instance postgres requires a default db, from what i think jeffe said20:20
juicewhat level of abstraction do we want for trove or what level of abstraction do we think is most suitable for trove20:20
earthpiperWell we should not make a person only host one type of db system per cluster.20:20
hub_capand this is more than just /users its /anything20:20
*** SergeyLukjanov has quit IRC20:20
KennethWilke /db_specific_feature20:20
hub_capcorrect20:20
hub_capit could be /flushkeys for redis20:20
juiceis that we plan on configuring trove at deploy time for a specifc implementation and have it build those instance types20:20
hub_cap;)20:20
hub_capjuice: it shoudl be able to handle > 1 service_type20:20
hub_capin the same api20:20
juiceor is trove supposed to standup and handle any db implementation type20:20
hub_capyou configure it juice20:21
vipulso there are two types of things...20:21
hub_capto handle what u want to support20:21
hub_capavail_types=postgres, mysql, percona, redis20:21
hub_capso to speak20:21
vipuladditional operations on a db_type.. .which is differnt from the same operation, but different request for db_types20:21
juiceand from the end user do they know which service type they are getting20:21
hub_capyes so same uri, different body20:21
vipulI think we can support db_type specific actions20:21
hub_capsound familar?20:21
juicewe don't allow them currently to specify the service type on boot20:21
hub_cap /actions {}20:21
jcooleythe thing is, if you are managing multiple databases with the same infrastructure, what are you gaining if each one has a completely different command-implementation?20:22
grapexvipul: I don't know- so far it seems like the users call has had to change a lot. We've added things to it and then found out it was ambigious because of how MySQL worked. Maybe I've mistinterpretted what you're saying, but I can't imagine users would "just work" for all db types.20:22
SlickNikjuice: this proposal seeks to change that, I think.20:22
hub_captechnically juice we do20:22
jcooleyi mean, why not just clone the 5 or 6 nodes20:22
hub_cappass service_type in to the create, and watch it go20:22
jcooleyright,20:22
jcooleyif it doesn't work for a set of common types, why force a common infrastructure?20:22
hub_capwhat benefit does having a bunch of duplicate api nodes w/ a single config diffence buy you jcooley?20:22
hub_capits gonna be the same codebase20:23
jcooleyi dunno, i have different api nodes for nova, swift, savanna, ...20:23
hub_capso the difference between 6 nodes is gonna be service_type=blah20:23
vipulgrapex: Right, so I agree there may be differences, and I think instead of a body that's compeletely different for different databases, we come up with either a genericized API that works across, or we make things optional20:23
juiceok so the user specified the service type and they are now wanting to interact with a redis or postgres instance20:23
KennethWilkejcooley: but you should be able to spin up ubuntu and centos or whatever on one nova deployment20:23
earthpiperThis is just to make the deployment of new db types easier.20:23
jcooleyright, with the same api20:23
KennethWilkeon the same boxes if you would like20:24
earthpiperor not like20:24
jcooleywell, that's where i'm getting lost20:24
earthpiperyou can do what you want with it20:24
grapexvipul: I think having a generic user call won't be satisfying for power users, unless we offer it in addition to a type specific call20:24
datsun180bso even if not every db has a concept of users, ideally they'll all have a concept of connections. is that a common ground we can build off of?20:24
hub_capnot really20:24
hub_captake redis20:24
grapexSo there could be a user create call specific for MySQL, but then we could make a generic one for any DB.20:24
hub_capno users at all20:24
jcooleysure, flexibility is nice but i'm not seeing the code sharing.20:24
hub_capnil20:24
jcooleyonly infrastructure sharing.20:24
KennethWilkeusers?20:24
earthpiperIt returns 40420:24
earthpiperrather than a 20020:24
earthpiperbecause that route is not defined for redis20:25
hub_capso do we, since redis can support resizes, resets, all the things trove /instances support20:25
hub_capdo we have to stand up a diff service to host it?20:25
hub_capand do we need a different docbook altogether?20:25
hub_capjust so we can have separate services?20:25
vipulhub_cap: No, i think it's fine to return not-implemented if things don't match20:25
vipulbut that not impelemtned should come from the Guest Agent20:25
hub_capi dont agree20:25
vipulwhich determines whether that operation can be done or not20:25
hub_capid prefer to return "there is no route for this"20:25
KennethWilkei think not implemented should be returned by the api20:26
datsun180bmore informative than a 40420:26
hub_capthe same thing when you pass /instances/id/honeybooboo20:26
vipulexactly20:26
grapexYeah, we don't want the guest agent to have to be that intelligent about what the API can do.20:26
cp16netyeah not implemented doesnt sound like something that should be returned20:26
jcooleyi like vipul's idea of placing the differences in the guest agent...20:26
vipulwhy is it that they can invoke the same route at the same endpoint in oen case but not the other20:26
juicejumping to solutions here but what comes to mind is that each database would have it's own discrete api command structure and TROVE simply becomes a router to the different api implementations20:26
hub_capjuice: that is one of the approaches20:27
SlickNikgrapex: but the guest agent needs to be intelligent about what the API can do since the guestagent will be the one doing it!20:27
kevinconwayhub_cap: 501 Not Implemented20:27
juiceyou might even extend that and have different instances of task manager out there for the various implementations20:27
grapexjuice: That's my favorite idea, with the addition that you'd have a generic instance resource that could do actions that were performable by any db type20:27
hub_capnaw taskmgr shoudl be generi20:27
hub_capc20:27
juicethis approach allows you to keep a generic front end yet have documentable and implementation specific apis20:27
hub_capthe big differences are the api+guest impl20:27
grapexSlickNik: Of course, but the guest agent shouldn't have to understand someone made a request for a Redis operation and the server is MySQL20:27
vipuljuice: that means Trove has many APIs20:28
hub_capstop typing20:28
grapexThe API should know that and not even ask the guest agent20:28
hub_capdo we agree that trove can host > 1 capability20:28
KennethWilkeyes20:28
vipulyes20:28
earthpiperyes20:28
grapexyes20:28
kevinconway#vote yes20:28
hub_capgood20:28
robertmyersyes20:28
cp16netyes20:28
cp16net#voted20:28
hub_capi can start a vote kevinconway ;)20:28
vipulo/20:28
hub_capok good20:28
SlickNik#agreed20:28
hub_caplets move on20:28
KennethWilke#done20:28
hub_capnow its a matter of the proposal20:28
hub_capdo we 1) dynamically change the route20:28
hub_capor 2) define namespaces for the routes20:29
vipuli see 3 things here...20:29
KennethWilke220:29
hub_cap1 is potentially more confusing for the user (imho) and 2 is potentially more annoying for the user (since there is 1 type)20:29
jcooleygrapex: disagree.20:29
hub_capwhats 3?20:29
vipul1. choosing which extensions should be loaded instead of all20:29
vipul2. dynamic route / dynamic body20:29
vipul3. fixed route w/namespaced route20:30
jcooleyapi should not have all the intelligence or we have to bake the polymorphism into it20:30
hub_caphold up vipul20:30
hub_cap1 is a installation procedure20:30
hub_capand 2/3 are the api differnces20:30
grapexI think we agreed 1 wasn't an option if there's >1 capability20:30
hub_cap1 will happen20:30
earthpiperCorrect grapex20:30
esphub_cap: is 2) above basically defining new routes for each db type?20:30
vipulok.. makes sense20:30
KennethWilkeesp: yes20:30
hub_capu will choose the types you want to run based on your needs20:30
hub_capavail_types=cassandra,oracle,couchdb20:31
espKennethWilke: thx.  yeah I like that better.20:31
juicewe should revise that original vote to say "trove should dynamically support > 1 impl at runtime"20:31
KennethWilkeesp: yw :)20:31
grapexjuice: Good idea20:31
hub_caphuh!?!?20:31
hub_capno20:31
vipuli'm ok with dyanmically loading a route in the backend, but i am not ok with those supporting differnt bodies20:31
cp16net2: means to me that you dynamically look up the instance type and do the work20:31
hub_capit was jcooley that brought up to not support > 120:31
vipuli can see that we may have different validation rules for a db_type20:31
cp16net3 means that its defined in the uri20:31
hub_capwe are getting out of hand20:31
vipulbut the request body shoudl be the same/similar20:31
hub_caplet me rephrase20:31
KennethWilkecp16net: in any other case do you not need to know the instance type if trove supports multiple dbs?20:31
* hub_cap bangs the gavel20:32
jcooleyhub_cap: only meant that if they're really different and you can't share implementation, you're not gaining anything.20:32
hub_capwe will support > 1 impl in the same codebase/install/api server20:32
hub_capperiod20:32
hub_capif you want cassandra and redis, you can get them20:32
hub_capthats not being argued20:32
grapexvipul: I decided I couldn't stand the totally dynamic, every type uses the same request path idea when I realized different db_types would eventually have different bodies for the same request paths.20:32
hub_capif u have to restart the api server to install a new type, thats fine20:32
* hub_cap bangs the gavel and points at grapex20:32
KennethWilkegrapex: i agree20:32
*** KennethWilke has left #openstack-meeting-alt20:33
*** abaron has quit IRC20:33
*** KennethWilke has joined #openstack-meeting-alt20:33
hub_caplol netsplit20:33
grapexhub_cap: Am I in contempt?20:33
hub_capyes20:33
* KennethWilke shame20:33
hub_cap:P20:33
vipulyou have the floor hub_cap20:33
hub_capso the question is this20:33
imsplitbitNO20:33
hub_capdo we have an api that supports dynamic bodies, because we cannot guarantee that every call to /users will be the same20:33
imsplitbitI just wanted to be in contempt too :)20:34
hub_capor do we support namespaced urls, where the payload is the same20:34
grapexhub_cap: May I approach the bench?20:34
hub_capbut you have to type the type in20:34
hub_capgrapex: aye20:34
earthpiperI got dibs next.20:34
hub_capyes you do earthpiper20:34
imsplitbitthen me20:34
KennethWilkethen i!20:34
hub_capno imsplitbit20:34
hub_capnever20:34
grapexAnother thing to consider is in addition to namespaced requests for specific types, we could also make requests to the existing instances path w/o the db_type to do things which *ANY* instance could do20:34
imsplitbitdamnit20:34
grapexThink of it like calling a super class's interface20:35
hub_capit will, resizes will still go thru /instance/id20:35
hub_cap /instance/id/resize20:35
hub_capNO ACTIONS20:35
imsplitbitbut we all *love* actions20:35
grapexThose are our favorite!!20:35
juicedisagree20:35
* juice notes sarcasm20:35
hub_cap /instance/id/resize, /instances/id/user vs /instances/id/mysql/user, /instances/id/user vs /instances/id/redis/user20:35
grapexBut they're so hard to use... :(20:35
grapexj/k20:36
grapexPut me back in contempt20:36
earthpiperSo can I interject really quick.20:36
* hub_cap urges grapex to use Windows Millennium Edition20:36
espI think it would be less redundancy (in your DTO or value objects) if request payloads and response payloads are the same across db_types.20:36
hub_capearthpiper: plz do20:36
earthpiperOk20:36
earthpipertake a gander at client flows20:36
earthpiperat the bottom of the propsal20:36
earthpiperhttps://wiki.openstack.org/wiki/Trove/extensionsrefactor20:36
hub_capesp: we cant guarantee that20:36
SlickNikhub_cap: While I love the idea, I'm worried that this opens up the opportunity for the APIs of the different implementations to diverge to a point where they look like completely different APIs. This means that as a consumer, I have to relearn / re-work the API every time I need a different type of instance. This seems like a serious disadvantage for a managed db solution, which should make my life easier by providing somewhat of a consiste20:36
esphub_cap: nope but it's a good place to start.20:37
grapexesp: You could of course reuse classes that were similar as base objects between the request bodies of various types.20:37
vipulSlickNik: +120:37
imsplitbitSlickNik: +120:37
hub_capim not sure what SlickNik is saying20:37
hub_capvoting for #1 or #2?20:37
KennethWilke1 i believe20:37
vipulneither20:37
hub_capor voting against to ever have /usrs20:37
datsun180bso i have a half-baked idea wrt to marrying namespaces and dynamic20:37
grapexSlickNik: Do you mean a user switching between MySQL and Percona or something similar like that?20:37
SlickNiknot taking a side of the #1 or #2 fence yet.20:37
KennethWilkemay i?20:38
hub_capi dont think earthpiper got to interject20:38
hub_caphe just said go read some shit20:38
KennethWilkeearthpiper: gogogog20:38
earthpiperSo the problem is20:38
earthpiperIf we support other databases20:38
earthpiperstuff changes20:38
espgrapex: agreed but I guess I'd like to see how different each imp will be to say for sure20:38
earthpiperperoid20:38
vipulIf we have a single endpoint, and a single API... why would someone be required to figure out what the body or URI shoudl be based on a type20:38
earthpipervipul: that does not matter20:38
earthpiperhow else would you do it?20:39
earthpiperDifferent DB20:39
earthpipermeans a possible different contract to do stuff20:39
imsplitbitvipul: +120:39
vipulYou have a genericized body20:39
grapexI think the issue is, we're going between MySQL and NoSQL so stuff is going to change20:39
vipulsay someone  is using Java20:39
robertmyerswhy don't we just remove the ability to create users?20:39
robertmyersdone20:39
grapexI think between SQL db's things could be similar20:39
vipulthey are likely going to be bulidng a object model of our request /responses20:39
KennethWilkegrapex: +120:39
hub_caprobertmyers: you just made our director cry20:39
grapexWhat if we had, in addition to "mysql/instances/<instance_id>" and "postgres/instances/<instance_id>", a "sql/instancs/<instance_id>" which was a subset.20:39
vipulthey are going to be required to build new object models evyer time we add another db?20:40
grapexUses could use "sql" if they didn't care about MySQL specific details20:40
datsun180bwell for dbs that don't have users, how do you get your data to and from the db?20:40
hub_capsure but i think u have it backwards grapex20:40
imsplitbitdatsun180b: I like your concept of "connection"20:40
earthpiperdatsun180b: reddis does not support usetrs20:40
KennethWilkedatsun180b: redis exists20:40
earthpiperredis*20:40
hub_capinstances/id/mysql vs instances/id/sql20:40
earthpiperbut it does support backups20:40
datsun180bdo you communicate with redis via telepathy20:40
grapexvipul: Not if we were smart and made our schema use superclasses appropriately. The amount of changes could be minimized.20:40
vipulI still feel like there are different ways to handle thigns that service types do not support20:40
KennethWilkenope, sockets20:40
earthpiperonly sockets.20:40
hub_capuser sockets20:40
datsun180bso, a connection20:40
hub_cap:P20:40
earthpiperOh20:41
kevinconwayso /instances/id/sockets20:41
earthpiperSo we switch userrs to connections...20:41
hub_capok lets stop talking about users20:41
KennethWilkethank you!20:41
hub_caplets talk /flushkeys20:41
KennethWilke:)20:41
datsun180binstances/id/connections20:41
grapexOr rather, instances/id/users, whose request body is a subset of mysql/instances/id/users...20:41
hub_capthe goal here is _NOT_ to solve /users20:41
imsplitbithub_cap: lets talk /flush20:41
hub_capits to solve /any_db_operation20:41
*** ashestakov__ has quit IRC20:41
imsplitbitwhich applies to much more than redis or mysql or postgres20:42
hub_cap /rebalance_ring20:42
datsun180bwhere for mysql dbs instances/id/connections is an alias for instances/id/mysql/users20:42
datsun180bmaybe a 301 MOVED PERM20:42
hub_capdatsun180b: lets not reinvent users20:42
hub_capthis is not a conversation about users20:42
hub_capits a conversation about /anything for a specific db20:42
datsun180bi'm using it as an example to build a common ground20:42
earthpiperwe don't need to fix users. we need to fix the routing for DB specific stuff.20:42
vipulhaving additional DB operations is totally fine -- leave it to guest agent to determine whether it's something it can act on or not20:42
earthpipervipul: how do you pass it the message then?20:42
earthpiperWithout extending the API interface20:43
earthpiperso the user agent knows it is being passed that?20:43
earthpiperHow is that possible?20:43
hub_capsure so you will have /instances/id/rebalance20:43
vipulyou'd have to have a common rpc_api across all guest agents20:43
juicecan we do internal rerouting/redirects20:43
vipulbut the mysql_impl will decide it's not possible20:43
earthpiperHow does the user20:43
grapexAgain, why make the guest agent determine the type? The API knows the type and shouldn't even bother. In fact, it should validate that the user made a bad request well before considering talking to the guest.20:43
hub_capsee to me thats ugly vipul20:43
earthpiperwait20:43
hub_capevery guest has to impl, optionally, ANY call that ANY db can do?20:43
earthpiperIt's not the matter of it being ugly20:43
KennethWilkevipul: i don't think the api should shove anything the user gives it into rabbit20:43
datsun180bi foresee a lot of noops hub_cap20:44
earthpiperIt's a matter of how do you do it without extending the user api20:44
vipulfine, we can block that at the API level20:44
vipulwith policy based config or something20:44
earthpiperNo20:44
hub_capya datsun180b20:44
vipulthat's not the point20:44
earthpiperhow can the user send the message?20:44
earthpiperTo do whatever you want?20:44
hub_cap to /instances/id/something20:44
earthpiperYou have to extend the user api20:45
vipulthe user will see a consistent API with every available 'operatation'20:45
earthpiperperiod.20:45
hub_capobvi :)20:45
grapexHow about /instances/id/void redirects dynamically to the typed request path. :)20:45
hub_capsee id rather have namespaced apis w/ capabilities20:45
* juice is reading earthpipers proposal20:45
hub_capmysql/ can do users, schemas, and making_coffee20:45
*** gcheng has joined #openstack-meeting-alt20:45
juicedid we all have a chance to think about this before coming to the meeting20:45
KennethWilkeno20:45
hub_capcassandra/ can do rebalance_ring, users and making_donuts20:45
vipulnot really :)20:45
KennethWilkebut i did20:45
KennethWilke:)20:45
juiceperhaps we have bantered enough and need some time to give it some self-reflection and come back to this20:46
KennethWilkebecause i do not want to use trove for redis20:46
SlickNikearthpiper: I think the idea is to extend the API to every possible operation. And let the guestagent decide if it supports it or not. Not sure I like that….20:46
KennethWilkei mean mysql** sorrty20:46
hub_capredis/ CANT DO USERS (god tina eat your food - napolean voice)20:46
KennethWilkelol20:46
imsplitbitjuice: I agree20:46
vipuljuice: +1 i don't think we have enough background really to be able to make a call20:46
hub_capu know i feel thats valid20:46
earthpiperSlickNik: I don't like that idea either.20:46
hub_capcan we meet tomorrow to discuss?20:46
grapexhub_cap: Google hang outs?20:46
imsplitbitI am still a fan of simple generic api and internally we route/return the right stuff20:46
juiceworks for me20:46
vipulimsplitbit: +1 that's what i was leading towards..20:47
hub_capi was thinking irc grapex20:47
KennethWilkei think irc as well20:47
vipulthe user should see consistency20:47
imsplitbitthis /sql /nosql /mysql /postgres thing seems to be too confusing for the end user to me20:47
datsun180bif only we had a channel we were all on all day together20:47
grapexhub_cap: Seems like short notice20:47
hub_capsee vipul id argue that /users w/ different payloads is _not_ consistant20:47
SlickNikI'd like to think about this some more as well. +1 to meeting tomorrow.20:47
KennethWilkeconsistency seems hard unless we offer consistent technologies behind trove20:47
grapexhub_cap: Maybe a bit later?20:47
hub_capbut /mysql/users is20:47
grapexWe can all add to the wiki in the meanwhile20:47
KennethWilkeand redis != mysql != mongo != thing not yet made we want in trove20:47
hub_capdo we need > 24 hrs to ruminate on this grapex?20:47
vipulhub_cap: but then you have postgres/users == mysql/users pretty much20:47
hub_capor is your shcedule booked tomorrow?20:47
imsplitbithub_cap: stop talking users!!!!!!!!!!!!!!!!20:47
imsplitbit:)20:47
hub_capvipul: sure20:47
grapexhub_cap: Hey I know what I want20:47
juicedoes anyone know of resource for various api commands20:48
hub_capfor USERS20:48
hub_capexactly imsplitbit20:48
juicelike a digital copy of 7 databases in 7 weeks20:48
imsplitbitwhen I said users I meant "consumers of the api"20:48
kevinconway#topic users20:48
imsplitbitlol20:48
SlickNiklol20:48
hub_capsorry kevinconway you dont have that power20:48
grapexkevinconway: LOL!20:48
imsplitbit /ban hub_cap20:48
imsplitbitlol20:48
hub_capimsplitbit: even i dont have that power20:49
hub_capi wouldve kicked u alreay20:49
imsplitbitfo rill20:49
imsplitbitok lets keep talking about this20:49
hub_capnaw lets not20:49
imsplitbitmaybe not today20:49
hub_caplets thikn it out20:49
hub_caplets discuss when we are gonna revisit20:49
hub_capi want to tomorrow20:49
imsplitbitI just meant it's way too early to make a decision20:49
hub_capcuz earthpiper is sitting twiddling his thumbs20:49
earthpiperimsplitbit: not its not.20:49
imsplitbitI would be disappointed if we ruled on this in just 50 minutes20:49
earthpiperit's simple20:49
earthpiperthere is no other options really.20:50
earthpiperFor some DB's20:50
imsplitbitearthpiper: it's simple to you because you see it your way20:50
hub_capearthpiper: its not simple20:50
hub_cap+1 imsplitbit20:50
vipulyea I think we finally just got some context behind all this..20:50
hub_capits simple if youve been thinking about it for 2 wks20:50
vipulso need time20:50
vipulto absorbe20:50
hub_capits not if you are vipul20:50
earthpiperIndeed my bad20:50
imsplitbitlol20:50
hub_capand a member of the core team w/o context20:50
imsplitbithub_cap: we have a crypto thing tomorrow20:50
imsplitbitcan we schedule around that?20:50
SlickNikearthpiper: which is the first db service type that we're planning to try this with?20:51
hub_caphmm i dont have a crypto thing tomrrow imsplitbit ;)20:51
imsplitbitsome of us do20:51
hub_capSlickNik: caché20:51
vipultomorrow 2pst works for me20:51
grapexSome of us have pre-existing lives20:51
earthpiperSlickNik: I am working adding redis into trove.20:51
earthpiperon*20:51
hub_caphttp://www.intersystems.com/cache/20:51
grapexOr calendars that were arranged before we had a 24 hour deadline to argue what we wanted to do20:51
imsplitbitI can't do 2 pst20:51
imsplitbitug20:51
grapexI have to go home midway through tomorrow to look after mine and my neighbors dogs20:52
kevinconwayyeah, none of us CST guys are doing 2 pst20:52
imsplitbitearthpiper: I'd like to discuss this with you face to face behind the gym after school :)20:52
grapexSo I'm not sure when I could get back on until about 1 pst20:52
kevinconwaythats like… X;XX o'clock20:52
hub_capahh can u not do irc w/ the dogs grapex? understandable if not20:52
hub_capid like you to participate20:52
vipulimsplitbit: lol20:52
hub_capi want hte core team to agree20:52
earthpiperimsplitbit: you got bad knees dawg.20:52
hub_capor ill jus tmake a decision20:52
imsplitbitearthpiper: and you can't run that fast :)20:53
hub_capso i want vipul SlickNik grapex hub_cap to decide20:53
grapexhub_cap: I just don't want to pick a time when I'm in a meeting at Rax our in route20:53
vipul11pst?20:53
earthpiperimsplitbit: I do like cake.20:53
hub_capgrapex: lol OF COURSE!20:53
KennethWilkepunch and pie?20:53
imsplitbitseriously tho earthpiper come see me tomorrow morning I would love to have more insight20:53
hub_capok20:53
grapexvipul: I could try to get in place by 11pst20:53
* hub_cap bangs the gavel20:53
hub_capeveryone shut up20:53
* imsplitbit shuts up20:53
hub_capwe need to pick a time20:53
KennethWilkeNOW20:53
earthpiperKennethWilke: +120:53
kevinconwayi'm available at 7:15 CST20:53
vipul11pst?20:53
SlickNik11pst works for me.20:53
* TheRealBill chuckles20:53
kevinconwaylong bus ride to san antonio20:53
vipuldont' ask kevinconway20:53
* grapex begins loudly speaking in tongues20:54
vipulhe comes up with crazy ass times20:54
hub_capok how bout this20:54
imsplitbitI'm ok with 11pst20:54
hub_capill just decide what i want20:54
hub_capand be a dictator20:54
*** KennethWilke has left #openstack-meeting-alt20:54
*** KennethWilke has joined #openstack-meeting-alt20:54
hub_capor we can be big boys and pick a time20:54
kevinconwaymight want to pus hot 11:30 pst so we can get out of lunch and get back to a station20:54
imsplitbit11pst20:54
KennethWilketomorrow anytime 7-4cst20:54
imsplitbitok 113020:54
grapexIt worked for agriculture in the Soviet Union... why not?20:54
hub_cap1130 pst / 130 pst?20:55
grapexSounds good20:55
hub_capdone20:55
imsplitbit1:30 cst20:55
vipulokie20:55
KennethWilkek20:55
kevinconway#agree20:55
SlickNikokay, sounds good20:55
datsun180boh 1:30 CST makes more sense20:55
imsplitbit#agree20:55
robertmyers#agree20:55
imsplitbitlol20:55
datsun180b#agree20:55
* KennethWilke puts on his armor and tight pants20:55
KennethWilkebattle to the death!20:55
imsplitbityeah two times in pst didn't make sense to me either datsun180b20:55
hub_caplol20:55
hub_capok 5 min20:55
imsplitbitKennethWilke: Texas is a "Stand your ground" state20:56
hub_cap#topic open discussion20:56
*** openstack changes topic to "open discussion (Meeting topic: trove)"20:56
imsplitbit:)20:56
hub_capanyoen have anything?20:56
hub_caprelevant20:56
imsplitbitawe20:56
hub_capya20:56
hub_capthis hour is monitored20:56
SlickNikhub_cap: so one thing that came up is the ability to tag / push to pypi20:56
hub_capas in, we need to be big boys20:56
*** jasonb365 has joined #openstack-meeting-alt20:56
kevinconwayi'd like to talk about users20:56
hub_capcuz all of openstack is watching20:56
hub_capkevinconway: do i need to reiterate?20:56
imsplitbitgood point20:56
hub_capcuz i can talk to your mgr20:56
* hub_cap is serious20:56
grapexhub_cap: Man they must be really bored!20:56
hub_capwe can goof off all day long in #openstack-trove but this is a real meeting20:57
imsplitbityeah good point20:57
hub_capSlickNik: yes lets chat20:57
imsplitbitanyone got anything20:57
KennethWilkehmm, i wish i had something else to bring up, but the api is my main concern atm20:57
SlickNikright now it's restricted to trove_ptl (which is a group that has only you)20:57
hub_capSlickNik: had a good point20:57
imsplitbitoh20:57
hub_capso apparently only i can push to pypi?20:57
*** colinmcnamara has quit IRC20:58
hub_capcan we change that to anyoen in core SlickNik?20:58
SlickNikYeah, we can change this is we decide, but I wanted to run it by you guys first.20:58
hub_capyes +120:58
SlickNikYeah, it's a change in the ci-infra scripts20:58
*** colinmcnamara has joined #openstack-meeting-alt20:58
hub_capi trust core20:58
hub_capso i decree20:59
vipul<320:59
hub_capchange it SlickNik20:59
SlickNikgrapex / vipul you guys okay with it?20:59
vipulSlickNik yep20:59
*** jrodom has quit IRC20:59
grapexSlickNik: Sounds good to me.20:59
hub_capok done and done20:59
hub_cap#action SlickNik to change the group for pypi upload20:59
hub_cap:)20:59
SlickNikthx hub_cap, was just about to action myself.21:00
SlickNikThat's all I had21:00
hub_cap#endmeeting21:00
*** openstack changes topic to "OpenStack meetings (alternate)"21:00
openstackMeeting ended Wed Jul 24 21:00:13 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-07-24-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-07-24-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-07-24-20.00.log.html21:00
*** robertmyers has left #openstack-meeting-alt21:00
KennethWilkeermahgerdbehr!21:00
*** KennethWilke has left #openstack-meeting-alt21:00
*** TheRealBill has left #openstack-meeting-alt21:00
grapexPeace21:01
grapexo>21:01
grapex^^ Military Salute21:01
hub_capo721:01
datsun180bo&21:01
datsun180bmotorcycle accident21:01
SlickNikdatsun180b: was just about to ask21:01
grapexdatsun180b: ^^ Beachball riding a motorcycle21:03
*** djohnstone has quit IRC21:03
*** markwash has quit IRC21:03
*** DandyPandy has left #openstack-meeting-alt21:04
*** markwash has joined #openstack-meeting-alt21:07
*** jmcbride has joined #openstack-meeting-alt21:18
*** jergerber has quit IRC21:18
*** zane has quit IRC21:19
*** jmcbride1 has quit IRC21:21
*** pcm_ has quit IRC21:21
*** jmcbride has quit IRC21:23
*** betsy_ has quit IRC21:27
*** jmcbride has joined #openstack-meeting-alt21:31
*** pdmars has quit IRC21:34
*** vipul is now known as vipul-away21:37
*** qwerty_nor has quit IRC21:39
*** qwerty_nor has joined #openstack-meeting-alt21:39
*** vipul-away is now known as vipul21:40
*** megan_w has quit IRC21:42
*** jmcbride1 has joined #openstack-meeting-alt21:42
*** jmcbride has quit IRC21:43
*** kevinconway has quit IRC21:57
*** datsun180b has quit IRC21:59
*** rnirmal has quit IRC22:14
*** lastidiot has quit IRC22:16
*** Riddhi has quit IRC22:16
*** lifeless has quit IRC22:26
*** lifeless has joined #openstack-meeting-alt22:35
*** jcru has quit IRC22:36
*** jmcbride1 has quit IRC22:53
*** jmontemayor has quit IRC22:58
*** colinmcnamara has quit IRC23:06
*** vipul is now known as vipul-away23:12
*** vipul-away is now known as vipul23:14
*** jrodom has joined #openstack-meeting-alt23:16
*** jasonb365 has quit IRC23:17
*** colinmcnamara has joined #openstack-meeting-alt23:20
*** lastidiot has joined #openstack-meeting-alt23:21
*** jrodom has quit IRC23:28
*** colinmcnamara has quit IRC23:49
*** jmcbride has joined #openstack-meeting-alt23:54
*** colinmcnamara has joined #openstack-meeting-alt23:58

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