rafaelweingartner closed pull request #11: "yes" for KVM network throttling
URL: https://github.com/apache/cloudstack-documentation/pull/11
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/source/conceptsandterminology/choosing_deployment_architecture.rst 
b/source/conceptsandterminology/choosing_deployment_architecture.rst
index b3a9dec..a218193 100644
--- a/source/conceptsandterminology/choosing_deployment_architecture.rst
+++ b/source/conceptsandterminology/choosing_deployment_architecture.rst
@@ -168,7 +168,7 @@ supported by CloudStack. The following table provides this 
information.
 
+----------------------------------+-----------+--------------+------------+-----+--------+------------+
 | Feature                          | XenServer | vSphere      | KVM - RHEL | 
LXC | HyperV | Bare Metal |
 
+==================================+===========+==============+============+=====+========+============+
-| Network Throttling               | Yes       | Yes          | No         | 
No  | ?      | N/A        |
+| Network Throttling               | Yes       | Yes          | Yes        | 
No  | ?      | N/A        |
 
+----------------------------------+-----------+--------------+------------+-----+--------+------------+
 | Security groups in zones that use| Yes       | No           | Yes        | 
Yes | ?      | No         |
 | basic networking                 |           |              |            |   
  |        |            |


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to