All,
Since we are starting to discuss this document I have one fundamental
comment/question.
The part of it's abstract says:
This document proposes a "single-touch" approach for provisioning the
networking parameters related to Virtual Machine creation, migration
and termination on servers.
I would like to observe that in the tenant data center VMs are only a
small part of the tenant network.
Single-touch is of course great idea and that is why extension to one of
the common and very popular data center orchestration environments
(openstack) developed a module called Quantum.
This module is exactly targeting to not only provision networking
parameters to VMs but also to other network appliances including virtual
routers, firewalls, loadbalancers etc .. which are part of the tenant DC
network.
Ref: http://wiki.openstack.org/Quantum
So I would like to ask the authors of the draft-kompella-nvo3-server2nve
why there is the an attempt to reinvent the wheel and how far they are
going to maintain the vision of "single-touch" considering that much
broader aspect of this has been already solved ?
Best regards,
R.
PS. I am perfectly fine to hear that NVO3 does not want to adopt any
work which is done outside of IETF. However I think that such message
needs to be clearly weighted against current deployments as well as
existing market adoption of such solutions.
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
