Friday, 2015-04-24

openstackgerritMerged openstack/heat-specs: Add Python 3.4 support  https://review.openstack.org/17534000:02
*** sdake has quit IRC00:03
*** achanda has quit IRC00:07
*** pm90_ has quit IRC00:07
*** LiJiansheng has joined #heat00:19
*** xuhaiwei has joined #heat00:21
xuhaiweimorning all00:21
*** Qiming has quit IRC00:22
*** Marga_ has quit IRC00:23
*** kairat_kushaev2 has quit IRC00:33
*** Marga_ has joined #heat00:45
*** Marga_ has quit IRC00:46
*** spzala has joined #heat00:48
*** zhiwei has joined #heat00:53
*** Marga_ has joined #heat00:53
*** Marga_ has quit IRC00:54
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Enhance Manage Service with service-stack and vice-versa  https://review.openstack.org/16865801:07
openstackgerritMerged openstack/heat: Cancel nested stack updates when appropriate  https://review.openstack.org/17560601:07
*** spzala has quit IRC01:09
*** Tango has quit IRC01:11
*** Qiming has joined #heat01:14
*** Qiming_ has joined #heat01:14
*** haigang has joined #heat01:15
*** vahidh has quit IRC01:15
*** Qiming has quit IRC01:18
*** sdake has joined #heat01:22
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Scale-out and pid support for Manage Service listing  https://review.openstack.org/16865701:22
*** Qiming__ has joined #heat01:24
*** sdake_ has quit IRC01:26
*** Qiming_ has quit IRC01:28
*** serg_melikyan has joined #heat01:28
*** liusheng has joined #heat01:29
openstackgerritxu-haiwei proposed openstack/heat-specs: Multiple software configs triggered by one deployment  https://review.openstack.org/16829801:30
*** serg_melikyan has quit IRC01:32
*** Qiming__ is now known as Qiming01:34
*** erkules_ has joined #heat01:35
*** erkules has quit IRC01:38
*** Raj1 has joined #heat01:44
*** Yanyanhu has joined #heat01:45
*** Raj1 has quit IRC01:46
*** Raj1 has joined #heat01:48
*** sdake_ has joined #heat01:50
*** shardy_ has joined #heat01:50
*** shardy has quit IRC01:51
*** sdake has quit IRC01:53
*** Kennan2 is now known as Kennan01:55
*** shardy_ has quit IRC01:55
*** shardy has joined #heat01:55
Qimingshardy, so early?01:58
ramishramorning all02:01
Qimingmorning, ramishra02:01
*** Raj1 has quit IRC02:02
*** harlowja is now known as harlowja_away02:02
*** kbyrne has quit IRC02:05
*** kebray has joined #heat02:06
openstackgerritMiguel Grinberg proposed openstack/heat: Decouple trustee user from keystone_authtoken  https://review.openstack.org/17705502:08
*** KanagarajM has joined #heat02:09
openstackgerritMerged openstack/heat: Use six.iterkeys(x) instead of x.keys()  https://review.openstack.org/17629302:09
openstackgerritMerged openstack/heat: Replace dict.itervalues/dict.iteritems and use len over filter function  https://review.openstack.org/17676002:09
openstackgerritMerged openstack/heat: Update urllib/httplib/cStringIO to use six.moves  https://review.openstack.org/17676102:09
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Scale-out and pid support for Manage Service listing  https://review.openstack.org/16865702:09
*** kbyrne has joined #heat02:10
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Enhance Manage Service with service-stack and vice-versa  https://review.openstack.org/16865802:10
miguelgrinbergKanagarajM: hey, we seem to have the complete inverse schedule, we never meet02:11
KanagarajMmiguelgrinberg: hi02:11
miguelgrinbergwhat's your timezone?02:11
KanagarajMmiguelgrinberg: i'm in India UTC+5:3002:11
KanagarajMmiguelgrinberg: how about you?02:12
miguelgrinbergI'm US West Coast, it's 7pm here, and you are not even 8am there!02:12
KanagarajMyes right, its 7:45 AM.02:13
miguelgrinbergso you wanted to talk about the filtering I think?02:13
miguelgrinbergjamielennox|away: when you have a moment, could you look at https://review.openstack.org/#/c/177055/ and let me know what you think?02:14
KanagarajMyes, initially i thought that its making inconsitency with existing api02:15
openstackgerritMerged openstack/python-heatclient: Unit tests for stack actions  https://review.openstack.org/17675502:15
KanagarajMbut started to make your comments as its makes things proper02:15
miguelgrinbergKanagarajM: I think it is okay to do what you proposed for v1, but I think we should revisit when we work on v202:16
KanagarajMmiguelgrinberg: oh, i think i started to make changes and pushed some of them.02:17
KanagarajMmiguelgrinberg: for review.02:17
*** huangtianhua has joined #heat02:17
miguelgrinbergoh, I missed that. I like that better, so I'm happy that you agreed, but I do understand the argument of consistency02:18
KanagarajMmiguelgrinberg: yes. as it making the api better.02:19
miguelgrinbergKanagarajM: awesome, I'll find the updates and update my review.02:19
KanagarajMmiguelgrinberg: ok. how about making the existing rest api to avoid the inconsistency?02:21
miguelgrinbergyes, I would be okay with that for v1, then we can address filters as a whole for v2. And hopefully by that time the API-WG will have a recommendation.02:22
KanagarajMmiguelgrinberg: ok.02:23
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Search Resource Type  https://review.openstack.org/16866202:30
openstackgerritMerged openstack/python-heatclient: Add --nested-depth option to event-list  https://review.openstack.org/17396802:31
miguelgrinbergshardy: could you let me know if this seems reasonable? https://review.openstack.org/#/c/177055/.02:33
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Stack resource filtering, sorting and pagination  https://review.openstack.org/16866102:36
*** achanda has joined #heat02:37
elynnmorning02:43
*** LiJiansheng has quit IRC02:44
KanagarajMstevebaker: you are here?02:45
openstackgerritQiming Teng proposed openstack/heat: Split engine service test cases (2)  https://review.openstack.org/17675302:46
stevebakerKanagarajM: hi02:47
KanagarajMstevebaker: I updated the spec https://review.openstack.org/168662 using glob matching for resource type02:48
KanagarajMstevebaker: i assmed that in sepc, mentioning glob matching would be sufficient without specifying any matching char.02:49
KanagarajMstevebaker: kindly let me know if we need to add any specific matching chars ?02:49
stevebakerKanagarajM: we're already using a glob-style syntax for searching for pre-update hooks, so we should just use that02:50
openstackgerrithuangtianhua proposed openstack/heat: Support to generate hot template based on resource type  https://review.openstack.org/17324702:51
KanagarajMstevebaker: ok. let me have look at pre-update hook02:51
asalkeldstevebaker: https://launchpad.net/heat/+milestone/liberty-102:52
asalkeldi have just sync'd the specs and bps02:52
*** EricGonczer_ has joined #heat02:52
asalkeldfeel free to change the priorities02:52
asalkeld(a bunch of specs were approved yesterdya)02:53
stevebakerasalkeld: thanks02:54
stevebakerKanagarajM: I have made a comment on the spec02:54
KanagarajMstevebaker: sure. thanks. I will incorporate them.02:56
KanagarajMstevebaker: could you kindly review my other specs.02:57
*** EricGonczer_ has quit IRC02:57
stevebakerKanagarajM: sure02:57
*** haigang has quit IRC02:58
KanagarajMstevebaker: thanks.02:58
*** EricGonczer_ has joined #heat03:00
*** sdake has joined #heat03:00
*** sdake_ has quit IRC03:04
*** EricGonczer_ has quit IRC03:04
*** sdake_ has joined #heat03:04
*** LiJiansheng has joined #heat03:06
KanagarajMasalkeld: hi03:08
asalkeldhi03:08
*** sdake has quit IRC03:08
*** Qiming has quit IRC03:09
KanagarajMasalkeld: could you kindly review my specs :)03:09
openstackgerritDeliang Fan proposed openstack/heat: Add base url in links to Orchestration API  https://review.openstack.org/17477503:11
KanagarajMasalkeld: I tried to update the specs to avoid the tox py27 failure03:11
asalkeldKanagarajM: sure03:11
KanagarajMasalkeld: thanks.03:12
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Search Resource Type  https://review.openstack.org/16866203:18
asalkeldKanagarajM: the enable/disable one, it seems asymmetrical: disable == sys.exit, enable == set a flag in the db03:23
asalkeldsurely the disable should not actually sys.exit03:23
*** KanagarajM has quit IRC03:24
asalkeldbut be in a state that can be re-enabled03:24
*** asalkeld is now known as asalkeld_lunch03:27
*** GonZo2K has quit IRC03:31
*** Raj1 has joined #heat03:42
*** achanda has quit IRC03:44
*** Raj1 has quit IRC03:44
*** Raj1 has joined #heat03:45
*** vijayagurug has joined #heat03:49
openstackgerritMerged openstack/heat: Updated from global requirements  https://review.openstack.org/17682803:52
*** alanf-mc has quit IRC03:56
openstackgerrithuangtianhua proposed openstack/heat: Use snapshot's environment when stack restore  https://review.openstack.org/17153304:14
*** KanagarajM has joined #heat04:21
*** achanda has joined #heat04:35
*** Marga_ has joined #heat04:41
openstackgerritMerged openstack/heat: Update xrange and lambda for python3  https://review.openstack.org/17676204:43
openstackgerritEthan Lynn proposed openstack/heat: Use SHA256 instead of SHA1 for resource signature  https://review.openstack.org/17707505:03
*** Marga_ has quit IRC05:10
*** Marga_ has joined #heat05:11
*** rakesh_hs has joined #heat05:11
*** Qiming has joined #heat05:12
*** huangtianhua has quit IRC05:19
*** ygoto has joined #heat05:20
*** inc0 has joined #heat05:26
*** Tango has joined #heat05:31
inc0good morning everyone05:34
*** Marga_ has quit IRC05:36
*** Marga_ has joined #heat05:36
*** Marga_ has quit IRC05:36
*** Marga_ has joined #heat05:37
*** ananta has joined #heat05:40
anantaGood morning/afternoon05:40
*** hdd has joined #heat05:40
*** Marga_ has quit IRC05:42
*** Raj1 has quit IRC05:48
*** kebray has quit IRC05:51
*** ygoto has quit IRC05:56
*** nkhare has joined #heat05:58
*** david-ly_ has joined #heat06:01
*** david-lyle has quit IRC06:03
*** tspatzier has joined #heat06:10
openstackgerritSirushti Murugesan proposed openstack/heat: Change instances of x.next() to next(x)  https://review.openstack.org/17676306:27
openstackgerritSirushti Murugesan proposed openstack/heat: Update the rest of the code to satisfy flake8 in a py34 env  https://review.openstack.org/17676606:27
openstackgerritSirushti Murugesan proposed openstack/heat: Use six.moves.map/filter/zip  https://review.openstack.org/17676406:27
openstackgerritSirushti Murugesan proposed openstack/heat: Use six.text_type and six.reraise  https://review.openstack.org/17676506:27
*** jprovazn has joined #heat06:29
openstackgerritSirushti Murugesan proposed openstack/heat: Prevent false positives of UPDATE_COMPLETE in integration tests  https://review.openstack.org/17304506:29
openstackgerritSirushti Murugesan proposed openstack/heat: Run heat_integrationtests in parallel  https://review.openstack.org/17233906:30
*** chlong has quit IRC06:39
openstackgerritSirushti Murugesan proposed openstack/heat: Prevent false positives of UPDATE_COMPLETE in integration tests  https://review.openstack.org/17304506:40
openstackgerritSirushti Murugesan proposed openstack/heat: Don't assert against all the lb-members  https://review.openstack.org/17516206:40
openstackgerritSirushti Murugesan proposed openstack/heat: Run heat_integrationtests in parallel  https://review.openstack.org/17233906:40
openstackgerritSirushti Murugesan proposed openstack/heat: Prevent false positives of *_FAILED status  https://review.openstack.org/17516106:40
*** jtomasek has joined #heat06:54
openstackgerritKanagaraj Manickam proposed openstack/heat-specs: Enable or Disable a Heat-engine  https://review.openstack.org/16865906:57
*** sorantis has joined #heat07:06
*** coolsvap|afk is now known as coolsvap07:08
*** gcivitella has joined #heat07:08
*** coolsvap is now known as coolsvap|afk07:09
*** sdake_ has quit IRC07:20
*** Tango has quit IRC07:23
*** achanda has quit IRC07:24
*** ifarkas has joined #heat07:29
*** gcivitella has quit IRC07:31
*** gcivitella_ has joined #heat07:32
*** gcivitella_ is now known as gcivitella07:32
*** elynn has quit IRC07:33
shardymiguelgrinberg: will do, thanks for looking at it07:35
*** BManojlovic has joined #heat07:35
*** achanda has joined #heat07:36
asalkeld_lunchsirushti: patch bombs us :-O07:41
*** asalkeld_lunch is now known as asalkeld07:43
*** jistr has joined #heat07:44
*** huangtianhua has joined #heat07:48
*** alanf-mc has joined #heat07:51
*** alanf-mc_ has joined #heat07:53
*** alanf-mc has quit IRC07:56
*** achanda has quit IRC07:57
*** jcoufal has joined #heat07:57
*** alanf-mc_ has quit IRC08:00
*** jistr is now known as jistr|mtg08:09
*** zhiwei has left #heat08:20
*** yassine_ has joined #heat08:21
KanagarajMinc0: are you here?08:22
sirushtiasalkeld, heh, spammed! :)08:22
inc0KanagarajM, reporting08:23
KanagarajMinc0: you are having some concern on the enable/disable engine?08:23
inc0I'm just thinking of use case for it08:23
inc0we don't want it to be unused feature08:24
inc0and dead code08:24
KanagarajMthis blue print is for the maintanence cycle support.08:24
inc0yeah, I understand - I just don't know which part of maintenance cycle it will really solve08:25
KanagarajMduring the maintenance cycle, admin would want to disable a given engine and wants to complete all the in-progress actions for stack/resource in that engine08:25
inc0yes, but that's definiton of graceful shutdown08:25
inc0finish all your taks and then commit suicide08:26
asalkeldKanagarajM: is this a request from you company? if so it might just be worth writing down what their requirements are08:26
asalkeldalways good to write real world use down08:27
asalkeldalways good to write real world use case08:27
KanagarajMno, graceful shutdown currently does not bother for state of the resource/stack08:27
inc0it bothers about tasks running on engine08:27
inc0and when these are finished, only then we can kill our process08:28
inc0some processes can be continued on other engines (for example nested stacks)08:28
KanagarajMasalkeld: i brought it up after testing for a sample stack, which is in-pgress08:28
KanagarajM*in-progress.08:29
inc0I just want to avoid situation when we'll hold heat-engine shutdown until *other* engines finishes their tasks08:29
inc0maybe it would be better to fix graceful shutdown instead of introduce new API call08:29
inc0its far more intuitive08:30
KanagarajMthe real probel exist in the graceful shutdown and needs be fixed by this way.08:30
inc0It can be fixed in graceful shutdown as well08:31
inc0also, keep in mind that convergence will also help here08:31
inc0because it will unbind engine from stack08:31
KanagarajMand wanted to differentiate beween graceful shutdown while stopping the engine, as it might take more time to exit, if it process more stacks08:32
inc0so if we perform graceful shutdown, other engines will carry on creation of a stack08:32
inc0well, graceful shutdown has to take all the time it needs08:32
*** alexheneveld has joined #heat08:32
inc0also I don't think currenct graceful shutdown logic stops engine from taking RPC calls, and that's something that has to be fixed08:33
KanagarajMno, currently its not.08:34
*** pitr-ch has joined #heat08:34
openstackgerritSergey Kraynev proposed openstack/heat: Add scenario test for AWS loadbalancer  https://review.openstack.org/15319208:34
openstackgerritSergey Kraynev proposed openstack/heat: Add timeout hidden parameter to AWS LB  https://review.openstack.org/17712008:34
inc0then I agree that has to be fixed.08:34
inc0all I'm saying is thing you propose is critical functionality - no argument there08:34
inc0but I don't think it should be separate API08:35
inc0I think it should be graceful shutdown08:35
*** derekh has joined #heat08:35
KanagarajMok. intention was: wanted to allow the operator to abort the engine like now and at the same time, gracefully bring down. so wanted to introduce enable/disable.08:36
KanagarajMi reffered nova, on how its doing, in nova also, first they will mark the nova-compute as disabled and skip that nova-compute from scheduler further08:37
inc0I think we should check in with operators about that08:37
inc0yes, but that's difference08:37
inc0nova has computes08:37
inc0you don't mark nova scheduler as "disabled"08:37
KanagarajMand that is how they detach the nova-compute from scheduler08:37
inc0you just shut it down08:37
inc0we don't have compute agents08:37
KanagarajMno inc0, nova-compute is a proxy in case of vmare,08:38
inc0in case of vmware08:38
inc0its just one case08:38
openstackgerritSergey Kraynev proposed openstack/heat-specs: Improvements in deprecation process  https://review.openstack.org/15323508:38
inc0also real use-case for disabling copute agent is somewhat different08:38
inc0yeah, it detach nova-compute from scheduler08:39
inc0but it still takes care about virtual machines it has on compute node08:39
inc0projects notifications and so on08:39
inc0we don't have this issue - when we detach heat-engine its effectively useless08:39
openstackgerritSergey Kraynev proposed openstack/heat: Do not filter stacks if tags is empty list  https://review.openstack.org/17543608:40
*** sorantis has quit IRC08:40
KanagarajMwhen operator wants to conduct any maintenace activity on the server where heat-engine is running, he would want to first gracefully bring it down. ( i called as disable engine and you called as graceful shutdown :)08:40
KanagarajMthat problem needs to be fixed. we aggreed.08:41
inc0yes08:41
inc0I'll add that its critical problem in my opinion08:42
KanagarajMnow let us discuss on how to provide the option to operator08:42
*** alexheneveld has quit IRC08:42
inc0in my opinion we shouldn't think of "stacks in progress"08:42
inc0we should think of "tasks that this engine has to finish before it can die08:43
KanagarajMi felt that, if we given two steps 1. disable engine 2. stop all the thread and sys.exit08:43
inc0if you excuse me - daily scrum:( be back in 15minutes. Sorry08:44
KanagarajMinc0: i would like to come back to your question on how to fix it later and let us finalize on the above mentioned steps08:44
KanagarajMsure. kindly ping me back once your are back.08:44
*** ishant has joined #heat08:45
openstackgerritSteven Hardy proposed openstack/heat: Enable filtering events on event_time  https://review.openstack.org/17699008:45
KanagarajMasalkeld: sorry, i could follow up on your message. when i try to debug the issue found the need for this problem to fix.08:45
therveshardy, Do we really to enable exact match for event_time?08:47
asalkeldKanagarajM: ok08:47
openstackgerritMerged openstack/heat: Remove downgrade functions  https://review.openstack.org/17695908:47
* asalkeld watching tv ... friday evening ...08:48
shardytherve: currently there's not way to filter on time at all08:49
openstackgerritMerged openstack/heat: Change instances of x.next() to next(x)  https://review.openstack.org/17676308:49
shardytherve: I want to enable exact match, then event_time_gt and event_time_lt08:49
shardyso you can, for example, filter to only get the events since the current stack action started08:49
therveshardy, So you want to keep exact match?08:50
shardytherve: why not?08:50
shardythere's no other way to filter for a specific event either08:50
therveI don't know it seems kind of pointless08:50
shardytherve: wouldn't having the _gt and _lt versions be weird if we don't also offer an exact match though?08:51
therveshardy, Also, did you see my suggestion of using event_time_start and event_time_end?08:51
shardytherve: not yet, looking08:51
therveshardy, I just mentioned it here yesterday08:51
shardytherve: Ok, maybe I missed that, sorry08:52
shardytherve: my main requirement is to filter events only since, say, an update started08:52
therveI think exact match on time is weird by itself :)08:52
shardybut filtering on time at all seemed like the first step08:52
shardy<shrug>08:52
shardyI think our whole event filtering is weird atm08:53
therveThat's fair08:53
shardyit should be possible to filter on anything the client displays08:53
therveExact match on time depens on precision though08:53
shardyinstead, we've got some weird subset of stuff aligned with the DB schema08:54
therveWe somewhat expose db-specific stuff08:54
therveAgreed08:54
*** sorantis has joined #heat08:55
therveAnyway, no biggie08:55
openstackgerritOpenStack Proposal Bot proposed openstack/heat: Updated from global requirements  https://review.openstack.org/17712708:55
shardytherve: maybe you're right, it just seemed like a reasonable first step to me08:55
therveI don't think it's worth a 120 mail thread on api-wg08:56
shardyheh08:56
shardyI'll post the range patches later, then I guess we can decide if the exact one has merit or not08:56
shardyit's the range patches I actually need08:57
therveRight08:57
therveLike real users :)08:57
shardytherve: part of the reason I started like this, is I was thinking of having event_time take the range specification as an argument08:58
shardyit is less valuable if we're going to have a filter key for min/max gt/lt or whatver08:58
inc0I'm back, sorry08:59
* therve nods08:59
inc0KanagarajM, how about merging 2 steps together?08:59
inc0I mean note that by performing graceful shutdown heat-engine will stop accepting any new tasks09:00
inc0finish all of current tasks09:00
inc0and die09:00
*** inc0_ has joined #heat09:02
inc0_in my opinion there is no need for separate API for that - also that would make things complicated09:02
inc0_(network disconnected:()09:03
*** inc0 has quit IRC09:06
*** cody-somerville has joined #heat09:07
*** sorantis has quit IRC09:13
*** tochi has quit IRC09:16
d0ugalI'm trying to do a resource-show on a resource in a nested (tripleo) stack but failing.09:17
d0ugalCan anyone tell me how to do a resource show on the bottom entry? http://paste.openstack.org/show/205612/09:19
d0ugalI *think* that is the one causing my issues.09:19
KanagarajMinc0: fine. but if operator want to forceful exit as we do now, it might not be possible09:20
KanagarajMinc0: if we combine them in to one.09:20
*** alexheneveld has joined #heat09:21
kairat_kushaevGuys, I am wondering why do we need stack backup in general?09:21
KanagarajMinc0: i brought the api in to the picture, consider the suitiation where you have scale-out deployment and admin would want to graceful down in many numbers tehn it would make life eaiser with api09:22
kairat_kushaevI see that we using the temporary copy of stack (named oldstack) for rollback operations09:22
shardyd0ugal: have you seen my blog post on this?09:22
shardyd0ugal: you have to use the nested stack ID as the first argument to resource-show09:23
kairat_kushaevand there is a lot of problems with current backup stack implementation.09:23
shardye.g heat resource-show <nested id> <resource name>09:23
inc0_KanagarajM, if admins will want to kill service- trust me they know how to do that *right away*:), also as for scale out deployments there are tools to do that too - no need to specifically create API for that09:24
inc0_puppet ensure: stopped ;)09:24
*** bdossant has joined #heat09:25
inc0_on the other hand, we disable service...how admin will know if he can turn off his engine or he needs to wait a bit longer?09:25
*** KanagarajM_ has joined #heat09:26
*** alexheneveld has quit IRC09:26
inc0_KanagarajM_, did you get my last messages?09:26
KanagarajM_inc0: external tools are available.09:26
KanagarajM_inc0_: yes. it got disconnected09:27
inc0_I know the pain...09:27
shardyd0ugal: admittedly, it's something not super-obvious what the nested ID is, I do this:09:27
*** prazumovsky has joined #heat09:27
shardyheat resource-list --nested-depth 5 overcloud09:28
KanagarajM_inc0_, i felt that providing such functionality in heat would make admin life simpler.09:28
shardythen look for the resource and note the parent_resource09:28
KanagarajM_inc0_, yes some time really its very painful !09:28
shardythen do heat stack-list --show-nested | grep <parent_resource>09:28
shardyd0ugal: there's probably a heatclient optimization we can do to make that easier09:28
inc0_KanagarajM_, from what I know admins (I sit with them for last few years), I don't think they'll use it09:28
*** alexheneveld has joined #heat09:29
inc0_admins usually wants good tools that are common throughout services09:29
*** KanagarajM has quit IRC09:29
*** asalkeld has quit IRC09:29
KanagarajM_inc0_, yes.09:30
shardyd0ugal: in your case, the thing failing is a deployment, so I'd go straight to:09:30
inc0_graceful shutdown should work the way I've described - stop getting new tasks, finish what you're doing and die09:30
shardyheat deployment-show 4e6d2b7e-039e-46a9-a8c9-29b1e06616fa09:30
openstackgerritMerged openstack/heat: Improve StackValidationFailed response in nested  https://review.openstack.org/17049009:30
shardyhttp://hardysteven.blogspot.co.uk/2015/04/debugging-tripleo-heat-templates.html09:30
shardyas noted in there09:30
KanagarajM_inc0_: hmm. my plan was, once heat is enabled with enable/disable, then bring it CLI and horizon, which helps admin to operate from common place across services09:31
shardyd0ugal: if those notes are unclear, I'm happy to have feedback so we can improve them, working towards a debug guide doc for TripleO09:31
*** jistr|mtg is now known as jistr09:32
sirushtikairat_kushaev, yeah, in convergence, we'd simply update to an older template id for rollback -> http://specs.openstack.org/openstack/heat-specs/specs/kilo/convergence-rollback.html09:32
KanagarajM_inc0_, like nova, cinder, heat, etc. in that angle, i planned for the api and cli too.09:32
inc0_KanagarajM_, another thing;) admins don't use horizon that much:P but what I mean is - when we should actually kill heat-engine after disabling?09:32
inc0_when we can be sure we can kill process safely?09:32
*** alexheneveld has quit IRC09:34
KanagarajM_inc0_, i think after disabling admin would kill engine by stopping. its for sure.  but if we bring disable process as part of stop engine, then it would dealy to its entend.09:35
inc0_KanagarajM_, but to some indefinite moment in time09:35
kairat_kushaevsirushti: Sounds good, at the current moment we have situations when backup resources has incorrect reference when update failed09:36
inc0_if we take my approach - admin calls shutdown and forgets about whole thing09:36
inc0_it will die when it will die09:36
inc0_and heat-engine will know when to die in safe way09:36
KanagarajM_inc0_, yes, so i felt that let us give kind of forceful shutdown and graceful shutdown09:36
kairat_kushaevsirushti: Now I am trying to handle it in correct way but it seems that it is quite difficult with current approach09:37
*** sdake has joined #heat09:37
inc0_KanagarajM_, we won't need to "give" forceful shutdown09:37
inc0_kill -9 does the job perfectly09:37
KanagarajM_inc0_, that is there for sure.09:37
inc0_but we should give way to shut down gracefully09:38
inc0_but I think we don't need to give 2 different ways09:38
KanagarajM_inc0_, sure we will give it. but we can't mark the engines are in disabled mode, which is required during maintanence.09:39
*** sdake_ has joined #heat09:39
KanagarajM_that was the another intention of this blueprint. which will clearly differentiate engines from acitve engines.09:39
inc0_KanagarajM_, I don't think it is. I can't think of any case when we want heat-engine to be working and not accepting RPC tasks09:39
inc0_besides graceful shutdown09:39
inc0_KanagarajM_, killing engine will differentiate them from alive ones;)09:40
KanagarajM_once its shutdowned, we should not allow to start when its marked with disabled like other services09:40
inc0_KanagarajM_, why would you want that?09:40
*** alexheneveld_ has joined #heat09:40
*** sorantis has joined #heat09:41
KanagarajM_inc0_, assume in scale-out environment, may heat-engines will be running, and admin would have killed some of them for maintanence purpose.09:41
inc0_yup, other engines takes on tasks09:42
KanagarajM_inc0_, now admin should have way to findout those engines are marked for maintanence09:42
inc0_I don't think we need to provide API for that...09:42
inc0_admins usually take on whole host for maintenance at once09:43
*** sdake has quit IRC09:43
inc0_whole controllers, they will know that its in maintenance without heat help09:43
*** alexheneveld has joined #heat09:44
*** jprovazn has quit IRC09:45
KanagarajM_inc0_, but if we provide cli at the minimum (or api to the max) it would help admin to figure it out from heat itself09:45
*** alexheneveld__ has joined #heat09:45
*** alexheneveld_ has quit IRC09:45
inc0_KanagarajM_, again, I don't think anyone will use it really09:45
KanagarajM_inc0_, as a first step nova-manage command would serve. second, to bring it external consumption heat cli/api would server09:45
inc0_this way09:45
inc0_please, rethink enhancing graceful shutdown instead09:47
KanagarajM_inc0_, graceful shoutdown we agreed up on i guess.09:48
inc0_yeah, and I think it will be enough09:48
*** Marga_ has joined #heat09:48
inc0_to provide one solution, but robust09:48
*** alexheneveld has quit IRC09:48
*** alexheneveld__ is now known as alexheneveld09:48
*** Marga_ has quit IRC09:50
KanagarajM_inc0_, my only botheration is, when admin uses maintance mode in nova, why not admin expect from heat09:50
inc0_because we dont have heat-compute09:50
*** Marga_ has joined #heat09:50
inc0_don't think of "disable" on nova09:50
inc0_nova has several services09:51
inc0_you don't disable nova-scheduler09:51
inc0_heat-engine is closer to nova-scheduler than to nova-compute09:51
inc0_also heat doesn't have any compute node agent09:52
KanagarajM_inc0_, i visualise heat-engine is simliar to nova-compute in terms of task its does. because nova-compute also takes RPC request and process it and talk to its backend and completes operation. like heat-engine does with resource plug-ins as backends.09:55
inc0_KanagarajM_, no, its nothing like it. Heat-engine is controller node service while nova-compute is compute node service09:56
inc0_you have 6 controller nodes for 150 compute nodes09:56
*** cdent has joined #heat09:57
KanagarajM_inc0_, here 150 is hypervisors, i assume09:57
inc0_yeah, another word for that09:57
inc0_(I don't like this word in relation to servers, because hypervisor is software, qemu or so...but I digress)09:58
KanagarajM_inc0_, no. for vmware, we can have one nova-compute for more than one vmware compute (cluster)09:58
inc0_I know09:58
inc0_but from openstack perspective its still compute node just the same09:58
KanagarajM_inc0_, yes. i am saying that one nova-compute could act for more than one compute node in case of vmware.09:59
KanagarajM_inc0_, ok. let us conclude on what we wanted to do on this blueprint10:00
KanagarajM_inc0_, 1. do the graceful shutdown.10:00
KanagarajM_inc0_, 2. maintenance mode for engine, at this moment, i will strop off from the blueprint10:01
inc0_if you'll do bp for graceful shutdown - you have +1 from me and I would very much like to help as well:)10:02
inc0_this is very important feature for us10:03
KanagarajM_inc0_, :) thanks10:03
inc0_thank yoy10:03
inc0_you10:03
KanagarajM_np.10:05
*** alexheneveld has quit IRC10:05
*** Marga_ has quit IRC10:06
openstackgerritRabi Mishra proposed openstack/heat: Add min_adjustment_step property to ScalingPolicy  https://review.openstack.org/17714810:07
*** alexheneveld has joined #heat10:07
*** alexheneveld_ has joined #heat10:10
openstackgerritRabi Mishra proposed openstack/heat: Add min_adjustment_step property to ScalingPolicy  https://review.openstack.org/17714810:10
*** sorantis has quit IRC10:12
*** alexheneveld has quit IRC10:12
*** Qiming has quit IRC10:13
*** alexheneveld has joined #heat10:14
*** serg_melikyan has joined #heat10:15
*** alexheneveld_ has quit IRC10:16
*** alexheneveld_ has joined #heat10:17
*** inc0_ has quit IRC10:18
*** alexheneveld has quit IRC10:19
*** strictlyb is now known as sb10:21
*** inc0 has joined #heat10:21
*** alexheneveld has joined #heat10:21
openstackgerritPeter Razumovsky proposed openstack/python-heatclient: Move usage methods *_request to get/post/etc  https://review.openstack.org/17540310:21
openstackgerritPeter Razumovsky proposed openstack/python-heatclient: Move SessionClient from HTTPClient to adapter  https://review.openstack.org/16348410:21
*** alexheneveld_ has quit IRC10:23
openstackgerritRabi Mishra proposed openstack/heat-templates: Add tests and example template for atomic hook  https://review.openstack.org/16664310:24
*** alexheneveld has quit IRC10:26
openstackgerrithuangtianhua proposed openstack/heat: Stop snapshot creation checking if image in DELETED  https://review.openstack.org/17715610:27
*** alexheneveld has joined #heat10:27
*** alexheneveld_ has joined #heat10:28
d0ugalshardy: Just reading back - sorry was in a meeting10:29
d0ugalshadower: I did read your post, but I guess I miss-understood something. Trying again with the above.10:29
*** inc0 has quit IRC10:31
shardyd0ugal: np, feel free to let me know if I've insufficiently described something10:31
shardyd0ugal: the blog post was something of a brain-dump, but hopefully still useful10:31
*** alexheneveld has quit IRC10:32
*** alexheneveld has joined #heat10:33
*** alexheneveld_ has quit IRC10:33
shardyd0ugal: the deployment-show is the real time-saver, as you don't need to care about either the nested stack id, or sshing into nodes looking at logs10:33
d0ugalaha10:34
d0ugalshardy: just checked my history, looks like I pasted the wrong ID10:34
d0ugal... multiple times :/10:35
shardyd0ugal: aha!10:35
shardyeasily done ;)10:35
d0ugalshardy: I have an error to trace down now, thanks!10:35
shardynp10:35
d0ugalshadower: Your post has been very useful btw, helped me out a few times already.10:35
shardyd0ugal: that's good to hear - I'm planning a follow-up with a decomposition of tripleo-heat-templates, explaining the abstractions10:36
d0ugalSounds great10:36
*** alexheneveld_ has joined #heat10:36
openstackgerritMerged openstack/heat: Use six.moves.map/filter/zip  https://review.openstack.org/17676410:37
*** alexheneveld has quit IRC10:37
*** sorantis has joined #heat10:40
*** alexheneveld_ has quit IRC10:41
*** alexheneveld has joined #heat10:43
*** alexheneveld_ has joined #heat10:47
*** alexheneveld has quit IRC10:48
*** alexheneveld_ is now known as alexheneveld10:48
*** serg_melikyan has quit IRC10:49
openstackgerritSergey Kraynev proposed openstack/heat: Add scenario test for AWS loadbalancer  https://review.openstack.org/15319210:50
*** alexheneveld_ has joined #heat10:51
*** alexheneveld has quit IRC10:52
*** sdake_ has quit IRC10:53
*** alexheneveld has joined #heat10:54
*** alexheneveld__ has joined #heat10:55
*** alexheneveld_ has quit IRC10:55
*** alexheneveld_ has joined #heat10:56
*** alexheneveld has quit IRC10:59
*** alexheneveld__ has quit IRC11:00
*** alexheneveld_ has quit IRC11:01
*** nkhare_ has joined #heat11:02
*** nkhare has quit IRC11:04
*** ananta_ has joined #heat11:09
*** hdd has quit IRC11:10
*** unmeshg has joined #heat11:11
*** ananta has quit IRC11:13
*** unmeshg has left #heat11:13
*** hdd has joined #heat11:15
*** alexpilotti has joined #heat11:18
*** cdent has quit IRC11:20
*** DaveJ__ has joined #heat11:27
*** inc0 has joined #heat11:28
*** Yanyanhu has quit IRC11:29
*** inc0 has quit IRC11:33
*** inc0_ has joined #heat11:33
*** huangtianhua has quit IRC11:35
*** serg_melikyan has joined #heat11:39
*** Marga_ has joined #heat11:41
*** inc0_ has quit IRC11:44
therveshardy, You don't happen to be core on os-collect-config?11:44
openstackgerritPeter Razumovsky proposed openstack/heat: Add parameters types table to docs  https://review.openstack.org/17718911:44
shardytherve: No, unfortunately I'm not11:45
therveNo worries :)11:45
*** inc0 has joined #heat11:46
openstackgerritMerged openstack/heat: Updated from global requirements  https://review.openstack.org/17712711:47
*** nkhare_ has quit IRC11:49
*** pitr-ch has quit IRC11:50
*** inc0 has quit IRC11:51
*** funzo has joined #heat11:51
*** Marga_ has quit IRC11:57
*** hdd has quit IRC12:00
*** EmilienM has quit IRC12:01
*** EmilienM has joined #heat12:01
*** ishant has quit IRC12:07
*** erkules_ is now known as erkules12:11
*** erkules has joined #heat12:11
*** hdd has joined #heat12:11
*** vijayagurug has left #heat12:14
*** hdd has quit IRC12:25
openstackgerritPeter Razumovsky proposed openstack/python-heatclient: Move usage methods *_request to get/post/etc  https://review.openstack.org/17540312:28
openstackgerritPeter Razumovsky proposed openstack/python-heatclient: Move SessionClient from HTTPClient to adapter  https://review.openstack.org/16348412:28
*** rpothier has joined #heat12:33
*** serg_melikyan has quit IRC12:34
*** sorantis has quit IRC12:34
*** serg_melikyan has joined #heat12:50
*** LiJiansheng has quit IRC12:51
*** yassine_ has quit IRC12:56
openstackgerritOpenStack Proposal Bot proposed openstack/heat: Updated from global requirements  https://review.openstack.org/17723012:57
*** yassine has joined #heat12:59
*** funzo has quit IRC13:01
*** rakesh_hs has quit IRC13:02
*** saju_m has joined #heat13:05
*** radez_g0n3 is now known as radez13:07
*** alexheneveld has joined #heat13:13
*** alexheneveld_ has joined #heat13:16
*** sb has quit IRC13:17
*** strictlyb has joined #heat13:17
*** alexheneveld has quit IRC13:18
*** alexheneveld_ is now known as alexheneveld13:18
*** dyasny has joined #heat13:25
*** alexheneveld has quit IRC13:27
*** prazumovsky has quit IRC13:27
*** jmckind has joined #heat13:38
*** smccully has quit IRC13:48
*** smccully has joined #heat13:49
*** jasond has joined #heat13:54
*** pitr-ch has joined #heat13:55
*** Qiming has joined #heat13:56
*** KanagarajM has joined #heat14:00
*** alex_xu has quit IRC14:03
*** yuntong has quit IRC14:03
*** KanagarajM_ has quit IRC14:04
*** signed8bit has joined #heat14:04
*** KanagarajM has quit IRC14:05
*** serg_melikyan has quit IRC14:11
*** jdandrea has quit IRC14:14
*** alex_xu has joined #heat14:14
*** serg_melikyan has joined #heat14:16
*** yuntong has joined #heat14:17
*** EricGonczer_ has joined #heat14:17
*** hydr0gen has quit IRC14:18
*** MasterPiece has joined #heat14:19
*** serg_melikyan has quit IRC14:19
*** jdandrea has joined #heat14:21
*** vijendar has joined #heat14:22
*** saju_m has quit IRC14:23
*** hdd has joined #heat14:25
*** ananta_ has quit IRC14:26
*** serg_melikyan has joined #heat14:32
*** serg_melikyan has quit IRC14:48
*** Tango has joined #heat14:48
*** Marga_ has joined #heat14:50
*** serg_melikyan has joined #heat14:50
openstackgerritKairat Kushaev proposed openstack/heat: Prohibit backup of failed resources  https://review.openstack.org/17586814:51
*** tspatzier has quit IRC14:51
*** kebray has joined #heat14:53
*** Drago has quit IRC14:54
openstackgerritKairat Kushaev proposed openstack/heat: Prohibit backup of failed resources  https://review.openstack.org/17586814:55
*** Drago has joined #heat14:55
*** sabeen has joined #heat14:55
*** jmckind has quit IRC14:56
*** pm90_ has joined #heat14:58
*** pm90_ has quit IRC14:58
*** jmckind has joined #heat14:59
*** pm90_ has joined #heat14:59
jdandreaI'm creating an installer for some Heat Resource Plugins. I want to add a conf group/options for it. Normally I've used heat.conf and oslo.config. Is this considered acceptable, or should they be elsewhere? (Presuming I'd add my groups/options using register_group/opt.)15:00
*** achanda has joined #heat15:03
*** ifarkas has quit IRC15:04
*** Raj1 has joined #heat15:04
*** Raj1 has quit IRC15:05
*** Raj1 has joined #heat15:06
*** BManojlovic has quit IRC15:06
*** achanda has quit IRC15:08
*** elynn has joined #heat15:10
*** sabeen3 has joined #heat15:14
*** jasond has quit IRC15:14
*** blomquisg has quit IRC15:15
*** sabeen has quit IRC15:15
openstackgerritTetiana Lashchova proposed openstack/heat: Add remaining_executions attribute to OS::Mistral::CronTrigger  https://review.openstack.org/17730815:19
*** blomquisg has joined #heat15:19
*** david-ly_ is now known as david-lyle15:22
*** jasond has joined #heat15:23
*** jasond has left #heat15:26
openstackgerritJiri Stransky proposed openstack/heat-templates: Ensure Puppet can run even on PoC net setups  https://review.openstack.org/17731715:28
*** cody-somerville has quit IRC15:29
openstackgerritTetiana Lashchova proposed openstack/heat: Use list over six.iterkeys()  https://review.openstack.org/17731815:32
*** jasond has joined #heat15:36
*** cody-somerville has joined #heat15:40
*** EricGonczer_ has quit IRC15:42
*** cdent has joined #heat15:45
*** Marga_ has quit IRC15:45
*** cody-somerville has quit IRC15:48
*** sdake has joined #heat15:51
*** Marga_ has joined #heat15:55
openstackgerritMerged openstack/heat: Use SHA256 instead of SHA1 for resource signature  https://review.openstack.org/17707515:58
*** Raj1 has quit IRC15:58
*** Raj1 has joined #heat16:02
*** smccully has quit IRC16:08
*** bdossant has quit IRC16:09
*** serg_melikyan has quit IRC16:11
*** smccully has joined #heat16:12
*** serg_melikyan has joined #heat16:16
*** Qiming has quit IRC16:18
*** serg_melikyan has quit IRC16:20
*** MasterPiece has quit IRC16:21
*** pm90_ has quit IRC16:28
*** Raj1 has quit IRC16:29
*** jcoufal has quit IRC16:31
*** jcoufal has joined #heat16:33
*** jcoufal has quit IRC16:36
*** jistr has quit IRC16:36
*** saju_m has joined #heat16:42
*** derekh has quit IRC16:48
*** achanda has joined #heat16:52
*** sdake has quit IRC16:53
*** alanf-mc has joined #heat16:53
*** bnemec is now known as beekneemech16:54
*** pm90_ has joined #heat16:59
*** pm90_ has quit IRC17:01
*** pm90_ has joined #heat17:01
*** pm90_ has quit IRC17:02
*** pm90_ has joined #heat17:03
openstackgerritRabi Mishra proposed openstack/heat: Add min_adjustment_step property to ScalingPolicy  https://review.openstack.org/17714817:06
*** sdake has joined #heat17:12
*** Grace1 has joined #heat17:17
Grace1Hello I tried to launch a windows instance using heat template, and the script is written using powershell17:17
*** GonZo2K has joined #heat17:18
Grace1I can run the powershell script directly from powershell command prompt, but failed to run from userdata17:18
Grace1the script is:17:18
*** GonZo2K has quit IRC17:18
*** GonZo2K has joined #heat17:18
Grace1$allsnapshot=$testcode1  -split "<a\s+" | select-string "(?<=\>)(\d+)(.*)SNAPSHOT(?=\/\<)" -allmatches | % { $_.matches } | % { $_.value }  |get-unique |sort -descending17:18
Grace1the error is:17:18
Grace1 $allsnapshot=$testcode1 -split "<a\s+" |="" select-string="" "(?&lt;="\&gt;" &lt;&lt;&lt;&lt;="" )(\d+)(.<="" p="">  *)SNAPSHOT(?=\/\<)" -allmatches | % { $.matches } | % { $.value } |get-uniqu  e |sort -descending  + CategoryInfo          : ObjectNotFound: (?<=\>:String) [], CommandNotFou  ndException  + FullyQualifiedErrorId : CommandNotFoundException17:19
Grace1I tried single quotes, but still failed17:19
*** EricGonczer_ has joined #heat17:19
*** EricGonc_ has joined #heat17:21
Grace1so could anybody tell me how to solve this?17:21
Grace1Thanks so much17:21
*** MasterPiece has joined #heat17:22
*** EricGonczer_ has quit IRC17:24
Grace1the script is: $allsnapshot=$testcode1  -split "<a\s+" | select-string "(?<=\>)(\d+)(.*)SNAPSHOT(?=\/\<)" -allmatches | % { $_.matches } | % { $_.value }  |get-unique |sort -descending17:28
Grace1I think it's caused by the special charcter when parsing by python17:30
Grace1but I don't know how to correct17:30
openstackgerritMerged openstack/heat: Add parameters types table to docs  https://review.openstack.org/17718917:30
*** cdent has quit IRC17:30
ryansbGrace1: you're sending the user data as part of your heat template, yes?17:31
Grace1yes17:35
ryansbhere's an example of safely encoding that command in yaml http://da.gd/Vyguj17:36
Grace1the complete error is:17:36
Grace1execute_user_data_script C:\Program Files (x86)\Cloudbase Solutions\Cloudbase-Init\Python27\lib\site-packages\cloudbaseinit\plugins\windows\userdatautils.py:58 2015-04-24 01:31:59.765 1632 DEBUG cloudbaseinit.plugins.windows.userdatautils [-] User_data stderr: The term '?<=\>' is not recognized as the name of a cmdlet, function, script fi  le, or operable program. Check the spelling of the name, or if a path was inclu  ded, verify that17:36
ryansbtry testing out your yaml here http://yaml-online-parser.appspot.com/ to make sure it's working properly17:36
Grace1i see. thanks a lot17:37
ryansbthat online yaml parser (or you can get local ones, or DIY in a python shell) helps a lot with template authoring17:38
Grace1I knows little about python, I think this is caused by special character in python17:38
Grace1but struggling to fix it17:39
*** cody-somerville has joined #heat17:47
*** cody-somerville has quit IRC17:47
*** cody-somerville has joined #heat17:47
openstackgerritRyan Brown proposed openstack/heat-specs: Add ASG batch hook proposal  https://review.openstack.org/17172417:50
*** harlowja_away is now known as harlowja17:51
*** vijayagurug has joined #heat17:51
*** Marga_ has quit IRC17:56
*** jmckind has quit IRC17:57
*** gcivitella has quit IRC18:04
*** yassine has quit IRC18:06
*** vijayagurug has left #heat18:08
*** Raj3 has joined #heat18:22
*** Marga_ has joined #heat18:26
*** Raj3 has quit IRC18:29
*** Raj3 has joined #heat18:29
*** kebray has quit IRC18:35
openstackgerritMiguel Grinberg proposed openstack/heat: Decouple trustee user from keystone_authtoken  https://review.openstack.org/17705518:38
*** cody-somerville has quit IRC18:40
*** signed8bit is now known as signed8bit_ZZZzz18:43
*** jtomasek has quit IRC18:46
*** saju_m has quit IRC18:59
*** spzala has joined #heat19:03
*** hdd has quit IRC19:13
*** DaveJ__ has quit IRC19:21
*** dprince has joined #heat19:28
*** signed8bit_ZZZzz is now known as signed8bit19:28
dprincezaneb: hi, remind me, is there a way to disable nested stack validation?19:29
* dprince thought he remembered there was...19:29
*** kebray has joined #heat19:31
openstackgerritMerged openstack/heat: Do not filter stacks if tags is empty list  https://review.openstack.org/17543619:41
*** pm90_ has quit IRC20:00
*** jdob has quit IRC20:03
*** yassine has joined #heat20:03
*** serg_melikyan has joined #heat20:08
zanebdprince: nope, don't think so20:09
dprincezaneb: so I found my issue. I had an empty param_defaults section and apparently that fails validations.20:10
dprincezaneb: removing the empty section fixed it20:10
*** Raj3 has quit IRC20:10
zanebkk :)20:10
dprincezaneb: I think strict validation is automatically off for nested stacks by default20:10
dprincezaneb: no need to mess w/ that from what I can tell20:10
stevebakershardy: yes, I talked to dprince. I suggested an out-of-tree resource plugin which subclasses OS::Neutron::Port20:15
dprincestevebaker: hi20:15
stevebakerdprince: hi20:15
dprincestevebaker: hey, so I figured out a way to just use normal Heat resources for all this20:15
stevebakerdprince: oh yeah?>20:15
dprincestevebaker: http://fpaste.org/215303/14299066/20:16
dprincestevebaker: your suggestion to extend Neutron::Port got me thinking... why not neutron20:17
*** blomquisg has quit IRC20:17
*** dyasny has quit IRC20:17
dprincestevebaker: so what I'm trying is just creating a provider network for neutron, which is like an external entity20:17
dprincestevebaker: which basically just provides us IPAM (ip management)20:18
dprincestevebaker: this avoids the clunky 'index' variable stuff we had tried to use to generate IPs from the cidr20:18
dprincestevebaker: it will require a good bit of nested stackification... but I think it'll fly20:19
stevebakerdprince: so how do you choose an IP to assign?20:19
stevebakerdprince: one network per port?20:19
dprincestevebaker: no, that was just a quick example20:19
stevebakersorry, that was 2 different questions20:19
dprincestevebaker: there are two peices to this. One is the network architecture20:20
dprincestevebaker: so for example a physical network architecture might have 4-6 networks in it or something20:20
dprincestevebaker: and then each server would get a port on each of those networks20:20
dprincestevebaker: the idea is I can use the resource registry to enable/disable these things20:21
*** pm90_ has joined #heat20:22
*** pm90_ has quit IRC20:22
dprincestevebaker: so you'd have a network arch resource, and then you'd have a resource for the servers nested stack which would plug in to allow it to get IPs (these aren't actually attached to the server as far has Heat is concerned).20:22
stevebakersounds nice and clean20:22
dprincestevebaker: well, it is a step in the right direction I think20:23
*** pm90_ has joined #heat20:23
stevebakerdprince: so you don't care that a server has a specific IP, just that it is in the desired network?20:23
dprincestevebaker: for the most part yes. We also have a couple Virtual IPs we'll need to generate. And the network arch would effect the nets those go on. I care about where those go but there are only a few and the virtual IPs are sort of top level resources anyways so we know how to deal w/ them.20:24
*** blomquisg has joined #heat20:25
dprincestevebaker: but in general just having servers be on the right network is what we need.20:26
stevebakergood stuff20:26
dprincestevebaker: I'm optimistic... but I'll probably hit some crushing road block this weekend and come ask you some questions early next week20:27
stevebakerdprince: sure, no problem20:27
*** Raj3 has joined #heat20:34
*** Raj3 has quit IRC20:37
*** Raj3 has joined #heat20:38
*** alexheneveld has joined #heat20:38
*** Raj3 has quit IRC20:42
*** ashishjain has joined #heat20:45
ashishjainHello20:45
*** yassine has quit IRC20:47
ashishjainhello I got a question on heat autoscaling20:48
ashishjainSay for example if I deploy a heat stack which would autoscale to max 3 instances and initial size 1 is 1 instance20:50
ashishjainNow this 1 instance has got a high CPU_UTIL which crosses the threshold, so one more instance will be instantiated20:50
ashishjainnow how will the 3 instance be auto deployed -20:50
ashishjain1) Will it be if CPU_UTIL for instance 1 still remains high and above the threshold20:50
ashishjain2) Will it be if CPU_UTIL for instance 2 goes above threshold20:50
ashishjain3) or Will it if CPU_UTIL average of instance 1 +2 goes above threshold20:51
ashishjaincan someone throw some light on this20:51
*** Raj3 has joined #heat20:53
*** spzala has quit IRC20:56
*** ashishjain has quit IRC20:59
*** htruta has quit IRC21:01
*** sdake_ has joined #heat21:04
*** Raj3 has quit IRC21:08
*** sdake has quit IRC21:08
*** serg_melikyan has quit IRC21:12
*** sdake has joined #heat21:19
*** serg_melikyan has joined #heat21:22
*** EricGonc_ has quit IRC21:23
*** sdake_ has quit IRC21:23
*** Marga_ has quit IRC21:23
*** serg_melikyan has quit IRC21:34
*** radez is now known as radez_g0n321:36
*** jasond has quit IRC21:36
*** signed8bit has quit IRC21:40
*** hdd has joined #heat21:46
openstackgerritMiguel Grinberg proposed openstack/heat: Decouple trustee user from keystone_authtoken  https://review.openstack.org/17705521:47
*** smccully has quit IRC21:52
*** pm90_ has quit IRC21:53
*** vijendar has quit IRC21:55
*** hdd has quit IRC22:04
*** rpothier has quit IRC22:09
*** sdake_ has joined #heat22:11
*** Kennan2 has joined #heat22:12
*** Kennan has quit IRC22:12
*** Marga_ has joined #heat22:13
*** sdake has quit IRC22:15
*** sdake has joined #heat22:23
*** sdake_ has quit IRC22:27
*** dprince has quit IRC22:28
*** Drago has quit IRC22:28
*** kfox1111 has joined #heat22:31
kfox1111It there a test framework yet for launching a heat template and ensuring it "completes"?22:31
kfox1111not mocked up or anything, I mean really testing the template itself on a real cloud.22:31
*** harlowja_ has joined #heat22:41
*** harlowja has quit IRC22:41
*** sdake_ has joined #heat22:53
*** achanda has quit IRC22:53
*** sdake__ has joined #heat22:55
*** sdake has quit IRC22:56
openstackgerritPavlo Shchelokovskyy proposed openstack/heat: Do not pass around rich objects in Trove resources  https://review.openstack.org/17748122:57
*** sdake_ has quit IRC22:59
openstackgerritPavlo Shchelokovskyy proposed openstack/heat: Do not pass rich objects in Zaqar Queue  https://review.openstack.org/17748823:14
*** Grace1 has quit IRC23:16
*** kebray has quit IRC23:44
*** sdake__ has quit IRC23:52
*** achanda has joined #heat23:53
*** sabeen3 has quit IRC23:58
*** achanda has quit IRC23:59
*** shardy_ has joined #heat23:59

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