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
Basically, I want to let tenants “save”, “duplicate” and “share” network
topologies by means of an API and a standardized JSON format that
describes network topologies. This google document provides detailed
description:
https://docs.google.com/document/d/1nPkLcUma_nkmuHYxCuUZ8HuryH752gQnkmrZdXeE2LM/edit#
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.)
A non-Heat JSON output like the one in the document might conceivably be
easier for people to build tools such as visualisations on top of. On
the other hand, Heat templates can take advantage of the visualisation
code that already exists in Horizon.
If this becomes read-only then maybe the API can change to something like:
/v2/{tenant_id}/networks/{network_id}/topology
There is a concern in Neutron of not duplicating efforts done by Heat
team and also to find the right place for this API.
The intended work does NOT include any application driven orchestration
system, does NOT include any already existing or vender-specific
standard format for describing topologies, actually we want to
standardized one based on Neutron but it is still on discussion.
If Heat developers could provide their point of view about this
proposal, wether it should be moved to Heat or it is fine to keep it in
Neutron.
It does sound very much like you're trying to solve the same problem as
Heat.
cheers,
Zane.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
