GitHub user kwanggithub opened a pull request:

    https://github.com/apache/cloudstack/pull/151

    CLOUDSTACK-6697: bigswitch networking plugin update

    1. provide compatibility with the Big Cloud Fabric (BCF) controller
       L2 Connectivity Service in both VPC and non-VPC modes
    2. virtual network terminology updates: VNS --> BCF_SEGMENT
    3. uses HTTPS with trust-always certificate handling
    4. topology sync support with BCF controller
    5. support multiple (two) BCF controllers with HA
    6. support VM migration
    7. support Firewall, Static NAT, and Source NAT with NAT enabled option
    8. add VifDriver for Indigo Virtual Switch (IVS)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kwanggithub/cloudstack feature_bigswitch

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/151.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #151
    
----
commit de823568db9be289c0ba2d58c8a13e06a027f183
Author: KC Wang <kuangching.w...@gmail.com>
Date:   2014-09-26T21:09:30Z

    CLOUDSTACK-6697: bigswitch networking plugin update
    
    1. provide compatibility with the Big Cloud Fabric (BCF) controller
       L2 Connectivity Service in both VPC and non-VPC modes
    2. virtual network terminology updates: VNS --> BCF_SEGMENT
    3. uses HTTPS with trust-always certificate handling
    4. topology sync support with BCF controller
    5. support multiple (two) BCF controllers with HA
    6. support VM migration
    7. support Firewall, Static NAT, and Source NAT with NAT enabled option
    8. add VifDriver for Indigo Virtual Switch (IVS)

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to