Sounds good to me.
Best regards,
Hongbin
From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org]
Sent: May-12-16 9:12 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Jinja2 for Heat template
Hi,
My concern is that using option 1
est regards,
>
> Hongbin
>
>
>
> *From:* Yuanying OTSUKA [mailto:yuany...@oeilvert.org
> <yuany...@oeilvert.org>]
> *Sent:* May-12-16 6:02 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [magnum] Jinja2 for
)
Subject: Re: [openstack-dev] [magnum] Jinja2 for Heat template
We discussed the management of Heat templates several times. It seems the
consensus is to leverage the *conditionals*feature from Heat (option #1). From
the past discussion, it sounds like option #2 or #3 will significantly
complicate
if they want to
run newer version of Magnum with older version of OpenStack. Thoughts.
Best regards,
Hongbin
From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org]
Sent: May-12-16 6:02 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Jinja2 for Heat
Hi,
Thanks for your helpful comment.
I didn’t know about the pattern you suggested.
We often want to “if” or “for” etc…
For example,
* if private network is supplied as parameter, disable creating network
resource.
* if https parameter is enable, tcp 6443 port should be opened instead of
8080
On Thu, May 12, 2016 at 11:08:02AM +0300, Pavlo Shchelokovskyy wrote:
>Hi,
>
>not sure why 3 will bring chaos when implemented properly.
I agree - heat is designed with composition in mind, and e.g in TripleO
we're making heavy use of it for optional configurations and it works
pretty
Hi,
not sure why 3 will bring chaos when implemented properly.
Can you abstract the "thing" (sorry, not quite familiar with Magnum) that
needs FP + FP itself into a custom resource/nested stack? Then you could
use single master template plus two environments (one with FP, one
without), and
Hi, all.
Now, I’m trying to implement following bp.
* https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips
This bp requires to disable/enable “floating ip resource” in heat template
dynamically.
We have 3 options to implement this.
1. Use “conditions function”
*
