From bff04b1b150b62c67bb16e3980caba9ef3af5fec Mon Sep 17 00:00:00 2001 From: Guido Trotter <ultrotter@google.com> Date: Thu, 4 Jun 2009 13:48:35 +0100 Subject: [PATCH] 2.1 design: non bridged instances support Signed-off-by: Guido Trotter <ultrotter@google.com> Reviewed-by: Iustin Pop <iustin@google.com> --- doc/design-2.1.rst | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/doc/design-2.1.rst b/doc/design-2.1.rst index d5d067706..25f75fe4e 100644 --- a/doc/design-2.1.rst +++ b/doc/design-2.1.rst @@ -153,6 +153,39 @@ The parameters will be kept, as for the BEPARAMS into a "default" category, which will allow us to expand on by creating instance "classes" in the future. Instance classes is not a feature we plan implementing in 2.1, though. +Non bridged instances support +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Current State and shortcomings +++++++++++++++++++++++++++++++ + +Currently each instance NIC must be connected to a bridge, and if the bridge is +not specified the default cluster one is used. This makes it impossible to use +the vif-route xen network scripts, or other alternative mechanisms that don't +need a bridge to work. + +Proposed changes +++++++++++++++++ + +The new "mode" network parameter will distinguish between bridged interfaces +and routed ones. + +When mode is "bridge" the "link" parameter will contain the bridge the instance +should be connected to, effectively making things as today. The value has been +migrated from a nic field to a parameter to allow for an easier manipulation of +the cluster default. + +When mode is "route" the ip field of the interface will become mandatory, to +allow for a route to be set. In the future we may want also to accept multiple +IPs or IP/mask values for this purpose. We will evaluate possible meanings of +the link parameter to signify a routing table to be used, which would allow for +insulation between instance groups (as today happens for different bridges). + +For now we won't add a parameter to specify which network script gets called +for which instance, so in a mixed cluster the network script must be able to +handle both cases. The default kvm vif script will be changed to do so. (Xen +doesn't have a ganeti provided script, so nothing will be done for that +hypervisor) External interface changes -------------------------- -- GitLab