Tuesday, 2015-06-30

*** dsneddon has joined #heat00:03
*** sdake has quit IRC00:07
*** dims has joined #heat00:12
*** steveg_afk has joined #heat00:16
*** blomquisg has joined #heat00:18
*** boris-42 has joined #heat00:30
*** steveg_afk has quit IRC00:32
*** pm90_ has quit IRC00:44
*** sthillma has quit IRC00:53
*** randallburt has quit IRC01:09
*** Drago has joined #heat01:11
openstackgerritAngus Salkeld proposed openstack/heat: Convergence: Correct the class name EngineListener  https://review.openstack.org/19653101:12
*** Drago has quit IRC01:13
*** Drago has joined #heat01:13
openstackgerritAngus Salkeld proposed openstack/heat: Convergence: Fix stack status_reason  https://review.openstack.org/19653301:16
*** Qiming has joined #heat01:29
*** Qiming_ has joined #heat01:30
*** Qiming has quit IRC01:34
openstackgerritRico Lin proposed openstack/heat: support list resources with details  https://review.openstack.org/19657101:35
*** Qiming_ is now known as Qiming01:35
*** tobe has joined #heat01:38
*** LiJiansheng has joined #heat01:39
*** tobe has quit IRC01:39
*** Marga_ has joined #heat01:45
*** steveg_afk has joined #heat01:48
*** Marga_ has quit IRC01:48
*** Marga_ has joined #heat01:49
*** erkules has quit IRC01:52
*** erkules_ has joined #heat01:52
*** elynn has joined #heat01:58
*** Yanyanhu has joined #heat01:59
*** EricGonczer_ has joined #heat01:59
*** Slower has quit IRC01:59
*** elynn has quit IRC02:06
*** elynn has joined #heat02:08
*** chlong_ has joined #heat02:08
*** chlong__ has joined #heat02:10
elynnmorning all :)02:10
*** chlong_ has quit IRC02:13
*** ananta_ has joined #heat02:14
ananta_good morning02:15
*** tobe has joined #heat02:16
asalkeldo/02:21
*** ananta_ has quit IRC02:26
openstackgerritRico Lin proposed openstack/heat: support list resources with details  https://review.openstack.org/19657102:27
*** EricGonczer_ has quit IRC02:27
*** chlong_ has joined #heat02:28
openstackgerritRico Lin proposed openstack/heat: support list resources with details  https://review.openstack.org/19657102:30
*** steveg_afk has quit IRC02:30
*** chlong__ has quit IRC02:31
*** chlong has joined #heat02:31
*** chlong_ has quit IRC02:34
*** mwheckmann has joined #heat02:37
*** elynn_ has joined #heat02:37
*** elynn has quit IRC02:37
*** mwheckmann has quit IRC02:46
*** fbo_ has quit IRC02:48
openstackgerritMerged openstack/heat: Fix config generator for oslo.service  https://review.openstack.org/19636702:48
*** ananta_ has joined #heat02:50
*** kebray has joined #heat02:51
ananta_asalkeld: there are few patches required for convergence rollback to work properly02:51
*** fbo has joined #heat02:51
asalkeldok02:51
asalkeldwhich reviews?02:51
ananta_https://review.openstack.org/#/c/196619/ and https://review.openstack.org/#/c/196536/02:52
asalkeldananta_: i think i am heading to the conclusion that the convergence-unit-test-framework thing is starting to be a very high priority02:52
asalkeldit's just not easy to test otherwise02:53
ananta_asalkeld: yes and Ishant Tyagi have started on it :)02:54
asalkeldananta_: i don't see any logical change here https://review.openstack.org/#/c/196619/1/heat/engine/stack.py02:54
asalkeld(is it just the test cases?)02:54
ananta_asalkeld: no, the break in the elif is removed...and it is very important02:55
ananta_the search still needs to continue to see if there is any resoruce with current template ID, it shouldn't stop there02:55
asalkeldok, spotted that change now02:56
*** yuanying has quit IRC02:56
ananta_asalkeld: difficult to spot the change as it got moved out...in line comparison would have helped02:57
ananta_asalkeld: may be i should put a comment there :)02:57
ananta_asalkeld: before https://review.openstack.org/#/c/196536/, the args supplied to heat were not passed to updated stack... and update-rollback was failing02:59
ananta_sirushti: o/03:00
asalkeldyeah, i nearly made a bug for that03:00
asalkeldit's still a bit messy, but will do for now03:00
ananta_asalkeld: sure, let me know if it can be refactored in some way03:00
asalkeldi wonder if we really need to create a stack object and instead just pass the common_params in03:00
asalkeldlet's get it working, then stand back and see how we can make it better03:01
ananta_asalkeld: true... we don't need to pass the whole stack...but it was there for me to pass :) and aligned with old logic03:01
ananta_asalkeld: sure03:01
asalkeldboth +2'd03:01
ananta_asalkeld: thank you!03:02
asalkeldi have 2 you can have a look at: https://review.openstack.org/#/c/196531/ https://review.openstack.org/#/c/196531/03:02
openstackgerritMerged openstack/python-heatclient: Fix argument order for assertEqual  https://review.openstack.org/19571803:02
ramishramorning all03:02
asalkeldhttps://review.openstack.org/#/c/196533/03:02
asalkeldhi ramishra03:02
ramishrahi asalkeld03:03
ananta_asalkeld: sure03:03
*** kevinbenton has joined #heat03:08
*** gberginc has joined #heat03:09
ananta_asalkeld: reviewed03:10
asalkeldta03:10
*** MasterPiece has quit IRC03:13
*** pm90_ has joined #heat03:21
*** Drago has quit IRC03:32
sirushtimorning all03:45
sirushtiananta_, hi, what's up?03:45
*** dims has quit IRC03:48
*** Slower has joined #heat03:52
*** kebray has quit IRC03:56
*** Slower has quit IRC04:00
*** coolsvap|away is now known as coolsvap04:08
*** sdake has joined #heat04:09
*** sdake_ has joined #heat04:10
ananta_sirushti: you may want to review https://review.openstack.org/#/c/196536/ and https://review.openstack.org/#/c/196619/04:10
sirushtiananta_, sure04:11
sirushtiananta_, can we put those two in the DNM chain just to be sure so that we don't regress on any of the existing functional tests?04:12
*** KanagarajM has joined #heat04:12
ananta_sirushti: sure04:12
sirushtiananta_, thanks04:12
KanagarajMgood morning all04:12
*** david-lyle has quit IRC04:13
*** achanda has joined #heat04:13
*** sdake has quit IRC04:13
*** david-lyle has joined #heat04:14
*** vasanth has joined #heat04:18
*** pm90_ has quit IRC04:22
sirushtistevebaker, Hi, around? re: grenade testing04:25
stevebakersirushti: hi04:25
*** sdake has joined #heat04:25
sirushtistevebaker, Hi, so do you want the whole of heat_integrationtests to run during the verify phase?04:25
sirushtistevebaker, I was hoping we run only a few smoke tests04:25
sirushtilike what tempest does04:26
sirushtiFWIW, I've also drafted a spec about the kind of upgrade tests we could write -> https://review.openstack.org/#/c/190641/2/specs/liberty/upgrade-tests.rst04:26
stevebakersirushti: only running smoke tests sounds reasonable, but we need some mechanism for specifying which tests are smoke04:27
sirushtistevebaker, I'm thinking we need to move to something like tempest-lib04:27
stevebakeryes, that was always the plan, when it was ready to be consumed04:28
*** gberginc has quit IRC04:28
*** sdake_ has quit IRC04:29
*** vasanth has quit IRC04:29
*** achanda has quit IRC04:30
sirushtiok, I think it's being used now for python-.*client functional tests04:30
*** pm90_ has joined #heat04:31
stevebakerok, that is a good start04:31
*** tobe has quit IRC04:31
sirushtiok, I'll take a better look at it, thanks04:32
*** tobe has joined #heat04:32
sirushtistevebaker, also, when you find time, could you please take a look at the direction of that upgrade-testing spec^ and let me know if that's okay04:34
stevebakersure, I'll take a look04:35
sirushtithanks04:35
*** ananta_ has quit IRC04:52
*** sdake_ has joined #heat04:59
*** sdake has quit IRC05:03
*** LiJiansheng has quit IRC05:11
*** vijayagurug has joined #heat05:19
*** LiJiansheng has joined #heat05:24
*** nihilifer has joined #heat05:25
*** rakesh_hs has joined #heat05:28
*** ifarkas has joined #heat05:31
openstackgerritThomas Herve proposed openstack/heat: Add a new crypt method using cryptography  https://review.openstack.org/19501805:39
*** ishant has joined #heat05:42
*** Marga_ has quit IRC05:43
*** ishant|2 has joined #heat05:46
*** achanda has joined #heat05:48
*** ishant has quit IRC05:49
*** tshtilma has joined #heat05:52
*** gberginc has joined #heat05:53
openstackgerritPratik Mallya proposed openstack/heat: Add properties_data encryption to heat-manage  https://review.openstack.org/19532506:02
*** achanda has quit IRC06:04
openstackgerritPratik Mallya proposed openstack/heat: Fix heat-manage bug encrypting encrypted data  https://review.openstack.org/19563906:04
openstackgerritRabi Mishra proposed openstack/heat: Fix valdaition error for  parameter group  https://review.openstack.org/19695606:08
openstackgerritRabi Mishra proposed openstack/heat: Fix validation error for  parameter group  https://review.openstack.org/19695606:09
*** pm90_ has quit IRC06:11
*** pm90_ has joined #heat06:11
*** erkules_ is now known as erkules06:12
*** erkules has joined #heat06:12
*** tlashchova_ has joined #heat06:16
openstackgerritPratik Mallya proposed openstack/heat: Add properties_data encryption to heat-manage  https://review.openstack.org/19532506:17
openstackgerritPratik Mallya proposed openstack/heat: Fix heat-manage bug encrypting encrypted data  https://review.openstack.org/19563906:18
*** Marga_ has joined #heat06:26
*** achanda has joined #heat06:26
*** sdake_ has quit IRC06:29
*** lsmola has joined #heat06:33
openstackgerritThomas Herve proposed openstack/heat: Support snapshot deletion policy in Server  https://review.openstack.org/18558206:33
*** tspatzier has joined #heat06:38
*** pm90_ has quit IRC06:38
*** nkhare has joined #heat06:40
*** pm90_ has joined #heat06:46
therveramishra, Around? Got a question on https://review.openstack.org/#/c/194052/06:49
ramishratherve: hi.. sure06:49
therveramishra, Do you know what's the deal with _resource_names being used outside of ResourceGroup?06:50
therveOh06:52
therveSoftwareDeploymentGroup is a ResourceGroup06:52
therveUrggg06:53
ramishratherve: yeah06:53
therveramishra, Thanks06:53
ramishraSDG has some way of handling it;)06:53
therveI also discovered group removal policies... Good lord06:54
openstackgerritKanagaraj Manickam proposed openstack/heat: Adds designate.domain constraint  https://review.openstack.org/19256906:54
openstackgerritKanagaraj Manickam proposed openstack/heat: Designate Domain resource  https://review.openstack.org/19389706:54
openstackgerritKanagaraj Manickam proposed openstack/heat: Designate Record resource  https://review.openstack.org/19389806:54
ramishraI think I'll refactor SDG later06:54
*** pm90_ has quit IRC06:56
*** boris-42 has quit IRC07:02
*** achanda has quit IRC07:03
*** hdd has quit IRC07:11
*** pm90_ has joined #heat07:14
*** pm90__ has joined #heat07:18
*** pm90_ has quit IRC07:21
*** dkusidlo has joined #heat07:22
*** LimorStotland has joined #heat07:24
*** dkusidlo has quit IRC07:33
*** e0ne has joined #heat07:33
*** chlong has quit IRC07:35
*** e0ne has quit IRC07:37
openstackgerritPratik Mallya proposed openstack/heat: Add properties_data encryption to heat-manage  https://review.openstack.org/19532507:40
*** jistr has joined #heat07:43
*** BManojlovic has joined #heat07:43
*** jtomasek has joined #heat07:46
openstackgerritPratik Mallya proposed openstack/heat: Fix heat-manage bug encrypting encrypted data  https://review.openstack.org/19563907:48
*** LiJiansheng has quit IRC07:50
*** pm90__ has quit IRC07:53
*** pm90_ has joined #heat07:54
*** sdake_ has joined #heat07:55
*** shardy_ has joined #heat07:58
*** shardy has quit IRC07:59
*** LiJiansheng has joined #heat08:01
*** sergmelikyan has joined #heat08:02
*** jistr has quit IRC08:03
*** shardy_ has quit IRC08:03
*** shardy has joined #heat08:04
*** jistr has joined #heat08:10
*** sergmelikyan has quit IRC08:14
*** sergmelikyan has joined #heat08:15
*** tobe has quit IRC08:17
*** LiJiansheng has quit IRC08:19
*** LiJiansheng has joined #heat08:21
*** derekh has joined #heat08:22
*** sergmelikyan has quit IRC08:25
*** sergmelikyan has joined #heat08:26
*** LiJiansheng has quit IRC08:26
derekhI'm wondering if I should do a heat temp revert in tripleo CI until this lands https://review.openstack.org/#/c/196717/108:26
derekhAny ETA on when this might land ?08:27
pm90_+1 for that patch, it is breaking our templates :(08:28
pm90_I mean, without it our templates are breaking08:29
*** yassine_ has joined #heat08:34
*** sergmelikyan has quit IRC08:37
*** alex_xu_ is now known as alex_xu08:38
*** LiJiansheng has joined #heat08:39
*** pm90_ has quit IRC08:41
*** sdake_ has quit IRC08:45
-openstackstatus- NOTICE: OpenStack CI is down due to hard drive failures08:46
*** ChanServ changes topic to "OpenStack CI is down due to hard drive failures"08:46
*** mwheckmann has joined #heat08:50
*** pas-ha has joined #heat08:51
pas-hamorning all08:51
openstackgerritAngus Salkeld proposed openstack/heat: wip: yaql function  https://review.openstack.org/19698408:56
*** sergmelikyan has joined #heat09:00
*** e0ne has joined #heat09:02
*** yuanying has joined #heat09:05
*** yuanying has quit IRC09:10
*** yuanying has joined #heat09:11
*** e0ne is now known as e0ne_09:15
openstackgerritSteven Hardy proposed openstack/heat-specs: Add HOT resource_type_mapping annotation  https://review.openstack.org/19665609:22
shardytherve, tspatzier: ^^ I reworked the spec to move to a HOT annotation as discussed yesterday09:23
shardythe one thing we lose is the ability to do any grouping or compound constraint, but that's probably OK09:24
tspatzierhi shardy, cool, I'll have a look after lunch09:24
shardytspatzier: great, thanks! :)09:24
tspatziershardy: the compound constraint was a nice thing. I'll think about it - maybe we can find some clever combination? Or is it really two separate ideas?09:26
*** e0ne_ has quit IRC09:26
shardytspatzier: I'm not sure, I couldn't see a way to keep it but will think about it more, any ideas on that much appreciated! :)09:26
shardyderekh: I just approved it, I missed that we only just landed the change because it's not a revert09:29
derekhshardy: ack, thanks09:29
*** e0ne has joined #heat09:29
openstackgerritSteven Hardy proposed openstack/heat: Add str_split function to HOT 2015-10-15  https://review.openstack.org/19562909:31
*** tlashchova_ has quit IRC09:38
*** ochuprykov has joined #heat09:43
*** ananta_ has joined #heat09:49
*** LimorStotland has quit IRC09:49
*** LiJiansheng has quit IRC09:59
*** sergmelikyan has quit IRC10:10
*** LiJiansheng has joined #heat10:11
*** sergmelikyan has joined #heat10:11
*** coolsvap is now known as coolsvap|away10:14
*** Yanyanhu has quit IRC10:15
*** Qiming has quit IRC10:15
*** sergmelikyan has quit IRC10:17
*** elynn_ has quit IRC10:23
*** e0ne is now known as e0ne_10:23
*** ananta_ has quit IRC10:23
*** e0ne_ is now known as e0ne10:25
*** LimorStotland has joined #heat10:27
*** sergmelikyan has joined #heat10:37
*** cmyster has joined #heat10:37
*** shardy_ has joined #heat10:43
*** shardy has quit IRC10:45
*** Drago1 has joined #heat10:45
*** Drago1 has quit IRC10:45
*** Drago1 has joined #heat10:46
*** sergmelikyan has quit IRC10:47
*** shardy_ has quit IRC10:48
*** yuanying has quit IRC10:49
*** shardy has joined #heat10:49
*** chlong has joined #heat10:50
*** LiJiansheng has quit IRC10:51
ramishraochuprykov: hi10:57
ochuprykovramishra: hi10:58
ramishraochuprykov: can you pl validate if all the corner cases that you can think of with RG rolling_update  is taken care of now?10:59
ochuprykovramishara: taking into account that capacity = count + blacklist?11:00
ramishrayes11:00
ochuprykovseems that it is correct11:01
ramishraif you can put all the corner cases in the comment, I'll add them to the unit tests11:02
ochuprykovok, i will write some corner cases in comments11:02
ramishraochuprykov: thanks11:03
openstackgerritKanagaraj Manickam proposed openstack/heat: Designate Domain resource  https://review.openstack.org/19389711:05
openstackgerritKanagaraj Manickam proposed openstack/heat: Designate Record resource  https://review.openstack.org/19389811:05
*** dims has joined #heat11:07
*** EricGonczer_ has joined #heat11:10
*** LiJiansheng has joined #heat11:11
*** ishant|2 has quit IRC11:13
*** sergmelikyan has joined #heat11:14
*** Qiming has joined #heat11:15
ramishrashardy: hi!11:18
shardyramishra: Hi!11:18
*** dkusidlo has joined #heat11:19
*** asalkeld has quit IRC11:20
ramishrashardy: I've responded to your blacklist query for https://review.openstack.org/#/c/194052/, we do a final update as we leverage the blacklisted items during update to manage the min_in_service11:20
shardyramishra: does it make sense to consider a blacklisted item as one of those in service?11:22
ramishrashardy: during the update yes, why not11:22
shardyramishra: well the use-case for the blacklist is removing nodes which are either broken or are being removed from service11:23
*** EricGonczer_ has quit IRC11:23
shardymaybe it's fine, it just seems a bit odd to consider those nodes as "in service"11:23
*** sparr has quit IRC11:23
shardynot a blocker, just an observation :)11:24
ramishrashardy: we plan to blacklist them after the update, that's why I've considered them, I agree it's debatable.11:24
shardyramishra: Ok, np, in practice I doubt operators will drop nodes and trigger a rolling update in the same operation anyway11:25
shardyunless they're crazy and/or very brave ;D11:25
ramishrayeah, I agree. but if we agree that dropping blacklist is the first thing and then we do any rolling update, we can do that. but we would have same number of updates(additional one in the beginning)11:26
ramishrathe replace function is getting complicated with blacklist, final size etc.11:28
shardymaybe dropping them first would be slightly more logical, as by definition stuff in the blacklist is excluded from the group, and any operations on the group11:29
*** KanagarajM has quit IRC11:29
shardywould that help simplify things slightly, if we drop removed nodes, adjust the counts, then start the rolling update?11:29
ramishrayeah. sure. I'll try that11:30
shardyramishra: I'm thinking it'd be good if _replace didn't need to know anything about the blacklist, other than perhaps some class variables reflecting the current count11:30
ramishraif we remove blacklist in the beginning it would be ok. else, we may end up updating the blacklisted nodes, which we don't want11:31
shardyrelatedly, should we resize before trying the rolling update?11:32
shardye.g if there's a blacklist, and/or an increase in count, we should probably handle that (to have the correct number of in-service nodes at the start of the rolling update), then do any replacement of existing nodes?11:34
*** EricGonczer_ has joined #heat11:34
ramishrawhat about blacklist? Also we add items to maintain min_in_service, so resize afterwards makes sense to me.11:34
ochuprykovi'm +1 to resize after11:34
ochuprykovin this case we needn't to create new instances only for managing min_in_service11:36
*** radez is now known as radez_g0n311:36
*** sparr has joined #heat11:38
*** EricGonczer_ has quit IRC11:39
shardyramishra: resize uses _resource_names so it should respect the blacklist11:39
shardyI'm just thinking that if you increase count at the same time as modifying the resource definition, you probably want more capacity11:39
shardyso it's quite likely that reducing the capacity by the batch count for a long time is not what you wanted11:40
shardyIf you add any new nodes (and remove any blacklisted ones), then you can process the rolling update without the temporary reduction in capacity, e.g less nodes than was even specified before the update11:41
shardyAgain, this may well be a corner case not worth focussing too much on, just trying to think what an operator would want/expect11:41
*** steveg_afk has joined #heat11:44
ramishrayeah.. I know _replace function is complex now. But it  takes care of most corner cases with minimum number of updates.. at least I believe so;)11:44
ramishraprobably most of the cases may not happen in real-life. ex. modify resource def and reduce the count with a min_in_service same as count etc11:46
*** liusheng has quit IRC11:48
*** tochi has quit IRC11:49
shardyramishra: Yeah, you may be right, I'm just trying to figure out the order of least operator astonishment11:50
shardye.g if I increase count from 50 to 100, while also updating resource_def with a batch count of 1011:50
shardywould you expect to have a net number of nodes of 40 or 90 during the rolling update?11:50
shardyI think I would expect 9011:51
shardyAnyway, no big deal, just throwing the idea out there for consideration :)11:52
*** EricGonczer_ has joined #heat11:53
ramishrarolling update would do 40 and the 50 by resize, yeah I got your point. assumption is update is only for existing resources;)11:53
*** EricGonc_ has joined #heat11:57
*** jruano has joined #heat11:57
*** radez_g0n3 is now known as radez11:58
*** EricGonczer_ has quit IRC11:58
*** jistr is now known as jistr|class11:59
*** EricGonczer_ has joined #heat12:00
*** EricGonc_ has quit IRC12:01
openstackgerritSteven Hardy proposed openstack/heat-specs: Add HOT resource_type_mapping annotation  https://review.openstack.org/19665612:02
Qimingdpm12:02
Qimingdon't get the idea why we do resource definition update and group resize together12:02
*** sergmelikyan has quit IRC12:04
*** jistr|class is now known as jistr12:07
*** lkarm has joined #heat12:08
*** dkusidlo has quit IRC12:18
*** ochuprykov has quit IRC12:19
*** Marga_ has quit IRC12:21
*** Marga_ has joined #heat12:21
*** nkhare has quit IRC12:25
*** pm90_ has joined #heat12:31
*** pm90_ has quit IRC12:33
*** pm90_ has joined #heat12:33
pm90_what does it mean when jenkins marks a build as unstable?12:35
kairat_kushaevpm90_: static.openstack.org has harddisk failure12:36
kairat_kushaevpm90_: So right now gates are broken12:36
*** dkusidlo has joined #heat12:38
*** sergmelikyan has joined #heat12:39
*** shardy has quit IRC12:43
*** shardy has joined #heat12:43
*** EricGonczer_ has quit IRC12:45
*** mwheckmann has quit IRC12:47
pm90_kairat_kushaev: ah, thanks for the info!12:52
*** rpothier has joined #heat12:58
*** bdossant has joined #heat12:58
*** ananta_ has joined #heat13:00
ananta_Could some one please review these convergence patches: https://review.openstack.org/#/c/196619/ and https://review.openstack.org/#/c/196536/13:01
ananta_and also https://review.openstack.org/#/c/195387/13:01
*** sergmelikyan has quit IRC13:02
*** KanagarajM has joined #heat13:02
*** sergmelikyan has joined #heat13:03
*** ananta_ has quit IRC13:03
*** sergmelikyan has quit IRC13:08
*** sergmelikyan has joined #heat13:14
*** jonesbr has joined #heat13:14
*** sergmelikyan has quit IRC13:14
*** sergmelikyan has joined #heat13:20
*** nihilifer has quit IRC13:21
*** EricGonczer_ has joined #heat13:21
*** jaime49 has joined #heat13:22
*** EricGonc_ has joined #heat13:22
*** EricGonczer_ has quit IRC13:25
*** e0ne is now known as e0ne_13:29
*** gberginc has quit IRC13:31
*** boris-42 has joined #heat13:31
*** dkusidlo has quit IRC13:31
*** cody-somerville has joined #heat13:32
*** cody-somerville has quit IRC13:32
*** cody-somerville has joined #heat13:32
*** htruta has joined #heat13:35
openstackgerritSirushti Murugesan proposed openstack/heat-specs: Add a spec for in tree upgrade tests  https://review.openstack.org/19064113:36
*** e0ne_ has quit IRC13:39
*** jaime49 has quit IRC13:41
*** jaime49 has joined #heat13:41
*** LiJiansheng has quit IRC13:42
*** dkusidlo has joined #heat13:43
*** KanagarajM has quit IRC13:46
*** e0ne has joined #heat13:46
*** ochuprykov has joined #heat13:46
*** jaime49 has quit IRC13:47
tspatziershardy: I looked at your latest spec. Looks good to me!13:50
tspatzieron the compound constraints, I really don't have a good idea right now.13:50
tspatzierThe only thing that comes to mind is some kind of namespacing like in the XML world. I.e. template in namespace 1 only works with templates in the same namespace.13:51
tspatzierOtherwise, if we would put explicit template names or IDs in a template ('works_with: [template1.yaml, template2.yaml] it would not be self-contained any more.13:52
tspatzier... but something like this is really a second step that we could do at some point in the future.13:53
thervetspatzier, Not sure why you say that the proposal make the registry obsolete13:55
thervetspatzier, Surely that's only the case if you only have one provider for the resource13:55
*** dyasny has joined #heat13:55
therveWhereas the point is to have several?13:55
*** LiJiansheng has joined #heat13:56
tspatziertherve: I thought if you have nested templates files all annotated with the new mapping, it is not necessary any more to declare this explicitly in the environment. It can all be discovered from a common directory or something.13:56
tspatzieror environment could overrule/restrict the discovered mapping?13:57
thervetspatzier, Ah, you meant for the user-one, gotcha13:57
tspatzierHow both play together is actually an interesting question.13:57
therveI was thinking for the server side one13:57
*** bdossant_ has joined #heat13:58
therveAs a first step I would keep things explicit13:58
tspatziertherve: also for server side, a provide could decide to put a couple of possible provider templates in a certain dir and not declare a resource_registry13:58
*** bdossant has quit IRC13:59
*** sergmelikyan has quit IRC13:59
tspatzieragreed. I guess once the new feature is there, we will get to some kind of best practises when to use which mechanism13:59
*** sergmelikyan has joined #heat13:59
*** jecarey has joined #heat14:00
shardytspatzier: thanks for the feedback, agree we can leave the compound constraints thing until later14:00
*** dims has quit IRC14:01
shardythe point is to allow multiple implementations of the same resource type though, that's the main point of this change wrt TripleO requirements14:01
shardye.g to make the different implementations more easily discoverable14:01
*** dims has joined #heat14:01
*** wmlynch has joined #heat14:02
shardySo IMO we do still need the resource_registry to define which implementation is actually selected14:02
*** LiJiansheng has quit IRC14:03
therveRight, we could potentially make the registry optional14:04
*** pas-ha has quit IRC14:04
shardyWell I think possibly a heatclient feature to create the registry automatically if exactly one impelementation is discovered could be nice14:04
therve+114:05
shardyOr I suppose heat could resolve it, but heatclient still needs to know which files to include in the request14:05
shardye.g it's already created the resource_registry mapping by that point anyway14:05
therveshardy, About the resource_type_mapping section, and hoping to not derail the conversation14:05
therveshardy, Would it be generic enough to be what has been called "template metadata" in some past discussions?14:06
shardyHmmm14:07
shardyI suppose, but I hadn't really envisaged any freeform usage, only things related to mapping the template to a resource type14:07
*** dkusidlo has quit IRC14:07
openstackgerritTetiana Lashchova proposed openstack/python-heatclient: Add support for template-function-list command  https://review.openstack.org/19507014:08
openstackgerritTetiana Lashchova proposed openstack/python-heatclient: Add support for template-version-list command  https://review.openstack.org/19269614:08
shardye.g it's only a map because we might want to add some of the other tosca stuff like capabilities later14:08
therveI'm sure we can ask Randall what he thinks :)14:08
shardyI suppose folks could (ab)use the resource_type list and put whatever they want in there though ;)14:08
therveYeah, let's hope not14:09
therveI guess you don't provide any storage/query guarantee in this spec, was just wondering14:10
shardyYeah, I don't see how we can validate the resource_type list to enforce *only* types from the environment, it's going to be if <env type> in <resource type list>14:12
shardybut I'd prefer not to document it as anything-goes-here, or make any promises about validation in future :)14:12
*** dkusidlo has joined #heat14:12
therveSure, but we could call it metadata without any guarantee for now, and see if people are interested on building stuff around it14:14
*** bdossant_ has quit IRC14:14
therveIf we call it resource_type_mapping we're kind of stuck with that name for a while14:15
*** jruano has quit IRC14:15
Qimingshardy, why don't we persist this mapping into heat db?14:18
*** pas-ha has joined #heat14:18
shardyQiming: because the point is better composability before the stack is persisted by heat14:20
shardye.g to enable clients to make better decisions about which resource_registry mappings are valid, and to allow heat to validate that14:20
Qimingvalidation is always needed14:21
shardytherve: I'm -1 on the generic metadata idea, I'd prefer to this section to be limited to composability related stuff, e.g aligning somewhat with tosca14:22
therveMokay14:23
therveI'm not super excited about the proliferation of keywords14:23
*** shardy_ has joined #heat14:24
openstackgerritRico Lin proposed openstack/heat: support list resources with details  https://review.openstack.org/19657114:24
openstackgerritRakesh H S proposed openstack/heat: Consolidates cinder unit tests  https://review.openstack.org/19651014:24
openstackgerritRakesh H S proposed openstack/heat: Resource plugin for cinder volume encryption  https://review.openstack.org/19510314:24
*** shardy has quit IRC14:24
*** wmlynch has quit IRC14:27
*** shardy_ has quit IRC14:29
*** shardy has joined #heat14:30
*** lapalm has joined #heat14:32
*** wmlynch has joined #heat14:32
*** ochuprykov has quit IRC14:32
*** FL1SK has quit IRC14:35
*** hdd has joined #heat14:36
*** kebray has joined #heat14:37
*** vijayagurug has left #heat14:37
*** pm90_ has quit IRC14:43
*** kebray has quit IRC14:44
shardyAnyone know where the hot guide has moved (again) to?14:44
*** dkusidlo has quit IRC14:45
shardythe one covering composition and software config in detail14:45
shardyhttp://docs.openstack.org/user-guide/hot.html just links to the template guide14:45
*** lkarm has left #heat14:46
*** sergmelikyan has quit IRC14:47
*** pm90_ has joined #heat14:48
*** dsneddon has quit IRC14:48
*** sergmelikyan has joined #heat14:49
*** sergmelikyan has quit IRC14:49
*** dsneddon has joined #heat14:51
*** ChanServ changes topic to "support @ https://ask.openstack.org | developer wiki @ https://wiki.openstack.org/wiki/Heat | development @ https://launchpad.net/heat | logged @ http://eavesdrop.openstack.org/irclogs/%23heat/"14:51
-openstackstatus- NOTICE: The log volume was repaired and brought back online at 14:00 UTC. Log links today from before that time may be missing, and changes should be rechecked if fresh job logs are desired for them.14:51
*** dkusidlo has joined #heat14:53
*** e0ne is now known as e0ne_14:55
*** EricGonc_ has quit IRC14:55
*** shardy has quit IRC14:56
*** shardy has joined #heat14:56
*** jaypipes has quit IRC14:58
*** e0ne_ is now known as e0ne14:58
*** sergmelikyan has joined #heat14:58
*** e0ne is now known as e0ne_14:59
*** e0ne_ is now known as e0ne14:59
*** pm90_ is now known as pratikmallya14:59
*** pas-ha has quit IRC15:01
*** sergmelikyan has quit IRC15:06
*** shardy has quit IRC15:12
*** pas-ha has joined #heat15:13
*** dkusidlo has quit IRC15:14
*** jruano has joined #heat15:16
*** Qiming has quit IRC15:17
*** shardy has joined #heat15:18
*** BManojlovic has quit IRC15:18
*** mikeit has joined #heat15:20
*** cmyster_ has joined #heat15:22
*** cmyster has quit IRC15:26
*** Slower has joined #heat15:36
openstackgerritPratik Mallya proposed openstack/heat: Add properties_data encryption to heat-manage  https://review.openstack.org/19532515:38
*** sabeen1 has quit IRC15:38
openstackgerritPratik Mallya proposed openstack/heat: Fix heat-manage bug encrypting encrypted data  https://review.openstack.org/19563915:43
tspatziershardy: I was distracted for a while and just scanned the history. So you say the resource_registry will still be the definitive source for which provider template is used. And the resource_type_mapping section is just for doing some initial discovery to see what options exist? Right?15:43
tspatzierSo what would be the overall flow: user discovery based on annotation. Then defines the resource registry with the selected provider templates?15:44
tspatzierReally just a question. Because we definitely need a place where the final mapping is defined. Otherwise, if we discover multiple options for a resource type, who would decide on the one to choose, right?15:45
*** Drago1 has quit IRC15:47
*** kencjohnston has joined #heat15:49
*** Marga_ has quit IRC15:53
*** sdake has joined #heat15:54
*** mrutkows has joined #heat15:54
*** achanda has joined #heat15:56
*** sdake_ has joined #heat15:56
jdandreaHas anyone been in touch with chamberk or barnold in relation to stack-lifecycle-scheduler-hint lately? I've been trying to reach either/or regarding stack resource IDs (vs. Nova/Cinder/etc. IDs) to no avail.15:59
*** tspatzier has quit IRC16:00
*** achanda has quit IRC16:00
*** sdake has quit IRC16:00
*** jistr has quit IRC16:01
*** tlashchova_ has joined #heat16:01
*** sergmelikyan has joined #heat16:01
*** vijayagurug has joined #heat16:02
jdandrea... though I did confirm that those IDs *are* obtainable during the lifecycle plugin do_pre_op phase (per a brief chat with either sbaker or zaneb in Vancouver, I forget now, as a result of starting to implement convergence).16:03
*** spzala has joined #heat16:04
*** Drago has joined #heat16:05
*** shardy has quit IRC16:06
*** shardy has joined #heat16:07
*** rakesh_hs has quit IRC16:13
*** Drago has quit IRC16:13
*** Drago has joined #heat16:14
*** pas-ha has quit IRC16:16
*** shardy_ has joined #heat16:17
*** shardy has quit IRC16:18
*** pas-ha has joined #heat16:18
*** beekneemech is now known as bnemec16:19
*** sergmelikyan has quit IRC16:21
*** EricGonczer_ has joined #heat16:23
*** shardy_ has quit IRC16:23
*** e0ne is now known as e0ne_16:23
*** shardy has joined #heat16:24
*** heatuser has joined #heat16:25
*** tlashchova_ has quit IRC16:25
heatuserDoes heat support vertical scaling ?16:25
*** jaypipes has joined #heat16:26
*** sergmelikyan has joined #heat16:28
*** dontalton has joined #heat16:29
heatuserDoes heat support vertical scaling ?16:31
*** e0ne_ has quit IRC16:34
*** achanda has joined #heat16:35
*** e0ne has joined #heat16:36
*** FL1SK has joined #heat16:36
pas-haheatuser, what do you mean by vertical? you can resize VMs via stack-update, but currently heat is too optimistic in that regard16:37
pas-hathat is usual workflow is that after VM resize user should manually go into this VM, check that everything is working as it should and that finally confirm the resize with Nova16:38
heatuserpas-ha: how do you do a stack-update ?16:38
pas-haheat instead always automatically confirms the resize when VM goes to VERIFY_RESIZE state16:38
pas-hachange the template part describing the flavor of the server and issue a usual stack update16:39
heatuserwhat is a usual stack update ?16:39
pas-haheat http://docs.openstack.org/developer/python-heatclient/man/heat.html16:40
pas-havia command line interface or API of python-heatclient16:41
*** tshtilma has quit IRC16:42
heatusercan I change the flavor inside the template itself ?16:43
heatuserlike, I want to have a trigger that changes the flavor16:43
heatuserpas-ha16:44
pas-hafor that you would probably need to use a service like Mistral, heat templates are not imperative16:44
pas-hacouple a Mistral workflow with Ceilometer alarm and make it update the stack with template containing fatter flavor16:45
jdandreaheatuser:16:46
*** yassine_ has quit IRC16:47
jdandreaheatuser: The OS::Nova::Server resource type has a "flavor" property. According to the docs it can be updated without replacement. http://docs.openstack.org/hot-reference/content/OS__Nova__Server.html16:47
pas-hain anyway, that's actually not the best application design - resizing Nova server is disturbing the app that is inside, you can definitely count on your app outages16:48
jdandreapas-ha: Good/tangential point to be aware of, yep.16:48
jdandreaAs for the question itself though, it does appear possible.16:48
heatuserso, resizing a nova server is not recommended ?16:49
jdandreaAs for triggers, yeah, Mistral/Ceilometer.16:49
*** mwheckmann has joined #heat16:49
pas-hayou must understand what you are doing and how it will affect the workload16:49
heatuseronce you set it to one particular flavor, it's bad to change it to another ?16:49
pas-haagain, it depends on what are you using this VM for / what application is running on that VM16:50
*** openstackgerrit has quit IRC16:50
pas-haand how much you are bound to uptime of your application16:50
heatuserassume, I'm running the worst possible thing16:51
*** openstackgerrit has joined #heat16:51
pas-hayou might loose some intermittent data probably - during resize AFAIK Nova brings up a new VM with new flavor, and then kills the old one after resize is confirmed16:52
pas-hait probably tries to keep all the partitions like ephemeral though, not sure16:53
*** kencjohnston has quit IRC16:53
pas-haalso, if you've done any manual changes inside the VM before resize - they all would be gone, you'd have to repeat them inside the resized one16:54
* pas-ha not even sure if the original user data would be executed on the resized VM16:54
heatuserpass-ha: so it doesn't actually resize the current vm, it creates the new vm with new flavor and copies everything from the previous vm ?16:54
heatuserpass-ha: might not even copy everything; might lose data ?16:55
jdandreaheatuser: Some supplementary info, as you mentioned vertical scaling earlier: http://docs.openstack.org/openstack-ops/content/scaling.html16:56
pas-haAFAIK something like that, but probably depends on what exactly flavor parameters are changing (CPU no, RAM, sizes of partitions) and how much the actual compute backend supports live changes to them16:56
pas-hae.g. AFAIR vmware (some older versions ?) had some problems with increasing some values online without restarting the VM16:57
pas-hajdandrea, that link is for scaling your deployment AFAIU, not the app16:58
jdandreaUsing nova directly, there is "nova resize" and "nova snapshot" (followed by "nova boot"). They are more heavyweight (especially if stuff ends up being copied between compute/controller nodes).16:58
*** lapalm has quit IRC16:59
heatuserpas-ha: I want to be able to change both CPU and RAM on the fly16:59
jdandreapas-ha: *nods* but the note at the top mentions scaling and I thought that was worth pointing out (vertical in a traditional sense vs horizontal with clouds)16:59
*** derekh has quit IRC16:59
*** lapalm has joined #heat16:59
pas-haheatuser, you can ask nova team what limitations are there17:00
pas-hanova resize is what probably should be used here (snapshot/boot is more destructive for the app inside the VM)17:01
jdandreaDoc page for resize: http://docs.openstack.org/user-guide/cli_change_the_size_of_your_server.html - and note that the resized server may end up on a different compute node! (Not sure if that matters.) I second pas-ha, be aware that there is interruption and assess what that will mean for the server/app.17:03
heatusercan I issue a nova resize command within a hot template itself ?17:03
*** lapalm has quit IRC17:03
jdandreaheatuser: HOT is declarative, so the idea is you modify the template and issue a stack-update. Heat then orchestrates the changes by communicating with Nova, Cinder, et. al as needed. (I wonder if Heat effectively makes a resize request under the hood? Haven't checked the source for that.)17:04
*** e0ne has quit IRC17:05
jdandreaSo in the template you are saying "This is how I want reality to be." So long as the template is copacetic, Heat then conducts the various services to make whatever changes are needed, and in a sensible order if there's more than one change.17:06
jdandreaIn a sense, then, you're not having to remember "Which command do I use to do X in service Y again?" (Though it probably doesn't hurt to understand/appreciate what happens behind the scenes in various cases.)17:07
*** randallburt has joined #heat17:07
pas-hajdandrea, yes, heat makes resize request17:07
jdandrea:D17:08
*** sabeen has joined #heat17:08
pas-haand then blindly confirms it as I pointed17:08
jdandrea*chuckle* yup17:08
heatusercan OS::Ceilometer::Alarm trigger a nova sesize request ?17:08
pas-hanot in heat, as I sad you would have to use another service to do an automated stack update for you, like Mistral17:09
*** sergmelikyan has quit IRC17:09
jdandreaA ceilometer alarm issues a trigger (or logs in a file), but Heat is meant to orchestrate nouns, not verbs, as it were. :)17:09
jdandreaThis would be a verb, hence Mistral, yup.17:10
*** sergmelikyan has joined #heat17:10
* jdandrea looks away from the present Autoscaling and the deprecated HA Restarter resource (I know, I know, those are verb-y).17:11
*** sabeen has quit IRC17:12
heatuserohh, another thing17:13
*** sabeen1 has joined #heat17:14
heatuserin OS::Heat::AutoScalingGroup, can I pass a reference to a nova server from a parent template to a nested/child template ?17:15
heatuserjdandrea or pas-ha17:16
*** sdake has joined #heat17:17
shardyheatuser: yes, the native ASG resource can scale out stacks (not only nova servers), so you can define a template containing a nova server resource, which then passes the server ID into a child template (so you'd scale out the unit of two templates)17:18
shardyhttps://github.com/openstack/heat-templates/blob/master/hot/asg_of_stacks.yaml#L5117:18
heatusershardy: my goal to scale a OS::Heat::SoftwareDeployment17:19
shardyheatuser: that is certainly possible, although I'm intrigued by the use-case17:20
*** mikeit has quit IRC17:21
*** sdake_ has quit IRC17:21
heatusershardy:so, do I need to redefine everything from this SoftwareDeployment in the child template, or I can just pass the ids in to the child template from the parent template ?17:21
shardyheatuser: if you create the server outside the group, then pass the ID in and scale out config/deployment resources, you'd just be reapplying an increasingly duplicated configuration multiple times, no?17:22
shardyheatuser: you can just pass in the IDs, if you don't want to scale out the other resources17:22
*** metral is now known as metral_zzz17:23
*** sabeen1 has quit IRC17:23
heatusershardy: I want to scale config and server from SoftwareDeployment17:23
heatusershardy: but not depends_on17:24
*** sabeen has joined #heat17:24
heatusershardy: so, do I need to redefine config, server, depends_on in a child template ?17:25
*** htruta_ has joined #heat17:25
heatusershardy: or can I just pass the IDs from the parent template ? or maybe, I can define the software deployment under resource in ASG ?17:26
shardyheatuser: sorry, you've lost me tbh - you just put whatever resources you want to scale out inside the child template, then have AutoScalingGroup scale it out17:26
shardyhttp://hardysteven.blogspot.co.uk/2015/05/heat-softwareconfig-resources.html17:26
shardythat may provide some context around applying multiple config/deployment resources to a single server17:26
shardyScaling just a SoftwareDeployment makes no sense AFAICT, because inside an ASG every resource will be identical17:27
shardybut if you want to do it, yes it's technically possible and you can just pass in the IDs17:27
heatusershardy: I'm trying to implement horizontal scaling17:28
heatusershardy: and when I'm scaling up/down, I want to include all the configs with each vm that I scale up/down17:28
heatusershardy: that is what I'm trying to do17:29
*** tshtilma has joined #heat17:30
*** sergmelikyan has quit IRC17:31
*** mwheckmann has quit IRC17:33
*** dyasny has quit IRC17:33
*** metral_zzz is now known as metral17:37
*** dyasny has joined #heat17:37
*** achanda_ has joined #heat17:38
*** spzala has quit IRC17:40
*** achanda has quit IRC17:40
*** achanda has joined #heat17:42
*** jecarey has quit IRC17:43
*** achanda_ has quit IRC17:44
*** pas-ha has quit IRC17:46
*** sdake_ has joined #heat17:47
*** lsmola has quit IRC17:49
*** sdake has quit IRC17:50
*** sdake_ is now known as sdake17:50
openstackgerritSteven Hardy proposed openstack/heat-specs: Add nested-validation spec  https://review.openstack.org/19719917:51
*** jecarey has joined #heat17:56
*** vijayagurug has left #heat17:56
*** chlong has quit IRC17:56
*** e0ne has joined #heat17:58
*** lapalm has joined #heat18:00
*** lapalm has quit IRC18:04
*** e0ne is now known as e0ne_18:04
*** sthillma has joined #heat18:05
*** e0ne_ is now known as e0ne18:07
*** spzala has joined #heat18:11
*** tspatzier has joined #heat18:11
*** sthillma has quit IRC18:14
openstackgerritJulio Ruano proposed openstack/heat: WIP: Add Service to Magnum resources  https://review.openstack.org/19720718:14
*** sthillma has joined #heat18:15
*** tellesnobrega_ has joined #heat18:15
*** e0ne is now known as e0ne_18:18
*** randallburt has quit IRC18:18
*** tellesnobrega_ has quit IRC18:20
*** achanda has quit IRC18:21
*** heatuser has quit IRC18:22
*** e0ne_ is now known as e0ne18:23
*** htruta_ has quit IRC18:26
*** shardy has quit IRC18:27
*** shardy has joined #heat18:27
*** gberginc has joined #heat18:27
*** jruano_ has joined #heat18:31
*** jruano has quit IRC18:32
openstackgerritMiguel Grinberg proposed openstack/heat: Prepare SignalResponder class for more signal types  https://review.openstack.org/19722018:37
*** multi_io has quit IRC18:37
*** multi_io has joined #heat18:43
*** sdake has quit IRC18:46
*** sdake has joined #heat18:47
*** randallburt has joined #heat18:48
*** cmyster_ has quit IRC18:55
*** lapalm has joined #heat19:06
*** lapalm has quit IRC19:06
*** lapalm has joined #heat19:06
*** dsneddon has quit IRC19:09
*** achanda has joined #heat19:10
*** lapalm has quit IRC19:11
*** shardy has quit IRC19:13
*** e0ne is now known as e0ne_19:14
*** blomquisg has quit IRC19:14
*** blomquisg has joined #heat19:15
*** e0ne_ is now known as e0ne19:15
*** dsneddon has joined #heat19:18
*** tlashchova_ has joined #heat19:22
*** tspatzier has quit IRC19:24
*** Marga_ has joined #heat19:26
*** randallburt has quit IRC19:30
*** Marga_ has quit IRC19:32
*** Marga_ has joined #heat19:32
*** Marga_ has quit IRC19:36
*** Marga__ has joined #heat19:36
*** Marga__ has quit IRC19:53
*** achanda has quit IRC19:54
*** achanda has joined #heat19:55
openstackgerritOpenStack Proposal Bot proposed openstack/heat: Updated from global requirements  https://review.openstack.org/19510819:56
*** achanda has quit IRC19:59
*** jaime49 has joined #heat20:01
openstackgerritOpenStack Proposal Bot proposed openstack/python-heatclient: Updated from global requirements  https://review.openstack.org/19727520:02
*** jruano_ has quit IRC20:04
*** jruano has joined #heat20:05
openstackgerritMerged openstack/heat: Coverage: Full coverage for engine function methods  https://review.openstack.org/19645320:06
*** tshtilma has quit IRC20:07
*** lapalm has joined #heat20:07
*** gokrokve has joined #heat20:10
*** lapalm has quit IRC20:12
*** sergmelikyan has joined #heat20:13
*** mrutkows has quit IRC20:15
*** sergmelikyan has quit IRC20:17
*** sergmelikyan has joined #heat20:18
*** serg_melikyan has joined #heat20:24
*** sergmelikyan has quit IRC20:25
*** lapalm has joined #heat20:28
*** lapalm has quit IRC20:30
*** lapalm has joined #heat20:30
*** tlashchova_ has quit IRC20:30
*** serg_melikyan has quit IRC20:32
*** sergmelikyan has joined #heat20:34
*** lapalm_ has joined #heat20:34
*** lapalm has quit IRC20:34
*** e0ne has quit IRC20:35
*** jtomasek has quit IRC20:37
*** gberginc has quit IRC20:38
*** EricGonczer_ has quit IRC20:39
*** randallburt has joined #heat20:43
*** lapalm_ has quit IRC20:46
*** radez is now known as radez_g0n320:58
*** vahidh has quit IRC21:09
*** pratikma_ has joined #heat21:13
*** pratikmallya has quit IRC21:13
*** rpothier has quit IRC21:14
*** sergmelikyan has quit IRC21:17
*** vahidh has joined #heat21:21
*** daneyon has joined #heat21:27
*** dyasny has quit IRC21:42
*** jonesbr has left #heat21:44
*** kairat_kushaev has quit IRC21:47
*** skraynev has quit IRC21:49
*** Raj1 has joined #heat21:54
*** jecarey has quit IRC21:57
*** jruano has quit IRC21:59
*** spzala has quit IRC22:04
*** kebray has joined #heat22:04
*** randallburt has quit IRC22:04
*** hdd has quit IRC22:06
*** gokrokve has quit IRC22:07
*** jaime49 has quit IRC22:09
*** dims_ has joined #heat22:19
*** sergmelikyan has joined #heat22:19
*** Raj1 has quit IRC22:19
*** dims has quit IRC22:22
*** gokrokve has joined #heat22:22
*** pleia2 has quit IRC22:23
*** Hazelesque has quit IRC22:23
*** Hazelesque_ has joined #heat22:23
*** pleia2 has joined #heat22:25
*** kebray has quit IRC22:35
openstackgerritMerged openstack/heat: Remove default of port_security_enabled  https://review.openstack.org/19671722:35
*** dontalton has quit IRC22:37
openstackgerritOpenStack Proposal Bot proposed openstack/heat: Updated from global requirements  https://review.openstack.org/19510822:38
*** asalkeld has joined #heat22:38
*** gokrokve has quit IRC22:44
openstackgerritOpenStack Proposal Bot proposed openstack/python-heatclient: Updated from global requirements  https://review.openstack.org/19727522:45
*** jruano has joined #heat22:45
*** randallburt has joined #heat22:47
*** sabeen has quit IRC22:48
*** daneyon has quit IRC22:52
*** sergmelikyan has quit IRC22:52
*** jruano has quit IRC22:57
*** dims_ has quit IRC23:01
*** randallburt has quit IRC23:09
asalkeldstevebaker: yaql poc -> https://review.openstack.org/#/c/196984/123:13
stevebakerasalkeld: now that you've done it, what do you think of the idea?23:13
asalkelddocumenting the yaql will be an issue23:15
asalkeldone option is to have it as an option at the end of get_attr23:16
stevebakeryaql really needs some auto-generated reference cods23:16
stevebakerdocs23:16
asalkeldso either {get_attr: [normal, stuff, extra]} OR {get_attr: [normal, stuff, "yaql expression"]}23:17
asalkeldyaql is really good at selecting items out of json23:17
asalkeldi'll leave it out there for a bit, and see what people think23:18
stevebakerok23:19
kfox1111whats the status of conditionals in heat? going to be able to do it in liberty?23:19
stevebakerasalkeld: evil idea: implement yaql extensions which evaluate heat intrinsic functions inside yaql23:20
* kfox1111 reads up a few lines23:20
kfox1111nice. :)23:20
asalkeldkfox1111: what do you really want?23:22
stevebakerkfox1111: tripleo has come up with an approach using environment resource types so you can choose a stack resource which might create resources, or nothing. https://github.com/openstack/tripleo-heat-templates/blob/master/network/ports/noop.yaml https://github.com/openstack/tripleo-heat-templates/blob/master/network/ports/vip.yaml23:23
asalkeldconditional resources/variables?23:23
kfox1111heh. what I want... The ability to write one template that takes in paramaters for configuration rather then needing to fork the template and make specific versions.23:23
asalkeldkfox1111: ok, so be a bit more explicit23:24
asalkeldturn on/off resources23:24
asalkeldor change values?23:24
kfox1111like, one template that works with nova-network and neutron based on paramaters.23:24
asalkeldso resources23:24
kfox1111or the ability to pass an optional floating ip and have it used if passed.23:24
kfox1111or, here's a wrinkle.23:24
kfox1111neutron port allows specifying security groups.23:25
asalkeldstevebaker: we could totally change to yaql IF we didn't have implicit dependancies23:25
kfox1111specifying a security group of ["default"] is different then not specifying anything.23:25
kfox1111some way of optionally dropping out a paramater to a resource entirely.23:25
stevebakerasalkeld: the yaql would need to do its own dependency evaluation, which could be the hard part23:26
kfox1111or lastly, some way to make paramaters required or optional depending on another paramater.23:26
asalkeldkfox1111: keep it coming, i'll see if i can implement any of those with yaql23:26
asalkeldstevebaker: nope, i don't think it can23:26
asalkeldso we could force people to put depends_on in their resources23:27
asalkeldbut that is pain for users23:27
kfox1111Id rather have to specify dependencies manually if it ment I can do conditionals.23:27
kfox1111maintaining seperate templates is painful. :/23:28
stevebakerkfox1111: we feel your pain, its just that nobody has stepped up to implement it yet23:30
kfox1111it would be nice to have a conditional that allows easily switching one software deployment for another depending on what type of image it is (ubuntu, centos, etc)23:30
asalkeldkfox1111: is almost seems like it would be better to have the logic in the environment23:32
stevebakerthe yaql function might be a suitable way to build the conditional expression, just need to figure out how to do the conditional parts (maybe the yaql function could gain a if/elif/else arguments)23:32
kfox1111one of the advantages of params, is its a nice contract between user and tempate writer.23:34
kfox1111horizon gives you a nice way for users to answer a few questions (paramaters) and out pops a working system.23:34
kfox1111environments are not so easy to craft.23:34
stevebakeryes, environments are powerful and complicated23:35
kfox1111for the app catalog use case, I'd really like to not ever have to exaplain to a user how to use an environment. :/23:35
kfox1111at least by default. if conditionals are supported, there could be a form paramater that says "pull config from environment" or something.23:36
asalkeldna23:37
kfox1111stevebaker: https://www.youtube.com/watch?v=N3onNfjf4uY23:37
asalkeldbrb, breakfast23:37
stevebakerconditional templates would mean the end of our static dependency representation, which I think we could only consider once convergence is in23:37
kfox1111gota prototype going where you can browse the app catalog, then start up a heat template right from the ui.23:37
kfox1111so the user's work flow is basically, pick a web app, hit launch, fill out a form for config, and get a working app. :)23:38
stevebakerkfox1111: nice23:38
*** Qiming has joined #heat23:39
kfox1111but getting users to contribute truely generic templates to the catalog's going to be hard if they end up being very specific like most end up being without conditionals. :/23:39
stevebakerkfox1111: selecting one or more environment files could work in that flow too though23:39
kfox1111hmm... so pre can some environment files and make those available as options too?23:40
*** tochi has joined #heat23:40
stevebakerkfox1111: yes, the app catalog metadata should describe environment files too, and how they can be combined23:41
kfox1111hmm....23:42
kfox1111there only is ever one root environment file though?23:42
kfox1111(the horzion ui seems to imply that)23:42
stevebakerkfox1111: horizon is lagging the cli/api. Multiple environments are overlayed on each other in order.23:43
kfox1111so you could have a list of possible environemnts, and only some are valid with each other? hmm...23:44
stevebakerkfox1111: tripleo/tuskar are dealing with the exact same issue (introspecting templates and building a ui). You should read the thread [openstack-dev] [TripleO][Heat] Tuskar v. Heat responsibilities23:44
stevebakerkfox1111: shardy has already started with some proposals23:44
stevebakerlike nested validation23:44
kfox1111well, for the plugin, all we are doing is calling into the existing heat wizard, prepopulating the heat_url. we could prepopulate the env_url pretty easily, but it would be hard to populate multiple if the ui doesn't support it.23:44
kfox1111I've been skimming that thread, but not digging in closely. I guess I'll go back and have a closer look.23:45
stevebakeryes, horizon will need an enhancement. You could still do most things with a single environment though23:45
kfox1111I guess the other option is I can pass a bunch of include's if thats possible through.23:45
*** dims has joined #heat23:45
*** dims has quit IRC23:46
kfox1111it still feels kind of odd to have the environment and user form split though.23:46
kfox1111you ask the user to customize the template set, then ask them a bunch of other questions. it would be nice to be able to do it all at once.23:47
kfox1111but, it does have the interesting ramification that the app catalog running on the local cloud knows if, say, neutron is supported,23:47
kfox1111and can selectively add a neutron environment file to the app so that the user doesn't have to know the details.23:47
kfox1111at the summit, env include was talked about. is that going through in liberty?23:49
stevebakeryes, which a bp like this could help with https://review.openstack.org/#/c/196656/3/specs/liberty/resource-type-mapping.rst,cm23:49
stevebakerI'm not aware of an env include spec yet23:50
*** jruano has joined #heat23:50
kfox1111looking at the bp.23:51
kfox1111bummer. cause if it was supported, I could just build up a new env file dynamically which was just a bunch of includes, and then pass the whole thing as an env text blob to the horizon dialog.23:52
stevebakerkfox1111: my mindset is that heat templates describe a very broad architecture of the cloud app, and environments state the specific implementations23:53
stevebakerkfox1111: I'd like to implement it, but there is not much left after PTL and tripleo duties23:55
kfox1111yeah. in my mindset, a heat template is the instructions for deploying a web scale application. the user only cares about answering a few questions to get a working thing. env's take coder knowhow, and therefore tend to break that. :/23:55
asalkeldlol interface matching23:55
kfox1111so in your mindset mixed with mine, the template writer should be providing the env's?23:56
kfox1111and the paramaters are the final config?23:57
*** htruta_ has joined #heat23:57
asalkeldkfox1111: parameters are a part of the environment23:58
asalkeldliterally23:58
asalkeldenvironment = parameters + resource_registry23:58
kfox1111but not exposed via form in horizon or the heat cli.23:58
kfox1111which is a thing that non computer scientists can understand.23:59
kfox1111yaml, not so much.23:59
stevebakerkfox1111: yes, the template writer also writes one or more environments.23:59
kfox1111interesting. so under that model, it does make sense to put them in the catalog along with the template it self.23:59

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