| *** sacharya has joined #openstack-meeting-alt | 00:27 | |
| *** NehaV has joined #openstack-meeting-alt | 00:31 | |
| *** yidclare has quit IRC | 00:34 | |
| *** NehaV has quit IRC | 00:40 | |
| *** anteaya has quit IRC | 01:11 | |
| *** NehaV has joined #openstack-meeting-alt | 01:18 | |
| *** NehaV has quit IRC | 01:25 | |
| *** NehaV has joined #openstack-meeting-alt | 01:25 | |
| *** jmaron has quit IRC | 01:29 | |
| *** vkmc has quit IRC | 01:41 | |
| *** jmaron has joined #openstack-meeting-alt | 02:00 | |
| *** markwash has joined #openstack-meeting-alt | 02:04 | |
| *** markmcclain has quit IRC | 02:06 | |
| *** jmaron has quit IRC | 02:07 | |
| *** amytron has joined #openstack-meeting-alt | 02:09 | |
| *** tanisdl has quit IRC | 02:19 | |
| *** NehaV has quit IRC | 02:45 | |
| *** markwash has quit IRC | 02:46 | |
| *** markwash has joined #openstack-meeting-alt | 02:53 | |
| *** jmaron has joined #openstack-meeting-alt | 03:04 | |
| *** msisk has joined #openstack-meeting-alt | 03:10 | |
| *** jmaron has quit IRC | 03:12 | |
| *** bdpayne has quit IRC | 03:17 | |
| *** mberwanger has joined #openstack-meeting-alt | 03:34 | |
| *** NehaV has joined #openstack-meeting-alt | 03:41 | |
| *** NehaV1 has joined #openstack-meeting-alt | 03:41 | |
| *** NehaV has quit IRC | 03:45 | |
| *** NehaV1 has quit IRC | 03:49 | |
| *** markwash has quit IRC | 03:50 | |
| *** markwash has joined #openstack-meeting-alt | 03:57 | |
| *** sacharya has quit IRC | 04:00 | |
| *** msisk has quit IRC | 04:09 | |
| *** jmaron has joined #openstack-meeting-alt | 04:09 | |
| *** markwash has quit IRC | 04:12 | |
| *** jmaron has quit IRC | 04:14 | |
| *** akuznetsov has joined #openstack-meeting-alt | 04:16 | |
| *** mberwanger has quit IRC | 04:34 | |
| *** NehaV has joined #openstack-meeting-alt | 04:35 | |
| *** mberwanger has joined #openstack-meeting-alt | 04:38 | |
| *** NehaV has quit IRC | 04:43 | |
| *** markwash has joined #openstack-meeting-alt | 04:51 | |
| *** mberwanger has quit IRC | 05:06 | |
| *** markwash has quit IRC | 05:07 | |
| *** enikanorov-w has quit IRC | 05:08 | |
| *** enikanorov-w has joined #openstack-meeting-alt | 05:10 | |
| *** akuznetsov has quit IRC | 05:28 | |
| *** NehaV has joined #openstack-meeting-alt | 05:30 | |
| *** NehaV has quit IRC | 05:39 | |
| *** markwash has joined #openstack-meeting-alt | 05:43 | |
| *** amytron has quit IRC | 05:55 | |
| *** markwash has quit IRC | 06:03 | |
| *** jmaron has joined #openstack-meeting-alt | 06:10 | |
| *** jmaron has joined #openstack-meeting-alt | 06:10 | |
| *** jmaron has quit IRC | 06:15 | |
| *** dmakogon_ has joined #openstack-meeting-alt | 06:24 | |
| *** NehaV has joined #openstack-meeting-alt | 06:25 | |
| *** markwash has joined #openstack-meeting-alt | 06:29 | |
| *** NehaV has quit IRC | 06:32 | |
| *** markwash has quit IRC | 06:44 | |
| *** ruhe has joined #openstack-meeting-alt | 06:52 | |
| *** jmaron has joined #openstack-meeting-alt | 07:11 | |
| *** jmaron has quit IRC | 07:15 | |
| *** markwash has joined #openstack-meeting-alt | 07:27 | |
| *** dmakogon_ has quit IRC | 07:28 | |
| *** dmakogon_ has joined #openstack-meeting-alt | 07:37 | |
| *** markwash has quit IRC | 07:39 | |
| *** boris-42 has joined #openstack-meeting-alt | 07:42 | |
| *** benl has joined #openstack-meeting-alt | 07:51 | |
| *** aignatov has quit IRC | 08:00 | |
| *** aignatov has joined #openstack-meeting-alt | 08:01 | |
| *** dmakogon_ has quit IRC | 08:11 | |
| *** ameade has quit IRC | 08:11 | |
| *** clarkb has quit IRC | 08:11 | |
| *** jeblair has quit IRC | 08:11 | |
| *** ameade has joined #openstack-meeting-alt | 08:12 | |
| *** jeblair has joined #openstack-meeting-alt | 08:12 | |
| *** clarkb has joined #openstack-meeting-alt | 08:12 | |
| *** jmaron has joined #openstack-meeting-alt | 08:12 | |
| *** jmaron has quit IRC | 08:17 | |
| *** markwash has joined #openstack-meeting-alt | 08:22 | |
| *** markwash has quit IRC | 08:34 | |
| *** markwash has joined #openstack-meeting-alt | 08:48 | |
| *** dmitryme has joined #openstack-meeting-alt | 08:59 | |
| *** markwash has quit IRC | 09:09 | |
| *** akuznetsov has joined #openstack-meeting-alt | 09:11 | |
| *** jmaron has joined #openstack-meeting-alt | 09:12 | |
| *** ruhe has quit IRC | 09:16 | |
| *** jmaron has quit IRC | 09:17 | |
| *** dkoryavov has joined #openstack-meeting-alt | 09:18 | |
| *** ruhe has joined #openstack-meeting-alt | 09:18 | |
| *** ruhe has quit IRC | 09:37 | |
| *** akuznetsov has quit IRC | 09:37 | |
| *** akuznetsov has joined #openstack-meeting-alt | 09:40 | |
| *** akuznetsov has quit IRC | 09:43 | |
| *** dmitryme has quit IRC | 09:45 | |
| *** isviridov has quit IRC | 09:52 | |
| *** pcm_ has joined #openstack-meeting-alt | 10:04 | |
| *** pcm_ has quit IRC | 10:06 | |
| *** pcm_ has joined #openstack-meeting-alt | 10:06 | |
| *** boris-42 has quit IRC | 10:09 | |
| *** dmitryme has joined #openstack-meeting-alt | 10:09 | |
| *** jmaron has joined #openstack-meeting-alt | 10:12 | |
| *** akuznetsov has joined #openstack-meeting-alt | 10:14 | |
| *** ruhe has joined #openstack-meeting-alt | 10:16 | |
| *** jmaron has quit IRC | 10:17 | |
| *** benl has quit IRC | 10:22 | |
| *** isviridov has joined #openstack-meeting-alt | 10:24 | |
| *** dmitryme has left #openstack-meeting-alt | 10:38 | |
| *** markmcclain has joined #openstack-meeting-alt | 10:39 | |
| *** sergmelikyan has joined #openstack-meeting-alt | 10:48 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 10:50 | |
| *** dkoryavov has quit IRC | 10:54 | |
| *** SergeyLukjanov has quit IRC | 10:54 | |
| *** ruhe has quit IRC | 10:59 | |
| *** ruhe has joined #openstack-meeting-alt | 11:01 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 11:03 | |
| *** dina_belova has joined #openstack-meeting-alt | 11:05 | |
| *** jmaron has joined #openstack-meeting-alt | 11:13 | |
| *** jmaron has quit IRC | 11:18 | |
| *** boris-42 has joined #openstack-meeting-alt | 11:19 | |
| *** benl has joined #openstack-meeting-alt | 11:33 | |
| *** benl has quit IRC | 11:37 | |
| *** dosaboy_ is now known as dosaboy_afk | 11:43 | |
| *** dina_belova has quit IRC | 11:45 | |
| *** ruhe has quit IRC | 12:00 | |
| *** SergeyLukjanov has quit IRC | 12:11 | |
| *** pdmars has joined #openstack-meeting-alt | 12:12 | |
| *** jmaron has joined #openstack-meeting-alt | 12:14 | |
| *** jmaron has quit IRC | 12:18 | |
| *** jmaron has joined #openstack-meeting-alt | 12:24 | |
| *** akuznetsov has quit IRC | 12:31 | |
| *** _crobertsrh is now known as crobertsrh | 12:32 | |
| *** akuznetsov has joined #openstack-meeting-alt | 12:36 | |
| *** dosaboy_afk has quit IRC | 12:55 | |
| *** akuznetsov has quit IRC | 13:01 | |
| *** ruhe has joined #openstack-meeting-alt | 13:04 | |
| *** dina_belova has joined #openstack-meeting-alt | 13:11 | |
| *** dina_belova has quit IRC | 13:12 | |
| *** dina_belova has joined #openstack-meeting-alt | 13:12 | |
| *** dina_belova has quit IRC | 13:17 | |
| *** akuznetsov has joined #openstack-meeting-alt | 13:20 | |
| *** eankutse has joined #openstack-meeting-alt | 13:22 | |
| *** eankutse has joined #openstack-meeting-alt | 13:24 | |
| *** eankutse1 has joined #openstack-meeting-alt | 13:25 | |
| *** anteaya has joined #openstack-meeting-alt | 13:26 | |
| *** eankutse has quit IRC | 13:28 | |
| *** NehaV has joined #openstack-meeting-alt | 13:37 | |
| *** amytron has joined #openstack-meeting-alt | 13:40 | |
| *** eankutse1 has quit IRC | 13:42 | |
| *** NehaV1 has joined #openstack-meeting-alt | 13:45 | |
| *** isviridov is now known as isviridov_ | 13:45 | |
| *** NehaV has quit IRC | 13:46 | |
| *** ogelbukh has joined #openstack-meeting-alt | 13:54 | |
| *** sirmax has quit IRC | 13:54 | |
| *** sirmax has joined #openstack-meeting-alt | 13:55 | |
| *** eankutse has joined #openstack-meeting-alt | 14:06 | |
| *** isviridov_ has left #openstack-meeting-alt | 14:10 | |
| *** dina_belova has joined #openstack-meeting-alt | 14:13 | |
| *** sacharya has joined #openstack-meeting-alt | 14:15 | |
| *** dina_belova has quit IRC | 14:17 | |
| *** eankutse has quit IRC | 14:17 | |
| *** ruhe has quit IRC | 14:17 | |
| *** eankutse has joined #openstack-meeting-alt | 14:18 | |
| *** eankutse has quit IRC | 14:21 | |
| *** Riddhi has joined #openstack-meeting-alt | 14:25 | |
| *** tanisdl has joined #openstack-meeting-alt | 14:28 | |
| *** sacharya has quit IRC | 14:32 | |
| *** Riddhi has quit IRC | 14:33 | |
| *** akuznetsov has quit IRC | 14:35 | |
| *** sergmelikyan has quit IRC | 14:45 | |
| *** akuznetsov has joined #openstack-meeting-alt | 14:50 | |
| *** eankutse has joined #openstack-meeting-alt | 14:52 | |
| *** rnirmal has joined #openstack-meeting-alt | 14:53 | |
| *** eankutse has quit IRC | 14:56 | |
| *** eankutse has joined #openstack-meeting-alt | 14:56 | |
| *** ruhe has joined #openstack-meeting-alt | 14:57 | |
| *** akuznetsov has quit IRC | 14:58 | |
| *** akuznetsov has joined #openstack-meeting-alt | 14:59 | |
| *** eankutse has quit IRC | 14:59 | |
| *** esker has joined #openstack-meeting-alt | 15:00 | |
| *** eankutse has joined #openstack-meeting-alt | 15:01 | |
| *** NehaV1 has quit IRC | 15:03 | |
| *** jmontemayor has joined #openstack-meeting-alt | 15:04 | |
| *** sacharya has joined #openstack-meeting-alt | 15:04 | |
| *** rnirmal has quit IRC | 15:10 | |
| *** dina_belova has joined #openstack-meeting-alt | 15:13 | |
| *** NehaV has joined #openstack-meeting-alt | 15:17 | |
| *** eankutse1 has joined #openstack-meeting-alt | 15:18 | |
| *** dina_belova has quit IRC | 15:18 | |
| *** eankutse1 has quit IRC | 15:19 | |
| *** eankutse1 has joined #openstack-meeting-alt | 15:20 | |
| *** eankutse has quit IRC | 15:20 | |
| *** NehaV has quit IRC | 15:20 | |
| *** NehaV has joined #openstack-meeting-alt | 15:21 | |
| *** esker has quit IRC | 15:35 | |
| *** yidclare has joined #openstack-meeting-alt | 15:47 | |
| *** NehaV1 has joined #openstack-meeting-alt | 15:48 | |
| *** akuznetsov has quit IRC | 15:49 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 15:49 | |
| *** NehaV has quit IRC | 15:51 | |
| *** msisk has joined #openstack-meeting-alt | 15:53 | |
| *** dina_belova has joined #openstack-meeting-alt | 15:54 | |
| *** pcm_ has quit IRC | 15:56 | |
| *** boris-42 has quit IRC | 15:57 | |
| *** ruhe has quit IRC | 16:05 | |
| *** vinodmr has joined #openstack-meeting-alt | 16:09 | |
| *** SergeyLukjanov has quit IRC | 16:16 | |
| *** rnirmal has joined #openstack-meeting-alt | 16:18 | |
| *** ruhe has joined #openstack-meeting-alt | 16:21 | |
| *** vinodmr has quit IRC | 16:25 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 16:28 | |
| *** jmontemayor has quit IRC | 16:30 | |
| *** dina_belova has quit IRC | 16:32 | |
| *** betsy has joined #openstack-meeting-alt | 16:34 | |
| *** dina_belova has joined #openstack-meeting-alt | 16:37 | |
| *** akuznetsov has joined #openstack-meeting-alt | 16:38 | |
| *** mugsie has joined #openstack-meeting-alt | 16:53 | |
| *** kiall has joined #openstack-meeting-alt | 16:56 | |
| *** vinodmr has joined #openstack-meeting-alt | 16:59 | |
| *** tsimmons has joined #openstack-meeting-alt | 16:59 | |
| kiall | #startmeeting designate | 17:00 |
|---|---|---|
| openstack | Meeting started Wed Aug 21 17:00:10 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
| *** openstack changes topic to " (Meeting topic: designate)" | 17:00 | |
| openstack | The meeting name has been set to 'designate' | 17:00 |
| kiall | Heya - Who's about? | 17:00 |
| mugsie | o/ | 17:00 |
| tsimmons | Howdy from Texas. | 17:00 |
| betsy | o/ | 17:00 |
| *** NehaV1 has quit IRC | 17:01 | |
| vinodmr | vinod here | 17:01 |
| *** NehaV has joined #openstack-meeting-alt | 17:01 | |
| kiall | simonmcc / Capttofu ? | 17:01 |
| eankutse1 | Emmanuel here | 17:01 |
| simonmcc | o/ | 17:01 |
| kiall | Okay .. That'll do :) | 17:02 |
| *** pdmars has quit IRC | 17:02 | |
| kiall | #topic API v2.0 Discussion/Feedback | 17:02 |
| *** openstack changes topic to "API v2.0 Discussion/Feedback (Meeting topic: designate)" | 17:02 | |
| *** CaptTofu has joined #openstack-meeting-alt | 17:02 | |
| * CaptTofu is present | 17:02 | |
| kiall | So - I've got review up thats far from production ready, but it getting to large to continue adding more to :) | 17:02 |
| kiall | https://review.openstack.org/#/c/42859/ | 17:02 |
| kiall | This is a start on the /zones endpoint, and lots of the "bits" that make it work | 17:03 |
| kiall | "Happy Path" CRUD+List operations are working nicely, and have tests etc | 17:03 |
| kiall | So - Anyone wanting to start to play with it, please do :) | 17:03 |
| kiall | Anyone happen to look it over and have any comments? | 17:04 |
| betsy | okay | 17:04 |
| tsimmons | Cool, we'll check it out. | 17:04 |
| *** ruhe has quit IRC | 17:04 | |
| eankutse1 | Not yet. Will do | 17:04 |
| betsy | I've looked at it very briefly. I'll look at it more in depth and start playing with it | 17:04 |
| kiall | Cool :) I'm wanting to get it merged sooner rather than later - It's just too "big" already and will be difficult to review as more iterations go on top | 17:05 |
| simonmcc | I've looked & added some comments, mostly around documenting some bits | 17:05 |
| kiall | Okay .. So.. | 17:06 |
| kiall | We updated the API v2 spec to replace the "old" pagination with the "new" | 17:06 |
| kiall | Any more comments on that before someone starts implementing it? :) | 17:06 |
| eankutse1 | not from me | 17:07 |
| tsimmons | Nope, I think it's good. | 17:07 |
| betsy | +1 | 17:07 |
| CaptTofu | I agree | 17:07 |
| kiall | Cool - Okay :) | 17:07 |
| kiall | Anything from anyone else on APIv2 before moving over to Blueprints and Bugs? :) | 17:08 |
| simonmcc | nothing from me | 17:09 |
| *** SergeyLukjanov has quit IRC | 17:09 | |
| tsimmons | or me | 17:09 |
| kiall | #topic Blueprints and Bugs | 17:09 |
| *** openstack changes topic to "Blueprints and Bugs (Meeting topic: designate)" | 17:09 | |
| mugsie | nope | 17:09 |
| *** dina_belova has quit IRC | 17:10 | |
| kiall | We filed/cleaned yup a couple of blueprints/bugs this morning.. With an eye towards making sure there are pieces for people to grab and work on .. There's obviously lots more to add .. but it's a start | 17:10 |
| kiall | The blueprints list https://blueprints.launchpad.net/designate | 17:10 |
| eankutse1 | Thanks Kiall for filing bugs and blueprints | 17:10 |
| kiall | has a bunch of generally useful features - most of which should be easy enough to pick up and work on :) | 17:10 |
| CaptTofu | bite-sized tasks++ | 17:11 |
| kiall | Some examples would be domain-import-export (from traditional bind/rfc zone files) | 17:11 |
| betsy | kiall: so is that one for v1 or v2? | 17:12 |
| kiall | caching-backend - which needs to be renamed to caching-storage ;) a small caching layer been the DB and DB Users .. | 17:12 |
| betsy | I'm assuming these are all on v1. Is that right? | 17:12 |
| kiall | We do lots of "GET where ID = 1234" that could easily not need to hit the DB | 17:12 |
| *** dina_belova has joined #openstack-meeting-alt | 17:12 | |
| kiall | betsy: generally speaking, we should stop adding to v1 .. But .. v2 isn't ready, so there's no harm ;) | 17:13 |
| betsy | Yeah. That's where I was a little confused | 17:13 |
| kiall | Anyway - | 17:13 |
| kiall | ugh | 17:13 |
| kiall | tried to delete that ;) | 17:13 |
| kiall | There's also the bind9 and agent stuff we talked about during the week - they aren't filed | 17:13 |
| simonmcc | caching-storage - sounds a little premature? or something we should leverage in SQLA? | 17:13 |
| kiall | But are generally in need of some love :) | 17:14 |
| tsimmons | I was planning on filing a blueprint for that. | 17:14 |
| kiall | simonmcc: possibly :) but it's still generally useful :) | 17:14 |
| *** dina_belova has quit IRC | 17:15 | |
| kiall | tsimmons: please do :) Anything anyone see's that they think is missing etc.. file one :) | 17:15 |
| kiall | Anyway - The point of all this is :) myself / simonmcc / CaptTofu are figuring out what bugs/blueprints are missing, and are filing as we find them.. | 17:16 |
| eankutse1 | Thanks for doing that | 17:16 |
| *** lifeless has quit IRC | 17:16 | |
| kiall | No problem.. It's a change for us .. we're used to filing tickets in JIRA! | 17:17 |
| *** lifeless has joined #openstack-meeting-alt | 17:17 | |
| betsy | I know. We have an internal tool, too | 17:17 |
| kiall | Being split between two is awful :) | 17:17 |
| betsy | Trying to figure out the best way to tie them together | 17:17 |
| betsy | Exactly! | 17:17 |
| CaptTofu | perhaps just internal tickets for proprietary issues | 17:18 |
| kiall | Anyway - Hopefully there's enough in the lists to last a few weeks ;) | 17:18 |
| CaptTofu | if something designate-specific, public | 17:18 |
| kiall | CaptTofu: yea, ideally *everything* designate related goes in LaunchPad .. :) | 17:19 |
| kiall | There's also a second bug list for the client.. https://bugs.launchpad.net/python-designateclient/+bugs | 17:19 |
| kiall | Although .. I know there are 50 or so bugs in the client that aren't filed. We'll port them from JIRA :) | 17:19 |
| kiall | So, that's all we has listed on the agenda for today.. Nice and short! | 17:20 |
| kiall | #topic Open discussion | 17:20 |
| *** openstack changes topic to "Open discussion (Meeting topic: designate)" | 17:20 | |
| kiall | Anything else from anyone? | 17:20 |
| CaptTofu | yes | 17:21 |
| CaptTofu | I'm curious how other organizations using Designate are doing with their implementations | 17:21 |
| CaptTofu | if what's worth discussing | 17:21 |
| CaptTofu | if not, glad to take it offline | 17:21 |
| eankutse1 | We are Bind9 based | 17:21 |
| *** mordred has quit IRC | 17:22 | |
| eankutse1 | so we are still working through some issues | 17:22 |
| eankutse1 | to get a Bind9 installation | 17:22 |
| eankutse1 | and then think of a migration plan | 17:22 |
| CaptTofu | eankutse1: do you use any backing databases? | 17:22 |
| kiall | eankutse1: I'd bet :) the bind9 support has lagged, and defiantly needs work | 17:22 |
| eankutse1 | yes we do | 17:22 |
| *** dmakogon_ has joined #openstack-meeting-alt | 17:22 | |
| CaptTofu | I updated mysqlbind recently and it works pretty well. You only have to re-write your zone conf file. I can discuss offline if you are interested. | 17:23 |
| CaptTofu | very easy to use. | 17:23 |
| tsimmons | Right now we're using a PowerDNS backend to get a small implementation up and running with a few environments so we can get an idea of what our eventual implementation will look like. | 17:23 |
| eankutse1 | CapTofu: that would be helpful | 17:23 |
| eankutse1 | We will get in touch with you - maybe tsimmons | 17:24 |
| tsimmons | For sure. | 17:25 |
| kiall | CaptTofu: maybe the best thing would be to add to the documentation? That way it's totally public etc :) | 17:25 |
| eankutse1 | Even better | 17:25 |
| *** akuznetsov has quit IRC | 17:25 | |
| kiall | We should probably add a docs sections for each backend covering the backend specific stuff | 17:26 |
| tsimmons | It would be helpful to have more specific instructions on setting up each one, yeah. | 17:26 |
| *** ruhe has joined #openstack-meeting-alt | 17:26 | |
| simonmcc | +1 on that | 17:26 |
| *** markwash has joined #openstack-meeting-alt | 17:27 | |
| kiall | #action New doc section to be added for backend specific, starting with CaptTofu's mysqlbind docs.. | 17:27 |
| kiall | So - Are there any others areas you, as "new guys", have found lacking? | 17:28 |
| kiall | doc areas* | 17:28 |
| *** akuznetsov has joined #openstack-meeting-alt | 17:28 | |
| CaptTofu | :) | 17:29 |
| CaptTofu | @kiall agreed | 17:29 |
| CaptTofu | oops, not hipchat | 17:29 |
| kiall | hah :D | 17:29 |
| betsy | kiall: I haven't noticed any | 17:29 |
| kiall | betsy: that sounds promising :) | 17:29 |
| tsimmons | There could be more instruction on backend setup, like we've said here. | 17:30 |
| kiall | #action Add doc section on plain bind9 backend, including agent limitations.. | 17:30 |
| *** mordred has joined #openstack-meeting-alt | 17:30 | |
| kiall | #action Get a blueprint together discussing the future of the agent, and how it will interact with API v2's "server pools" | 17:31 |
| kiall | ^ that one is likely to need input from everyone, HPs implementation is very different than I expect may others would be.. So getting that right for everyone is a meeting to itself | 17:31 |
| kiall | many others would be* | 17:32 |
| eankutse1 | I agree | 17:32 |
| kiall | Okay :) Anything else? | 17:32 |
| tsimmons | #agree the documentation for agent could be fleshed out some more after that ^ | 17:32 |
| betsy | kiall: True | 17:32 |
| tsimmons | Could we get some clarification on the designate client? Just a quick background on it? | 17:33 |
| eankutse1 | +1 | 17:33 |
| betsy | Looks like it hasn't been worked on since folsom? | 17:34 |
| simonmcc | it's a python binding & cli client for the rest api | 17:34 |
| kiall | betsy: "Happy Path" works perfectly :) | 17:34 |
| kiall | If it runs into an issue, it's not very user friendly | 17:34 |
| betsy | kiall: :) | 17:34 |
| kiall | I use it daily.. More than I use the API by itself | 17:34 |
| simonmcc | FM there are parts of the API not covered by it, but all the core stuff is there | 17:35 |
| eankutse1 | Cool | 17:35 |
| betsy | cli clients are always handy | 17:35 |
| kiall | Anyway - As simonmcc said, the tradition in openstack is to include both Python API bindings and a CLI that makes use of those bindings in a single package | 17:35 |
| eankutse1 | Sounds like there is some work to be done there as well | 17:35 |
| betsy | We could probably use some documentation around that, too | 17:35 |
| simonmcc | it'll need the v2 api added to it for a start :-) | 17:36 |
| betsy | Unless I've just missed that | 17:36 |
| kiall | eankutse1: I think the error handling is the main area .. and, when v2 comes out, we can make it MUCH more user friendly | 17:36 |
| eankutse1 | ok | 17:36 |
| simonmcc | #action add usage example for python-designate cli | 17:36 |
| kiall | Today, it's quite "awkward" to use | 17:37 |
| kiall | e.g | 17:37 |
| kiall | $ designate record-delete b1bbcb29-d2f7-4ec4-82e3-0bbb32230977 6d3bf479-8a93-47ae-8c65-3dff8dba1b0d | 17:37 |
| kiall | first UUID is the domain, second is the Record | 17:37 |
| kiall | The v2 api will make looking up domains etc by name doable | 17:37 |
| kiall | (and actually works in the /zones review I mentioned earlier) | 17:38 |
| *** venkatesh has joined #openstack-meeting-alt | 17:38 | |
| kiall | Anyway, we have some docs on our internal wiki that explain how to use the CLI. We'll port those, and add docs on the python bindings aswell | 17:39 |
| eankutse1 | Great! | 17:39 |
| betsy | Awesome | 17:39 |
| kiall | #action Document designateclient python bindings.. | 17:39 |
| kiall | Starting the cycle again :D Anything else? | 17:40 |
| CaptTofu | not from me. | 17:40 |
| *** esker has joined #openstack-meeting-alt | 17:40 | |
| simonmcc | should we pypi the client? | 17:41 |
| kiall | I have 1 last one :) | 17:41 |
| kiall | simonmcc: yea, all we had to do to make that happen is tag to repo | 17:41 |
| kiall | Jenkins will build the package based on the and upload it to pypi | 17:41 |
| *** akuznetsov has quit IRC | 17:41 | |
| simonmcc | ok, doh, we've talked about that before :-) | 17:41 |
| kiall | :) | 17:41 |
| simonmcc | so, what's your "one last thing" ? | 17:42 |
| CaptTofu | nifty! | 17:42 |
| kiall | What would you change about these meetings? | 17:42 |
| CaptTofu | more people. | 17:42 |
| CaptTofu | just so we have more project involvement | 17:42 |
| CaptTofu | but that's an external issue | 17:42 |
| betsy | CaptTofu: we're trying :) | 17:42 |
| tsimmons | Make them in person :D | 17:43 |
| *** rnirmal has quit IRC | 17:43 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 17:43 | |
| betsy | Road trip to Ireland!! | 17:43 |
| kiall | I want to make sure time is well spent by everyone .. If we're not covering stuff people are interested in talking about .. or any other issues. Lets fix it :) | 17:43 |
| eankutse1 | I think we are doing well so far | 17:44 |
| betsy | +1 | 17:44 |
| eankutse1 | useful | 17:44 |
| eankutse1 | in the future | 17:44 |
| eankutse1 | we might be able to | 17:44 |
| kiall | Cool - For anyone who hasn't sat in on some of the other OpenStack meetings that go on .. Do.. :) | 17:44 |
| eankutse1 | publish | 17:44 |
| eankutse1 | agenda ahead of time | 17:44 |
| kiall | I knew that was going to come up ;) | 17:45 |
| eankutse1 | :-) | 17:45 |
| kiall | The agena is on https://wiki.openstack.org/wiki/Meetings/Designate | 17:45 |
| kiall | But .. It was only updated this morning ;) | 17:45 |
| kiall | i.e. no good. | 17:45 |
| eankutse1 | Cool. Thanks for letting me know | 17:45 |
| kiall | Also - everyone can edit that page, and add items.. | 17:46 |
| betsy | Okay | 17:46 |
| kiall | Doesn't matter what it is! Maybe you want to dicuss how to implement some feature, or general project direction, or .. those are all things you can just add | 17:47 |
| tsimmons | Is there/should there be a designate mailing list where we could send out the agenda/other info to people, perhaps get more people involved? | 17:47 |
| kiall | #action Update agenda as soon as items are thought of! | 17:47 |
| kiall | tsimmons: generally, the other openstack projects share the openstack-dev list, and publish meeting stuff in advance to there.. We probably should too :) | 17:48 |
| kiall | #action Start publishing meeting schedules/agenda to the openstack-dev list. | 17:48 |
| tsimmons | I see, that should help drive some traffic to the project/meetings. | 17:48 |
| mugsie | do we need to register as a topic on that list? | 17:49 |
| kiall | I'm not sure there should be a designate specific dev list, there used to 1 for each project.. and they go removed :) | 17:49 |
| kiall | mugsie: no, just prefix designate stuff with "[Designate] My Subject Here" | 17:49 |
| simonmcc | the problem with the -dev list is that it's getting to be hight traffic ;/ | 17:49 |
| kiall | simonmcc: yea, that's the idea behind the prefixes :) | 17:50 |
| kiall | you can move [Nova] to somewhere else, but let [Glance] and [Designate though.. | 17:50 |
| simonmcc | kiall :-0 | 17:50 |
| kiall | (using your email client's tiles) | 17:50 |
| kiall | rules* | 17:50 |
| mugsie | kiall: there is a filter option in the mailing list software now | 17:51 |
| kiall | Oh, really? News to me | 17:51 |
| mugsie | that has a load of projects as "topics" | 17:51 |
| kiall | #action mugsie to look into if we need to register as a "topic" :) | 17:51 |
| kiall | Starting the cycle again :D Anything else? | 17:52 |
| eankutse1 | Not from me | 17:52 |
| simonmcc | not from me | 17:53 |
| mugsie | nor me | 17:53 |
| kiall | Okay I guess not, thanks everyone :) I think there's plenty of useful feedback buried in the logs! | 17:53 |
| CaptTofu | thanks! | 17:53 |
| simonmcc | cheers! | 17:53 |
| eankutse1 | Bye | 17:53 |
| kiall | No wonder my IRC is so laggy: 5 packets transmitted, 0 received, 100% packet loss, time 5999ms | 17:53 |
| kiall | 100% -_- | 17:53 |
| kiall | #endmeeting | 17:54 |
| *** openstack changes topic to "OpenStack meetings (alternate)" | 17:54 | |
| openstack | Meeting ended Wed Aug 21 17:54:01 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:54 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-08-21-17.00.html | 17:54 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-08-21-17.00.txt | 17:54 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-08-21-17.00.log.html | 17:54 |
| *** arborism has joined #openstack-meeting-alt | 17:54 | |
| tsimmons | See ya, thanks guys. | 17:54 |
| *** vinodmr has left #openstack-meeting-alt | 17:54 | |
| *** dina_belova has joined #openstack-meeting-alt | 17:54 | |
| *** nicole has joined #openstack-meeting-alt | 17:57 | |
| *** mugsie has left #openstack-meeting-alt | 17:57 | |
| *** nicole is now known as Guest47485 | 17:57 | |
| *** Guest47485 has left #openstack-meeting-alt | 17:57 | |
| *** Guest47485 has joined #openstack-meeting-alt | 17:58 | |
| *** ruhe has quit IRC | 17:58 | |
| *** vkmc has joined #openstack-meeting-alt | 18:02 | |
| *** Guest47485 has left #openstack-meeting-alt | 18:04 | |
| *** rnirmal has joined #openstack-meeting-alt | 18:08 | |
| *** yogesh has joined #openstack-meeting-alt | 18:17 | |
| *** boris-42 has joined #openstack-meeting-alt | 18:19 | |
| *** yogesh has quit IRC | 18:19 | |
| *** pdmars has joined #openstack-meeting-alt | 18:23 | |
| *** grapex has joined #openstack-meeting-alt | 18:24 | |
| *** venkatesh has quit IRC | 18:26 | |
| *** eankutse1 has quit IRC | 18:27 | |
| *** yogesh has joined #openstack-meeting-alt | 18:35 | |
| *** tsimmons has quit IRC | 18:36 | |
| *** tsimmons has joined #openstack-meeting-alt | 18:42 | |
| *** yogesh has quit IRC | 18:50 | |
| *** Riddhi has joined #openstack-meeting-alt | 18:50 | |
| *** yogesh has joined #openstack-meeting-alt | 18:51 | |
| *** eankutse has joined #openstack-meeting-alt | 18:52 | |
| *** tsimmons has quit IRC | 18:54 | |
| *** eankutse has quit IRC | 18:56 | |
| *** eankutse has joined #openstack-meeting-alt | 18:57 | |
| *** akuznetsov has joined #openstack-meeting-alt | 18:57 | |
| *** tsimmons has joined #openstack-meeting-alt | 18:57 | |
| *** yogesh has quit IRC | 18:58 | |
| *** sarob has joined #openstack-meeting-alt | 18:59 | |
| *** msisk has quit IRC | 19:16 | |
| *** esker has quit IRC | 19:20 | |
| *** sarob has quit IRC | 19:21 | |
| *** sarob has joined #openstack-meeting-alt | 19:21 | |
| *** ashestakov has joined #openstack-meeting-alt | 19:25 | |
| *** sarob has quit IRC | 19:25 | |
| *** vipul is now known as vipul-away | 19:36 | |
| *** vipul-away is now known as vipul | 19:36 | |
| *** boris-42 has quit IRC | 19:37 | |
| *** jmontemayor has joined #openstack-meeting-alt | 19:42 | |
| *** yogesh has joined #openstack-meeting-alt | 19:47 | |
| *** djohnstone has quit IRC | 19:48 | |
| *** akuznetsov has quit IRC | 19:49 | |
| *** vipul is now known as vipul-away | 19:51 | |
| *** esp has joined #openstack-meeting-alt | 19:53 | |
| *** vipul-away is now known as vipul | 19:53 | |
| *** yogesh has quit IRC | 19:54 | |
| *** yogesh has joined #openstack-meeting-alt | 19:55 | |
| *** esker has joined #openstack-meeting-alt | 19:56 | |
| *** KennethWilke has joined #openstack-meeting-alt | 19:56 | |
| *** cweid has joined #openstack-meeting-alt | 19:57 | |
| *** KennethWilke has quit IRC | 19:57 | |
| *** imsplitbit has joined #openstack-meeting-alt | 19:58 | |
| *** vinodmr has joined #openstack-meeting-alt | 19:59 | |
| *** vinodmr has quit IRC | 19:59 | |
| *** KennethWilke has joined #openstack-meeting-alt | 19:59 | |
| vipul | #startmeeting trove | 20:00 |
| openstack | Meeting started Wed Aug 21 20:00:07 2013 UTC and is due to finish in 60 minutes. The chair is vipul. Information about MeetBot at http://wiki.debian.org/MeetBot. | 20:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 20:00 |
| *** openstack changes topic to " (Meeting topic: trove)" | 20:00 | |
| openstack | The meeting name has been set to 'trove' | 20:00 |
| KennethWilke | howdy | 20:00 |
| *** jcru has joined #openstack-meeting-alt | 20:00 | |
| imsplitbit | o/ | 20:00 |
| vipul | o/ | 20:00 |
| dmakogon_ | hi 2 all | 20:00 |
| amytron | o/ | 20:00 |
| *** saurabhs has joined #openstack-meeting-alt | 20:00 | |
| dmakogon_ | o/ | 20:00 |
| *** robertmyers has joined #openstack-meeting-alt | 20:00 | |
| robertmyers | o/ | 20:00 |
| esp | o/ | 20:00 |
| *** SlickNik has joined #openstack-meeting-alt | 20:00 | |
| vipul | #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting | 20:00 |
| pdmars | o/ | 20:01 |
| kevinconway | \-\0/-/ | 20:01 |
| SlickNik | o/ | 20:01 |
| vipul | #topic action items | 20:01 |
| *** openstack changes topic to "action items (Meeting topic: trove)" | 20:01 | |
| cp16net | o^/ | 20:01 |
| cweid | o/ | 20:01 |
| vipul | imsplitbit: first one is you | 20:01 |
| *** datsun180b has joined #openstack-meeting-alt | 20:01 | |
| vipul | imsplitbit to move his clustering reviews to a feature branch | 20:01 |
| grapex | o/ | 20:02 |
| imsplitbit | yeah I've got the clustertype stuff out there for review | 20:02 |
| vipul | i assume this was for the cluster api itself maybe | 20:02 |
| vipul | ? | 20:02 |
| imsplitbit | I've created a feature branch and I'm moving my current work for cluster api into it | 20:02 |
| *** tsimmons has joined #openstack-meeting-alt | 20:02 | |
| datsun180b | o7 | 20:02 |
| imsplitbit | yes | 20:02 |
| vipul | cool | 20:02 |
| imsplitbit | I haven't pushed it up yet | 20:02 |
| dmakogon_ | can it be extended ? | 20:02 |
| imsplitbit | I would love some feedback on the clustertype | 20:02 |
| imsplitbit | both for trove and trove client | 20:02 |
| vipul | #action imsplitbit to push up cluster api to feature branch | 20:02 |
| *** vinodmr has joined #openstack-meeting-alt | 20:02 | |
| vipul | imsplitbit: Yea i've been meaning to find some time | 20:03 |
| vipul | i'll look this week. | 20:03 |
| SlickNik | Same here | 20:03 |
| vipul | i did browse over it though... | 20:03 |
| imsplitbit | kk thx! | 20:03 |
| vipul | next item was hub_cap.. | 20:03 |
| vipul | i guess we skip him | 20:03 |
| vipul | #action hub_cap to find out what happens w/ feature based reviews that land after FF | 20:03 |
| vipul | next.. SlickNick | 20:03 |
| SlickNik | Yeah, I made a couple of changes to the devstack review. | 20:04 |
| SlickNik | But I have to yet make the default role change | 20:04 |
| SlickNik | So I'm going to action this one again for myself. | 20:04 |
| SlickNik | #action SlickNik update devstack review to add role to default devstack users. | 20:04 |
| *** key2 has joined #openstack-meeting-alt | 20:04 | |
| vipul | cool.. | 20:04 |
| vipul | thanks! | 20:04 |
| vipul | and that is all for actions | 20:04 |
| *** yogesh has quit IRC | 20:04 | |
| arborism | doh! meant to comment on cluster stuff, was afk for a minute or so :X | 20:04 |
| vipul | #topic Automated Backups Design | 20:04 |
| *** openstack changes topic to "Automated Backups Design (Meeting topic: trove)" | 20:04 | |
| vipul | arborism: that'll be after this topic | 20:04 |
| vipul | cp16net: wanna take it away? | 20:05 |
| cp16net | yes... thx | 20:05 |
| cp16net | so this name i think is a little off now that i have more defined | 20:05 |
| cp16net | its more about scheduled tasks | 20:05 |
| vipul | #link https://wiki.openstack.org/wiki/Trove/scheduled-tasks | 20:05 |
| cp16net | this will require a scheduler that will send messages to the guests to rn the tasks | 20:06 |
| cp16net | these tasks could be anything | 20:06 |
| *** yogesh has joined #openstack-meeting-alt | 20:06 | |
| cp16net | but initially we will have backups | 20:06 |
| cp16net | this could be extended to allowing updates to pacakges for the customer | 20:06 |
| arborism | theoretically, the guest upgrade blueprint could find some usefulness as a scheduled task as well, no? | 20:07 |
| cp16net | like mysql/guest or other packages | 20:07 |
| vipul | yep i would think we'd be able to do that | 20:07 |
| cp16net | it surely can | 20:07 |
| arborism | niiiiice | 20:07 |
| SlickNik | @cp16net: will the guest be agnostic about these tasks? | 20:07 |
| *** vinodmr has left #openstack-meeting-alt | 20:08 | |
| cp16net | SlickNik: the guest will be able to handle them | 20:08 |
| cp16net | the idea is that the scheudler will send a task to the guest to act on | 20:09 |
| cp16net | that guest will complete that task and report back on it | 20:09 |
| SlickNik | cp16net: Sorry if I was a bit unclear. Meant to ask whether the guest would know the difference between whether a task was part of a schedule or not? | 20:09 |
| cp16net | that its complete and such | 20:09 |
| SlickNik | Or does it look like just another task to the gues | 20:09 |
| vipul | cp16net: so what does it mean for a maintenance window | 20:09 |
| SlickNik | guest* | 20:09 |
| vipul | like does the guest know not to accept any more 'tasks' ? | 20:09 |
| cp16net | SlickNik: i think it would be able to tell if it was a scheudled | 20:10 |
| grapex | cp16net: What would the distinction be? | 20:10 |
| cp16net | because the guest needs to report back saying that the task it was given is complete | 20:10 |
| grapex | Or rather, what value does having that distinction give us? | 20:10 |
| grapex | Seems like a typical "call". Or a longer running task issued via "cast" which the guest then updates Trove on | 20:10 |
| cp16net | vipul: the maintenance window is decalared by the customer of when they would want these schedules to run | 20:11 |
| SlickNik | So then do we need a separate scheduler component? Or can the guest just run the task based on the schedule of the task? | 20:11 |
| grapex | which currently happens through the database, but will possibly be over RPC in the future via conductor or something. | 20:11 |
| vipul | kinda agree with grapex.. seems unnecessary for the guest to be aware or differentiate how an request to it originated | 20:11 |
| cp16net | grapex: this is a good point that we need bidirectional comm between the guest and system | 20:11 |
| cp16net | i was thining that the conductor could handle some of this | 20:11 |
| grapex | SlickNik: The guest has to schedule stuff it makes it harder to manage if things begin to fail or die | 20:11 |
| grapex | cp16net: Possibly | 20:12 |
| cp16net | but that is just a dream atm | 20:12 |
| grapex | but for this conversation | 20:12 |
| grapex | let's assume that the guest has a decent way to pass back info to Trove | 20:12 |
| grapex | cp16net: I have a feeling the first phase of conductor won't take too long | 20:12 |
| cp16net | SlickNik: the idea i have is that theere is a new service running as the scheduler | 20:12 |
| dmakogon_ | i thinks the best way it to pass data through DB | 20:12 |
| vipul | dmakogon_: that's how it's done now | 20:13 |
| cp16net | grapex: yes i agree that because its just a dream i have | 20:13 |
| grapex | dmakogon_: Maybe- we could create a strategy for using the DB still if people want to- | 20:13 |
| vipul | yea it should be configuratable i suppose | 20:13 |
| grapex | let's save the talk of sending messages back on the guest for when we discuss Conductor later | 20:13 |
| cp16net | have the guest agent have different stragetys? | 20:13 |
| cp16net | ew.. spellign | 20:13 |
| *** tsimmons has quit IRC | 20:14 | |
| *** jasonb365 has joined #openstack-meeting-alt | 20:14 | |
| vipul | let's table that for now.. talk about automated tasks now | 20:14 |
| dmakogon_ | and choosing strategy would be configurable ?? | 20:14 |
| vipul | a maintentenance window to me seems like a time the guest should not be able to do things that may be long running | 20:14 |
| cp16net | so lets bring this back to the scheduled task | 20:14 |
| vipul | like i want to upgrade my guest agent during a time window.. | 20:14 |
| cp16net | its going to handle scheudling a task on behalf of the customer | 20:14 |
| vipul | so i can be sure a backup isn't runnign when i take it down | 20:15 |
| SlickNik | cp16net: I'm still working through the pro's and cons of having a separate scheduler. | 20:15 |
| grapex | vipul: Ah | 20:15 |
| *** yogesh has quit IRC | 20:15 | |
| grapex | Well, we already have code to see if an action in trove can be performed | 20:15 |
| dmakogon_ | scheduler should be done like it done in nova | 20:15 |
| dmakogon_ | or am i wrong ? | 20:15 |
| SlickNik | nova scheduler is something different. | 20:16 |
| vipul | grapex: Yea i'd wnat to extend that to take the maintenance window into account i susppose | 20:16 |
| cp16net | dmakogon_: thats the idea | 20:16 |
| grapex | vipul: What may be possible is to query to see if the guest or instance is ready at routine intervals and then upgrade if possible | 20:16 |
| grapex | dmakogon_: I think we should take whatever is applicable from Nova | 20:16 |
| SlickNik | grapex / dmakogon_: I don't think that nova does time based scheduling. | 20:16 |
| vipul | grapex: that could work as well | 20:16 |
| key2 | dmakogon_: Can you create the blueprint? | 20:17 |
| vipul | SlickNik: agreed, everything time based just is a periodic task within exisitng services | 20:17 |
| grapex | So | 20:17 |
| dmakogon_ | key2: i could do that | 20:17 |
| grapex | cp16net: do you see a distinction between what you propose and these time based calls to the guest? | 20:17 |
| *** rnirmal has quit IRC | 20:18 | |
| grapex | key2 dmakogon_: I'm not sure if there's a dictinction between what you're suggesting and the scheduled tasks blueprint | 20:18 |
| vipul | grapex: cp16net i do see one diff... nova doens't take inot account a user's specified time | 20:18 |
| cp16net | i'm a little confused between what the question i am reading | 20:18 |
| SlickNik | why can't the scheduled task info just be stored on the guest. | 20:18 |
| datsun180b | Because containers aren't reliable for keeping time | 20:18 |
| cp16net | oh i see what you mean | 20:18 |
| SlickNik | And the guest can decide when to run based on a periodic task, this time based info, and maintenance window info. | 20:18 |
| redthrux | and we don't want the guest to grow larger and larger having to track things | 20:18 |
| grapex | SlickNik: Let's say the guest dies- | 20:18 |
| cp16net | we dont want to make the guest any more complicated | 20:18 |
| *** benl has joined #openstack-meeting-alt | 20:19 | |
| cp16net | we rather keep it in the infra | 20:19 |
| SlickNik | Well, if the guest dies it can't run anything anyway. | 20:19 |
| grapex | SlickNik: Maybe the guest could send back in it's heart beat if it has resources on hand to perform tasks | 20:19 |
| cp16net | this needs to be able to handle different senarios | 20:19 |
| vipul | you'd have to give the guest access to the database | 20:19 |
| vipul | where will it configure itself from | 20:19 |
| imsplitbit | NOOOOOOOOOOOOOOO | 20:19 |
| imsplitbit | :) | 20:19 |
| vipul | but we should look at simplifying this.. it may very well be create a crontab entry on the guest | 20:20 |
| vipul | but what drives that might be some trove service | 20:20 |
| cp16net | one of the ideas here is that its plugable with diffrernt strategies | 20:20 |
| key2 | well. let's consider how we different from Nova in terms of requirements to the module | 20:20 |
| esp | yeah I think having a dedicated scheduler makes sense. | 20:20 |
| SlickNik | A separate scheduler is a single point of failure for jobs across multiple guests. | 20:20 |
| grapex | So the issue is do we want to make the guest store this information on scheduling and also have to be in charge of cron | 20:20 |
| cp16net | vipul: i think thats a bad idea to have cron running on the geust | 20:20 |
| kevinconway | vipul: wouldn't a cron schedule on the guest make it harder to implement the scheduler pause you want to introduce for maintenance windows? | 20:20 |
| cp16net | it should be centalized | 20:21 |
| redthrux | (and clusterable) | 20:21 |
| cp16net | redthrux: +1 | 20:21 |
| imsplitbit | if it is centralized then clusterable is a requirement | 20:21 |
| vipul | kevinconway: point.. | 20:21 |
| key2 | redthrux: +1 | 20:21 |
| key2 | I desperately want Cassandra )) | 20:21 |
| esp | SlickNik: not necessarily | 20:22 |
| dmakogon_ | Cassandra is easy clusterable | 20:22 |
| SlickNik | cp16net: you can't really control running _only_ in maintenance windows if it's centralized. | 20:22 |
| dmakogon_ | key2: but the point is scheduler for now | 20:22 |
| grapex | SlickNik: Is it because the central point wouldn't know if the maintenance window is happening? | 20:22 |
| cp16net | SlickNik: its the only way you can if the customer is to define when the window is | 20:22 |
| SlickNik | You don't know if the guest / network is down when you schedule the cast. | 20:22 |
| imsplitbit | well lets not get bogged down too heavy in impl details | 20:22 |
| grapex | SlickNik: We have heart beats though, so we should know | 20:22 |
| cp16net | SlickNik: there is an api that the customer can define what the window will be | 20:22 |
| SlickNik | So when the guest picks the message up, it _might_ well be out of the window. | 20:22 |
| key2 | dmakogon_: I mean we should keep clustering in mind | 20:23 |
| dmakogon_ | key2: yes, it's really true! | 20:23 |
| grapex | SlickNik: I am expecting the latency to be short enough that won't be a problem | 20:23 |
| vipul | You should only send messages to services that are up | 20:23 |
| grapex | Maybe I'm assuming too much | 20:23 |
| cp16net | SlickNik: you bring up a good point tho | 20:23 |
| cp16net | SlickNik: there has to be a fuzzy window | 20:23 |
| SlickNik | So what if you send one message after another. | 20:23 |
| SlickNik | Guest is up | 20:23 |
| grapex | SlickNik: I know at Rack, the latency of messages isn't more than a second or so | 20:23 |
| cp16net | it can not be exact | 20:23 |
| kevinconway | grapex: could always treat it like medication. take as soon as possible or just the next dose. whichever is soonest. | 20:23 |
| SlickNik | But the first action takes a long time to complete, so that when the guest picks the second message, it's out of the window. | 20:24 |
| grapex | SlickNik: Maybe what's needed are TTLs and gauranteed delivery | 20:24 |
| SlickNik | You can't guarantee maintenance windows unless you build that logic _into_ the guest. | 20:24 |
| *** esker has quit IRC | 20:24 | |
| vipul | That's logic that can be built into the scheduling hting to only send it the second message after you know the first maintennace task is done | 20:24 |
| grapex | So if the scheduler makes the guest do something, and it doesn't, the request is cancelled | 20:24 |
| *** crobertsrh is now known as _crobertsrh | 20:25 | |
| vipul | grapex: that's assuming syncronous | 20:25 |
| grapex | SlickNik: There could also be time windows sent- so the guest would know if it's past the given Window don't bother | 20:25 |
| redthrux | +1 grapex - easily done with messages in if you are using rabbitmq | 20:25 |
| vipul | it seems like the scheduler component will need to keep task status in mind.. and if it does you can solve for these things | 20:25 |
| SlickNik | Vipul, what if the guest is already taking a backup based on a user call. | 20:25 |
| kevinconway | could scheduled tasks come with an expiry time where the guest will refuse it with knowledge that another task is coming? | 20:25 |
| vipul | that's somethign the scheduler shoudl be aware | 20:25 |
| vipul | you shoudln't blindly schedule things | 20:25 |
| cp16net | vipul: grapex: SlickNik: should we have a meeting outisde of this meeting on this? | 20:25 |
| vipul | whether you're in a maintenance window or not | 20:25 |
| *** tsimmons has joined #openstack-meeting-alt | 20:25 | |
| vipul | cp16net: yes | 20:25 |
| SlickNik | Yes, please | 20:26 |
| SlickNik | cp16net: ^^^ | 20:26 |
| vipul | moving on.. evryone.. look over the Design please | 20:26 |
| key2 | cp16net: yes | 20:26 |
| vipul | let's try to meet again | 20:26 |
| vipul | this week or next? | 20:26 |
| cp16net | i'd gladly talk more but we do have more to talk about orry | 20:26 |
| cp16net | this week perferably | 20:26 |
| vipul | let's throw out some times | 20:26 |
| vipul | tomorrow at 2PST? | 20:26 |
| cp16net | we could chat tmorrow at this same time | 20:27 |
| SlickNik | Works for me | 20:27 |
| imsplitbit | I can't make that but don't hold it up on me | 20:27 |
| cp16net | 3cst? | 20:27 |
| vipul | ok 1pst tomorrow 3cst | 20:27 |
| vipul | done | 20:27 |
| vipul | #topic Trove API section for DB type selection | 20:27 |
| *** openstack changes topic to "Trove API section for DB type selection (Meeting topic: trove)" | 20:27 | |
| vipul | imsplitbit: is this you? | 20:27 |
| imsplitbit | no | 20:28 |
| dmakogon_ | me | 20:28 |
| vipul | go dmakogon_ | 20:28 |
| dmakogon_ | what the idea, we should provide specific chose to user for service type | 20:28 |
| dmakogon_ | it could be setted by config, or be stored at DB and be manually added to it | 20:29 |
| vipul | service_type is something that we allow user to specify | 20:29 |
| vipul | in the create instance call | 20:30 |
| dmakogon_ | in this way every one could extend initail configs for trove and build custom images with differernt DBs | 20:30 |
| vipul | with that, today you can support >1 type of db in trove | 20:30 |
| dmakogon_ | for now it specifies only one type | 20:30 |
| dmakogon_ | it's not normal | 20:30 |
| vipul | in the config? yes | 20:30 |
| SlickNik | dmakogon_: the trove config only specifies the _default_ service type. | 20:30 |
| dmakogon_ | trove should do it's dinamically | 20:30 |
| vipul | that becomes the default service_type ... BUT if you had another entry in service_images it would honor that | 20:30 |
| SlickNik | You can still have other service types that you can explicitly pick during the instance create call. | 20:31 |
| arborism | One thing to consider, is that given you'll likely want specific flavors for different service_types, how do you guarantee such affinity? You could let the flavor drive the service_type (e.g. mysql.xl)... | 20:31 |
| dmakogon_ | my point is to extend API for adding new dinamic parameter | 20:31 |
| dmakogon_ | service_type | 20:31 |
| vipul | arborism: https://blueprints.launchpad.net/trove/+spec/service-type-filter-on-flavors | 20:31 |
| dmakogon_ | and it's should be done | 20:32 |
| SlickNik | arborism: good point. there's a later topic scheduled to discuss that very thing ^^^ | 20:32 |
| grapex | arborism: I'd rather have some new API resource analogous to Nova images that let a user enumerate service types. | 20:32 |
| vipul | dmakogon_: so a management API | 20:32 |
| cp16net | dmakogon_: could there be an extension for this? | 20:32 |
| vipul | yes! grapex we disucssed this a while ago | 20:32 |
| kevinconway | grapex: +1 | 20:32 |
| vipul | GET /servicetypes | 20:32 |
| grapex | vipul: Sorry... good we agree though. :) | 20:32 |
| dmakogon_ | cp16net: i think we could do that | 20:33 |
| SlickNik | I like that idea, grapex / vipul | 20:33 |
| vipul | grapex: no worries.. i just mean we should revive that discussion | 20:33 |
| vipul | it was proposed by demorris a while ago.. then sort of died | 20:33 |
| vipul | but since ther is a lot of itnerest in support >1 service type.. we kinda need the API | 20:33 |
| dmakogon_ | it wont die | 20:33 |
| vipul | dmakogon_: So i think what you want is a management api to add new service types.. please file a BP | 20:34 |
| dmakogon_ | i will try to make a propose at wiki | 20:34 |
| dmakogon_ | ok | 20:34 |
| cp16net | grapex: so that the maintainer could disable types or set one as default? | 20:34 |
| vipul | done? moving on | 20:34 |
| SlickNik | good with it | 20:34 |
| vipul | #topic clustering API update | 20:34 |
| *** openstack changes topic to "clustering API update (Meeting topic: trove)" | 20:34 | |
| grapex | cp16net: Sure | 20:34 |
| arborism | dmakogon_: While spec'ing, can you also take into consideration versioning? i.e. mysql-5.5 vs. 5.6 | 20:34 |
| dmakogon_ | arborism: ok | 20:35 |
| vipul | dmakogon_: you wanted to chime in here? | 20:35 |
| kevinconway | arborism: nova images handle the same thing | 20:35 |
| key2 | arborism: anything else beside version? | 20:35 |
| dmakogon_ | but it although makes API more complicated | 20:35 |
| kevinconway | ubuntu 12 vs ubuntu 13 are just different images | 20:36 |
| vipul | anyone have anythign to say about clusterin API? | 20:36 |
| arborism | I wasn't advocating for anything, I was just mentioning that while writing out the specs, to consider the implications of wanting multiple versions of a service_type available. How it's impl'd/handled is up in the air. | 20:36 |
| arborism | vipul: Yes | 20:36 |
| dmakogon_ | kevinconway: should you propose still image for it | 20:36 |
| vipul | arborism: dmakogon_: i'll try to find an old wiki for it | 20:37 |
| dmakogon_ | vipul: i have | 20:37 |
| arborism | So given the API Ref, I'm not sure I see how it will work in the future w/ the inevitable parameter groups and region awareness requirements | 20:37 |
| arborism | (regarding Clustering API) | 20:37 |
| vipul | go for it.. | 20:37 |
| dmakogon_ | if, in future, trove will have multiple service support | 20:38 |
| *** rnirmal has joined #openstack-meeting-alt | 20:38 | |
| vipul | yes.. | 20:38 |
| dmakogon_ | we sould build flexible clustering API that will be applicapable for all | 20:38 |
| dmakogon_ | sorry for slow typing | 20:38 |
| vipul | no worries :) | 20:39 |
| imsplitbit | I believe that's what we're attempting to do | 20:39 |
| imsplitbit | we're trying to make it as open as possible | 20:39 |
| dmakogon_ | that is why, although Trove API(single-node) should be changed | 20:39 |
| vipul | #link https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API-Using-Instances | 20:39 |
| dmakogon_ | because of alot of NoSQL doesn't support ACL at db-layer | 20:39 |
| vipul | dmakogon_: after lookign at that proposal.. do you think there are things that don't fit with other dbs? | 20:40 |
| arborism | vipul: redis | 20:40 |
| dmakogon_ | cassandra | 20:40 |
| vipul | arborism: :P | 20:40 |
| dmakogon_ | alot of dbs | 20:40 |
| vipul | are we going to bring up users again | 20:40 |
| imsplitbit | where? | 20:40 |
| imsplitbit | how? | 20:40 |
| imsplitbit | lol | 20:40 |
| imsplitbit | please god no | 20:40 |
| arborism | can i elaborate on redis? | 20:40 |
| imsplitbit | sure | 20:40 |
| kevinconway | even i don't want to talk about users anymore | 20:40 |
| arborism | without users ;) | 20:40 |
| imsplitbit | please proceed | 20:40 |
| arborism | Say I have 3 DCs, and I want a Redis Master in each | 20:40 |
| dmakogon_ | we don't need users in NoSQL | 20:41 |
| arborism | I'll use consistent hashing client side | 20:41 |
| arborism | to pick | 20:41 |
| arborism | How, with the clustering api, will I be able to add a read slave | 20:41 |
| arborism | picking whether I want to daisy chain, or connect directly to master | 20:41 |
| arborism | plus, choose the ability to accept explicit writes on a slave (aka readonly) | 20:41 |
| imsplitbit | I am not sure where in the clustering api it doesn't allow you to do that | 20:42 |
| arborism | Because as a whole, I'd logically consider the entire deployment a cluster, but with the api spec | 20:42 |
| arborism | There's no "nodeType" | 20:42 |
| arborism | only cluster type | 20:42 |
| vipul | i think that's what the clusterConfig is for | 20:42 |
| *** yogesh has joined #openstack-meeting-alt | 20:42 | |
| vipul | you specify the primary.. at least in that example | 20:42 |
| vipul | we may need to extend what goes in there based on service type | 20:43 |
| arborism | well, read replica uses primary, add a node doesn't | 20:43 |
| imsplitbit | there is a concept of roles within thee clustering api | 20:43 |
| arborism | vipul: but doesn't clusterConfig end up becoming a parameter group? | 20:43 |
| SlickNik | arborism: can you explain what you mean by parameter group? | 20:44 |
| SlickNik | (or link to something that does, please) | 20:44 |
| arborism | e.g. key-value-pairs related to the service_type | 20:44 |
| arborism | a la, conf pairs | 20:44 |
| vipul | arborism: i guess it would become that if we allowed it to change | 20:45 |
| vipul | maybe what we need is a concrete API example that will do what you want.. | 20:45 |
| arborism | Let me paste out a couple of things I wrote, then add a quick comment: | 20:45 |
| arborism | > In "Create Replication Set: (No previous db instance, fresh)", should be able to specify flavorRef per Node. | 20:45 |
| vipul | and we should compare that with what we've come up with so far | 20:45 |
| arborism | > "Create Replication Set" is a POST to /clusters, but "Add Node" is a PUT to /clusters/{cluster_id}/nodes, this seems inconsistent. | 20:46 |
| arborism | Is primaryNode the means of association, or is it the URI (i.e. /clusters/{cluster_id}) | 20:46 |
| arborism | > Confused on "Promote a slave node to master"; where is it indicating the promotion action explicitly? Why not /clusters/{cluster_id}/promote? | 20:46 |
| arborism | > What's the expected behavior of a resize, delete, restart-db, or restart on /instance/{instance_id}? Block? Forward to /clusters? | 20:46 |
| dmakogon_ | arborism: flavorRef of each node should be the same | 20:47 |
| dmakogon_ | it is like BP | 20:47 |
| dmakogon_ | best-practicies | 20:47 |
| arborism | dmakogon_: Not true. We had that discussion awhile ago. You might want a read slave with a beefier profile to handle ad-hoc queries | 20:47 |
| imsplitbit | correct | 20:47 |
| arborism | I modeled out multiple service types, and arrived at: https://gist.github.com/amcr/96c59a333b72ec973c3a | 20:48 |
| arborism | To me, it seems a little easier to grok | 20:48 |
| imsplitbit | create should allow you to easily create a cluster of instances of all the same flavor really easily but shouldn't be so inflexible so as to disallow individual flavors | 20:48 |
| arborism | imsplitbit: +1 | 20:49 |
| key2 | imsplitbit: +1 | 20:49 |
| dmakogon_ | arborism: i will do it in my way | 20:50 |
| imsplitbit | with regard to the notes, I'll need to look through them more and we can discuss further. but for example, adding a an instance to a cluster is a cluster operation | 20:50 |
| imsplitbit | so it would be in /cluster, not /instance | 20:50 |
| vipul | so do we need to set up another meeting to discuss clusters? | 20:50 |
| dmakogon_ | imsplitbit: +1 | 20:50 |
| imsplitbit | seems like it | 20:50 |
| vipul | some of these questions we should send in ML as well | 20:50 |
| vipul | mailing list | 20:50 |
| vipul | Sounds like we have a big enough audience that IRC isn't going to work for every time zone | 20:51 |
| dmakogon_ | even if you create a cluster with tha same flavors for each node, you could do a instance_resize, on each of it | 20:51 |
| imsplitbit | and it may be that the doc is unclear and questions like this will help us get that fixed | 20:51 |
| vipul | arborism: what would you prefer | 20:51 |
| arborism | i'm amicable to whatever works for you guys | 20:51 |
| vipul | running out of time.. 10 minutes to go | 20:51 |
| SlickNik | Yes, we might need to take some of these discussion to the mailing list. | 20:51 |
| key2 | ML +1 | 20:52 |
| vipul | arborism: send the email [trove] in subject line :) | 20:52 |
| vipul | #topic Flavors per Service Type | 20:52 |
| *** openstack changes topic to "Flavors per Service Type (Meeting topic: trove)" | 20:52 | |
| vipul | https://blueprints.launchpad.net/trove/+spec/service-type-filter-on-flavors | 20:52 |
| SlickNik | arborism does raise some valid points that I would like to see addressed. | 20:52 |
| vipul | so arborism this is somehting you might be interested in as well.. | 20:52 |
| vipul | if everyone is good with it.. we'll start working on it | 20:52 |
| arborism | It is, because I want to shield Trove specific flavors from regular compute provisioning | 20:53 |
| arborism | and vice versa | 20:53 |
| vipul | k cool | 20:53 |
| SlickNik | I'm totally good with it. | 20:53 |
| vipul | #topic Trove Conductor | 20:53 |
| *** openstack changes topic to "Trove Conductor (Meeting topic: trove)" | 20:53 | |
| vipul | who's doing this | 20:53 |
| datsun180b | me | 20:54 |
| datsun180b | That is, I'm working on implementing a proof of concept first | 20:54 |
| datsun180b | I don't have a #link handy but KennethWilke wrote up a rough of what we want | 20:54 |
| vipul | datsun180b: i assume you captured some of the comment from today.. about making it optional | 20:54 |
| datsun180b | #link https://wiki.openstack.org/wiki/Trove/guest_agent_communication | 20:54 |
| datsun180b | if i didn't, i hope eavesdrop did | 20:55 |
| grapex | It seems like all step one of this needs to be is to set up a OpenStack daemon that receives RPC calls | 20:55 |
| arborism | nice, didn't see this one. we have heartbeats turned off for this very concern. | 20:56 |
| grapex | and receives one for the heartbeat, and another for backup status | 20:56 |
| datsun180b | grapex: done in poc | 20:56 |
| vipul | Ok everyone please look at ^^ as well, we'll have to tlak more about it next meeting | 20:56 |
| SlickNik | datsun180b / KennethWilke: reading the wiki on it. Nice explanation! | 20:56 |
| grapex | make the guest use that instead of updating the DB | 20:56 |
| datsun180b | that's as much as i've got presently though | 20:56 |
| vipul | sorry guys.. moving on... time constraint | 20:56 |
| vipul | #topic Naming convention / style guide | 20:56 |
| *** openstack changes topic to "Naming convention / style guide (Meeting topic: trove)" | 20:56 | |
| imsplitbit | ok real quick | 20:56 |
| grapex | vipul: I'm adding an action for datsun180b | 20:56 |
| imsplitbit | I've been looking through trove code | 20:56 |
| vipul | thanks grapex | 20:56 |
| grapex | #action datsun180b to do pull request on phase one of Trove Conductor | 20:57 |
| imsplitbit | and I've noticed that the json structures aren't consistent for keys | 20:57 |
| imsplitbit | some are camel case and some are underscore | 20:57 |
| *** tsimmons has quit IRC | 20:57 | |
| vipul | the actual request bodies? | 20:57 |
| imsplitbit | I just wanted to bring that up and see if we can come to an agreement some point soon on getting some consistency there | 20:57 |
| datsun180b | for example, root_enabled ? | 20:57 |
| SlickNik | can you link a couple of examples, imsplitbit? | 20:58 |
| imsplitbit | sure | 20:58 |
| datsun180b | my fault | 20:58 |
| arborism | flavorRef vs. service_type | 20:58 |
| vipul | ugh.. | 20:58 |
| vipul | don't know what the openstack stance is on this | 20:58 |
| imsplitbit | well | 20:58 |
| grapex | Does anyone know if an *official* OpenStack style has popped up int he past few years? | 20:58 |
| imsplitbit | yeah | 20:58 |
| datsun180b | besides HACKING? | 20:58 |
| imsplitbit | we have flavorRef | 20:58 |
| imsplitbit | resorePoint | 20:58 |
| imsplitbit | and service_type | 20:58 |
| grapex | Originally we looked and found swift and nova had different styles in their API | 20:58 |
| imsplitbit | root_enabled | 20:58 |
| imsplitbit | it was confusing to me having not worked in the api until recently | 20:59 |
| datsun180b | I'm to blame for root_enabled! I was young and naive! | 20:59 |
| grapex | imsplitbit: It's "flavorRef" as Nova did it that way. | 20:59 |
| kevinconway | grapex: all lower case, underscored, and using wingdings characters | 20:59 |
| grapex | But it seems like after that | 20:59 |
| grapex | we've gone with PEP8 styles | 20:59 |
| imsplitbit | right | 20:59 |
| grapex | And IIRC Nova is also inconsistent in it's own API | 20:59 |
| imsplitbit | and pep8 would smack you upside the head for camelcase | 20:59 |
| grapex | So maybe what we do is decided to go forward with PEP8 styled field names in the future | 21:00 |
| imsplitbit | I'm not opposed to either | 21:00 |
| grapex | and keep the old names around for backwards compatability | 21:00 |
| imsplitbit | but I'm opposed to both | 21:00 |
| imsplitbit | it looks messy | 21:00 |
| datsun180b | i don't know that pep8 governs variable naming, past it must be tokenizable by the parser | 21:00 |
| dmakogon_ | https://blueprints.launchpad.net/trove/+spec/multi-service-type-support - is gonna be approved ? | 21:00 |
| cp16net | yea i didnt think it mattered | 21:00 |
| grapex | datsun180b: Keep in mind when I say PEP8, this isn't a code convention, but one for the Rest API- PEP8 won't catch it | 21:00 |
| *** KennethWilke has quit IRC | 21:00 | |
| vipul | #action Find json style guide vipul hub_cap grapex | 21:00 |
| kevinconway | http://www.python.org/dev/peps/pep-0008/#naming-conventions | 21:01 |
| vipul | ok moving on.. | 21:01 |
| SlickNik | pep8 has no take on the matter. | 21:01 |
| vipul | #topic open Discussion | 21:01 |
| *** openstack changes topic to "open Discussion (Meeting topic: trove)" | 21:01 | |
| cp16net | haha gl on finding one :-P | 21:01 |
| vipul | continue.. :) | 21:01 |
| grapex | So quick question | 21:01 |
| dmakogon_ | all blueprints are approved for today ? | 21:01 |
| grapex | arborism: https://gist.github.com/amcr/96c59a333b72ec973c3a Is the style here of putting different keys for each service type what we're going with? | 21:01 |
| vipul | oh.. . | 21:02 |
| arborism | No, just a thought experiment of avoiding a /custer api | 21:02 |
| datsun180b | guess i'd better reread pep8, i'm getting rusty | 21:02 |
| kevinconway | vipul: grapex: http://javascript.crockford.com/code.html closest you might get to a style guide for JS related things | 21:02 |
| grapex | arborism: Ok | 21:02 |
| vipul | arborism: dmakogon_ this might interest you https://wiki.openstack.org/wiki/Reddwarf-versions-types | 21:02 |
| vipul | it is the serviceType api that never got implemented | 21:02 |
| grapex | vipul: Thanks | 21:02 |
| kevinconway | datsun180b: http://www.pylint.org/ | 21:03 |
| grapex | One more question - and this may be a can of worms | 21:03 |
| vipul | oh noe grapex :) | 21:03 |
| grapex | and not the fun kind either that jump out like a gag | 21:03 |
| arborism | Is it about users? | 21:03 |
| arborism | ;) | 21:03 |
| grapex | but the bad kind of worms | 21:03 |
| cp16net | doh | 21:03 |
| grapex | arborism: Lol | 21:03 |
| grapex | So- the reference guest, as it is today- does it block all incoming RPC calls when doing a backup? | 21:03 |
| datsun180b | kevinconway: a foolish consistency... | 21:03 |
| dmakogon_ | vipul: i think we should do that | 21:03 |
| kevinconway | datsun180b: meaning if you break consistency ever | 21:04 |
| kevinconway | for any reason | 21:04 |
| vipul | So i don't think we do... since it's asynchronous | 21:04 |
| SlickNik | grapex: I think it works on one message at a time. | 21:04 |
| vipul | SlickNik: that is correct.. but create backup isn't sync | 21:04 |
| grapex | I ask this because we need the guest to report on the size of the volume even while doing a backup. | 21:04 |
| cp16net | vipul: so its in its own thread when runnning a backup? | 21:04 |
| vipul | we do spawn a subprocess to take the backup | 21:05 |
| vipul | which probably doesn't block | 21:05 |
| vipul | i could be wrong | 21:05 |
| SlickNik | we spawn a subprocess, yes. | 21:05 |
| grapex | vipul: Ok, so then it can get other RPC calls as it's taking the backup? | 21:05 |
| grapex | Just checking | 21:05 |
| vipul | I _think_ so.. i'd have to get back to you | 21:05 |
| grapex | By the way this is what Sneaky Pete does in case it's not obvious what I'm driving at. Some of the questions in the meeting today made me think otherwise. | 21:05 |
| grapex | If it doesn't we can work to change the reference guest | 21:06 |
| grapex | vipul: Ok | 21:06 |
| vipul | i woudl be great to block though :P | 21:06 |
| vipul | so we could do things like upgrade.. and mke sure upgrade only happens after backup is finished | 21:06 |
| grapex | vipul: There are ways around that, like using the trove code that currently checks to see if an action is being performed. | 21:07 |
| grapex | But that's back to the discussion we already finished up. | 21:07 |
| grapex | Since we're past time | 21:07 |
| vipul | alrighty.. calling it done | 21:07 |
| vipul | #endmeeting | 21:07 |
| *** openstack changes topic to "OpenStack meetings (alternate)" | 21:07 | |
| openstack | Meeting ended Wed Aug 21 21:07:45 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:07 |
| dmakogon_ | vipul: soon i'll propose my own version of API, that wont ruined current Trove and add new stuff for it | 21:07 |
| grapex | Thanks vipul! | 21:07 |
| cp16net | awesome | 21:07 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-08-21-20.00.html | 21:07 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-08-21-20.00.txt | 21:07 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-08-21-20.00.log.html | 21:07 |
| cp16net | thanks! | 21:07 |
| *** imsplitbit has left #openstack-meeting-alt | 21:08 | |
| SlickNik | so grapex, just looked at the code. | 21:08 |
| vipul | dmakogon_: Ok, please write it up | 21:08 |
| *** dmakogon_ has left #openstack-meeting-alt | 21:09 | |
| *** esp has left #openstack-meeting-alt | 21:09 | |
| *** Riddhi has quit IRC | 21:13 | |
| *** dina_belova has quit IRC | 21:16 | |
| *** betsy has quit IRC | 21:19 | |
| *** tsimmons has joined #openstack-meeting-alt | 21:21 | |
| *** tsimmons has left #openstack-meeting-alt | 21:21 | |
| *** jmontemayor has quit IRC | 21:21 | |
| *** pdmars has quit IRC | 21:23 | |
| *** yogesh has quit IRC | 21:23 | |
| *** yogesh has joined #openstack-meeting-alt | 21:24 | |
| *** SlickNik has left #openstack-meeting-alt | 21:25 | |
| *** yogesh has quit IRC | 21:26 | |
| *** ashestakov has left #openstack-meeting-alt | 21:28 | |
| *** jasonb365 has quit IRC | 21:30 | |
| *** vipul is now known as vipul-away | 21:32 | |
| *** vipul-away is now known as vipul | 21:35 | |
| *** eankutse has quit IRC | 21:37 | |
| *** eankutse has joined #openstack-meeting-alt | 21:37 | |
| *** eankutse has quit IRC | 21:37 | |
| *** SergeyLukjanov has quit IRC | 21:45 | |
| *** robertmyers has quit IRC | 22:09 | |
| *** dina_belova has joined #openstack-meeting-alt | 22:17 | |
| *** dina_belova has quit IRC | 22:21 | |
| *** dina_belova has joined #openstack-meeting-alt | 22:27 | |
| *** dina_belova has quit IRC | 22:32 | |
| *** sarob has joined #openstack-meeting-alt | 22:38 | |
| *** sacharya has quit IRC | 22:48 | |
| *** benl has quit IRC | 22:53 | |
| *** rnirmal has quit IRC | 23:05 | |
| *** NehaV has quit IRC | 23:11 | |
| *** mberwanger has joined #openstack-meeting-alt | 23:13 | |
| *** mberwanger has quit IRC | 23:21 | |
| *** yogesh has joined #openstack-meeting-alt | 23:24 | |
| *** datsun180b has quit IRC | 23:27 | |
| *** dina_belova has joined #openstack-meeting-alt | 23:28 | |
| *** dina_belova has quit IRC | 23:32 | |
| *** yidclare has quit IRC | 23:40 | |
| *** yogesh has quit IRC | 23:41 | |
| *** yidclare has joined #openstack-meeting-alt | 23:41 | |
| *** jcooley has quit IRC | 23:41 | |
| *** yidclare has quit IRC | 23:42 | |
| *** jcooley has joined #openstack-meeting-alt | 23:44 | |
| *** saurabhs has left #openstack-meeting-alt | 23:51 | |
| *** sacharya has joined #openstack-meeting-alt | 23:51 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!