Wednesday, 2013-10-23

*** rudrarugge has quit IRC00:00
*** SumitNaiksatam has quit IRC00:15
*** cody-somerville has quit IRC00:18
*** sacharya has joined #openstack-meeting-alt00:21
*** SumitNaiksatam has joined #openstack-meeting-alt00:24
*** rakhmerov has joined #openstack-meeting-alt00:33
*** SumitNaiksatam has quit IRC00:34
*** rakhmerov has quit IRC00:37
*** sacharya1 has joined #openstack-meeting-alt00:40
*** sacharya has quit IRC00:40
*** mestery has quit IRC00:41
*** SumitNaiksatam has joined #openstack-meeting-alt00:41
*** sarob has quit IRC00:41
*** nosnos has joined #openstack-meeting-alt00:43
*** SumitNaiksatam has quit IRC00:50
*** Devioslang has joined #openstack-meeting-alt00:54
*** lblanchard has quit IRC00:57
*** vipul is now known as vipul-away01:00
*** vipul-away is now known as vipul01:09
*** gokrokve has quit IRC01:10
*** gokrokve has joined #openstack-meeting-alt01:11
*** gokrokve has quit IRC01:16
*** malini has left #openstack-meeting-alt01:20
*** markmcclain has quit IRC01:22
*** openstack has joined #openstack-meeting-alt01:34
*** ChanServ sets mode: +o openstack01:34
clarkb#startmeeting test01:34
openstackMeeting started Wed Oct 23 01:34:55 2013 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.01:34
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:34
*** openstack changes topic to " (Meeting topic: test)"01:34
openstackThe meeting name has been set to 'test'01:35
clarkb#topic clarkb test01:35
*** openstack changes topic to "clarkb test (Meeting topic: test)"01:35
clarkb#endmeeting01:35
*** openstack changes topic to "OpenStack meetings (alternate)"01:35
openstackMeeting ended Wed Oct 23 01:35:14 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/test/2013/test.2013-10-23-01.34.html01:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/test/2013/test.2013-10-23-01.34.txt01:35
openstackLog:            http://eavesdrop.openstack.org/meetings/test/2013/test.2013-10-23-01.34.log.html01:35
*** rakhmerov has quit IRC01:37
*** rakhmerov1 has joined #openstack-meeting-alt01:37
*** markwash has quit IRC01:38
*** esker has joined #openstack-meeting-alt01:38
*** anteaya has quit IRC01:39
*** SergeyLukjanov has quit IRC01:58
*** lpabon has joined #openstack-meeting-alt02:01
*** demorris has joined #openstack-meeting-alt02:08
*** markwash has joined #openstack-meeting-alt02:10
*** IlyaE has quit IRC02:15
*** vipul has quit IRC02:25
*** vipul has joined #openstack-meeting-alt02:25
*** IlyaE has joined #openstack-meeting-alt02:46
*** cody-somerville has joined #openstack-meeting-alt02:56
*** IlyaE has quit IRC03:16
*** lpabon has quit IRC03:17
*** vkmc has quit IRC03:24
*** demorris has quit IRC03:33
*** IlyaE has joined #openstack-meeting-alt03:46
*** jecarey has joined #openstack-meeting-alt03:46
*** gokrokve has joined #openstack-meeting-alt03:56
*** flwang has quit IRC03:56
*** gokrokve has quit IRC03:58
*** gokrokve has joined #openstack-meeting-alt04:01
*** IlyaE has quit IRC04:02
*** esker has quit IRC04:05
*** cody-somerville has quit IRC04:08
*** rosmaita has quit IRC04:12
*** heman-th has quit IRC04:12
*** ameade_ has quit IRC04:12
*** venkat_ has quit IRC04:12
*** esheffield has quit IRC04:12
*** nikhil has quit IRC04:12
*** iccha_ has quit IRC04:12
*** clarkb has quit IRC04:13
*** esheffield has joined #openstack-meeting-alt04:16
*** nikhil has joined #openstack-meeting-alt04:16
*** venkat_ has joined #openstack-meeting-alt04:17
*** hemanth has joined #openstack-meeting-alt04:17
*** IlyaE has joined #openstack-meeting-alt04:17
*** IlyaE has quit IRC04:20
*** iccha has joined #openstack-meeting-alt04:20
*** ameade has joined #openstack-meeting-alt04:20
*** rosmaita has joined #openstack-meeting-alt04:20
*** clarkb has joined #openstack-meeting-alt04:23
*** jmaron has quit IRC04:28
*** cody-somerville has joined #openstack-meeting-alt04:28
*** IlyaE has joined #openstack-meeting-alt04:33
*** flwang has joined #openstack-meeting-alt04:33
*** IlyaE has quit IRC04:34
*** esker has joined #openstack-meeting-alt04:37
*** cody-somerville has quit IRC04:38
*** sacharya1 has quit IRC05:00
*** esker has quit IRC05:11
*** esker has joined #openstack-meeting-alt05:11
*** akuznetsov has joined #openstack-meeting-alt05:13
*** cody-somerville has joined #openstack-meeting-alt05:14
*** cody-somerville has joined #openstack-meeting-alt05:14
*** esker has quit IRC05:16
*** akuznetsov has quit IRC05:17
*** dmakogon_ has joined #openstack-meeting-alt05:18
*** akuznetsov has joined #openstack-meeting-alt05:20
*** esker has joined #openstack-meeting-alt05:21
*** esker has quit IRC05:24
*** esker has joined #openstack-meeting-alt05:25
*** jmaron has joined #openstack-meeting-alt05:29
*** esker has quit IRC05:29
*** nadya has joined #openstack-meeting-alt05:37
*** esker has joined #openstack-meeting-alt05:46
*** esker has quit IRC05:47
*** jmaron has quit IRC05:48
*** esker has joined #openstack-meeting-alt05:48
*** nadya has quit IRC05:50
*** esker has quit IRC05:52
*** cody-somerville has quit IRC05:53
*** jecarey has quit IRC05:53
*** akuznetsov has quit IRC06:02
*** SergeyLukjanov has joined #openstack-meeting-alt06:06
*** nadya has joined #openstack-meeting-alt06:15
*** akuznetsov has joined #openstack-meeting-alt06:17
*** esker has joined #openstack-meeting-alt06:19
*** nadya has quit IRC06:19
*** IlyaE has joined #openstack-meeting-alt06:22
*** nadya has joined #openstack-meeting-alt06:30
*** nadya has quit IRC06:42
*** cody-somerville has joined #openstack-meeting-alt06:43
*** akuznetsov has quit IRC06:47
*** akuznetsov has joined #openstack-meeting-alt06:48
*** IlyaE has quit IRC06:51
*** akuznetsov has quit IRC06:52
*** esker has quit IRC06:53
*** resker has joined #openstack-meeting-alt06:56
*** amcrn has quit IRC07:09
*** lsmola has joined #openstack-meeting-alt07:13
*** jcoufal has joined #openstack-meeting-alt07:13
*** dmakogon_ has quit IRC07:40
*** akuznetsov has joined #openstack-meeting-alt07:51
*** SergeyLukjanov has quit IRC08:02
*** derekh has joined #openstack-meeting-alt08:11
*** ifarkas has joined #openstack-meeting-alt08:11
*** kiall has quit IRC08:12
*** kiall has joined #openstack-meeting-alt08:22
*** jtomasek has joined #openstack-meeting-alt08:34
*** jmaron has joined #openstack-meeting-alt08:44
*** jmaron has quit IRC08:49
*** eankutse has joined #openstack-meeting-alt08:56
*** flwang has quit IRC09:11
*** nosnos has quit IRC09:12
*** nosnos has joined #openstack-meeting-alt09:13
*** away_dude is now known as dmakogon09:14
*** dukhlov has joined #openstack-meeting-alt09:14
*** nosnos has quit IRC09:17
*** jtomasek has quit IRC09:22
*** jtomasek has joined #openstack-meeting-alt09:25
*** gokrokve has quit IRC09:28
*** gokrokve has joined #openstack-meeting-alt09:29
*** gokrokve has quit IRC09:33
*** tsufiev has joined #openstack-meeting-alt09:34
*** jmaron has joined #openstack-meeting-alt09:45
*** jmaron has quit IRC09:50
*** ogelbukh has quit IRC09:50
*** gokrokve has joined #openstack-meeting-alt09:59
*** ogelbukh has joined #openstack-meeting-alt10:00
*** eankutse has quit IRC10:01
*** Devioslang has quit IRC10:03
*** gokrokve has quit IRC10:08
*** ruhe has joined #openstack-meeting-alt10:11
*** ruhe has quit IRC10:27
*** pcm_ has joined #openstack-meeting-alt10:27
*** gokrokve has joined #openstack-meeting-alt10:34
*** gokrokve has quit IRC10:39
*** pcm_ has quit IRC10:45
*** pcm_ has joined #openstack-meeting-alt10:45
*** jmaron has joined #openstack-meeting-alt10:46
*** jmaron has quit IRC10:50
*** ifarkas has quit IRC11:04
*** ruhe has joined #openstack-meeting-alt11:06
*** rakhmerov1 has quit IRC11:16
*** jmaron has joined #openstack-meeting-alt11:16
*** rakhmerov has joined #openstack-meeting-alt11:16
*** flwang has joined #openstack-meeting-alt11:17
*** gokrokve has joined #openstack-meeting-alt11:35
*** gokrokve has quit IRC11:40
*** pdmars has joined #openstack-meeting-alt12:03
*** mestery has joined #openstack-meeting-alt12:20
*** anteaya has joined #openstack-meeting-alt12:20
*** ruhe has quit IRC12:25
*** resker has quit IRC12:29
*** jmaron has quit IRC12:31
*** vkmc has joined #openstack-meeting-alt12:37
*** gokrokve has joined #openstack-meeting-alt12:37
*** julim has joined #openstack-meeting-alt12:38
*** akuznetsov has quit IRC12:39
*** gokrokve has quit IRC12:41
*** akuznetsov has joined #openstack-meeting-alt12:43
*** akuznetsov has quit IRC12:46
*** harlowja_ has quit IRC12:46
*** ruhe has joined #openstack-meeting-alt12:47
*** ruhe has quit IRC12:47
*** akuznetsov has joined #openstack-meeting-alt12:49
*** jmaron has joined #openstack-meeting-alt12:53
*** dprince has joined #openstack-meeting-alt12:57
*** ruhe has joined #openstack-meeting-alt13:00
*** IgorYozhikov has quit IRC13:01
*** ruhe has quit IRC13:04
*** jmaron has quit IRC13:06
*** lblanchard has joined #openstack-meeting-alt13:06
*** gokrokve has joined #openstack-meeting-alt13:07
*** fvollero|gone is now known as fvollero13:11
*** gokrokve has quit IRC13:12
*** eankutse has joined #openstack-meeting-alt13:15
*** eankutse has quit IRC13:15
*** eankutse has joined #openstack-meeting-alt13:15
*** jmaron has joined #openstack-meeting-alt13:28
*** kevinconway has quit IRC13:29
*** kevinconway has joined #openstack-meeting-alt13:37
*** gokrokve has joined #openstack-meeting-alt13:38
*** amytron has joined #openstack-meeting-alt13:39
*** sacharya has joined #openstack-meeting-alt13:41
*** gokrokve has quit IRC13:43
*** sacharya has quit IRC13:48
*** akuznetsov has quit IRC13:50
*** akuznetsov has joined #openstack-meeting-alt13:53
*** demorris has joined #openstack-meeting-alt13:56
*** IlyaE has joined #openstack-meeting-alt13:58
*** rakhmerov has quit IRC13:58
*** jecarey has joined #openstack-meeting-alt14:01
*** amotoki has joined #openstack-meeting-alt14:06
*** gokrokve has joined #openstack-meeting-alt14:09
*** esker has joined #openstack-meeting-alt14:10
*** Barker has joined #openstack-meeting-alt14:11
*** gokrokve has quit IRC14:14
*** jergerber has joined #openstack-meeting-alt14:26
*** sacharya has joined #openstack-meeting-alt14:29
*** jmontemayor has joined #openstack-meeting-alt14:33
*** gokrokve has joined #openstack-meeting-alt14:36
*** betsy has quit IRC14:41
*** msisk has joined #openstack-meeting-alt14:50
*** akuznetsov has quit IRC14:52
*** tanisdl has joined #openstack-meeting-alt14:52
*** gkleiman has joined #openstack-meeting-alt14:53
*** gkleiman_ has joined #openstack-meeting-alt14:53
*** jrodom has joined #openstack-meeting-alt14:53
*** jrodom has quit IRC14:53
*** jrodom has joined #openstack-meeting-alt14:53
*** sarob has joined #openstack-meeting-alt14:55
*** jcoufal has quit IRC14:56
*** jodom has joined #openstack-meeting-alt15:01
*** cody-somerville has quit IRC15:01
*** jodom has quit IRC15:02
*** jodom has joined #openstack-meeting-alt15:02
*** jodom has quit IRC15:03
*** jodom has joined #openstack-meeting-alt15:04
*** jrodom has quit IRC15:04
*** kgriffs_afk is now known as kgriffs15:08
*** jmaron has quit IRC15:10
*** amotoki has quit IRC15:13
*** kgriffs has left #openstack-meeting-alt15:13
*** sarob has quit IRC15:16
*** rnirmal has joined #openstack-meeting-alt15:16
*** sarob has joined #openstack-meeting-alt15:17
*** jcoufal has joined #openstack-meeting-alt15:18
*** sarob has quit IRC15:19
*** jmaron has joined #openstack-meeting-alt15:23
*** Barker has quit IRC15:26
*** akuznetsov has joined #openstack-meeting-alt15:27
*** akuznetsov has quit IRC15:28
*** Barker has joined #openstack-meeting-alt15:28
*** beekneemech is now known as bnemec15:30
*** akuznetsov has joined #openstack-meeting-alt15:33
*** gokrokve has quit IRC15:33
*** betsy has joined #openstack-meeting-alt15:34
*** markmcclain has joined #openstack-meeting-alt15:39
*** jodom has quit IRC15:47
*** jrodom has joined #openstack-meeting-alt15:47
*** SergeyLukjanov has joined #openstack-meeting-alt15:51
*** jergerber has quit IRC15:53
*** zhiyan has joined #openstack-meeting-alt15:58
*** jrodom has quit IRC16:02
*** jrodom has joined #openstack-meeting-alt16:02
*** isviridov is now known as d16:11
*** d is now known as do16:11
*** do is now known as tests16:11
*** tests is now known as do16:11
*** dmakogon_ has joined #openstack-meeting-alt16:17
*** IlyaE has quit IRC16:18
*** gkleiman has quit IRC16:27
*** gkleiman_ has quit IRC16:28
*** markwash has quit IRC16:34
*** jrodom has quit IRC16:37
*** mugsie has joined #openstack-meeting-alt16:39
*** cody-somerville has joined #openstack-meeting-alt16:40
*** cody-somerville has joined #openstack-meeting-alt16:40
*** harlowja has joined #openstack-meeting-alt16:43
*** IlyaE has joined #openstack-meeting-alt16:44
*** vinod1 has joined #openstack-meeting-alt16:48
*** wdcd has joined #openstack-meeting-alt16:50
*** wdcd has quit IRC16:50
*** tsimmons has joined #openstack-meeting-alt16:54
*** jrodom has joined #openstack-meeting-alt16:55
*** jrodom has quit IRC16:55
*** jrodom has joined #openstack-meeting-alt16:55
*** Guest96418 has joined #openstack-meeting-alt16:56
*** IlyaE has quit IRC16:57
*** tacuddy2000 has joined #openstack-meeting-alt16:58
*** derekh has quit IRC17:01
mugsie#startmeeting designate17:01
openstackMeeting started Wed Oct 23 17:01:49 2013 UTC and is due to finish in 60 minutes.  The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: designate)"17:01
openstackThe meeting name has been set to 'designate'17:01
kiallHeya17:02
*** jodom has joined #openstack-meeting-alt17:02
*** jodom has quit IRC17:02
tsimmonshi17:02
*** jodom has joined #openstack-meeting-alt17:02
mugsiehey17:02
*** jrodom has quit IRC17:02
*** cody-somerville has quit IRC17:02
vinod1hi17:02
kiallI've not had a chance to fully catchup on last week meeting, so I've asked mugsie to run this again17:02
betsyhere17:02
mugsiewe missing anyone?17:02
vinod1artom?17:02
mugsie#topic Review action items from last week17:03
*** openstack changes topic to "Review action items from last week (Meeting topic: designate)"17:03
kiall(We've been travelling since last friday btw)17:03
msiskhere, too.17:03
mugsieSearch out any logging guidelines from other OpenStack projects (vinodmr)17:04
betsyYeah? Any place exciting?17:04
mugsienorthern ireland17:04
vinod1I haven't been able to get to it.  Will get it to it after about 2 weeks17:04
mugsiesome of our team live up there, so we decided to visit17:04
mugsievinod1: cool17:04
*** CaptTofu has joined #openstack-meeting-alt17:04
eankutseeankutse17:04
mugsie#action Search out any logging guidelines from other OpenStack projects (vinodmr) - 2 weeks17:05
* CaptTofu is here17:05
mugsieReview HP's DEBUG level logs, increase anything generally useful to INFO or above (kiall)17:05
kiallNot had a chance with travelling+visitors :(17:05
mugsie#action Review HP's DEBUG level logs, increase anything generally useful to INFO or above (kiall)17:06
mugsieUpdate APIv2 Spec with proposed RRset/Record changes (kiall)17:06
kiallI've given a quick look over during our last log review, but nothing stood out17:06
CaptTofuall my fault :)17:06
kiallSame as above I'm afraid :(17:06
mugsie#action Update APIv2 Spec with proposed RRset/Record changes (kiall)17:06
mugsieMySQL BIND9 Docs (CaptTofu)17:06
CaptTofuneed to update those been busy with travel.17:06
mugsie#action MySQL BIND9 Docs (CaptTofu)17:06
mugsieok, so most (all?) of those have been pushed to future meetings17:07
mugsieand finally17:07
mugsieUpdate domain-import-export blueprint with pro's and con's of content types (artom)17:07
kiallApologies - The whole HP DNS team has been travelling + meeting up for face to face time, so we've had little "real work" done over the last week!17:08
mugsiedid people  have a chance to look that over?17:08
mugsieor shall I push that on?17:08
eankutseDid not see updates to blueprint17:09
tsimmonsI haven't looked.17:09
mugsie#link https://blueprints.launchpad.net/designate/+spec/domain-import-export17:09
kiallYea, I'm personally in favor of using accept/content-type headers with /zones and /zones/{id}17:09
kiallrather than /zonefile/import and /zonefile/export..17:09
mugsieeankutse: there was some editing in the whiteboard area, but not a major list17:10
eankutsek. I see it17:10
mugsieif people havent had a chance, i think we should push it on17:10
vinod1#agreed17:11
mugsie#action Update domain-import-export blueprint with pro's and con's of content types (artom)17:11
betsy#agreed17:11
mugsie#topic Open Disscussion17:11
*** openstack changes topic to "Open Disscussion (Meeting topic: designate)"17:11
*** artom has joined #openstack-meeting-alt17:11
*** akuznetsov has quit IRC17:11
mugsieartom: have any update on your change?17:11
eankutseI added a couple of questions to https://wiki.openstack.org/wiki/Designate/Server_Pools17:12
mugsiemost people have not had a chance to read the blueprint, so currently it is set to come up next week17:12
mugsieeankutse: cool, I havent seen them yet, so will look this week17:12
eankutseok17:12
mugsie#action Review Server Pools questions (mugsie)17:13
eankutseI just added them about an hour ago17:13
mugsieah, thats why I missed them then :)17:14
eankutse:-)17:14
mugsieanything else?17:14
eankutsemaybe we can take just one of the questions17:14
eankutseI'ii post it here17:14
mugsieyeah17:14
eankutseIn Phase2 & 3, Async Response (202 Accepted), the current planned implementation has a "Status" field added to the Domains and Records tables in Central that is updated based on the response from the backend. How do we go about returning details of Errors if operation failed for some reason?17:15
mugsie#link https://wiki.openstack.org/wiki/Designate/Server_Pools#Questions17:15
*** markwash has joined #openstack-meeting-alt17:15
mugsieeankutse: the plan is to work like nova17:15
mugsiea GET /zone/record ... will show status = ERROR17:16
mugsieor ERROR-Schedualign / deleting etc17:16
eankutsehow about details of the error?17:16
betsyAre details in the body?17:17
kialleankutse: generally, if we accept the request, it should suceed17:17
kiallany errors are likely to be things that only the operator can fix17:17
eankutsebut they need a hint on what caused the failure17:18
eankutseso17:18
betsyRight, so they would need to know details so they could know how to fix them17:18
kiallSo, we could provide the user with lots of detail .. but it's beyond their control to fix..17:18
eankutseok.17:18
artomSurely the more information, the better?17:18
artomWithout necessarily giving them stacktraces and such.17:19
eankutseSo you mean that user errors (including validation errors) will have been caught before now?17:19
mugsieeankutse: yes17:19
kiallIdeally, all user-caused and user-fixable errors should be caught before accepting the request at all17:19
*** jcoufal has quit IRC17:19
betsyI didn't think that was true with saync calls17:19
kiallFor example - Would you want nova to say "error scheduling vm - no capacity available" to end users? I'm guessing no :)17:19
betsy*async17:19
kiallIt's also something an end user can't fix17:19
mugsiebetsy: it is, we do all the checks to ensure it can be created before we put it in the queue to be created17:20
mugsie / updated / deleted /etc17:20
mugsiethis just fits where the backend currently sits, after all the checks have been done17:20
*** RajeshMohan has joined #openstack-meeting-alt17:20
*** SergeyLukjanov has quit IRC17:21
vinod1What action can the user take after an error?  The normal behavior on an error - especially one that you do not understand is to retry17:21
betsyNot if it's something like invalid domain name17:21
vinod1So at least the error message should indicate what action the user can take - report the error to admins and wait for problem to be resolved?17:22
mugsiebetsy: which would have returned a 400 error to the user17:22
kiallvinod1: correct, the user should retry. If a zone/record/etc makes it into an "ERROR" state, something has gone wrong that is outside of the users control.17:22
betsyBut a 400 with detail -- invalid domain name17:22
mugsievinod1: if you look at how nova reprts issues with cvreating instances, it only give a very basic indication of what happened17:22
mugsiebetsy: yes17:22
kiallbetsy: yea, the 400 with details happens before the request is accepted and placed into the async queue17:23
vinod1In those kind of errors when you get into an error state - would a retry help?17:23
mugsieit could17:23
mugsiesay if the backend had a failuer, and the quiry expired17:23
mugsieand then had to be retried17:23
kiallvinod1: that depends on the issue, say the async action is finally being run, and the database server is down.. It's going to fail and the zone will end up in an ERROR state.17:24
kiallRetrying, as an end user, makes sense here.. there waiting for your failover and/or staff to fix the DB (or whatever else is broken)17:24
kiallIf the user provides bad input, that request will be rejected with a 400 containing some details, and will never make it into the queue at all17:25
mugsieeankutse: does that answer the question?17:26
eankutsehmmm…yes17:27
mugsieanything else, just chuck it into that question section17:27
eankutseNext one...17:27
eankutseIn Phase2 & 3, Async Response (202 Accepted), we should consider returning Location Header that points to the URL of the resource (that is being created). The user can check the status of the operation using this17:27
mugsieeankutse: yeap, it should17:28
*** jprovazn has joined #openstack-meeting-alt17:28
mugsiei thought I documented it to say it did17:28
mugsie but it seems i didnt17:28
eankutsemaybe I missed it.17:28
mugsieno, just checked, I never actually wrote it17:29
mugsie(sorry)17:29
eankutseI know we mentioned that the use will hvae to call GET /domain.id17:29
mugsieyeah17:29
eankutsek. One more that is just remotely related...17:30
eankutseNot directly related to achieving Async but should we consider following recommendations from http://docs.openstack.org/api/openstack-compute/2/content/LinksReferences.html and add "self" and "bookmark" links in the final response body after the resource is available?17:30
mugsiei think we have that in the API v2 spec17:30
eankutsek. Cool :-)17:30
mugsiethaty all responces will have a links section with rel=self etc17:31
mugsiecool17:31
mugsieanything else from anyone?17:31
mugsiegoing once17:31
eankutsenot for me17:31
vinod1none from me17:32
betsyI'm good17:32
tsimmonsI'm good.17:32
kiallNot from me :)17:32
mugsiecool, thanks everyone17:32
eankutsebye17:32
artomWait, was that the call for open discussion?17:32
mugsieif you think of anything during the week just dump it on the agenda!17:32
mugsieyup :)17:33
artomDoh.17:33
mugsiehave something?17:33
artomTwo semi-related things.17:33
mugsiecool, go for it17:33
artomDoes https://blueprints.launchpad.net/designate/+spec/multi-backend depend on pools? Or can it be started in parallel?17:33
*** dukhlov has quit IRC17:34
mugsieyup17:34
kiallmulti-backend was more about writing changes to 2 backends at once17:34
*** dukhlov has joined #openstack-meeting-alt17:34
*** lblanchard has quit IRC17:34
artomYou answered 'yup' to an 'or' question - while logically that's sound, I need to know what half of the 'or' you're agreeing with ;)17:35
*** fvollero has quit IRC17:35
kiallAt HP, we write certain changes (create/delete zone) to multiple places..17:35
mugsieartom: as it turns out i was wrong - yes, it can be started with out pools17:35
kiallThe idea was for to take the code we have there, and make it generic enough to write changes to any 2 backends at once17:35
eankutseusing one scheduler?17:36
mugsiethis is independant of schedualers17:36
mugsiethis is the same records being writen]17:37
mugsieto btoth backends17:37
mugsieboth*17:37
eankutsek17:37
kialleankutse: when a zone is created on HP Cloud, we create it in PowerDNS as usual, but ALSO need to create it at one of our partners17:37
eankutseok17:37
tsimmonsSo essentially sending a duplicate message to two different places?17:38
mugsietsimmons: yes17:38
artomI might pick up that bp, pending discussions around here. But good to know it can happen before pools.17:38
mugsieartom: cool.17:38
mugsieyou had a second thing artom?17:39
artomSecond thing: a NSD-slave backend that depends on 1. multiple backends and 2. a PowerDNS backend17:39
*** SergeyLukjanov has joined #openstack-meeting-alt17:40
artomThe idea would be that the NSD-slave backend would only send remote control commands to a NSD server that would then AXFR from the PowerDNS server.17:40
artomSo it would be a mutant backend that doesn't actually store anything, and depends on another backend.17:40
artomWould that be acceptable?17:40
mugsieyeah, log a blueprint for it17:41
artomAh, right, so discussion can take place there.17:41
kiallYea - I think that needs some thought :)17:42
mugsiewell, just so the detaisl can be knocked out beter#17:42
mugsiedetails17:42
*** tsimmons has left #openstack-meeting-alt17:42
mugsiecan't type today :(17:42
mugsiebut in general, sounds grand17:42
artomSure, grand :)17:43
mugsiewe good to finish up everyone?17:43
* artom is good.17:43
mugsiethanks everyone!17:44
eankutsethx17:44
mugsie#endmeeting17:44
*** openstack changes topic to "OpenStack meetings (alternate)"17:44
openstackMeeting ended Wed Oct 23 17:44:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-10-23-17.01.html17:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-10-23-17.01.txt17:44
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-10-23-17.01.log.html17:44
*** jmcbride has joined #openstack-meeting-alt17:44
*** vinod1 has quit IRC17:53
*** mugsie has left #openstack-meeting-alt17:53
*** IlyaE has joined #openstack-meeting-alt17:54
*** vinod1 has joined #openstack-meeting-alt17:58
*** arborism has joined #openstack-meeting-alt18:00
*** jmcbride1 has joined #openstack-meeting-alt18:01
*** arborism is now known as amcrn18:02
*** jmcbride has quit IRC18:03
*** jmcbride has joined #openstack-meeting-alt18:04
*** jmcbride1 has quit IRC18:06
*** SergeyLukjanov has quit IRC18:07
*** msisk has left #openstack-meeting-alt18:10
*** sarob has joined #openstack-meeting-alt18:12
*** sarob has quit IRC18:12
*** SergeyLukjanov has joined #openstack-meeting-alt18:13
*** sergmelikyan has quit IRC18:19
*** slagun_ has quit IRC18:19
*** vinod1 has quit IRC18:31
*** tacuddy2000 has quit IRC18:33
*** lblanchard has joined #openstack-meeting-alt18:34
*** harlowja has quit IRC18:40
*** dprince has quit IRC18:40
*** harlowja has joined #openstack-meeting-alt18:50
*** nadya has joined #openstack-meeting-alt18:54
*** sarob has joined #openstack-meeting-alt19:05
*** zhiyan has quit IRC19:06
*** ashestakov has joined #openstack-meeting-alt19:12
*** jmcbride1 has joined #openstack-meeting-alt19:12
*** jmcbride1 has quit IRC19:13
*** jmcbride1 has joined #openstack-meeting-alt19:13
*** jmcbride has quit IRC19:14
*** CaptTofu has quit IRC19:30
*** IlyaE has quit IRC19:32
*** cody-somerville has joined #openstack-meeting-alt19:33
*** sarob has quit IRC19:36
*** KennethWilke has joined #openstack-meeting-alt19:38
*** amcrn is now known as [a]mcrn19:39
*** Barker has quit IRC19:42
*** cweid has joined #openstack-meeting-alt19:42
*** Barker has joined #openstack-meeting-alt19:43
*** gokrokve has joined #openstack-meeting-alt19:44
*** IlyaE has joined #openstack-meeting-alt19:47
*** jmaron has left #openstack-meeting-alt19:48
*** robertmyers has joined #openstack-meeting-alt19:51
*** grapex has joined #openstack-meeting-alt19:53
*** jtomasek has quit IRC19:54
*** nadya has quit IRC19:58
cp16netbuller?20:00
cweido/20:01
*** NehaV has joined #openstack-meeting-alt20:01
hub_caphai20:01
hub_cap#startmeeting trove20:01
openstackMeeting started Wed Oct 23 20:01:40 2013 UTC and is due to finish in 60 minutes.  The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: trove)"20:01
openstackThe meeting name has been set to 'trove'20:01
KennethWilkehello20:01
robertmyerso/20:01
kevinconway0/20:01
dmakogon_щ.20:01
ashestakovhi20:01
dmakogon_o/20:01
cp16net0^/20:01
*** imsplitbit has joined #openstack-meeting-alt20:01
*** datsun180b has joined #openstack-meeting-alt20:01
imsplitbito/20:02
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting20:02
datsun180bhere here20:02
hub_cap#link http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-10-16-20.00.html20:02
grapexo/20:02
hub_cap#topic action items20:02
*** openstack changes topic to "action items (Meeting topic: trove)"20:02
hub_capgrapex: BUILDING_ERROR_DNS20:02
pdmarso/20:02
dohi everybody20:02
*** jcru has joined #openstack-meeting-alt20:02
hub_capgrapex to fix issue where instances in BUILDING_ERROR_DNS cannot be deleted.20:02
*** rnirmal_ has joined #openstack-meeting-alt20:02
grapexhub_cap: Argh! I didn't quiet finish this- I will soon. Sorry!20:02
*** rnirmal_ has quit IRC20:03
hub_capdo u have status on that grapex?20:03
vipulo/20:03
kevinconwaygrapex: did you do anything to finish that?20:03
[a]mcrno/ (until 13:30)20:03
*** rnirmal_ has joined #openstack-meeting-alt20:03
grapexhub_cap: I didn't do much of it yet, sorry.20:03
hub_capsorry grapex i didnt see your update20:03
imsplitbitgrapex: do you think the timeline is realistic20:03
hub_capdoh20:03
*** redthrux has joined #openstack-meeting-alt20:03
*** pcm_ has quit IRC20:03
hub_capok so do u want me to keep it in grapex for next wk?20:04
grapexhub_cap: I do.20:04
*** [a]mcrn is now known as amcrn20:04
hub_cap#action grapex to fix issue where instances in BUILDING_ERROR_DNS cannot be deleted.20:04
grapexhub_cap: I'll be sure to do that before next week. Thanks!20:04
*** rnirmal has quit IRC20:04
*** rnirmal_ is now known as rnirmal20:04
hub_capok lets move on20:04
hub_capdatsun180b to add backup status updates to conductor20:04
cp16netlets do20:04
*** artom has left #openstack-meeting-alt20:04
hub_capdo u have updates for that datsun180b?20:05
*** demorris has quit IRC20:05
datsun180bgerrit review added backups to conductor this morning. do you know what your other two wishes are?20:05
kevinconwaydatsun180b: do you have code?20:05
imsplitbitdatsun180b: please do update us20:05
*** ashestakov has quit IRC20:05
*** do is now known as isviridov20:05
hub_caplulz20:06
cp16net<320:06
hub_capok so moving on?20:06
datsun180bworking on adding robertmyers' suggestions through real-mode tests presently, i'll append a new review when those clear20:06
dmakogon_нгз20:06
dmakogon_yup20:06
*** yogeshmehra has joined #openstack-meeting-alt20:06
*** vinod1 has joined #openstack-meeting-alt20:06
hub_cap#topic conductor support20:07
*** openstack changes topic to "conductor support (Meeting topic: trove)"20:07
datsun180bwell if it was an action then i don't know that it needs to be a topic too20:07
*** esp has joined #openstack-meeting-alt20:07
robertmyersdatsun180b: good work20:07
hub_capdatsun180b: link your reviews20:07
datsun180b#link https://review.openstack.org/#/c/45116/20:08
hub_capok so status is waiting for reviews eh?20:08
datsun180bi'll abandon the other once since the two pieces are now fused20:08
*** SergeyLukjanov is now known as _SergeyLukjanov20:08
hub_capoh man20:08
hub_capmaybe we should make them dependent commits on each other20:09
datsun180bnope, abandoned20:09
hub_capthats a topic i need to gain more clarity on20:09
*** _SergeyLukjanov has quit IRC20:09
hub_capdukhlov: has an issue with a huge commit20:09
vipuldatsun180b: Do you think we should completely remove the sql_connection string in the conf?20:09
hub_capand we need to find a way to split them better, and i think this is another case of that datsun180b20:09
vipuldatsun180b: If we are sure that we don't need db anymore -- we should do that20:09
grapexhub_cap: I'd like to discuss it at some point. I think we should tiny commits with one idea each, but they shouldn't be so small they are dependent on each other.20:09
hub_capgrapex: yes can u add it to the agenda (breaking up commits)20:10
datsun180bvipul: worth adding that to the review i'd say, but i'll agree when conductor isn't optional20:10
vipuldatsun180b oh so you have made it optional20:10
datsun180bi tried splitting the conductor work up earlier, and it kind of didn't go anywhere so today i figured i'd just stack the backups stuff on top and get it all done in one swipe20:11
robertmyersif we make it not optional that would clean it up a lot20:11
dmakogon_robertmyers, yes20:11
datsun180bthe backups needed to be redone so conductor _could_ do the work20:11
* hub_cap is confused... its optional?20:11
dmakogon_that is why it should be done20:11
*** vinod1 has quit IRC20:11
grapexvipul: is making it optional as important if it completely replaces guest agent communication to the db in one fell swoop?20:11
dmakogon_because we have huge refactoring coming20:11
datsun180bhub_cap: by request it was, because in rev1 it didn't completely sever the db tie20:12
*** sacharya has quit IRC20:12
*** vinod1 has joined #openstack-meeting-alt20:12
grapexvipul: Previously I had issues as I felt pushing conductor would force anyone using the reference agent to use both conductor as well as allowing db access from the agent20:12
vipulgrapex: No.. I think if we catch everything then I am ok with it not being optional20:12
grapexvipul: Cool.20:12
*** vinod1 has left #openstack-meeting-alt20:12
robertmyerslets do it then20:12
hub_cap#action conductor is no longer optional20:12
*** SergeyLukjanov has joined #openstack-meeting-alt20:12
vipulso just as a side though20:12
hub_cap#undo20:13
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x1765d10>20:13
vipulwe've run nova-network in multi-host.. we had to disable nova-conductor20:13
vipulbecause it couldn't keep up with the status updates20:13
datsun180byeah making it not optional isn't tough20:13
hub_cap#action datsun180b to make conductor no longer optional20:13
hub_capvipul: thats not a very nice bug :o20:13
datsun180bespecially compared to refactoring backups mid-change without breaking my stride20:13
datsun180b>:C20:13
*** saurabhs has joined #openstack-meeting-alt20:13
*** demorris has joined #openstack-meeting-alt20:14
hub_capvipul: so we have a issue where a deployed conductor started choking right, the nova conductor?20:14
*** ashestakov has joined #openstack-meeting-alt20:14
grapexvipul: In that case, I know it could be considered cruft but maybe we should keep using it optional for awhile20:15
hub_capmaybe that means we should deploy >1 conductor  in a given topic, eh?20:15
vipulhub_cap: Yes.. so if we feel confident the same won't happen with trove-conductor then i'm ok with making it required20:15
vipulbut it's a insurance policy in case20:15
grapexvipul: I like insurance. :)20:15
hub_capvipul: is nova-conductor disabled?20:15
vipulhub_cap: That's an option.. it really depends on how many guests you have20:15
hub_capor just on a per-host20:15
grapexI vote we keep it optional for now until we have more data on its real world behavior.20:16
robertmyershow often are the heart beats?20:16
hub_capi believe the "insecure" way for nova-conductor was to put it on each host20:16
vipul90 seconds maybe20:16
datsun180brobertmyers: ~1minute?20:16
datsun180bmaybe 90 seconds20:16
vipulhub_cap: yep, then it defeats the purpose of conductor which was no db access to other things20:16
hub_capvipul: well somewhat20:16
hub_capif u get root access to the vm u still dont ahve db access unless u can get on the host20:17
hub_capor craft msgs, knowing the uuid's of other guests20:17
kevinconwayrobertmyers: the guests should just send a message when they die20:17
kevinconwayletting everyone know that it died20:17
kevinconwaysounds simple20:17
robertmyersdead simple20:17
hub_capkevinconway: lol20:17
grapexkevinconway: It would look like "{ 'method':'death', 'args', 'aarggggggghhhhh'}"20:17
datsun180bwell what if it sends the swansong 90 seconds before it dies20:17
espkevinconway: like a suicide letter?20:17
datsun180bthat way we'll know ahead of time20:18
hub_cap'message': 'i regret nothing'20:18
grapexesp: That's even better20:18
vipullol esp20:18
hub_capok srsly though20:18
datsun180bespecially if it's for an unpredicted reason or a kp or segfault or something20:18
hub_capim ok w/ making conductor disable'able20:18
hub_capbut the thing that scares me is that if its disable-able20:18
vipuldatsun180b, grapex: i say we make it optional for v120:18
hub_capthat means everyone will disable it20:18
hub_capand bugs wont ever get fixed20:18
vipullet's enable it in gate20:18
datsun180bhooray, less work for me20:18
hub_capif it requires u to put it on every host, like nova-conductor20:18
hub_capthen its obvi that there is an issue20:19
*** demorris has quit IRC20:19
*** sacharya has joined #openstack-meeting-alt20:19
vipulwe can deprecate it in 'J'20:19
hub_capdeprecate what? the old comm layer? in J /20:20
hub_cap?20:20
vipulthe optional flag20:20
grapexvipul: Hmm- there were some things, like scheduled backups, that depended on this though. :(20:20
hub_capor we can make it non optional20:20
hub_capand make u do the _exact_ same thing u have to do anywya for nova-conductor20:21
*** jecarey has quit IRC20:21
hub_capand since its running in your env  you have a reason to try to fix it20:21
datsun180buse_conductor is defaulted to True in cfg.py fyi20:21
hub_caprather than leaving it disabled ;)20:21
vipulfair enough.. the only thing with that is it'll be another thing that has to run alongside guest20:21
hub_capwhat scares me vipul20:21
*** demorris has joined #openstack-meeting-alt20:21
hub_capis that a 3rd thing will come along which needs db acces20:22
hub_capthen we have to build 2x ways to talk to the db for that _thing_20:22
hub_capbecause its optional20:22
vipulSure yea it'll be a headache to support all these code paths20:22
hub_capso we deal w/ the fact that we have a known issue and have 1 logic path20:23
hub_capand spend cycles fixing it rather than spend cycles on building the next thing w/ 2 db paths20:23
datsun180bi'm all for stamping out the "guest agent can just update the host db" idea forever20:24
vipulsure - It may be the case that we have a lot less traffic going to conductor.. and it may not cause issues like it does for nova20:24
datsun180bso if anyone suggests a new feature that uses it we can all exchange sidelong glances and knowing smiles20:24
vipulwe just gotta be careful it doesn't become the sink for every db request20:25
hub_capok we are almost 30 min in on this subject20:25
datsun180bi thought its whole point was to be the sink20:25
*** eankutse has quit IRC20:25
vipulFor the Guest Agent.. possibly.. since it doesn't do a whole lot anyway with the DB20:25
hub_capthe agent shouldnt _need_ db access to read20:26
hub_capit should be passed wht it needs20:26
hub_capif it needs to update the db it uses conductor20:26
hub_capfor now20:26
datsun180bright, it should be the sink for GAs access to the db20:26
hub_capfor GA writes to the db20:26
hub_capfor GA reads, we pass in the info it needs20:26
datsun180b^^ captured in my changes to backup's process fyi20:27
vipulok works for me20:27
*** jmcbride1 has quit IRC20:27
hub_capok so non-optional vipul?20:27
imsplitbitgo!20:27
vipulsure -- we'll be sure to test it out20:27
hub_capheh ya :)20:27
hub_capok moving on20:28
hub_cap#topic Tempest for integration tests20:28
*** openstack changes topic to "Tempest for integration tests (Meeting topic: trove)"20:28
hub_capso this was on last wk20:28
hub_capbut i dont think it was discussed20:28
hub_capwith clarkb and co we defined a way to preseed the nodes with the needed stuff for diskimage builder20:28
*** demorris has quit IRC20:29
hub_capthen devstack can build the images easier / faster20:29
dmakogon_hub_cap, could we use heat-jeos for images ?20:29
dmakogon_hub_cap, it is official part of heat20:29
hub_capthen we can run those w/ tempest tests after devstack uploads them20:29
hub_capdmakogon_: if heat-jeos uses dib then yes20:29
hub_capdib is waht we use20:29
hub_caphttp://docs.openstack.org/developer/heat/getting_started/jeos_building.html20:30
hub_capdiskimage-builder/bin/disk-image-create vm fedora heat-cfntools -a amd64 -o fedora-heat-cfntools20:30
hub_capcorrect dmakogon_: that tutorial uses dib20:30
hub_capthis is what weve done since the beginning of dib20:30
*** eankutse has joined #openstack-meeting-alt20:30
dmakogon_hub_cap, i will start ML thread for this20:30
hub_capdmakogon_: why?20:31
hub_capwe know what we are doing20:31
hub_capwhat do u need to discuss?20:31
dmakogon_hub_cap, i think we nee several options20:31
hub_capnope not for testing20:31
hub_capyou can do whatever u want dmakogon_ in production20:31
*** demorris has joined #openstack-meeting-alt20:31
dmakogon_k20:31
hub_capthis topic is specific for tempest testing (see the topic change above)20:31
*** jecarey has joined #openstack-meeting-alt20:32
dmakogon_i know20:32
hub_capso this will be useful for the old tests (the ones run by jenkins) and the new ones (tempest)20:32
dmakogon_any updates with trove framework ?20:32
hub_capwith respect to testing?20:32
*** eankutse1 has joined #openstack-meeting-alt20:33
dmakogon_yes20:33
hub_capnope we dont need to test it20:33
hub_capim sorry20:33
hub_capwe dont neec to change it to test20:33
hub_capmoving on? other questions?20:33
dmakogon_hm, could you describe your plans for tempest and trove20:34
dmakogon_please20:34
hub_capdemorris: around?20:34
hub_capdmakogon_: plans are well known, i descibed them above20:34
hub_capbut i will write up a wiki article explaining20:34
dmakogon_hub_cap, thanks20:34
hub_cap#action write up wiki article wrt testing + tempest + trove20:34
hub_cap#totpic Blueprint Rigor / Structure20:34
hub_caplol totpic20:34
hub_cap#topic Blueprint Rigor / Structure20:34
*** openstack changes topic to "Blueprint Rigor / Structure (Meeting topic: trove)"20:35
*** eankutse has quit IRC20:35
hub_capso demorris has brought to attention the lack of details on some of our blueprints20:35
hub_capand possibly that we come up with a base structure for them, so that we dont get 1 line blueprints that really do a terrible job at describing things20:35
hub_capso i agree that we (the people on teh bug triage team) need to better triage this20:36
*** demorris has quit IRC20:36
hub_capi also think that we need to be blueprinting early rather than creating a blueprint after we finish the code20:36
hub_capbox20:37
hub_capjust as a check bo20:37
dmakogon_agreed20:37
*** demorris has joined #openstack-meeting-alt20:37
hub_capso the bug triage team needs to do better work here20:37
hub_capcuz i dont think we have a bug triage team if i look @ the "new" bugs in trove20:37
vipulhub_cap: yup agree with evyerthing you said20:37
grapexhub_cap: True, but will a lack of blueprints some time before code is finished mean completed code can't be checked in? What in the case of tinier items?20:37
hub_cap37 New bugs20:37
hub_capgrapex: everythign needs a blueprint20:38
hub_capjk20:38
hub_capi thik we can relax rules on blueprints sometimes20:38
hub_capif its a VERY small change, and not pertaining to a bug20:38
hub_capi think its ok to not have a blueprint20:38
grapexFor example, if someone is looking at the code and finds a small thing they can fix, I'd rather they make a tiny blue print for it rather than list it as a bug.20:38
demorrishub_cap: sorry, my wireless is spotty on the ride back to Austin, I take it we are talking about my BP topic20:38
grapexhub_cap: Ok, no blue print for those cases is even better. :)20:38
hub_capdemorris: we were ;)20:38
kevinconwayso if i have a cool idea i want someone else to do, can i make a blueprint?20:38
hub_capjk demorris but we have spoke a lot about it20:38
hub_capkevinconway: hell yes u can20:39
hub_capand should20:39
demorrisk, i could drop at any moment, but I will try to contribute while I am connected20:39
hub_capdemorris: i covered it from your perspective i think20:39
vipulone other point.. is we discuss any blueprints in IRC, the author shoudl be responsible for capturing the decision points and writing them up in teh BP20:40
hub_cap++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++20:40
hub_capthats to vipul ^ ^20:40
hub_capotherwise t hey will have to deal with us asking the same questions over and over hehe20:41
vipulI have a hard time keeping up with eveything we've talked about.. so it'll make it easier at review time20:41
hub_cap#action bug triage team to police blueprints better20:42
*** demorris_ has joined #openstack-meeting-alt20:42
hub_capok time to move on!!20:42
cp16netdo it!20:43
hub_cap#topic Datastore types20:43
*** openstack changes topic to "Datastore types (Meeting topic: trove)"20:43
hub_capashestakov:  ^ ^ go!20:43
*** demorris has quit IRC20:43
*** demorris_ is now known as demorris20:43
ashestakovguys, review it pls, i know there are lot of changes, but it already blocker for another things20:44
hub_capashestakov: plz link the reviews20:44
hub_capjust so we can see them20:44
hub_cap#link them20:44
jodomashestakov: is the blueprint up to date with the current implementation?20:44
ashestakov1 min, im from another pc20:44
ashestakovjodom, not at all20:44
ashestakovit contains no new updates20:45
jodomashestakov: ok, perhaps i need to go read through the mailing list thread to see where we landed based on grapex's feedback.20:45
demorrisi believe the API changed a bit, so it would be helpful to see that updated on the core BP20:46
hub_cap++20:46
jodom+120:46
ashestakovhttps://review.openstack.org/#/c/47936/ cli20:46
demorrisnot that I am opposed to anything specific, just want to see the holistic spec20:46
ashestakovhttps://review.openstack.org/#/c/47934/20:46
ashestakovhub_cap: can you share link to my gist with doc draft?20:47
hub_capyes sec20:47
hub_capcrap i closed your gist ashestakov20:48
hub_capashestakov: fwiw, make your gists public20:48
ashestakovlet me recover it20:48
kevinconwayalso, to anyone making gists: please make the text fit in the box20:48
hub_cap++ kevinconway20:49
ashestakovhttps://gist.github.com/andreyshestakov/657d7cb0528092f4c6e920:49
demorrisdid we settle on the topic around nesting versions with a datastore type?  And also the issue around GUID's for types vs. just string names?20:49
ashestakovthis draft20:49
hub_capashestakov: plz update to put in the wiki :)20:49
*** eankutse has joined #openstack-meeting-alt20:49
hub_capand make your gists public ;)20:49
datsun180buse #link for your links pretty please20:49
grapexashestakov: I find gists harder to follow than the ML20:49
kevinconwayand fit in the box20:49
ashestakovwill do, once finish20:49
hub_caplike this hehe20:50
hub_caphttps://gist.github.com/hub-cap?page=1020:50
hub_capok so we moving on?20:50
*** eankutse1 has quit IRC20:50
hub_capill tkae that as a yes!20:51
demorriswell, I am still not sure of the status...20:51
hub_capdemorris: status is that there are revies20:51
hub_cap*reviews20:51
demorriswhats left on this one, the review is in, there are a few outstanding comments20:51
ashestakovdemorris, now it supports names and uuids20:51
demorrisand we want the wiki BP updated20:51
grapexdemorris: I'm updating my review of it with a few more issues20:51
grapexMinor stuff20:52
demorrisgrapex: okay20:52
hub_capdemorris: so its still in flight more or less20:52
grapexThough there are currently no tests associated with the PR20:52
ashestakovanything else except minor stuff?20:52
demorrisso maybe in the next day we could be done talking about this one :)20:52
hub_capashestakov: i htink its all minor at this point20:52
hub_capdemorris: feel free to review the code ;)20:52
hub_capyogeshmehra do we need to talk about "multiple node templates"20:53
hub_capim not sure if that was from last wk20:53
ashestakovif only minor staff left, i can fix it even today20:53
yogeshmehrayes...20:53
yogeshmehrahello...20:53
demorrisoh I have browsed it…i think ashestakov has done a great job20:53
hub_capyogeshmehra: did u discuss that last wk? or is that a new item?20:54
demorrisi am not going to get in the business of reviewing y'alls code…I'll stick to spec's and BP's for now :)20:54
hub_cap#topic Multiple Node templates20:54
*** openstack changes topic to "Multiple Node templates (Meeting topic: trove)"20:54
yogeshmehrahub_cap:this is new item20:54
hub_capok go yogeshmehra20:54
dmakogon_nice topic20:54
dmakogon_i like it20:54
yogeshmehra:-)20:54
dmakogon_(facebook like)20:54
dmakogon_;)20:54
yogeshmehracurrent trove/heat integration even with the externalization is incomplete..20:55
yogeshmehrasome maintenance of the stack within trove....topics like this are pending even before we get into clustering/replication20:55
dmakogon_yogeshmehra, could you describe bottlenecks ?20:56
yogeshmehrawill the guestagent be running on all nodes...20:56
dmakogon_yogeshmehra, what kind of problems do we have ?20:57
dmakogon_yes20:57
yogeshmehrawould there be multiple prepare msgs posted for each of the nodes from task manager20:57
dmakogon_yes20:57
dmakogon_i suppose20:57
vipulcurrently we don't keep track of the multiple nodes in Trove20:57
yogeshmehrai went through: https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API20:57
dmakogon_vipul, because we don't have 220:57
vipuldo we keep track of the stack id?20:57
imsplitbityogeshmehra: thank you!20:58
dmakogon_no20:58
dmakogon_vipul, no20:58
vipulso how do we do things against the 'stack'?20:58
vipuland what are things that shoudl be done against the 'stack' through heat vs. directly through Nova20:58
dmakogon_creating instance/volume - that is all20:58
yogeshmehradmakogon_: no for>20:58
yogeshmehrano for?20:58
vipulwhat about restart / resize,e etc20:58
hub_cap2 minutes20:58
dmakogon_vipul, doing it with nova20:59
vipulthat breaks down when you have >1 instance no?20:59
dmakogon_vipul, heat only creates stack20:59
dmakogon_vipul, somehow20:59
yogeshmehradmakogon_: along with instances...20:59
yogeshmehrahow does the framework take care of multiple nodes getting "prepare"d21:00
vipulprobably need to continue in #openstack-trove21:00
kevinconwayor ML21:00
hub_capyes vipul21:00
dmakogon_ML would be great21:00
hub_capML ftw21:00
hub_cap#endmeeting21:00
*** openstack changes topic to "OpenStack meetings (alternate)"21:00
openstackMeeting ended Wed Oct 23 21:00:53 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-10-23-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-10-23-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-10-23-20.01.log.html21:00
yogeshmehrahub_cap: beyond clustering api doc...do we have a design wiki as well...on trove...21:01
yogeshmehra?21:01
hub_capyogeshmehra: plz move to #openstack-trove21:01
yogeshmehrasure..21:01
*** esp has left #openstack-meeting-alt21:02
*** ashestakov has left #openstack-meeting-alt21:03
*** jprovazn has quit IRC21:03
*** cweid has left #openstack-meeting-alt21:05
*** lblanchard has quit IRC21:07
*** pdmars has quit IRC21:10
*** eankutse has quit IRC21:12
*** datsun180b has left #openstack-meeting-alt21:12
*** Guest96418 has left #openstack-meeting-alt21:15
*** jergerber has joined #openstack-meeting-alt21:15
*** IlyaE has quit IRC21:16
*** imsplitbit has left #openstack-meeting-alt21:19
*** demorris has quit IRC21:21
*** julim has quit IRC21:26
*** saurabhs has left #openstack-meeting-alt21:30
*** jmontemayor has quit IRC21:33
*** IlyaE has joined #openstack-meeting-alt21:33
*** betsy has quit IRC21:34
*** jmcbride has joined #openstack-meeting-alt21:41
*** jmcbride has quit IRC21:54
*** dmakogon_ has quit IRC21:58
*** esker has quit IRC21:58
*** SergeyLukjanov is now known as _SergeyLukjanov22:02
*** _SergeyLukjanov has quit IRC22:02
*** NehaV has left #openstack-meeting-alt22:03
*** yogeshmehra has quit IRC22:05
*** Barker has quit IRC22:06
*** lsmola has quit IRC22:08
*** sacharya has quit IRC22:15
*** robertmyers has quit IRC22:15
*** amytron has quit IRC22:33
*** SergeyLukjanov has joined #openstack-meeting-alt22:41
*** rnirmal has quit IRC22:43
*** openstack has joined #openstack-meeting-alt22:47
*** ChanServ sets mode: +o openstack22:47
*** KennethWilke has quit IRC22:56
*** grapex has quit IRC23:15
*** jergerber has quit IRC23:23
*** sacharya has joined #openstack-meeting-alt23:27
*** jrodom has joined #openstack-meeting-alt23:28
*** jrodom has quit IRC23:28
*** julim has joined #openstack-meeting-alt23:29
*** jodom has quit IRC23:32
*** jcru has quit IRC23:32
*** julim has quit IRC23:33

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