Wednesday, 2019-01-30

openstackgerritDeepak proposed openstack/heat master: Heat support for Tap-as-a-Service resources  https://review.openstack.org/58923800:01
*** sdake has quit IRC00:19
openstackgerritNakul Dahiwade proposed openstack/heat master: Support for shared services in multi region mode  https://review.openstack.org/60247300:23
*** sdake has joined #heat00:27
*** sdake has quit IRC01:19
*** sdake has joined #heat01:23
*** _fragatina has quit IRC02:05
*** _fragatina has joined #heat02:06
*** _fragatina has quit IRC02:07
openstackgerritjohjuhyun proposed openstack/heat master: Heat templates doesn't support AZ for trove cluster  https://review.openstack.org/63196802:34
*** sdake has quit IRC03:00
*** maddtux has joined #heat03:04
*** ramishra has joined #heat03:23
*** ricolin has joined #heat03:29
*** skramaja has joined #heat03:32
*** k_mouza has joined #heat04:07
*** k_mouza has quit IRC04:11
*** mikecmpbll has quit IRC04:23
*** nnsingh has joined #heat05:11
*** _fragatina has joined #heat05:23
*** _fragatina has quit IRC05:24
*** _fragatina has joined #heat05:24
*** _fragatina has quit IRC05:46
*** _fragatina has joined #heat05:46
openstackgerritMerged openstack/heat-specs master: Change openstack-dev to openstack-discuss  https://review.openstack.org/62187306:30
ricolinzaneb, around?06:55
zanebyep06:55
ricolinI got a question about the temp file design in remote stack06:55
ricolinso if we really go with create a new tempfile for each remote client call, isn't that means we will keep regenerate file each time when we creat/delete/update/check_complete?06:57
ricolinzaneb, ^^^06:59
*** radeks_ has joined #heat07:11
*** jawad_axd has joined #heat07:13
*** radeks_ has quit IRC07:17
zanebricolin: afraid so, yes07:18
*** radeks_ has joined #heat07:23
*** jawad_axd has quit IRC07:43
*** gkadam has joined #heat07:51
*** e0ne has joined #heat07:56
openstackgerritZane Bitter proposed openstack/heat master: Heat support for Tap-as-a-Service resources  https://review.openstack.org/58923807:56
*** jtomasek has joined #heat08:00
ricolin#startmeeting heat08:01
openstackMeeting started Wed Jan 30 08:01:23 2019 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: heat)"08:01
openstackThe meeting name has been set to 'heat'08:01
ricolin#topic roll call08:01
*** openstack changes topic to "roll call (Meeting topic: heat)"08:01
zanebhowdy08:02
ricolino/08:02
openstackgerritZane Bitter proposed openstack/heat master: Rename the client routines for sfc to more generic name  https://review.openstack.org/62521008:02
openstackgerritZane Bitter proposed openstack/heat master: Heat support for Tap-as-a-Service resources  https://review.openstack.org/58923808:02
ramishrahi, I won't be around for long though08:02
ricolinramishra, got it, let's get start08:03
ricolin#topic Do we have a way of tagging high-priority stories for the release?08:03
*** openstack changes topic to "Do we have a way of tagging high-priority stories for the release? (Meeting topic: heat)"08:03
ricolinzaneb, about this, how about using https://storyboard.openstack.org/#!/board/list08:04
zanebthat works, but iirc there are two ways of creating boards08:05
zanebeither adding stuff manually, or automatically using tags08:05
ricolinzaneb, any idea which might be better fit?08:06
zanebTBH I think tags is easier08:06
ramishraricolin: there is a wiki page for it;) https://wiki.openstack.org/wiki/StoryBoard/Priority08:06
ricolinSo I remember I once create a board here08:06
ricolinhttps://storyboard.openstack.org/#!/board/7108:06
zanebgood ol' board 7108:07
* ricolin try to figure out what is a working list08:09
zanebthat wiki page illustrates some annoying idealogical biases on the part of the storyboard developers08:09
zaneb"nobody does triage properly so we won't let 'em try"08:09
ricolinso shall we keep using tag `high-priority` and use that board 71?08:11
ramishrayeah, tbh I don't like it a bit. It force changes the way things used to work well08:11
zanebricolin: no, I think we should have a board for each release08:12
*** asmita has joined #heat08:12
ricolinthat can be done08:12
zaneblike "Heat Stein release" and list the stuff targeted for Stein08:12
zanebmaybe showing status in each lane like https://storyboard.openstack.org/#!/board/8 ?08:12
ricolinyes, that sounds better08:14
ricolinI guess instead say it's mid/hi/low, just list the things we need to do and see how we doing with it08:15
ricolins/instead say/instead of saying/08:16
ramishrahttps://docs.openstack.org/infra/storyboard/gui/theory.html, I think it suggest tracking stuff like trello boards (backlog, in-progess, complete etc) for releases08:16
zanebyeah, if it doesn't end up getting done then it wasn't High, and we bump it to the next release ;)08:16
ramishrarather than based on priority08:16
ricolinso let's quick brainstorm here, I think we all agree on give a release based Board/working list, so what state we should add in08:17
zaneba tag like heat-stein-target maybe?08:19
*** e0ne has quit IRC08:20
ricolinhow can we move around the state08:21
ricolinzaneb, I think the tag is good08:21
ricolinInfra team use task instead:)08:24
zanebdisadvantage of a tag is that anyone can set it, but I don't think we need to care about that08:25
ricolinzaneb, I think we can always go through the Story and see who added that tag, so it's fine IMO08:26
zanebyeah08:26
ricolinSo I need some more time to learn about how to move things around state(todo->inprogress) in a board08:27
ramishraricolin: gotta go, btw, heat-agents gate is broken. unit tests are broken with paunch I think, if someone has time to fix before I find time to check it.08:27
ricolinSo what state we need?08:27
ricolinramishra, I will go for that right after meeting and before I need to go too:)08:28
ricolinramishra, thx!08:28
*** shubham_potale_ has joined #heat08:28
zanebricolin: I think you create each lane with a different query, so e.g. under review column is is has tag heat-stein-target and status==Review08:28
ricolinzaneb, I think that's why infra team use task I assume08:29
zanebricolin: maybe. that board is waaay old. infra-cloud was decommissioned some time back08:30
ricolinzaneb, I will try to see if tag and task state can be query at the same time08:31
*** bnemec has joined #heat08:31
zanebyou can if I'm reading https://docs.openstack.org/infra/storyboard/gui/theory.html#worklists-and-boards correctly08:32
ricolinTBH, storyboard still slow08:32
zanebyup :/08:33
ricolinIs it because the server issue? or it's because the app it self?08:33
zanebso is bugzilla though08:34
zaneband launchpad wasn't great08:34
zanebI think they fixed some stuff on the server, and created some missing indexes08:34
zanebbut at the end of the day, all single-page JS apps that retrieve all their data from an API are slow08:36
zaneb*cough*Gerrit08:36
ricolinappears we can set priority to a task, but I don't know how08:36
zaneblol08:37
zanebshall we move on?08:37
ricolinyes we should08:37
ricolin#action rico will go setup Board for Stein release08:38
*** mikecmpbll has joined #heat08:38
ricolin#topic This seems like it would be a good feature for Stein08:39
*** openstack changes topic to "This seems like it would be a good feature for Stein (Meeting topic: heat)"08:39
ricolin#link https://storyboard.openstack.org/#!/story/200357908:39
zanebthis is my nomination for the first story to receive the tag for stein ;)08:40
zanebprobably not much more to say about it since ramishra already left :D08:41
ricolinI believe so:)08:41
zanebbut I think this would be a useful achievement for the release, and it's an easy review08:41
zanebnext topic :)08:42
ricolinzaneb, I always think we should improve what we doing with rollback, so agree on that08:42
*** gkadam has quit IRC08:42
ricolin#topic multi-cloud08:43
*** openstack changes topic to "multi-cloud (Meeting topic: heat)"08:43
ricolinSo just back around that idea for where to put auth info for another cloud, and what's best for tempfile08:43
*** ttsiouts has quit IRC08:44
ricolinso I know the concern about temp file08:45
*** ttsiouts has joined #heat08:45
ricolinI mean it do leave file behind if we have error else where08:45
zanebit's worse than that, it leaks a file descriptor08:46
ricolinyeah, so we must do some change08:46
*** maddtux has quit IRC08:46
ricolinI can change it to regenerate file for each remote client request08:47
ricolinbut wondering if there's any better way we can targeting here08:47
zanebI think that's the way to go. writing a tempfile is relatively cheap08:47
zanebcompared to the HTTP request, it's certainly cheap08:47
ricolinit is08:48
zanebthe only alternative i can really is is to regenerate both the tempfile *and* the context for each request. which is obviously worse08:49
ricolinzaneb, NO!08:49
*** ttsiouts has quit IRC08:49
* zaneb just thought of a nasty hack08:50
ricolinI guess we have to wait for python 3.x to be the oldest before get rid of temp file08:50
ricolinzaneb, what hack08:50
zanebwe could override _action_recorder() to create the context in there and clean it up at the end08:51
ricolinyes08:52
ricolinnasty08:52
zanebI told you so08:52
ricolina good idea, but nasty08:52
zanebso in short, a good idea08:53
ricolinI can live with that:) LOL08:54
ricolinzaneb, regarding context with auth and auth_type here https://review.openstack.org/#/c/580550/9/heat/common/context.py08:55
zanebhmm, actually that idea still sucks for getting the attributes08:56
zanebmaybe we should override node_data() to clear the context08:57
ricolinso the node date have to first check if it needs to be replaced and validate the remote authentication08:59
ricolinAlso auth and auth_type can be use in server side too, and it's not necessary be stored in clouds.yaml.09:00
*** asmita has quit IRC09:02
zanebricolin: what would that look like? where would the data come from?09:03
zanebon the server side09:04
ricolinWith WSGI, we use HTTP_X_AUTH_KEY to store password when heat/common/auth_password.py, maybe we can use it to store auth too?09:04
*** mikecmpbll has quit IRC09:06
zanebricolin: do clients do that? because if they don't it's irrelevant whether we can read it09:07
ricolinIt's not in our client design, so that's for Rest API only now09:11
*** asmita has joined #heat09:14
asmitaricolin : Hi09:15
ricolinasmita, Hi back09:15
ricolin:)09:15
zanebI don't see the point in implementing any auth method that the rest of OpenStack doesn't support09:15
*** mikecmpbll has joined #heat09:16
ricolinzaneb, I guess we can override _auth_plugin in context and move ks_loading.get_plugin_loader to remote stack too09:18
zanebthat would be less risky imho09:19
*** gfidente has joined #heat09:20
ricolinBTW let's end the meeting lol09:20
ricolin#endmeeting09:21
*** openstack changes topic to "OpenStack Heat (Logs: http://eavesdrop.openstack.org/irclogs/%23heat/)"09:21
openstackMeeting ended Wed Jan 30 09:21:25 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2019/heat.2019-01-30-08.01.html09:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2019/heat.2019-01-30-08.01.txt09:21
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2019/heat.2019-01-30-08.01.log.html09:21
*** k_mouza has joined #heat09:21
ricolinI got to go, but will be keep working on those when I'm back09:21
ricolinzaneb, ^^^09:22
zanebok, thanks ricolin!09:22
*** k_mouza has quit IRC09:22
*** k_mouza has joined #heat09:23
*** ricolin has quit IRC09:28
*** maddtux has joined #heat09:38
*** ttsiouts has joined #heat09:38
*** ramishra has quit IRC09:40
*** ramishra has joined #heat09:40
* pas-ha hi all, have a strange thing in my Heat as of Queens, wonder if it is a know issue / is there a workaround10:00
pas-hahi all, have a strange thing in my Heat as of Queens, wonder if it is a know issue / is there a workaround10:00
pas-hawe have not huge but deep enough stacks running as a base for CI, and at some occasions when the job is aborted, the stack which is in CREATE_IN_PROGRESS is attempted to be DELETEd10:01
pas-haafter that sometimes the stack is being stuck in DELETE_IN_PROGRESS, with various symptoms like the resource of nested stack is DELETE_IN_PROGRESS, but the stack show on it shows CREATE_COMPLETE or CREATE_IN_PROGRESS10:02
pas-haalso heat-engine logs contain warnings like 'Failed to stop all workers for stack ... , stack cancel is not complete'10:03
pas-haanyone seen such behavior?10:03
pas-hamost of those stuck in CREATE_IN_PROGRESS were as it seems waiting on some WaitCondition inside the nested stack10:04
pas-haI'm trying to come up with a simple enough repro for now, will keep you posted10:05
thervepas-ha: You probably have rollback enabled. Wait conditions are failing, and heat is trying to delete the stack10:09
*** e0ne has joined #heat10:18
pas-haAFAIK no10:19
*** sshnaidm has quit IRC10:19
pas-hathere's no rollback in neither create nor delete10:19
pas-habut I'll doublecheck10:20
pas-hais there a config option that sets rollback by default?10:20
pas-haI've also found that the cancel action has hard-coded number of retries and timeout between them (3 and 5s respectively) will try to unhardcode those too10:21
*** ramishra has quit IRC10:26
*** sshnaidm has joined #heat10:26
pas-hathat's the kind of descrepancy between status of nested stack as a resource vs nested stack as a stack http://paste.openstack.org/show/744240/10:35
pas-hatherve: another question - I could manually delete all the created resources and then abandon the stack, but will "stack abandon" delete all the Heat-specific resources like wait conditions?10:37
*** ramishra has joined #heat10:39
thervepas-ha: If you delete the resources you can delete the stack10:39
therveabandon probably works? No idea10:40
pas-haI'll try but for now it seems to be hanging on delete of a Heat-specific resource that I can not delete10:40
therveOkay10:41
therveI'd hope abandon wouldn't be different10:41
*** ttsiouts has quit IRC11:25
*** k_mouza_ has joined #heat11:41
*** k_mouza has quit IRC11:45
*** k_mouza_ has quit IRC11:46
*** k_mouza has joined #heat11:47
*** k_mouza has quit IRC11:47
*** k_mouza has joined #heat11:48
*** ttsiouts has joined #heat11:58
*** sdake has joined #heat12:01
*** gkadam has joined #heat12:08
*** gkadam is now known as gkadam-bmgr12:19
openstackgerritVishal Manchanda proposed openstack/heat-dashboard master: Fix gate failures by a new pycodestyle  https://review.openstack.org/63392812:21
*** k_mouza has quit IRC12:37
*** maddtux has quit IRC12:43
*** sdake has quit IRC12:43
*** sdake has joined #heat12:45
*** e0ne has quit IRC12:48
*** Ashika has joined #heat12:58
AshikaHello..When we trying to delete the stack it is going into delete_failed state and these are the errors found in heat-engine.log12:59
Ashika2019-01-30 21:37:01.086 24056 DEBUG heat.engine.stack_lock12:59
AshikaCan anyone help us in knowing what is stack_lock exactly means?13:00
*** _fragatina has quit IRC13:38
*** _fragatina has joined #heat13:38
*** e0ne has joined #heat13:46
*** ekultails has joined #heat14:00
*** jcoufal has joined #heat14:02
*** vabada_ has quit IRC14:05
*** sdake has quit IRC14:20
*** sdake has joined #heat14:34
*** k_mouza has joined #heat14:35
*** skramaja has quit IRC14:42
*** mchlumsky has joined #heat14:43
*** sdake has quit IRC14:49
*** sdake has joined #heat14:55
*** sdake has quit IRC15:11
*** k_mouza has quit IRC15:13
*** sdake has joined #heat15:13
*** gkadam-bmgr has quit IRC15:57
*** _fragatina has quit IRC16:01
*** sdake has quit IRC16:14
*** sdake has joined #heat16:22
pas-haAshika: this is DEBUG statement, what is the actual ERROR in the logs?16:23
openstackgerritMerged openstack/heat master: Rename the client routines for sfc to more generic name  https://review.openstack.org/62521016:23
openstackgerritMerged openstack/heat master: Heat support for Tap-as-a-Service resources  https://review.openstack.org/58923816:23
*** Ashika has quit IRC16:26
*** e0ne has quit IRC16:31
*** e0ne has joined #heat16:31
*** ramishra has quit IRC16:40
*** k_mouza has joined #heat16:47
*** sdake has quit IRC16:51
*** k_mouza_ has joined #heat16:57
*** k_mouza has quit IRC16:59
*** sdake has joined #heat17:00
*** radeks_ has quit IRC17:02
*** radeks_ has joined #heat17:02
*** _fragatina has joined #heat17:06
*** bnemec has quit IRC17:14
*** k_mouza_ has quit IRC17:15
*** ttsiouts has quit IRC17:18
*** e0ne has quit IRC17:31
*** mikecmpbll has quit IRC17:39
*** mikecmpbll has joined #heat18:07
*** shardy has quit IRC18:15
*** sshnaidm is now known as sshnaidm|afk18:25
*** ttsiouts has joined #heat18:28
*** ekultails has quit IRC18:33
*** e0ne has joined #heat19:06
*** ekultails has joined #heat19:11
*** e0ne has quit IRC20:05
*** sdake has quit IRC20:06
*** sdake has joined #heat20:07
*** ttsiouts has quit IRC20:11
*** e0ne has joined #heat20:17
*** e0ne has quit IRC20:19
*** ttsiouts has joined #heat20:33
*** sdake has quit IRC20:39
*** sdake has joined #heat20:42
*** sdake has quit IRC20:44
*** sdake has joined #heat20:46
*** e0ne has joined #heat20:48
*** gfidente has quit IRC20:48
*** ttsiouts has quit IRC20:49
*** ttsiouts has joined #heat20:50
*** ttsiouts has quit IRC20:53
*** ekultails has quit IRC20:57
*** sdake has quit IRC21:01
*** k_mouza has joined #heat21:02
*** sdake has joined #heat21:02
*** shubham_potale_ has quit IRC21:03
*** ekultails has joined #heat21:05
*** k_mouza has quit IRC21:06
*** e0ne has quit IRC21:18
*** radeks_ has quit IRC21:19
*** higgins has quit IRC21:25
*** higgins has joined #heat21:26
zanebpas-ha: so obviously the delete operation involves a traversal of the resource graph. when it gets to a node that has locked a resource, it will stop and wait for the resource to be unlocked again21:28
zanebin your case the CREATE_IN_PROGRESS wait condition has locked the resource21:28
zanebthis is why we have the cancel thing, it's job is to stop all of the tasks working on previous traversals, which should result in them releasing their locks on the resources21:29
zanebthe log you mentioned indicates that there are locks that still have not been released 3x5s after telling them to stop21:31
zanebthe key to the mystery is figuring out why the worker tasks are not being stopped21:32
zaneb(or if they are, why the lock is not being released)21:38
*** sdake has quit IRC21:38
*** e0ne has joined #heat21:47
*** sdake has joined #heat21:50
*** openstackgerrit has quit IRC21:50
zanebpas-ha: I can't see any obvious bugs in the code, and nothing is special about WaitCondition21:51
*** e0ne has quit IRC21:58
*** ekultails has quit IRC22:02
*** sdake has quit IRC23:01
*** sdake has joined #heat23:29
*** sdake has quit IRC23:33

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