Wednesday, 2013-10-09

*** colinmcnamara has quit IRC00:01
*** colinmcnamara has joined #openstack-meeting-alt00:02
*** kebray_ has joined #openstack-meeting-alt00:04
*** kebray_ has quit IRC00:05
*** julim has quit IRC00:05
*** kebray has joined #openstack-meeting-alt00:05
*** colinmcnamara has quit IRC00:06
*** markwash has quit IRC00:29
*** __nikhil__ has joined #openstack-meeting-alt00:51
*** demorris has joined #openstack-meeting-alt00:57
*** sarob_ has joined #openstack-meeting-alt00:59
*** amytron has joined #openstack-meeting-alt00:59
*** noslzzp has joined #openstack-meeting-alt01:00
*** amytron has quit IRC01:02
*** sarob has quit IRC01:02
*** amytron has joined #openstack-meeting-alt01:03
*** sarob_ has quit IRC01:03
*** amytron has quit IRC01:09
*** amytron has joined #openstack-meeting-alt01:10
*** amytron has quit IRC01:19
*** demorris has quit IRC01:20
*** amytron has joined #openstack-meeting-alt01:20
*** jrodom has joined #openstack-meeting-alt01:21
*** amytron has quit IRC01:29
*** amytron has joined #openstack-meeting-alt01:30
*** tanisdl has joined #openstack-meeting-alt01:33
*** amytron has quit IRC01:33
*** tanisdl has quit IRC01:33
*** noslzzp has quit IRC01:34
*** rev has left #openstack-meeting-alt01:34
*** amytron has joined #openstack-meeting-alt01:35
*** amytron has quit IRC01:41
*** amytron has joined #openstack-meeting-alt01:41
*** amytron has quit IRC01:43
*** amytron has joined #openstack-meeting-alt01:44
*** amytron has quit IRC01:50
*** amytron has joined #openstack-meeting-alt01:51
*** yidclare has quit IRC01:52
*** amytron has quit IRC01:52
*** amytron has joined #openstack-meeting-alt01:54
*** amytron has quit IRC01:55
*** amytron has joined #openstack-meeting-alt01:57
*** amytron has quit IRC02:07
*** amytron has joined #openstack-meeting-alt02:07
*** jrodom has quit IRC02:09
*** amytron has quit IRC02:09
*** amytron has joined #openstack-meeting-alt02:10
*** amytron has quit IRC02:19
*** amytron has joined #openstack-meeting-alt02:20
*** amytron has quit IRC02:21
*** amytron has joined #openstack-meeting-alt02:23
*** amytron has quit IRC02:29
*** amytron has joined #openstack-meeting-alt02:30
*** amytron has quit IRC02:41
*** amytron has joined #openstack-meeting-alt02:43
*** sarob has joined #openstack-meeting-alt02:46
*** amytron has quit IRC02:46
*** amytron has joined #openstack-meeting-alt02:47
*** sarob has quit IRC02:48
*** sarob has joined #openstack-meeting-alt02:49
*** sarob_ has joined #openstack-meeting-alt02:51
*** amytron has quit IRC02:51
*** amytron has joined #openstack-meeting-alt02:52
*** sarob has quit IRC02:53
*** amytron has quit IRC02:54
*** amytron has joined #openstack-meeting-alt02:55
*** sarob_ has quit IRC02:59
*** amytron has quit IRC02:59
*** sarob has joined #openstack-meeting-alt03:00
*** amytron has joined #openstack-meeting-alt03:00
*** sarob has quit IRC03:04
*** bdpayne has quit IRC03:04
*** bdpayne has joined #openstack-meeting-alt03:05
*** bdpayne has quit IRC03:05
*** amytron has quit IRC03:07
*** amytron has joined #openstack-meeting-alt03:08
*** hemanth_ has joined #openstack-meeting-alt03:10
*** openstack has joined #openstack-meeting-alt03:23
*** hobana.freenode.net sets mode: +ns 03:23
*** hobana.freenode.net sets mode: -o openstack03:28
-hobana.freenode.net- *** Notice -- TS for #openstack-meeting-alt changed from 1381289012 to 135457693703:28
*** hobana.freenode.net sets mode: +ct-s 03:28
*** amytron has joined #openstack-meeting-alt03:28
*** fungi has joined #openstack-meeting-alt03:28
*** torgomatic has joined #openstack-meeting-alt03:29
*** chmouel_ has joined #openstack-meeting-alt03:29
*** hemanth_ has joined #openstack-meeting-alt03:29
*** __nikhil__ has joined #openstack-meeting-alt03:29
*** kebray has joined #openstack-meeting-alt03:29
*** sacharya has joined #openstack-meeting-alt03:29
*** betsy has joined #openstack-meeting-alt03:29
*** harlowja has joined #openstack-meeting-alt03:29
*** morazi has joined #openstack-meeting-alt03:29
*** jomara has joined #openstack-meeting-alt03:29
*** gokrokve_ has joined #openstack-meeting-alt03:29
*** marios has joined #openstack-meeting-alt03:29
*** _ozstacker_ has joined #openstack-meeting-alt03:29
*** kevinconway has joined #openstack-meeting-alt03:29
*** dguitarbite has joined #openstack-meeting-alt03:29
*** ErikB has joined #openstack-meeting-alt03:29
*** enikanorov-w has joined #openstack-meeting-alt03:29
*** jesusaurus has joined #openstack-meeting-alt03:29
*** santhoshsram has joined #openstack-meeting-alt03:29
*** dosaboy has joined #openstack-meeting-alt03:29
*** lsmola has joined #openstack-meeting-alt03:29
*** flwang has joined #openstack-meeting-alt03:29
*** HenryG has joined #openstack-meeting-alt03:29
*** vipul has joined #openstack-meeting-alt03:29
*** notmyname has joined #openstack-meeting-alt03:29
*** kiall_ has joined #openstack-meeting-alt03:29
*** flaper87|afk has joined #openstack-meeting-alt03:29
*** pleia2 has joined #openstack-meeting-alt03:29
*** ivoks has joined #openstack-meeting-alt03:29
*** fvollero has joined #openstack-meeting-alt03:29
*** briancline has joined #openstack-meeting-alt03:29
*** slagun_ has joined #openstack-meeting-alt03:29
*** netapp has joined #openstack-meeting-alt03:29
*** markmcclain has joined #openstack-meeting-alt03:29
*** bnemec has joined #openstack-meeting-alt03:29
*** jmaron has joined #openstack-meeting-alt03:29
*** ikhudoshyn_ has joined #openstack-meeting-alt03:29
*** slagle has joined #openstack-meeting-alt03:29
*** sergmelikyan has joined #openstack-meeting-alt03:29
*** dkehn has joined #openstack-meeting-alt03:29
*** nimi has joined #openstack-meeting-alt03:29
*** aignatov has joined #openstack-meeting-alt03:29
*** sirushti has joined #openstack-meeting-alt03:29
*** david-lyle has joined #openstack-meeting-alt03:29
*** mtreinish has joined #openstack-meeting-alt03:29
*** cp16net has joined #openstack-meeting-alt03:29
*** jdprax has joined #openstack-meeting-alt03:29
*** jeblair has joined #openstack-meeting-alt03:29
*** ctracey has joined #openstack-meeting-alt03:29
*** EmilienM has joined #openstack-meeting-alt03:29
*** rosmaita has joined #openstack-meeting-alt03:29
*** ogelbukh has joined #openstack-meeting-alt03:29
*** ekarlso has joined #openstack-meeting-alt03:29
*** stevebaker has joined #openstack-meeting-alt03:29
*** shhu has joined #openstack-meeting-alt03:29
*** SpamapS has joined #openstack-meeting-alt03:29
*** shanks has joined #openstack-meeting-alt03:29
*** lifeless has joined #openstack-meeting-alt03:29
*** sfineberg has joined #openstack-meeting-alt03:29
*** yportnova has joined #openstack-meeting-alt03:29
*** esmute has joined #openstack-meeting-alt03:29
*** iccha has joined #openstack-meeting-alt03:29
*** dhellmann has joined #openstack-meeting-alt03:29
*** sdague has joined #openstack-meeting-alt03:29
*** cweid has joined #openstack-meeting-alt03:29
*** konetzed has joined #openstack-meeting-alt03:29
*** ameade_ has joined #openstack-meeting-alt03:29
*** shadower has joined #openstack-meeting-alt03:29
*** mordred has joined #openstack-meeting-alt03:29
*** ahdinosa1r has joined #openstack-meeting-alt03:29
*** westmaas has joined #openstack-meeting-alt03:29
*** annashen has joined #openstack-meeting-alt03:29
*** jcooley has joined #openstack-meeting-alt03:29
*** jdbarry has joined #openstack-meeting-alt03:29
*** plomakin_ has joined #openstack-meeting-alt03:29
*** megan_w has joined #openstack-meeting-alt03:29
*** sbadia has joined #openstack-meeting-alt03:29
*** hub_cap has joined #openstack-meeting-alt03:29
*** al-maisan has joined #openstack-meeting-alt03:29
*** clarkb has joined #openstack-meeting-alt03:29
*** simonmcc has joined #openstack-meeting-alt03:29
*** juice has joined #openstack-meeting-alt03:29
*** ChanServ has joined #openstack-meeting-alt03:29
*** hobana.freenode.net sets mode: +o ChanServ03:29
*** hobana.freenode.net changes topic to "OpenStack meetings (alternate)"03:29
*** amytron has quit IRC03:30
*** amytron has joined #openstack-meeting-alt03:31
*** amytron has quit IRC03:49
*** amytron has joined #openstack-meeting-alt03:50
*** dguitarbite has quit IRC03:50
*** dguitarbite has joined #openstack-meeting-alt03:51
*** amytron has quit IRC03:58
*** amytron has joined #openstack-meeting-alt03:59
*** dguitarbite has left #openstack-meeting-alt03:59
*** dguitarbite has joined #openstack-meeting-alt04:03
*** amytron has quit IRC04:04
*** amytron has joined #openstack-meeting-alt04:05
*** sarob has joined #openstack-meeting-alt04:07
*** amytron has quit IRC04:07
*** amytron has joined #openstack-meeting-alt04:08
*** amytron has quit IRC04:11
*** amytron has joined #openstack-meeting-alt04:12
*** sarob has quit IRC04:16
*** amytron has quit IRC04:16
*** sarob has joined #openstack-meeting-alt04:16
*** IlyaE has joined #openstack-meeting-alt04:16
*** amytron has joined #openstack-meeting-alt04:17
*** sarob has quit IRC04:21
*** amytron has quit IRC04:25
*** amytron has joined #openstack-meeting-alt04:26
*** amytron has quit IRC04:40
*** amytron has joined #openstack-meeting-alt04:42
*** amytron has quit IRC04:45
*** jmaron has quit IRC04:45
*** amytron has joined #openstack-meeting-alt04:47
*** gokrokve_ has quit IRC04:48
*** sacharya has quit IRC04:59
*** boris-42 has joined #openstack-meeting-alt05:03
*** amytron has quit IRC05:03
*** amytron has joined #openstack-meeting-alt05:04
*** amytron has quit IRC05:14
*** amytron has joined #openstack-meeting-alt05:15
*** amytron has quit IRC05:17
*** amytron has joined #openstack-meeting-alt05:19
*** amytron has quit IRC05:22
*** amytron has joined #openstack-meeting-alt05:24
*** sarob has joined #openstack-meeting-alt05:27
*** SergeyLukjanov has joined #openstack-meeting-alt05:27
*** amytron has quit IRC05:32
*** sarob has quit IRC05:32
*** amytron has joined #openstack-meeting-alt05:32
*** amytron has quit IRC05:41
*** amytron has joined #openstack-meeting-alt05:42
*** markwash has joined #openstack-meeting-alt05:45
*** amytron has quit IRC05:45
*** jmaron has joined #openstack-meeting-alt05:46
*** amytron has joined #openstack-meeting-alt05:47
*** amytron has quit IRC05:48
*** markwash has quit IRC05:49
*** SergeyLukjanov has quit IRC06:02
*** IlyaE has quit IRC06:07
*** dguitarbite has quit IRC06:09
*** shanks` has joined #openstack-meeting-alt06:15
*** shanks has quit IRC06:17
*** IlyaE has joined #openstack-meeting-alt06:23
*** dkehn_ has joined #openstack-meeting-alt06:25
*** bnemec has quit IRC06:25
*** SergeyLukjanov has joined #openstack-meeting-alt06:25
*** vipul is now known as vipul-away06:25
*** ogelbukh1 has joined #openstack-meeting-alt06:25
*** bnemec has joined #openstack-meeting-alt06:26
*** dkehn has quit IRC06:26
*** ogelbukh has quit IRC06:26
*** IlyaE has quit IRC06:29
*** ogelbukh1 is now known as ogelbukh06:33
*** SergeyLukjanov has quit IRC06:37
*** bnemec has quit IRC06:37
*** bnemec_ has joined #openstack-meeting-alt06:37
*** jmaron has quit IRC06:41
*** flaper87|afk is now known as flaper8706:46
*** SergeyLukjanov has joined #openstack-meeting-alt06:46
*** SergeyLukjanov has quit IRC06:53
*** vipul-away is now known as vipul07:01
*** marios has quit IRC07:03
*** GheRivero has joined #openstack-meeting-alt07:04
*** jmaron has joined #openstack-meeting-alt07:07
*** annashen has quit IRC07:11
*** jdbarry has quit IRC07:12
*** jesusaurus has quit IRC07:13
*** GheRivero has quit IRC07:14
*** annashen has joined #openstack-meeting-alt07:16
*** jesusaurus has joined #openstack-meeting-alt07:17
*** jdbarry has joined #openstack-meeting-alt07:18
*** GheRivero has joined #openstack-meeting-alt07:20
*** flaper87 is now known as flaper87|afk07:24
*** david-lyle has quit IRC07:26
*** david-lyle has joined #openstack-meeting-alt07:28
*** vponomaryov has joined #openstack-meeting-alt07:30
*** jcoufal has joined #openstack-meeting-alt07:30
*** jmaron has quit IRC07:33
*** boris-42 has quit IRC08:06
*** flaper87|afk is now known as flaper8708:06
*** derekh has joined #openstack-meeting-alt08:18
*** akuznetsov has joined #openstack-meeting-alt08:22
*** jmaron has joined #openstack-meeting-alt08:31
*** jmaron has quit IRC08:36
*** NikitaKonovalov has joined #openstack-meeting-alt08:46
*** sergmelikyan has quit IRC08:53
*** sergmelikyan has joined #openstack-meeting-alt08:54
*** NikitaKonovalov has quit IRC09:13
*** venkatesh has joined #openstack-meeting-alt09:25
*** jmaron has joined #openstack-meeting-alt09:32
*** jmaron has quit IRC09:37
*** SergeyLukjanov has joined #openstack-meeting-alt09:41
*** akuznetsov has quit IRC09:41
*** NikitaKonovalov has joined #openstack-meeting-alt09:47
*** flaper87 is now known as flaper87|afk10:17
*** lsmola has quit IRC10:25
*** akuznetsov has joined #openstack-meeting-alt10:29
*** pcm_ has joined #openstack-meeting-alt10:33
*** jmaron has joined #openstack-meeting-alt10:33
*** pcm_ has quit IRC10:34
*** pcm_ has joined #openstack-meeting-alt10:34
*** lsmola has joined #openstack-meeting-alt10:37
*** jmaron has quit IRC10:37
*** boris-42 has joined #openstack-meeting-alt10:55
*** noslzzp has joined #openstack-meeting-alt11:01
*** morazi has quit IRC11:10
*** enikanorov-w_ has joined #openstack-meeting-alt11:15
*** enikanorov-w has quit IRC11:17
*** NikitaKonovalov_ has joined #openstack-meeting-alt11:17
*** NikitaKonovalov has quit IRC11:18
*** NikitaKonovalov_ is now known as NikitaKonovalov11:18
*** flaper87|afk is now known as flaper8711:18
*** jmaron has joined #openstack-meeting-alt11:34
*** jmaron has quit IRC11:38
*** venkatesh has joined #openstack-meeting-alt12:06
*** vkmc has joined #openstack-meeting-alt12:08
*** vkmc has joined #openstack-meeting-alt12:08
*** pdmars has joined #openstack-meeting-alt12:09
*** sergmelikyan has quit IRC12:11
*** dukhlov has joined #openstack-meeting-alt12:16
*** markmcclain has quit IRC12:18
*** NikitaKonovalov has quit IRC12:23
*** jmaron has joined #openstack-meeting-alt12:34
*** jmaron has quit IRC12:38
*** venkatesh has quit IRC12:40
*** jomara has quit IRC12:47
*** NikitaKonovalov has joined #openstack-meeting-alt12:48
*** lblanchard has joined #openstack-meeting-alt12:51
*** sarob has joined #openstack-meeting-alt12:54
*** julim has joined #openstack-meeting-alt12:54
*** sacharya has joined #openstack-meeting-alt12:55
*** demorris has joined #openstack-meeting-alt12:58
*** anteaya has joined #openstack-meeting-alt13:01
*** NikitaKonovalov has quit IRC13:04
*** nikhil has joined #openstack-meeting-alt13:05
*** ErikB has quit IRC13:07
*** ErikB has joined #openstack-meeting-alt13:08
*** jergerber has joined #openstack-meeting-alt13:08
*** jodom has joined #openstack-meeting-alt13:14
*** 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:31
*** dkehn_ is now known as dkehn13:32
*** amytron has joined #openstack-meeting-alt13:46
*** markwash has joined #openstack-meeting-alt13:55
*** markwash has joined #openstack-meeting-alt13:55
*** markmcclain has joined #openstack-meeting-alt13:56
*** IlyaE has joined #openstack-meeting-alt14:02
*** venkatesh has joined #openstack-meeting-alt14:02
*** jdprax has left #openstack-meeting-alt14:03
*** lpabon has joined #openstack-meeting-alt14:10
*** esheffield has joined #openstack-meeting-alt14:13
*** sarob has quit IRC14:30
*** SergeyLukjanov has quit IRC14:30
*** sarob has joined #openstack-meeting-alt14:30
*** sarob has quit IRC14:35
*** julim has quit IRC14:35
*** sacharya has quit IRC14:38
*** julim has joined #openstack-meeting-alt14:40
*** jmontemayor has joined #openstack-meeting-alt14:49
*** kiall_ is now known as Kiall14:51
*** rnirmal has joined #openstack-meeting-alt14:55
*** markwash has quit IRC15:02
*** demorris has quit IRC15:03
*** markwash has joined #openstack-meeting-alt15:03
*** flaper87 is now known as flaper87|afk15:05
*** markwash has quit IRC15:05
*** demorris has joined #openstack-meeting-alt15:06
*** SergeyLukjanov has joined #openstack-meeting-alt15:06
*** sacharya has joined #openstack-meeting-alt15:10
*** jcoufal has quit IRC15:18
*** HenryG has quit IRC15:19
*** sarob has joined #openstack-meeting-alt15:29
*** yidclare has joined #openstack-meeting-alt15:31
*** akuznetsov has quit IRC15:32
*** SergeyLukjanov has quit IRC15:34
*** flaper87|afk is now known as flaper8715:39
*** markmcclain has quit IRC15:45
*** lsmola has quit IRC15:46
*** HenryG has joined #openstack-meeting-alt15:46
*** flaper87 is now known as flaper87|afk15:47
*** bdpayne has joined #openstack-meeting-alt15:51
*** boris-42 has quit IRC16:01
*** boris-42 has joined #openstack-meeting-alt16:02
*** colinmcnamara has joined #openstack-meeting-alt16:04
*** demorris has quit IRC16:05
*** anteaya has quit IRC16:07
*** venkatesh has quit IRC16:08
*** colinmcnamara has quit IRC16:09
*** markwash has joined #openstack-meeting-alt16:14
*** vponomaryov has left #openstack-meeting-alt16:14
*** enikanorov-w_ has quit IRC16:16
*** enikanorov-w has joined #openstack-meeting-alt16:17
*** boris-42 has quit IRC16:23
*** boris-42 has joined #openstack-meeting-alt16:23
*** _ozstacker_ has quit IRC16:24
*** akuznetsov has joined #openstack-meeting-alt16:28
*** yidclare has quit IRC16:36
*** shamail has joined #openstack-meeting-alt16:38
*** ErikB has left #openstack-meeting-alt16:40
*** shamail has quit IRC16:41
*** eankutse has quit IRC16:45
*** eankutse has joined #openstack-meeting-alt16:51
*** chmouel_ is now known as chmouel16:51
*** boris-42 has quit IRC16:54
*** SergeyLukjanov has joined #openstack-meeting-alt16:54
*** boris-42 has joined #openstack-meeting-alt16:55
*** IlyaE has quit IRC16:55
*** rnirmal has quit IRC16:57
*** boris-42 has quit IRC16:58
*** tsimmons has joined #openstack-meeting-alt17:01
*** Kiall has quit IRC17:01
*** tsimmons has quit IRC17:01
*** derekh has quit IRC17:02
*** pdmars_ has joined #openstack-meeting-alt17:04
*** pdmars has quit IRC17:08
*** pdmars_ has quit IRC17:08
*** pdmars has joined #openstack-meeting-alt17:09
*** mugsie has joined #openstack-meeting-alt17:11
*** venkatesh has joined #openstack-meeting-alt17:14
*** yogesh has joined #openstack-meeting-alt17:14
*** lblanchard has quit IRC17:15
*** sarob has quit IRC17:16
*** sarob has joined #openstack-meeting-alt17:16
*** markmcclain has joined #openstack-meeting-alt17:18
*** sarob_ has joined #openstack-meeting-alt17:21
*** sarob has quit IRC17:21
*** kiall_ has joined #openstack-meeting-alt17:21
*** IlyaE has joined #openstack-meeting-alt17:22
*** yidclare has joined #openstack-meeting-alt17:28
*** noslzzp has quit IRC17:29
*** venkatesh has quit IRC17:32
*** sarob_ has quit IRC17:33
*** sarob has joined #openstack-meeting-alt17:34
*** sarob has quit IRC17:38
*** bnemec_ is now known as bnemec17:44
*** boris-42 has joined #openstack-meeting-alt17:58
*** jrodom has joined #openstack-meeting-alt18:01
*** jrodom has quit IRC18:01
*** tsimmons has joined #openstack-meeting-alt18:05
*** jodom has quit IRC18:05
*** demorris has joined #openstack-meeting-alt18:05
*** jrodom has joined #openstack-meeting-alt18:11
*** jrodom has quit IRC18:13
*** tsimmons has left #openstack-meeting-alt18:21
*** dmakogon_ipod has joined #openstack-meeting-alt18:25
*** rnirmal has joined #openstack-meeting-alt18:30
*** dmakogon_ipod is now known as dmakogon18:32
dmakogoni'm home18:32
dmakogonlet's talk18:32
*** lblanchard has joined #openstack-meeting-alt18:37
*** akuznetsov has quit IRC18:56
*** demorris has quit IRC19:00
*** pdmars_ has joined #openstack-meeting-alt19:04
*** IlyaE has quit IRC19:04
*** demorris has joined #openstack-meeting-alt19:06
*** pdmars has quit IRC19:08
*** vipul is now known as vipul-away19:10
*** vipul-away is now known as vipul19:10
*** dmakogon_ has joined #openstack-meeting-alt19:11
*** dmakogon_ has quit IRC19:12
*** dmakogon_ has joined #openstack-meeting-alt19:13
*** akuznetsov has joined #openstack-meeting-alt19:14
*** dmakogon has quit IRC19:14
*** jrodom has joined #openstack-meeting-alt19:15
*** IlyaE has joined #openstack-meeting-alt19:21
*** vipul is now known as vipul-away19:25
*** vipul-away is now known as vipul19:26
*** ozstacker has joined #openstack-meeting-alt19:27
*** jrodom has quit IRC19:31
*** lsmola has joined #openstack-meeting-alt19:32
*** yogesh has quit IRC19:44
*** datsun180b has joined #openstack-meeting-alt19:49
*** KennethWilke has joined #openstack-meeting-alt19:52
*** NehaV has joined #openstack-meeting-alt19:53
*** cweidenkeller has joined #openstack-meeting-alt19:53
cweidenkellero/19:53
hub_caplol @ 5 min early19:54
cweidenkeller-_-19:54
KennethWilke\o/19:54
hub_capstop it! ;)19:54
dmakogon_guys, patience)))19:55
KennethWilkenever!19:55
* KennethWilke flips tables19:55
*** gokrokve has joined #openstack-meeting-alt19:56
*** tanisdl has joined #openstack-meeting-alt19:57
*** grapex has joined #openstack-meeting-alt19:57
dmakogon_1 minute19:59
*** isviridov has joined #openstack-meeting-alt19:59
*** mattgriffin has joined #openstack-meeting-alt20:00
dmakogon_o/20:00
*** jcru has joined #openstack-meeting-alt20:00
isviridovo/20:00
hub_cap#startmeeting trove20:00
openstackMeeting started Wed Oct  9 20:00:46 2013 UTC and is due to finish in 60 minutes.  The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
datsun180bOh, I think it's time20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
openstackThe meeting name has been set to 'trove'20:00
*** imsplitbit has joined #openstack-meeting-alt20:00
cp16neto^/20:00
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting20:01
kevinconway\\o//20:01
*** robertmyers has joined #openstack-meeting-alt20:01
*** SlickNik has joined #openstack-meeting-alt20:01
imsplitbito/20:01
datsun180bpresent20:01
mattgriffino/20:01
isviridovHi all20:01
SlickNikhere20:01
pdmars_o/20:01
SlickNikHello all20:01
KennethWilkehowdy20:01
kevinconway\\\o///20:01
cweidenkelleroi20:01
grapexo/20:01
*** pdmars_ is now known as pdmars20:01
hub_cap#link http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-10-02-20.00.html20:01
juiceo/20:01
hub_cap#topic update to action items20:01
hub_capgod SlickNik this is embarrasing20:01
cp16netlol20:02
hub_caphave u done any work w/ LP for group stuff?20:02
SlickNikugh, I keep forgetting about this. I'm gonna do it right now. :)20:02
hub_cap#action SlickNik to check with other teams to set groups permissions correctly on LaunchPad20:02
* hub_cap is removed20:02
hub_cap;)20:02
SlickNikvery clever.20:02
SlickNik;)20:02
hub_capnow its your fault if its not done20:03
hub_caphahahahah victory20:03
SlickNikheh20:03
hub_cap#topic escaping dots in urls20:03
dmakogon_does users could be able to retrigg their builds ?20:03
hub_capdatsun180b: go20:03
datsun180bokay20:03
hub_capdmakogon_: it has to do with that and modifying bugs / blueprints20:03
*** dmakogon_ is now known as dmakogon20:03
datsun180bso there's a problem when issuing requests that end in a field that is dotted20:03
datsun180buser calls except create for example20:03
datsun180bso in case a username/hostname contains a dot, the route mapper has a habit of eating the final extension, thinking it's a file extension20:04
hub_capcan u give an example?20:04
isviridovdoesn't user should encode url himself?20:04
datsun180bthis can be a problem when issuing a call like GET /users/foo.bar, because the response ends up being a 404: 'user foo DNE'20:05
*** colinmcnamara has joined #openstack-meeting-alt20:05
vipulo/20:05
datsun180bso to get around this we can escape the dots as %2e: "GET /users/foo%2ebar"20:05
*** demorris has quit IRC20:05
dmakogonok with that20:05
datsun180bbut to issue this call manually, it must be encoded a SECOND time: GET /users/foo%252ebar20:05
*** jcorbin has joined #openstack-meeting-alt20:06
isviridovdatsun180b:  is it python client issue?20:06
datsun180bThis is an issue with the way we use route mapper20:06
hub_capwell the issue is _cuz_ we use route.mapper20:06
datsun180bThis has been a pain point for Rax users, even ones using curl or similar clients to issue requests20:06
dmakogonhow do we able to fix that ?20:07
isviridovIt should be done on client side  http://www.w3schools.com/tags/ref_urlencode.asp20:07
datsun180bOne way would be to inspect the request object to look for the 'missing' extension20:07
datsun180bbut that would require a whitelist of expected suffixes and limit possible usernames20:07
*** esp has joined #openstack-meeting-alt20:07
datsun180banother approach would be to use unique ids for users that do not contain the username or host20:08
hub_capive ruled on this in the past fwiw, and i think it should not be something we whitelist. its up to the user to deal with20:08
kevinconwaydatsun180b: who uses curl for our api?20:08
kevinconwaythat sounds painful20:08
hub_caplol kevinconway no rules against it20:08
hub_capi write al my webapps in bash20:08
dmakogonhah20:08
hub_capbash on bails?20:08
dmakogonnice20:08
* KennethWilke dies20:08
grapexkevinconway: Curl is the preferred choice for people who want to show examples proving they actually wrote a REST API and not something that requires a special client. :)20:09
NehaVbut there needs to be a sophisticated way to handle it for customers20:09
datsun180bwell i'm having a hard time speaking for all of our users20:09
isviridovso it is you job to encode urls properly, right?20:09
hub_cap++20:09
*** colinmcnamara has quit IRC20:09
datsun180bi'll reiterate another approach: to not refer to users by their name or host in request URL20:09
hub_caplets just say its the job of the consumer. i rule on it.20:09
datsun180bcompletely sidestep the issue20:09
hub_capdatsun180b: i agree w/ that somewhat, but the mysql api allows for it20:10
*** saurabhs has joined #openstack-meeting-alt20:10
hub_capand how else can we delete users20:10
hub_cap:/20:10
datsun180bdelete users/user-uuid20:10
hub_capif they are their own resource20:10
NehaVcurrently it is not clear how customers with a . name can easily handle it20:10
datsun180bthat would be a v2 change i'm guessing20:10
datsun180bhub_cap: final word?20:11
hub_capNehaV: we should document that20:11
isviridovit is ugly, we don't ask google to add extra logic to make incorrect requests working20:11
dmakogonso, make a conclusion20:11
hub_capbut we are not going to sacrifice functionlity of the app for this20:11
kevinconwaydatsun180b: can i take my 50/5020:11
hub_capobvi dmakogon wants us to move on20:11
hub_cap;)20:11
isviridovit is standard, what we are talking about20:11
hub_cap++20:12
dmakogonno, Ed said - "final word" )))20:12
kevinconwayisviridov: it's not standard to double url encode your input20:12
NehaVdocumenting is fine but we are not giving a good experience. this is a common use case to have . in username20:12
datsun180bespecially in ipv4 addresses20:12
hub_capNehaV: the other solutions limit the app behavior20:12
hub_capyou have to blacklist particular users that are allowed in mysql, artificilly limiting behavior20:12
hub_capso we either accept that you have to encode, or limit our api20:13
vipulwhy not just patch routes?20:13
isviridovkevinconway:  yes, that is why no additional logic of recognition wrong encoding on server side20:13
vipuldoes it give us the ability to get teh extension?20:13
hub_capvipul: i did a while ago, for escaping dots20:13
vipulif so.. we could write some hack that concats20:13
isviridovwhat about url fixing on reverse proxy side if it exists?20:14
vipulwe don't have any use case in our api for extensions anyway20:14
kevinconwayi think we need a new daemon to translate user names to the right format20:14
hub_capvipul: https://github.com/bbangert/routes/commit/1c5da13b9fc227323f7023327c8c97e9f446353f20:14
datsun180bfor example if i wanted to name a user foobar.json it would be ambiguous20:14
vipulwe allow .json in the url? is it meaningful?20:15
hub_capyes we do20:15
datsun180bvipul: apparently it is20:15
hub_capits a format string, try it out20:15
vipulthat's what the accept is for20:15
NehaVhub_cap - isn't there a better way to fix it rather than just documenting and asking to add escape20:15
hub_cap.xml and .json20:15
cp16netit can override the accept headers20:15
hub_capNehaV: not that doesnt break the overall functionality of the app for _anything_ that requires dots in urls20:15
isviridovhub_cap:  +120:16
datsun180bwell i'll note that we've exhausted 15 minutes of our weekly meeting about this. this discussion may need to continue somewhere or somewhen else with respect to the other issues we have to discuss20:16
kevinconwayto the mailing list!20:16
datsun180bthat's actually a good idea20:16
dmakogonML or die20:16
hub_capML or die20:16
cp16net+120:16
kevinconwayML or pie20:17
hub_capill take pie20:17
hub_capmoving on20:17
datsun180bbut i'm not in control of this meeting, i just technically have the floor. hub_cap, up to you to move the topic if you like20:17
hub_cap#topic Provisioning post ACTIVE20:17
*** demorris has joined #openstack-meeting-alt20:17
*** amcrn has joined #openstack-meeting-alt20:17
*** yogeshmehra has joined #openstack-meeting-alt20:17
hub_capvipul: this is u ya?20:17
vipulThis is me.. comment on redthrux's patch for moving DNS provisioning20:17
hub_caphey put your name on the things u add20:18
vipulthings like DNS.. floating IPs.. security groups20:18
vipularen't needed unless the instnace is usable20:18
vipulwhich means ACTIVE20:18
vipulso why not provision them after that20:18
dmakogonabout that, we cannot add any resource creation after poll_untill cuz it would brake or limit heat workflow20:18
grapexvipul: I think the issue is they actually are needed20:18
vipulgrapex: they are needed even if the instance never goes active?20:19
dmakogoncuz heat would cover every resources ever imagined20:19
grapexIf there is no DNS, the instance can't actually be used.20:19
hub_capi believe firmly that if the resources we are supposed to create do not get created, its FAILED20:19
dmakogongrapex: why is that ?20:19
vipulSure.. which is why if DNS fails.. then we dont' consider it active20:19
hub_capif we need a sec grp or dns, and the instance comes online but dns failed, mark it as FAILED20:19
vipulregardless of whether mysql came up20:19
hub_capcorrect vipul20:19
isviridovdo we have any cases when user fixes proviosioning parts? Like re-adding floating IP?20:19
hub_capFAIL20:19
grapexvipul: dmakogon: Do you mean, why provision that stuff if the instance itself won't provison? Why not put it at the end?20:19
hub_capisviridov: no point in that20:19
hub_capjust delete/recreate20:19
grapexI agree we should put it at the end- maybe20:20
grapexI just think the status should only be ACTIVE if *all* resources have provisioned20:20
hub_cap++20:20
vipulsure.. agreed20:20
isviridovso, let us think about it as atomic thing20:20
grapexvipul: So maybe we agree on the point that the resource prov order should be changed20:20
grapexCurrently, the status of ACTIVE comes back when the server and volume are ACTIVE and the guest status is also ACTIVE20:20
dmakogonserver -> DB -> sec.gr -> fl.ip -> dns20:20
hub_capwell20:21
hub_capserver+db+sec+ip+dns20:21
grapexIf we want to move the provisioning of other stuff until after the server provisions, then we'd need to essentially set the active status in the trove database at the end of the task manager provisioning routine20:21
hub_cap= ACTIVE20:21
*** SergeyLukjanov has quit IRC20:21
dmakogonthis all would work with nova background20:21
SlickNikI agree on the ACTIVE part (i.e. an instance should go ACTIVE iff none of the component parts fail provisioning), still thinking about the order part.20:21
hub_capso the status is async20:21
hub_capits sent back from teh guest20:21
isviridovorder is defined by dependencies, but result is single20:22
hub_capso i dont think we need to necessarily wait for that to prov other resources20:22
hub_capwe can always clean up20:22
grapexhub_cap: Right now the active status checks the server and volume STATUS, plus the service (guest) status, and if they're all ACTIVE it shows the user ACTIVE20:22
grapexMaybe what we do is20:22
*** eankutse has quit IRC20:22
grapexin the taskmanager, we wait until everything provisions, and then we save something to the trove DB as a marker saying we beleive all resources provisioned20:22
*** eankutse has joined #openstack-meeting-alt20:22
grapexthen the ACTIVE status is whether the Trove taskmanager thinks it finished plus if the service status is ACTIVE20:22
dmakogonhub_cap: vipul: grapex: how this would work with heat provisioning20:23
vipulcouldn't we use task state for that20:23
dmakogon??20:23
grapexvipul: Maybe20:23
vipulso maybe we actually make use of that when aggregating the end user status20:23
*** SergeyLukjanov has joined #openstack-meeting-alt20:23
grapexdmakogon: Not sure, but I think if we changed that it would be closer to what we need for Heat20:23
vipultaksmanager goes to PROVISION COMPELTE or whatever -> implies ACTIVE20:23
grapexvipul: Or maybe it should be set to NONE-20:24
grapexthat actually would be more consistent with the other action code20:24
dmakogonhub_cap: vipul: grapex: when we are using heat all resources already created with stack, so we cannot manipulate and controll creation of any instance related resources !20:24
grapexvipul: But I agree with the idea20:24
hub_cap+1 dmakogon20:24
hub_caplets not change it20:24
isviridov+120:24
SlickNikdmakogon: Ideally heat would be able to provision all this for us, so we wouldn't have to piecemeal provision an instance.20:24
dmakogonhub_capL totally agree with you20:24
vipulcan't you do thinks with HEAT that wait for conditions to be met20:25
grapexdmakogon: The idea isn't that we're dramatically changing it, we're just moving stuff around a bit20:25
*** SergeyLukjanov has quit IRC20:25
grapexBtw, I only think this is necessary if we care about the order of provisioning20:25
dmakogongrapex: it would brake whole workflow provisioning20:25
grapexI personally don't know if its worth doing now20:25
dmakogoni'm suggesting to leave it as it is20:26
hub_capvipul: WaitConditions20:26
vipulFor now, we could let it go to ACTIVE.. and if DNS proviisioning fails, mark as FAILED20:26
grapexdmakogon: I honestly agree. Vipul, what was a big motivation to change the order?20:26
hub_caplets solve redthrux's meeting20:26
hub_capLOL20:26
vipulI don't think the whole status reporting needs to be solved20:26
hub_capissue20:26
grapexvipul: I don't think that would work for DNS20:26
hub_capi dont think the whole thing needs to be redone20:26
grapexSo redthrux had to miss the meetign due to a doctor appointment20:26
grapexI talked to him a bit20:26
grapexHere is his real problem20:26
hub_caplets make sure that we mark a status to failed for dns if it fails20:27
grapexWhen DNS fails, we set it to a task status that means that DNS fails-20:27
dmakogonhub_cap: vipul: grapex: forget about DNS, it also would be a part of heat resources20:27
grapexthe problem is though, in this state a Delete operation is not allowed. That's the bug we need to fix- it should be possible to delete such instances.20:27
dmakogonhub_cap: vipul: grapex: dns is not critial resource20:27
vipulheat = magic wand20:27
grapexdmakogon: It's only critical if we want users to be able to use it to log into their databases.20:27
SlickNiklol @ vipul20:28
grapexvipul: Lol20:28
hub_capdmakogon: thats not correct. it is critical20:28
hub_capif you need dns20:28
dmakogonhub_cap: vipul: grapex: mgmt allows to re-create dns record or we could do that by hands20:28
hub_capand its part of your workflow20:28
hub_capno20:28
hub_capno no no20:28
hub_capif dns fails your instance fails20:28
hub_capperiod20:28
hub_capdelete/recreate20:28
hub_capand fix your crappy dns system ;)20:28
grapexHow about we make an action item to allow DELETE to work on instances in the BUILDING_ERROR_DNS state?20:28
vipulSo in the current patch, we tell taskamanger to provision the instance, and immediately go create DNS20:28
isviridovgrapex:  let us fix bug with deleting, instead of introducing new ones20:28
SlickNikdmakogon: I don't think any of trove's customers need to or want to involve themselves with managing DNS :)20:29
dmakogongrepex +120:29
hub_cap++20:29
SlickNikgrapex: agreed20:29
dmakogonSlickNik: maybe so, so i'm ok with new DNS status20:29
dmakogonlike grapex said20:29
dmakogoncould we talk about security groups review ?20:29
grapex#action Fix bug with DELETE to allow instances in BUILDING_ERROR_DNS state to be deleted.20:30
vipulthat's works.. I still think we are unnecessarily provisioning things unless we wait for Gueat to come active20:30
dmakogonalmost everyone already seen it, so i want tot make a conclusion20:30
grapexvipul: I agree20:30
grapexvipul: it just seems like no one wants to fix it right now if Heat is coming20:30
hub_capok moving on?20:30
imsplitbityes pls20:30
grapexvipul: I think it would be possible in a minimal way, but it sounds like there's not much support... maybe we can talk later.20:31
vipulyep.. revist after HEAT20:31
SlickNiksounds good20:31
hub_cap#topic Provision database in specific tenant20:31
hub_cap#link https://blueprints.launchpad.net/trove/+spec/dedicated-tenant-db-provisioning20:31
hub_capisviridov: yer up20:31
*** akuznetsov has quit IRC20:31
isviridovso, idea is to make Trove real DBaaS out of the box20:31
hub_capcan u explain what this means?20:31
*** Barker has joined #openstack-meeting-alt20:32
isviridovNow we are creating db in target tenant quota, but already have own quota management20:32
isviridovwhy not create all instances in f.e. trove tenant?20:32
*** akuznetsov has joined #openstack-meeting-alt20:32
vipulit's possible.. just need a custom remote.py20:33
hub_capim confused, so youre saying submit resources on behalf of a single user?20:33
grapexisviridov: What is the difference between "trove tenant" and "target tenant quota"?20:33
vipulone super-tenant?20:33
vipulthat holds all instances20:33
hub_capso nova resources are not shown as the users instances?20:33
isviridovso, user doesn't care about his quota and doesn't see instances what belongs to trove actually20:33
hub_caplike a shadow user so to speak20:33
vipulsounds like it20:34
amcrnisviridov: because as a provider, if your deployment currently assigns a tenant per user, you now have no way of restricting resources on a developer/project basis?20:34
dmakogonit means that trove should own personal tenant and which you rule all stuff20:34
hub_caphi amcrn!20:34
amcrnhi :)20:34
hub_capthats now how openstack works though20:34
hub_capwhat problem are you trying to solve?20:34
amcrnright, so I'm asking what's the problem he's trying to solve20:34
amcrnjinx :P20:34
SlickNikYou'd have the extra overhead of doing _all_ of the quota management yourself.20:34
hub_capif you need managed resources in nova20:35
hub_capthen we should fix nova to allow it20:35
hub_capive spoken w/ the nova team about this (a long time ago)20:35
isviridovhub_cap:  it is an idea to hide all trove resource management from user a20:35
hub_capto provision resources that maybe a user cant see when they list nova isntances, or at least cant use it20:35
hub_caplike the problem is a user sees nova resources20:36
hub_capand can, for instance, change ram20:36
vipulyea if you're running Trove against a public nova endpoint, i see the issue..20:36
hub_capyes this is not a trove problem20:36
vipulyou have Trove instances littered in your acct along with compute instances20:36
hub_capits a resource viewing / accessing issue in nova20:36
hub_caplets talk to nova to see if htey would still allow "shadow"/"managed" users20:36
*** KennethWilke has quit IRC20:36
isviridov1 sec20:37
vipulbtw isviridov.. if you _really_ want to do this.. just put in a diffrent remote.py :)20:37
isviridovlook you have got me vipul20:38
isviridovjust create all instances in trove tenant, not users'one20:38
isviridovand handle all quota inside that tenant20:38
*** cweidenkeller has quit IRC20:39
isviridovso, user uses it as pure dbaas20:39
hub_capisviridov: its pure dbaas w/ multiple tenants too20:39
dmakogonso, all auth stuff could happen under the hood of trove api20:39
hub_capfor the record20:39
vipulupstream trove supports deployment that creates instances in user's tenant...20:39
vipulyou could alwyas change that behavior.. which is the reason why we make it pluggbale20:40
hub_capfwiw, this shoud not be fixed in trove... there is no need to have a single global tenant id think20:40
vipulnot in upstream20:40
hub_capvipul: and not contribue it upstream20:40
hub_capvipul: ++20:40
*** dukhlov_ has joined #openstack-meeting-alt20:40
hub_capmanaged instances will be the best approach in nova20:40
dmakogonhub_cap: vipul: is it possible to make it configurable20:40
dmakogon ?20:40
hub_capi dont think its necessary..20:41
hub_capall of openstack behaves one way20:41
hub_capwe should stay standard20:41
isviridovanyhow we don't give access to db instances for user20:41
isviridovwhy he should see and manage all that resources?20:41
hub_capagain this goes back to "what is the problem you are trying to solve"20:41
hub_capif the problem is users can see your nova resources20:41
vipuldmakogon: it is today20:42
hub_capthen teh problem is that we need to fix it in nova20:42
dmakogonvipul: what ?20:42
vipuldmakogon: It is already configurable.. how you decide to spin up nova resources20:43
rnirmaland other projects as well.. since the same applies for cinder or designate for example20:43
hub_cap++20:43
rnirmalalso there's a caveat with using single tenant when you want to create tenant networks20:43
*** akuznetsov has quit IRC20:43
rnirmalsay for private tenant network for a cluster20:43
dmakogonvipul: i mean to make it resources per user tenant and resources per trove tenant20:43
hub_caprnirmal: ++20:43
hub_capit will be a problem20:44
vipuldmakogon: Yes that's all driven by whether you pass down the auth-token to NOva or obtain a new one for the shadow tenant20:44
hub_capwe should move on20:44
hub_capthere are more things20:44
vipulyes20:44
isviridovlet us20:44
dmakogonvipul: oh, i got it20:44
SlickNikyup20:44
*** boris-42 has quit IRC20:45
hub_cap#topic Provisioning several db processes on the same cluster20:45
hub_cap#link https://blueprints.launchpad.net/trove/+spec/shared-cluster-db-provisioning20:45
hub_capok im not a fan of this one either20:46
hub_cap:)20:46
hub_capweve talked about it in the past20:46
isviridovIt is about cloud utilization. The idea to host several database daemons on the same cluster20:46
hub_capif you have too many spare cycles on your nodes, your nodes are too big20:46
isviridov)20:46
hub_capshrink the nodes if you have extra utilization20:46
hub_capand prov a new cluster20:46
imsplitbithub_cap: +1000000020:46
hub_capupgrades, guest status, and many other things would not be easy20:47
*** boris-42 has joined #openstack-meeting-alt20:47
isviridovNot extra, but idle20:47
rnirmaland create more vms where necessary.. or containers..they are cheap20:47
hub_cap++++++++++ rnirmal20:47
SlickNikI think this is a bad idea in general.20:47
kevinconwayso you want to have one instance run multiple guests and multiple db engines?20:47
hub_capcloud is cheap20:47
hub_capkevinconway: thats what he was proposing20:47
amcrni could see a situation once baremetal is supported, that you'd want multiple processes (say Redis) on a single machine to avoid wasting hardware, but other than that, i'm with hub_cap/rnirmal/etc.20:47
hub_capwhat is active? active_cassandra, active_mongo, some status thereov?20:48
hub_capmy mongo is up but my cassandr is down20:48
hub_capwhat does that mean20:48
hub_capor 2 clusters20:48
imsplitbityeah we've definitely talked alot about this in the past and the general concensus has always been one container does one thing20:48
kevinconwaydoes one user access all the engines?20:48
juiceamcrn: even in that case wouldn't it be better to use an lxc driver to partition the instances and resources?20:48
isviridovkevinconway:  different20:49
amcrnjuice: fair enough20:49
grapexisviridov: I feel like for flexibility, this *should* have been built into Trove. But as you can see no one likes it. :)20:49
*** amytron has quit IRC20:49
juiceamcrn: assuming lxc driver works with nova :P20:49
SlickNikjuice / amcrn: yup, even if baremetal were supported, I'd push for having these agents run in separate containers on the bare metal node so some isolation exists.20:49
* hub_cap spills some coffee over grapex's keyboard20:49
*** sarob has joined #openstack-meeting-alt20:49
isviridovlooks it will be in future or substituled witk containers like dokit20:49
isviridovthanks, let's move on20:49
hub_cap#topic Auto-recovery of node in replica/cluster20:50
hub_cap#link https://blueprints.launchpad.net/trove/+spec/auto-recovery-of-cluster-replica20:50
hub_capnow i like this!20:50
isviridovFinally ^)20:50
hub_caphahah20:50
vipulwhat types of metrics woudl we push to ceilometer20:51
*** sarob has quit IRC20:51
dmakogonyes, as we discussed earlier, autorecovery/failover is one of the goals for IceHOuse20:51
vipuland how does ceilometer notify Trove to do sometihng20:51
*** sarob has joined #openstack-meeting-alt20:51
dmakogonvipul: specific database related metrics20:51
isviridovvipul:  it depends on the type of cluster and specific for db20:51
cp16netBender: C'mon, it's just like making love. Y'know, left, down, rotate sixty-two degrees, engage rotors...20:51
hub_capi agree w cp16net20:52
dmakogoncp16net: nice one)))20:52
vipullol20:52
isviridovvipul:  celiometer has Alerts mechanism which is used in HEAT for autoscaling20:52
datsun180bsounds like someone else needs coffee on their keyboard20:52
* hub_cap throws a random number of Ninja Turtles at cp16net20:52
juiceD2020:52
hub_capok srsly though, i think that we can discuss the approach offline. i do like the idea though20:52
dmakogonhub_cap +120:53
kevinconwayML is nigh20:53
vipulhow about doing this for a single instance?20:53
hub_capyes ML++20:53
vipulwhy does it need to wait for clusters20:53
hub_caplets table this20:53
hub_capi reallyw ant to discuss the next one20:53
dmakogonvipul: as first step - maybe, what about down-time and data consistency ?20:53
SlickNikI like the idea as well. But I think a prereq for it would be to have some sort of cluster / replica implemented no?20:53
vipulit's down anyway.. if it needs to be recovered20:53
*** sarob_ has joined #openstack-meeting-alt20:54
isviridovfrom backup f.e.20:54
dmakogonrecovery = spinning new instance20:54
imsplitbitbtw I would like to open the trove channel for replication/cluster api discussion after this meeting and tomorrow morning when everyone gets in20:54
isviridovthe criteria should be defined for single instance20:54
*** vkmc has quit IRC20:54
isviridovimsplitbit:  would love to join20:54
SlickNikvipul: I like the idea but, I'm not sure what would be the recovery in case a single instance is down?20:55
vipulrestore from last known backup20:55
vipulwhich is all you can do20:55
*** sarob has quit IRC20:55
isviridovyes20:55
dmakogonSlickNik : provisioning new one20:55
vipuli'm just saying there is opportunity to prove this with a single instance.. before getting crazy with clusters20:55
hub_capheyo20:55
hub_cap#table it20:55
dmakogonto substitute20:55
hub_cap#move on20:55
vipulfine!20:55
hub_cap:P20:55
hub_cap#topic Lunchpad meetings20:56
SlickNikI like it, but table for later.20:56
hub_capcrap i menat to fix that typo20:56
hub_cap*meant20:56
isviridovThe last from my side20:56
SlickNikheh20:56
hub_cap#link https://launchpad.net/sprints20:56
hub_capdid the openstack bot die?20:56
dmakogongood idea20:56
isviridovWe are in different timezone, let us arrange the topic meetings20:56
imsplitbitoh noes20:56
SlickNiklooks like it20:56
imsplitbitno bot?!20:57
dmakogonscheduling is always good way20:57
isviridovhub_cap:  how it can help with scheduling?20:57
vipulwhat is this link for20:57
vipulare we having a gathering?20:57
hub_capim not sure. im curios to know if we need it20:57
isviridovvipul:  for creating public visible meeting20:57
hub_capso like this meeting?20:57
dmakogonhub_cap: yes, we could plan discussions20:58
kevinconwayisviridov: other than this one?20:58
SlickNikWhat's wrong with #openstack-meeting-alt for that?20:58
amcrn"Launchpad can help you organize your developer sprints, summits and gatherings. Register the meeting here, then you can invite people to nominate blueprints for discussion at the event. The meeting drivers control the agenda, but everyone can see what's proposed and what's been accepted."20:58
isviridovkevinconway:  yes, but by the topic20:58
dmakogonmonday = cluster API , tue = failover20:58
amcrnI imagine it's a replacement for the wiki you're using20:58
kevinconwayoh no… meetings every day?20:58
amcrn(that holds the topics, last weeks notes, etc.)20:58
isviridovamcrn:  forget about description, it is just a tool20:58
hub_caphow is this different from just being in #openstack-trove ?20:58
hub_capand sayding "lets discuss tomorrow at 10am"20:58
SlickNikhere's an example of a sprint: https://launchpad.net/sprints/uds-131120:59
dmakogonkevinconway: if you want to be involved everywhere20:59
isviridovhub_cap:  we can come together and discuss specific topic20:59
vipuli hate launchpad..20:59
kevinconwaythis is a ML topic20:59
vipulso the less we do the better IMHO :P20:59
hub_capisviridov: how do we not do that _in_ the room?20:59
hub_capdoes it allow for async?20:59
dmakogonvipul made good conlusion for this topic: "I have LP"20:59
hub_capif it requires us to be somewhere, virtually, at the same time21:00
vipuls/have/hate21:00
hub_capi dont se what it buys us over just being in the channel21:00
SlickNikSo like amcrn said, it would only be a replacement for the meeting agenda page on the wiki, if anything…21:00
hub_capand for async, we have the ML21:00
fungiahh, yep, openstack (the meetbot) is missing his ops hat. fixing21:00
hub_cap<3 fungi21:00
hub_capill endmeeting after21:00
SlickNikthanks fungi!21:00
*** ChanServ sets mode: +o openstack21:00
hub_cap#endmeeting21:00
*** openstack changes topic to "OpenStack meetings (alternate)"21:00
openstackMeeting ended Wed Oct  9 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-09-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-10-09-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-10-09-20.00.log.html21:00
hub_capGOTO #openstack-trove21:01
hub_caplets continue21:01
fungithe bot should be all set for the next meeting at least21:01
*** SlickNik has left #openstack-meeting-alt21:01
*** imsplitbit has left #openstack-meeting-alt21:01
*** esp has left #openstack-meeting-alt21:04
*** grapex has quit IRC21:04
*** amcrn has left #openstack-meeting-alt21:05
*** pdmars has quit IRC21:06
*** jcorbin has left #openstack-meeting-alt21:06
*** gokrokve has quit IRC21:07
*** lblanchard has quit IRC21:08
*** demorris has quit IRC21:09
*** IlyaE has quit IRC21:09
*** lpabon has quit IRC21:12
*** pcm_ has quit IRC21:12
*** eankutse1 has joined #openstack-meeting-alt21:21
*** eankutse1 has quit IRC21:22
*** eankutse has quit IRC21:25
*** IlyaE has joined #openstack-meeting-alt21:37
*** robertmyers has quit IRC21:39
*** IlyaE has quit IRC21:41
*** Barker has quit IRC21:43
*** sacharya has quit IRC21:47
*** colinmcnamara has joined #openstack-meeting-alt21:52
*** yogeshmehra has quit IRC21:53
*** colinmcnamara has quit IRC21:56
*** colinmcnamara has joined #openstack-meeting-alt21:56
*** dukhlov_ has quit IRC21:59
*** colinmcnamara has quit IRC22:00
*** dosaboy has quit IRC22:01
*** jergerber has quit IRC22:13
*** jmaron has quit IRC22:13
*** NehaV has left #openstack-meeting-alt22:20
*** dosaboy has joined #openstack-meeting-alt22:21
*** dmakogon has quit IRC22:28
*** colinmcnamara has joined #openstack-meeting-alt22:32
*** noslzzp has joined #openstack-meeting-alt22:39
*** datsun180b has quit IRC22:44
*** jcru has quit IRC22:46
*** julim has quit IRC22:48
*** eankutse has joined #openstack-meeting-alt22:49
*** eankutse has joined #openstack-meeting-alt22:50
*** IlyaE has joined #openstack-meeting-alt23:06
*** jmaron has joined #openstack-meeting-alt23:14
*** IlyaE has quit IRC23:15
*** jmaron has quit IRC23:23
*** eankutse1 has joined #openstack-meeting-alt23:39
*** yidclare has quit IRC23:40
*** eankutse has quit IRC23:43
*** venkatesh has joined #openstack-meeting-alt23:46
*** torgomatic has quit IRC23:49
*** sarob_ has quit IRC23:50
*** sarob has joined #openstack-meeting-alt23:51
*** sacharya has joined #openstack-meeting-alt23:52
*** jrodom has joined #openstack-meeting-alt23:53
*** sarob has quit IRC23:55
*** colinmcnamara has quit IRC23:55

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