Tuesday, 2014-03-25

lifelessstevebaker: ^00:01
stevebakerlifeless: I was installing dib with pip, and a 1.4 bug means that all files loose their execute bit00:02
stevebakerlifeless: and then fedora 20 came out which had heat-cfntools pre-installed, which met our testing needs for a little while00:03
*** rpothier has joined #heat00:03
*** radez is now known as radez_g0n300:13
*** openstack has joined #heat00:19
*** IlyaE has joined #heat00:19
openstackgerritSean Dague proposed a change to openstack/heat: heat is enabled by default in devstack now  https://review.openstack.org/8267800:20
*** RockKuo has joined #heat00:22
*** IlyaE has quit IRC00:26
*** matsuhashi has joined #heat00:26
*** Tross has joined #heat00:26
*** duncanjw has quit IRC00:27
*** jpeeler has quit IRC00:30
*** fandi has quit IRC00:34
*** lindsayk has quit IRC00:36
sdake_stevebaker if you want to take a look at this patch set it should be pretty easy to review and result in one less open bug :) https://review.openstack.org/#/c/82593/00:40
*** lipinski has joined #heat00:42
sdake_looks like systemd made its way into oslo-incubator - guess we can fix that in juno https://review.openstack.org/#/c/81211/00:43
stevebakersdake_: done, thanks00:43
sdake_thanks stevebaker00:43
sdake_need anything done besides reviews?  I went thrugh the bugs and looks like all are waiting on developer action00:43
sdake_https://bugs.launchpad.net/bugs/1296859 is unassigned but I'm not sure if i could fix it in a couple days00:45
uvirtbotLaunchpad bug 1296859 in heat "stack-list throws an error if any stack returned contains a template error" [Medium,Triaged]00:45
*** samstav has quit IRC00:45
sdake_i guess we could turn off validation for stack-list as randall suggests00:45
*** wchrisj has quit IRC00:45
sdake_seems so -- hacky :)00:45
stevebakerwe should make sure validation is turned off for delete too00:46
sdake_well if you like i'll take a look at fixing those two scenarios00:46
sdake_but I can't guarantee i'll be able to get er done in the next couple days00:46
stevebakersdake_: a review on this would be handy https://review.openstack.org/#/c/80882/00:47
stevebakersdake_: and this https://review.openstack.org/#/c/80868/00:48
openstackgerritA change was merged to openstack/heat: Document software config classes  https://review.openstack.org/8140700:49
sdake_stevebaker I -1 that first change00:49
sdake_I think it lacks internationalization of the exception00:50
sdake_other then that looks good00:50
sdake_the 2nd patch - let me eat first :)00:50
stevebakersdake_: actually there are zero i18n messages in heatclient, we haven't done that yet00:51
*** fandi has joined #heat00:51
sdake_oh that was client00:52
sdake_I didn't notice the different repo :(00:52
sdake_i'll go ahead and +a then00:52
*** wchrisj has joined #heat00:56
sdake_stevebaker just to be clear - i3-rc1 is cut as soon as the bug list is zero/01:01
sdake_or would we possibly remove some bugs?01:01
stevebakersdake_: yep, bug list needs to be zero, either by fixin-em or kickin-em01:01
sdake_not sure how else I can help this week other then try to tackle that validate problem01:02
sdake_and stay on top of reviews01:02
sdake_so I guess i'll work on the validate problem and if it doesn't make it we can kick it01:02
sdake_iirc it was medium01:02
stevebakersdake_: yep, and if it gets kicked but still lands before rc1 it will still be released in rc101:04
sdake_cool i'll focus on that01:04
sdake_my other commitments that I thought I had this week are off so I'm at your disposal :)01:04
stevebakergood to know01:05
*** RockKuo has quit IRC01:09
openstackgerritDong Liu proposed a change to openstack/heat: Add subnets as a dependency for router  https://review.openstack.org/8245201:16
*** rwsu has quit IRC01:26
*** nosnos has joined #heat01:29
*** matsuhashi has quit IRC01:30
*** matsuhashi has joined #heat01:30
*** wchrisj has quit IRC01:31
*** rpothier_ has joined #heat01:35
*** rpothier has quit IRC01:39
*** wchrisj has joined #heat01:39
*** rwsu has joined #heat01:42
*** wchrisj has quit IRC01:44
*** wchrisj has joined #heat01:49
*** wchrisj_ has joined #heat01:53
*** wchrisj has quit IRC01:53
*** IYozhikov_away has quit IRC01:56
*** IgorYozhikov has joined #heat01:56
*** IgorYozhikov is now known as IYozhikov_away01:57
*** RockKuo has joined #heat01:57
*** denis_makogon has quit IRC01:58
*** denis_makogon has joined #heat01:58
*** wchrisj_ has quit IRC02:00
openstackgerritA change was merged to openstack/python-heatclient: Do not use the '+' operation with dict_items()  https://review.openstack.org/8252302:09
openstackgerritA change was merged to openstack/heat: Error and NotFound inherit HeatException class  https://review.openstack.org/8259302:10
openstackgerritA change was merged to openstack/heat: Properly encode heat.common.exception in rpc  https://review.openstack.org/8238602:15
*** duncanjw has joined #heat02:28
openstackgerritA change was merged to openstack/heat: heat is enabled by default in devstack now  https://review.openstack.org/8267802:29
*** duncanjw has quit IRC02:32
*** mestery has joined #heat02:34
*** liang has joined #heat02:35
*** mestery has quit IRC02:46
*** mestery has joined #heat02:46
*** fandi has quit IRC02:50
*** cmyster_ has quit IRC02:54
*** Tross has left #heat02:57
*** wchrisj has joined #heat03:02
sdake_stevebaker all done with https://review.openstack.org/#/c/80868/03:04
sdake_actually an easy review - looked daunting originally :)03:04
*** wchrisj has quit IRC03:06
*** wchrisj has joined #heat03:07
*** matsuhashi has quit IRC03:12
*** wchrisj has quit IRC03:14
*** wchrisj has joined #heat03:15
*** david-lyle has joined #heat03:17
*** wchrisj_ has joined #heat03:19
*** wchrisj has quit IRC03:20
*** wchrisj has joined #heat03:24
*** wchrisj_ has quit IRC03:25
*** gokrokve has joined #heat03:27
*** wchrisj_ has joined #heat03:28
*** wchrisj has quit IRC03:29
*** nosnos has quit IRC03:29
*** matsuhashi has joined #heat03:30
*** wchrisj has joined #heat03:32
*** wchrisj_ has quit IRC03:32
*** chandankumar_ has joined #heat03:33
*** matsuhashi has quit IRC03:36
*** wchrisj_ has joined #heat03:39
*** wchrisj has quit IRC03:40
*** chandankumar_ has quit IRC03:40
*** mspreitz has joined #heat03:40
*** wchrisj has joined #heat03:43
*** wchrisj_ has quit IRC03:43
*** wchrisj has quit IRC03:47
*** harlowja_ is now known as harlowja_away03:49
*** gokrokve has quit IRC03:50
*** gokrokve has joined #heat03:52
*** pablosan_ has joined #heat03:53
*** pablosan has quit IRC03:54
*** chandankumar_ has joined #heat03:55
*** gokrokve has quit IRC03:57
*** killer_prince is now known as lazy_prince04:06
*** nati_ueno has quit IRC04:13
*** Linz has quit IRC04:16
*** Linz has joined #heat04:16
*** cfriesen has quit IRC04:17
*** nkhare has joined #heat04:19
*** matsuhashi has joined #heat04:23
*** chandankumar_ has quit IRC04:23
*** nosnos has joined #heat04:25
openstackgerritA change was merged to openstack/heat: Reimplement DHCPAgent as net's property  https://review.openstack.org/8172604:28
*** duncanjw has joined #heat04:29
*** duncanjw has quit IRC04:33
*** nati_ueno has joined #heat04:40
*** pasquier-s has quit IRC04:41
*** nkhare_ has joined #heat04:42
*** lipinski has quit IRC04:44
*** ramishra_ has joined #heat04:45
*** Linz has quit IRC04:46
*** Tross has joined #heat04:47
*** pasquier-s has joined #heat04:54
*** nkhare has quit IRC04:54
*** nkhare_ has quit IRC04:54
*** nkhare has joined #heat04:55
openstackgerritAndrew Plunk proposed a change to openstack/heat: Chef solo resource  https://review.openstack.org/5520805:08
*** matsuhashi has quit IRC05:14
*** pasquier-s has quit IRC05:16
*** matsuhashi has joined #heat05:18
*** skraynev_afk is now known as skraynev05:19
skraynevMorning05:20
*** gokrokve has joined #heat05:21
*** gokrokve has quit IRC05:25
*** IlyaE has joined #heat05:31
openstackgerritMitsuru Kanabuchi proposed a change to openstack/heat: Change router's prop name agent_id to l3_agent_id  https://review.openstack.org/8271605:34
*** nati_ueno has quit IRC05:47
*** chandan_kumar has quit IRC05:48
*** e0ne has joined #heat05:49
*** e0ne has quit IRC05:49
*** nati_ueno has joined #heat05:51
*** cmyster has joined #heat05:54
cmystermorning05:55
*** ramishra_ has quit IRC06:06
skraynevzaneb: Are you still here?06:07
openstackgerritMitsuru Kanabuchi proposed a change to openstack/heat: Change router's prop name agent_id to l3_agent_id  https://review.openstack.org/8271606:09
*** cmyster_ has joined #heat06:11
openstackgerritJenkins proposed a change to openstack/heat: Imported Translations from Transifex  https://review.openstack.org/7256606:12
*** cmyster has quit IRC06:14
*** mestery has quit IRC06:18
*** mspreitz has quit IRC06:26
*** duncanjw has joined #heat06:29
*** duncanjw has quit IRC06:36
*** ramishra has joined #heat06:51
*** ramishra_ has joined #heat06:53
*** ramishra has quit IRC06:54
*** ramishra_ has quit IRC06:55
openstackgerritChmouel Boudjnah proposed a change to openstack/heat: Add docker network_gateway attribute  https://review.openstack.org/8251106:57
*** lsmola_ has quit IRC07:02
*** lsmola_ has joined #heat07:03
chmouelpas-ha: the python docker client? yes that would be the location of the library07:03
*** ramishra has joined #heat07:13
*** IlyaE has quit IRC07:14
chmouelmorning all07:18
openstackgerrithuangtianhua proposed a change to openstack/python-heatclient: Deprecate preview --create-timeout in favor of --timeout  https://review.openstack.org/8272707:21
*** gokrokve has joined #heat07:21
*** gokrokve has quit IRC07:26
*** saju_m has joined #heat07:30
cmyster_morning chmouel07:32
*** nati_ueno has quit IRC07:37
therve'morning07:37
cmyster_morn07:41
*** tspatzier has joined #heat07:45
*** pasquier-s has joined #heat07:48
*** ifarkas has joined #heat07:48
*** tomek_adamczewsk has joined #heat07:48
*** FL1SK has quit IRC07:51
openstackgerritChmouel Boudjnah proposed a change to openstack/heat: Rename docker plugin to dockerheat  https://review.openstack.org/8273007:53
*** jstrachan has joined #heat07:59
thervechmouel, I don't understand, we already use the docker module and it works?08:00
*** FL1SK has joined #heat08:03
cmyster_I am getting this: http://paste.openstack.org/show/74220/ I remember something about it, but can't find if there is already an open bug here08:04
*** che-arne has quit IRC08:04
cmyster_a UTF8 issue in the DB08:04
*** e0ne has joined #heat08:10
*** jprovazn has joined #heat08:10
*** TonyBurn has joined #heat08:11
*** fandi has joined #heat08:15
cmyster_fixed with alter table migrate_version CHARACTER SET utf8 COLLATE utf8_unicode_ci;08:19
cmyster_for some reason it was latin_swedish for me08:20
*** pasquier-s has quit IRC08:22
*** pasquier-s has joined #heat08:25
*** duncanjw has joined #heat08:30
shardymorning all08:31
cmyster_morning08:31
shardycmyster_: I had the same issue, it's due to the mysql default AFAIK and/or something not being explicitly specified in the schema08:32
cmyster_https://bugs.launchpad.net/heat/+bug/127688008:32
uvirtbotLaunchpad bug 1276880 in heat "heat-db-setup should set default character set to utf-8" [Medium,Fix released]08:32
shardycmyster_: I fixed it by manually alterning the collation via the mysql cli08:32
cmyster_worked around it by updating the table manualy08:32
cmyster_ya08:32
shardy++ ;)08:32
openstackgerritThomas Herve proposed a change to openstack/python-heatclient: Resolve files in resource types  https://review.openstack.org/8052808:34
*** duncanjw has quit IRC08:36
*** alexheneveld has joined #heat08:42
*** giulivo has joined #heat08:46
*** matsuhashi has quit IRC08:49
*** jistr has joined #heat08:49
*** saju_m has quit IRC08:50
*** saju_m has joined #heat08:52
*** jistr is now known as jistr|training08:54
pas-hamorning08:55
*** matsuhashi has joined #heat08:56
*** DaveJ__ has joined #heat09:01
*** gokrokve has joined #heat09:05
*** gokrokve has quit IRC09:05
*** gokrokve has joined #heat09:05
openstackgerritTomas Sedovic proposed a change to openstack/heat: Don't create cloud-init user unless specified  https://review.openstack.org/7967809:10
*** chandan_kumar has joined #heat09:13
openstackgerritA change was merged to openstack/heat-templates: Add template for separated node/broker OpenShift  https://review.openstack.org/8163209:13
*** matsuhashi has quit IRC09:14
*** derekh has joined #heat09:15
*** matsuhashi has joined #heat09:18
*** cmyster has joined #heat09:19
*** cmyster_ has quit IRC09:22
*** lipinski has joined #heat09:24
*** alexheneveld has quit IRC09:35
*** saju_m has quit IRC09:38
*** nosnos has quit IRC09:39
*** duncanjw has joined #heat09:39
*** che-arne has joined #heat09:41
*** duncanjw has quit IRC09:42
*** cmyster has quit IRC09:45
*** bvandenh has quit IRC09:47
openstackgerrithuangtianhua proposed a change to openstack/heat: Remove the property validate for stack-adopt  https://review.openstack.org/8275909:56
*** saju_m has joined #heat09:57
*** matsuhashi has quit IRC10:08
*** matsuhashi has joined #heat10:10
*** bvandenh has joined #heat10:10
*** e0ne_ has joined #heat10:16
*** e0ne has quit IRC10:19
openstackgerritThomas Herve proposed a change to openstack/python-heatclient: Resolve files in resource types  https://review.openstack.org/8052810:21
*** faramir1 has joined #heat10:39
*** liang has quit IRC10:54
openstackgerritRoman Podoliaka proposed a change to openstack/heat: Fix listing of stacks with non-ascii parameters  https://review.openstack.org/8254510:54
*** saju_m has quit IRC11:07
*** saju_m has joined #heat11:08
*** saju_m has quit IRC11:09
*** ramishra has quit IRC11:11
openstackgerritA change was merged to openstack/heat: Store stack domain credentials for deployments  https://review.openstack.org/8086811:12
*** saju_m has joined #heat11:15
*** ramishra has joined #heat11:19
*** alexheneveld has joined #heat11:23
*** gokrokve has quit IRC11:23
*** RockKuo has quit IRC11:32
*** e0ne_ has quit IRC11:33
*** alexheneveld has quit IRC11:33
*** e0ne has joined #heat11:33
*** gokrokve has joined #heat11:34
*** gokrokve_ has joined #heat11:38
*** saju_m has quit IRC11:38
*** e0ne has quit IRC11:38
*** aweiteka has quit IRC11:38
*** saju_m has joined #heat11:38
*** gokrokve has quit IRC11:39
*** jistr|training has quit IRC11:40
*** jistr has joined #heat11:41
*** jistr is now known as jistr|training11:41
*** gokrokve_ has quit IRC11:42
*** ifarkas has quit IRC11:43
*** rpothier_ has quit IRC11:46
*** fandi has quit IRC11:47
*** ifarkas_ has joined #heat11:48
*** ifarkas_ has quit IRC11:50
*** ifarkas has joined #heat11:51
*** skraynev is now known as skraynev_afk12:01
*** harlowja_away has quit IRC12:03
*** aweiteka has joined #heat12:06
*** gokrokve has joined #heat12:10
*** e0ne has joined #heat12:12
*** e0ne has quit IRC12:13
*** duncanjw has joined #heat12:14
*** e0ne has joined #heat12:14
*** TonyBurn has quit IRC12:16
*** TonyBurn has joined #heat12:16
*** matsuhashi has quit IRC12:16
*** e0ne has quit IRC12:18
*** gokrokve has quit IRC12:19
*** gokrokve has joined #heat12:22
*** matsuhashi has joined #heat12:23
*** networkn8 has joined #heat12:23
*** david-lyle has quit IRC12:23
*** nkhare has quit IRC12:26
*** gokrokve has quit IRC12:28
*** gokrokve has joined #heat12:32
*** andersonvom has joined #heat12:33
*** bgorski has joined #heat12:34
*** sgordon has joined #heat12:38
*** alexheneveld has joined #heat12:40
*** saju_m has quit IRC12:41
*** gokrokve has quit IRC12:43
*** gokrokve has joined #heat12:43
*** mkollaro has joined #heat12:44
*** gokrokve has quit IRC12:47
*** asalkeld has quit IRC12:48
*** dims_ has quit IRC12:52
*** achampion has quit IRC12:52
*** gokrokve has joined #heat12:53
*** insanidade has joined #heat12:55
*** saju_m has joined #heat12:55
insanidadesdake_: are you there ? quick question, if you don't mind.12:55
*** saju_m has quit IRC12:59
*** mwheckmann has joined #heat12:59
*** saju_m has joined #heat13:00
*** rpothier has joined #heat13:01
*** dims_ has joined #heat13:02
*** mkollaro has quit IRC13:03
*** mkollaro1 has joined #heat13:03
*** mkollaro1 is now known as mkollaro13:03
*** matsuhashi has quit IRC13:03
*** saju_m has quit IRC13:04
*** saju_m has joined #heat13:05
aignatovhi heaters, I'm trying to create stack with the following template http://paste.openstack.org/show/74245/13:06
aignatovbut always I get StackValidationFailed: Property error : eba: image "1" does not validate glance.image13:07
aignatovwhat does 'glance.image' mean? is it special type of some prop?13:07
*** bgorski has quit IRC13:07
*** saju_m has quit IRC13:09
therveaignatov, That means you don't have an image named "1"13:10
*** saju_m has joined #heat13:10
*** asalkeld has joined #heat13:11
aignatovtherve: if i pass existed image id I get the same13:12
aignatovexisting13:12
therveI don't know then13:13
therveThe message should be improved13:13
therveIf you have access to heat logs you may have some more info13:14
*** spzala has joined #heat13:16
*** TonyBurn has quit IRC13:17
*** blomquisg has joined #heat13:18
*** blomquisg has quit IRC13:18
*** bgorski has joined #heat13:19
*** blomquisg has joined #heat13:19
*** arbylee has joined #heat13:20
openstackstatusNOTICE: the gerrit event stream is currently hung, blocking all testing. troubleshooting is in progress (next update at 14:00 utc)13:20
*** ChanServ changes topic to "the gerrit event stream is currently hung, blocking all testing. troubleshooting is in progress (next update at 14:00 utc)"13:20
*** wchrisj has joined #heat13:20
*** pablosan_ is now known as pablosan13:20
*** lazy_prince has quit IRC13:22
*** lazy_prince has joined #heat13:24
lipinskiHeat allows for retrieving templates.  Is there any way to retrieve environment used for stack -creation13:25
*** jcru has joined #heat13:26
*** wchrisj has quit IRC13:26
*** mestery has joined #heat13:28
shardylipinski: At the moment, no13:28
*** mestery has quit IRC13:28
*** pafuent has joined #heat13:28
*** ChanServ changes topic to "support @ https://ask.openstack.org | developer wiki @ https://wiki.openstack.org/wiki/Heat | development @ https://launchpad.net/heat | logged @ http://eavesdrop.openstack.org/irclogs/%23heat/"13:29
openstackstatusNOTICE: the issue with gerrit cleared on its own before any corrective action was taken13:29
*** mestery has joined #heat13:29
*** ramishra has quit IRC13:30
*** lazy_prince is now known as killer_prince13:35
*** wchrisj has joined #heat13:35
shardytherve: quick question re 80528:13:40
shardywhat's the use-case for the recurse_if logic?13:40
therveshardy, resource groups and autoscaling groups13:40
*** nati_ueno has joined #heat13:40
shardytherve: do you have an example of what the type: syntax would look like?  I didn't see a test covering it?13:41
shardytherve: the reason for my question is last week I was discussing an idea with some Tuskar folks, and they'd like to be able to actually embed a nested template via type (the actual body via a reference to another resource)13:42
therveshardy, http://paste.openstack.org/show/74246/ for example. Maybe it's missing a test indeed13:42
therveshardy, get_file may be the way for that13:43
*** fandi has joined #heat13:44
*** cfriesen has joined #heat13:44
*** duncanjw has quit IRC13:47
*** blomquisg has quit IRC13:47
*** samstav has joined #heat13:50
shardytherve: Ok, thanks, the language in the commit message made it sound a bit similar to what we discussed, which was something like:13:50
shardyhttp://paste.openstack.org/show/74248/13:50
*** radez_g0n3 is now known as radez13:51
shardywhere you could for example have a provider template which took various parameters, and output a stack template and an image which had been built and uploaded to glance13:51
shardyI guess we'd have to resolve that in the parser anyway not the client13:52
*** andersonvom has quit IRC13:53
*** zns has joined #heat13:57
*** wchrisj has quit IRC13:57
*** wchrisj_ has joined #heat13:59
therveshardy, That part would need to be done on the server side, I think13:59
*** blomquisg has joined #heat13:59
therveOh you just said that13:59
*** andersonvom has joined #heat13:59
*** nati_ueno has quit IRC13:59
*** achampion has joined #heat14:00
*** ramishra has joined #heat14:00
*** ramishra has quit IRC14:02
*** ramishra has joined #heat14:04
*** pas-ha has quit IRC14:06
*** duncanjw has joined #heat14:08
*** vijendar has joined #heat14:09
*** faramir1 has quit IRC14:18
openstackgerritZane Bitter proposed a change to openstack/heat: Fail if non-existent security group referenced  https://review.openstack.org/8155814:21
*** alexheneveld_ has joined #heat14:21
*** alexheneveld has quit IRC14:22
*** alexheneveld_ is now known as alexheneveld14:22
thervezaneb, Should you use HeatException?14:22
zanebtherve: check the comments for patch set 2 ;)14:23
aignatovtherve: hi, i conducted log for the issue I faced above14:23
aignatovhttp://paste.openstack.org/show/74251/14:23
*** mestery has quit IRC14:24
thervezaneb, What's the benefit of not using it though?14:25
zanebit's just a replacement for a client exception... those don't inherit from HeatException either... what is the point?14:26
*** mkollaro has quit IRC14:26
* zaneb was happy when it was just "raise Exception(...)"14:27
*** alexpilotti has quit IRC14:28
*** david-lyle has joined #heat14:31
thervezaneb, It provides the msg_fmt thing14:31
*** mestery has joined #heat14:33
*** jmckind has joined #heat14:35
jasondwhy does heat validate resources that weren't changed during update?14:36
aignatovtherve: could you please try my example above? I think it's easy to reproduce14:36
shardyjasond: we have to validate the whole updated stack because unchanged resources may reference those which have changed14:39
therveaignatov, Well, it doesn't work for me because I don't have an image with such an id14:41
*** mkollaro has joined #heat14:41
therveaignatov, What's the output of glance image-list?14:41
*** cmyster has joined #heat14:43
*** cmyster has joined #heat14:43
cmysterback (network outage)14:44
aignatovtherve: http://paste.openstack.org/show/74252/14:44
aignatovthe last one in the list14:44
therveaignatov, What about nova image-list?14:45
aignatovtherve: http://paste.openstack.org/show/74253/14:46
jasondshardy: i see.  i guess you can't validate the state of something that changes after create then https://github.com/openstack/heat/blob/master/heat/engine/resources/nova_keypair.py#L130-L13714:46
therveaignatov, Well I don't know.14:47
aignatovso, it seems there is some bug in heat, because before adding glance constraints it was worked well14:48
therveIt works for me, I start instances all the time14:49
therveThe glance constraint does mostly the same thing as before14:49
therveExcept with a crappy error message14:50
aignatovok, I'll try to check again my environment14:50
shardyjasond: that code actually looks wrong to me - I think that validation should probably be a constratint in the schema for the name property, not a validation check14:50
shardyconstraint even14:50
*** wwallnrr__ has joined #heat14:52
shardyjasond: In general, I expect resource validate() methods to implement more static checking, like dependent or mutually exclusive properties14:52
therveaignatov, You can try this patch to get more info: http://paste.openstack.org/show/74254/14:52
*** Qiming has joined #heat14:53
jasondshardy: makes sense.  i don't think it's being used that way everywhere14:53
*** rcleere has joined #heat14:54
jasondshardy: i'll see if a parameter constraint will work.  thanks14:54
aignatovtherve: thx, I'll try14:56
*** arbylee has quit IRC14:58
*** bgorski has quit IRC14:59
*** bgorski has joined #heat14:59
*** kgriffs_afk is now known as kgriffs14:59
*** IlyaE has joined #heat15:00
* shardy just did his first ever stack-abandon && stack-adopt15:00
*** arbylee has joined #heat15:00
shardykinda interesting/scary15:00
aignatovtherve: hehe, I've got the following http://paste.openstack.org/show/74255/15:00
aignatovseems issue is clear for me now15:00
aignatovbut definitely it should be raised before validation :)15:01
therveHum what15:01
*** alexheneveld has quit IRC15:01
therveI guess it created the keystone client at that point? That's pretty bad15:02
aignatovwhere could I find it? in logs?15:03
shardywell heat.conf is misconfigured, stack_user_domain has been modified from the default without setting up an admin15:04
shardyaignatov: how did you install heat?15:04
aignatovlocally, into my laptop, my heat looks into the devstack env outside of my machine15:06
pscheieIs there a heat command that shows all the instances belonging to a stack?15:06
*** sgordon has quit IRC15:07
pscheieresource-list shows all the resources, but, for example, doesn't show that we have 10 instances of a certain resource (spun via instancegroup)15:08
shardyaignatov: sounds like either the heat.conf has been manually updated or devstack is not up to date15:08
pscheieI can do 'nova list |grep <stackname>' but that seems...crude.15:09
thervepscheie, heat resource-show ?15:09
aignatovshardy: yes, my heat.conf contains only stack_user_domain property15:10
shardyaignatov: in particular perhaps you're missing https://review.openstack.org/#/c/76036/2/lib/heat and https://review.openstack.org/#/c/75424/15:10
*** spzala has quit IRC15:10
zanebshardy: what was that summit session you went to about Neutron reimplementing orchestration?15:11
zanebshardy: I'm looking here but can't spot it: https://wiki.openstack.org/wiki/Summit/Icehouse/Etherpads#Neutron15:11
pscheietherve, that gives me info about an individual resource, but not of the whole stack.15:13
*** saju_m has quit IRC15:13
*** spzala has joined #heat15:13
Qimingheat resource-list --recursive <stack_name>15:13
shardyzaneb: https://etherpad.openstack.org/p/icehouse-neutron-service-insertion-chaining I think15:13
thervepscheie, I guess I meant resource-list15:13
zanebshardy: ah, thanks15:13
shardyzaneb: they wanted to have a template defined combination of resources, which they would orchestrate IIRC15:13
zanebit's becoming clear to me why they want that15:14
zanebthe API is so broken that it's illegible to external orchestration15:14
*** packet has joined #heat15:14
shardyzaneb: haha, well we've known that for a while ;)15:15
zanebso instead of fixing it, they want to reimplement orchestration inside the API15:15
pscheietherve, yes, that sort of works--except we're starting to use InstanceGroups to create multiple instances, and resource-list only shows one resource, that of the InstanceGroup.15:15
*** wchrisj_ has quit IRC15:15
zanebI always new it was bad, but I'm starting to get a concrete sense of the particular ways in which it is broken15:15
zanebknew*15:16
pscheieQiming, what version of heat provides the --recursive option?15:17
*** spzala has quit IRC15:17
Qimingpscheie: no version, it is a feature request, :)15:18
pscheieQiming, ah, yes, that would be useful.15:18
Qimingnot only CLI output is confusing, horizon is suffering from the same problem15:19
*** cmyster has quit IRC15:19
*** e0ne has joined #heat15:19
Qimingwhen you create a xxxGroup resource, the members can not be shown, so the output is not correct15:20
shardypscheie: You can use the nested stack id available via resource-show <stack> <instancegroupresource> to resource-list the nested stack containing the resources15:20
shardyQiming: The output is correct, just not what you're expecting - the resources in xxGroup are created in a nested stack, so they are not in the top level stack containingthe xxGroup resource15:21
*** cmyster has joined #heat15:21
*** cmyster has joined #heat15:21
shardyarguably some convenient way to traverse nested resources from the client would be nice15:21
shardyatm you have to do it in several steps15:21
*** rbuilta has joined #heat15:22
Qimingif you are referencing some other resources in the LaunchConfiguration, in the horizon topology view, those resources are linked to the group resource, because the individual members cannot be shown15:22
shardyhttp://hardysteven.blogspot.co.uk/2013_08_01_archive.html15:22
pscheieyeah, I'm doing it in several steps currently.15:23
shardythat provides a simple worked example of how to get the resource-list for the nested stack15:23
pscheiewas hoping there was something built-in for it.15:23
zanebshardy: looks like you'll have more work to do in Atlanta: http://summit.openstack.org/cfp/details/19 ;)15:23
*** alexheneveld has joined #heat15:23
aignatovshardy, therve: yes, it's working now, I've just removed stack_user_domain definition from my heat.conf15:24
shardyzaneb: sigh15:24
*** mestery has quit IRC15:24
shardyaignatov: good to hear, at some point you may want to unstack/stack with a recent devstack to configure that correctly15:25
Qimingshardy: I said that it is incorrect, because heat really need a way to express 'contains' relationship, besides 'references' relationship among resources15:25
*** pas-ha has joined #heat15:25
aignatovshardy, thx,  domain specific things is new for me, when should I use it?15:25
shardyQiming: And I agreed the client interfaces can be improved :)15:25
aignatovis there any docs about it?15:26
shardyaignatov: It's turned on by default in devstack now, just looks like you were unlucky and somehow ended up with a broken config15:26
openstackgerritThomas Herve proposed a change to openstack/heat: Don't catch all exceptions in image constraint  https://review.openstack.org/8284615:26
openstackgerritJun Jie Nan proposed a change to openstack/python-heatclient: get_file: encode non utf-8 encoding files via base64  https://review.openstack.org/7644315:27
openstackgerritJun Jie Nan proposed a change to openstack/python-heatclient: get_file: do not read same url once again  https://review.openstack.org/8088215:27
shardyaignatov: There are links to the BP and key patches here: https://bugs.launchpad.net/puppet-heat/+bug/128888015:27
uvirtbotLaunchpad bug 1288880 in puppet-heat "Updates required for stack domain users" [Undecided,New]15:27
*** alexheneveld_ has joined #heat15:28
shardyaignatov: I've not done docs for deployers yet, but I'm planning to write something15:28
*** alexheneveld has quit IRC15:30
shardyaignatov: note heat auth_token needs this https://review.openstack.org/#/c/80341/ to avoid the issues discussed in bug #129109715:30
uvirtbotLaunchpad bug 1291097 in heat "deployment native signalling failing" [High,Fix committed] https://launchpad.net/bugs/129109715:30
shardyI need to figure out how to get some response from devstack-core on that one :\15:31
*** alexheneveld has joined #heat15:31
shardyThat won't affect you unless you're using the new software-config resources15:31
aignatovshardy: Thanks a lot for the info, I'm just trying to figure out what configuration needed to fix savanna(sahara) heat provisioning engine15:32
*** alexheneveld_ has quit IRC15:32
aignatovbecause in the mid-icehouse there were no needs in domain specific things15:33
shardyaignatov: Yeah, it's new stuff which recently landed under the instance-users BP15:33
shardyaignatov: If you do nothing then heat falls back to the old behavior with log warnings15:34
shardyaignatov: the advantage of the new approach is you no longer need to be admin to create heat stacks containing certain resources15:34
*** wchrisj has joined #heat15:35
*** wchrisj has quit IRC15:35
aignatovshardy: any special resource types?15:36
aignatovor is it something like delegating admin privileges?15:36
*** wchrisj has joined #heat15:36
shardyaignatov: Anything which creates a keystone user, so WaitConditionHandle, ScalingPolicy, User/AccessKey and the new *SoftwareDeployment resources15:37
shardyaignatov: it's for the credentials we deploy inside instances e.g for signalling waitcondition events15:37
shardyaignatov: the users associated with those credentials are now created in a separate heat-specific domain, completely isolated from the stack owner's project15:37
shardywhich is more secure, and removes the admin requirement, because you configure a domain-admin user which heat uses to manage the create/delete of those users15:38
*** sgordon has joined #heat15:39
aignatovshardy: makes sense, thanks for the explanation, I'll try to play with it for more comprehension15:42
*** Qiming has quit IRC15:42
*** alexpilotti has joined #heat15:44
sdake_morning15:45
*** alexpilotti has quit IRC15:46
aignatovshardy, one simple question, Sahara has one use case when it creates trust for long living clusters to be able remove it after some time. So using heat, do I need special configuration in heat to work with trusts?15:47
shardyaignatov: Not for you to use trusts, but if you want heat to use trusts (instead of storing a password in the DB), e.g for deferred operations like autoscaling, you may want to specify deferred_auth_method=trusts15:48
shardythat also became the default in devstack recently and we're moving towards making it the heat default for everyone:15:49
shardyhttps://review.openstack.org/#/c/80002/15:50
openstackgerritRabi Mishra proposed a change to openstack/heat: Provides ability to reference existing neutron resources  https://review.openstack.org/8285315:50
aignatovshardy: thanks15:54
*** jergerber has joined #heat15:54
*** Linz has joined #heat15:57
*** Linz has quit IRC15:57
*** packet has quit IRC15:57
*** Linz has joined #heat15:57
*** killer_prince is now known as lazy_prince15:57
sdake_shadower nice work on the sellinux issue15:58
sdake_shadower++15:58
*** alexheneveld_ has joined #heat15:59
*** packet has joined #heat15:59
*** mestery has joined #heat15:59
*** alexheneveld has quit IRC16:00
*** alexheneveld_ is now known as alexheneveld16:00
*** fandi has quit IRC16:06
*** fandi has joined #heat16:09
*** mestery has quit IRC16:09
*** mestery has joined #heat16:10
*** skraynev_afk is now known as skraynev16:14
skraynevzaneb: are you here?16:14
openstackgerritA change was merged to openstack/python-heatclient: Updated from global requirements  https://review.openstack.org/7669816:15
zanebskraynev: I am :)16:15
jasondshardy: apparently even parameters that haven't been change get validated during update, so a property constraint isn't going to work :/16:15
skraynevzaneb: couple questions.16:16
skraynevzaneb: first about https://review.openstack.org/#/c/81558/16:16
skraynevzaneb: could you add assert for checking status_reason of stack16:16
*** nati_ueno has joined #heat16:17
zanebI guess that would make sense16:17
shardyjasond: not sure I follow, so the issue is you want to update to create a keypair which already exists with the same name?16:17
skraynevzaneb: I suppose, it give additional confirmation of cause failing16:17
skraynevzaneb: ok16:18
jasondshardy: if you update a stack without changing the nova keypair, nova keypair validation will fail https://bugs.launchpad.net/heat/+bug/129674716:18
uvirtbotLaunchpad bug 1296747 in heat "Nova keypair cannot be updated" [High,Triaged]16:18
skraynevzaneb: and other question about validation of outputs.16:18
shardyjasond: maybe that logic should move so we only check in handle_create?16:18
skraynevzaneb: in comment you offered call validate(self.args). May be you meant validate(self, self.args) or something else?16:19
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Add OS:Barbican:Order resource  https://review.openstack.org/8190616:19
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Add OS:Barbican:Secret resource  https://review.openstack.org/7935516:19
jasondshardy: wouldn't that be the same as removing validation completely?  the stack would still be created and then fail16:20
jasondthat's what i'm leaning toward16:20
zanebskraynev: do you have the link handy?16:20
skraynevyeap... sec16:21
skraynevzaneb: https://review.openstack.org/#/c/82486/1/heat/engine/function.py16:21
zanebta16:21
zanebskraynev: nope, my comment is correct :)16:22
*** ifarkas has quit IRC16:22
thervejasond, I remember commenting on https://bugs.launchpad.net/heat/+bug/1278532 and not getting a response16:22
uvirtbotLaunchpad bug 1278532 in heat "The KeyPair resource needs validation" [Undecided,Fix released]16:22
*** sdague has joined #heat16:22
therveConsidering the issue maybe we should revert that change?16:22
shardyjasond: what about comparing the resource_id with the id from the get_keypair instead?16:22
sdagueso reiterating a heat question from -dev in wrapping my brain around things enough to help build out some tests16:23
jasondtherve: your comment was vague so i didn't comment.  i should've asked for clarification16:23
sdagueheat question, I shouldn't need anything more than cloud-init in an instance to get user_data executed in an OS::Nova::Server, should I?16:23
thervejasond, Well, yes. Please do :)16:23
skraynevzaneb: Well, it will be class method or you suggest call it in validate method of Function class?16:23
shardyjasond: and just pass instead of raising if the id's match?16:23
lipinskiMentioned this yesterday and just got around to trying again. - Nested provider templates.16:23
lipinskiThese seem to work only if I set all the resources in a registry under /etc/heat/environment.d16:24
shardysdague: No, if you specify user_data_format=RAW, otherwise you also need heat-cfntools16:24
lipinskiIf I set a resource registry in a passed environment file, nested ones are not found.16:24
zanebskraynev: it's not a method, it's a function. you already defined it right there in that patch16:24
sdagueshardy: ok, I've got user_data_format=RAW16:24
thervelipinski, That'd be a bug I suppose16:24
lipinskie.g., template -> ResourceA (providerA) -> ResourceB (providerB) = ResourceB not found16:24
shardysdague: Ok, it should just get passed to cloud-init then16:24
lipinskitherve: ok - will submit.  thanks16:24
shardysdague: otherwise you can use e.g the Fedora cloud image (F20+) which contains heat-cfntools16:25
sdagueoh, it looks like it mostly did work, but blew up earlier than I expected16:25
sdagueshardy: yeh, I was mostly trying to figure out what's testable with just cloud-init on some of these, as that should make us be able to do more things in the gate16:26
sdagueas we could even do quite a bit with cirros16:26
lipinskiok, one more, plese confirm as a bug (and not user error) before I submit: When I use a file URL in resource_registry, there is some corruption of the url16:27
skraynevzaneb: Ou you talk about ancillary function.16:27
lipinskiresource_registry:  "My::Res::Node": "file:///root/My-Res-Node.hot.yaml"16:27
sdagueanyway, at least I'm slightly sanity checked now, I can sort out the specific fail16:27
sdaguethanks16:28
lipinskierror: Could not fetch file:///root/file:///root/My-Res-Node.hot.yaml from the environment16:28
shardysdague: Sounds good - you may also be interested in the new OS::Heat::MultipartMime and OS::Heat::CloudConfig resources then16:28
lipinskiIt's automatically adding on 'file:///$PWD'16:28
sdagueshardy: probably, but I need to walk before I can run16:28
skraynevzaneb: but it looks like recursion , because if we call func.validate, it will call validate() and that function.validate and etc.16:29
jasondshardy: good idea.  i'll see if that will work.  thanks16:29
shardysdague: btw, I'm going to be focussing on tempest tests over the next couple of weeks, please shout if there are any concerns re where I'm putting stuff in the tree ;)16:29
zanebskraynev: why is recursion bad?16:30
*** varora has left #heat16:30
*** nati_ueno has quit IRC16:30
shardysdague: I'm not 100% clear where API testing ends and scenario testing begins, but hopefully we can add some better coverage to both16:30
skraynevzaneb: no, recursion is cool thing, and sometimes it gives head explosion. But I understand my mistake, I thought that it will be infinite recursion16:31
zanebskraynev: say you have a tree like this: http://paste.openstack.org/show/74265/16:32
sdagueshardy: will do16:32
zanebyou need to recurse to make sure you validate both functions16:32
zanebyou can't stop at the first one16:32
*** alexheneveld has quit IRC16:33
zaneband you can't call the validate method on its args, because args is a list, not a Function16:33
zanebso you call validate and it continues traversing the tree16:33
skraynevzaneb: gotcha.16:33
zanebcool :)16:34
skraynevzaneb: I forgot, that in validate we will call on args of function not on this function.16:34
zanebI can see why that would have been confusing :)16:35
*** pvaneck has joined #heat16:35
skraynevzaneb: I guess it is my fatigue today ;) never mind :)16:38
jasondshardy: bah, resource_id isn't set at that point.  i'll just revert the commit that added validation16:40
*** sgordon has quit IRC16:40
openstackgerritJason Dunsmore proposed a change to openstack/heat: Revert "Add validation to KeyPair resource"  https://review.openstack.org/8286216:41
sdagueshardy: yeh, especially with the fact that a lot of heat's API is really the HOT dsl, it's an interesting question. Honestly, my take right now is to determine it by backend image. If we can pull it off quickly with cirros, it's probably game for API16:43
sdagueif it's going to be longer and require a real image, put it in scenario16:44
lipinskiIs there a way to perform a count in a template?  Say, get the size of a list?16:44
shardysdague: Ok, sounds good, I'm starting with fairly minimal exercising of API calls we don't currently hit (in API tests) and plan to move on to more complex "real" tests in scenarios16:45
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Add OS:Barbican:Order resource  https://review.openstack.org/8190616:46
pas-haanyone having problems with latest devstack?16:49
*** jpeeler has joined #heat16:52
*** jpeeler has quit IRC16:52
*** jpeeler has joined #heat16:52
*** tomek_adamczewsk has quit IRC16:58
*** jistr|training has quit IRC16:58
*** IYozhikov_away is now known as IgorYozhikov16:59
*** nati_ueno has joined #heat17:02
*** ifarkas has joined #heat17:03
radixgood morning17:03
*** harlowja has joined #heat17:03
*** cmyster has quit IRC17:05
*** mkollaro has quit IRC17:07
*** tspatzier has quit IRC17:08
*** kgriffs is now known as kgriffs_afk17:10
*** mkollaro has joined #heat17:10
*** ramishra has quit IRC17:11
*** saurabhs has joined #heat17:12
*** ramishra has joined #heat17:13
*** alexheneveld_ has joined #heat17:15
lipinskiany way to set per-instance data on a resourcegroup?17:16
openstackgerritA change was merged to openstack/heat: Don't create cloud-init user unless specified  https://review.openstack.org/7967817:17
*** saurabhs1 has joined #heat17:17
radixlipinski: can you be more specific?17:18
lipinskiI create a ResourceGroup with say 4 instances.  Can I give them each a unique name?17:19
*** sgordon has joined #heat17:19
lipinskie.g., node-1, node-2, node-3, etc.17:19
*** saurabhs has quit IRC17:19
*** ifarkas_ has joined #heat17:20
*** zns has quit IRC17:21
openstackgerritThomas Herve proposed a change to openstack/heat: Include exception in custom constraints errors  https://review.openstack.org/8288117:27
lipinskiradix: you know if that's possible?17:27
radixahem, sorry17:27
radixlipinski: no, names are generated for you17:28
radixlipinski: oh, wait, do you mean resource names or server names?17:29
lipinskiserver names17:29
radixhmm17:29
lipinski(well, any parameters for that matter).17:29
radixI don't _think_ that's possible either17:29
lipinskiIt would be nice if I could pass a list of data for any resource property and that list would be cycled through.17:29
*** rpothier_ has joined #heat17:29
radixlipinski: can you explain your use case?17:30
lipinskie.g., I could have a ResourceGroup of 4 instances.  For a avail_zone, I could pass a [ 'zone1', 'zone2' ] value.  When the group was instantiated, instance 0 would be assigned zone1; instance 1 zone2; instance2 zone1; instance 3 zone217:30
lipinskiI have multiple use cases where I want to have a group of resources that have same properties (for the most part) - e.g., flavor, image, volumes, etc.  But, I just want to pass some data that may differ for each instance.17:31
*** skraynev is now known as skraynev_afk17:32
*** jprovazn has quit IRC17:32
*** rpothier has quit IRC17:33
thervelipinski, You can create 2 groups I suppose for now17:34
lipinskitherve: yeah - by the time I address the handful of different permutations - I end up having to individually specify each server - negating the usefulness of ResourceGroup at all.17:34
*** zns has joined #heat17:35
lipinskiavail_zone was just an example.  Plus, I have a requirement for each VM to be created with a unique name - ResourceGroup can't seem to do that either.17:35
lipinskiRight now, on the OS Dashboard all VMs are spun up with same name.17:35
thervelipinski, servers are created with a unique name already though17:36
*** e0ne has quit IRC17:36
lipinskitherve: I specify a name property to OS::Nova::Server.17:37
lipinskiI have a (now conflicting) requirement about having a user-defined prefix to the server names.17:37
therveWell yeah don't :)17:37
lipinskiI wish.17:37
therveYou can use the stack name maybe17:37
lipinskicustomers have long wish lists :)17:37
lipinskiand short timeframes17:37
lipinskiI'm trying to get to a static template that can be used and support multiple configuration options simply by changing the paraemeters/environment.  It's not working as I'd hope and now will have to have software that generates a custom template for every deployment - at that point, templates start to lose their value pretty quickly as I could just invoke the orchestration myself...17:38
* therve shrugs17:38
lipinskiI know.  I do appreciate the help, though...17:39
lipinskidoes any of this sound like something I should create a blueprint for?  Would that be possibly useful for others?17:39
radixit's unclear what features you would want17:39
lipinskisome way to specify per-instance parameters via a ResourceGroup.  probably easiest though the use of lists17:40
therveThat may be doable17:41
lipinskiI would think it wouldn't be too hard.  I'm no python developer, or I would prototype something myself.  I may try to anyways to learn.  I see the majority of the code in heat/engine/resources/resource_group.py17:42
*** mspreitz has joined #heat17:44
*** jstrachan has quit IRC17:47
*** mestery_ has joined #heat17:48
*** mestery has quit IRC17:48
*** mspreitz_ has joined #heat17:49
*** mspreitz_ has left #heat17:49
*** mspreitz has left #heat17:50
*** mestery_ is now known as mestery17:50
*** derekh has quit IRC17:55
*** imtiaz has joined #heat17:55
*** Darnoth has joined #heat17:56
*** imtiaz has quit IRC17:57
*** mspreitz has joined #heat17:59
mspreitzSpamapS: are you there?18:00
*** yogesh_ has joined #heat18:00
mspreitzzaneb: are you there?18:00
*** kgriffs_afk is now known as kgriffs18:02
thervelipinski, Ideally you would create a blueprint describing what you'd like, with use cases and example templates18:06
therveOtherwise a mail on the list18:06
lipinskitherve: ok - will do.  Thanks18:06
*** packet has quit IRC18:07
SpamapSmspreitz: here for a bit.. whassup?18:08
mspreitzSpamapS: just wanted to confirm some thinking about how to fix that problem where Heat is stuck if an update fails partway through.18:09
mspreitzFirst, is there an official bug for this?18:09
sdakezaneb looks like the murano cats get it to me18:10
sdakezaneb whats your take?18:10
SpamapSmspreitz: Yes...18:10
SpamapSmspreitz: https://bugs.launchpad.net/heat/+bug/116005218:10
uvirtbotLaunchpad bug 1160052 in heat "Need a way to retry failed operations" [High,In progress]18:10
mspreitzthanks18:11
SpamapSmspreitz: and there is a blueprint attached https://blueprints.launchpad.net/heat/+spec/update-failure-recovery18:11
*** packet has joined #heat18:11
SpamapSmspreitz: I have recently confirmed that you can manually recover with abandon/adopt18:12
mspreitzI am having trouble finding the link from bug to blueprint18:12
mspreitzIs there one?18:13
mspreitzI am guessing not.  Moving along..18:14
SpamapSmspreitz: there is18:14
SpamapSmspreitz: it is on the right side, after all the subscribers18:14
mspreitzAh, thanks!18:14
SpamapSmspreitz: and on the blueprint there is a link back to the bug18:14
mspreitzYes, the link in the other direction is nicely obvious18:15
mspreitzSpamapS: In our earlier discussion, and in that blueprint, I do not see the word "workflow".  This gratifies me, I think Heat orchestration is not and should not be as simple as creating and running a workflow.18:16
SpamapSsdake: hey.. I'm a bit concerned about https://review.openstack.org/#/c/79678/ ...18:16
SpamapSshardy: ^^18:16
mspreitzI just wanted to double-check for agreement18:16
sdakeSpamapS which part18:16
SpamapSthat has changed a fairly fundamental thing about how OS::Nova::Server works.. a change I 100% support.. but I wonder if it will be too much surprise.18:16
sdakeSpamapS I guess there are a couple ways to mitigate that18:17
sdakewe could communicate the change (mailing lists, blog posts)18:17
therveWhat's that rule about empty lines between imports?18:17
mspreitzsdake: yes, socialize the change18:17
sdakeIf this is the way forward, we have to accept that at some point our users are going  to have to deal with it18:18
sdakemight as well be sooner rather then later18:18
sdakemspreitz yup but the change has already been made18:18
*** blomquisg has quit IRC18:18
SpamapSsdake: we should to that anyway. But IMO we have to have a cycle where we deprecate the behavior. Which is why I was so surprised at your respons on the users list taht this was "almost merged.18:18
sdakeit can also be documented in the release notes18:18
openstackgerritThomas Herve proposed a change to openstack/heat: Don't catch all exceptions in image constraint  https://review.openstack.org/8284618:19
sdakeSpamapS I see, you mean wait 6 months to fix the bug while warning users its coming?18:19
sdakeI guess my general take is a 6 month warning seems a bit much18:21
SpamapSsdake_: the fix involves changing a default behavior.18:21
sdakeif we take that approach for every change, it quickly becomes untenable18:21
mspreitzSpamapS: sorry to double-team you, but regarding broken updates, I wanted to confirm that others agree that making and running a workflow is not the answer18:21
mspreitzothers here can chime in too18:21
sdakeSpamapS I guess there was a communication breakdown, I did read the review comments in detail before +a the review18:22
mspreitzI mean, not the best answer18:22
sdakeSpamapS suggest adding an item for the wednesday meeting to discuss a plan to either mitigate or revert18:22
SpamapSsdake: we can make the new behavior optional. That makes it a config decision, not a 6 month release upgrade decision.18:23
shardySpamapS: can you clarify what is backwards incompatible?18:23
mspreitzsdake: or make it a per-instance option?18:23
SpamapSmspreitz: ACK, window_size=118:23
shardySpamapS: we still have the ADMIN_USER property, marked as support.DEPRECATED18:23
SpamapSshardy: users who expect to ssh as admin_user will be broken now.18:24
therveSpamapS, is the behavior really changing?18:24
therveIf the conf value stayed the same?18:24
SpamapSshardy: right, we should have it marked as deprecated, but still defaulting to ec2-user .. wait.. we do.. doh18:24
shardytherve: only if they haven't specified a user in heat.conf18:24
therveadmin_user is not even in Havana AFAICT18:25
SpamapSI misread the diff.. so the default stays ec2-user .. and OS::Nova::Server will still, by default, use it?18:25
SpamapStherve: it is. I put it there.18:25
*** shakamunyi has joined #heat18:25
*** shakamunyi has quit IRC18:25
thervehum...18:25
*** shakamunyi has joined #heat18:26
*** shakamunyi has quit IRC18:26
shardySpamapS: Yes, it's still defaulted to ec2-user, but you get the new behavior if you set it to an empty string18:26
therveSpamapS, https://github.com/openstack/heat/blob/stable/havana/heat/engine/resources/server.py where?18:26
sdakeya imo that seems ok18:26
*** lipinski1 has joined #heat18:26
SpamapSOk yeah I read it wrong. Ignore me.18:26
sdakebut definately communicating it makes sense18:26
SpamapSbut thanks for the reassurance :)18:27
*** lipinski has quit IRC18:27
mspreitzIf old config gets old behavior, we are good18:27
mspreitzwell, pretty good18:27
shardymspreitz: AFAICS we do18:27
mspreitzthat just moves the problem from our laps to the operators'18:27
shardyhttps://review.openstack.org/#/c/79678/5/heat/common/config.py18:27
mspreitzthey still have the problem of whether to surprise all their users18:27
SpamapSmspreitz: that is ok. Operators can be expected to read release notes and look for deprecation errors in logs.18:28
SpamapSmspreitz: right, the idea is to let the users know _well_ in advance of the change.18:28
mspreitzYeah, but it's the same kind of problem: at some point an operator has to throw the switch, pissing off any user who has not yet caught up.18:29
SpamapSmspreitz: Yeah.. 6 months may be too short for those users.18:30
sdakewe dont have to deprecate in a 6 month window18:30
SpamapSmspreitz: it is measurable though. An operator has direct contact information for _every_ user.18:31
sdakewe can keep the deprecation in for 12 or 18 months18:31
*** blomquisg has joined #heat18:31
mspreitzSpamapS: agreed, the operators have better contact with users18:31
SpamapSsdake: I think we might want to keep that one around until K18:31
*** alexheneveld has joined #heat18:31
sdakeSpamapS no sweat off my back as long as selinux works ;)18:31
SpamapSmspreitz: excellent point. So, on to workflowing things18:32
sdakewe still have things like describe which were deprecated 2 cycles ago18:32
mspreitzSpamapS: yes, please, I have to leave soon18:32
SpamapSmspreitz: me too. Ok so you are correct. THe idea is that Heat would in fact develop its own workflow to get from point a (where it is now) to point b (where the user wants it to go)18:33
mspreitzI have two reasons for not liking a workflow oriented approach.  1: it is not good at quickly reacting to exogenous changes on either side18:33
*** alexheneveld_ has quit IRC18:34
mspreitz2: it is not good at retry logic that has to back up before it can move forward18:34
*** ifarkas_ has quit IRC18:35
mspreitzSpamapS: What I am saying is that I think the best approach is different from: Heat computes  workflow to move from A to B and then hands it off to dumb workflow engine that can only run that workflow18:36
mspreitzRather I think the best approach is a heat engine that, after making one change, can reconsider A and B and decide what to do next.18:37
mspreitzThat naturally is more pwerful.18:37
mspreitzIt can accommodate changes in A and B that happened while it was working on one thing18:37
SpamapSmspreitz: yes, you're saying, use convergence, rather than workflow18:37
mspreitzyes18:37
SpamapSwe agree18:38
mspreitzI'm late for my next task, I am going away thinking there is agreement here. pls let me know asynchronously if I'm wrong.18:38
SpamapSmspreitz: so I'd like for that to be the way Heat works. I also think that to do that without a lot of spurious errors and retries, we need to get Heat's engine out of the business of tracking state for resources.18:39
mspreitzYes, let Heat use the tracking that others already do, or get info from the true source.18:40
mspreitzLot's more to say, but gotta go now.18:40
SpamapSmspreitz: ciao18:40
*** mspreitz has left #heat18:40
*** e0ne has joined #heat18:41
therveSpamapS, that's interesting. Do you think we shouldn't detect when a server goes into error? Or do you have something else in mind?18:41
openstackgerritRabi Mishra proposed a change to openstack/heat: Provides ability to reference existing neutron resources  https://review.openstack.org/8285318:42
SpamapStherve: Heat has no business monitoring things no.18:44
SpamapStherve: heat-engine I should say18:44
SpamapStherve: but Heat knowing when the monitoring service has detected a failure, and acting automatically, yes.18:44
SpamapStherve: the point is, Heat shouldn't keep track of the state of the resources. It should query or subscribe to notifications only.18:45
shardy+1 on notifications, I'd like to see all the polling for state stuff die18:47
therveYes :)18:47
therveVote for my design summit session!18:47
sdakeya notify would be good18:47
sdakeprefer event driven - more scalable18:47
shardyOoh, have submissions opened now?18:47
therveshardy, About 2 weeks ago18:47
shardyhaha18:48
therve:)18:48
* shardy missed that somehow18:48
*** kgriffs is now known as kgriffs_afk18:50
sdakewhere is the link for the design summit sessions therve?18:50
*** shakayumi has joined #heat18:50
*** shakayumi has quit IRC18:50
* sdake needs better filters18:50
thervesdake: http://summit.openstack.org/18:50
*** shakayumi has joined #heat18:51
sdaketherve thanks18:52
radixzaneb: are you planning on a session for healing/convergence/whatever?18:53
*** ifarkas_ has joined #heat18:53
radixtherve: wait, there's voting now?18:53
therveradix, Not really. During meetings I guess.18:54
radixSpamapS: or you?18:54
radixSpamapS: I'm wondering if there should be something where an external source can say "hey I noticed resource <x> is messed up"18:55
*** ramishra has quit IRC18:55
*** ramishra has joined #heat18:55
SpamapSradix: I have been really focused on getting graceful notifications into some kind of state for TripleO's push for HA.. once that is done, I will think about design sessions.18:56
therveradix, Presumably that's whare notifications are?18:56
SpamapSradix: But yes I want that to be the push18:56
therves/whare/what18:56
radixSpamapS: well, yes, but I'm specifically thinking it needs to be a notification about specific resources18:56
radixer, s/SpamapS/therve/18:56
radixtherve: just telling heat "hey fix yourself" means checking all resources in a stack, which can be too much18:57
radixif we say "I found that resource X is dead" would allow heat to only repair that one resource without having to recheck everything else18:57
shardyradix: but convergence starts with checking all resources anyway18:57
radixshardy: no, not "checking"18:58
therveradix, Who's "I" in "I found"?18:58
sdakeradix therve there is no voting for design sessions18:58
shardyradix: well that's the model we've been working towards - stack-check aligns DB status with the world, stack-converge fixes the world so all is good again :)18:58
radixshardy: hm, stack-align sounds unscalable18:58
SpamapSradix: oh .. hmmm18:59
*** che-arne has quit IRC18:59
shardyradix: or are you saying notify some out of band metric such as application status?18:59
SpamapSradix: that is a bit backwards from what I think Heat should do18:59
*** derekh has joined #heat18:59
thervesdake: I meant that some needs to be selected for the summit. It's more free flow indeed18:59
*** jistr has joined #heat18:59
SpamapSradix: I think Heat should subscribe to "server X status" ... the thing that knows about server X doesn't know about "resources"18:59
shardyradix: no more unscalable than create or update - asycnronous notifications/monitoring should happen via ceilometer, not heat18:59
*** ramishra has quit IRC18:59
radixshardy: no, I'm saying e.g. some monitoring system that would watch nova RPC events (or in the future, hopefully marconi queues or whatever that nova publishes)19:00
radixwhatever it is, I don't think "check the world" is feasible19:00
therveradix, Yeah those are notifications19:00
SpamapSshardy: so I think we should just eliminate the DB status.19:00
shardyradix: Ah, Ok well that makes sense, I thought you were talking about operator interaction19:00
*** bgorski has quit IRC19:00
sdakeI wonder how many session slots we have available19:01
shardySpamapS: possbly, but it's useful as a cache so we don't have to poll for every user resource-show request19:01
SpamapSwe still have to poll.19:02
SpamapSwell.. sorry.. we still SHOULD19:02
shardySpamapS: we'd just use it for caching the latest notification19:02
*** jprovazn has joined #heat19:02
SpamapSthat status is a lie..19:02
sdakeif you use the notification system you dont have to poll19:02
sdakehowever, not all services implement notifications19:02
shardysdake: ++19:02
sdakeso I think the expectation that we could rely on that as a general means may not be possible to meet19:02
SpamapSright so notifications are an optimization.19:02
sdakeyup optimization plain and simple19:03
therveWell we need to do it incrementally anyway19:03
shardysdake: Yeah I just added a comment to therve's session proposal saying we should start with an analysis of the state of notifications accross projects19:03
therveIt's like like we can flip a switch19:03
SpamapSPolling for resource-show seems fine. Polling for resource-list might be a bit much.. but we can give the user ids.. and a --poll to get real statuses.19:03
therveIt's *not* like we can flip a switch19:03
SpamapSBut the status we show in resource-list ... is a lie.19:03
SpamapSas are many caches. :)19:03
shardytherve: Yeah, just be good to know that the functionality exists in a usable state in many/most of the projects19:03
sdakewe may have to bootstrap some of the notification efforts in other projects if we really want to use that as part of our resource lifecycle19:04
sdakewhich is pretty straightforward, notifications are dead smiple to develop19:04
SpamapSimagine there are no notifications19:04
therveshardy, Oh yeah. I'm sure it can be half broken. It was in nova not long ago19:04
*** julienvey has joined #heat19:04
SpamapShow bad is it, really, to poll statuses of servers when you need them. When do you _actually_ need them?19:04
sdakethe big problem I see with notifications is that theyare less reliable then polling given the half-hearted attempt at notifications most projects undertake ;)19:05
radixsorry got distracted19:05
*** shakayumi has quit IRC19:05
radixSpamapS: I want to make sure there's a design that's _possible_, or a way forward, that doesn't involve polling19:05
shardyradix: +119:06
sdakeradix who is this cat http://summit.openstack.org/cfp/details/12619:06
sdakeI'm not familiar with him19:06
SpamapSradix: why?19:06
radixSpamapS: because it's unscalable? :)19:06
SpamapSwhat makes it unscalable?19:06
radixSpamapS: imagine a stack with 1000 nodes19:06
sdakepolling is inherently less scalable19:07
radixthat's at least 1000 calls to nova every time we need to check19:07
shardySpamapS: part of the problem is the cost of all the API requests, e.g creating 100 empty stacks on my machine takes nearly a minute due to all the API overhead (keystone etc)19:07
sdakebut it isn't unscalable19:07
radixif we can just *be notified* when a node goes down, we can double check that node's status and recreate it if necessary19:07
SpamapSIf I have a cloud.. which can host 1000 nodes, I expect that the status for those nodes will be queried quite often.19:07
thervesdake: Were you in Portland? Ken was there.19:07
*** lindsayk has joined #heat19:07
sdaketherve no19:08
sdakeis he a rackspace guy?19:08
radixsdake: yes19:08
sdakeengineer, manager ?19:08
SpamapSshardy: yes if I tried to host a cloud on a developer machine I would expect everything to serialize and basically suck ;)19:08
radixengineer manager :)19:08
sdakeso both then radix ? :)19:08
radixsdake: yes19:08
*** zns has quit IRC19:09
radixSpamapS: rate limiting!19:09
SpamapSis a crime19:09
therveradix, Note that you'll have thousands of API calls when you create the stack anyway19:09
radixit's *really* annoying to try to check the status of 1000 nova nodes19:09
SpamapSradix: batching!19:09
therveSo if you redo a check later, it's not more expensive than creating one19:09
sdakethis looks interesting19:09
radixtherve: I create 1000 node stacks way fewer than they would be checked19:09
sdakehttp://summit.openstack.org/cfp/details/119:10
therveradix, Getting the status of a server is also way cheaper than creating one :)19:10
therveSo all in all...19:11
radixwe can have a polling mechanism if you want19:11
therveAt any rate, I agree with you that we should optimize our number of calls. Or the quality of them. But we need some19:12
*** lindsayk1 has joined #heat19:12
*** lindsayk has quit IRC19:12
radixbut I hope that whatever mechanisms we have in heat will allow us to take advantage of notification if/when it becomes available to tell it which resources have died19:12
therve+119:12
thervePeople uses notifications for billing. They must work :)19:12
radixrackspace already has an event feed from its cloud servers that I'd like to take advantage of by writing a bit of glue to heat19:13
radixand avoid having to check all resources in a stack when some failure is detected19:13
radixand I *hope* that nova itself grows support for sending push-y notifications to something like a marconi queue19:14
shardySpamapS: My point is the API overhead is significant, using lightweight amqp notifications and caching the status locally is likely to perform better, especially if you have lots of customers in a large cloud :)19:14
radixtherve: yeah, though on the private RPC :P19:14
therveradix, I think we should use those for now19:14
therveIf the interface becomes better, we'll switch19:14
radixwell, someone can use them, I don't think we can :)19:15
radixRS heat deployment is outside of the nova datacenter19:15
radix(actually it's running *on* that cloud...)19:16
therveThe key is probably to separate the resource creation from the status check19:16
therveThen you could be able to plug a different event feed19:16
*** alexheneveld has quit IRC19:16
radixby creation do you mean re-creation?19:16
therveNo I mean creation in general19:17
radixwell... what about the deletion of the resource?19:17
radixwhen it turns bad19:17
therveYeah same thing19:17
radixit's not really identical to the initial creation19:17
therveIt is in the sense that we do an action, and then wait for the result by doing get forever19:17
*** openstackgerrit has quit IRC19:18
radixtherve: I think the proposed "stack-converge", if there's an alternative mechanism than the proposed "stack-align"19:18
therveI don't really think about convergence for now19:18
*** openstackgerrit has joined #heat19:18
radixer19:18
radixI meant to say I think stack-converge is good19:18
therveI'm mostly thinking about removing polling from Heat19:18
radixtherve: which polling?19:18
therveradix, The one we do after each action19:18
radixahhh19:19
radixI see19:19
therveeg nova.boot(). while x: server.get()19:19
radixyeah19:19
therveThat introduces notifications gently into Heat :)19:19
therveThen maybe convergence and all can benefit from it19:19
radixI guess that'd be good19:20
*** kgriffs_afk is now known as kgriffs19:21
*** kfox1111 has joined #heat19:21
kfox1111YAY. I just got a leter from legal saying I can contribute to OpenStack. :)19:21
radixkfox1111: hooraaaaaaaaaaaaay19:21
kfox1111So, should I create blueprints for heat-templates for mongodb and elasticsearch?19:22
radixkfox1111: what, you mean just the example templates?19:22
*** denis_makogon has quit IRC19:22
radixkfox1111: I don't think heat-templates typically has blueprints19:22
kfox1111so just a review then?19:22
*** dmakogon_ has joined #heat19:23
radixyou can just submit them for review in gerrit19:23
radixyeah19:23
kfox1111k. thanks. :)19:23
sdakekfox1111 HELL FROZE OVER GRATZ! :)19:23
kfox1111:)19:23
sdakekfox1111 b lueprints for heat-templates aren't really required19:23
sdakethe requirements around that repo are pretty informal19:23
radixtherve: so I guess there needs to be a way to push a "this resource just transitioned to status X" message to heat19:23
sdakefor example, we have a noop check/gate19:23
radixtherve: those messages could be subscribed to by things like resource-waiting-for-creation, and the states could also be written to the DB for stack-converge to check later19:24
therveradix, Yep. In an internal API though.19:24
radixtherve: well, I think it should be external too :)19:24
radixwell... hmm19:24
radixmaybe internal is ok regardless19:25
radixso I guess we don't have to argue about that :)19:25
*** duncanjw has quit IRC19:27
*** alexheneveld has joined #heat19:27
*** tango has joined #heat19:27
radixok, I'm going to grab some lunch19:29
radixbbl19:29
*** arbylee has quit IRC19:34
*** arbylee has joined #heat19:36
*** shakayumi has joined #heat19:45
*** shakayumi has quit IRC19:45
*** kfox1111 is now known as Guest5994619:48
*** kfox1111 has joined #heat19:48
*** kfox11111 has joined #heat19:48
kfox1111"Caution: Do not check in changes on your master branch. Doing so will cause merge commits when you pull new upstream changes, and merge commits will not be accepted by Gerrit."19:48
kfox1111Does that mean you should branch before committing any changes?19:48
kfox1111does the branch name matter and do you need one per new review, or only per feature?19:49
*** IlyaE has quit IRC19:49
*** andersonvom has quit IRC19:50
*** kfox11111 has quit IRC19:51
*** shakayumi has joined #heat19:54
openstackgerritKevin Fox proposed a change to openstack/heat-templates: Add a scalable ElasticSearch cluster set of templates in Hot format.  https://review.openstack.org/8290319:55
*** ramishra has joined #heat19:56
*** shakamunyi has joined #heat19:56
*** shakayumi has quit IRC19:58
*** duncanjw has joined #heat20:00
*** rbuilta has quit IRC20:02
*** shakamunyi has quit IRC20:03
*** derekh has quit IRC20:05
*** jistr has quit IRC20:06
*** shakamunyi has joined #heat20:06
*** IlyaE has joined #heat20:07
*** e0ne has quit IRC20:15
*** jprovazn has quit IRC20:15
*** e0ne has joined #heat20:16
*** e0ne has quit IRC20:20
*** BillArnold has joined #heat20:22
*** mkollaro has quit IRC20:23
*** alexheneveld has quit IRC20:24
shardykfox1111: You should branch per topic (e.g per bug or per blueprint)20:26
shardykfox1111: e.g I do git checkout -b bug/123456 or git checkout -b bp/my-new-feature20:26
shardythen commit your changes, rebase as needed using rebase -i origin, and then submit the series via git review20:27
shardynote you should do git review -s before the first commit so the hook which adds the ChangeId is setup20:27
thervestevebaker, I'd like possible to have the constraint fixes in icehouse20:28
stevebakertherve: OK, feel free to add the milestone back, then ping individuals for reviews20:29
thervestevebaker, How does it work? Can gerrit still merge in master?20:29
stevebakertherve: there won't be an rc1 release until bugs go to zero, either by fixing in master or deferring20:30
stevebakerI'm trying to be brutal about deferring because we're quite behind http://old-wiki.openstack.org/rc/20:30
therveOK no problem. Those bugs are not critical, we can backport them later if deemed useful.20:31
*** mkollaro has joined #heat20:32
stevebakeralso I expect there will be an rc220:34
kfox1111shardy: ok, thanks. :)20:34
*** vijendar has quit IRC20:37
*** vijendar has joined #heat20:37
*** vijendar has quit IRC20:39
*** insanidade has quit IRC20:40
sdake_stevebaker I think that idea of not validating the templates for all operations but update and create will be pretty invasive20:46
sdake_we don't actually validate, the parser plugin does that work20:46
openstackgerritRabi Mishra proposed a change to openstack/heat: Provides ability to reference existing neutron resources  https://review.openstack.org/8285320:47
sdake_so we need to either hack the plugin or make a new one20:47
*** ramishra has quit IRC20:47
*** ramishra has joined #heat20:48
stevebakersdake_: another option is reverting that change until we come up with a migration strategy20:49
sdake_you mean reverting the pluggable parsers?20:50
stevebakersdake_: revert the specific validation which is causing existing stacks to fail validation (checking template version?)20:51
zanebwhat bug are we talking about?20:52
*** ramishra has quit IRC20:52
stevebakerhttps://bugs.launchpad.net/heat/+bug/129685920:52
uvirtbotLaunchpad bug 1296859 in heat "stack-list throws an error if any stack returned contains a template error" [Medium,Triaged]20:52
stevebakerERROR: "2014-03-07" is not a valid heat_template_version. Should be one of: ('2013-05-23',)20:52
sdake_it isn't just checking tmeplate version20:52
sdake_but that is easy enough to hack around20:53
sdake_the entire parser is different20:53
zanebworkaround: don't upload broken templates ;)20:53
sdake_zaneb the templates are already in the db20:53
sdake_and they can't be shown/deleted/worked on20:53
stevebakerzaneb: these templates were already in before that validation was added20:53
zanebyeah, it's a bummer20:54
zanebwe could add a DB migration to fix 'em?20:54
sdake_it makes heat unworkable - the templates cant even be deleted20:54
sdake_rather the stacks20:54
zaneblike we did with all of the recent HOT changes20:54
stevebakerI thought stack-list avoided parsing each stack anyway, for performance20:54
sdake_stevebaker it calls stack.load, which calls template.lod which calls the pluggable parser parsing code20:55
thervestevebaker, It doesn't gather outpus20:55
therveoutputs20:55
sdake_one option is to make pluggable parsers in the mainline which are less strict20:56
sdake_and only call those for cases not in update/create20:56
sdake_this is what i'm working on now20:56
sdake_but it won't be tidy20:56
zanebsdake_: https://review.openstack.org/#/c/73580/7/heat/db/sqlalchemy/migrate_repo/versions/041_migrate_hot_template_resources.py <- something like this20:57
*** IlyaE has quit IRC21:01
sdake_zaneb you think doing that for just the version field would cover all the cases of mixed hot+cfn use since you already have that migration?21:01
*** radez is now known as radez_g0n321:01
sdake_zaneb it looks like that migration doesn't handle parameters or intrinsics21:02
sdake_I don't understand the details of the parser enough to know if that matters or not21:03
zanebafaik you'd just have to go through and wherever you see hot_template_version change it to 2013-05-23, wherever you see HeatTemplateFormatVersion change it to 2012-12-12 and wherever you see AWSTemplateFormatVersion change is to 2012-09-0921:04
sdake_cool21:04
sdake_well that is nice and tidy21:04
zanebfor that bug, anyway21:05
sdake_i'm wondering if there are other cases outside of the heta version fiel dthough21:05
zanebwe haven't yet removed the old intrinsic functions from HOT21:05
zanebalthough tspatzier has suggested it, which means we'd need another migration21:05
sdake_ok so intrinsics aren't a problem21:05
sdake_what about parameters?21:06
zanebyet ;)21:06
zanebparameters were the first thing implemented in HOT, so I don't think they've changed21:06
sdake_could folks mix hot and cfn parameter syntax?21:06
sdake_prior to your rework of the pluggable parsers?21:06
zanebthe pluggable parser stuff didn't really touch that, but tspatzier's work during Icehouse to replace the parameters parsing definitely did21:08
*** pafuent has quit IRC21:08
zanebbut I'm not sure if it allowed a mix beforehand or not21:08
zanebyou might need to check with him21:08
sdake_i'll test it out on havana21:08
sdake_so sounds like we may have two bugs21:08
sdake_and then all the possible failure scenarios are fixed21:08
*** shakayumi has joined #heat21:08
zanebactually, I think it did allow a mix, because I remember fixing one of the OpenShift templates that had a mix21:09
*** blomquisg has quit IRC21:09
*** shakayumi has quit IRC21:09
sdake_so assuming I add migrations for those two things, are there more things we need to address?21:09
*** alexheneveld has joined #heat21:10
*** shakamunyi has quit IRC21:11
sdake_are we allowed to change existing migration patches?  One scenario with version is if we come out with a new hot version, and I simply replace every version with 2013-05-23, I dont want to break new versions21:12
*** aweiteka has quit IRC21:12
sdake_so theoretical migration patch would need to whitelist the new versions as they come into the source base21:13
sdake_zaneb eg assume that the new versions are good if they are in the template for future migrations21:14
zaneb"are we allowed to change existing migration patches" <- no.21:14
sdake_so when that migration runs in the future, it would change to the old version of hot if there was a new template version21:15
*** ifarkas has quit IRC21:15
zanebalthough... adding to a whitelist might not be the worst thing21:15
sdake_ya seems like a reasonable exception to me21:16
*** ifarkas_ has quit IRC21:16
zanebrandallburt was talking at one point about having a script that ran on demand, rather than a DB migration21:16
zanebjasond: any idea what the outcome of that ^ was?21:16
sdake_stevebaker given that migrations can't be backported, i think we will need to fix both of these before release21:19
sdake_zaneb since this is our last chance to fix thee, can you think of other scenarios besides version and parameters which should be migrated?21:19
zanebsdake_: not that I can think of, but ping tspatzier with an email. He has done most of the work in this area21:21
sdake_zaneb will do thanks21:21
*** blomquisg has joined #heat21:23
*** lindsayk1 has quit IRC21:25
sdake_stevebaker I'll have migration patches ready for review tomorrow21:26
sdake_nearing my end of  day here and not sure i can get er done today21:26
*** asalkeld has quit IRC21:28
stevebakersdake_: ok, thanks. I guess migrating to an arbitrary version is better than nothing21:29
*** achampion has quit IRC21:29
*** julienvey has quit IRC21:30
zanebsdake: rather than whitelisting versions, you could just modify all versions that look like a date and are before the scheduled Icehouse release21:31
zanebon the theory that if anyone genuinely creates a new version, it will be after then21:31
*** gokrokve has quit IRC21:32
*** andersonvom has joined #heat21:32
radixI wonder if it's worth having a cross-team session about notifications21:37
*** rpothier_ has quit IRC21:40
*** andersonvom has quit IRC21:40
sdake_stevebaker we will need a general exception to be able to change migrations in the future to add to the whitelist of versions *not* to migrate21:40
sdake_the migration in quesiton i mean21:40
sdake_radix i htink that would be great!21:40
zanebradix: I think randallburt proposed one in the Heat track already21:41
zanebif he hadn't already, I was going to ;)21:41
*** IlyaE has joined #heat21:43
*** alexpilotti has joined #heat21:44
openstackgerritA change was merged to openstack/heat: Add subnets as a dependency for router  https://review.openstack.org/8245221:44
sdake_nova sort of standardized em21:45
sdake_but not in a real consstent way with other projects21:45
sdake_zaneb some people have put the current date in the template version21:45
sdake_in fact the bug does that :(21:45
sdake_zaneb actually that is a really good idea21:45
sdake_zaneb sorry didn't see your original msg inbetween21:45
radixjust filed http://summit.openstack.org/cfp/details/144 (convergence)21:45
radixzaneb: therve proposed one about heat21:45
radixbut I think he's just talking about using existing nova RPC notifications21:46
*** lekha has quit IRC21:46
zanebradix: I was referring to http://summit.openstack.org/cfp/details/8621:46
sdake_bitcoin miners still making 100 a  day21:46
* sdake_ yays21:46
radixzaneb: oh21:47
*** blomquisg has quit IRC21:47
*** russellb has quit IRC21:47
radixI think we are talking about different things :)21:47
zanebperhaps21:47
zaneb;)21:47
*** zigo has quit IRC21:47
*** wendar has quit IRC21:47
radixI didn't really give much context, that's my fault21:47
zanebradix: what did *you* mean by 'notifications'?21:47
*** lekha has joined #heat21:48
*** lindsayk has joined #heat21:48
radixI'm talking about stuff like nova sending notifications about lifecycle events for its resources to other services21:48
radixover something a bit more accessible (dare I say "public") than the existing RPC thing21:48
*** russellb has joined #heat21:48
radixe.g. marconi21:48
sdake_zaneb i parsed radix's suggetstion as getting the various projects in the room together to standardize the notifications across project21:48
radixgranted marconi isn't even a part of openstack so it may be early times21:48
radixToo Soon21:48
sdake_eg - make a notification specification21:49
radixright21:49
*** wendar has joined #heat21:49
*** zigo has joined #heat21:49
*** lindsayk has quit IRC21:57
*** jmckind has quit IRC22:00
*** blomquisg has joined #heat22:00
*** lindsayk has joined #heat22:01
*** mwheckmann has quit IRC22:02
openstackgerritA change was merged to openstack/python-heatclient: get_file: do not read same url once again  https://review.openstack.org/8088222:04
openstackgerritA change was merged to openstack/python-heatclient: get_file: encode non utf-8 encoding files via base64  https://review.openstack.org/7644322:04
openstackgerritA change was merged to openstack/heat: Revert "Add validation to KeyPair resource"  https://review.openstack.org/8286222:04
*** sgordon has quit IRC22:04
*** lindsayk has quit IRC22:04
sdake_anyone know when you write migrations if you typically write test cases for them?22:06
*** BillArnold has quit IRC22:06
stevebakersdake_: we have been doing that recently, yes. but its usually quite superficial; does the column exist...22:07
stevebakerAny reviews for this? https://review.openstack.org/#/c/82394/22:07
*** lindsayk has joined #heat22:08
sdake_stevebaker looks good22:10
*** jcru has quit IRC22:15
openstackgerritSteve Baker proposed a change to openstack/heat: Make OS::Nova::Server networks property updatable  https://review.openstack.org/7429922:18
*** dims_ has quit IRC22:18
*** yogesh_ has quit IRC22:18
*** blomquisg has quit IRC22:18
stevebakerrebased the test ^ feel free to review22:18
*** zns has joined #heat22:19
stevebakerreviews for this please? https://review.openstack.org/#/c/81558/22:19
*** IlyaE has quit IRC22:24
*** zns has quit IRC22:25
*** zns has joined #heat22:25
*** arbylee has quit IRC22:27
*** varora has joined #heat22:28
*** blomquisg has joined #heat22:31
*** dims_ has joined #heat22:34
*** lindsayk has quit IRC22:38
*** lindsayk has joined #heat22:39
*** arbylee has joined #heat22:39
*** arbylee has quit IRC22:43
*** jergerber has quit IRC22:44
*** rcleere has quit IRC22:46
*** achampion has joined #heat22:46
*** jpeeler has quit IRC22:54
openstackgerritA change was merged to openstack/heat: Don't catch all exceptions in image constraint  https://review.openstack.org/8284623:02
*** david-lyle has quit IRC23:08
*** faramir1 has joined #heat23:14
*** rpothier_ has joined #heat23:25
*** giulivo has quit IRC23:28
*** mkollaro has quit IRC23:30
*** mkollaro has joined #heat23:31
*** tango has quit IRC23:47
*** blomquisg has quit IRC23:47
*** faramir1 has quit IRC23:48
*** cfriesen has quit IRC23:57

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