Revision bff04b1b

b/doc/design-2.1.rst
153 153
which will allow us to expand on by creating instance "classes" in the future.
154 154
Instance classes is not a feature we plan implementing in 2.1, though.
155 155

  
156
Non bridged instances support
157
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
158

  
159
Current State and shortcomings
160
++++++++++++++++++++++++++++++
161

  
162
Currently each instance NIC must be connected to a bridge, and if the bridge is
163
not specified the default cluster one is used. This makes it impossible to use
164
the vif-route xen network scripts, or other alternative mechanisms that don't
165
need a bridge to work.
166

  
167
Proposed changes
168
++++++++++++++++
169

  
170
The new "mode" network parameter will distinguish between bridged interfaces
171
and routed ones.
172

  
173
When mode is "bridge" the "link" parameter will contain the bridge the instance
174
should be connected to, effectively making things as today. The value has been
175
migrated from a nic field to a parameter to allow for an easier manipulation of
176
the cluster default.
177

  
178
When mode is "route" the ip field of the interface will become mandatory, to
179
allow for a route to be set. In the future we may want also to accept multiple
180
IPs or IP/mask values for this purpose. We will evaluate possible meanings of
181
the link parameter to signify a routing table to be used, which would allow for
182
insulation between instance groups (as today happens for different bridges).
183

  
184
For now we won't add a parameter to specify which network script gets called
185
for which instance, so in a mixed cluster the network script must be able to
186
handle both cases. The default kvm vif script will be changed to do so. (Xen
187
doesn't have a ganeti provided script, so nothing will be done for that
188
hypervisor)
156 189

  
157 190
External interface changes
158 191
--------------------------

Also available in: Unified diff