Open Stack

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 choose which one to use right where you have this logic split
in your code.

Option 2 is not so bad either IMO (AFAIK Trove was doing that at sometime,
not sure of current status), but the above would be nicer.

Best regards,

Dr. Pavlo Shchelokovskyy
Senior Software Engineer
Mirantis Inc
www.mirantis.com

On Thu, May 12, 2016 at 4:44 AM, Yuanying OTSUKA <yuanying at oeilvert.org>
wrote:

> 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”
>     *
> https://blueprints.launchpad.net/heat/+spec/support-conditions-function
> 2. Dynamically generate heat template using Jinja2
> 3. Separate heat template to “kubecluster-with-floatingip.yaml” and
> “kubecluster-no-floatingip.yaml”
>
> Option 1 is easy to implement, but unfortunately this isn’t supported by
> Mitaka release.
> Option 2 needs a Jinja2 template support by Magnum.
> Option 3 will bring chaos.
>
> Please let me know what you think.
>
>
> Thanks
> -OTSUKA, Yuanying
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160512/a5cd2804/attachment.html>