Difference between revisions of "XenServerNetworkQoS"

Revision as of 23:29, 31 January 2011

Launchpad Entry: NovaSpec:xs-network-qos
Created:
Contributors:

Summary

Adds the ability to set networking bandwidth capacity limits for each instance. Capacity limits are set based on the bandwidth settings set in flavors.

Release Note

This provides the ability to se

Rationale

User stories

As a service provider, I want to limit the amount of bandwidth provided per instance.
As operations, I want to protect instances from Denial of Service attacks.

Assumptions

Multi NIC and flavors are in place.

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Test/Demo Plan

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

@@ Line 9: / Line 9: @@
 == Release Note ==
-This section should include a paragraph describing the end-user impact of this change.  It is meant to be included in the release notes of the first release in which it is implemented.  (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
+This provides the ability to se
-It is mandatory.
 == Rationale ==
 == User stories ==
-As a service provider, I want to limit the amount of bandwidth provided per instance.
+# As a service provider, I want to limit the amount of bandwidth provided per instance.
+# As operations, I want to protect instances from Denial of Service attacks.
 == Assumptions ==
 Multi NIC and flavors are in place.
@@ Line 29: / Line 28: @@
 This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
-=== 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.
-=== 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]]