Difference between revisions of "XenServerOVS"

Revision as of 20:29, 31 January 2011

Launchpad Entry: NovaSpec:xs-ovs
Created:
Contributors:

Summary

Adds support for the Open vSwitch in XenServer. This allows for the transition away from the standard Linux Bridge in XenServer and gives us more granular networking protections without having to utilize iptables, arptables, or ebtables for the host. OVS will also provide better IPv6 protections which will enable us to prevent things like NDP attacks which we currently can't properly protect against with the Liunx bridge.

Release Note

OVS is currently bundled into the XenServer platform. ACLs would be fired on instance create and teardown to protect the guest. If a blanket set of security rules are used, then this can run independent of Nova in dom0.

Rationale

Out of the box, XenServer is built for a single Enterprise and is not really built with the concept of being multi-tennant which is typically what Service Providers require. In order to fully secure the guests from each other, certain networking rules need to be applied to the virtual interfaces of each guest from the hypervisor. This ensures better security and an overall better experience for the guests.

User stories

1. As a service provider, I want to ensure customer instances are secure. 2. As a user, I want to make sure my instance is protected.

Assumptions

NovaSpec:xs-inject-networking is present in order for script to get it's input data for the rules.

Design

Determine which ACLs need to be implemented to block all of the proper traffic. Need to prevent ARP poisoning, MAC address spoofing, and unauthorized sniffing of traffic for IPv4. Also need to prevent NDP attacks in IPv6.

Implementation

vif_rules.py is pushed down the XenServer host on provisioning of host nodes. Script to enable or disable rules is ran on VM start, reboot, or shutdown.

Code Changes

Modifications to vif_rules.py and vif scripts in XenServer dom0

Test/Demo Plan

This need not be added or completed until the specification is nearing beta.

@@ Line 17: / Line 17: @@
 == User stories ==
+. As a service provider, I want to ensure customer instances are secure.
+. As a user, I want to make sure my instance is protected.
 == Assumptions ==
-User is running [[XenServer]].
+[[NovaSpec]]:xs-inject-networking is present in order for script to get it's input data for the rules.
-User wants to isolate and protect the networking of all of their instances.
-User wants to use Open vSwitch instead of Linux Bridge.
 == Design ==
-You can have subsections that better describe specific parts of the issue.
+Determine which ACLs need to be implemented to block all of the proper traffic.  Need to prevent ARP poisoning, MAC address spoofing, and unauthorized sniffing of traffic for IPv4.  Also need to prevent NDP attacks in IPv6.
 == Implementation ==
-This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
+vif_rules.py is pushed down the [[XenServer]] host on provisioning of host nodes.  Script to enable or disable rules is ran on VM start, reboot, or shutdown.
-=== UI Changes ===
-Should cover changes required to the UI, or specific UI that is required to implement this
 === Code Changes ===
-Code changes should include an overview of what needs to change, and in some cases even the specific details.
+Modifications to vif_rules.py and vif scripts in [[XenServer]] dom0
-=== Migration ===
-Include:
-* data migration, if any
-* redirects from old URLs to new ones, if any
-* how users will be pointed to the new way of doing things, if necessary.
 == Test/Demo Plan ==
 This need not be added or completed until the specification is nearing beta.
-== Unresolved issues ==
-This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
-== BoF agenda and discussion ==
-Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
 ----
 [[Category:Spec]]