Question about Heat parser
Dear all, In the context of my post-doc research, I'm working with HOT templates and I want to parse them. Instead of developing a new parser, I want to reuse the one that is used by Heat but I don't want to connect to a running OpenStack to do the parsing. Is it possible to use Heat as a standalone parser (i.e. without connecting to a running OpenStack) ? Thank you for your answer. Best regards, Adja SYLLA _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
On 22/01/19 1:45 AM, adjandeye.sylla@orange.com wrote:
Dear all,
In the context of my post-doc research, I’m working with HOT templates and I want to parse them.
Instead of developing a new parser, I want to reuse the one that is used by Heat but I don’t want to connect to a running OpenStack to do the parsing.
Is it possible to use Heat as a standalone parser (i.e. without connecting to a running OpenStack) ?
Yes, that shouldn't be a problem. You can import Heat as a library ("from heat.engine import template"). As long as you don't call any of the methods that deal with the database (i.e. load()/store()), you should have no trouble. Note that there are a number of template APIs (the ones that deal with intrinsic functions) that take a 'stack' argument. Originally we passed a heat.engine.stack.Stack object, but now you should pass a heat.engine.stk_defn.StackDefinition object. That should make things easier for you, because a StackDefinition can be constructed from a Template, and it doesn't deal with the database at all, so you can skip the complexity of the Stack object. We look forward to hearing the results of your research :) cheers, Zane.
Thank you. I will import the Heat library and use it to do the parsing. I will give your news of my results :-) cheers, Adja -----Message d'origine----- De : Zane Bitter [mailto:zbitter@redhat.com] Envoyé : mardi 22 janvier 2019 07:18 À : openstack-discuss@lists.openstack.org Objet : Re: Question about Heat parser On 22/01/19 1:45 AM, adjandeye.sylla@orange.com wrote:
Dear all,
In the context of my post-doc research, I'm working with HOT templates and I want to parse them.
Instead of developing a new parser, I want to reuse the one that is used by Heat but I don't want to connect to a running OpenStack to do the parsing.
Is it possible to use Heat as a standalone parser (i.e. without connecting to a running OpenStack) ?
Yes, that shouldn't be a problem. You can import Heat as a library ("from heat.engine import template"). As long as you don't call any of the methods that deal with the database (i.e. load()/store()), you should have no trouble. Note that there are a number of template APIs (the ones that deal with intrinsic functions) that take a 'stack' argument. Originally we passed a heat.engine.stack.Stack object, but now you should pass a heat.engine.stk_defn.StackDefinition object. That should make things easier for you, because a StackDefinition can be constructed from a Template, and it doesn't deal with the database at all, so you can skip the complexity of the Stack object. We look forward to hearing the results of your research :) cheers, Zane. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
participants (2)
-
adjandeye.sylla＠orange.com
-
Zane Bitter