On Nov 2, 2013, at 3:12 PM, Salvatore Orlando sorla...@nicira.com wrote:
Hi.
I looked at the detailed API specification submitted by Edgar.
I think that the document Edgar shared does a fine job in discussion how an
API for managing logical topologies should work.
On the other hand,
Excerpts from Kyle Mestery (kmestery)'s message of 2013-11-05 06:35:04 +0800:
On Nov 2, 2013, at 3:12 PM, Salvatore Orlando sorla...@nicira.com wrote:
Hi.
I looked at the detailed API specification submitted by Edgar.
I think that the document Edgar shared does a fine job in
On Nov 4, 2013, at 7:31 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Kyle Mestery (kmestery)'s message of 2013-11-05 06:35:04 +0800:
On Nov 2, 2013, at 3:12 PM, Salvatore Orlando sorla...@nicira.com wrote:
Hi.
I looked at the detailed API specification submitted by Edgar.
I think
On 3 November 2013 17:36, Edgar Magana emag...@plumgrid.com wrote:
Zen, Kevin, Aaron, Salvatore et al,
Thank you so much for taking some time and reviewing this proposal. I
couldn't get any time slot neither in Neutron nor Heat track to have a deep
discussion about this proposal. My
Il giorno 03/nov/2013 17:15, Robert Collins robe...@robertcollins.net
ha scritto:
On 3 November 2013 17:36, Edgar Magana emag...@plumgrid.com wrote:
Zen, Kevin, Aaron, Salvatore et al,
Thank you so much for taking some time and reviewing this proposal. I
couldn't get any time slot
Zen, Kevin, Aaron, Salvatore et al,
Thank you so much for taking some time and reviewing this proposal. I
couldn't get any time slot neither in Neutron nor Heat track to have a deep
discussion about this proposal. My conclusions are the following:
- This API should be allocated in Heat project,
On Mon, Oct 28, 2013 at 01:19:13PM -0700, Edgar Magana wrote:
Hello Folks,
Thank you Zane, Steven and Clint for you input.
Our main goal in this BP is to provide networking users such as Heat (we
consider it as a neutron user) a better and consolidated network building
block in terms of
Hi Edgar,
It seems like this blueprint is related more to building an api that
manages a network topology more than one that needs to build out the
dependencies between resources to help create the network topology. If we
are talking about just an api to save, duplicate, and share these
network
Tim,
You statement building an api that manages a network topology more than
one that needs to build out the dependencies between resources to help
create the network topology
Is exactly what we are proposing, and this is why we believe this is not
under Heat domain.
This is why we are NOT
Hi Edgar,
I definitely see the usecase for the idea that you propose. In my opinion,
I don't see the reason for moving the management of topology into neutron,
Heat already provides this functionality (besides for the part of taking
an existing deployment and generating a template file). Also, I
that I am missing and it will help me to improve
current proposal.
Thanks,
Edgar
From: Aaron Rosen aro...@nicira.com
Reply-To: OpenStack List openstack-dev@lists.openstack.org
Date: Tuesday, October 29, 2013 12:48 PM
To: OpenStack List openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev
To: OpenStack List
Subject: Re: [openstack-dev] [Heat] Network topologies
Tim,
You statement building an api that manages a network topology more than
one that needs to build out the dependencies between resources to help
create the network topology
Is exactly what we are proposing, and this is why we
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
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
On Oct 28, 2013, at 9:07 AM, Mike Spreitzer
mspre...@us.ibm.commailto:mspre...@us.ibm.com
wrote:
Zane Bitter zbit...@redhat.commailto: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
On Sun, Oct 27, 2013 at 08:37:15AM -0700, 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:
On Mon, Oct 28, 2013 at 10:07:08AM -0400, 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
Excerpts from Steven Hardy's message of 2013-10-28 07:47:06 -0700:
On Sun, Oct 27, 2013 at 08:37:15AM -0700, 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
Hello Folks,
Thank you Zane, Steven and Clint for you input.
Our main goal in this BP is to provide networking users such as Heat (we
consider it as a neutron user) a better and consolidated network building
block in terms of an API that you could use for orchestration of
application-driven
19 matches
Mail list logo
