Thursday, 2014-04-24

*** Qiming has joined #heat00:01
*** gokrokve has quit IRC00:03
*** blomquisg has joined #heat00:05
*** nati_ueno has quit IRC00:05
*** Qiming has quit IRC00:14
*** gokrokve has joined #heat00:30
*** gokrokve has quit IRC00:34
*** nati_ueno has joined #heat00:36
*** rpothier_ has joined #heat00:36
*** zhiyan_ is now known as zhiyan00:37
*** rpothier has quit IRC00:40
*** nati_ueno has quit IRC00:40
*** rpothier_ has quit IRC00:45
*** rpothier__ has joined #heat00:45
*** randallburt has joined #heat00:49
*** randallburt has quit IRC00:50
*** randallburt has joined #heat00:51
*** lindsayk has quit IRC00:53
lifelessrandallburt: hi; SpamapS radix and I talked without you as we couldn't find you at the time.00:54
lifelessrandallburt: I've sent mail to the list, and would be delighted to do high bandwidth chat at a mutually convenient time :)00:55
randallburtlifeless:  no worries, I tried to ping SpamapS via hangouts on my phone at the time; I just got bogged down in other meetings. sorry about that.00:55
lifelessrandallburt: no worries00:55
lifelessrandallburt: hopefully the etherpad is appealing :)00:55
randallburt:D00:55
randallburtI read "appalling" at first.00:56
openstackgerritDmitry Borodaenko proposed a change to openstack/heat: Ignore nova limits set to '-1'  https://review.openstack.org/8938900:57
*** lindsayk has joined #heat00:57
*** Darnoth has quit IRC00:58
*** zhiyan has quit IRC00:58
*** gokrokve has joined #heat00:59
openstackgerritDmitry Borodaenko proposed a change to openstack/heat: Ignore nova limits set to '-1'  https://review.openstack.org/8938900:59
*** zhiyan has joined #heat01:00
*** harlowja has joined #heat01:00
randallburtlifeless:  my fav: "- run each individual convergence step via taskflow via a distributed set of workers". Now that I know what you mean by "taskflow" I may convince kebray to let me chip in on that if I can get my Glance work sorted too. Its been a big wish of mine for a while, but no real time to devote to it.01:01
*** annegentle has quit IRC01:02
*** IlyaE has joined #heat01:03
*** gokrokve has quit IRC01:04
*** nati_ueno has joined #heat01:10
*** IlyaE has quit IRC01:15
lifelessrandallburt: cool01:15
*** TravT has quit IRC01:15
*** Qiming has joined #heat01:22
*** fandi has quit IRC01:27
*** nati_ueno has quit IRC01:28
*** masahito has joined #heat01:33
masahitoto disucuss BPs should I attend weekly heat meeting and propose the BPs as topic?01:34
*** nosnos has joined #heat01:36
*** asalkeld has quit IRC01:41
openstackgerritOpenStack Proposal Bot proposed a change to openstack/heat: Updated from global requirements  https://review.openstack.org/8923201:41
masahitoumm... noone is in here...01:46
*** asalkeld has joined #heat01:53
sdake_masahito just file a blueprint01:56
sdake_we dont typically discuss bluepreints in our weekly meeting unless they are highly controversial01:56
*** gokrokve has joined #heat01:59
*** lindsayk has quit IRC02:00
*** gokrokve has quit IRC02:00
*** gokrokve has joined #heat02:01
*** jrist has quit IRC02:02
*** IlyaE has joined #heat02:04
*** gokrokve has quit IRC02:05
masahitosdake_: thanks for response02:06
*** IlyaE has quit IRC02:06
*** jrist has joined #heat02:10
masahitoI've registered 3 BPs, stack-repairing, property-check and elastic-stack.02:13
masahitoWill these BPs be reviewed by heat review team in the futrue?02:15
lifelessmasahito: it sounds like they will probably overlap with the fairly large refactoring we've just proposed on the list02:25
*** nati_ueno has joined #heat02:26
*** alexheneveld has quit IRC02:33
masahitolifeless: that's means we've already deceided to refactoring heat for Juno release, haven't we.02:41
lifelessmasahito: decided? No. Getting substantial buy-in that its needed? yes :)02:42
masahito For collaboration with Mistral or implementing stack-convergence.02:42
lifelessmistral was discussed this morning in the weekly meeting02:42
lifelessstack convergence I hope will be just the way heat does things (vs a special command or something)02:43
*** alexpilotti has quit IRC02:49
masahitolifeless: Oh. I misunderstood large refactoring has been already propoesed.  sorry : -)02:50
masahitoI try to watch the weekly meeting.02:50
masahitoThanks a lot.02:54
*** andersonvom has joined #heat02:55
*** onorua has joined #heat02:55
*** gokrokve has joined #heat02:59
sdake_lifeless I dont think refactor means what you think it means :)03:00
lifelesssdake_: incrementally improving the design via a series of correctness preserving changes?03:00
sdake_Code refactoring is the process of restructuring existing computer code – changing the factoring – without changing its external behavior. Refactoring improves nonfunctional attributes of the software. Advantages include improved code readability and reduced complexity to improve source code maintainability, and create a more expressive internal architecture or object model to improve extensibility.03:01
lifelesssdake_: wikipedia? I think the definition in the refactoring book is closer to whats in my head. Not to worry :)03:02
sdake_i think the term your looking for is ground-up rewrite :)03:02
sdake_i have a hard time calculating how we could get from where we are today to how you want the code to behave in an incremental evolutionary way03:04
sdake_its more like congress - throw em all out :)03:04
lifelesssdake_: the transition plan section has a suggestion on such a path03:06
randallburtsdake_:  a belated lol.03:08
sdake_update has been rewritten 5+ times and still isn't correct03:08
*** harlowja is now known as harlowja_away03:09
sdake_it isn't because the architecture is unsound, its because new problems are discovered that were not understood originally03:09
sdake_if the end goal is 100k resource scale, wouldn't an incremental change approach be to see if update could be made to work at that scale?03:10
randallburtsdake_:  so the concern here is that because this proposal implies essentially zero difference between a create and an update that now both won't be correct?03:11
* stevebaker is back03:11
*** IlyaE has joined #heat03:12
sdake_o/ stevebaker03:13
lifelesssdake_: the basic operation model falls apart when dealing with 40 node clusters03:16
lifelesssdake_: you are right that we can do little tweaks to change things without changing the core, but there doesn't seem like much reason to believe the current approach can cope with e.g. autoscaling a 40 node cluster (the requirement to hit STACK_READY before submitting a new update each time)03:16
*** samstav has quit IRC03:17
sdake_when I spoke with zane about refactoring update to work he popped out a 3 month schedule03:19
sdake_I wouldn't call that a little tweak ;)03:19
asalkeldsdake_ I think bits can be done here with no interuption03:19
asalkeld(the observer)03:20
asalkeldand probably as you go on developing it should be easy enough to move to this functionality03:21
*** IlyaE has quit IRC03:22
randallburtwe may be able to even keep most of the taskrunner interface intact (for example) for minimal impact on the current resource implementations. They'd become shims for the distributed tasking perhaps, but its still incremental.03:23
sdake_lifeless is the basis of the argument that one process cannot handle autoscaling in a way that meets our goals?03:23
randallburtsdake_:  I would also add scaling to servicing large numbers of tenants all with stacks of various sizes, complexities and orchestration footprints.03:25
lifelesssdake_: I can't quite parse that question. Number of processes isn't a key thing here. (beyond getting to being highly available, of course)03:26
sdake_randallburt you mean the work jasond wrapped up doesn't scale to your targets03:26
*** cmyster has joined #heat03:27
*** cmyster has joined #heat03:27
randallburtsdake_:  so far, so good, but there will be a definite point where the db locking will cause problems as we have to scale up engine nodes.03:27
cmystermorning03:27
sdake_one process is responsible for autoscaling - at some upper bound that process hits a limit03:27
randallburtsdake_:  but as of now our traffic isn't terribly high03:27
sdake_my question is - was your assertion that this upper limit is 40 vms?03:28
sdake_horizontal scaling originally identified in our architecture was focused around a DHT model - not database locking03:29
sdake_DHT has no scale limit03:29
sdake_but that implementation, after 2 years, was never delivered because it fit into warren buffet's inbox labled "too hard"03:30
randallburtsdake_:  plus someone probably brought up zookeeper and people lost it.03:30
asalkeld:-)03:31
sdake_dont even get me started on zookeeper03:31
asalkeldwell it would be good if we can just not need locking at all03:31
sdake_agree the answer to that is dht as originally specified in the architecture03:32
lifelessso I can certainly see a DHT sitting in this model too03:32
sdake_yes i read the proposal03:33
lifeless:)03:33
*** arbylee has joined #heat03:34
sdake_point being dht was specified in the architecture - database locking was implemented - the correct answer to unlimited horizontal scaling is dht not database locking03:34
lifelesssdake_: a DHT alone doesn't get you one-and-only-one agent operating on a thing (because DHT resizing isn't atomic in most DHTs - but DHT + consensus can get you that)03:35
lifelesssdake_: that leaves the callgraph implementation though as a big remaining source of user visible pain03:35
sdake_atomic dht membership is likely one reason why dht was never implemented as the scaleout solution03:37
lifelesssdake_: we're currently going through the business case process to fund this project; the exact implementation is entirely up to heat-core to dictate - what SpamapS and I are doing is trying to kick start a discussion and have a feasible design that isn't disruptive to deliver03:37
sdake_if you can protect the correctness of heat, you would have my support03:38
lifelesssdake_: our intent is to have ~10 folk working on this (devs and test folk, not counting project mgmt folk etc)03:38
sdake_I'm not convinced the correctness of heat could be protected03:38
lifelessso we can tackle a reasonable sized chunk of work03:38
sdake_yup i heard the staffing ideas - those folks will have to come up to speed on the code base03:40
sdake_i typically find someone full time takes 6-12 mos if they are highly comptent03:40
sdake_(to come up to speed)03:41
asalkeldsdake_ just change your nick to "getoffmylawn" ;)03:42
sdake_and take your damn dog with you03:42
cmysterteehee03:42
asalkeldlol03:42
lifelesssdake_: yeah, I know - SpamapS is likely going to regret getting his wish of more folk hacking on heat :)03:43
lifelesssdake_: can you articulate the correctness concerns you have?03:43
sdake_if at each step along the change sets, heat continues to be deployable from trunk03:44
lifelesssdake_: I mean, some things like 'stack state -> _FAILED if any resource can't be provisioned' are things we *want to change*, but I presume you don't consider that an existing element of correctness03:44
lifelesssdake_: oh hell yes it has to be. No broken trunk ever. NONONO.03:44
sdake_no that is incorrect03:44
sdake_(incorrect re stack state failed)03:44
sdake_just like update fails - whole stack is busted - incorrect03:45
lifelesssdake_: so - trunk status - we're driving this from the tripleo team and the HP cloud team - both of whom are CD focused and want a stable reliable trunk at any point in time03:46
sdake_the code as is doesn't operate correctly as we would expect it to do so03:46
*** ramishra has joined #heat03:46
lifelessasalkeld: questions for you inline03:46
sdake_my general take is I'd like to fix the things that are incorrect and make them behave correctly03:47
sdake_but I'm just one heat core guy of many :)03:47
sdake_i think changing the code to something more complex is likely to lead to less correctness03:48
sdake_but just a hunch03:48
lifelessI certainly agree - complexity -> bugs.03:49
lifelesshave you seen 'simple made easy' ?03:49
sdake_doesn't ring a bell03:49
asalkeldor: complexity for dummies03:49
lifelesshttp://www.infoq.com/presentations/Simple-Made-Easy-QCon-London-201203:49
lifelessso, how would you handle allowing new stack updates to be requested before the prior one has reached STACK_READY ?03:50
lifelesswithout the key changed for that - moving from its-a-call-stack to its-a-graph-convergence-problem ?03:51
sdake_9pm at night been rolling since 6am I hope you dont expect a design to magically pop out of my head :)03:51
lifelessnot at all03:51
lifelessjust I don't want to fall into the trap of solving only-some-issues which can happen when we don't look at the whole thing03:52
sdake_food is here - i'm off for the night03:52
lifelessciao03:52
asalkeldlifeless, dht is a good idea imo03:52
sdake_dht was the original design - never implemented03:52
sdake_have to ask the question why03:53
stevebakerlifeless, SpamapS: hey, os-apply-config hasn'03:53
lifelessstevebaker: hasn't ?03:53
*** vinsh is now known as vinsh_away03:53
stevebakert made it to pypi or tarballs.os (release 0.1.15)03:53
sdake_night03:54
cmysternn sdague03:54
cmysterNO03:54
cmysterthat tab key I tell you...03:54
*** nati_ueno has quit IRC03:55
lifelessasalkeld: so dependencies03:57
asalkeldlifeless, I can see we are going to need dht03:57
asalkeldto prevent flap03:57
randallburtsdake_:  re Why not DHT - no one brought it up to jasond AFAIK and he wasn't working on Heat 2 years ago ;)03:57
asalkeldin the case you were going through03:57
asalkeld# of jobs can't get out of hand03:58
lifelessasalkeld: so think about the events happening here03:59
asalkeldelse delete too many, then create too many03:59
lifelessasalkeld: I don't think hysteresis implies a DHT03:59
asalkeldlifeless, no - but makes it easier to track work on a particular resource04:00
asalkeldhash the resource_id04:00
asalkeldand you can monitor what those jobs on that resource are doing04:00
lifelessasalkeld: thats not a DHT, but sure :) (its a hash ring)04:00
lifelessin fact, I don't think a DHT gets you hysteresis in and of itself04:01
lifelessand you'd need some gnarly green-thread-introspection stuff to prevent concurrency04:01
asalkeldagree04:02
lifelessso I'd rather not complect these things - hysteresis - things working on the scaling group should implement hysteresis and lock each other out.04:02
asalkeldwell it should just be another nested stack04:03
lifelessasalkeld: as far as dependencies go, what I think you mean is04:03
lifelesssome things need to reach when a child comes or goes04:03
lifelesse.g. when a launchconfig goes complete you want to start the work on the instance04:04
asalkeldwell I was thinking of all the yields and how each big resource has potentially many stages04:05
lifelessasalkeld: so a nested stack thats being replicated? Sure, but the # of such stacks and the last direction of change and size of change is what you need for hysteresis04:05
lifelessasalkeld: so each yield point is basically going to become a separate action04:05
asalkeldhow are the stages broken up04:05
asalkeldyes04:06
asalkeldjust saying that need some tought04:06
asalkeldthought04:06
asalkeldand we need to be able to package that well04:06
lifelessso the question in the strawman up there is...04:06
lifelesswhat event should the next stage be reacting too - how will the diff-and-create-actions code know when to run next04:06
asalkeldyes, since it's internal knowledge (what stage of the resource creation is up to)04:07
lifelessthere are I think two things that I'd like to have here - one generic graph diff that looks at desired vs actual (and neds to be scaling aware to know to use a desired template on a sub stack etc)04:08
*** gokrokve has quit IRC04:08
lifelessand secondly, resource specific knowledge that plugins supply that says 'ok, the resource I have here is incomplete or wrong in X way, so I need to do Y to adjust it'04:08
asalkeldcould just be "in progress" (i.e. needs to be run again)04:09
lifelessthen the generic stuff would run until the broad shape is correct and then the resource specific stuff would kick in to do the actual local work04:09
lifelessas an example making a server with a neutron port04:09
lifelessthe graph diff would see server depends on port and nothing exists, so a) make port and return (make port is then the (B) resource specific bit)04:10
lifelesswhen the port comes alive the parent gets the event, which diffs again and sees the port is there but not the server, so hands off to the (B) resource specific bit for servers.04:10
asalkeldwell we will need resources to be smarter04:11
asalkeldso they can figure out what needs to be done04:11
lifelesswhen the server comes alive, its parent gets a graph change event, the generic diff code would run to get local constraints, then back into the resource specific stuff for whatever resource the parent was04:12
asalkeldor, we go the other way an say a resource can only do one thing, and you must use nested stacks to compose04:12
lifelessinternalwise I'd say a nested stack is what a complex resource is04:12
lifelessnot sure that users should see that aspect of it but that seems likely to be hidable04:13
asalkeldit would push our nested stack capablitiy04:13
lifelessok so lets be specific04:16
lifelessthere needs to be an ability for a given resource to diff current state vs desired state04:16
lifelesswhere that resource might be a hand specified one, or a member of a scale group04:16
lifelessthe more we generalise that the less diff code we need to write04:16
*** harlowja_away is now known as harlowja04:18
asalkeldit does just sound like a new stack04:18
lifelessit needs to be efficient - local and frugal on data requirements04:20
lifeless(no diffing all the subchildren on every run!)04:21
lifelessthat might be a generation checking-and-signoff thing04:21
lifelessthere are a few ways to make incremental graph diffs fast04:21
cmysterguys since not too many people are only and this might be important for later, can you take this to a thread of sorts ?04:22
asalkeldcmyster, you are welcome to interupt04:23
asalkeldwe can put this in an etherpad at some point04:23
cmystercan't, got other things to worry about before my boss comes, but would love to read about it later and might comment on it04:24
cmysterfrom a QE point of view04:24
lifelessit is a thread :)04:24
lifelesstheres the etherpad04:24
lifelessand the mailing list04:24
lifelessthis is just a breakout session04:24
*** randallburt has quit IRC04:24
cmysterk04:25
asalkeldlifeless, this seems like uni (I did elec. eng process control) inputs (template), outputs (observer state), feedback (actioner/differ)04:28
asalkelddrive output to look like desired input04:29
*** blomquisg has quit IRC04:29
*** asalkeld has quit IRC04:35
*** arbylee has quit IRC04:39
*** lipinski has quit IRC04:40
*** blomquisg has joined #heat04:42
*** asalkeld has joined #heat04:51
*** nati_ueno has joined #heat04:52
*** chandan_kumar has joined #heat05:00
*** blomquisg has quit IRC05:05
*** gokrokve has joined #heat05:07
*** rwsu has quit IRC05:07
*** nati_ueno has quit IRC05:07
*** nosnos has quit IRC05:08
*** blomquisg has joined #heat05:09
*** gokrokve has quit IRC05:11
*** IlyaE has joined #heat05:11
lifelessasalkeld: it is indeed05:12
openstackgerritSteve Baker proposed a change to openstack/heat: Do not initialise stack_user password  https://review.openstack.org/8999905:19
openstackgerritSteve Baker proposed a change to openstack/heat: Refactor DB resource fetching from Resource to Stack  https://review.openstack.org/9000005:19
openstackgerritSteve Baker proposed a change to openstack/heat: resource_get_all_by_stack returns a dict  https://review.openstack.org/9000105:19
openstackgerritSteve Baker proposed a change to openstack/heat: Fetch all db resources in one query  https://review.openstack.org/9000205:19
openstackgerritSteve Baker proposed a change to openstack/heat: Do not query database for every metadata_get  https://review.openstack.org/8973705:19
openstackgerritSteve Baker proposed a change to openstack/heat: Use resource methods for metadata get/set  https://review.openstack.org/8973605:19
stevebakerlifeless: if the above check passes, up to https://review.openstack.org/#/c/90002/ would be worth testing in yr cloud05:21
stevebakerSpamapS: when you're about, can you check why oac 0.1.17 didn't make it to pypi? thanks05:22
*** e0ne has joined #heat05:22
*** daneyon has quit IRC05:23
lifelessstevebaker: he only did ocollectc AFAIK05:23
*** rwsu has joined #heat05:23
*** onorua has quit IRC05:26
*** e0ne has quit IRC05:26
*** nkhare has joined #heat05:27
*** wwallnrr__ has quit IRC05:27
*** nati_ueno has joined #heat05:33
*** nosnos has joined #heat05:35
*** tspatzier has joined #heat05:44
*** renlt has joined #heat05:44
*** renlt has quit IRC05:45
*** renlt has joined #heat05:46
*** yogeshmehra has joined #heat05:47
*** Qiming has quit IRC05:48
*** Qiming has joined #heat05:49
*** nati_ueno has quit IRC05:58
*** tspatzier__ has joined #heat05:59
*** tspatzier has quit IRC06:02
*** tspatzier__ has quit IRC06:05
*** nati_ueno has joined #heat06:05
*** tspatzier has joined #heat06:07
*** gokrokve has joined #heat06:07
openstackgerritOpenStack Proposal Bot proposed a change to openstack/heat: Imported Translations from Transifex  https://review.openstack.org/8975006:09
*** yogeshmehra has quit IRC06:11
*** gokrokve has quit IRC06:12
*** IlyaE has quit IRC06:13
*** jprovazn has joined #heat06:23
*** IlyaE has joined #heat06:23
*** saju_m has joined #heat06:23
*** harlowja is now known as harlowja_away06:30
*** IlyaE has quit IRC06:37
therveGood morning!06:37
asalkeldyo therve06:40
*** yogeshmehra has joined #heat06:41
*** shakamunyi has quit IRC06:42
cmystermorning06:45
*** ramishra has quit IRC06:45
*** ramishra has joined #heat06:46
openstackgerritSushil Kumar proposed a change to openstack/heat: Restores Nova API for volume attach and detach  https://review.openstack.org/8979606:49
*** blomquisg has quit IRC06:50
*** ifarkas has joined #heat06:59
*** blomquisg has joined #heat07:05
skraynevGood morning all ;)07:07
*** shakamunyi has joined #heat07:08
*** gokrokve has joined #heat07:08
*** lsmola has joined #heat07:09
cmystermorning07:11
lifelesstherve: o/07:11
*** e0ne has joined #heat07:11
*** shakamunyi has quit IRC07:12
*** gokrokve has quit IRC07:12
*** e0ne has quit IRC07:16
*** onorua has joined #heat07:16
thervelifeless, Man where's that etherpad07:17
therveIt sounds like stuff was discussed07:17
*** e0ne has joined #heat07:17
openstackgerritJun Jie Nan proposed a change to openstack/heat-templates: Add one example to show deploy sequence  https://review.openstack.org/8175707:18
therveOh got the mail07:18
*** sorantis has joined #heat07:18
*** sorantis has quit IRC07:19
lifelesstherve: stuff was :)07:19
openstackgerritJun Jie Nan proposed a change to openstack/heat-templates: Example template that performs copying of SSH keys  https://review.openstack.org/8339707:19
lifelesstherve: typical lifeless crazy, of course07:19
*** sorantis has joined #heat07:19
therveYeah I already saw your BP yesterday :)07:20
sorantismorning07:20
*** ramishra has quit IRC07:24
therveThe plan is cute but super unrealistic regarding time07:25
*** ifarkas has quit IRC07:25
*** ifarkas has joined #heat07:26
lifelesstherve: J? placeholder arguably07:26
thervelifeless, Okay07:26
lifelesstherve: I'm thinking 6-12 month process to deliver it all, with a focused team just doing that07:26
lifelesssome benefits will be felt earlier than others07:27
therveSo I'm started looking a tiny bit of that plan07:28
therveWhich is move to use notifications07:28
therveInstead of polling07:29
lifelessstevebaker: testing your patchset now07:29
lifelesstherve: yeah, important transition07:29
lifelesstherve: what do you think of the idea in that plan - of an abstraction layer to move everything to events ?07:29
therveI don't think it involves ceilometer though, we should plug into the nova notifications directly07:29
*** lipinski has joined #heat07:30
thervelifeless, Isn't event just another term for notification?07:30
asalkeldtherve, one potential benefit to using ceilometer would be you could just setup alarms on state changes07:32
asalkeldand heat would not have to process that stream of notifications07:32
*** sorantis has quit IRC07:33
asalkeldon  a large deployment I could imagine that is quite a burden07:33
asalkeld(processing large number of notifications)07:33
therveMaybe07:34
therveFrom a performance standpoint I'm not sure that's valid, because creating and receiving alarms is not super cheap07:36
therveI can see why separating the concerns sounds appealing, though07:36
shardymorning all07:37
lifelesstherve: yes07:37
lifelesstherve: I think ceilometer for things we don't get directly (e.g. load levels on a VM) makes a lot of sense07:38
lifelesstherve: we don't want to reinvent ceilometer07:38
thervelifeless, Sure, but that's not the core of the problem07:38
thervestates change is07:38
therveIe "let me know when this server transition to ACTIVE/ERROR"07:38
lifelesstherve: well, the core of the problem is only looking for that while provisioning, rather than all the time; polling is a symptom not a cause of that.07:43
lifelesstherve: I think we're agreeing. BTW you didn't really answer 19:29 < lifeless> therve: what do you think of the idea in that plan - of an abstraction layer to move everything to events ?07:44
thervelifeless, I don't think I understood it07:44
lifelesstherve: oh, also another data point - lots of APIs fail poorly - like having to call nova delete many times to make it actually delete a node07:44
therveIs it the thing talking about polling the DB?07:45
lifelessso we need some mix of stuff in the solution07:45
lifelesstherve: the idea of the observer is that it does *whatever is needed* to keep an up to date model of the reality, whether thats subscribing to notifications, polling via an API, or $whatever07:45
lifelesstherve: and then all the code behind it can be built on an event basis07:46
cmystermorning shardy07:47
therveThat sounds nice in theory07:47
*** akuznetsov has quit IRC07:51
*** akuznetsov has joined #heat07:52
*** sorantis has joined #heat07:55
*** mkollaro has joined #heat08:03
*** bvandenh has joined #heat08:03
*** shakamunyi has joined #heat08:09
*** gokrokve has joined #heat08:09
*** sorantis has quit IRC08:13
*** shakamunyi has quit IRC08:13
*** gokrokve has quit IRC08:13
*** sorantis has joined #heat08:14
*** e0ne has quit IRC08:15
lifelessstevebaker: success with 30 nodes08:17
*** e0ne has joined #heat08:17
*** nosnos has quit IRC08:18
*** derekh has joined #heat08:18
*** yogeshmehra has quit IRC08:19
*** jistr has joined #heat08:21
*** julienvey has joined #heat08:22
*** saju_m has quit IRC08:35
*** alexheneveld has joined #heat08:41
*** nati_ueno has quit IRC08:46
*** alexheneveld has quit IRC08:48
*** e0ne_ has joined #heat08:48
*** e0ne has quit IRC08:51
*** pas-ha has joined #heat08:52
openstackgerritDimitri Mazmanov proposed a change to openstack/heat: Add a Nova Flavor resource.  https://review.openstack.org/9002908:54
openstackgerritDimitri Mazmanov proposed a change to openstack/heat: Add a Nova Flavor resource.  https://review.openstack.org/9002908:57
*** saju_m has joined #heat09:01
openstackgerritDimitri Mazmanov proposed a change to openstack/heat: Add a Nova Flavor resource.  https://review.openstack.org/9002909:03
*** renlt has quit IRC09:09
*** shakamunyi has joined #heat09:09
*** gokrokve has joined #heat09:10
*** shakamunyi has quit IRC09:14
*** gokrokve has quit IRC09:14
*** denis_makogon has joined #heat09:21
*** cdent has joined #heat09:26
*** zhiyan is now known as zhiyan_09:32
*** jprovazn has quit IRC09:36
*** saju_m has quit IRC09:36
*** saju_m has joined #heat09:38
*** alexheneveld has joined #heat09:42
*** bvandenh has quit IRC09:45
openstackgerritDimitri Mazmanov proposed a change to openstack/heat: Add a Nova Flavor resource.  https://review.openstack.org/9002909:45
*** bvandenh has joined #heat09:45
*** blomquisg has quit IRC09:53
*** alexheneveld has quit IRC09:55
*** zhiyan_ is now known as zhiyan09:58
openstackgerritDimitri Mazmanov proposed a change to openstack/heat: Add a Nova Flavor resource.  https://review.openstack.org/9002910:02
*** blomquisg has joined #heat10:06
*** dims has quit IRC10:08
*** zhiyan is now known as zhiyan_10:08
*** gokrokve has joined #heat10:11
*** jprovazn has joined #heat10:12
*** gokrokve has quit IRC10:15
*** nosnos has joined #heat10:15
*** dims has joined #heat10:19
*** e0ne_ has quit IRC10:20
*** Qiming has quit IRC10:26
*** sorantis has quit IRC10:34
*** blomquisg has quit IRC10:36
*** sorantis has joined #heat10:41
*** saju_m has quit IRC10:45
sorantistherve, hi! got a minute?10:48
thervesorantis, Don't ask to ask :)10:49
sorantisack :)10:49
*** blomquisg has joined #heat10:49
sorantisreading your comments now. Any reason why I should remove check_create_complete?10:50
openstackgerritSergey Kraynev proposed a change to openstack/heat: Allow empty sections in the yaml templates  https://review.openstack.org/9005811:04
*** e0ne has joined #heat11:05
*** e0ne has quit IRC11:10
*** gokrokve has joined #heat11:11
*** e0ne has joined #heat11:12
*** blomquisg has quit IRC11:14
*** gokrokve has quit IRC11:16
thervesorantis, Because your resource is created right away11:20
therveAFAIU check_create_complete is useless here11:20
sorantisI see11:20
cmysteroh right, this reminds me,11:20
cmystershardy: did you see my commit ?11:21
*** blomquisg has joined #heat11:28
*** julienve_ has joined #heat11:31
*** nkhare has quit IRC11:31
*** ramishra has joined #heat11:34
*** rpothier__ has quit IRC11:38
*** chandan_kumar has quit IRC11:45
*** pas-ha has quit IRC11:45
*** cdent has quit IRC11:46
*** Qiming has joined #heat11:48
*** blomquisg has quit IRC11:54
*** asalkeld has quit IRC11:56
*** shakamunyi has joined #heat11:57
*** achampion has quit IRC11:59
shardycmyster: You mean the software config review?12:00
cmysteroh hi, yes12:00
shardycmyster: just looking at it now12:01
*** jamie_h has joined #heat12:07
shardycmyster: I though you didn't write API tests :P12:07
shardy;)12:07
*** aweiteka has joined #heat12:08
cmysterI don't but this is an exception. no time to write a scenario and you need to make sure it works12:08
cmysterI repeat myself. API means nothing from a QE POV12:08
cmyster200 OK is not a valid answer from my POV etc etc...12:09
*** erecio has joined #heat12:09
shardyI see value in both test types12:10
cmysterthere is,12:10
cmysternot saying there is no value. just not to me, remember the apple example ?12:10
*** gokrokve has joined #heat12:12
shardyI'm not going to argue it again, happy to see contributions which improve tempest coverage via whatever category :)12:12
*** erecio has quit IRC12:13
shardycmyster: but FWIW my understanding is we're moving towards making the API tests things which can be done with a standard (e.g cirros) image, and the scenario tests more involved tests which require a bigger image containing agents etc, hence much much slower12:13
shardycmyster: so the key value of API coverage is smoke tests which can realistically be done in the gate12:14
shardyif everything is a full-fat integration test in scenarios, we won't be able to gate on it because it will take hours to run12:14
shardydamn, I'm arguing it again, aren't I ;)12:14
* shardy shuts up12:14
cmysterI'm not arguing one bit :) you are correct obviously, but my reason to avoid it are a bit different12:14
cmysterarguing makes good code.12:15
*** jdob has joined #heat12:16
*** gokrokve has quit IRC12:17
cmysterlong story shot, have I had time and could be dedicating 100% to this specific thing, I won't do it as an API test.12:17
shardyIt looks like a good start to me12:18
cmysterIts to big and important to just whisk a short scenario, so here at least I can cover all the basics12:18
shardyperhaps you can collaborate later with stevebaker and nanjj on a more "real world" scenario test12:18
cmysterindeed12:19
cmysterI need to return to the sanity scenario I was working on as well...12:19
cmysterI will add elements from here as well12:19
*** yogeshmehra has joined #heat12:20
*** aweiteka has quit IRC12:22
shardycmyster: few comments added, mostly minor stuff12:23
*** erecio has joined #heat12:24
*** yogeshmehra has quit IRC12:25
*** erecio has quit IRC12:27
*** rpothier__ has joined #heat12:34
*** julienve_ has quit IRC12:39
*** erecio has joined #heat12:40
*** nosnos has quit IRC12:42
*** cmyster has quit IRC12:42
*** rbuilta has joined #heat12:43
*** julienve_ has joined #heat12:53
*** spzala has joined #heat12:54
sdaguestevebaker: congrats on gerrit change 90K :)12:55
*** jamie_h has quit IRC12:59
*** jamie_h has joined #heat12:59
*** alexpilotti has joined #heat13:01
*** nkhare has joined #heat13:05
shardysdague: Hi, I'm working on some tests using the cirros image like we discussed last week13:05
shardysdague: Is it safe to use compute.image_ref as the stack input, i.e will that always be cirros in the gate?13:06
shardythen we use orchestration.image_ref whereever we need the full cfntools image?13:06
sdagueyes, I think that's sane13:07
shardysdague: Ok, thanks13:07
sdaguewe should probably make that set of assumptions more explicit in the tempest.conf. That compute image needs to be something yuo can ssh to, and orchestration image needs to be something with cnftools13:08
shardyI've got a template which does wait condition signalling via curl with a cirros image now, so we can probably convert some of the existing tests to use the same approach13:08
sdaguecool13:08
shardyOk, sounds good13:08
shardyin general I've been erring towards using wait conditions to return data from the instance instead of SSHing to them13:09
*** achampion has joined #heat13:09
shardythen in future we can use either SoftwareDeployment resources or a native WaitCondition replacement instead13:09
shardye.g http://paste.fedoraproject.org/96586/3450041313:10
*** aweiteka has joined #heat13:11
*** gokrokve has joined #heat13:13
sdagueshardy: so question on the template replacement, what happens if dev_name_2 showed up in that template?13:14
shardysdague: Hmm, true, I should probably make the test a regex13:15
sdagueshardy: yeh, this was actually less about this test in particular13:16
shardyI was making some assumptions like the attached disk will be vdb, because the cirros image doesn't allow disk lookup by uuid13:16
shardywhereas we could do an explicit lookup on e.g the full Fedora image13:16
sdagueit was just something I was wondering about heat template replacement, because by not using a sigal of some sort, I wasn't sure what the behavior was13:16
*** cdent has joined #heat13:16
shardyOh, you mean str_replace?13:16
sdagueyeh13:17
shardythat just does a dumb replacement, so it's up to the template author to choose substitution tokens which are suitably unique within the template snippet13:17
*** gokrokve has quit IRC13:17
shardyIf someone puts dev_name_2 in the userdata, it will get substituted with e.g vdb_213:18
*** sgran has quit IRC13:19
*** blomquisg has joined #heat13:20
sdagueok, like c macros13:20
sdagueis that something well documented? I could imagine someone tripping over it.13:20
*** ramishra_ has joined #heat13:21
shardyhttp://docs.openstack.org/developer/heat/template_guide/hot_spec.html#str-replace13:21
shardyseems quite well explained there13:21
*** ramishra has quit IRC13:22
*** sorantis has quit IRC13:23
*** vijendar has joined #heat13:28
*** pas-ha has joined #heat13:30
*** samstav has joined #heat13:31
*** blues-man has joined #heat13:31
*** sgordon has joined #heat13:33
*** sgordon has quit IRC13:33
*** sgordon has joined #heat13:33
*** sgran has joined #heat13:36
*** sorantis has joined #heat13:40
*** yogeshmehra has joined #heat13:41
*** varora has joined #heat13:43
*** pafuent has joined #heat13:45
*** akuznetsov has quit IRC13:46
*** nanjj has joined #heat13:47
*** zns has joined #heat13:48
*** zns has quit IRC13:48
*** zns has joined #heat13:48
*** nanjj has quit IRC13:48
sdakemorning13:49
shardymorning sdake13:49
*** varora has left #heat13:50
*** nanjj has joined #heat13:50
*** zns has quit IRC13:51
nanjjHi13:51
sdakehey shardz13:53
*** vinsh_away is now known as vinsh13:53
*** zns has joined #heat13:54
*** zhiyan_ is now known as zhiyan13:55
*** che-arne has joined #heat13:58
*** sabeen has joined #heat14:00
*** radez_g0n3 is now known as radez14:01
*** andersonvom has quit IRC14:01
*** gokrokve has joined #heat14:01
*** zns has quit IRC14:03
*** zz_gondoi is now known as gondoi14:03
*** sabeen has quit IRC14:04
*** sabeen has joined #heat14:05
*** akuznetsov has joined #heat14:05
*** zns has joined #heat14:07
*** denis_makogon has quit IRC14:13
*** andersonvom has joined #heat14:15
*** funzo has quit IRC14:27
*** funzo has joined #heat14:28
*** funzo is now known as Guest1881814:28
*** kgriffs|afk is now known as kgriffs14:29
*** nanjj has quit IRC14:31
*** Guest18818 is now known as funzo14:37
*** TravT has joined #heat14:37
*** sjmc7 has joined #heat14:46
*** IlyaE has joined #heat14:49
*** daneyon has joined #heat14:53
*** ramishra_ has quit IRC14:53
*** piyush1 has joined #heat14:54
*** jamie_h has quit IRC14:57
*** jamie_h has joined #heat14:57
*** yogeshmehra has quit IRC15:00
*** dims has quit IRC15:03
*** chandan_kumar has joined #heat15:04
*** pafuent has quit IRC15:04
*** nkhare has quit IRC15:04
*** dims has joined #heat15:05
*** pablosan has joined #heat15:05
openstackgerritJay Dobies proposed a change to openstack/heat: Added explicit call to validate template version  https://review.openstack.org/9010915:06
*** ramishra has joined #heat15:08
*** pafuent has joined #heat15:10
*** tspatzier has quit IRC15:14
*** zns has quit IRC15:15
*** mspreitz has joined #heat15:16
*** david-lyle has joined #heat15:16
*** chandan_kumar has quit IRC15:16
openstackgerritJason Dunsmore proposed a change to openstack/heat: Don't use SSH in Rackspace::Cloud::Server  https://review.openstack.org/8321815:20
*** ramishra has quit IRC15:20
*** julienve_ has quit IRC15:22
openstackgerritPavlo Shchelokovskyy proposed a change to openstack/heat: Add range constraint to AWS volume size  https://review.openstack.org/8988115:27
*** nanjj has joined #heat15:28
*** onorua has quit IRC15:38
*** m_22 has joined #heat15:42
*** mspreitz has quit IRC15:47
*** piyush1 has quit IRC15:51
*** nanjj has quit IRC15:52
*** nanjj has joined #heat15:52
*** mspreitz has joined #heat15:53
*** mkollaro has quit IRC15:54
*** zns has joined #heat15:57
*** mspreitz_ has joined #heat15:57
*** mspreitz has quit IRC15:57
*** mspreitz_ is now known as mspreitz15:57
*** mspreitz has quit IRC15:59
*** lsmola has quit IRC16:00
*** tspatzier has joined #heat16:01
*** pafuent has quit IRC16:01
*** dims has quit IRC16:03
*** pafuent has joined #heat16:03
*** ramishra has joined #heat16:05
*** dims has joined #heat16:06
therveSpamapS, We still require cfn-api for wait conditions16:07
thervere your email16:07
SpamapStherve: we do not require waitconditions, however. :)16:07
SpamapSdeployments serve that purpose nicely now16:07
therveHum right16:08
shardySpamapS: the only issue is deployments require agent support16:08
therveshardy, So do wait conditions?16:08
shardytherve: no they don't, you can just use curl16:08
therveOh that's right16:08
*** randallburt has joined #heat16:08
shardyI'm thinking of reviving my WaitSignal patch which would provide attributes which would allow a curl call to the native signal API16:08
*** sorantis_ has joined #heat16:09
therveWell because there are widely insecure though16:09
SpamapSshardy: https://git.openstack.org/cgit/openstack/tripleo-image-elements/tree/elements/os-refresh-config/os-refresh-config/post-configure.d/99-refresh-completed16:09
SpamapSshardy: curl works fine for deployments too16:09
shardySpamapS: only if you use the CFN API16:09
SpamapSwe only support one per server right now in tripleo .. that's our bug.. but we just alias the deployment signal as 'completion-signal' and it works16:09
shardySpamapS: I'm talking about providing the same sort of interface via the native signal API16:10
SpamapSshardy: so deployments are feeding me a cfn url?16:10
shardySpamapS: yes16:10
SpamapSweird16:10
shardydepending on the transport16:10
SpamapSnicely hidden from me16:10
SpamapSbut WEIRD16:10
shardyI agree16:10
shardyI think it was a pragmatic decision based on what worked at the time16:10
SpamapSYeah for sure16:10
therveshardy, How can you provide a URL for signal?16:10
therveFor the native signal API I mean16:11
shardytherve: provide the URL, and a token, then you can use curl to post to the URL16:11
SpamapSI'm guessing that it would require a native ec2-signer-like interface16:11
therveshardy, So effectively time constrained16:11
therveI guess it doesn't matter so much for wait conditions16:12
*** Qiming has quit IRC16:12
*** sorantis has quit IRC16:12
shardyExactly, it's a harder problem for other stuff which doesn't have a finite expiry16:12
*** sorantis_ has quit IRC16:13
*** mkollaro has joined #heat16:13
shardytherve: http://paste.fedoraproject.org/96649/9835601116:13
SpamapSI think we might want to consider copying swift's tempurl scheme16:14
*** piyush1 has joined #heat16:14
*** bvandenh has quit IRC16:14
shardythere's an example of where I'd like to use a OS::Heat::WaitSignal16:14
SpamapSrather than trying to use tokens16:14
SpamapStokens are massive16:14
shardySpamapS: I think stevebaker is actually looking at using swift for the signalling16:14
shardywhich would be another way to solve it16:14
SpamapSshardy: yeah, that will definitely scale better than client->heat-api->rabbitmq->heat-engine->mysql16:15
SpamapSat the cost of needing either some kind of swift notification mechanism or polling swift like mad16:15
*** piyush2 has joined #heat16:15
therve?16:15
therveDid you really mean "definitely" here? :)16:16
SpamapStherve: yes16:16
SpamapStherve: we currently poll heat-api->rabbitmq->heat-engine->mysql like mad16:17
*** dims has quit IRC16:17
SpamapStherve: polling swift like mad WILL scale better16:17
therveOh you you mean that signalling, okay16:17
SpamapStherve: until we have a user consumable notification bus, swift wins16:17
*** zns has quit IRC16:18
*** dims has joined #heat16:18
*** piyush1 has quit IRC16:18
therveSwift temporary URLs sounds like web hooks, which several people were adamant not to use because of security concerns16:18
therveBut anyway16:18
*** ramishra has quit IRC16:19
*** andrew_plunk has joined #heat16:20
*** ramishra has joined #heat16:22
*** kfox1111 has joined #heat16:23
kfox1111so.... I have two templates. template A creates an instance. Its very generic. I have template B, which nests template A, giving it a bunch of params, so the user doesn't have to fill out a bunch of stuff to relaunch the same stack instance.16:24
kfox1111Now, here's the rub... Say I want to allow template B to attach metadata to the instance A generates, but only if they pass some metadata. Is that possible?16:25
*** chandan_kumar has joined #heat16:25
shardykfox1111: pass a parameter into template A with a default value which equals no metadata?16:26
kfox1111can I pass a metadata structure through? What happens if I pass nothing? Will it freak out if you have no value on the left hand side?16:27
shardyOh, you mean the metadata template section, not the metadata property to the Server resource16:27
shardyI'm not sure if that will work16:28
kfox1111the Nova::Server metadata map.16:28
kfox1111hmmm... This I think is another case of wanting an if. :/16:29
kfox1111and maybe a json deserializer function of some kind.16:29
*** bvandenh has joined #heat16:29
shardycan't you just pass some values as parameters which modify the content of the metadata?16:30
kfox1111so for now, I'd have to fork the template and allow passing of only one key=value in the forked template.16:30
shardywhy do you have to pass the entire structure?16:30
kfox1111hmm... but I probably cant do that either. I don't think I can use a Ref as a key...16:30
kfox1111passing the entire structure woudl be the most flexable.16:30
*** arbylee has joined #heat16:30
kfox1111the other option is two paramaters, a "metadata_key" and a "metadata_value", which would allow passing one metadata pair.16:31
shardykfox1111: maybe start a ML thread describing your use-case, then we can all have a look and either suggest a way to do it, or work out if it makes sense to enable it16:31
kfox1111but I dont think I can metadata: {{Ref: metadata_key}: {Ref: metadata_value}}16:31
kfox1111k.16:31
shardyFWIW so far we've deliberately avoided such template magic for the sake of simplicity16:32
shardybut concrete use-cases are always helpful when discussing such ideas16:32
therveYou should be able to pass the whole structure using a JSON param16:32
*** zns has joined #heat16:32
*** gokrokve_ has joined #heat16:32
therveThat's what I did right here: https://github.com/openstack/heat-templates/blob/master/hot/lb_server.yaml16:33
kfox1111therve: Really? Cool. looking...16:33
*** ramishra has quit IRC16:33
therveI didn't handle the empty case but there may be a way to make it work using defaults16:34
kfox1111hmm... so how does it work if template B is yaml?16:34
kfox1111does it take a string that it converts to json, or does it convert yaml to json?16:34
shardytherve: I thought kfox1111 was talking about the top-level metadata key, not the resource property16:34
shardytoo many overloaded meanings of metadata :(16:35
kfox1111heh. yeah.16:35
*** arbylee has quit IRC16:35
*** gokrokve has quit IRC16:36
kfox1111the only relyable definition I've ever come up with for what metadata means, is: "metadata is data that is, when viewed by a particular idividual at a particular time, is not considered important enough to be condisdered data" :)16:37
*** arbylee has joined #heat16:37
kfox1111one man's metadata is anothers data... :)16:37
*** andersonvom_ has joined #heat16:38
*** andersonvom has quit IRC16:38
*** arbylee1 has joined #heat16:38
*** jistr has quit IRC16:40
*** arbylee has quit IRC16:42
*** arbylee1 has quit IRC16:43
*** pafuent has left #heat16:44
*** zns has quit IRC16:45
*** zns has joined #heat16:46
*** pafuent has joined #heat16:47
*** jamie_h_ has joined #heat16:48
*** sorantis has joined #heat16:48
*** harlowja_away is now known as harlowja16:51
shardySpamapS: FYI the cinder tempest test I mentioned yesterday https://review.openstack.org/#/c/90143/16:51
*** jamie_h has quit IRC16:52
*** jamie_h_ has quit IRC16:54
*** shardy is now known as shardy_afk16:57
openstackgerritRob Crittenden proposed a change to openstack/python-heatclient: Heat client does not support OS_CACERT option  https://review.openstack.org/8766416:57
*** jpeeler has quit IRC16:58
*** jpeeler has joined #heat16:59
*** jpeeler has quit IRC16:59
*** jpeeler has joined #heat16:59
*** zns has quit IRC17:01
*** blues-man has quit IRC17:01
*** cdent has quit IRC17:01
*** e0ne has quit IRC17:01
*** zhiyan is now known as zhiyan_17:03
*** lindsayk has joined #heat17:03
*** Michalik- has quit IRC17:04
*** gpocentek has joined #heat17:04
openstackgerritJason Dunsmore proposed a change to openstack/heat: Rackspace::Server::SSHWaitCondition resource  https://review.openstack.org/8538617:07
*** gokrokve_ has quit IRC17:08
gpocentekhello17:10
gpocentekI'm working on a patch for the heat section of the isntallation documentation: https://review.openstack.org/#/c/90071/17:11
gpocentekI'd like to make sure I'm not completely wrong there, a review from an expert on the subject would be much appreciated :)17:12
*** derekh has quit IRC17:15
*** chandan_kumar has quit IRC17:19
*** chandan_kumar has joined #heat17:19
*** zns has joined #heat17:21
*** randallburt has quit IRC17:22
openstackgerritJason Dunsmore proposed a change to openstack/heat: API changes for param to show soft-deleted stacks  https://review.openstack.org/8864117:23
openstackgerritJason Dunsmore proposed a change to openstack/heat: Engine changes for API param to show soft-deleted stacks  https://review.openstack.org/8864217:23
*** piyush2 has quit IRC17:28
*** akuznetsov has quit IRC17:32
*** akuznetsov has joined #heat17:32
*** daneyon has quit IRC17:38
*** gokrokve has joined #heat17:40
*** andersonvom_ has quit IRC17:42
*** jprovazn has quit IRC17:47
*** zns has quit IRC17:48
*** andersonvom has joined #heat17:49
*** andersonvom has quit IRC17:49
*** mkollaro has quit IRC17:50
*** IlyaE has quit IRC17:52
*** nati_ueno has joined #heat17:52
*** zns has joined #heat17:57
*** yogesh has joined #heat17:59
*** randallburt has joined #heat17:59
*** e0ne has joined #heat18:03
*** ifarkas has quit IRC18:05
*** nati_ueno has quit IRC18:06
*** piyush1 has joined #heat18:11
*** piyush2 has joined #heat18:12
*** che-arne has quit IRC18:13
*** nati_ueno has joined #heat18:13
*** nati_ueno has quit IRC18:14
*** zns has quit IRC18:14
*** piyush1 has quit IRC18:15
*** nanjj has quit IRC18:16
openstackgerritA change was merged to openstack/heat: Add link to a resource's nested stack  https://review.openstack.org/8578118:21
*** e0ne has quit IRC18:21
*** e0ne has joined #heat18:22
*** nati_ueno has joined #heat18:22
*** Darnoth has joined #heat18:23
*** lindsayk has quit IRC18:27
*** andersonvom has joined #heat18:27
*** blamar_ has joined #heat18:29
*** blamar_ is now known as blamar18:29
*** mspreitz has joined #heat18:30
mspreitzWas there some discussion of removing tenant ID from the URLs of Heat?18:30
zanebthere was, yes18:30
mspreitzresolution?18:30
zanebprobably will happen in the v2 API18:30
mspreitzthanks18:30
*** derekh has joined #heat18:31
zanebexpect to see a design summit session on the v2 api18:31
*** ramishra has joined #heat18:34
*** zns has joined #heat18:37
*** mkollaro has joined #heat18:38
*** ramishra has quit IRC18:39
*** lindsayk has joined #heat18:42
*** andersonvom has quit IRC18:46
*** nati_ueno has quit IRC18:49
*** andersonvom has joined #heat18:50
*** sballe has quit IRC18:50
*** chandan_kumar has quit IRC18:52
*** zns has quit IRC18:54
*** zns has joined #heat18:55
*** ramishra has joined #heat18:55
*** ramishra has quit IRC19:00
*** sballe has joined #heat19:00
*** IlyaE has joined #heat19:00
*** arbylee has joined #heat19:01
openstackgerritDimitri Mazmanov proposed a change to openstack/heat: Add a Nova Flavor resource.  https://review.openstack.org/9002919:04
*** arbylee has quit IRC19:05
*** dims has quit IRC19:11
*** varora has joined #heat19:12
*** blamar has quit IRC19:12
*** andersonvom has quit IRC19:13
*** nanjj has joined #heat19:14
*** chandan_kumar has joined #heat19:16
*** cdent has joined #heat19:18
*** saurabhs has joined #heat19:20
*** bvandenh has quit IRC19:21
saurabhshey guys need some help with heat template. so I am trying to deploy Trove service with Heat-Tripleo. In my heat template, I am trying to create mysql and rabbitmq resources then specify IP of mysql and rabbit in control plane metadata. But that IP is not getting initialized correctly.19:23
saurabhshttps://github.com/saurabhsurana/tripleo-heat-templates/blob/master/trove-control-plane.yaml#L704-#L70619:23
saurabhsI always get empty string for rabbit.host19:23
*** chandan_kumar has quit IRC19:23
saurabhswhen I do 'heat resource-metadata'19:24
saurabhsit shows me:19:24
saurabhs    "rabbit": {19:24
saurabhs      ….19:24
saurabhs     "host": "",19:24
saurabhs      …..19:24
saurabhs    },19:24
*** david-lyle_ has joined #heat19:26
*** nanjj has quit IRC19:27
*** rbuilta has quit IRC19:29
*** nati_ueno has joined #heat19:30
*** piyush2 has quit IRC19:32
*** dims has joined #heat19:33
*** mspreitz has quit IRC19:35
*** varora has left #heat19:35
erecioHi everbody. I have a doubt about the AWS::EC2::SecurityGroup resource. Under this resource you have two diff properties SecurityGroupEgress and SecurityGroupIngress. Both has a property named IpProtocol and  in the AWS docs say that cant take this valid values for EC2-VPC "19:38
erecio(Ref http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-security-group-rule.html). Right now Openstack not support the value "-1" to add tcp,udp and icmp in one rule, its possible to add a BP to support this? Other solution could be add one rule for each in the template. Im new on OS and Im not sure. Thanks.19:38
*** sdague has quit IRC19:41
erecio*Both has a property named IpProtocol and  in the AWS docs say that cant take this valid values for EC2-VPC " tcp | udp | icmp or any protocol number (see Protocol Numbers).Use -1 to specify all."19:41
therveerecio, Does the VPC case mean anything in the case of openstack though?19:42
*** sdague has joined #heat19:42
ereciotherve, Sorry I dont follow you19:45
therveerecio, In AWS, the -1 value is only possible for VPC, correct?19:45
*** IlyaE has quit IRC19:46
*** varora has joined #heat19:46
*** pablosan is now known as zz_pablosan19:47
ereciotherve, Im not sure. Its under AWS::EC2::SecurityGroup. Im checking the AWS doc if mention something about -1 only in VPC19:48
*** varora has left #heat19:48
therveerecio, You just said "for EC2-VPC" yourself19:50
*** IlyaE has joined #heat19:50
ereciotherve,  Yes, i didnt realize19:51
therveerecio, Anyway, have you tried talking to the neutron folks about it?19:52
erecioits valid only vor VPC.19:52
therveIf neutron supports it heat can use it easily19:52
*** jreypo has joined #heat19:53
ereciotherve, No yet. Im not familiar with Heat so i dont know how works the parser.19:54
ereciotherve, I know that this came from Nova19:55
therveerecio, Heat is mostly a way to have a template to talk to APIs19:55
therveSo security groups APIs are exposed by either nova or neutron19:55
therveIf they support -1 in protocol, Heat will as well19:56
ereciotherve, Perfect19:56
therveIt doesn't seem like a super exciting feature though :)19:56
*** ramishra has joined #heat19:56
*** david-lyle_ has quit IRC19:56
*** piyush1 has joined #heat19:57
ereciotherve, ahah thats for sure. As i say, I can define three times the rule one for each protocol :-)19:57
therveProbably 2 because icmp is kind of seperate I think19:58
*** piyush2 has joined #heat19:58
*** ramishra has quit IRC20:01
*** piyush1 has quit IRC20:01
*** sorantis has quit IRC20:02
*** zz_pablosan is now known as pablosan20:02
*** harlowja is now known as harlowja_away20:06
ereciotherve, Thanks!20:07
therveNo problem20:08
*** sgordon has quit IRC20:29
sdake_zaneb around?20:34
zanebyep20:34
*** blomquisg has quit IRC20:34
sdake_are you going to be in the office tomorrow20:34
zanebdefine 'office' ;)20:34
sdake_sitting in your pjs in front of a laptop20:35
zanebthen yes20:35
zaneb:D20:35
*** Slower has quit IRC20:37
*** Slower has joined #heat20:38
*** nanjj has joined #heat20:39
*** derekh has quit IRC20:39
*** radez is now known as radez_g0n320:40
*** piyush2 has quit IRC20:44
*** piyush1 has joined #heat20:49
*** che-arne has joined #heat20:50
*** piyush2 has joined #heat20:51
*** jdob has quit IRC20:52
*** piyush1 has quit IRC20:53
*** Michalik- has joined #heat20:54
*** erecio has quit IRC20:55
*** cdent has quit IRC20:56
*** ramishra has joined #heat20:57
*** nanjj has quit IRC20:59
*** alexheneveld has joined #heat20:59
*** harlowja_away is now known as harlowja21:01
*** ramishra has quit IRC21:02
*** bvandenh has joined #heat21:05
*** nanjj has joined #heat21:16
*** IlyaE has quit IRC21:16
*** e0ne has quit IRC21:21
*** aweiteka has quit IRC21:22
*** pafuent has left #heat21:22
*** nanjj has quit IRC21:25
*** tspatzier has quit IRC21:31
zaneb3 slots left... 6 proposals to fit in21:32
zanebbtw I hope everyone has voted in the TC elections?21:32
*** zns has quit IRC21:33
zanebactually, 7 proposals to fit in21:33
*** nati_ueno has quit IRC21:33
zanebradix: so the conclusion is that we don't need either the autoscaling or the convergence sessions, and that lifeless's session only requires one slot?21:35
*** vijendar has quit IRC21:39
SpamapSzaneb: yes, radix should have communicated that to you yesterday.21:43
SpamapSzaneb: autoscaling, convergence, lifeless, all one session.21:43
zanebhe left a comment, I just wanted to confirm that was the meaning21:43
*** zns has joined #heat21:45
*** mspreitz has joined #heat21:48
randallburttitled "A lifeless convergence of autoscaling"21:49
*** rpothier__ has quit IRC21:50
zanebrandallburt: note to self, don't schedule that one right after lunch21:51
radix+1 :)21:51
zaneb4 proposals, 2 slots21:52
randallburtindeed zaneb. btw do we know what "day" we'll have in ATL? I noticed several of us are giving presentations during that "other" part of the conference21:52
zanebindeed we do21:52
*** e0ne has joined #heat21:52
*** derekh has joined #heat21:52
randallburtzaneb:  and that day is?21:52
zanebhaha, yes, that's the question isn't it21:53
randallburtlol21:53
* zaneb is looking for the magic link21:53
*** gondoi is now known as zz_gondoi21:53
*** IlyaE has joined #heat21:53
*** zz_gondoi is now known as gondoi21:53
*** bvandenh has quit IRC21:54
zanebrandallburt: Wednesday21:54
zanebhttps://docs.google.com/spreadsheet/ccc?key=0AmUn0hzC1InKdGNXcWlWX0FIekQxbUtvRVlnVF9IV3c&usp=drive_web#gid=521:54
randallburtzaneb:  cool, thanks!21:54
*** dims has quit IRC21:56
*** e0ne has quit IRC21:57
*** david-lyle has quit IRC21:57
*** ramishra has joined #heat21:58
*** ramishra has quit IRC22:02
*** gondoi is now known as zz_gondoi22:03
*** saurabhs has quit IRC22:05
*** dims has joined #heat22:09
*** saurabhs has joined #heat22:10
*** lindsayk has quit IRC22:11
*** lindsayk has joined #heat22:12
*** achampion has quit IRC22:15
*** e0ne has joined #heat22:16
*** e0ne_ has joined #heat22:18
*** Michalik- has quit IRC22:19
openstackgerritMike Spreitzer proposed a change to openstack/heat-templates: Worked on Fedora 20 examples in HOT  https://review.openstack.org/8852322:19
randallburtzaneb:  https://blueprints.launchpad.net/heat/+spec/dynamic-flavors and its associated implementation https://review.openstack.org/#/c/90029/ seem really questionable as a user-facing resource. I'm curious to your thoughts as the bp is approved.22:20
*** shakamunyi has quit IRC22:20
*** e0ne has quit IRC22:21
*** e0ne_ has quit IRC22:22
*** kgriffs is now known as kgriffs|afk22:23
zanebrandallburt: we discussed it (yesterday?), and my thoughts are that it's fine for /contrib and really questionable as a user-facing resource22:23
randallburtzaneb:  k. I'll review my review then22:24
*** piyush2 has quit IRC22:24
*** yogesh has quit IRC22:24
*** zns has quit IRC22:24
*** zns has joined #heat22:28
*** Michalik- has joined #heat22:30
zanebit's down to resource versioning or constraint-based selection of images for the last slot22:31
*** mspreitz has quit IRC22:35
*** andrew_plunk has quit IRC22:43
*** zns has quit IRC22:43
randallburtzaneb:  my boss will hate me, but IMO its constraint-based image selection.22:44
zanebrandallburt: too late, I already picked resource versioning ;)22:44
*** derekh has quit IRC22:45
zanebrandallburt: what I wrote in the comments was "I'm going to drop this session in the hope that Heat's role will be limited to exposing the new API when it is provided by Glance."22:45
randallburtzaneb:  maybe consolidate? I think the resource versioning will be tricky, but the constraint based selection of flavors and/or images shouldn't be too tricky/contrivercial. We could even do it with new resources instead of some sort of param constraint/lookup.22:45
sdakewe can probably have a over-beer discussion about constraint-based image selection22:45
randallburtzaneb:  but Glance does or should already, though.22:46
randallburtsdake:  fair enough.22:46
randallburtsdake:  but you buy the beer ;)22:46
zanebrandallburt: see spzala's comments on http://summit.openstack.org/cfp/details/6822:46
sdakeyou assume I have more then 25$ in my checking account randallburt :)22:46
zanebI'm ok with merging the two, though, if you think they're related22:46
randallburtsdake:  its work related. RedHat buys the beer then ;)22:46
zanebrandallburt: don't listen, he has a corporate CC ;)22:47
randallburtzaneb:  they aren't related, but I don't feel either would necessarily take a whole session.22:47
sdakeI'm pretty sure the corporate cc masters will have my head after summit22:47
*** IlyaE has quit IRC22:47
sdakedoes splitting 50/50 ever work?22:47
zanebrandallburt: the question for me is, will the same audience be interested in both?22:47
randallburtsdake:  it did for one or two session in HKG IIRC22:48
zanebother PTLs have said it is a bad idea to combine topics with different audiences22:48
sdakemight be an option - wider audience then over beer and I wont go broke :)22:48
sdakezaneb makes sense to follow their lead then22:48
*** rpothier__ has joined #heat22:48
zanebnobody knows whether to show up, and then it's disruptive as people leave part-way through22:48
randallburtzaneb:  fair point. I'm not fussed either way. I'll blame you when kebray yells at me (he's interested in a strategy around resource versioning).22:49
zanebhe's in luck at the moment I guess22:50
randallburtzaneb:  :D22:50
zanebrandallburt: I'm scheduling it last though, when everyone will be catatonic :D22:50
randallburtbut *I'm* interested in constraints-based-constraints so I'll just drink sdake's beer and be happy22:50
kebrayI"m not sure the context here, but I do occasionally fuss with randallburt, but only because he's so capable and I like the challenge even when he clearly shows me how I am wrong.22:51
randallburtzaneb:  good plan. and kebray you get your resource versioning session in ATL looks like.22:51
zanebrandallburt: I think kebray is saying he wants me to de-schedule it again ;)22:51
randallburtand don't let him fool you, he's a slave driver ;)22:52
randallburtzaneb:  no don't! I just remembered my reviews are due. (just kidding; I give kebray a hard time every chance I get because he's so easy to work with and its unsettling sometimes ;)22:52
kebrayI'm just waiting to cash in my chips randallburt .22:53
randallburtkebray:  lol, indeed.22:53
kebrayI'm going to need a big favor from you one day... I just don't know when.22:53
randallburtkebray:  I anxiously await the day.. ;)22:53
randallburtzaneb:  ok, caught up on the comments and I'm good. No more fussing from me.22:54
zanebwe have a schedule!22:58
*** ramishra has joined #heat22:58
* zaneb waits for sched.org to sync22:59
*** Michalik- has quit IRC22:59
*** m_22 has quit IRC23:02
*** ramishra has quit IRC23:03
randallburtzaneb:  congrats and thanks!23:03
zanebpleasure :)23:04
*** lifeless has quit IRC23:04
*** lifeless has joined #heat23:05
*** IlyaE has joined #heat23:05
*** alexheneveld has quit IRC23:16
*** e0ne has joined #heat23:18
*** m_22 has joined #heat23:18
*** sabeen has quit IRC23:19
*** samstav has quit IRC23:22
*** e0ne has quit IRC23:22
*** achampion has joined #heat23:22
*** sjmc7 has quit IRC23:23
*** gokrokve has quit IRC23:26
*** saurabhs has left #heat23:27
*** randallburt has quit IRC23:28
zanebyay! http://junodesignsummit.sched.org/type/heat23:33
*** IlyaE has quit IRC23:34
*** mspreitz has joined #heat23:40
*** m_22 has left #heat23:43
*** e0ne has joined #heat23:43
*** gokrokve has joined #heat23:46
spzalarandleburt: just got back on IRC. Thanks for liking the constraint-based image selection session :-) so seems like it missed by just one.23:46
spzalasdake: randleburt: I think the beer should be on me and tspatzier ;) when we discuss constraint-based image selection23:47
*** e0ne has quit IRC23:47
spzalazaneb: I have just added a new comment of my findings on Glance support for image properties.23:48
spzalazaneb: on this one, http://summit.openstack.org/cfp/details/6823:48
*** Qiming has joined #heat23:56
*** ramishra has joined #heat23:59

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