Thursday, 2014-01-09

*** swygue has quit IRC00:04
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Add call to preview stack with template and params  https://review.openstack.org/6557600:14
*** sjmc has quit IRC00:15
*** rongze has joined #heat00:23
*** alexheneveld has quit IRC00:25
*** alexheneveld has joined #heat00:28
*** slong has joined #heat00:30
*** slong_ has quit IRC00:31
*** IlyaE has joined #heat00:46
*** rongze has quit IRC00:52
*** tango has quit IRC00:59
*** rwsu has quit IRC01:00
openstackgerritRandall Burt proposed a change to openstack/heat: Refactor CLB to work with groups  https://review.openstack.org/6558601:05
*** yogesh has joined #heat01:06
*** randallburt has quit IRC01:13
*** pvaneck has quit IRC01:13
*** rongze has joined #heat01:23
*** rongze has quit IRC01:28
*** nosnos has joined #heat01:29
*** yogesh has quit IRC01:34
*** yogesh has joined #heat01:35
*** kebray_ has quit IRC01:37
*** yogesh has quit IRC01:39
*** slong has quit IRC01:42
*** larsks is now known as larsks|Zzz01:45
*** sballe has quit IRC01:47
*** sballe has joined #heat01:47
*** sballe has quit IRC01:55
*** rongze has joined #heat01:59
*** IlyaE has quit IRC02:12
*** plomakin_ has joined #heat02:14
*** TonyBurn has joined #heat02:14
*** sgran_ has joined #heat02:14
*** grncdr has quit IRC02:15
*** sgran has quit IRC02:15
*** plomakin has quit IRC02:15
*** TonyBurn_ has quit IRC02:15
*** erkules_ has joined #heat02:16
*** grncdr has joined #heat02:18
*** erkules has quit IRC02:19
*** grncdr has left #heat02:29
*** alexheneveld has quit IRC02:34
*** yogesh has joined #heat02:45
*** nati_ueno has quit IRC02:50
*** yogesh has quit IRC02:50
*** alienyyg has joined #heat02:52
*** andersonvom has quit IRC02:52
*** alienyyg has quit IRC02:56
*** alienyyg has joined #heat02:59
*** blamar has quit IRC03:05
*** alienyyg has quit IRC03:05
*** spzala has quit IRC03:05
*** liang has joined #heat03:06
*** alienyyg has joined #heat03:08
*** kebray_ has joined #heat03:11
*** andersonvom has joined #heat03:12
*** andersonvom has quit IRC03:12
*** andersonvom1 has joined #heat03:12
*** blamar has joined #heat03:14
asalkeld_stevebaker, you busy with the get_file bp?03:27
stevebakerasalkeld_: yep, well I'm actually busy practicing for tomorrow's webinar03:28
asalkeld_O what webinar is that?03:28
asalkeld_ptl?03:28
stevebakerstate of the project, this is the last one03:28
asalkeld_ok, power on then ;)03:29
*** alienyyg has quit IRC03:29
*** gokrokve has joined #heat03:29
openstackgerritA change was merged to openstack/heat-templates: Fix MultiNode_DevStack template  https://review.openstack.org/6483303:33
*** alienyyg has joined #heat03:33
*** kebray_ has quit IRC03:38
*** alienyyg has quit IRC03:39
*** kebray_ has joined #heat03:40
*** kebray_ has quit IRC03:55
stevebakerasalkeld_: this one needs one more review https://review.openstack.org/#/c/64900/04:02
asalkeld_looking04:02
*** kebray_ has joined #heat04:03
*** kebray_ has quit IRC04:04
asalkeld_ zip(*[((04:05
asalkeld_ga04:05
*** harlowja is now known as harlowja_away04:07
asalkeld_stevebaker, i didn't review that earlier cos' it hurt my eyes/brain04:11
asalkeld_still does04:11
andersonvom1asalkeld_: I feel ya! ;)04:12
asalkeld_don't like code like that04:12
*** andersonvom1 is now known as andersonvom04:12
asalkeld_clever code is not clever IMHO04:12
andersonvomhey, since you guys are reviewing stuff... I've been having problems getting jenkins to accept these two patches because of tempest tests. do you have any idea on how to proceed?04:13
andersonvomhttps://review.openstack.org/#/c/58641/04:13
andersonvomhttps://review.openstack.org/#/c/63041/04:14
*** harlowja_away is now known as harlowja04:14
andersonvomasalkeld_: agreed. clever code to me means it's concise and anyone can immediately understand04:14
stevebakerandersonvom: can you run those tempest tests locally?04:17
asalkeld_andersonvom, is says:  Please rebase your change and upload a new patchset.04:17
*** cody-somerville has quit IRC04:17
*** kebray_ has joined #heat04:19
*** arbylee has joined #heat04:22
*** nkhare has joined #heat04:25
andersonvomasalkeld_: which patch?04:28
andersonvomstevebaker: I have not. I have actually been trying to figure out how to do that. :$04:29
stevebakerandersonvom: if you use devstack its pretty easy04:29
andersonvomI do04:29
*** kebray_ has quit IRC04:30
stevebakerstep 1: enable tempest in devstack04:30
stevebakerthere is no step 204:30
asalkeld_well you have to run tempest04:30
andersonvomhuh04:30
andersonvominteresting04:30
stevebakerbut seriously, once the devstack is running, cd tempest; testr run test_non_empty_stack04:31
*** cody-somerville has joined #heat04:31
*** kebray_ has joined #heat04:32
andersonvomcool. just chatting to the misses here and will try that in a short while. =D04:33
andersonvomthanks. will keep you posted04:33
*** kebray_ has quit IRC04:38
*** nosnos_ has joined #heat04:47
*** rongze has quit IRC04:47
*** rushiagr has joined #heat04:49
*** cody-somerville_ has joined #heat04:49
*** sdake_ has joined #heat04:49
*** asalkeld__ has joined #heat04:50
*** cody-somerville has quit IRC04:55
*** liang has quit IRC04:55
*** nosnos has quit IRC04:55
*** asalkeld_ has quit IRC04:55
*** sdake has quit IRC04:55
*** liang has joined #heat04:57
*** arbylee has quit IRC05:10
*** rongze has joined #heat05:18
*** kebray_ has joined #heat05:19
*** rongze has quit IRC05:22
*** rongze has joined #heat05:23
andersonvomso, once I enable tempest, do I run it with "testr run —parallel tempest"?05:26
andersonvomoh, just saw stevebaker's msg05:26
*** chandankumar has joined #heat05:27
*** rongze has quit IRC05:27
*** skraynev has quit IRC05:30
*** skraynev has joined #heat05:33
skraynevMorning All) It was good holidays))) Congratulations to all a Happy 2014 :)05:35
skraynevtherve, did you ask me?05:36
*** gokrokve has quit IRC05:38
*** chandankumar_ has joined #heat05:39
*** nati_ueno has joined #heat05:43
*** kebray_ has quit IRC05:44
openstackgerritJenkins proposed a change to openstack/heat: Imported Translations from Transifex  https://review.openstack.org/6450406:07
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Check resources are in expected states  https://review.openstack.org/5864106:14
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Add way to group exceptions in DependencyTaskGroup  https://review.openstack.org/6247906:14
*** rongze has joined #heat06:23
*** rongze has quit IRC06:24
*** rongze_ has joined #heat06:24
*** chandankumar has quit IRC06:25
*** harlowja is now known as harlowja_away06:25
*** gokrokve has joined #heat06:49
*** sgran_ is now known as sgran06:53
*** bvandenh has joined #heat06:54
*** gokrokve has quit IRC06:54
*** andersonvom has quit IRC06:56
*** sergmelikyan has joined #heat07:09
*** SergeyLukjanov has joined #heat07:18
openstackgerritSerg Melikyan proposed a change to openstack/heat: Implements Nova FloatingIP resources  https://review.openstack.org/6283607:20
*** rushiagr is now known as rushiagr_away07:26
*** ifarkas has joined #heat07:39
*** tspatzier has joined #heat07:46
*** SergeyLukjanov has quit IRC07:47
*** SergeyLukjanov has joined #heat07:48
*** sergmelikyan has quit IRC07:49
*** sergmelikyan has joined #heat07:54
*** alienyyg has joined #heat07:54
*** andersonvom has joined #heat07:57
*** erkules_ is now known as erkules07:57
*** jprovazn has joined #heat07:58
*** renlt has joined #heat08:00
*** renlt has quit IRC08:00
*** rushiagr_away is now known as rushiagr08:00
*** renlt has joined #heat08:01
openstackgerritFeng Ju proposed a change to openstack/heat: Fix heat-keystone-setup error when try to create heat user  https://review.openstack.org/6523808:02
*** andersonvom has quit IRC08:03
*** rushiagr2 has joined #heat08:09
*** rushiagr has quit IRC08:13
shardymorning08:21
alienyyghi shardy08:21
*** jistr has joined #heat08:24
*** SergeyLukjanov has quit IRC08:44
*** nati_ueno has quit IRC08:47
*** aignatov has joined #heat08:49
openstackgerritChmouel Boudjnah proposed a change to openstack/heat-templates: Add swift hot example.  https://review.openstack.org/6532308:54
chmouelit could be nice to have yaml validation on heat-templates checks for heat-templates repo08:54
*** tomek_adamczewsk has joined #heat09:00
shardychmouel: Yeah I've thought the same thing09:02
*** tomek_adamczews1 has joined #heat09:02
*** _ruhe is now known as ruhe09:04
*** tomek_adamczewsk has quit IRC09:05
*** che-arne has quit IRC09:07
*** rushiagr2 is now known as rushiagr09:08
*** tomek_adamczews1 has quit IRC09:09
therveskraynev, Yeah let me remember :)09:09
*** tomek_adamczewsk has joined #heat09:09
skraynevtherve: no problem, I will wait your memories)))09:10
therveOh yeah09:10
therveskraynev, https://bugs.launchpad.net/heat/+bug/125683609:10
thervei don't think there is anything to do here, do you think otherwise?09:11
chmouelshardy: ok filled a bp for that https://blueprints.launchpad.net/heat-templates/+spec/templates-validations-jenkins-job09:11
*** tomek_adamczewsk has quit IRC09:12
*** tomek_adamczewsk has joined #heat09:12
thervechmouel, We could call heat template-validate on them09:12
chmoueltherve: cool09:13
skraynevtherve, yeap, I agree with you. It's completed thing. and we have solution. (unfortunately it looks as "hack")09:13
therveskraynev, OK I'll close it then09:14
*** alexheneveld has joined #heat09:15
*** giulivo has joined #heat09:15
skraynevtherve, currently, I offer close it and wait changes in neutron (many vip to lbaas)09:15
skraynevand then make it more clear)09:16
*** tomek_adamczewsk has quit IRC09:18
openstackgerritChmouel Boudjnah proposed a change to openstack/heat-templates: Add swift hot example.  https://review.openstack.org/6532309:19
*** tomek_adamczewsk has joined #heat09:19
*** MaximB has joined #heat09:23
openstackgerritA change was merged to openstack/heat: Avoid error on double-delete of nested stack  https://review.openstack.org/6275209:24
openstackgerritA change was merged to openstack/heat: Fix schema format in template generation unit tests  https://review.openstack.org/6489909:25
shardywoohoo, gate seems to be working again :)09:25
*** SergeyLukjanov has joined #heat09:25
skraynevaha))) I hope, that it's not exception.09:26
MaximBshardy: how would openstack/heat work if I install them on/as a VM on esxi?09:27
*** tomek_adamczewsk has quit IRC09:28
openstackgerritA change was merged to openstack/heat: Validate number of instance metadata entries  https://review.openstack.org/6186409:29
openstackgerritA change was merged to openstack/heat: Improve tools/uninstall-heat  https://review.openstack.org/6469409:29
chmoueltherve: about heat validate-templates, i think that come back to the discussion we had at the office in the other day if the client or the server do the validation09:29
openstackgerritA change was merged to openstack/python-heatclient: Added API reference document  https://review.openstack.org/6366509:29
skraynevshardy, You was right;) take off my hat to you09:30
thervechmouel, Yeah. There was a problem that you define resources on the server side, so we wouldn't be able to validate that on the client09:30
chmoueltherve: trying to add validate-templates in heat-templates would have to be done on a running v09:30
therveSure that sounds like an easy tempest task09:30
chmoueli am not sure how that plugs all together in jenkins09:31
chmouelyou upload a review at first to heat-templates, jenkins pick it up and launch a devstack09:32
*** sergmelikyan has quit IRC09:32
*** giulivo has quit IRC09:32
*** giulivo has joined #heat09:33
chmouelbut I am not sure how tempest takes that get validated by tempest09:33
*** rushiagr is now known as rushiagr_away09:36
shardyMaximB: It will work, but ideally the nova-compute part of openstack needs to be on bare metal, or VM's running on VM's can be very slow (unless you can use nested virt)09:37
openstackgerritA change was merged to openstack/python-heatclient: Remove vim header  https://review.openstack.org/6432609:37
openstackgerritA change was merged to openstack/python-heatclient: Enable deleting multiple stacks with single call  https://review.openstack.org/6066409:37
openstackgerritA change was merged to openstack/python-heatclient: Remove ununsed httplib2 requirement  https://review.openstack.org/6525109:37
shardychmouel: I think it would just be a case of wiring heat-templates into the devstack gate, but we could just have a "unit" test which does a json/yaml syntax check first09:38
*** renlt has quit IRC09:38
MaximBshardy: but how do you install openstack on esxi? you install it on a vm machine inside esx or just any machine or?09:38
shardythe sytax check should be simple, and would be better than what we have now :)09:38
shardyMaximB: Yeah, for test/evaluation purposes you could install it all inside one VM09:39
shardythat is what many folks do for development, but as I said, it is slow for anything other than trivial testing09:40
openstackgerrithuangtianhua proposed a change to openstack/heat: Fixes template not using the JSON or YAML format  https://review.openstack.org/6564409:40
shardypersonally I prefer running it all natively on my laptop09:40
chmouelshardy: yeah i was thinking about the unit test at first09:40
*** alienyyg has quit IRC09:41
MaximBshardy: so I can install it on my laptop and connect to the esxi?09:41
*** alienyyg has joined #heat09:41
shardyMaximB: Probably, there is a vmware driver for nova-compute, but I've never tried it09:44
shardyhttp://docs.openstack.org/trunk/config-reference/content/vmware.html09:44
*** rushiagr_away is now known as rushiagr09:47
*** derekh has joined #heat09:52
*** julienvey has quit IRC09:53
*** bgorski has joined #heat09:54
*** tspatzier has quit IRC09:56
*** tspatzier has joined #heat09:58
*** nati_ueno has joined #heat09:58
*** andersonvom has joined #heat10:01
openstackgerritChmouel Boudjnah proposed a change to openstack/heat-templates: Make pep8-cfn-json2yaml PEP8 free  https://review.openstack.org/6564610:01
*** plomakin_ has quit IRC10:01
*** plomakin has joined #heat10:01
*** nati_ueno has quit IRC10:02
*** sergmelikyan has joined #heat10:05
*** andersonvom has quit IRC10:05
*** tomek_adamczewsk has joined #heat10:08
*** asalkeld__ is now known as asalkeld10:14
*** rushiagr2 has joined #heat10:14
*** liang has quit IRC10:15
*** rushiagr has quit IRC10:18
sergmelikyanshardy, I would like to implement https://blueprints.launchpad.net/heat/+spec/discover-catalog-resources, if there is no objections. This seems like valuable feature.10:27
shardysergmelikyan: Ok, I can assign it to you10:28
shardysergmelikyan: done!10:29
sergmelikyanshardy, Thx!10:30
*** SergeyLukjanov has quit IRC10:30
*** aignatov has quit IRC10:37
*** jprovazn has quit IRC10:39
*** ruhe is now known as _ruhe10:42
*** jpeeler has quit IRC10:44
*** nosnos_ has quit IRC10:46
*** aignatov has joined #heat11:05
*** _ruhe is now known as ruhe11:06
*** tspatzier_ has joined #heat11:06
*** tspatzier has quit IRC11:10
*** nkhare has quit IRC11:11
*** jprovazn has joined #heat11:11
*** ruhe is now known as _ruhe11:18
*** _ruhe is now known as ruhe11:23
*** asalkeld has quit IRC11:24
*** asalkeld has joined #heat11:27
*** che-arne has joined #heat11:37
*** jamieh has joined #heat11:44
*** rongze_ has quit IRC11:46
alienyyghi guys,thank you for your help, now the  autoscaling works for me, and after tha I wanna to learn more about this project, I mean be  a devoloper, not only user, so can you guys give me some advice how can I get into this?11:46
MaximBshardy: is there a minimum specs for a vm install of openstack?11:46
MaximBalso the wiki says http://docs.openstack.org/havana/install-guide/install/apt/content/ ubuntu 12.04, would it work for a new version like 13.04 or 13.10?11:49
shardyMaximB: There are details of hardware requirements in the openstack operations guide11:51
shardyMaximB: for a minimal all-in-one test environment, I'd suggest 8G ram minimum11:52
*** cody-somerville_ has quit IRC11:52
shardyRe Ubuntu, I expect so but I think the docs only cover the LTS version11:53
shardyI run only on Fedora and RHEL ;)11:53
sergmelikyanalienyyg, as usually :) Send changes on review to review.openstack.org, See bugs and BP on launchpad.net/Heat11:54
shardyalienyyg: good news, start by looking at https://wiki.openstack.org/wiki/Heat/DevelopmentProcess11:55
*** ruhe is now known as ruhe_away12:05
*** cody-somerville_ has joined #heat12:06
*** ruhe_away is now known as ruhe12:08
*** cody-somerville_ is now known as cody-somerville12:10
*** dims_ is now known as dims12:11
MaximBshardy:  about this guide: http://docs.openstack.org/havana/install-guide/install/apt/content/basics-networking.html ,do I need to create 2 machines? if so, what specs each machine should have?12:15
*** rongze has joined #heat12:21
*** rongze_ has joined #heat12:22
*** derekh has quit IRC12:23
*** ruhe is now known as _ruhe12:23
*** radez_g0n3 is now known as radez12:25
*** rongze has quit IRC12:26
*** rpothier has quit IRC12:32
*** renlt has joined #heat12:33
*** renlt has quit IRC12:34
*** renlt has joined #heat12:35
*** rushiagr2 has quit IRC12:36
sdake_morning12:39
*** _ruhe is now known as ruhe12:50
alienyygshardy: too many there, so it means the developer is review the code ,fix bugs, or raise blueprint and then make it become reality, so know how to do it now12:51
*** derekh has joined #heat12:57
*** alienyyg has quit IRC13:07
*** rongze_ has quit IRC13:07
*** sgordon has joined #heat13:09
chmouelanyone knows if heat bulitins ssl setup is supposed to work?13:12
*** rongze has joined #heat13:17
*** larsks|Zzz is now known as larsks13:20
openstackgerritThomas Spatzier proposed a change to openstack/heat: Refactor Parameters Schema based on common Schema  https://review.openstack.org/6568813:20
*** alexpilotti has joined #heat13:25
*** radez is now known as radez_g0n313:31
*** rushiagr2 has joined #heat13:37
*** rpothier has joined #heat13:39
*** renlt has quit IRC13:41
*** rushiagr2 is now known as rushiagr13:51
*** sballe has joined #heat13:52
*** jdob has joined #heat14:01
*** andersonvom has joined #heat14:01
*** jpeeler has joined #heat14:05
*** jpeeler has quit IRC14:05
*** jpeeler has joined #heat14:05
*** andersonvom has quit IRC14:06
*** andersonvom has joined #heat14:08
*** andersonvom has quit IRC14:18
*** jcru has joined #heat14:22
*** SergeyLukjanov has joined #heat14:23
thervetspatzier_, Looking at your patch, it seems that changing things into lower-case is backward incompatible14:24
therveIn particular as the ouput of template validation14:25
tspatzier_hi therve14:25
therveSorry, hi :)14:26
tspatzier_The change should be only internally in the code used by the engine. The templates can still have uppercase, and when read in it is transformed to lowercase14:26
thervetspatzier_, The output changes, though14:26
*** tspatzier_ is now known as tspatzier14:27
therveSee http://paste.openstack.org/show/60878/ as a before/after14:27
tspatzierWhat is the output used for? I thought it was "just" objects used inside the engine and in testcases. So nothing really critical to the user.14:28
therveNo the output is returned by an API14:28
therveIt is used for example by horizon14:28
therveThere are already some bad stuff in it, like constraints are normalized between HOT and CFN14:29
therveBut I'm not sure we should break compatibility here. I guess lower-case isn't so bad, but still14:29
tspatzierOk, got it.14:30
*** pbacterio has joined #heat14:31
*** pbacterio has left #heat14:31
tspatzierThis is really a mess actually.14:31
therveYeah I know :/14:32
tspatzierSo I think internally we should really just go with one option. And then maybe have some to_external function?14:33
tspatzierCurrently, everything is kept as it comes from the template, right?14:34
therveWell HOT is translated14:34
therveAt least some keys are14:35
tspatzierThat also something I am changing in that patch. No translation of params any more, but plain read as schema objects.14:37
therveWell you're translation CFN presumably?14:38
*** andersonvom has joined #heat14:38
tspatzierpreviously we translated parts into CFN14:38
tspatziertherve: So for validate, is it always input == output?14:42
*** vijendar has joined #heat14:42
thervetspatzier, No, it's output == CFN (mostly)14:42
*** arbylee has joined #heat14:46
tspatzierHm, so maybe so to_external code would be best. Internally it would really be nice to just deal with the objects and not distinguish between CFN and HOT.14:47
tspatzierAnd then some code to externalize the schema objects. I could also revert the constants to uppercase and deal with upper/lower in comparisions inside the code, but that would leave the additional attributes (hidden, required) in your sample.14:49
therveI think additional fields are okay, you can ignore them14:51
*** arbylee1 has joined #heat14:51
therveI also think it may be reasonable to change the output for HOT, especially if we stard handling constraints properly14:51
therveBut it seems that CFN template should still get out as CFN syntax14:52
tspatzierSure14:52
tspatzierIs template-validate the only place where this hits?14:52
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Unscoped List Stacks  https://review.openstack.org/6304114:53
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Add filter and pagination to stack_get_all  https://review.openstack.org/6303914:53
therveI would say so14:53
*** arbylee has quit IRC14:54
*** MaximB has quit IRC14:55
tspatzierOk. I guess I will add a comment to the review about what we talked. Also what the options would be. Then think about it again and change it. ... and wait for other comments :-)14:56
therveThansk :)14:57
*** alienyyg has joined #heat15:01
*** alienyyg has quit IRC15:03
*** swygue has joined #heat15:06
*** john-n-seattle1 has joined #heat15:07
*** john-n-seattle1 has left #heat15:09
*** john-n-seattle1 has joined #heat15:10
*** zaneb has quit IRC15:12
*** alienyyg has joined #heat15:13
*** alienyyg has left #heat15:14
sdake_I figured out how to mark all read in thunderbird!!15:15
*** andersonvom has quit IRC15:15
openstackgerritChmouel Boudjnah proposed a change to openstack/python-heatclient: Use python requests lib for all our http thingies  https://review.openstack.org/6570415:15
*** topol has joined #heat15:19
*** andersonvom has joined #heat15:22
*** rwsu has joined #heat15:23
*** dims has quit IRC15:23
*** tspatzier has quit IRC15:24
*** dims has joined #heat15:24
*** IlyaE has joined #heat15:27
*** rongze has quit IRC15:31
*** granny has joined #heat15:31
*** jdob has quit IRC15:35
*** jdob has joined #heat15:36
*** zaneb has joined #heat15:38
*** randallburt has joined #heat15:41
*** randallburt has quit IRC15:41
*** randallburt has joined #heat15:42
*** sjmc has joined #heat15:47
*** rcleere has joined #heat15:48
*** granny has quit IRC15:48
zanebtherve: see https://review.openstack.org/#/c/65325/1/heat/engine/service.py for an example of how we should handle it15:51
*** jmckind has joined #heat15:52
*** chandankumar_ has quit IRC15:54
*** tims has joined #heat15:56
*** tims has quit IRC15:56
*** tims has joined #heat15:56
*** jhurlbert has quit IRC15:57
*** funzo has quit IRC15:59
*** funzo has joined #heat16:01
openstackgerritDennyZhang proposed a change to openstack/heat: Remove vim header  https://review.openstack.org/6469116:09
*** spzala has joined #heat16:09
*** jdag is now known as jdaggett16:10
*** ifarkas has quit IRC16:11
*** alexpilotti has quit IRC16:20
shadowerI've been reading the docs and it occurred to me that OS::Heat::RandomString should be using a cryptographically secure PRNG instead of Mersenne twister16:21
shadowerhttp://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::RandomString16:21
shadowerhappy to look into it myself -- just checking if I'm not missing something obvious16:21
thervezaneb, Hum it's not totally clear what this code does :)16:22
zanebtherve: it retrieves the label from the parameter class by calling label() and adds it to the output to be returned with the key expected by the API16:23
zanebtherve: we need to start doing that for all of the stuff returned from the API, instead of grabbing it from the dictionary the parameter was defined with16:24
zaneband move the function into heat.engine.api16:24
therveMokay, it looks a bit awkward though16:24
*** IlyaE has quit IRC16:25
*** kebray_ has joined #heat16:25
zanebmore awkward than the format_*() functions in https://github.com/openstack/heat/blob/master/heat/engine/api.py ?16:25
therveYeah, because we do "give me the param schema. Oh but just replace that one key"16:26
*** alexheneveld has quit IRC16:27
zanebit's adding, not replacing16:27
zanebbut yes, it's awkward at the moment because there's only one thing we're accessing that way16:27
zanebbut after tspatzier's patch goes in, we need to access _everything_ that way16:27
zaneband then it won't be awkward16:27
therveIt's not replacing? Why would label not be in the dict?16:27
zanebwe don't make it available in ParamSchema16:28
therveOkay16:29
zanebactually, you might be right16:29
*** tomek_adamczewsk has quit IRC16:29
therveIt seems the answer is "it depends" :)16:30
zanebhttps://review.openstack.org/#/c/62418/8/heat/engine/hot.py16:30
zanebyeah, we do if it's available, but it's not necessarily the one you want16:30
therveAnyway I see your point16:30
therveI really wish we used HOT everywhere internally, and just have translation at the borders16:31
zanebI really wish we were completely independent of the template format everywhere internally, and just have translation at the borders16:31
zanebgoing fishing through the template keys is how we got into this mess16:32
therveYeah16:32
zanebgoing fishing through HOT template keys doesn't solve the problem, it just changes it16:32
therveRight by HOT I mean HOT schema objects16:32
zanebif we have programmatic APIs for everything, we will be able to plug in a new template formate easily16:33
zanebor, for that matter, modify HOT easily16:33
zanebyep, that is essentially the goal16:33
zanebthere will likely be HOT schema objects and cfn schema objects that read different templates, but have the same API16:34
* therve nods16:35
thervezaneb, On that subject, do you think we should change the output of template-validate for HOT templates?16:35
therveIt looks like we would have trouble translation constraints, for example16:36
*** randallburt1 has joined #heat16:36
zanebyeah16:36
*** rushiagr2 has joined #heat16:36
zanebtbh I think we will have to add a new validate API16:36
zanebor perhaps a separate get_params API16:36
therveOh noes new APIs :/16:37
zaneband fix some of my original mistakes, and some of the things that have emerged from HOT16:37
zanebbetter a new API than to make an old one incompatible with existing clients16:38
*** randallburt has quit IRC16:38
therveAgreed. We still need to make the old compatible, though16:38
*** rushiagr has quit IRC16:39
*** randallburt1 has quit IRC16:42
*** che-arne has quit IRC16:49
*** che-arne has joined #heat16:50
*** aignatov has quit IRC16:51
*** pablosan has joined #heat16:53
*** tspatzier has joined #heat16:53
*** derekh has quit IRC17:02
*** rushiagr2 is now known as rushiagr_away17:03
*** gokrokve has joined #heat17:03
*** alexpilotti has joined #heat17:09
*** alexheneveld has joined #heat17:10
*** randallburt has joined #heat17:15
*** randallburt has quit IRC17:20
openstackgerritChmouel Boudjnah proposed a change to openstack/python-heatclient: Use python requests lib for all our http thingies  https://review.openstack.org/6570417:20
*** m4dcoder has joined #heat17:23
m4dcoderalexpilotti: you there?17:23
alexpilottim4dcoder: sure17:23
*** m4dcoder_ has joined #heat17:25
m4dcoder_alexpilotti: i want to see what you have done so far with the windows instance bp17:26
m4dcoder_alexpilotti: any room for me to work with you on that bp?17:26
alexpilottim4dcoder_: you mean since yesterday? :-)17:26
*** ruhe is now known as _ruhe17:27
m4dcoder_alexpilotti: :)  i didn't know how long you've been working on that.17:27
alexpilottim4dcoder_: sure, I'm going to publish the heat templates for Windows this week17:28
alexpilottim4dcoder_: we have Heat support already in the Windows cloud init: https://github.com/cloudbase/cloudbase-init17:28
*** m4dcoder has quit IRC17:28
alexpilottim4dcoder_: so basically that bp is mostly related to documenting the Windows specific stuff17:29
alexpilottim4dcoder_: if you'd like to help, there's always space! :-)17:29
m4dcoder_alexpilotti: sure.  so if i understand what you're saying, the cloudbase init implementation already works on Windows?  there's not much dev work, just documentation?17:30
alexpilottim4dcoder_: correct. We're finishing up the heat templates this week (MSSQL, Exchane, Sharepoint, etc)17:30
alexpilottim4dcoder_: so if you'd like to help on testing them it'd be great :-)17:31
shardyalexpilotti: are you going to publish those templates somewhere?17:31
*** jistr has quit IRC17:31
alexpilottishardy: definitely yes17:31
m4dcoder_alexpilotti: that's awesome!  i would like to test that.  can you review the ML?  shardy posted some comments.  does your implementation address those?17:32
shardyalexpilotti: great!  If you like, I'm pretty sure we'd be happy to have them in the heat-templates repo :)17:32
*** alexheneveld has quit IRC17:32
*** pvaneck has joined #heat17:33
*** swygue has quit IRC17:33
shardym4dcoder_: My ML comments may be obsolete by the sounds of it17:33
alexpilottishardy: sounds good! We're also planning to put cloudbase-init on stackforge17:33
*** swygue has joined #heat17:34
shardyalexpilotti: Are there any plans for cloudbase-init to merge back into cloud-init?17:34
shardy(I remember it was mentioned at one point)17:34
alexpilottishardy: we're also looking at that, but there's really too much refactoring involved17:34
alexpilottishardy: actually cloudbase-init started because it was impossible to simply port cloud-init17:35
alexpilottishardy: there's also teh licensing issue17:35
alexpilottishardy: cloudbase-init is Apache2, while cloud-init is GPL17:35
shardyalexpilotti: Ok, the one concern I have is divergence between the two tools, but are you aiming to maintain compatibility with cloud-init interfaces indefinitely?17:35
alexpilottishardy: if by interfaces you mean metadata services, then yes17:36
shardyalexpilotti: Oh really, I incorrectly assumed cloudbase-init was a fork17:36
alexpilottishardy: nope, it's a total rewrite17:36
shardyalexpilotti: well the main things Heat currently cares about is stuff like the cloud-config DSL and part-handler functionality17:37
alexpilottishardy: it was written with multiplatform portability in mind and some guys lately used it for a FreeBSD version17:37
alexpilottishardy: yep, that's part of the multi part user data plugin17:37
shardyalexpilotti: Ok, sounds good :)17:38
alexpilottishardy: do you have plans for design changes on the part-handler functionality?17:39
shardyalexpilotti, m4dcoder_: I'm really glad you guys are picking this up, windows support is something many users have asked for and so far we've not had the bandwidth to investigate17:39
m4dcoder_alexpilotti: when you've published, can you send a shout out on the ML along with some instructions on setup?17:40
shardyalexpilotti: No, but we need to ensure what we have stays working (i.e without hacks to support two different cloud-init implemenations)17:40
*** rushiagr_away is now known as rushiagr217:40
alexpilottim4dcoder_: sure!17:41
alexpilottishardy: I also hate the idea of two separate tools, so if we can overcome the licensing issues and merge the two tools (possibly as a openstack core or at least stackforge project), that would be great17:42
shardyalexpilotti: ++17:42
*** swygue has quit IRC17:42
*** nati_ueno has joined #heat17:42
*** randallburt has joined #heat17:44
*** randallburt has quit IRC17:44
*** randallburt has joined #heat17:44
*** gokrokve has quit IRC17:49
*** gokrokve has joined #heat18:01
*** m4dcoder_ has quit IRC18:02
*** gokrokve has quit IRC18:03
openstackgerritA change was merged to openstack/heat: Update log message for scale out/in  https://review.openstack.org/6460618:03
*** aignatov has joined #heat18:05
*** rushiagr2 is now known as rushiagr_away18:06
*** harlowja_away is now known as harlowja18:07
*** derekdon has joined #heat18:08
*** sdake_ has quit IRC18:12
*** rushiagr_away is now known as rushiagr218:12
*** derekdon has quit IRC18:13
*** yogesh has joined #heat18:24
*** tspatzier has quit IRC18:39
*** tango|2 has joined #heat18:42
*** che-arne has quit IRC18:45
*** rushiagr2 has quit IRC18:47
*** bgorski has quit IRC18:49
*** _ruhe is now known as ruhe18:52
stevebakershardy: hey, should I mention V2 API as a possible icehouse feature in the Project Update webinar?18:57
*** alexheneveld has joined #heat18:59
radixhmm19:03
radixis there any code that actually uses heatclient in heat? I see that there's a method to return a heat client, but I don't see anything calling it19:03
*** randallburt has quit IRC19:03
radix(maybe in review?)19:05
*** alexpilotti has quit IRC19:06
*** alexpilotti has joined #heat19:09
*** wwallnrr__ has joined #heat19:09
stevebakerradix: https://review.openstack.org/#/c/58879/ https://review.openstack.org/#/c/58880/19:11
radixah, of course, the config management stuff19:11
*** SergeyLukjanov has quit IRC19:13
*** aignatov has quit IRC19:15
*** jamieh has quit IRC19:18
zanebradix: when we go multiregion we'll need it for nested stacks too19:18
*** wwallnrr__ has left #heat19:18
radixzaneb: so, the other day you said something that I didn't quite notice at the time19:21
radix(changing subjects entirely)19:21
radix<zaneb> 1) split out the database, 2) split the implementation out of the resources into a separate python api 3) create native resources using this api 4) wrap a ReST API around the API19:21
radixzaneb: can you explain #3 a little more?19:21
zanebso currently we have AWS autoscaling resources...19:22
*** rcleere has quit IRC19:22
zanebthere's no point implementing native ones just yet, because the implementation is still buried in the AWS ones19:22
zanebbut when the implementation is encapsulated behind its own API, we can go ahead and start using that19:23
zaneband add the ReST client/server interface in the middle later19:23
radixzaneb: are you talking about using the python code in-process, or talking to the separate AS API?19:23
zanebusing the python code in-process for 319:24
radixthe design that was discussed at the summit and laid out in the specs was resources talking to the AS REST API19:24
zanebseparate api for 419:24
zaneb(rest api for 4)19:24
zanebright, and that is absolutely the goal IMO19:24
radixok, so you're suggesting this as an intermediate step?19:24
zanebbut that doesn't mean that there are no intermediate steps that are useful19:25
zanebexactly, yeah19:25
zanebI'm just concerned about schedule risk19:25
radixyeah, me too19:25
zanebwe're nearly at I-219:25
zanebtherve I gather is not devoting time to it any more19:25
radixthough I'm wary of spending time on internal resources before getting to the API19:25
radixer, "internal resources" was a bad way of putting that19:26
zanebI understand19:26
radixok :)19:26
zanebI am wary of doing a top down implementation where we only discover if everything fits at the last possible moment19:26
radixyeah19:26
radixI guess ideally those intermediate resources should be trivial, if the other parts are amenable19:27
zanebindeed19:27
radixanyway, I'm basically trashing all of the BPs right now and recreating the chain of dependencies19:27
zanebbtw the intermediate resource thing was something that shardy pointed out to me19:27
radixthey were basically backwards from what they needed to be, and I didn't realize it19:27
zanebwhich I agree with, but I would still think we should do it in that order even without them19:28
radixyeah19:28
radixokay19:28
radixwell, I will create a BP for them19:28
radixzaneb: btw, afaik the thing you put in #1 doesn't actually need to be #119:28
zanebI think #1 & #2 are somewhat linked19:29
radixbut maybe I'm mistaken19:29
radixI'm imagining that the first step is "create a library that generates templates" (basically what you said as #2). then the intermediate resources could be  implemented in terms of that library.19:30
radixthe intermediate resources would just use a nested stack19:30
radixonce we get to a separate process / engine, that needs a different database19:30
zanebby separate database I mean separate table19:31
zanebnot necessarily it's own db19:31
zanebbut don't store any data in the resource19:31
radixhmm19:31
zanebstoring data in the nested stack is fine19:32
openstackgerritJason Dunsmore proposed a change to openstack/heat: Close SSH connections in Cloud Servers resource  https://review.openstack.org/6576119:33
zanebbut not in the AutoscalingGroup resource, and especially not in the LaunchConfig resource, &c.19:33
radixokay, I think I know what you mean19:34
radixto be clear19:34
jdobhey all, are there any docs on heat templates besides the example templates repo? i've found the client docs but nothing specific to the template format19:34
radixthe state that isn't represented by the generated template or nested stack is what we're talking about, and what's left is basically cooldowns and rolling update tracking info (and maybe something else I'm forgetting)19:34
larsksjdob: There http://docs.openstack.org/developer/heat/template_guide/openstack.html which lists all the supported resource types.19:35
zanebradix: yeah, exactly. we can't have any of that data tied to a resource in the local stack19:35
radixright19:35
radixokay, that sounds reasonable19:35
jdoblarsks: ah cool, that looks like a good starting point, thanks19:36
zanebradix: as far as everything that happens in the nested stack is concerned, that's already pretty well abstracted and should port right across without much difficulty when that becomes a process boundary19:36
*** tomek_adamczewsk has joined #heat19:37
radixhuh. where the heck is that state stored in the AWS-based resources? I'm not seeing any resource_data19:37
zaneba lot of it is just in the properties19:38
*** rcleere has joined #heat19:38
radixhmm, looks like last adjustment time is stored in metadata19:38
zanebe.g. when we want to know the launch config, we go fishing for it in the local stack and copy all of its properties into a server19:39
radixcool: metadata.keys()[0] :-(19:39
zanebyikes19:39
radixI wonder what key that is, haha19:39
zanebyeah, that's the level of stuff we're dealing with ;)19:39
radixohhh, it's a dynamic key, it's a timestamp19:39
radixokay, I look forward to obsoleting that code ;-)19:39
zanebso, this is why we need separate DB tables :D19:40
*** IlyaE has joined #heat19:40
radixhehe19:42
*** spzala has quit IRC19:44
*** ruhe is now known as _ruhe19:44
*** blamar has quit IRC19:54
*** gokrokve has joined #heat19:56
jdobis there a way to specify arbitrary metadata on a resource? more generally, if I make two Server resources with slightly different values and I wanted to tell them apart when i view the resources on a stack19:59
*** radez_g0n3 is now known as radez20:05
*** SergeyLukjanov has joined #heat20:09
zanebjdob: other than the name you mean?20:09
zanebthere is a metadata section on each resource, but note that is contains data that is available inside the instance20:10
zanebthat may or may not be what you want in this case20:10
jdobya, because my example was too small. i have 10, of two different types, and i need to tell them apart20:10
jdobthats what i was looking at, the metadata thing. i wasnt sure if the fields were locked into enumerated values or if i could shove my own jdob-type-id sort of thing in there20:11
jdoband have heat return it to me when i look up the stack resources20:11
*** alexpilotti has quit IRC20:11
*** SergeyLukjanov has quit IRC20:11
zanebyeah, the content of the metadata is entirely up to you20:12
jdobis that available on ever resource, not just Server ?20:12
jdober, "resource type"20:12
zanebthough in-instance tools like os-collect-config will treat certain bits of data in certain ways20:12
zanebyes, every resource can have metadata20:13
zanebactually, OS::Nova::Server is a confusing one, because it has a metadata _property_ as well20:13
jdoboh, thats not the same thing?20:14
jdob(glad you said that :)20:14
zanebtbh I have no idea what that is20:14
*** spzala has joined #heat20:14
radixNova servers have arbitrary metadata that can be associated with them20:14
jdobbut thats injected into the server?20:15
radixit's completely inert IIRC20:15
zanebbut the metadata you want lives a level up, at the same level as the properties20:15
jdobzaneb: thats still on a resource by resource basis, not at the stack level, right?20:15
zanebradix: oh, so it's metadata in the Nova API, but not something that is available to the instance?20:15
radixI *think*, yes20:15
jdoball of my 10 instances i described are the same stack20:16
*** sdake has joined #heat20:16
*** sdake has quit IRC20:16
*** sdake has joined #heat20:16
zanebjdob: yes, so inside each resource you have a 'properties' key, and you can also have a 'metadata' key20:16
zanebradix: thanks, I had been wondering about that ;)20:16
jdobah, perfect, thats the sort of thing i was looking for20:17
zanebjdob: caveat: it only applies to servers20:17
jdobah, hrm...20:18
*** mkollaro has joined #heat20:19
zanebjdob: that is to say, the property that radix was talking about is only for servers20:19
jdoboh oh, gotcha20:19
zanebjdob: the metadata thing is for everything20:19
jdobya, i'll be querying heat, not nova directly, so i dont care about the one that makes it to that level20:19
zanebjdob: cool, then the metadata attribute/key/whatever-you-want-to-call-it on each resource will do what you want20:21
jdobexcellent, thanks for your help. i still have yet to get heat running on my setup, so it might be a bit before i have more questions, but that definitley helps20:21
mkollarois there somewhere an example on how to combine multiple HOT files? I want to deploy a lot of various topologies that are somewhat similar and I'd rather not create a different template for each20:22
zanebmkollaro: o/ :)20:22
mkollaroor maybe some way to reuse parts of other templates20:22
zanebgood question20:23
mkollarozaneb: \o20:23
radixso, the AS blueprints *weren't* backwards, I was just momentarily confused about what the arrows meant :)20:23
radixbut I'm adding more20:23
zanebmkollaro: we have an AWS::CloudFormation::Stack resource type that creates a new stack20:23
zanebso you can manage a tree of stacks from a collection of templates like that20:24
zaneb(at some point we will create an OS::Heat::Stack equivalent)20:24
mkollaroI don't understand...what exactly is meant by "stack" here?20:24
zanebstack = the collection of resources created from a template by Heat20:24
zanebso stack =~= template20:25
mkollarooh20:25
zanebeffectively you can compose templates using a resource type that pulls in another template20:25
mkollaroand am I somehow able to reuse the parameters to the template, or do I have to define them anew each time?20:26
zanebyou pass any parameters you want through the Stack resource's 'Parameters' property20:27
* zaneb goes to look for the docs20:27
*** alexpilotti has joined #heat20:27
radixzaneb: can you cast your eyes on the dependency graph here? https://blueprints.launchpad.net/heat/+spec/as-lib-db20:29
zanebmkollaro: http://docs.openstack.org/developer/heat/template_guide/cfn.html#AWS::CloudFormation::Stack20:29
mkollaroso, if I have one template that creates a single VM (+ floating ip, volume, etc) and I want to have another template that is essentially the same, but creates 3 of them?20:29
radixtherve: if you happen to still be around a quick review of that bp tree would be nice :)20:29
zanebmkollaro: that is not so easy. you can use a ScalingGroup to create a group of servers (with the size determined by a property), but you can't yet do it for an arbitrary template (i.e. with floating ip, volume, &c.). We are working on that though, that's actually what radix is doing at the moment :)20:32
mkollarooh20:32
mkollarogood luck with that then :D20:32
sjmcmkollaro - i ended up scripting template generation to do this20:33
zanebthat's exactly what I thought when I saw all those blueprints he assigned to himself :D20:33
mkollarosjmc: templates of templates? :D20:34
radixheh heh20:34
sjmc:)  kinda20:34
zanebradix: but seriously, that looks good ;)20:34
radixzaneb: yay20:34
radixthere's probably yet more detail to fill in20:34
radixand it may not be a strict ordering (some patches for as-lib might happen before as-lib-db for example)20:35
radixbut it's a, uh, completion order I guess20:35
mkollarozaneb: thanks for the help, I'll probably be annoying you with a few questions for the next week20:35
zanebmkollaro: np, please do :)20:35
mkollaro:)20:35
zanebmkollaro, sjmc: there have been a few folks who asked us to do templating of templates _inside_ heat. Those folks are destined to be eternally disappointed ;)20:36
sjmczaneb - i know, that's why i didn't ask :)20:36
sjmcbut in my case i needed to be able to generate a variable number of servers + floating ips + volumes20:37
sjmcand there doesn't seem to be a way to do it other than copy n pasting20:37
zanebsjmc: for the record I think doing that _outside_ of Heat is actually a great idea20:37
zanebsjmc: but good news, we will eventually let you [auto]scale templates, and then you won't have to any more20:38
mkollaroso, before I jump into this, what are currently the biggest problems around heat?20:39
*** tomek_adamczewsk has quit IRC20:39
sjmc:)   yeah. i know heat's a work in progress. i may be getting more involved in it soonish, waiting to get more direction from my management20:39
*** spzala has quit IRC20:41
*** Gamekiller77 has joined #heat20:41
Gamekiller77i know this is listed as a heat dev channel but can i ask some simple support questions for heat here too ?20:42
zanebGamekiller77: certainly :)20:44
Gamekiller77so getting odd auth errors20:45
zanebpaste.openstack.org20:46
*** radix__ has quit IRC20:46
Gamekiller77will do when i get it to gen again great home sick one day and stuff start to work hehe20:47
mkollarodoes heat have some cleanup function? I want to spawn some vms, run something on them and then kill them20:48
therveradix, The first is a bit obscure still20:48
Gamekiller77got it20:48
zanebmkollaro: when you delete the stack, it deletes all of the resources again20:49
therveradix, Otherwise it looks good I guess20:49
zanebmkollaro: but what you're asking about sounds more like a workflow20:49
Gamekiller77zaneb, http://paste.openstack.org/show/60911/  i just using simple create20:50
radixtherve: as-lib-db you mean?20:50
therveradix, Yep20:50
radixtherve: yeah, that's kinda why I was thinking some of as-lib might get started before as-lib-db20:50
Gamekiller77this is the simple text i use http://paste.openstack.org/show/60912/20:50
zanebmkollaro: the Mistral project is hoping to implement something like that20:50
mkollarozaneb: what's that?20:50
radixwe could do some basic template generation logic in before we do e.g. cooldown management20:50
therveradix, Sounds like a good idea yeah20:50
zanebmkollaro: so a workflow could be something like "Create a stack, then wait for this task to run on it, then delete the stack again". Mistral is a project to create an openstack api to do that. (Sometimes I call it 'cron as a service', which really annoys them.)20:52
*** denis_makogon has quit IRC20:52
*** dmakogon_ has joined #heat20:53
mkollarohehe20:53
mkollarozaneb: I was thinking about running ansible on it and then deleting it20:53
zanebHeat can takes care of tearing things down cleanly20:54
zanebbut you need an external script to decide when you task has finished and you want to go ahead and delete20:54
zanebthe latter is the part that Mistral will eventually give you an API for20:54
mkollarozaneb: in what kind of state is that project?20:56
zanebvery early days, I think20:56
sdakethey have just got started20:56
sdakefastest openstack projects have been 1 year to relative maturity20:57
zanebyeah, they just announced that they were going to start it back in October20:57
sdakethey are on month 1 or 220:57
zanebI haven't been following along since then to see when they actually did start20:57
mkollarothis is the problem in openstack...stuff I want will maybe exist a few months later :)20:58
sdakeI don't think I would have really considered heat relatively mature and reliable until it hit 18 months of dev20:58
sdakemkollaro ya it is a really big space and lots of  folks want lots of things20:59
sdakeand there are "only" 1k technical contributors to OpenStack (I think 1k is right)20:59
sjmcon the subject of the future, is the direction regarding software setup to use cloudinit to bootstrap chef/puppet/ansible/something? or is there likely to be something more formal21:00
sjmci know there's been to-ing and fro-ing on that21:00
Gamekiller77zaneb, did you take a look at my paste ?21:00
zanebsdake: sounds right21:00
*** jamieh has joined #heat21:01
zanebGamekiller77: no, thanks for the reminder!21:01
Gamekiller77not a problem21:01
arbylee1hey all, we're looking to update the heatclient to support the limit/marker pagination params on stacks.  It looks like there's some pagination code in StackManager from 2012 (before we implemented pagination) and it doesn't look like anyone is calling the method with the paging kwargs currently21:01
*** randallburt has joined #heat21:02
arbylee1wondering if anyone has context on that part of the code and if it's safe to go ahead and remove/overhaul to support the existing paging params21:02
sdakearbylee1 cool submit patch through workflow - sounds handy21:02
zanebGamekiller77: so the problem there is that's not a whole template21:02
sdakeI think overhaul is ok - it was added by a contributor who did pagination for a bunch of problems21:02
sdakeproblems/projects :)21:02
sdakeand maybe it could use a more modern view21:03
Gamekiller77ok21:03
Gamekiller77good21:03
Gamekiller77i need to find a simple quick template to spin up a simple server21:03
arbylee1sdake: thanks, we'll go ahead and change it then21:03
Gamekiller77to make sure it all works so i can sign it off21:03
sdakesjmc we are currently going to stick with cloudinit :)21:04
sdakesjmc I think the current thinking is to expose more of cloudinit to the user21:04
zanebGamekiller77: http://paste.openstack.org/show/60913/ would be the equivalent template to your snippet21:04
Gamekiller77thanks21:04
sdakesjmc there is alos the concept of adding specific resources for specific config management tools (eg chef/puppet/ansible)21:04
sjmcok, sdake. any thoughts around pushed software config (ansible-style)?21:06
sdakesjmc early on we started with that approach actually (ssh pushing to the guests)21:06
sdakesjmc however our current method is more scalable because it relies on the vm to do the orhcestration21:07
sjmcyeah, that makes sense21:07
sdakewith the previous ssh-push based method we would have had to scale that service out to multiple processors21:07
sjmcright21:07
sdakeinstead with the current mode we just load the data in the text field, and nova et al is responsible for the scaling :)21:07
Gamekiller77you guys need to provide just a little more description to the errors that pop up on the dashboard21:07
sdakeerror reporting in heat is pretty bad21:08
sdakenot going to lie :)21:08
sjmcsdake - i've been booting images that don't always have packages i'd expect to be there, which has sometimes meant installing provisioning clients has been tricky21:08
sdakesjmc which provisioning clients?21:08
sjmcansible, puppet or whatever21:09
zanebGamekiller77, sdake: some are better than others. The real problem is a lack of sanity checks. That error should have complained about the properties section being missing altogether, not about being empty21:09
sjmcbut if that's definitely going to be the direction i'll work around those issues rather than hoping for my ssh-pushed config21:09
Gamekiller77yah i just got an error the key was not spelled right21:09
zanebmore errors = better errors21:10
sdakesjmc I am not a big fan of the server approach to config management (eg have a server drive the activity like puppet/chef/ansible do)21:10
Gamekiller77zaneb, i need to add the network to that template you gave me21:10
sdakebut I realize it is a reality of what people want out of heat21:10
sjmcsdake - yeah, i definitely see for heat it's best not to let that scaling monster into the room21:10
Gamekiller77what line should  i add21:10
jasondzaneb: what did you mean "I'd also suggest that each group of EngineService, EngineListener and ThreadGroupManager share a unique engine_id"?21:10
sdakesjmc and I believe we intend to provide proper hooks so folks investment in those toolchains doesn't waste21:10
openstackgerritThomas Herve proposed a change to openstack/heat: Don't query for resource during stack creation  https://review.openstack.org/6391421:11
sdakewell, that is why we didn't do it in heat initially21:11
sdakewe have enough scaling problems to deal with21:11
sjmc:)  yeah21:11
sdakeactually why we removed it initially :)21:11
openstackgerritJason Dunsmore proposed a change to openstack/heat: Allow an in-progress stack to be deleted  https://review.openstack.org/6300221:11
zanebGamekiller77: by add a network, you mean add a Neutron network resource? Or just connect the server to an existing network?21:11
sjmcwill heat run ok with multiple engines and apis now? i know there was some work recently on that21:12
sdakesjmc I believe jasond did that work on master and last report I got was its all done :)21:12
sjmcwoo21:12
zanebjasond: I meant that e.g. EngineService will generate an engine_id when it is created21:12
sdakesjmc but you will ahve to use icehouse to get it (we aren't backporting)21:12
Gamekiller77so got stack create error that it needed a network to attach to21:13
jasondsjmc, sdake: yes, it's done.  there's a bugfix in for delete during an in-progress action.  here is the doc https://review.openstack.org/#/c/63963/21:13
sjmcsdake - understood. it'll be a while till we get it properly set up anyway i think, we're still experimenting21:13
sjmcthanks jasond21:14
zanebGamekiller77: docs for OS::Nova::Server are here: http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server21:14
Gamekiller77zaneb, the code you gave me worked fine just i got this error Create_Failed: Resource create failed: BadRequest: Multiple possible networks found, use a Network ID to be more specific. (HTTP 400) (21:15
Gamekiller77perfect i needed that21:15
Gamekiller77thanks for all the support21:15
zanebGamekiller77: np :)21:17
Gamekiller77OMG i been looking for this guide for a while21:17
Gamekiller77thanks you so much21:17
Gamekiller77yah i keep failing at network ID21:17
sdakejasond nice docs21:17
jasondsdake: thanks21:17
sdakejasond have you tested heat at much scale yet?21:18
jasondsdake: not yet21:19
sdakecurious how the db lock impacts scaling limits21:19
zanebsdake: as long as collisions are unusual it should be pretty minimal21:20
zaneband collisions should be unusual21:20
*** gokrokve has quit IRC21:21
*** gokrokve has joined #heat21:22
Gamekiller77is there a tool to validate a template for HOT yet ?21:22
Gamekiller77i saw someone say there was for the yaml21:22
jasondzaneb: how is using stack_lock.engine_id related to singleton classes?21:23
zanebGamekiller77: there is a validate_template API in heat21:23
Gamekiller77ok i see what i need to add to the template just not sure what the formate is i figure this out i need to add a new type to the my template21:24
Gamekiller77can you have more then one type in a template ?21:25
zanebjasond: right now you need a global thread list, because there's only one engine_id per process (so if you encapsulated it in a class, it would be a Singleton). If there were one engine_id per EngineService, then you can store all the thread group list locally21:25
*** gokrokve has quit IRC21:26
zanebGamekiller77: maybe https://github.com/openstack/heat-templates/blob/master/hot/servers_in_existing_neutron_net.yaml is a good example to look at21:28
Gamekiller77yup already made it there21:29
Gamekiller77hehe21:29
jasondthere's only one EngineService and one EngineListener (listening on different AMQP queues).  they both need access to the thread group list21:29
Gamekiller77just read that site thanks man i get up to speed fast21:29
jasond*read/write access, that is21:30
zanebthe EngineService creates the listener, so it's no problem to pass the thread group list to it21:31
zanebs/listener/EngineListener/21:31
zaneb"there's only one EngineService and one EngineListener" <- so, they're Singletons at the moment21:32
zanebbecause they're using some global state21:33
zanebbut there's no reason they couldn't encapsulate that global state21:33
randallburtzaneb:  true but is there ever a reason to have more than one of each per engine?21:33
zanebrandallburt: no21:34
zanebbut encapsulating global state is desirable in itself21:34
randallburtzaneb:  so not a big deal atm, IMO. I do like the idea of encapsulating the thread group management, however. that could certainly be a follow on.21:34
*** nkhare has joined #heat21:35
zanebwell, we have to design this new bit (thread group management) _now_. So why not define it the way we want at the start - it isn't really any more work21:36
randallburtzaneb:  understood, I just don't think one (ThreadGroupManager) is predicated on changing the object hierarchy in the current patch.21:37
Gamekiller77thanks you zaneb i am up and running.  Will there be more logic in the template down the line to pull the local project ID for networking and images and keys already in the project ?21:38
*** sgordon has quit IRC21:38
jasondrandallburt: i agree, i'd rather put in a follow up patch.  it's been difficult getting people to look at this review.  would rather get the current patch in now while people are thinking about it21:39
zanebrandallburt: I haven't looked at the latest patchset yet21:39
jasondzaneb: although i'm still not sure how changing stack_lock.engine_id would help21:40
randallburtzaneb:  tbh me either, but its on my todo today.21:40
zanebthe object hierarchy in patch set 6 made my eyes bleed21:40
zaneb(only saying that 'cos it's not jasond's fault ;)21:40
randallburtzaneb, jasond: so much for being acommodating ;) TBH, I didn't have an issue with the original organization, but I was on vacation at the time. At least that's the story I'm sticking to.21:42
jasondzaneb: :)  can i quote you on saying that i've invented a radical new paradigm of OO design?21:42
randallburtjasond:  should def include that in your performance review.21:42
zanebjasond: you may :)21:43
*** blomquisg has quit IRC21:43
*** topol has quit IRC21:43
zanebjasond: http://paste.openstack.org/show/60917/21:45
jasondzaneb: that makes sense, thanks21:47
zanebreading the review again, it's clear that I didn't explain it very well21:48
jasondzaneb: it's no problem, thanks for the example21:49
zanebcool. that snippet was a more succinct explanation of what I was trying to suggest ;)21:51
*** jdob has quit IRC21:52
zanebjasond: btw ThreadGroupManager could be a defaultdict with an overridded __delitem__() method21:53
zanebperhaps not unidentical to https://github.com/openstack/heat/blob/master/heat/engine/dependencies.py#L9421:53
jasondcool, that helps21:55
*** nati_ueno has quit IRC21:56
*** gfidente has joined #heat21:57
stevebakersjmc: I think when ansible software config support is added it will be pull-based. This is what ansible recommends for large scale anyway, but instead of calling ansible from cron it is called by the software config polling mechanism21:58
*** nati_ueno has joined #heat21:59
sjmcok, thanks stevebaker. that was the impression i'd got from following amiling list discussions21:59
sjmcdo you see heat being involved getting those clients available, or do you think that'll remain part of a template's cloudinit ?21:59
sjmci can't use waitconditions at the moment so i think we're stuck with pushing configs for the near term (otherwise we never know when things are finished)22:02
*** nati_ueno has quit IRC22:03
*** nati_ueno has joined #heat22:04
*** dims has quit IRC22:12
*** gfidente has quit IRC22:12
*** gokrokve has joined #heat22:14
*** mestery has quit IRC22:16
stevebakersjmc: the recommended method would be to create a custom image containing os-collect-config, os-refresh-config, os-apply-config, your configuration tool, and the heat config hook script22:17
*** alexpilotti has quit IRC22:17
stevebakersjmc: but if you can't or won't use custom images you could install all that with cloud-init on boot, which can be specified in the template22:18
stevebakersjmc: why can't you use waitconditions?22:18
*** dims has joined #heat22:18
*** mestery has joined #heat22:19
*** rpothier has quit IRC22:21
*** jprovazn has quit IRC22:24
*** jamieh has quit IRC22:24
*** asalkeld has quit IRC22:25
lifelessstevebaker: don't they still require you to be admin?22:26
sjmcstevebaker, lifeless: yeah, that22:26
sjmcsorry, on phone22:26
*** radix_ has joined #heat22:27
*** asalkeld has joined #heat22:27
*** asalkeld has left #heat22:29
*** asalkeld has joined #heat22:29
stevebakersjmc: ah, ok. I just need to check which reason22:33
*** denis_makogon has joined #heat22:33
*** randallburt has quit IRC22:34
denis_makogongoodday 2 all, i've got few questions to all, does heat able to perform resource updating through stack update (example - resize instance/volume, add security group, resize volume) ?22:34
*** kebray_ has quit IRC22:38
zanebdenis_makogon: yes, but support for each one has to be implemented independently. So e.g. we support resize for instances but not for volumes at the moment22:40
*** jmckind has quit IRC22:40
denis_makogonzaneb, what about security groups ?22:40
zanebdenis_makogon: on which resource?22:41
denis_makogonzaneb, perhaps Neutron22:41
zanebOS::Neutron::Port22:42
zanebthat should work22:42
denis_makogonzaneb, you said that heat doesn't support update for volumes, right ?22:43
*** jcru has quit IRC22:43
zanebvolumes will be replaced if you modify them22:43
zanebwhich is probably not what you want22:44
denis_makogonyes22:44
asalkelddenis_makogon: look here: http://docs.openstack.org/developer/heat/template_guide/openstack.html22:44
asalkeldand look for "Can be updated without replacement."22:44
*** rwsu has quit IRC22:45
*** Linz has quit IRC22:48
*** kebray_ has joined #heat22:50
*** radez is now known as radez_g0n322:51
*** alexheneveld has quit IRC22:52
*** nati_ueno has quit IRC22:54
*** randallburt has joined #heat22:55
*** alexheneveld has joined #heat22:55
*** randallburt has quit IRC22:55
*** randallburt has joined #heat22:55
*** nati_ueno has joined #heat22:56
*** nkhare has quit IRC22:56
*** nati_ueno has quit IRC22:57
*** nati_ueno has joined #heat22:57
*** yogesh has quit IRC23:06
*** Linz has joined #heat23:06
*** yogesh has joined #heat23:06
*** Linz has quit IRC23:07
*** vijendar has quit IRC23:07
*** Linz has joined #heat23:07
*** denis_makogon has quit IRC23:07
*** mkollaro has quit IRC23:08
*** yogesh has quit IRC23:11
*** mkollaro has joined #heat23:15
*** rcleere has quit IRC23:19
*** pablosan has quit IRC23:20
*** pablosan has joined #heat23:23
*** slong has joined #heat23:28
*** alexpilotti has joined #heat23:35
*** sballe has quit IRC23:36
*** sballe has joined #heat23:36
*** tims has quit IRC23:39
*** Gamekiller77 has quit IRC23:46
*** Linz has quit IRC23:46
*** Linz has joined #heat23:49
*** sjmc has quit IRC23:58

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