Friday, 2019-09-13

*** k_mouza has quit IRC00:05
*** maddtux has joined #heat00:50
*** ayoung has quit IRC01:24
*** tkajinam has quit IRC01:54
*** tkajinam has joined #heat02:11
*** hongbin has joined #heat02:32
*** tkajinam has quit IRC02:36
*** tkajinam has joined #heat02:56
*** ramishra has joined #heat03:16
*** hongbin has quit IRC03:34
*** skramaja has joined #heat03:57
*** radeks has quit IRC04:35
*** jtomasek has joined #heat05:16
*** radeks has joined #heat05:17
*** tkajinam has quit IRC05:54
*** tkajinam has joined #heat06:03
*** tkajinam_ has joined #heat06:19
*** tkajinam has quit IRC06:22
*** ttsiouts has joined #heat07:26
*** ramishra has quit IRC07:26
*** ramishra has joined #heat07:28
*** ttsiouts has quit IRC07:36
*** gfidente has joined #heat07:37
*** ttsiouts has joined #heat07:37
*** ttsiouts has quit IRC07:41
*** ttsiouts has joined #heat07:59
*** ivve has joined #heat08:00
*** tkajinam_ has quit IRC08:01
*** gfidente has quit IRC08:06
*** rubasov has quit IRC08:15
*** rubasov has joined #heat08:23
*** k_mouza has joined #heat08:24
*** gfidente has joined #heat08:25
*** e0ne has joined #heat08:38
*** gfidente has quit IRC08:39
*** gfidente has joined #heat08:43
*** ttsiouts has quit IRC09:02
*** ttsiouts has joined #heat09:03
*** ttsiouts has quit IRC09:07
*** ttsiouts has joined #heat09:14
*** jawad_axd has joined #heat09:19
*** ivve has quit IRC09:32
*** ttsiouts has quit IRC09:57
*** ttsiouts has joined #heat09:57
*** ttsiouts has quit IRC10:02
*** tkajinam has joined #heat10:05
*** ivve has joined #heat10:05
*** k_mouza has quit IRC10:09
*** k_mouza has joined #heat10:33
*** maddtux has quit IRC10:33
*** jawad_axd has quit IRC10:55
*** jawad_axd has joined #heat10:55
*** k_mouza has quit IRC11:09
*** k_mouza has joined #heat11:09
*** jawad_axd has quit IRC11:37
*** jawad_axd has joined #heat11:37
*** zaneb has quit IRC11:48
*** zaneb has joined #heat11:49
*** ttsiouts has joined #heat12:19
*** tkajinam has quit IRC12:25
*** jawad_ax_ has joined #heat12:38
*** jawad_axd has quit IRC12:41
*** jawad_ax_ has quit IRC13:18
*** jawad_axd has joined #heat13:19
*** jawad_ax_ has joined #heat13:22
*** jawad_axd has quit IRC13:24
*** jawad_ax_ has quit IRC13:28
*** jawad_axd has joined #heat13:29
*** ttsiouts has quit IRC13:31
*** ttsiouts has joined #heat13:32
*** jawad_axd has quit IRC13:33
*** ttsiouts_ has joined #heat13:34
*** ttsiouts has quit IRC13:35
openstackgerritDavid Peacock proposed openstack/heat master: Update get_hosts to use available API  https://review.opendev.org/68206114:11
*** radeks has quit IRC14:21
*** rubasov has quit IRC14:23
*** dpeacock has joined #heat14:24
*** k_mouza has quit IRC14:31
*** k_mouza_ has joined #heat14:32
*** rcernin has quit IRC14:42
*** e0ne has quit IRC14:43
*** rubasov has joined #heat14:57
*** k_mouza_ has quit IRC15:17
*** k_mouza has joined #heat15:24
*** jtomasek has quit IRC15:28
*** ivve has quit IRC15:29
*** ttsiouts_ has quit IRC15:37
*** ttsiouts has joined #heat15:38
*** ttsiouts has quit IRC15:42
*** mailingsam has joined #heat15:46
mailingsamdid anyone try nested heat stack created? heat cli errors with nested file not found15:47
mailingsamI'm trying the example here https://docs.openstack.org/heat/pike/template_guide/composition.html15:48
mailingsamHeat cli in Devstack Master is unable to find my_nova.yaml file15:48
*** gfidente is now known as gfidente|afk15:50
*** ramishra has quit IRC15:51
*** mailingsam has quit IRC15:58
gregworkstevebaker: no i hadnt seen that website16:25
*** k_mouza has quit IRC16:42
*** bnemec is now known as beekneemech16:48
*** k_mouza has joined #heat16:57
*** k_mouza has quit IRC17:01
gregworkin a resource section is condition: [ this, not: that ] valid ?17:23
gregworker condition: [ this, not: { that } ]  i guess17:23
zanebgregwork: I'm confused about what you're wanting that to do17:26
gregworki have two condtions defined in the conditions block this and that.  in the resource section i want to define resources based on the trueness of those conditions situationally ..17:26
gregworkmy this and that in conditions are equals scenarios so they will be true or false, in the resource section my resource should be created based on if this is true but not that17:27
gregworkim trying to see if i can do something like17:27
gregworkr:17:28
gregwork  type: ...17:28
gregwork  condtion:17:28
gregwork    - this17:28
gregwork    - not: { that }17:28
gregworkor somesuch17:28
gregworkthere some scenarios where that will need to be true so thats why im not just creating a total assertion in conditions: .. its situational where i want to "not: that"17:29
gregworkthis is ultimately me trying to exclude some softwaredeployment steps for a particular node type in a nested stack so im trying to use a high level control at the resource to exclude it, rather than do it in the software config itself17:30
zanebgregwork: btw the answer to your earlier yaql question is $.node_map.items().where($[1].type = 'primary-db').select($[0])17:37
zanebgregwork: you can use the 'and' and 'or' functions to combine conditions. it's not clear to me which one you want in this case17:39
gregworkzaneb: thanks i had tried a few variations of that without success.  good to see a working example17:39
zanebhttp://yaqluator.com/ is quite helpful17:39
zanebbut yaql syntax looks mostly like line noise and the documentation is poor :/17:40
gregworkyeah i saw that today, wish i had it when i was mucking about with yaql .. i was having to make a simple test stack and deploy it over and over17:40
gregworkand troubleshoot lol17:40
zanebyou can always import the lib and play with it in a python repl, but the website makes it dead simple17:40
gregworkregarding the and/or/not .. im trying to figure out if i can define the conditions in the resource using and/or logic .. or if i need to do that in the conditions: section17:41
zanebyou can do either IIRC17:41
gregworki assume resource: condition: Accepts a list17:41
gregworkand the list can have - not: stuff17:42
gregworkfrom a grammar pov17:42
zanebit accepts either a string or an and/or/not function (and the arguments to that function may be strings or and/or/not functions (and it's turtles all the way down))17:43
gregworkah ok so like17:44
gregworkr:17:44
gregwork  condition:17:44
gregwork    and:17:44
gregwork      - this17:44
gregwork      - not: that17:44
zanebyes17:45
gregworkzaneb: do you know who the PM for rh osp is ?18:02
gregworkor product owner18:03
gregworkwhatever the lingo is18:03
gregworkthe decision maker18:03
gregworkis it sean cohen ?18:03
zanebmaybe? I find it hard to keep track18:03
gregworkim trying to rfe in them cloning the heat client packages out of rhel-7-server-openstack-13-rpms out of that repo into a more accessible repo.  the placement of those packages there means that 99% of the customer base will be unable to use softwareconfig/software deploy with their instances since nobody buys infinite amount of infra entitlements and you need an infra entitlement to install those packages18:05
gregworkricolin mentioned there is a 3rd party upstream workaround using docker but that isnt going to fly for a lot of people18:05
gregworkespeically the ones that are interested in paying for support18:06
gregworki think softwareconfig/deployment are really powerful tools and it seems short sighted from a product pov that its hamstrung like this18:06
gregworkagain from the perspective of enterprise, who use rh cdn / satellite18:06
zanebthis is not really the right place to discuss RH products18:07
gregworki suppose18:07
gregworkredhatters are legion on this ircnetwork tho18:07
gregwork:)18:07
zanebalso do you mean the heat-agents packages? afaik clients are available to anyone18:08
zaneband have nothing to do with sw deployments specifically18:08
gregworkthey arent incorporated into the rhel7 cloud image at all, and doing a yum provides */various/heatcfntoolthings they only exist in that infra repo18:09
gregworkrhel7 cloud image has the base cloudinit service, but not the heatcfn stuff18:09
gregworkso you cant pass it say a software deployment with ansible18:09
gregworkor puppet18:10
gregworkonly a cloud init shell script18:10
gregworkwhich i am using to install the cfn rpms to then pick up the rest of my deployment18:10
zanebheat-cfntools is massively out of date and should not be used by anyone18:10
gregworkreally ?18:10
zanebreally18:10
gregworki am just a casual consumer, im not in the know :)18:11
zaneband is also not involved in sw deployments18:11
gregworkso my sw deploy doesnt work without this18:12
gregworkhttps://github.com/gprocunier/cloudforms-heat-deployment/blob/master/cloud-init/node-configuration.sh#L23-L3618:12
zanebI don't see heat-cfntools in that list at all?18:12
gregworkperhaps i misspoke, those packages allow heat-config-ansible to happen18:13
gregworkand they are missing18:13
zanebyeah, it's heat-agents18:13
gregworkit would be nice if they were incorporated into the cloud image, and were also accessible outside of an infra sub18:14
gregworkyou see what im saying though ?18:15
zanebI agree they should be available with any RHEL sub18:15
* gregwork nods18:15
gregworkhence my question, mr cohen the guy i have to convince?18:15
gregworki have a support ticket rfe opened18:16
zanebgetting them preinstalled in the cloud image is probably too optimistic, but you can always build your own image18:16
gregworkzaneb: but only if i subscribe an instance to the main osp infra channel which you will not have entitlements for after you deploy your overcloud18:16
zanebI have no idea who you have to convince, but fwiw it's more of a technical issue than something that PM are blocking. I guarantee PM don't care either way18:16
gregworkso your options are to use something out of band or forget about using heat-config-ansible18:17
gregworkok well .. ill keep digging ig uess18:18
gregwork*guess18:18
gregworkthanks for your time :)18:18
*** gfidente|afk has quit IRC20:11
*** hjensas has quit IRC20:24
*** hjensas has joined #heat20:28
*** openstackgerrit has quit IRC20:51
*** k_mouza has joined #heat22:30
*** k_mouza has quit IRC23:39
*** rcernin has joined #heat23:57

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