15:06:55 <VikramDham> #startmeeting QTIP 10012015
15:06:55 <collabot> Meeting started Thu Oct  1 15:06:55 2015 UTC.  The chair is VikramDham. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:06:55 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:06:55 <collabot> The meeting name has been set to 'qtip_10012015'
15:07:42 <VikramDham> Hello All
15:07:58 <VikramDham> #info vikram dham
15:08:12 <Mofassir> #info Mofassir Arif
15:08:49 <VikramDham> #info Mofassir can you provide update on heat integration with QTIP?
15:09:20 <Mofassir> Yes Vikram, Sure.
15:10:28 <Mofassir> So we are trying to use a config file that will be specified by the user before the benchmark is run and in that config file the user will also be mentioning the details regarding the VMs. such as their availability zones, OS, public networks etc.
15:11:04 <Mofassir> we will parse this information and pass it to our class responsible for bringing up VMs.
15:11:52 <Mofassir> that class will generate the Heat template with the required information from the config file and the VMs will be spwaned
15:12:45 <Mofassir> Currently the function that generates the Heat Template is running giving us some identation issues for the yaml files it is generating and we are trying to resolve it
15:13:56 <Mofassir> thats the brief update on the Heat front
15:16:03 <VikramDham> have you been able to debug what the issue is?
15:18:45 <Mofassir> the issue comes from the way python library treats  "{"  "}". inside the heat template there are 3 sections. Parameters, Resources and Outputs. resources sometimes call certain values from parameters. for example, "network: {get_param: public_network}"
15:19:11 <Mofassir> now when we write this line to a yaml file. The file sees "{" as an indentation
15:20:02 <Mofassir> so instead of writing back network: {get_params:public_network} we end up writing back
15:20:05 <Mofassir> Network:
15:20:12 <Mofassir> get_params
15:20:29 <Mofassir> get_params: public network
15:20:50 <Mofassir> we are trying to find a workaround for this behavior
15:22:30 <VikramDham> are yo uasking user to write heat template inside config.yaml and then again parse it to generate heat config file/
15:22:33 <VikramDham> ?
15:23:03 <VikramDham> Can you share the problematic confg.yaml?
15:24:16 <Mofassir> no, the user only enters the bare minimum values which are specific to their deployment of OpenStack. the user doesnt have to write the Heat Template inside the config file.
15:24:33 <Mofassir> the config file available on the ehterpad and that is not the problem area
15:26:46 <VikramDham> Correct me: config.yaml => QTIP => heat template file? Or is there any other file input to the QTIP for generatin heat template?
15:27:01 <Mofassir> That is correct
15:27:09 <Mofassir> no other file is needed
15:27:47 <VikramDham> where is user adding curly braces?
15:29:28 <Mofassir> the curly braces are added by the QTIP code for generating the Heat Template. i am posting a sample Heat Template on etherpad with the areas which our program is have making mistakes
15:33:37 <Mofassir> https://etherpad.opnfv.org/p/Qtip
15:44:09 <VikramDham> still not clear if you are not able to print curly braces or if you are having some other problem
15:44:38 <VikramDham> do you know how to fix the issue?
16:01:43 <VikramDham> not clear what problem you are facing - please send email if you need help
16:01:48 <VikramDham> #endmeeting