Monday, 2013-09-30

*** matsuhashi has joined #openstack-trove00:05
*** jlucci has quit IRC00:20
*** jlucci has joined #openstack-trove00:20
*** jlucci has quit IRC00:36
*** krow has joined #openstack-trove00:40
*** asalkeld has left #openstack-trove00:41
*** yogeshmehra has joined #openstack-trove00:55
*** yogeshmehra has quit IRC01:02
*** nosnos has joined #openstack-trove01:05
*** erkules_ has joined #openstack-trove01:31
*** erkules has quit IRC01:34
*** robertmy_ has joined #openstack-trove01:40
*** robertmyers has quit IRC01:40
*** yogeshmehra has joined #openstack-trove01:59
*** yogeshmehra has quit IRC02:03
*** matsuhashi has quit IRC02:16
*** matsuhashi has joined #openstack-trove02:21
*** matsuhashi has quit IRC02:29
*** matsuhashi has joined #openstack-trove02:30
*** yogeshmehra has joined #openstack-trove03:00
*** dmakogon has quit IRC03:01
*** dmakogon has joined #openstack-trove03:01
*** yogeshmehra has quit IRC03:04
*** shivamS has joined #openstack-trove04:00
*** yogeshmehra has joined #openstack-trove04:01
*** yogeshmehra has quit IRC04:05
*** asalkeld has joined #openstack-trove04:32
*** asalkeld has left #openstack-trove04:32
*** vipul-away is now known as vipul04:38
*** zacksh_ has joined #openstack-trove04:42
*** shivamS has quit IRC04:47
*** zacksh has quit IRC04:49
*** shivamS has joined #openstack-trove04:49
*** shivamS has quit IRC04:50
*** shivamshukla has joined #openstack-trove04:59
*** SushilKM has joined #openstack-trove05:21
*** robertmyers has joined #openstack-trove05:43
*** robertmy_ has quit IRC05:43
*** yogeshmehra has joined #openstack-trove05:45
*** matsuhas_ has joined #openstack-trove05:57
*** matsuhashi has quit IRC05:58
*** nosnos_ has joined #openstack-trove05:58
*** nosnos has quit IRC05:59
*** robertmy_ has joined #openstack-trove06:30
*** robertmyers has quit IRC06:32
*** rushiagr has joined #openstack-trove06:35
*** matsuhas_ has quit IRC06:57
*** nosnos has joined #openstack-trove07:02
*** nosnos_ has quit IRC07:02
*** robertmyers has joined #openstack-trove07:05
*** robertmy_ has quit IRC07:05
*** matsuhashi has joined #openstack-trove07:05
*** yogeshmehra has quit IRC07:16
*** rushiagr has quit IRC07:36
*** matsuhashi has quit IRC07:40
*** rushiagr has joined #openstack-trove07:41
*** matsuhashi has joined #openstack-trove07:42
*** matsuhashi has quit IRC07:42
*** matsuhashi has joined #openstack-trove07:44
*** matsuhashi has quit IRC07:45
*** matsuhashi has joined #openstack-trove07:48
*** matsuhashi has quit IRC07:48
*** rushiagr has quit IRC08:07
*** matsuhashi has joined #openstack-trove08:13
*** yogeshmehra has joined #openstack-trove08:17
*** yogeshmehra has quit IRC08:21
*** robertmy_ has joined #openstack-trove08:27
*** robertmyers has quit IRC08:27
*** yogeshmehra has joined #openstack-trove08:27
*** yogeshmehra has quit IRC08:31
*** cweidenk1ller has quit IRC08:57
*** cweidenkeller has quit IRC08:58
*** ppenjoy has joined #openstack-trove09:13
*** yogeshmehra has joined #openstack-trove09:28
*** yogeshmehra has quit IRC09:32
*** ppenjoy has left #openstack-trove09:34
*** krow has quit IRC09:40
*** rushiagr has joined #openstack-trove10:10
*** SushilKM has quit IRC10:21
*** rushiagr_ has joined #openstack-trove10:26
*** rushiagr has quit IRC10:26
*** rushiagr_ is now known as rushiagr10:26
*** yogeshmehra has joined #openstack-trove10:29
*** ikhudoshyn has quit IRC10:32
*** yogeshmehra has quit IRC10:33
*** ikhudoshyn has joined #openstack-trove10:33
*** PradeepChandani has joined #openstack-trove10:57
openstackgerritAndrey Shestakov proposed a change to openstack/trove: Add support of UUID in flavors Removed int() conversion from flavors  https://review.openstack.org/4873511:09
*** rushiagr has quit IRC11:11
*** asalkeld has joined #openstack-trove11:29
*** yogeshmehra has joined #openstack-trove11:30
*** yogeshmehra has quit IRC11:35
*** rushiagr has joined #openstack-trove11:46
*** SushilKM has joined #openstack-trove12:04
*** pdmars has joined #openstack-trove12:14
*** SushilKM has quit IRC12:16
*** SushilKM has joined #openstack-trove12:17
*** yogeshmehra has joined #openstack-trove12:30
*** SushilKM has quit IRC12:31
*** yogeshmehra has quit IRC12:35
*** ppenjoy has joined #openstack-trove12:42
*** robertmy_ has quit IRC12:44
*** ppenjoy has left #openstack-trove12:44
*** rushiagr has quit IRC12:49
*** jcru has joined #openstack-trove13:12
*** nosnos has quit IRC13:13
*** kevinconway has quit IRC13:13
*** rnirmal has joined #openstack-trove13:15
*** radez_g0n3 is now known as radez13:19
*** openstackgerrit has quit IRC13:22
*** openstackgerrit has joined #openstack-trove13:22
*** kevinconway has joined #openstack-trove13:32
*** haomaiwang has quit IRC13:32
openstackgerritAndrey Shestakov proposed a change to openstack/trove: Add support of UUID in flavors Removed int() conversion from flavors  https://review.openstack.org/4873513:33
*** amytron has joined #openstack-trove13:43
*** Barker has joined #openstack-trove13:53
*** robertmyers has joined #openstack-trove14:03
*** demorris has joined #openstack-trove14:12
*** jlucci has joined #openstack-trove14:31
*** yogeshmehra has joined #openstack-trove14:32
*** yogeshmehra has quit IRC14:38
*** adrian_otto has joined #openstack-trove14:42
*** datsun180b has joined #openstack-trove14:46
*** jmontemayor has joined #openstack-trove14:53
*** adrian_otto has quit IRC14:56
*** adrian_otto has joined #openstack-trove14:57
*** jlucci1 has joined #openstack-trove15:04
*** Barker has quit IRC15:06
*** jlucci has quit IRC15:07
*** Barker has joined #openstack-trove15:11
openstackgerritMonty Taylor proposed a change to openstack/trove: Update from global requirements  https://review.openstack.org/4898615:16
*** adrian_otto has quit IRC15:18
hub_capi will be merging this when robots +1 ^ ^15:20
*** paul_lodronio has joined #openstack-trove15:21
*** matsuhashi has quit IRC15:25
*** shivamshukla_ has joined #openstack-trove15:31
*** tanisdl has joined #openstack-trove15:33
ikhudoshynhub_cap: Hi, looks like there are busy days around?15:36
hub_capHAH yes ikhudoshyn15:37
isviridovhub_cap, #link https://review.openstack.org/48986 does it mean that we can't use mockito anymore?15:37
ikhudoshynhow do you find new ios? (u seem to be the only one who cares<)))15:37
ikhudoshyn,))15:37
hub_capikhudoshyn: i hate it15:38
ashestakovhi15:38
ashestakovhttps://review.openstack.org/#/c/48735/ review pls15:38
hub_capisviridov: im pretty sure mordred just removed ones we didnt use15:38
ashestakovhub_cap: any luck with service types?15:38
ikhudoshynhub_cap: just like me, its kinda 'god plz let me unsee this')15:38
hub_capnot saying we "cant" use them15:38
hub_capikhudoshyn: yes i know15:38
openstackgerritMonty Taylor proposed a change to openstack/trove: Update from global requirements  https://review.openstack.org/4898615:39
mordredoh. blech. I guess I should exclude test-requirements from that patch15:40
ikhudoshynhub_cub: we now seem to be cool with Ed, i won't stay in his way. Now I'm doing some Mongo support. But before I'd like to merge some refactorings in GA. Just to extract some generic stuff from mysql specific code15:40
ikhudoshynIf u dont mind15:40
mordredbut yes. you guys should have getting off of mockito and proboscis on your todo list15:40
hub_capashestakov: not yet its been a busy / frustrating wk15:40
hub_capmordred: dont worry ;)15:40
mordredor otherwise convincing the rest of openstack to move to them15:40
*** adrian_otto has joined #openstack-trove15:41
openstackgerritMonty Taylor proposed a change to openstack/trove: Update from global requirements  https://review.openstack.org/4898615:41
hub_capmordred: /me is a standard whore and is working to make things like this standard... proby has been on my list, and now mockito is15:41
mordredthere. left test-requirements out of that change, because I don't really care about that right now15:41
ashestakovhub_cap: maybe we can schedule time for review/commnts for service types?15:41
hub_capashestakov: im not toucing code today and ive got a full day15:42
hub_capive got a queue with your and dmakogon reviews in it15:42
hub_capthey will be done today. period.15:42
mordredhub_cap: I think you're just a whore in general :)15:42
ashestakovhub_cap: thanks15:43
ikhudoshynhub_cup: plz add this https://review.openstack.org/#/c/48435/ to your queue. There is more to come, but I'd like to do it piece by piece15:43
hub_capmordred: u know me too well15:43
openstackgerritMonty Taylor proposed a change to openstack/trove: Update from global requirements  https://review.openstack.org/4898615:43
mordredone last time15:43
hub_capikhudoshyn: aye15:43
mordredmaybe that will pass15:43
ikhudoshynhub_cap: thanks15:44
hub_capwe shall see if you pass our unstandardness with your review mordred15:44
* mordred punches hub_cap with a stick15:44
hub_capi mean, its like a gate of eliteness for trove. sure u can handle the rest of openstack, but have you seen THIS!!?!?!?!15:44
* hub_cap vomits15:44
mordredhub_cap: oh, you think you're the special ones? dude. SO MANY SNOWFLAKES15:45
hub_capyup mordred dont put me on your tongue i might melt (wow that re-reads like a mordred comment)15:45
datsun180bi don't know why i'm dreading submitting a change to devstack so much15:48
hub_capdatsun180b: dont worry... be happy....15:48
* hub_cap is so cliché15:48
datsun180boh i'm pretty happy now. think i got the db access thing for conductor nailed this morning15:48
hub_capdatsun180b: its not that hard, the hard part is getting 2 people to +2 it15:48
hub_capwoot datsun180b15:49
datsun180bjust have to make sure i can get an instance to go active without the logs screaming tracebacks at me15:49
datsun180bi've gotten the restart/retry process down to two scripts: ./IDDQD and then ./IDKFA15:49
ikhudoshyndatsun180b: hi, are there any news with conductor?15:50
*** ashestakov has quit IRC15:50
datsun180bikhudoshyn: you just read it15:51
hub_caplol datsun180b15:51
ikhudoshynthere's another guy who cant wait for it, i'll better go and teach him these spells15:51
ikhudoshyn)15:52
datsun180bikhudoshyn: if i can get an instance to go ACTIVE in this current test i'm running I'll submit my code reviews. That should be today15:52
ikhudoshynoh! that will be great15:53
ikhudoshynmay the force be with u15:54
*** demorris has quit IRC15:57
*** jmontemayor_ has joined #openstack-trove16:02
*** Nate2 has quit IRC16:04
*** jmontemayor has quit IRC16:04
*** tanisdl has quit IRC16:09
*** tanisdl has joined #openstack-trove16:10
*** Nate1 has joined #openstack-trove16:11
*** Nate2 has joined #openstack-trove16:14
*** Nate1 has quit IRC16:14
*** rnirmal has quit IRC16:15
cp16nethub_cap: you mentioned you dont like the new ios?16:18
cp16nethttp://www.youtube.com/watch?v=JTpXVv-DaBQ16:24
cp16netnew ios brings kids to tears16:24
cp16netlol16:24
juiceoh-my-goodness16:26
juiceman - the whiney, tired 5 year old was not in the user persona set at apple16:26
* hub_cap watches cp16net16:26
hub_capwait16:26
* hub_cap watches, cp16net16:26
cp16netlol16:27
hub_captricky tricky commas16:28
hub_capOMG thats the best 17 seconds ever16:28
cp16nethahaha16:29
cp16net:)16:29
*** erkules_ is now known as erkules16:31
cp16netjuice: isnt that the truth...16:32
*** ashestakov has joined #openstack-trove16:33
hub_capcp16net: juice this baby is way cooler http://www.youtube.com/watch?v=kOb1jesGECQ16:42
cp16netlol weird baby16:43
hub_capROUGH TOOTIN BABY16:44
juicei'm impressed that baby has such good balance on the hamper16:45
juiceand the rhymes are superb16:46
juiceassuming it was free-style16:46
hub_capits gotta be freestyle16:48
*** jmontemayor_ has quit IRC16:59
*** esp has joined #openstack-trove16:59
*** yidclare has joined #openstack-trove17:00
*** yogeshmehra has joined #openstack-trove17:03
*** Nate2 has quit IRC17:06
*** KennethWilke has joined #openstack-trove17:06
*** jmontemayor has joined #openstack-trove17:08
*** KennethWilke has quit IRC17:09
*** isviridov_ has joined #openstack-trove17:11
hub_capSlickNik: are the docs you started not on docs.o.o?17:13
hub_capi dont see them (http://docs.openstack.org/)17:13
espI think SlickNik is out today.17:19
esphub_cap: could you please take a look at these at your convenience?  https://review.openstack.org/#/c/48535/   https://review.openstack.org/#/c/47206/17:24
*** Nate1 has joined #openstack-trove17:26
*** isviridov_ has quit IRC17:26
hub_capesp: k17:26
*** isviridov__ has joined #openstack-trove17:26
esphub_cap: thx!17:26
*** adrian_otto has quit IRC17:26
*** jmontemayor has quit IRC17:28
*** demorris has joined #openstack-trove17:29
*** zigo_ has joined #openstack-trove17:32
zigo_Hi there! I'm trying to package Trove for Debian. I was wondering, what is trove-server for? Is this a central server, somehow???17:33
zigo_Come on guys, wake up! :)17:35
*** isviridov_ has joined #openstack-trove17:35
juicehello zigo_17:35
*** adrian_otto has joined #openstack-trove17:35
juicewhere do you see a reference to trove-server?17:35
zigo_juice: Hi.17:35
zigo_juice: There's bin/trove-server in the source code.17:36
juicewe have trove-api and trove-taskmanager and trove-guestagent17:36
hub_capzigo_: hi17:36
zigo_juice: Thanks a lot.17:36
hub_capzigo_: trove-server is only for testing17:36
hub_capjust like juice says, the rest are either old artifacts or specifically for testing17:36
*** isviridov__ has quit IRC17:37
zigo_For the moment, I have python-trove, trove-common, trove-api, trove-guestagent and trove-taskmanager as .deb files. Does this sound right?17:37
hub_captrove-server is kinda like the other services, where you can spin up "all" services in one, like keystone / glance ( i dont know if they do that anymore, to tell u the truth...)17:37
hub_capzigo_: thats how rackspace does it internally ;)17:37
hub_capiirc17:38
zigo_Oh, they already did some packaging work? Interesting.17:38
hub_capwell internally17:38
zigo_It'd be nice if Rackspace was sharing a bit more ... :)17:38
hub_capand likely wrong (i did some of it...)17:38
zigo_I mean, on the packaging side.17:38
datsun180bwe're trying17:38
hub_capzigo_: ++17:38
zigo_datsun180b: Ah, well, then get in touch with me! :)17:38
hub_capdatsun180b: ya zigo_ is specific about packaging17:39
zigo_datsun180b: I'm the guy maintaining all of OpenStack in Debian.17:39
datsun180bwell i was speaking more generally17:39
hub_capdatsun180b: Thomas Goirand (look up his posts in openstack)17:39
datsun180byeah /whois helps there17:40
zigo_FYI guys, I'm currently working on Trove, then TrippleO and Marconi, since I'm done with the rest of (well, let's hope I am... :) )17:40
zigo_I guess I'll have more questions later on.17:40
zigo_Anyway, thanks.17:40
hub_capzigo_: great! ping us w/ questions17:42
hub_capand ill see u in HK17:42
hub_capnot sure if u remember but we met in portland outside17:42
zigo_hub_cap: I do remember I met some "reddwarf" people yes! :)17:42
zigo_Not sure I would remember your face (met too many people).17:43
hub_capi know zigo_, there is one of you, so i rmember heh17:43
juicezigo_ I might hit you up on packaging issues with debian vs pypi17:43
zigo_hub_cap: I for sure will be happy to see you guys again. HK is like 2 hours away from my home ! :)17:43
*** isviridov__ has joined #openstack-trove17:43
hub_capyup i knew you were in china i dont know where.. so ya ill see you in HK :)17:43
juiceright now there is a nice unhealthy mix of the two types in openstack and it seems to cause recurring version issues17:43
*** adrian_otto has quit IRC17:44
zigo_I live in Shanghai.17:44
yogeshmehrahubcap: i need few minutes on trove/heat17:45
*** isviridov_ has quit IRC17:45
*** isviridov__ has quit IRC17:48
hub_capyogeshmehra: yes lets chat here17:48
yogeshmehrasure17:48
yogeshmehrawas just checking..17:49
yogeshmehratrove/heat, is it in progress...17:49
yogeshmehrai was not able to get the instances active...17:49
*** jmontemayor has joined #openstack-trove17:49
hub_capyogeshmehra: no one is working on it exactly right now17:49
yogeshmehraand they are not reachable ssh17:49
hub_capcan you ping the IPs?17:49
hub_capdid you run the iptables MASQUERADE command?17:50
hub_capjust making sure of teh basics first17:50
yogeshmehrahub_cap: i did run the iptables MASQ... cmd17:50
yogeshmehrayeah, makes sense...17:50
yogeshmehraat one time, they were pingable...and nother, they were not17:50
hub_capok cool17:50
hub_capdid you add the heat key?17:51
hub_capi forgot to add this in trove-integration17:51
hub_capyou might need to post a review for trove-integration17:51
hub_capand add this17:51
yogeshmehrayeah, heatkey is done...17:51
hub_capok cool17:52
zigo_OUTCH !17:52
hub_captry ssh ec2-user@ip17:52
zigo_signing_dir = /tmp/keystone-signing-nova17:52
hub_capzigo_: ya that makes sense right ;) ;)17:52
zigo_This kind of joke generated a CVE for Nova! :)17:52
hub_capcan u file a bug for that zigo_?17:52
zigo_Ok.17:53
hub_capOUCH17:53
yogeshmehrahub_cap: it says cannot communicate on port 2217:53
hub_capnot a good joke then!!17:53
hub_capyogeshmehra: thats odd.. i have not tested in a while, can u do me a favor?17:53
hub_capand you just try to create a instance using heat w/o trove on your setup17:53
hub_capusing our image17:53
hub_capand see if it has the same result17:53
yogeshmehrahub_cap: creating an instance and even an instance group is success out of trove...directly using the heat api17:54
*** isviridov_ has joined #openstack-trove17:54
yogeshmehraimage from within trove and using it to create an instancegroup works...17:55
hub_capcan you post the yaml you send to heat?17:55
yogeshmehrayeah...17:55
hub_capoh this is nice... we should change our setup to use this17:55
hub_caphttps://bugs.launchpad.net/heat/+bug/110134717:55
yogeshmehrait is: https://github.com/openstack/heat-templates/blob/master/cfn/F17/InstanceGroup.template17:55
*** rnirmal has joined #openstack-trove17:55
yogeshmehrathis is the template i used for creating a 2 node deployement of an image from trove...17:56
yogeshmehraactually, the heat stack and the instance within the stack is visisble....but it doesn't come to ACTIVE state..17:57
hub_capbut could you ssh in yogeshmehra?17:58
hub_capthats the issue at hand17:58
yogeshmehratrue...i couldn't17:58
hub_captry to use a vanilla heat image17:59
hub_captake our image and trove out of teh equation all together17:59
hub_capmake sure you have heat setup properly17:59
yogeshmehrahubcap: i have it setup...17:59
yogeshmehrai tested it using trove image itself...it did come up and was sshable...17:59
yogeshmehraTemplate:  https://github.com/openstack/heat-templates/blob/master/cfn/F17/InstanceGroup.template and  mysql image from trove...18:00
hub_caplol @esp, you hit the RC1 oslo bug18:00
esphmm18:00
espdo I win a prize?18:00
esptrip to hong kong?18:01
hub_capyou win a wait18:01
espawesome.  I win a lesson in patience.  that's a more zen way to put it.18:02
hub_capesp: look @ the comment i left18:02
espk18:02
*** jmontemayor has quit IRC18:04
espah, ok. thx for clarifying!18:04
*** isviridov_ has quit IRC18:05
*** demorris_ has joined #openstack-trove18:06
yogeshmehrahub_cp: SOS.... :-)18:06
SlickNikhey gusy18:06
SlickNikguys*18:06
yogeshmehrai'll work out a fresh one and send you some logs..18:06
yogeshmehraoffline..18:06
SlickNikhub_cap: travelling today, so will be on and off.18:07
*** isviridov_ has joined #openstack-trove18:07
yogeshmehraSlicknick: thanks..18:07
SlickNikWhat's up yogeshmehra?18:07
SlickNikhub_cap: the docs that I put on are up on o.o18:07
*** jmontemayor has joined #openstack-trove18:07
SlickNikhttp://docs.openstack.org/18:07
*** demorris has quit IRC18:07
*** demorris_ is now known as demorris18:07
SlickNikclick on Python Developer Documentation18:08
yogeshmehraoops...i misread u...18:08
hub_capohhhhhhhh SlickNik thank you18:08
hub_capi wsnt sure where18:08
yogeshmehraslicknick: forget thanks... :-)18:08
*** SnowDust has joined #openstack-trove18:09
SnowDustHeRe I CoMe !18:09
SnowDusthello buddies ..18:10
yogeshmehrasnowdust: hey18:10
SnowDustyogeshmehra: hi ! !18:11
yogeshmehrai am figuring out the trove/heat...18:12
yogeshmehrawill continue..18:12
SnowDustec2_user@ip wont work18:12
SnowDustno route to host is the answer :)18:13
SnowDustwhen u try ssh18:13
SnowDustthat all means .. the port is blocked ? ?18:13
yogeshmehrais the instance pingable18:13
SnowDustnope18:13
yogeshmehrafor u..18:13
SnowDustonly .. nova shows active status18:13
SnowDustwith ip18:13
yogeshmehrait was for me once and not later..18:13
SnowDusthmm ..18:13
SnowDustbtw ... i read somewhere we have to make jeos images for heat ?18:15
SnowDustis that necessary ?18:15
*** isviridov_ has quit IRC18:16
yogeshmehraour vertica and mysql images work with heat18:16
yogeshmehrai booted them up using anotehr het template..18:16
yogeshmehrabut all this without trove..18:16
yogeshmehrausing heat apis18:16
yogeshmehraper vipul we should check the sec groups as well18:17
yogeshmehrafor port 22 rule..18:17
SnowDusttx !18:18
yogeshmehrai am trying a new one..18:19
hub_capSnowDust: hello!18:19
SnowDusthi hub_cap18:19
*** isviridov_ has joined #openstack-trove18:19
hub_capi see you asking questions all weekend, sorry that no one replied SnowDust. how are things coming?18:21
*** isviridov_ has quit IRC18:21
SnowDusti made my way upto .. the looping calls .. end of heat orchestration :)18:22
SnowDustthen the box never comes to active state :)18:22
SnowDustand it timesout ( taskmanager )18:22
SnowDustthe instance is shown active in nova ..18:22
SnowDustheat says the stacking is complete18:22
SnowDust:) and with that me and yogeshmehra are trying to solve that ..18:23
hub_capcan you SSH into it SnowDust?18:24
SnowDustno .. as mentioned no route to host18:24
SnowDusti tried .. the vanilla installs .. no cocktail :d18:24
SnowDuststill facing that ..18:25
hub_capso even vanilla heat w/o any trove related stuff gives you no ssh ?18:26
hub_capare you using the trove image?18:26
hub_captry ssh ec2-user@IP too18:26
yogeshmehrahub_cap: without trove it does give ssh....18:27
hub_capok18:27
hub_capare you using cloud environments? like i could have a ssh into the machine to see whats going wrong/ or is it local to your laptops?18:28
hub_capbrb18:28
SnowDusti meant .. trove vanilla with heat configurations enabled .. in /etc/trove-taskmanager.conf  and hitting18:29
SnowDust./redstack rd-client instance create ...18:30
SnowDustthat will run all the heat functions .. in  /trove/trove/taskmanager/models.py18:30
SnowDustand .. will timeout .. during the poll activity to check machine status getting active18:30
SnowDustfinally when i check ..18:30
SnowDustnova says box is active18:31
SnowDustheat says stacking is complete18:31
SnowDustand ssh says .. no route to host ! :-)18:31
yogeshmehrasnowdust: per hub_cap, he wanted to know if without trove, the heat is functional18:31
yogeshmehraand it is...18:31
SnowDustyeah should be :) ..18:32
SnowDustor #heat will have meltdown ...18:32
*** Barker has quit IRC18:33
*** jmontemayor has quit IRC18:34
*** isviridov_ has joined #openstack-trove18:35
*** isviridov_ has quit IRC18:37
*** Barker has joined #openstack-trove18:38
*** krow has joined #openstack-trove18:41
*** jlucci1 has quit IRC18:44
*** openstackgerrit has quit IRC18:47
*** openstackgerrit has joined #openstack-trove18:47
*** isviridov_ has joined #openstack-trove18:50
*** shivamshukla_ has quit IRC18:51
*** isviridov_ has quit IRC18:52
*** krow has quit IRC18:55
*** tanisdl has quit IRC18:55
redthruxhey vipul, SlickNik - i wanted to get your take on https://review.openstack.org/#/c/48188/18:55
*** SnowDust has quit IRC18:56
*** paul_lodronio_ has joined #openstack-trove18:57
*** vipul has quit IRC18:57
*** vipul has joined #openstack-trove18:58
*** jlucci has joined #openstack-trove18:59
*** paul_lodronio has quit IRC18:59
*** paul_lodronio_ is now known as paul_lodronio18:59
*** jmontemayor has joined #openstack-trove19:00
*** krow has joined #openstack-trove19:03
*** radez is now known as radez_g0n319:05
*** tanisdl has joined #openstack-trove19:05
*** isviridov_ has joined #openstack-trove19:06
*** mmcdaris has joined #openstack-trove19:07
*** isviridov_ has quit IRC19:08
*** Nate1 has quit IRC19:09
hub_capashestakov: bad news19:14
hub_capafter thinking a bit more about it19:14
hub_capthe change to flavors will cause a contract change19:14
hub_capwhich means in order for it to become a string (its an int now)19:14
hub_capwe will have to rev the api19:14
*** paul_lodronio has quit IRC19:17
*** paul_lodronio has joined #openstack-trove19:17
ashestakovhub_cap: which contract?19:17
*** isviridov_ has joined #openstack-trove19:22
*** isviridov_ has quit IRC19:25
demorrisashestakov: the current API is running in production at RAX, so any non-additive changes to the V1.0 API will break the contract19:25
demorrisit means that any changes that change it, have to be on V1.1 or V2.0 etc, thats all19:25
*** KennethWilke has joined #openstack-trove19:26
demorrisit was inevitable that the project gets to this point, Nova has been through the same thing and it just means that Trove needs a strategy for API versioning, like all other openstack API's19:27
ashestakovhm, sounds bad when some contract restricts opensource19:27
demorrisit's not restricting it at all19:27
*** tanisdl has quit IRC19:27
demorrischanges can be made, you just can't change existing contracts19:27
demorriswhen you version an API, people then write bindings (python, C++, Java, etc.) and UI's, like horizon...19:28
vipulfwiw, I believe flavor "id" comes back as a string in the get/list instances, but comes back as an Int in flavor-list19:28
demorrisif you change that, then you break those19:28
datsun180bit's more of a social contract: users already have expectation X from event Y19:28
pdmarsand really, it has nothing to do with RAX, it's a contract between trove and its users19:28
datsun180bif Y is modified so that X is no longer fulfilled, we have broken the contract19:29
demorriscorrect, other providers, like HP could easily have this in production19:29
datsun180bif we implement new event Z, there was no previous expectation from it, and so we aren't necessarily breaking the contract19:29
demorrisvipul: not sure where y'all are with that :)19:29
vipuldemorris: :)19:30
demorrisdatsun180b: right, i consider those additive changes19:30
datsun180bi supposed if we offered a catalog API call then even additive changes could be considered breaky19:30
demorriswe have seen the flavor id stuff change before (without catching it) and it breaks downstream users of Trove19:30
datsun180bbut at that point i'm getting into hypotheticals19:30
hub_caphttp://docs.rackspace.com/cdb/api/v1.0/cdb-devguide/content/POST_createInstance__version___accountId__instances_.html19:31
hub_cap"flavorRef": 1,19:31
hub_capputting quotes around that breaks the contract19:31
hub_cap"flavorRef": "1" != "flavorRef": 119:31
datsun180bthe flavor id type is a good example, we can't guarantee that someone wasn't relying that our flavors were ints in the json19:32
demorrisyeah, and going back to what ashestakov, the point is not to be overly restrictive and limiting the project, these changes can be made, but the API needs to rev to do it, thats all19:32
demorristhere are extremes to this too, the AWS approach (which is like the MS approach), is avoid revving the API ever19:34
*** jmontemayor has quit IRC19:34
kevinconwaymaybe instead of revving the API we should just rename the project when we make changes that violate the contract19:35
kevinconwaythat sounds easier19:35
*** jmontemayor has joined #openstack-trove19:36
datsun180bkevinconway: let's start by renaming you19:36
hub_capkevinconway: LOL19:36
*** tanisdl has joined #openstack-trove19:37
*** isviridov_ has joined #openstack-trove19:38
*** isviridov__ has joined #openstack-trove19:38
*** tanisdl_ has joined #openstack-trove19:40
*** isviridov__ has quit IRC19:40
*** tanisdl has quit IRC19:41
*** tanisdl_ is now known as tanisdl19:41
ashestakovok, how we can make changes in api? can we split next version api?19:41
hub_capwe make a 1.1 api ashestakov19:42
hub_capevertying in 1.1 defaults back to 1.0 compatibility except for the changes19:43
ashestakovis it already done?19:43
hub_capthen we need 2x services, one in 1.1 and one in 1.019:43
hub_capnope19:43
hub_capits never been needed19:43
hub_capthe otehr services have it though (nova, glance...)19:43
demorrishub_cap: and those services dropped the point release concept19:43
demorrisNova went to just V1, V2, V3 naming convention19:43
demorrisi believe19:43
*** isviridov__ has joined #openstack-trove19:43
hub_capashestakov: if u can make it so its an int or a string19:44
hub_capthen itll work19:44
hub_capright demorris>19:45
hub_cap>19:45
hub_cap?19:45
hub_capHAH19:45
*** Nate1 has joined #openstack-trove19:45
*** Nate1 has joined #openstack-trove19:46
demorrisI guess you could make the json accept both right?19:46
demorrisi am not sure if that breaks any conventions19:47
kevinconwayhub_cap: doesn't keystone serve two api revs from the same process?19:47
hub_capyes thats how all the services work kevinconway19:47
hub_capbut its a question of do we want to do a ton of work for a smalll change if we can get _around_ it19:48
ashestakovcan we do type conversion for flavors?19:49
demorrishub_cap: yeah, this change does not strike me as a sole reason to rev the API, so if there is a way to support it without breaking the contract, great19:49
*** isviridov__ has quit IRC19:50
*** jlucci1 has joined #openstack-trove19:53
ashestakovwe can accept int values as well as strings, but do str(flavorid) for it19:53
*** isviridov__ has joined #openstack-trove19:53
hub_capashestakov: if we can accept ints and strings we should be able to tell the type from the json19:55
*** isviridov__ has quit IRC19:55
hub_capthe thing we have to avoid is this19:55
hub_capcurrently you pass "flavorRef": 119:55
hub_capif it becomes "flavorRef": "1"19:55
hub_capits a contract change, going from an int to a string19:55
hub_capeven tho int("1") evals to 119:56
*** jlucci has quit IRC19:56
ashestakovi mean you still be able to pass "flavorRef": 1, but on server part it will convrt to str()19:56
hub_capashestakov: but json wont allow19:56
hub_cap"flavorRef": something_without_quotes_thats_not_an_int,19:57
hub_capso19:57
*** jlucci1 has quit IRC19:57
hub_cap"flavorRef": 550e8400-e29b-41d4-a716-44665544000019:57
hub_capwould fail in json19:57
hub_capbut19:57
hub_cap"flavorRef": "550e8400-e29b-41d4-a716-446655440000" would not19:57
hub_capok brb gotta watch my baby for a few minutes19:58
ashestakovis it covered by contract how you should pass values? with quotes or not19:58
*** isviridov__ has joined #openstack-trove19:58
*** isviridov__ has quit IRC20:01
datsun180bashestakov: that would be in the schema of an individual request or response, so yes20:01
datsun180bone problem (in the case of flavor ids) is that xml doesn't so much have the types that json does, so whether flavor_id was a string or int was irrelevant so there was skew between our json and xml responses20:02
*** isviridov__ has joined #openstack-trove20:05
*** isviridov__ has quit IRC20:07
hub_capif its possible, id allow both string and int20:10
hub_capthen we wont have to rev the api20:10
*** isviridov__ has joined #openstack-trove20:10
hub_capis that possible w the schema code?20:10
*** isviridov__ has quit IRC20:10
kevinconwayhub_cap: is it even possible to do both and not break the API contract?20:13
kevinconwaybecause then it would be possible to get strings back out of the API20:13
hub_capif its an int, itll return as such20:13
hub_capif its a string, it will return as such20:13
kevinconwayright, so your client has to know what got put in originally20:13
hub_capim not sure that breaks the contract, due to the use case for each20:14
hub_capi dont think thats the case20:14
hub_capthe server needs to know what it is in order to properly represent it20:14
kevinconwayso if i load up my v1 client and it gets a UUID as the flavorRef, isn't that exactly what you're trying to prevent?20:14
datsun180bargh, i can't seem to get nova to play nice if i murder all screen sessions and try to install & kick-start again20:15
hub_capkevinconway: if your installation uses UUID's then you would expect them20:15
hub_capif it uses ints, you would expect those20:15
hub_capif its using ints and strings... we could have issues20:15
kevinconwayso you're saying it becomes a configuration option?20:15
kevinconwaywhat i mean is that if I point my v1 client at any openstack deploy i would expect an integer back for flavorRef20:16
hub_caphttps://gist.github.com/hub-cap/676955020:17
hub_capremember we are talking creates here, so you would be submitting the flavorRef20:18
*** jmontemayor has quit IRC20:18
hub_capand the list flavors will return json, and the id will be str/int20:18
datsun180bExplicit type checking in Python? That's a paddlin'.20:18
hub_capand then you take that value and pass it in to the create20:18
kevinconwaybut if the id is ever str that would be an API break20:18
hub_capdatsun180b: care to write the compatibility layer for v1.1 ?20:18
hub_capkevinconway: only for instances that require ints20:18
datsun180bWell it's not like you actually wrote if type(flavor_ref) == int20:19
hub_capand the flavor list will return ints if thats the case20:19
*** jmontemayor has joined #openstack-trove20:19
*** radez_g0n3 is now known as radez20:19
kevinconwayi guess i'm confused then. if we can have strings then why can't we have strings?20:19
juicejust to be clear here - everything to nova is a string20:19
juicewith respects to flavor id20:19
juiceonly in trove do we cast this is an int20:20
juicewe store our reference (prior to ashketov_) change as an int20:20
datsun180bBut since we made that distinction at one point in v1 we have to keep playing that game if we're going to claim we're still in v1. At least, that's what I understand from this. And in this case, the whole argument is moot when we accept and serve the request in XML20:21
juiceso there is a mismatch currently between nova and trove20:21
hub_capdatsun180b: correct, but who does that anyway ;)20:21
hub_capjuice: correct20:21
juicedatsun180b: this become tricky because we won't know whether they give us 1 or "1"20:21
datsun180bhub_cap: we have to leave the door open! what if they want an atom feed20:21
juicewe could by convention do something like hub_cap proposed in his gist20:21
datsun180bor they send us GET http://legitimate/url/to/api/function.json20:22
juiceor we can add a new field - flavor_id_description20:22
juiceall strings go in description20:22
juiceall ints continue to go into the current field20:22
hub_capjuice: naw its still the id field in nova20:23
juiceover time we phase out the old int field20:23
datsun180bAt one point we'll probably end up throwing the switch and flavors/<integer> will just 5XX20:23
hub_capwell we just need to rev the api to 1.1 and have backwards compat to 1.0 w/ a int, which is worst case20:23
datsun180ber, 4XX, user bad20:23
hub_capdatsun180b: yes thats the only problem20:24
*** Nate1 has quit IRC20:24
hub_capis that the error returned will likely change20:24
hub_capunless we add a flag (per kevinconway) to say "we only allow ints"20:24
juicei like my plan the best :)20:24
hub_capwhich id rather rev teh api at that point20:24
cp16netwow....20:24
datsun180bmy last job had a problem when they wanted to migrate to a new platform and shake up the api in a big way20:24
cp16nethttp://youtu.be/Q0W0MR6Ybgk?t=26s20:24
hub_capi dont think its hella work to reve the api20:24
datsun180bafter lots of customer education and such eventually they just built a monster and paraded the new api wearing the skin of the old api20:25
hub_capok so, executive decision20:25
hub_caprev the api20:25
hub_capits too hacky to maintain compat20:25
datsun180beventually they swapped out, i understand, but there was an interim20:26
hub_capif we rev the api, then rax (and hp) can decide when they go to v1.120:27
hub_capor tehcnically probably v2 :)20:27
hub_capill talk to some people who have rev'd the api's in nova20:27
datsun180bthis is kind of weird, but why do the screens in trove all start in /opt/stack/python-troveclient20:27
datsun180bwe must be missing a popd20:27
kevinconwayis this the only change we want for 1.1 or do we want to batch them for the rev?20:27
hub_capkevinconway: the changes just stay in v1.120:27
hub_capif we have a 2nd change, we put it in v1.1 w/ backwards compat20:28
hub_capthe rest of v1.1 is a passthru to v1.0 (acutally thats written backwards)20:28
vipulwhat happens to say /instances.. is that only in v1.0 or visible in 1.120:28
hub_capeverything is in 1.1, and all changes to the api20:28
vipuloh i guess you anaswered that20:28
hub_caplet me splain20:28
hub_capwell kinda20:28
*** Nate1 has joined #openstack-trove20:28
hub_capso everything is promoted to 1.1, and any calls to 1.0 are routed to 1.120:28
hub_capunless they have a explicit 1.0 service20:29
hub_capthats how i think itll work20:29
hub_capthen the 1.0 can just quote the int and push it (likely it wont even need to, python right!!)20:29
hub_cappush it to the 1.1 rev20:29
vipulhmm.. but everything is in 1.0 today.. so you'd move the current stuff to v1.1?20:29
hub_capitd be in both 1.0 and 1.120:29
hub_capthe v flag is in the paste.ini only20:30
vipuloh cuz you said "unless they have a explicit 1.0 service"20:30
hub_capso it really doesnt matter...20:30
hub_capcorrect20:30
vipulseems like everything woudl have a 1.0 service20:30
hub_capwell the common api_factory can define that i think20:31
hub_capso basically we need to figure it out :)20:31
hub_caplet me ask some people20:31
vipulyea i get the concept I think.. so not really a full Rev of the API20:31
vipuljust an extension.. dot release20:32
hub_capi think so20:32
hub_capmabye ;)20:32
hub_capcuz the other projects just use /v1 /v220:32
hub_capand default to v1.1 in the background20:32
vipulah ok20:32
hub_capso ll have to figure out how to go back to 1.020:32
hub_cap*we'll have to figure out20:32
hub_capthis will require a pretty massive rewrite id assume, of the api handling code20:33
* hub_cap wonders if its tiem to move to pecan/wsme in the process20:33
vipuleveryone's doing it :D20:34
hub_capit _is_ the future of OpenStack20:36
* hub_cap puts it on the todo list20:36
hub_capproblem is... adding flavors in horizon adds them as uuid's and ashestakov couldnt use them20:36
vipulouch20:37
vipulwe could do something crazy, like detect if it's an int or string in API code20:38
hub_capLOL vipul20:38
hub_capscroll up20:38
vipuloh20:38
vipul:P20:38
hub_caphttps://gist.github.com/hub-cap/676955020:38
hub_capafter chatting w/ kevinconway and co, it just became obviously hacky20:39
vipulwell then.. that should go in v1.020:39
datsun180bIs it worth it to make a distinction between what would go in a minor versus major version change20:42
hub_capit depends on how the other openstack projects do it20:43
hub_capthey dont seem to offer > 1 minor version20:43
datsun180blike requiring minor changes might just build on the previous version a la class APIv1_7(APIv1_6) but not hold that requirement for major versions20:43
datsun180bbut if the answer is lockstep then forget it20:43
datsun180bi think i'm getting caught up in irrelevant details while trying to help with this 1.0/1.1 situation20:44
hub_capthe answer is "the standards gods of OpenStack (mordred)" want us to keep in line.. and frankly i dont blame them20:45
hub_capthe family that plays together stays together!20:45
datsun180boh of course, so my musings are irrelevant as speculation20:45
lifelesshub_cap: openstack is basically semver20:45
lifelesshub_cap: but openstack has a nasty tendancy to backwards incompat changes in api servers every release20:46
hub_capi dont want to do that lifeless20:46
lifelesshub_cap: as features are dropped after deprecation periods20:46
datsun180bi'm not about to try to give you cat herding pointers20:46
hub_capand as much as i see they semver, the apis are only single major based :(20:46
lifelesssure20:46
hub_capso i guess they have just dropped their compat for the _last_ minor by now20:47
hub_capif they ever had it ;)20:47
hub_capand datsun180b fwiw, this is a 1.1 vs 1.0 thing20:48
*** ashestakov has quit IRC20:49
hub_capwe would have backward compat between 1.1 and 1.0 for this 'feature'20:49
datsun180byeah i'm trying to help but i'm all thumbs here20:50
hub_capthis will help for a general understanding http://semver.org/20:51
*** radez is now known as radez_g0n320:53
datsun180bwere you serious about that backward compatibility question earlier20:53
hub_caphmm what question?20:54
datsun180b<hub_cap> member:datsun180b: care to write the compatibility layer for v1.1 ?20:54
datsun180bfyi colloquy is terrible for irc20:54
hub_capahhhh datsun180b no i wasnt20:54
hub_capfocus on the conductor20:54
datsun180boh i'm focusing20:55
mordredhub_cap: what was the question?20:55
datsun180bif i could get this business to stop crying when i kill screen and restart it would speed things up, but right now i'm minutes from making sure i've got the db updated properly and then it's frantic code cleanup time20:56
mordredoh - API version20:56
hub_capmordred: "Have you ever drunk Baileys from a shoe?"20:56
hub_capno, boo on api version!20:56
mordredlifeless: I do not believe we are semver or even close to it for API versioning.20:56
mordredI think we may be getting close to thinking about wanting to be there for library stuff20:56
*** mordred has quit IRC20:57
*** mordred has joined #openstack-trove20:57
* datsun180b suppresses urge to suggest something ouroborean as a joke20:58
hub_cap:)20:58
hub_capmordred: we (Trove)  can still use it as a guideline21:00
hub_capi dont want to provide non compat to minor versions (but it seems like we, OpenStack, punt on that and just major rev everything)21:01
lifelessmordred: The intent I've seen on all reviews for apis is 'don't break it', 'new version if it would break it'21:01
lifelessmordred: which isn't that far off of semver, though I take your point21:01
mordredhub_cap: I think if you come up with a GOOD way to not screw people with your API versioning, no-one will be unhappy21:02
*** pdmars has quit IRC21:03
hub_capheh yes mordred21:03
*** jcru has quit IRC21:12
*** yogeshmehra has quit IRC21:31
*** isviridov_ has quit IRC21:32
*** adrian_otto has joined #openstack-trove21:33
*** robertmyers has quit IRC21:41
*** yogeshmehra has joined #openstack-trove21:45
*** Barker has quit IRC21:48
*** yogeshmehra has quit IRC21:58
hub_capvipul: https://review.openstack.org/#/c/48986/ <-- lets merge this22:06
*** amytron has quit IRC22:10
*** amytron has joined #openstack-trove22:10
*** datsun180b has quit IRC22:11
*** datsun180b has joined #openstack-trove22:11
*** paul_lodronio has quit IRC22:11
*** krow has quit IRC22:13
*** amytron has quit IRC22:17
*** rnirmal has quit IRC22:23
*** vipul is now known as vipul-away22:26
*** krow has joined #openstack-trove22:31
*** vipul-away is now known as vipul22:35
*** KennethWilke has quit IRC22:36
*** demorris has quit IRC22:38
*** jmontemayor has quit IRC22:45
*** shakayumi has joined #openstack-trove23:00
*** mmcdaris has quit IRC23:03
hub_capthx for the approve vipul23:04
vipulnp hub_cap23:04
vipulhub_cap: Ok with me merging https://review.openstack.org/#/c/47206/?23:07
hub_capmost def vipul23:07
vipul<323:08
datsun180b"status": "ACTIVE",23:09
datsun180bIT IS DONE23:09
vipulweeeee23:09
datsun180bit's taken so long to get just that to work and i think i may have found a bug in servicestatus.from_description in the process23:09
hub_capdatsun180b: can u imagine trove saying i am the alpha and the omega23:09
espthx!23:09
datsun180bnow to fix this bidness once and for all23:10
hub_caphorray23:10
datsun180byou'll hear from jenkins when i submit those reviews23:13
*** datsun180b has quit IRC23:13
openstackgerritA change was merged to openstack/trove: PEP8. F841  https://review.openstack.org/4628923:18
*** mmcdaris has joined #openstack-trove23:18
openstackgerritA change was merged to openstack/trove: Update from global requirements  https://review.openstack.org/4898623:22
openstackgerritA change was merged to openstack/trove: Added server_id to my.cnf template logic  https://review.openstack.org/4720623:22
*** tanisdl_ has joined #openstack-trove23:31
*** tanisdl has quit IRC23:33
*** tanisdl_ is now known as tanisdl23:33
*** asalkeld has quit IRC23:42
*** yogeshmehra has joined #openstack-trove23:43
hub_capvipul:  SlickNik can someone help me w/ this?23:45
hub_capvolume_time_out is SUPER low in the config (cfg.py)23:45
hub_capand when you try to prov an instance using the test env, it fails miserably23:46
hub_capbut why is it not failing the gate?23:46
hub_capredthrux: around?23:46
hub_capcfg.IntOpt('volume_time_out', default=2),23:47
hub_capthats 2 seconds LULZ23:47
vipulmust be that fast23:50
vipulthere is a sleep of 2.. which may make it 4 seconds23:50
openstackgerritMichael Basnight proposed a change to openstack/trove: Volume timeout is set too low  https://review.openstack.org/4908923:51
vipulvolume_time_out=3023:51
vipulthat's what's defined in sample23:51
hub_capoh i guess thats what int tests use23:53
hub_capthe problem is when we dont use int-tests23:53
hub_capwe have a broke-ass build23:53
hub_capbut this is good23:53
hub_capcuz moving to devstack is finding issues we have in our config23:53
hub_caphttps://review.openstack.org/#/c/49089/23:53
hub_capi bet server_delete_time_out is too low too23:53
vipuli assume in devstack we just take our .sample and use that?23:53
hub_capnope23:54
hub_capdtroyer insisted we do not do that23:54
hub_capso we can find issues like this in our code23:54
vipulso in devstack there is no sample?23:54
hub_capnope23:54
hub_capits inisets23:54
hub_capto a blank file23:54
hub_capw/ devstack you get like ~6 values23:54
vipulOh23:54
hub_capin the tmgr conf23:54
vipulthat explains that23:55
hub_capyup :)23:55
hub_capill up the server_delete_time_out=480 too23:55
hub_capbut to 6023:55
hub_cap480 is crazy big23:55
vipulthat could be what yogeshmehra was seeing with Heat..23:55
openstackgerritA change was merged to openstack/trove: Fixed method signature _create_server_volume_heat  https://review.openstack.org/4853523:55
vipulalthough that would not be subject to this timeout23:55
openstackgerritMichael Basnight proposed a change to openstack/trove: Volume timeout is set too low  https://review.openstack.org/4908923:55
hub_capi wonder if those are stupid low cuz of tests23:56
hub_capif so ill cry23:56
hub_capLITERALLY CRY23:56
*** adrian_otto has quit IRC23:56
hub_cap"lets tune down our defaults for test config" = RIDICULOUS FAIL23:56
*** adrian_otto has joined #openstack-trove23:56
vipulwell i know we've turned things UP for tests.. not sure if we've turned things down23:57
hub_capfake tests23:57
vipuloh yea those23:57
hub_capto make them faster23:57
hub_capya23:57
hub_capso if the fake tests come back at like +1min slower23:58
hub_capwe will know thats the case, and i will cry23:58
*** matsuhashi has joined #openstack-trove23:58
vipulI wonder.. does Heat also implement such polling timeouts?23:58
hub_capim sure it has polling timeouts.. it'd have to23:59
hub_capmaybe things dont stay stuck in build anymore23:59
hub_capif thats the case it doesnt need to23:59
vipulwell for things like volumes.. seems like you want Heat to do the same thing23:59
vipulwait for it to be 'available' before booting an instance23:59

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