On 28/10/13 15:07, Mike Spreitzer wrote:
Zane Bitter <zbit...@redhat.com> wrote on 10/28/2013 06:47:50 AM:
> On 27/10/13 16:37, Edgar Magana wrote:
> > Heat Developers,
> >
> > I am one of the core developers for Neutron who is lately working
on the
> > concept of "Network Topologies". I want to discuss with you if the
> > following blueprint will make sense to have in heat or neutron code:
> > https://blueprints.launchpad.net/neutron/+spec/network-topologies-api
> >
> > ...
>
> It sounds to me like the only thing there that Heat is not already doing
> is to dump the existing network configuration. What if you were to
> implement just that part and do it in the format of a Heat template? (An
> independent tool to convert the JSON output to a Heat template would
> also work, I guess.)
>
> ...
>
> It does sound very much like you're trying to solve the same problem as
> Heat.
>
In my templates I have more than a network topology. How would I
combine the extracted/shared network topology with the other stuff I
want in my heat template?
Copy and paste?
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
