Tuesday, 2013-12-17

*** tomek_adamczewsk has quit IRC00:06
*** tomek_adamczewsk has joined #heat00:06
asalkeldstevebaker,  https://dl.dropboxusercontent.com/u/2663410/2013-12-17%2011.06.04.jpg00:07
*** brint has quit IRC00:08
stevebakerkangaroo? Koala>00:08
stevebaker?00:08
asalkeldhaha00:08
asalkeldno just beef00:08
*** jcru has quit IRC00:10
sdake_angus have time for a phone call?00:12
asalkeldsure sdake00:13
*** tomek_adamczewsk has quit IRC00:26
openstackgerritTim Schnell proposed a change to openstack/heat: Adds Parameter Label to HOT spec and parameter schema  https://review.openstack.org/6241800:34
*** dims has quit IRC00:37
*** faramir1 has joined #heat00:38
*** dims has joined #heat00:39
timsstevebaker if you get a change to review ^^00:44
timswould love some feedback on general implementation00:44
timschance*00:44
*** pvaneck has quit IRC00:45
stevebakertims: ok, will do00:46
timsthanks :)00:46
stevebakertims: ah, I wanted to talk to you about that one.00:46
timsok00:46
*** dims has quit IRC00:47
stevebakerI'm thinking that the parameter name is the right thing to display. Having an alternative label just hides a thing that has real meaning in the stack. From a UX point of view this seems like a step back. We don't have labels for resources and outputs - I think parameters might be in the same category00:48
stevebakerIts entirely up to the template author to choose param names which are easy_to_understand00:49
timsI viewed it as a step forward from running django expressions to try and humanize the variable name00:51
timsI would argue that we may want to move in the direction of adding labels to things that may be interpreted into HTML at the UI level00:54
timsI think there is a fair amount of precedence for it00:54
*** nosnos has joined #heat00:54
timsI can imagine reasons where you may want parameter names short but labels larger and more descriptive00:55
timsdb_port vs database_port00:55
stevebakerdo we auto-humanize?00:55
timsI was just looking it up00:55
timsHorizon does in general00:55
stevebakerjust checking now00:56
stevebakerI remember trying it and it looked terrible00:56
timswe are manually humanizing labels that don't come from heat00:57
timshttps://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/stacks/forms.py#L17700:57
timswhich would look inconsistent if we aren't humanizing00:57
timsyeah its not super great I agree00:57
timshence adding labels to heat00:57
timsok at a quick glance it looks like we are passing the keynames without doing much to them01:00
stevebakerMy issue is that someone who launches the same stack via heatclient and horizon won't recognise the parameters, we are actually hiding information that they really need (ie, the parameter name)01:00
timsYeah, I get that, but I'm hoping that that user is smart enough to read the template for the parameters01:01
timsas opposed to the user who has no clue01:01
timsabout anything in Heat01:01
timsand is just filling out the form in the UI01:01
stevebakerheatclient is a UI too. the prettytable responses used to humanize the column names, but again that hid vital stack information so now it just outputs the raw attribute keys01:02
timsI would also say that perhaps the Heatclient is due for some upgrades when it comes to prompting for parameters01:02
timsits a UI for a different type of user perhaps01:02
*** dims has joined #heat01:02
timswe humanize the columns in the table for Horizon for example01:04
*** nosnos has quit IRC01:06
stevebakerI think we need to punt this to be discussed by some UX people. heatclient and horizon may or may not used by different personas but I'm not aware that those personas have been defined anywhere yet01:06
*** nosnos has joined #heat01:06
timsThere is precedent in humanizing parameter names and keys in all of the other project implementations that I have looked at in Horizon01:06
openstackgerritRichard Lee proposed a change to openstack/heat: Add way to group exceptions in DependencyTaskGroup  https://review.openstack.org/6247901:06
openstackgerritRichard Lee proposed a change to openstack/heat: Refactor Instance#_check_active  https://review.openstack.org/6247801:06
timscool01:06
timsI can start a thread on the UX askbot01:06
tims?01:06
timsif you are ok discussing it there01:07
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Check resources are in expected states  https://review.openstack.org/5864101:07
stevebakertims: but in this case the thing we're humanizing is something that is in the template, not some hard-coded label. I think this is the *one* good case for leaving some mildly technical name there, because they are doing something mildly technical01:08
stevebakertims: sure, point me at the askbot01:08
timshttp://ask-openstackux.rhcloud.com/questions/01:09
timsI'll write something up and post there tomorrow, its gettting late in the day for me01:09
stevebakerMaybe something like this would be acceptable:01:09
stevebakerlabel (name)01:09
timsI could be convinced of that for implementation in Horizon01:10
timsIt's not super pretty :P01:10
stevebakerand dare I suggest that labels should be localizable ;)01:11
timsthat's a good point01:11
timsI think that having labels is also going to be an accessibility thing01:11
stevebakersurely the description and helptext help here, I'm all for that01:12
timsit's easier for JAWS to read "Database Port" than "db_port"01:12
sdake_http://money.cnn.com/2013/12/16/investing/penny-stock-trader-millionaire/index.html?hpt=hp_t301:12
timsanyway, definitely worth continuing in the UX forum01:13
stevebakeryup01:13
timshaha, nice sdake_01:13
timsI'll post the link here once I get something up01:14
timshave a good night01:14
sdake_But he lost all of that over the course of a year and decided he needed to quit gambling. So he took a shot at investing.01:14
sdake_and the difference is/01:14
sdake_?01:14
sdake_oh here is the difference:01:15
sdake_"I think it's mainly for people who are gamblers," said Sykes, who taught himself all about trading. "But at casinos you play with low odds. With penny stocks, there are patterns that are very predictable."01:15
sdake_that cat doubled up 9 times01:17
*** andersonvom has quit IRC01:18
*** andersonvom has joined #heat01:18
*** andersonvom1 has joined #heat01:19
*** andersonvom has quit IRC01:19
*** rpothier_ has joined #heat01:20
*** randallburt has quit IRC01:20
*** andersonvom1 has quit IRC01:22
*** arbylee has quit IRC01:22
*** brint has joined #heat01:22
*** arbylee has joined #heat01:22
*** arbylee has quit IRC01:27
*** IlyaE has quit IRC01:29
*** swygue has joined #heat01:42
lifelessugh, I wish the heat locale files were not under heat/01:49
lifelessmakes grepping a PITA01:49
*** shakayumi has joined #heat01:51
*** AndrewMichalik has quit IRC01:51
*** randallburt has joined #heat01:52
*** jergerber has quit IRC01:53
*** radix_ has quit IRC01:58
*** nati_ueno has quit IRC02:01
openstackgerritlifeless proposed a change to openstack/heat: Add support for rebuild --preserve-ephemeral.  https://review.openstack.org/6252002:07
lifelessSpamapS: read it and weep ^02:07
*** randallburt has quit IRC02:08
*** arbylee has joined #heat02:15
*** andersonvom has joined #heat02:15
*** erkules_ has joined #heat02:18
*** erkules has quit IRC02:21
*** yogesh has quit IRC02:23
*** nati_ueno has joined #heat02:30
*** liang has joined #heat02:30
*** faramir1 has quit IRC02:31
lifelessstevebaker: ping - is the separate -P foo -P bar thing in a heatclient release ?02:32
*** brint has quit IRC02:33
stevebakerlifeless: yep, at least 2 releases I think02:36
lifelesscool, thanks02:37
*** swygue has quit IRC02:38
*** swygue has joined #heat02:45
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Check resources are in expected states  https://review.openstack.org/5864102:47
*** vkozhukalov has joined #heat02:48
*** SushilKM has joined #heat02:48
*** slong has joined #heat02:48
*** ccs has quit IRC02:51
*** faramir1 has joined #heat02:51
lifeless2013-12-17 02:51:15.637 2202 INFO migrate.versioning.api [-] 30 -> 31...02:51
lifelessERROR: (OperationalError) (1005, "Can't create table 'heat.stack_lock' (errno: 150)") '\nCREATE TABLE stack_lock (\n\tstack_id VARCHAR(36) NOT NULL, \n\tcreated_at DATETIME, \n\tupdated_at DATETIME, \n\tengine_id VARCHAR(36), \n\tPRIMARY KEY (stack_id), \n\tFOREIGN KEY(stack_id) REFERENCES stack (id)\n)ENGINE=InnoDB CHARSET=utf8\n\n' ()02:51
lifelesswould you like a bug for that?02:51
*** SushilKM has quit IRC02:52
*** dims has quit IRC02:53
lifelessstevebaker: ^02:53
*** dims has joined #heat02:53
*** rpothier__ has joined #heat02:53
lifelessstevebaker: I'm guessing a stack lock patch implies you're not doing the distributed thing we sketched out >02:54
lifeless?02:54
asalkeldlifeless, it assumes you are not using zookeeper02:55
lifelesswe're not, but the distributed thing we talked about didn't use zookeeper either; it was lock-free02:55
asalkeldaaa, yeah that is a big chunck of work not yet started02:56
lifelessanyhow02:56
lifelesswhat should I do about this barfing migration ?02:56
*** rpothier_ has quit IRC02:56
lifelesswe were on 28, now I'm on 30 but stuck :)02:56
asalkeldlifeless, I am looking ...02:57
lifelessasalkeld: I can file a bug if you like02:58
asalkeldok02:58
lifeless(while you poke around)02:58
lifelesshttps://bugs.launchpad.net/heat/+bug/126160502:59
uvirtbotLaunchpad bug 1261605 in heat "migration 30 -> 31 (031_stack_lock)  fails" [Undecided,New]02:59
asalkeldwe really need a migration test02:59
*** aignatov has joined #heat03:00
*** giulivo has quit IRC03:00
lifelessasalkeld: http://stackoverflow.com/questions/16227199/mysql-errno-15003:01
lifelessIf you're using the InnoDB engine, the ON DELETE SET DEFAULT is your problem. Here's an excerpt from the manual:03:01
lifeless        While SET DEFAULT is allowed by the MySQL Server, it is rejected as invalid by InnoDB. CREATE TABLE and ALTER TABLE statements using this clause are not allowed for InnoDB tables.03:01
lifelesshmm, no, ignore that, doesn't obviously apply03:02
*** SushilKM has joined #heat03:03
asalkeldI don't see a set default in the migrate03:03
lifelessright, I was just injecting random stackoverflow content03:04
lifelessheat wasn't entirely in the thing03:04
lifelesss/heat/head/03:04
asalkeldhttps://github.com/openstack/heat/blob/master/heat/db/sqlalchemy/migrate_repo/versions/030_remove_uuidutils.py#L2203:04
asalkeldcould it be that?03:04
lifelesswait, what - primary key and foreign key - methings the schema is too clever03:05
*** nanjj has joined #heat03:05
lifelessyeah different types would do it03:05
asalkeldso have stack_lock_id and stack_id03:06
lifelessdropping the stack_id does indeed fix it03:06
lifelesserm the FK03:06
lifelessdoes anything use the stack_lock table yet?03:06
asalkeldthis was backed out before because of this:(03:07
lifelessI think the schema is being overly clever.03:07
lifelessKISS: if you relate to something else, match it's type exactly.03:07
lifelessIf you are a separate table, you get your own ID.03:07
lifelessWhat you tell users about can be different.03:07
lifelessso stack.id should be an autoassigned int, for instance03:07
lifelessstack.uuid should be a uuid03:08
lifelessanyhoww03:08
lifelesswhat do we do ?03:08
asalkeldjasond`, should fix his patch03:09
asalkeldI could work up a wip patch to speed things up03:09
lifelessasalkeld: this is in trunk...03:10
lifelessasalkeld: which we deploy03:10
asalkeldok, let me see  if I can make a quick fix/ the alternative is another revert03:11
lifelessasalkeld: so, this came in Nov 12 - I'm not sure why noone else has noticed03:11
lifelessasalkeld: or maybe git is lying to me :)03:11
lifelessah no, merge of an old patch03:11
lifelessso, I'll revert it out of the tree I have here, to get things unbroken03:12
lifelesslet me know if you want /need me to try a fixed version03:12
asalkeldk03:12
*** faramir1 has quit IRC03:16
lifelessadded the patches to revert (I think!) to the bug03:18
*** nanjj has quit IRC03:22
*** nanjj has joined #heat03:22
*** rushiagr has joined #heat03:23
*** shakayumi has quit IRC03:24
*** faramir1 has joined #heat03:28
*** gokrokve has quit IRC03:31
*** AndrewMichalik has joined #heat03:31
*** gokrokve has joined #heat03:34
*** rcleere has joined #heat03:35
*** gokrokve has quit IRC03:37
*** gokrokve has joined #heat03:40
*** rongze has joined #heat03:40
*** slong has quit IRC03:44
openstackgerritMitsuru Kanabuchi proposed a change to openstack/heat: Implements resource types NetworkGateway  https://review.openstack.org/6228703:48
openstackgerritAngus Salkeld proposed a change to openstack/heat: Fix stack_lock migration  https://review.openstack.org/6253403:58
*** gokrokve has quit IRC03:58
asalkeldlifeless, ^03:58
asalkeldnot heavily tested, but seems to handle "heat-manage db_sync 3{0,1}"03:59
asalkeldand passes tests03:59
*** gokrokve has joined #heat04:00
asalkeldlifeless, the "unique=True" is doing what I guess jasond` wanted with the primary key04:02
*** gokrokve has quit IRC04:04
*** gokrokve has joined #heat04:05
lifelessasalkeld: on mysql ?04:05
asalkeldI have a devstack04:06
asalkeldmmm, fedora so that new thingy04:06
asalkeldthe thing that was mysql04:06
openstackgerrithuangtianhua proposed a change to openstack/heat: Fix docstring on heat  https://review.openstack.org/6253604:07
asalkeldlifeless, mariadb04:07
asalkeldis that close enough04:07
*** gokrokve_ has joined #heat04:08
*** gokrokve has quit IRC04:09
*** gokrokve_ has quit IRC04:09
*** gokrokve has joined #heat04:11
*** chandankumar has joined #heat04:16
*** swygue has quit IRC04:17
*** aignatov has quit IRC04:19
lifelessasalkeld: I reckon04:30
*** rongze has quit IRC04:33
*** gokrokve has quit IRC04:37
*** gokrokve has joined #heat04:37
*** SushilKM has quit IRC04:38
*** gokrokve has quit IRC04:41
*** arbylee has quit IRC04:43
*** SergeyLukjanov has joined #heat04:49
*** rongze has joined #heat04:55
*** rongze_ has joined #heat04:59
*** rongze has quit IRC05:00
*** rushiagr has quit IRC05:04
*** rongze_ has quit IRC05:04
*** ccs has joined #heat05:10
*** gokrokve has joined #heat05:20
*** guohliu has joined #heat05:23
*** spzala_ has quit IRC05:32
*** sgordon has quit IRC05:33
*** akuznetsov has quit IRC05:51
*** ccs has quit IRC05:52
*** sgordon has joined #heat05:52
*** nkhare has joined #heat05:53
*** ccs has joined #heat05:54
*** erkules_ has quit IRC05:56
*** gokrokve has quit IRC05:56
*** gokrokve has joined #heat05:56
*** rushiagr has joined #heat05:58
*** erkules_ has joined #heat05:59
*** SushilKM has joined #heat06:00
*** ccs has quit IRC06:00
*** gokrokve has quit IRC06:01
*** erkules_ is now known as erkules06:04
*** SushilKM__ has joined #heat06:04
*** SushilKM has quit IRC06:04
*** gondoi has quit IRC06:06
openstackgerritJenkins proposed a change to openstack/heat: Imported Translations from Transifex  https://review.openstack.org/6255106:06
*** gondoi has joined #heat06:09
*** gokrokve has joined #heat06:13
*** SushilKM__ has quit IRC06:14
*** SushilKM has joined #heat06:14
*** rongze has joined #heat06:15
*** sgordon has quit IRC06:17
*** nkhare has quit IRC06:26
*** nkhare has joined #heat06:27
*** nkhare has quit IRC06:27
*** nkhare has joined #heat06:27
*** gokrokve has quit IRC06:29
*** akuznetsov has joined #heat06:34
*** rushiagr has quit IRC06:36
*** sgordon has joined #heat06:36
*** SushilKM has quit IRC06:40
*** amritanshu_RnD has joined #heat06:41
*** andersonvom has quit IRC06:43
*** harlowja is now known as harlowja_away06:43
*** SushilKM has joined #heat06:43
*** rushiagr has joined #heat06:43
*** SergeyLukjanov has quit IRC06:45
*** vkozhukalov has quit IRC06:51
*** yogesh has joined #heat06:59
*** sgordon has quit IRC07:01
*** plomakin_ has quit IRC07:01
*** yogesh has quit IRC07:08
*** yogesh has joined #heat07:08
*** rushiagr has quit IRC07:11
*** rushiagr has joined #heat07:11
*** yogesh has quit IRC07:12
openstackgerritA change was merged to openstack/heat: Convert OSDBInstance to new Schema format  https://review.openstack.org/6182507:14
openstackgerritA change was merged to openstack/python-heatclient: Supports bash_completion for heatclient  https://review.openstack.org/6214407:14
*** yogesh has joined #heat07:21
shardymorning07:22
skraynevmorning07:22
*** dmakogon_ has quit IRC07:23
*** dmakogon_ has joined #heat07:24
*** yogesh_ has joined #heat07:29
*** yogesh has quit IRC07:33
*** urulama has joined #heat07:33
*** gokrokve has joined #heat07:40
*** andersonvom has joined #heat07:43
*** lsmola_ has joined #heat07:44
*** gokrokve has quit IRC07:44
*** bgorski has joined #heat07:47
*** scollier has quit IRC07:50
*** andersonvom has quit IRC07:51
*** akuznetsov has quit IRC07:56
*** TonyBurn has joined #heat07:58
chmouelhello07:59
*** scollier has joined #heat08:01
*** alexheneveld has quit IRC08:03
openstackgerritA change was merged to openstack/heat: WaitCondition Count property is now updatable  https://review.openstack.org/6121808:06
Alienyygmorning guys08:09
*** sergmelikyan has joined #heat08:21
*** pfreund has joined #heat08:25
*** vkozhukalov has joined #heat08:26
*** aignatov has joined #heat08:33
*** giulivo has joined #heat08:37
*** rushiagr has quit IRC08:38
*** rushiagr2 has joined #heat08:38
*** ifarkas has joined #heat08:40
*** rushiagr2 has quit IRC08:44
skraynevshardy: If I have a some bug in havana release, that has fixed in master, may I do *backport*?08:46
*** urulama has quit IRC08:47
shardyskraynev: which bug?08:47
skraynevhttps://bugs.launchpad.net/heat/+bug/124763808:47
uvirtbotLaunchpad bug 1247638 in heat "Heat Load Neutron Balancer not using reference" [Undecided,Fix released]08:47
*** rushiagr2 has joined #heat08:49
shardyskraynev: I've tagged the bug havana-backport potential, which will flag it as a candidate for the next stable release08:50
shardyskraynev: You can, if you wish, propose the backported fix yourself:08:50
shardyhttps://wiki.openstack.org/wiki/StableBranch#Proposing_Fixes08:50
shardyNormally we just tag bugs with havana-backport potential though, and pull all the backports together close to the release (the PTL normally does this)08:51
shardyhavana-backport-potential even08:51
*** asalkeld has quit IRC08:51
shardyskraynev: Unfortunately you're a few hours too late for 2013.2.108:52
skraynevshardy: Yep unfortunately(((08:52
*** asalkeld has joined #heat08:53
skraynevshardy: Also If you have tagged it, I think, that will be better give this contribution to PTL, IMO.08:54
openstackgerritLiang Chen proposed a change to openstack/heat: Enalbe parallel while deleting neutron resources  https://review.openstack.org/6258008:54
*** urulama has joined #heat08:54
openstackgerritanusha rayani proposed a change to openstack/python-heatclient: Misc typos in celiometer client  https://review.openstack.org/6258208:57
*** rushiagr2 is now known as rushiagr09:00
skraynevshardy: Also I wanted ask about changing bug status: AFAIK if commit message include bug id reference - status will be changed automatically. is it right? anyway, if fix was merged and status are still Triaged, Who could change status (I mean correct way, not who has right)09:06
skraynevshardy: this bug : https://bugs.launchpad.net/heat/+bug/125571309:06
uvirtbotLaunchpad bug 1255713 in heat "Calling heatclient from heat doesn't work in standalone mode" [Medium,Triaged]09:07
*** nosnos has quit IRC09:07
*** nosnos has joined #heat09:07
*** derekh has joined #heat09:07
*** SergeyLukjanov has joined #heat09:08
*** SergeyLukjanov has quit IRC09:09
shardyskraynev: The patch referenced in that bug is not the fix, but a related patch09:09
*** SergeyLukjanov has joined #heat09:09
shardyskraynev: So AFAICS the status is correct09:09
skraynevshardy: Oou. Sorry, it's my fault. I didn't know about it.09:11
skraynevshardy: thanks for the help.09:11
*** akuznetsov has joined #heat09:13
*** tomek_adamczewsk has joined #heat09:14
*** vkozhukalov has quit IRC09:35
*** faramir1 has quit IRC09:46
*** andersonvom has joined #heat09:48
lifelessasalkeld: stevebaker: want to know something super weird - the trunk migration works... if you have no data in the system09:49
lifeless2013-12-17 09:38:42.519 3671 INFO migrate.versioning.api [-] 30 -> 31...09:49
lifeless2013-12-17 09:38:42.611 3671 INFO migrate.versioning.api [-] done09:49
lifelessfrom a deployment09:49
lifelessso I think we need something similar to what nova has now, active tests on real db's09:49
lifelessSpamapS: ^09:50
*** vkozhukalov has joined #heat09:50
*** andersonvom has quit IRC09:52
*** nati_ueno has quit IRC09:53
*** nati_ueno has joined #heat09:55
*** SergeyLukjanov has quit IRC09:55
shardylifeless: +1 on migration testing, I hit a weird issue recently ref bug #124182609:56
uvirtbotLaunchpad bug 1241826 in heat "bin/heat-manage db_sync doesn't create db" [Medium,Fix released] https://launchpad.net/bugs/124182609:56
shardywould be great to catch these problems in the gate09:57
*** SergeyLukjanov has joined #heat09:57
shardyzigo: Hi09:57
thervelifeless, It's unfortunate, as we reverted the patch previously because of the same reason afaiu :/09:59
skraynevlifeless: Do you mean walk version db tests?09:59
*** nanjj has quit IRC10:00
shardytherve: gah.  Just reading the backscroll :(10:02
*** faramir1 has joined #heat10:04
lifelessskraynev: I mean having real data to test against10:05
lifelessskraynev: since migrations can fail depending on the data they migrate10:05
skraynevlifeless: Gotcha, thanks10:07
*** rushiagr has quit IRC10:13
*** rushiagr has joined #heat10:14
*** rcleere has quit IRC10:15
*** rcleere has joined #heat10:15
sergmelikyanshardy, Hi! if you got a moment, could you take a look at this change? https://review.openstack.org/6107410:18
*** rushiagr has quit IRC10:25
*** rushiagr has joined #heat10:33
*** vaibhav has joined #heat10:33
*** tomek_adamczewsk has quit IRC10:34
*** aignatov has quit IRC10:34
*** tomek_adamczewsk has joined #heat10:35
*** rushiagr2 has joined #heat10:39
*** vkozhukalov has quit IRC10:40
*** rushiagr has quit IRC10:40
*** vkozhukalov has joined #heat10:52
*** yogesh_ has quit IRC11:01
*** blak111 has quit IRC11:01
*** blak111 has joined #heat11:01
*** SergeyLukjanov has quit IRC11:01
*** liang has quit IRC11:02
*** yogesh has joined #heat11:03
*** rushiagr2 has quit IRC11:05
*** rushiagr3 has joined #heat11:05
*** guohliu has quit IRC11:05
*** aignatov has joined #heat11:07
*** dmakogon_ is now known as denis_makogon11:09
*** nati_ueno has quit IRC11:10
*** nati_ueno has joined #heat11:11
*** nati_uen_ has joined #heat11:12
*** rushiagr3 is now known as rushiagr11:14
*** nati_ueno has quit IRC11:15
*** rongze has quit IRC11:19
*** Alienyyg has quit IRC11:25
*** SergeyLukjanov has joined #heat11:26
*** SergeyLukjanov has quit IRC11:34
*** SergeyLukjanov has joined #heat11:37
*** akuznetsov has quit IRC11:43
*** rongze has joined #heat11:44
*** rongze_ has joined #heat11:45
*** zaneb has quit IRC11:49
*** rongze has quit IRC11:49
*** nkhare has quit IRC11:51
*** chandankumar has quit IRC11:53
*** chandankumar has joined #heat11:53
*** zaneb has joined #heat12:02
*** rongze_ has quit IRC12:03
*** akuznetsov has joined #heat12:04
*** shakayumi has joined #heat12:06
*** aignatov has quit IRC12:07
*** rushiagr2 has joined #heat12:08
*** rushiagr has quit IRC12:09
*** rushiagr3 has joined #heat12:11
*** rushiagr2 has quit IRC12:13
*** akuznetsov has quit IRC12:15
*** akuznetsov has joined #heat12:15
openstackgerritanusha rayani proposed a change to openstack/python-heatclient: Misc typos in celiometer client  https://review.openstack.org/6258212:21
*** akuznetsov has quit IRC12:25
*** faramir1 has quit IRC12:28
*** scollier has quit IRC12:29
*** scollier has joined #heat12:29
*** Alienyyg has joined #heat12:31
*** rongze has joined #heat12:34
*** vaibhav has quit IRC12:37
openstackgerritanusha rayani proposed a change to openstack/python-heatclient: Misc typos in Heat client  https://review.openstack.org/6258212:42
*** rongze has quit IRC12:42
*** nosnos has quit IRC12:51
*** Alienyyg has quit IRC12:54
*** akuznetsov has joined #heat12:55
*** SergeyLukjanov has quit IRC12:56
*** SergeyLukjanov has joined #heat12:58
skraynevshardy: I think, that many people simplify afraid to do commit without bug or bp. They may be think, that without any 'important' reference it will not be merged.13:06
*** rushiagr3 has quit IRC13:06
*** nati_uen_ has quit IRC13:06
shardyskraynev: Why do you think that is, have we communicated that message somewhere?13:07
shardyskraynev: IMO bugs should be about actual problems, not cosmetic cleanups or refactoring13:08
skraynevshardy: I mean review https://review.openstack.org/#/c/62582/13:08
shardyskraynev: Yeah, where I'm saying a bug is not really needed, but it's not a big issue ;)13:09
*** shakayumi has quit IRC13:10
*** shakayumi has joined #heat13:11
skraynevshardy: yep) I agree with you. I only wanted give some explanation: why people do it )13:12
shardyskraynev: I didn't really understand the explanation tbh13:13
skraynevskraynev: hah)) Let's try again: People create many simple bugs, because they think, that it's only way for getting approve on it change. that is all))13:15
*** shakayumi has quit IRC13:15
shardyskraynev: Ok, cool - well FWIW I think people should raise bugs for actual problems, blueprints for features/enhancements, and just send the patch for trivial/cosmetic stuff :)13:16
*** rpothier__ has quit IRC13:17
*** rongze has joined #heat13:18
skraynevshardy: Yeap) Good approach ;)13:20
*** urulama has quit IRC13:20
*** aignatov has joined #heat13:22
* skraynev Imagine how beginning developer make "difficult" decision: it is actual problem or trivial stuff? ))) To be or not to be? )))) heh))13:23
*** rongze_ has joined #heat13:39
*** andersonvom has joined #heat13:41
*** TonyBurn has quit IRC13:43
*** rongze has quit IRC13:43
openstackgerritBartosz GĂłrski proposed a change to openstack/heat: Add an external gateway property to neutron router  https://review.openstack.org/6011813:44
*** rongze_ has quit IRC13:48
*** rongze has joined #heat13:48
*** rongze_ has joined #heat13:49
openstackgerritSteven Hardy proposed a change to openstack/heat: Add initial support for instance_auth_method  https://review.openstack.org/6243913:53
openstackgerritSteven Hardy proposed a change to openstack/heat: SignalResponder store access/secret in resource data  https://review.openstack.org/6244013:53
openstackgerritSteven Hardy proposed a change to openstack/heat: heat_keystoneclient revise get_ec2_keypair  https://review.openstack.org/6244113:53
*** rongze has quit IRC13:53
*** shakayumi has joined #heat13:54
*** andersonvom has quit IRC13:55
*** pfreund has quit IRC13:56
*** lsmola_ has quit IRC13:56
*** stannie has quit IRC13:58
*** lsmola_ has joined #heat14:10
*** pfreund has joined #heat14:11
openstackgerritA change was merged to openstack/python-heatclient: Misc typos in Heat client  https://review.openstack.org/6258214:12
openstackgerritA change was merged to openstack/heat: Add OS::Neutron::RouterL3Agent for router.py  https://review.openstack.org/6138814:12
*** rpothier__ has joined #heat14:12
*** aweiteka has joined #heat14:15
*** stannie has joined #heat14:18
openstackgerritLiang Chen proposed a change to openstack/heat: Enable parallel while deleting neutron resources  https://review.openstack.org/6258014:20
*** radez_g0n3 is now known as radez14:26
*** denis_makogon has quit IRC14:29
*** shakayumi has quit IRC14:31
*** andersonvom has joined #heat14:32
*** aignatov has quit IRC14:33
*** vaibhav has joined #heat14:33
*** denis_makogon has joined #heat14:33
vaibhavtims: hi14:34
*** aignatov has joined #heat14:34
*** rpothier__ is now known as rpothier14:35
openstackgerritPablo Andres Fuente proposed a change to openstack/heat: wsgi.Resource exception handling to not log errors  https://review.openstack.org/6208014:35
*** vaibhav has quit IRC14:36
*** jcru has joined #heat14:38
*** rushiagr3 has joined #heat14:41
*** john-n-seattle1 has joined #heat14:44
*** topol has joined #heat14:50
sdakemorning14:50
shardyHi sdake14:50
sdakehey shards14:51
sdakehey look ohloh is improved to include openstack14:52
sdakehttp://www.ohloh.net/accounts/stevendake?utm_campaign=update13&utm_medium=email&utm_source=optin14:52
sdake7057 lifetime commits14:53
sdakeI've been busy apparently14:53
sdakethe last graph is trippy14:54
sergmelikyanGuys, which one is correct property name for instance in Nova terms? server_id or instance_id?14:56
* sergmelikyan try to found some already existing usages14:56
openstackgerritJulia Varlamova proposed a change to openstack/heat: Filter resource types by support status  https://review.openstack.org/5556714:57
therveFor nova, server_id14:57
*** gokrokve has joined #heat14:58
shardyYou can't control that via the Server resource properties though, if that is the question?14:58
sergmelikyanshardy, I am working on https://blueprints.launchpad.net/heat/+spec/nova-networking-floatingip and apparantly need replacement term for AWS InstanceId property name14:59
*** chandankumar has quit IRC14:59
*** Andrzej has joined #heat15:01
*** arbylee has joined #heat15:01
*** gokrokve has quit IRC15:01
*** gokrokve has joined #heat15:01
shardyAh, yeah server_id then15:02
*** SushilKM has quit IRC15:02
*** vijendar has joined #heat15:03
sdakesteve hardy do you have an account on ohloh?15:03
shardysdake: Yeah, it's shardy15:04
*** denis_makogon has quit IRC15:05
*** denis_makogon has joined #heat15:05
openstackgerritThomas Herve proposed a change to openstack/heat: Add new Ceilometer combination alarm resource  https://review.openstack.org/6267215:05
sdakehttps://www.ohloh.net/accounts/shardy15:05
sdakeshardy didn't exist before Jan 201215:06
shardyyup, that's me ;)15:06
sdakecrazy you weren't in dev all along15:06
shardysdake: I was doing mostly proprietary stuff for many years, unfortunately ;)15:06
sdakeya hard to show up in an onlin etracking tool with that sort of work15:07
sdakei did some proprietary work right out of school15:07
sdake@ INTC15:08
sdake3 years later, off to open source land15:08
*** rushiagr3 is now known as rushiagr15:11
sdakemy bitcoin miner put 800$ USD in my checking account this morning15:12
sdake\o/15:12
*** swygue has joined #heat15:13
*** amritanshu_RnD has quit IRC15:15
*** tims has quit IRC15:16
jasond`shardy: do you understand the problem that https://review.openstack.org/#/c/62534/ fixes?15:16
shardyjasond`: I believe so, but I've not tested the fix myself15:18
jasond`shardy: i don't understand it.  why did the migration fail for lifeless?15:18
jasond`i can't reproduce it15:19
shardyjasond`: It's the same/similar issue to why we had to revert your previous patch, where setting the defaults doesn't work if you're using the InnoDB engine15:19
shardyjasond`: What DB are you using?15:20
jasond`mysql15:20
openstackgerritSteven Dake proposed a change to openstack/heat-templates: OS::Metering::Alarm -> OS::Ceilometer::Alarm  https://review.openstack.org/6267715:20
*** urulama has joined #heat15:21
sdakeso..  mariadb vs mysql15:21
sdakewhich has more unicorns15:21
shardysdake: No, I think the issue is lifeless is using InnoDB not MyISAM on mysql15:22
*** pfreund has quit IRC15:22
jasond`shardy: i'm using innodb15:22
sdakewhat does fedora devstack use?15:22
jasond`i wonder if the mysql_ options in the migrate script work on mariadb15:23
shardyjasond`: hmm, in that case I'm not sure, hopefully lifeless and/or asalkeld can provide more info15:23
jasond`shardy: i'll ask asalkeld or lifeless when they get in.  thanks15:24
*** john-n-seattle1 has quit IRC15:24
shardyjasond`: You've had a rough time with this patch huh, thanks for sticking with it! :)15:25
*** urulama has quit IRC15:25
jasond`thank YOU all for sticking with it :)15:25
jasond`i was just waiting for someone to fire me from multi-engine15:26
*** spzala has joined #heat15:27
shardyjasond`: I don't think anyone else wanted that particular hot-potato ;)15:27
sdakejasond you are stuck with it now :)15:28
jasond`:)15:28
*** IlyaE has joined #heat15:29
sdakedo you need special permissions to set a relationship in a blueprint?15:39
shardysdake: I don't think so, you just add a dependency15:39
sdakewhats the button called?15:39
sdake(where is it)15:40
shardy"Add dependency", at the bottom, green "+"15:40
sdakethanks I'll look for that15:40
sdakeshardy have you written any blueprints for heat so far?15:40
shardysdake: quite a few, yes15:41
*** brint has joined #heat15:41
sdakecool - the blueprints or the code?15:41
sdaketoday I was going to try to link them all together15:41
shardysdake: Well both, normally before I start working on a feature, I'll at least dump some minimal info in a BP then start hacking on a topic branch15:42
shardyI should probably do detailed wiki descriptions too really, considering I keep asking new contributiors for them ;)15:42
sdakedetailed wiki seems overkill unless upstream requires it15:43
sdakeask forgiveness imo :)15:43
*** jergerber has joined #heat15:45
*** alcabrera has joined #heat15:46
*** alcabrera has left #heat15:46
Andrzejhi, i work in xlcloud and we use nested stacks for heat. but we are considering switching to providers and creating custom resource types.15:46
Andrzejdoes anyone know, is it possible to inject some information to resource template in different way than properties?15:46
Andrzejcan it be done with use of environments?15:46
Andrzejwe want to set some parameters of resource from environment, but not clutter stack template with properties15:47
*** SergeyLukjanov has quit IRC15:48
AndrzejI found some example of environment in documentation that I don't understand: https://wiki.openstack.org/wiki/Heat/Environments15:48
sdakehow do I get a test coverage report in tox?15:49
Andrzejis it valid? i thought environment can only have fields 'parameters' and 'resource_registry'15:49
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Remove X-Auth-Url header from authtoken middleware  https://review.openstack.org/6099115:49
*** vkozhukalov has quit IRC15:51
*** denis_makogon has quit IRC15:56
*** denis_makogon has joined #heat15:56
sdakeare the unit test results online somewhere?15:56
sdakewith coverage reports?15:56
therveWell the results are posted by jenkins16:00
therveBut I don't think we have coverage tracking16:01
sdakeI am pretty sure I have added that alteast twice to the infra :)16:01
*** radez is now known as radez_g0n316:02
therveYou should know where it is then :)16:02
*** bnemec_ is now known as bnemec16:02
*** yogesh has quit IRC16:02
*** aignatov has quit IRC16:03
shardysdake: I normall do run_tests.sh -c16:04
shardynormally16:04
shardyAndrzej: If I'm understanding correctly, you can do what you want with the environment16:05
shardyAndrzej: You specify parameters in the provider templates, then you can specify values for the parameters in the environment file you pass when creating the stack16:06
shardyAndrzej: Here is a really simple worked example:16:06
shardyhttp://hardysteven.blogspot.co.uk/2013/10/heat-providersenvironments-101-ive.html16:06
shardyAndrzej: Probably the key thing to mention is that the provider resource properties get converted into parameters for the nested stack16:08
shardye.g key_name in the blog example16:09
Andrzejshardy: thanks. in such I case I need to add property in resource for every parameter I want to use in nested stack, yes?16:11
Andrzejshardy: perfect for me would be, if I could leave properties section empty in resource, and use environment parameters in nested stack16:12
Andrzejshardy: stack template will be presented to the user and we hoped to hide some configuration parameters of nested stack16:13
*** akuznetsov has quit IRC16:13
*** tims has joined #heat16:14
Andrzejshardy: but if I understand correctly it is not possible, right?16:16
*** randallburt has joined #heat16:18
sdakehttps://blueprints.launchpad.net/tempest/+spec/tempest-heat-integration16:18
sdakerun_tests.sh is giving me mock_open errors16:18
sdakethere must be something non-standard about your enviornment shardy16:18
sdakebut it runs with with_venv.sh16:19
sdakeso I used that16:19
shardysdake: s/non-standard/non-broken ;)16:19
therveSomeone has any idea about http://logs.openstack.org/52/62252/1/gate/gate-heat-python27/74fd9de/console.html ?16:19
shardysdake: I guess maybe you're missing some of the test-requirements?16:20
openstackgerritJason Dunsmore proposed a change to openstack/heat: Prevent tempest from failing upon ActionInProgress  https://review.openstack.org/6270316:20
therveAppearing on https://review.openstack.org/#/c/62252/16:20
shardyAndrzej: I'm just checking16:20
shardytherve: There have been issues with MetadataRefreshTest on stable/grizzly for a long time16:21
shardytherve: I backported what I thought was the fix, but apparently not :(16:21
*** SushilKM has joined #heat16:21
therveOh grizzly16:21
therveThat may be why16:21
shardyI thought https://review.openstack.org/#/c/44029/ would fix it16:22
shardyevidently not16:23
*** ifarkas has quit IRC16:25
*** SushilKM has quit IRC16:30
*** jamieh_ has joined #heat16:32
shardyAndrzej: You're right, you currently can't specify nested stack parameters in the environment16:33
shardyAndrzej: It seems like something we may want to allow though, can you raise a bug and we'll take a look at fixing it?16:34
*** alcabrera has joined #heat16:36
*** jamieh_ has quit IRC16:36
*** rcleere has quit IRC16:37
*** alcabrera has left #heat16:37
*** SushilKM has joined #heat16:38
*** sjmc has joined #heat16:47
*** john-n-seattle1 has joined #heat16:50
*** rongze_ has quit IRC16:53
*** rongze has joined #heat16:53
*** SergeyLukjanov has joined #heat16:54
*** john-n-seattle1 has quit IRC16:55
*** vijendar has quit IRC16:56
openstackgerritJason Dunsmore proposed a change to openstack/heat: Prevent tempest from failing upon ActionInProgress  https://review.openstack.org/6270316:56
*** vijendar has joined #heat16:56
*** tomek_adamczewsk has quit IRC16:58
*** rcleere has joined #heat16:59
*** john-n-seattle1 has joined #heat17:10
*** pablosan has joined #heat17:11
timsstevebaker and anyone who would like to chime in on the parameter labels discussion17:13
timsI have posted the discussion on the UX askbot17:13
timshttp://ask-openstackux.rhcloud.com/question/119/should-heat-pass-parameter-labels-to-horizon/17:13
*** AndrewMichalik has quit IRC17:14
*** pablosan has quit IRC17:15
*** john-n-seattle1 has left #heat17:16
*** pablosan has joined #heat17:18
thervetims, Why isn't description good enough for this?17:19
timstherve you mean, we should use the description as the parameter label?17:20
thervetims, Yeah17:20
therveMost of the time it would be great, maybe a bit long sometimes17:20
timsthe label should be 2 or 3 words17:21
timswe have to worry about spacing and positioning in html17:21
timsthe description should be sentences17:21
*** urulama has joined #heat17:22
jasond`therve: the label would be in the html form next to an input box17:23
therveMaybe. They don't seem to be in practice17:23
jasond`so it would say "Database Name: ________" instead of "db_name: _______"17:23
timscorrect thanks jasond`17:23
therveOkay17:23
timsIf you look at the Horizon implementation currently the description lives in a box to the right of the form17:23
therveAdding a label feels weird, but maybe that's just me17:25
timsI was surprised by how many people had the same reaction, I would love to understand why it is weird17:26
*** urulama has quit IRC17:26
timsHorizon has some regex stuff that it does on some things to make variable names more human readable17:27
timslike replace underscore with space17:27
timsand capitalize beginnings of words17:27
thervetims, Template editing should be easier, not the other way around17:27
therveIt's just something in the way17:28
therveI guess it was the same arguments with metadata17:28
timsbut letting the template author be explicit about how the template will behave in the UI is valuable I think17:28
timsand it is optional17:28
timsif it isn't provided it will default to the keyname17:28
timswell metadata was the opposite argument actually17:29
timsmetadata was let's just throw things in here and not worry about it17:29
therveOkay :)17:29
timsI am very much for easy template editing17:30
thervetims, What about standarzing a format in the description?17:30
timsI don't see how that is less complex17:30
timsand the current debate is more about what to display in Horizon than how to implement in the template17:30
timsso you are ok with displaying a human-readable label in horizon?17:31
therveIE description= label: explanatory tewt17:31
thervetext17:31
therveIt's backward compatible, it's fairly easy to do, and it makes templates look nice17:31
*** randallburt has quit IRC17:31
timsit isn't self-explanatory17:31
therveWell sure, there is not much point to be against that17:31
jasond`wouldn't an older version of heat just ignore the label?17:31
timswell that is the current debate :)17:31
timsyes17:31
timsjasond`:17:32
timsI even wrote the code17:32
therveNow the debate is where to put the information, AFAIU17:32
therves/Now/No17:32
timshttps://review.openstack.org/#/c/62418/217:32
jasond`so backward compatibility isn't a consideration17:33
timsit is17:33
timsif the label doesn't exist Heat will insert the parameter key into the label field17:33
thervetims, What happens when you pass a template with a label to an old Heat install?17:33
jasond`tims: why doesn't the UI handle that17:34
timswell currently Heat just ignores things in the template that it doesn't care about17:34
timstherve ^17:34
timsso it would just store it as part of the template and ignore it17:34
therveOkay17:34
therveThat's good I guess17:34
timsjasond`: the UI should handle what?17:34
jasond`tims: falling back on the param name if label isn't present17:35
timsit could17:35
timsbased on my conversation with Zane though, Heat should start caring about compatibility issues17:36
timsinstead of letting downstream services handle it17:36
jasond`i dunno, the UI is rendering the template into an HTML form.  seems like that logic belongs in the UI17:37
jasond`anyway, that's another topic17:37
timsunless Heat wants to be opinionated about what should happen17:37
timswhich from what I have gathered it does17:37
timsmy original patch actually follows that train of thought jasond`17:39
*** rongze has quit IRC17:39
*** rongze has joined #heat17:40
*** swygue has quit IRC17:43
*** vkozhukalov has joined #heat17:44
openstackgerritKevin Benton proposed a change to openstack/heat: Adds extraroutes support to neutron routers  https://review.openstack.org/4104417:46
larsksIs the name of the stack being deployed available explicitly within the template via some function?17:48
*** AndrewMichalik has joined #heat17:48
thervelarsks: Yes, AWS::StackName IIRC17:49
openstackgerritKevin Benton proposed a change to openstack/heat: Adds extraroutes support to neutron routers  https://review.openstack.org/4104417:50
*** radix_ has joined #heat17:53
*** rongze has quit IRC17:53
*** rongze has joined #heat17:54
*** nati_ueno has joined #heat17:56
*** derekh has quit IRC17:58
*** randallburt has joined #heat18:01
*** sabeen has joined #heat18:02
*** nati_uen_ has joined #heat18:02
larskstherve: Thanks, I'll look into that.18:02
*** nati_uen_ has quit IRC18:04
*** nati_uen_ has joined #heat18:04
*** nati_uen_ has quit IRC18:05
*** nati_ueno has quit IRC18:05
*** nati_uen_ has joined #heat18:05
*** rongze has quit IRC18:18
*** harlowja_away is now known as harlowja18:22
*** yogesh has joined #heat18:25
openstackgerritStephen Sugden proposed a change to openstack/heat: Add PortCheck resource  https://review.openstack.org/6207818:25
*** blamar has quit IRC18:29
openstackgerritVijendar Komalla proposed a change to openstack/heat: Implement adopt-stack  https://review.openstack.org/6273018:30
*** vkozhukalov has quit IRC18:36
*** vkozhukalov has joined #heat18:37
*** ifarkas has joined #heat18:37
*** blamar has joined #heat18:39
openstackgerritKevin Benton proposed a change to openstack/heat: Adds extraroutes support to neutron routers  https://review.openstack.org/4104418:40
stevebakermorning18:47
*** pvaneck has joined #heat18:51
*** nati_ueno has joined #heat18:53
*** spzala has quit IRC18:56
*** nati_uen_ has quit IRC18:57
*** swygue has joined #heat18:58
*** SushilKM__ has joined #heat18:58
*** SushilKM has quit IRC18:58
*** rushiagr has quit IRC18:59
*** sabeen has quit IRC19:05
*** sabeen has joined #heat19:05
*** nati_ueno has quit IRC19:10
*** rongze has joined #heat19:13
*** nati_ueno has joined #heat19:13
*** rushiagr has joined #heat19:16
*** rongze has quit IRC19:18
*** gokrokve has quit IRC19:20
*** akuznetsov has joined #heat19:20
*** SnowDust has joined #heat19:22
*** akuznetsov has quit IRC19:22
*** urulama has joined #heat19:23
*** AndrewMichalik has quit IRC19:23
*** AndrewMichalik has joined #heat19:25
*** gamekiller77 has joined #heat19:25
gamekiller77Good day all i looking for a sample template i can play with to test my heat deployment any good links out there19:26
SnowDustanteaya still reading ur blog carefully .... "so all the teachers new me from the start."19:26
*** urulama has quit IRC19:27
*** harlowja is now known as harlowja_away19:30
openstackgerritZane Bitter proposed a change to openstack/heat: rackspace: Convert resources to new Schema format  https://review.openstack.org/6183419:31
SnowDustgamekiller77 : https://github.com/openstack/heat-templates19:32
SnowDustabsorb as much u can ...19:32
gamekiller77thanks SnowDust i just need to do a simple deployment to show it works to the bosses19:32
SnowDustdeploy a santa .. :)19:33
SnowDustthat works better in christmas time19:33
gamekiller77yah right19:33
gamekiller77i was hoping like a small mysql server or a simple URL test19:34
*** rushiagr has quit IRC19:36
gamekiller77love errors19:37
SnowDustgamekiller77: u will find one .. for your need .. look at cfn/f17 folder19:38
gamekiller77yah looking19:38
SnowDustgamekiller77: https://github.com/openstack/heat-templates/blob/master/cfn/F17/MySQL_Single_Instance.template19:40
gamekiller77thanks man19:40
gamekiller77i keep getting this19:40
gamekiller77An unknown problem occurred validating the template.19:40
SnowDustoops ..19:40
gamekiller77i doing direct input so going to try file next19:40
SnowDustheat <environment settings> template-validate --template-url <url>19:41
SnowDustheat <environment settings> template-validate --template-file <file path>19:41
gamekiller77ok that last one you gave me took19:42
gamekiller77hehe19:42
gamekiller77thanks man19:42
SnowDustuse .. heat --debug ( most essential switch to troubleshoot )19:42
gamekiller77yah i do that19:42
gamekiller77first time testing Heat19:42
gamekiller77just got my KVM nodes in line with volumes19:42
SnowDustno issues .. :-)19:42
gamekiller77so time to test this19:42
SnowDustgr819:42
stevebakertherve: was it you who started working on something like this https://blueprints.launchpad.net/heat/+spec/parameter-nested-schema19:43
thervestevebaker, Nope19:43
*** randallburt has quit IRC19:44
stevebakerasalkeld: ^ do you recall?19:45
gamekiller77SnowDust, i am bit of noob to heat but i need to have instances in place for them to work right with there name format they are listed in there template like F17 should be in place19:46
SnowDustnothing like that ..19:46
gamekiller77ok it failed hmm19:47
SnowDusttemplate = formatted file .. as per the template guide .. http://docs.openstack.org/developer/heat/template_guide/index.html19:47
SnowDustu can keep them in a github repo ..19:48
SnowDustclone them ..19:48
SnowDustand use them from the cloned repo path ..19:48
openstackgerritZane Bitter proposed a change to openstack/heat: Convert Server to new Schema format  https://review.openstack.org/6178619:48
SnowDustits as simple like that19:48
SnowDustu decide how ur repo gets organized19:48
thervestevebaker, I may have some time to take additional blueprint work, though, if that helps19:48
*** randallburt has joined #heat19:49
stevebakertherve: this one is autoscaling related https://blueprints.launchpad.net/heat/+spec/autoscaling-parameters19:49
gamekiller77yah sorry just learning as i got to teach my automation guys how to use this after i done validating this setup19:49
*** bgorski has quit IRC19:50
thervestevebaker, Hum I agree with radix on that one. I'm not sure what's the use case of the blueprint19:51
stevebakertherve: maybe reduce the scope of that blueprint to use case #219:52
*** randallburt has quit IRC19:52
*** IlyaE has quit IRC19:52
*** randallburt has joined #heat19:52
therveYeah. But it looks like it depends on a new autoscale resource19:52
stevebakertherve: and ignore scale-up for now19:52
stevebakermaybe I should kick that to i-3 and leave it unassigned19:53
therve+119:53
*** pafuent has joined #heat19:53
therveWe should also get some feedback from the creator19:54
SnowDustanteaya : best of ur blog is the git one .. gr8 work !19:54
stevebakertherve: have you been working on autoscaling?19:54
thervestevebaker, No19:55
therveWell, not recently19:55
therveIt's unclear if there is an agreement on any sort of design for it...19:56
stevebakeroh, I thought there was agreement and it was all go19:57
stevebakertherve, radix, maybe we should discuss at the heat meeting tomorrow19:58
*** SushilKM__ has quit IRC19:59
thervestevebaker, I can't attend the meetings :/19:59
*** SushilKM__ has joined #heat19:59
therveI was actually wondering if we could start alternating with 2 different times20:00
therveCeilometer does that and it's pretty nice20:00
*** ccs has joined #heat20:01
stevebakertherve: yes, we need to discuss alternative meeting times20:02
timshey stevebaker, I posted the link earlier but in case you missed the back scroll I want to make sure that I represented the discussion correctly20:02
timshttp://ask-openstackux.rhcloud.com/question/119/should-heat-pass-parameter-labels-to-horizon/20:02
stevebakertims: I'm just forming a reply now20:02
timsok thanks20:02
*** ifarkas has quit IRC20:05
*** ccs has quit IRC20:05
*** radez_g0n3 is now known as radez20:07
openstackgerritRichard Lee proposed a change to openstack/heat: Add way to group exceptions in DependencyTaskGroup  https://review.openstack.org/6247920:09
*** vkozhukalov has quit IRC20:11
zanebugh20:12
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Check resources are in expected states  https://review.openstack.org/5864120:13
zanebstevebaker: looks like we've managed to acquire two more badly-designed Neutron resources with magic hidden dependencies already since summit :(20:13
*** harlowja_away is now known as harlowja20:14
*** sgordon has joined #heat20:16
*** gokrokve has joined #heat20:18
*** brint has quit IRC20:19
gamekiller77hey guys do i need to enable the AWS api s on my openstack setup to have heat work ?20:19
*** denis_makogon has quit IRC20:19
randallburtgamekiller77:  nope, you can use the OpenStack "native" api20:19
*** sjmc has quit IRC20:19
*** brint has joined #heat20:19
gamekiller77ok just checking20:19
*** dmakogon_ has joined #heat20:19
*** mtaylor is now known as mordred20:20
gamekiller77i see a lot of AWS items in the template was just wondering20:21
zanebgamekiller77: heat supports a lot of AWS-like resources, but both AWS and native resource types call the OpenStack-native APIs20:22
SnowDustzaneb +120:22
zaneb(in many cases they're basically the same code)20:22
gamekiller77ok cool20:23
gamekiller77just jumping in to this so trying to understand.  I have a galara mysql i want to see if i can get in to orchestration with heat20:23
gamekiller77and use ceilo to have it scale out as needed20:23
*** IlyaE has joined #heat20:24
*** ccs has joined #heat20:27
*** ccs has quit IRC20:31
stevebakerzaneb: the Route had to satisfy the use case where a tenant is only allowed one router, but a stack needs to add a custom route20:32
stevebakerzaneb: I'm not sure what the other "badly designed" resource you're referring to, maybe we *both* missed the reviews for that one ;)20:34
zanebstevebaker: I'm looking at https://review.openstack.org/#/c/59626/8/heat/engine/resources/neutron/net.py and https://review.openstack.org/#/c/61388/3/heat/engine/resources/neutron/router.py20:34
zanebis there another one as well?20:34
zanebin both of those cases what should be just a property of the network/router has been elevated into a whole resource, with various hacks added to make things actually work right20:36
stevebakerzaneb: for Route that wouldn't have worked for the use case mentioned above. There is a particular neutron hardware plugin which has the restriction of only one (pre-existing) router per tenant20:39
zanebI don't see the connection?20:40
stevebakerzaneb: the router needs to be passed in as a parameter, because it already exists and is a singleton for the tenant20:41
SpamapSstevebaker: retry-failed-update is pretty important actually.. I just haven't been able to find time to work on it.20:41
SpamapSstevebaker: (noticing tha tyou deprioritized it)20:41
stevebakerSpamapS: cool, assign it to yourself and I'll raise the priority again20:42
SpamapSstevebaker: IMO we shouldn't drop priority without documenting the justification in the whiteboard.20:42
zanebstevebaker: if it's already set up then why isn't it assigned to an agent? (whatever that is)20:43
stevebakerSpamapS: I should have documented why. It was ttx's suggestion as a way of motivating assignees - it appears to have worked20:44
SpamapSstevebaker: haha20:44
openstackgerritPablo Andres Fuente proposed a change to openstack/heat: Deleting a stack with a deleted nested stack fails  https://review.openstack.org/6275220:44
SpamapSwhat will actually motivate me is having a CD cloud that I have to keep running over time. :)20:44
SpamapSwhich should be happening soon :)20:44
stevebakerzaneb: oooooooh. ignore everything I just said. I thought you were talking about this https://review.openstack.org/#/c/41044/20:45
*** rpothier has quit IRC20:46
zanebstevebaker: OH G*D20:47
sdake_someone needs to invent a mailbox filter that the US postal service can work with20:49
zanebstevebaker: that's just the wrong approach IMO. We should have a RouteTable resource, not individual Routes20:49
sgranthere should be both20:51
stevebakerzaneb: but if there is only one router per tenant, different stacks would need to contribute routes. With a RouteTable there would be the complexity of merging tables. At least with a single Route you know what to add and remove, and you can raise an error if there is a duplicate20:51
sgrana RouteTable contains a bunch of Routes20:51
zanebwell, we shouldn't be using dependencies within a stack to avoid race conditions20:52
zanebwe should write code without race conditions20:52
sdake_stevebaker what is your take on importing a salt server into the heat engine process address space20:52
zanebbecause if you have routes in multiple stacks contributing multiple routes, there's no dependencies there20:53
zanebso either fix the race conditions or don't do it, but don't just paper over the race conditions20:53
stevebakerI can't think of a complete solution which is heat-only. We could just say that we can't support adding routes to existing routers until neutron exposes an API for it20:56
stevebakerthen add a routes list property20:57
zanebthe neutron API is horrible, and we should actually be pushing back on them and letting them know that we can't actually use it safely20:57
zanebhalf the problem is that most of their core functionality is exposed as "extensions", so the API is completely balkanised20:58
*** SushilKM__ has quit IRC20:58
stevebakeri suppose that is partly a consequence of the heterogeneous networking hardware that it wraps20:59
sdake_stevebaker as of today, my bitcoin miner has officially ROIed, and is making 350-450$/day - should have 3 more months until its obsolete ;)20:59
stevebakersdake_: cool20:59
zaneb# depend on routes with greater addresses to order route installation21:00
zanebwtf? ^21:00
sdake_of course it drops output 20% every 2 weeks :(21:00
stevebakerzaneb: add your comments to the review21:02
zanebyeah, doing it now21:02
stevebakerzaneb: as for the agent stuff, I'd not looked at it until now.21:02
*** andrew_plunk has joined #heat21:03
stevebakerzaneb: they are admin-only - *possibly* that is justification for them being their own resources21:03
zanebstevebaker: ok, would be great if you could take a look. I'll probably post to the ML about it21:03
zanebtbh I can barely justify them existing at all if they are admin-only21:04
stevebakeradmins setting up their long-lived networking infrastructure with heat seems reasonable21:05
openstackgerritJason Dunsmore proposed a change to openstack/heat: Don't provide default values to properties.get()  https://review.openstack.org/6276021:06
*** topol has quit IRC21:06
*** dims has quit IRC21:08
*** pafuent has left #heat21:08
stevebakerzaneb: fwiw I did point out to Kevin how much you would dislike that solution, but I couldn't think of anything better ;)21:08
*** dims has joined #heat21:09
zanebstevebaker: better thing to do might be to fix the neutron api :)21:09
stevebakeryes, where race conditions belong!21:10
*** sgordon has quit IRC21:16
*** nati_ueno has quit IRC21:20
*** urulama has joined #heat21:24
*** tomek_adamczewsk has joined #heat21:24
openstackgerritRandall Burt proposed a change to openstack/heat: Add nested resource references to resource group  https://review.openstack.org/6161421:24
*** nati_ueno has joined #heat21:28
*** urulama has quit IRC21:28
*** sgordon has joined #heat21:29
*** AndrewMichalik has quit IRC21:30
*** 13WABKZ4U has joined #heat21:31
*** blomquisg has joined #heat21:36
*** 13WABKZ4U has quit IRC21:42
zanebstevebaker: there isn't even a race condition to deal with in the same stack, unless we have gone multi-threaded when I was not paying attention?21:43
*** SushilKM has joined #heat21:43
zanebstevebaker: those dependencies are just meaningless noise21:45
stevebakerzaneb: wouldn't a stack with multiple route resources end up with concurrent router-fetch/update calls?21:48
zanebstevebaker: nothing within a single stack or a tree of nested stacks is ever concurrent21:49
zanebever.21:49
zanebif you started it in handle_create and finished in check_create_complete then yes, you could get a race21:49
zanebbut don't do that21:49
stevebakerso what happens when a router get triggers IO which causes eventlet to schedule something else? could the creation of another unrelated resource  be started?21:50
zanebyes, but only a resource in a different stack resulting from a different user request21:51
zanebi.e. something outside of the local tree of nested stacks21:51
stevebakerah, ok. that makes things simpler21:52
zanebwhich is a problem, but not one that dependencies can solve21:52
stevebakeryes21:52
stevebakercould there be some reviews on this fix for gate race breakage? https://review.openstack.org/#/c/62703/21:53
*** tomek_adamczewsk has quit IRC21:54
*** tomek_adamczewsk has joined #heat21:55
lifelessI'm going to come back to pointing at idempotent handlers21:55
lifelesslet the race happen, clean up afterwards21:55
*** SushilKM has quit IRC21:56
*** Seal has joined #heat21:57
zaneblifeless: so the issue is that we want to add a route to the route table, and the only way is to read the route table, add a route and then write the whole route table again21:57
*** tomek_adamczewsk has quit IRC21:57
lifelessfor a router?21:57
zanebyes21:57
*** tomek_adamczewsk has joined #heat21:57
lifelessok, so two different stacks can race with each other21:57
lifelessplus end users.21:57
stevebakercorrect21:57
lifelessits a broken API in neutron21:58
stevebakerfor end users, that is the same for any resource21:58
lifelessany attempt to fix it in Heat is going to be incomplete.21:58
zanebso a good way would be to return an ETag header with the route table, then PUT with the If-Match header set to the ETag value. Neutron should return 412 if the route table has changed21:59
lifelessare you asserting the presence of a specific route, or the content of the whole table - in the template?21:59
stevebakera single route21:59
lifelessso, a user should be able to add a different route21:59
lifelessand not have it trashed21:59
lifeless-> can't solve in Heat.21:59
zanebyes21:59
zanebyes21:59
stevebakerunless it is concurrent21:59
lifelessquod erat demonstratum :)21:59
lifelessstevebaker: Neutron needs to allow a PATCH there to add a route rather than wholesale replacement22:00
*** tomek_adamczewsk has quit IRC22:00
*** randallburt has quit IRC22:00
*** tomek_adamczewsk has joined #heat22:00
*** tims1 has joined #heat22:00
zaneblifeless: yes, or alternatively it could do what I wrote above (which requires no API changes at least)22:00
stevebakerso should we allow a route resource in the meantime?22:00
*** SnowDust has quit IRC22:00
lifelesszaneb: sure, that would be safer (if everything doing edits used I-M)22:01
*** nati_uen_ has joined #heat22:01
*** andrew_plunk has quit IRC22:01
zanebstevebaker: IMO no. We should either fix the API or model the broken API, but not model a working API that is actually broken22:01
*** tims has quit IRC22:02
*** tomek_adamczewsk has quit IRC22:02
*** tomek_adamczewsk has joined #heat22:02
stevebakerzaneb: so you're suggesting optimistic concurrency on router updates?22:02
*** nati_uen_ has quit IRC22:03
zanebstevebaker: did you see my comment on https://review.openstack.org/#/c/41044/ ?22:03
*** nati_ueno has quit IRC22:03
*** nati_uen_ has joined #heat22:03
*** Seal has quit IRC22:03
stevebakerzaneb: read it22:05
zanebdid that answer the question?22:05
zanebI would describe the ETag/If-Match solution as optimistic concurrency. I think what lifeless described would be better. But if what we're being told about the Neutron API is accurate, then it is broken and needs to be fixed.22:07
*** aignatov has joined #heat22:08
andersonvomshardy:22:08
andersonvomoh well.. I might as well now. shardy, are you around? =P22:08
shardyandersonvom: yes22:09
andersonvomshardy: just wanted to make sure that we can rebase/fixup the management API for review again, given the last IRC meeting. that's the way we're going, right?22:10
*** rpothier has joined #heat22:10
*** aweiteka has quit IRC22:11
shardyandersonvom: Yes, but we need to get the ReST API enforced via policy.json first22:12
shardywhich I have started, but currently I'm trying to get the instance-users stuff moved on before returning to the request scoping work22:12
*** rpothier_ has joined #heat22:12
openstackgerritStephen Sugden proposed a change to openstack/heat: Add PortCheck resource  https://review.openstack.org/6207822:14
*** rpothier has quit IRC22:15
andersonvomshardy: humm, my impression of the plan was that there was going to be another endpoint enforced by policy.json. is this correct? or how does this relate to enforcing the rest of the API?22:17
*** andrew_plunk has joined #heat22:17
asalkeldmorning22:17
stevebakermorning22:17
*** sgordon has quit IRC22:18
andersonvommorning/afternoon/night22:18
*** tomek_adamczewsk has quit IRC22:21
openstackgerritSteve Baker proposed a change to openstack/heat: Service authorize stack user from provided stack  https://review.openstack.org/5887522:29
openstackgerritSteve Baker proposed a change to openstack/heat: OS::Nova::Server support for software config  https://review.openstack.org/5888022:29
openstackgerritSteve Baker proposed a change to openstack/heat: REST API for software config/deployment  https://review.openstack.org/5887822:29
openstackgerritSteve Baker proposed a change to openstack/heat: Resource types for software config/deployment  https://review.openstack.org/5887922:29
openstackgerritSteve Baker proposed a change to openstack/heat: Database model for software config/deployment  https://review.openstack.org/5887622:29
openstackgerritSteve Baker proposed a change to openstack/heat: RPC service for software config/deployment  https://review.openstack.org/5887722:29
openstackgerritSteve Baker proposed a change to openstack/heat: Allow choice in how SignalResponder user id is stored.  https://review.openstack.org/6190222:29
stevebakerjust a rebase22:29
*** SergeyLukjanov has quit IRC22:46
*** aignatov has quit IRC22:49
shardyandersonvom: Sorry my network just dropped for a while22:51
shardyandersonvom: So no new endpoint, we need to add policy enforcement to the existing ReST API22:52
shardyandersonvom: Then we can define a policy rule which is allows you to defeat the default tenant scoping, and access either different data via existing actions, or potentially some super-admin-only actions22:53
shardybasically the next step from https://review.openstack.org/#/c/58866/3/etc/heat/policy.json22:53
shardyBut the issue is we currently have no policy enforcement at all in the ReST API22:54
shardy(we do for the cloudformation and cloudwatch compatible ones)22:54
shardyandersonvom: ideally, this would all coincide with a revised v2 API, which doesn't contain the tenant in the path, then it would make more sense when you do a request which gives non-tenant-scoped data back22:55
stevebakershardy: should I rejig my SignalResponder change to always store user_id, access_id in resource data?22:56
shardystevebaker: I posted a patch which does that yesterday22:56
shardystevebaker: are we overlapping? :)22:56
stevebakerooh, where?22:56
shardyhttps://review.openstack.org/#/c/62440/22:56
shardyI need to rebase and remove https://review.openstack.org/#/c/62439/ from the chain, because ayoung has suggested an alternative approach which I'm in the process of writing up in a wiki page22:57
stevebakerah, I'm suggesting storing user_id in resource data instead of resource_id22:58
shardystevebaker: Ah, yeah I remember now, that wfm also if you need it for the software-config stuff23:00
shardyhowever23:00
shardytake a look at (2) here:23:00
shardyhttps://wiki.openstack.org/wiki/Heat/Blueprints/InstanceUsers23:00
shardyayoung has suggested something a little different, which may solve our credentials issue in a novel way23:00
*** dims has quit IRC23:01
shardyessentially, we could create a separate heat domain in keystone, where we create a separate user for each credential we need (potentially one for every instance and signal responder)23:01
shardythen just use username/password and auth_token to connect to the API23:01
*** harlowja is now known as harlowja_away23:02
shardywe can retain the policy restrictions related to heat_stack_user to limit the API surface accessible, and manage the lifecycle of each user on a per resource basis23:02
shardyfor example, we could disable the user after a waitcondition handle completes23:02
shardyI'm still mulling it over, but it could possibly allow us to dump a lot of trusts/oauth/ec2tokens complexity23:03
shardys/dump/avoid needing23:03
*** pablosan has quit IRC23:04
*** harlowja_away is now known as harlowja23:05
*** lsmola_ has quit IRC23:06
stevebakershardy: interesting. does that mean that the instances would need to make keystone requests for tokens?23:08
openstackgerritA change was merged to openstack/heat: Prevent tempest from failing upon ActionInProgress  https://review.openstack.org/6270323:08
shardystevebaker: Possibly, I was thinking they could just use python-heatclient23:09
shardyheat stack-signal --data "finished!"23:09
shardystevebaker: And we can still support the existing mode for ec2-keypairs via heat-cfntools23:10
stevebakeryep, that might be worth persuing23:11
shardybut maybe port that to also work with normal auth and the ReST API23:11
shardyonly the ec2-keypair will be owned by the new heat-domain-resource user, not the current user-created user23:11
shardyif you see what I mean ;)23:11
shardyI was thinking OS::Nova::Server could grow a "deploy_credentials" property, which pokes the username and randomly generated password into nova metadata23:12
*** vijendar has quit IRC23:12
*** vijendar has joined #heat23:13
stevebakerwe could integrate that with the software config stuff23:14
stevebakershardy: I could describe my option 5 in that wiki if you like23:15
*** dims has joined #heat23:16
shardystevebaker: Sure, go for it - I've asked ayoung to take a look and update the x509 section too23:16
*** swygue has quit IRC23:16
shardystevebaker: I've been chasing my tail a bit on this, so will be good to get all the ideas down then we can get a concrete plan23:16
shardystevebaker: I started implementing (1), but the more time I spend on it, the more wrong it seemed23:17
*** scroiset_ has quit IRC23:18
stevebaker1) looks like a real rabbit hole23:18
sdakeshardy up late !23:18
shardystevebaker: well I've actually nearly finished implementing it, but it doesn't solve one of the main problems, which is the ec2tokens thing23:19
shardystevebaker: Also the usage of trusts is kinda hairy and I might lose sleep worrying about bugs ;D23:19
shardysdake: Yeah..23:19
*** vijendar has quit IRC23:20
*** sgordon has joined #heat23:21
*** yogesh has quit IRC23:22
*** scroiset has joined #heat23:24
*** urulama has joined #heat23:24
shardystevebaker: ayoung is going to add his stuff, then if you add yours too, I'll review in the morning and start a ML thread if needed so we can agree the plan23:25
shardynow, I should get some sleep ;)23:25
shardynight all23:25
asalkeldnight shardy23:26
*** shardy is now known as shardy_afk23:26
sdakelater shardy_afk23:27
*** gokrokve has quit IRC23:28
*** urulama has quit IRC23:29
*** asalkeld has quit IRC23:29
*** asalkeld has joined #heat23:30
openstackgerritAnderson Mesquita proposed a change to openstack/heat: Check resources are in expected states  https://review.openstack.org/5864123:30
*** IlyaE has quit IRC23:33
*** tims1 has quit IRC23:38
*** agileclipse has joined #heat23:38
lifelessstevebaker:  / asalkeld: btw - https://review.openstack.org/#/c/62520/ - if you have any feedback, that would be awesome23:38
grncdrI am writing tests for this: https://review.openstack.org/#/c/62078/ and I have a question about how to best deal with writing a test that needs to time out23:38
lifelessI don't cut much heat code...23:38
asalkeldlifeless, I'll check it out23:39
grncdrright now I'm stepping a heat.engine.scheduler.TaskRunner in my resources check_create_complete method, but I don't know how to tell if that will step a hundred times a second or one...23:39
grncdrI'm modelling my unit test off of the ones for WaitCondition23:40
asalkeldgrncdr, we fake the sleep23:40
stevebakerlifeless: looking23:41
grncdrasalkeld: yeah I'm seeing there's a stub_wallclock method?23:41
asalkeldhttps://github.com/openstack/heat/blob/master/heat/tests/common.py#L4223:42
grncdrhm, I see test_timeout now...23:42
stevebakerlifeless: is there some novaclient quirk wrt preserve_ephemeral=None vs False vs not specified at all?23:42
asalkeldalso by default we disable the sleep in tests23:42
*** andrew_plunk has quit IRC23:42
grncdrI need a bigger screen. Trying to hack on OpenStack stuff on an 11" MBA is… tricky23:42
asalkeldlol grncdr that sounds tricky23:43
grncdrespecially because I don't think I can even run a dev stack locally23:43
lifelessstevebaker: no; I just don't want to have to bump novaclient in your requirements.txt23:43
lifelessstevebaker: which hard depending on a new parameter would cause23:43
stevebakerright, so method signature has changed23:43
lifelessstevebaker: having to bump requirements.text would mean having to wait for a release of nova-client23:44
grncdrasalkeld: should I be doing something like this in my tests? https://github.com/openstack/heat/blob/master/heat/tests/test_waitcondition.py#L22323:44
stevebakerlifeless: lgtm23:45
asalkeldgrncdr, yeah23:45
lifelessphew, cool - thanks23:45
asalkeldlifeless, I'll wait for jenkins to +123:47
stevebakerlifeless: btw, I tried to trigger the migration issue with data, but it worked. Did you perchance have any stack_lock records at the time?23:47
*** rcleere has quit IRC23:47
asalkeldstevebaker, lifeless I am busy making a migration test23:47
lifelessstevebaker: it's a new table ...23:47
lifelessstevebaker: so I'm confused by your question23:48
stevebakeryeah, duh23:48
* stevebaker eats words23:48
lifelessI can get you a dump of our DB23:48
lifelesswould need to sanitise it somehow23:48
asalkeldlifeless, yeah23:48
asalkeldI am right now trying to figure out waht data to put in the test23:49
stevebakerlifeless: what version of m(ariadb|ysql) are you running?23:49
lifelessii  mysql-server-core-5 5.5.32-0ubuntu23:49
lifelessii  mysql-server-5.5    5.5.32-0ubuntu23:49
lifelesspresumably the contents of the FK related table is sufficient23:50
lifelessasalkeld: http://paste.ubuntu.com/6591689/23:51
lifelessmysql heat -e 'select id from stack;' | pastebinit23:51
asalkeldta23:51
lifelessasalkeld: and yeah, run InnoDB23:52
lifelessanyone running ISAM should be shot.23:52
stevebakerinnodb is the default23:54
*** sabeen has quit IRC23:55
*** faramir1 has joined #heat23:58
lifelessI saw someone asking about ISAM w.r.t. this was all23:58
*** arbylee has quit IRC23:59

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