[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889985#comment-15889985
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9806:
--------------------------------------------

Github user prashanthvarma commented on the issue:

    https://github.com/apache/cloudstack/pull/1981
  
    PEP8 & PyFlakes compliance of our marvin test code:
    
    CloudStack$
    CloudStack$ pep8 test/integration/plugins/nuagevsp/.py
    CloudStack$
    CloudStack$ pyflakes test/integration/plugins/nuagevsp/.py
    CloudStack$
    
    Validations:
    
    Marvin test results:
    
    nosetests --with-marvin --marvin-config=nuage.cfg 
nuagevsp/test_nuage_vsp_domain_template.py
    
    Test Nuage VSP Domain Template selection per VPC ... === TestName: 
test_01_nuage_Domain_Template_selection_per_VPC | Status : SUCCESS ===
    ok
    Test Nuage VSP Domain Template selection per VPC as ROOT domain ... === 
TestName: test_02_nuage_Domain_Template_selection_per_VPC_as_ROOT_user | Status 
: SUCCESS ===
    ok
    Test Nuage VSP Domain Template selection per VPC as domain admin ... === 
TestName: test_03_nuage_Domain_Template_selection_per_VPC_as_domain_admin | 
Status : SUCCESS ===
    ok
    Test Nuage VSP Domain Template selection per VPC as domain ... === 
TestName: test_04_nuage_Domain_Template_selection_per_VPC_as_domain_user | 
Status : SUCCESS ===
    ok
    Test Nuage VSP Domain Template selection per VPC as subdomain admin ... === 
TestName: test_05_nuage_Domain_Template_selection_per_VPC_as_subdom_admin | 
Status : SUCCESS ===
    ok
    Test Nuage VSP Domain Template selection per VPC as subdomain ... === 
TestName: test_06_nuage_Domain_Template_selection_per_VPC_as_subdom_user | 
Status : SUCCESS ===
    ok
    Test Nuage VSP Global Domain Template ... === TestName: 
test_07_nuage_Global_Domain_Template | Status : SUCCESS ===
    ok
    Test Nuage VSP Global Domain Template as ROOT domain regular user ... === 
TestName: test_08_nuage_Global_Domain_Template_as_ROOT_user | Status : SUCCESS 
===
    ok
    Test Nuage VSP Global Domain Template as domain admin user ... === 
TestName: test_09_nuage_Global_Domain_Template_as_domain_admin | Status : 
SUCCESS ===
    ok
    Test Nuage VSP Global Domain Template as domain regular user ... === 
TestName: test_10_nuage_Global_Domain_Template_as_domain_user | Status : 
SUCCESS ===
    ok
    Test Nuage VSP Global Domain Template as subdomain admin user ... === 
TestName: test_11_nuage_Global_Domain_Template_as_subdomain_admin | Status : 
SUCCESS ===
    ok
    Test Nuage VSP Global Domain Template as subdomain regular user ... === 
TestName: test_12_nuage_Global_Domain_Template_as_subdomain_user | Status : 
SUCCESS ===
    ok
    
    ----------------------------------------------------------------------
    Ran 12 tests in 6203.613s
    
    OK
    
    
    [results.txt](https://github.com/apache/cloudstack/files/810482/results.txt)
    [runinfo.txt](https://github.com/apache/cloudstack/files/810483/runinfo.txt)



> Nuage domain template selection per VPC
> ---------------------------------------
>
>                 Key: CLOUDSTACK-9806
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9806
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: UI
>            Reporter: Sigert Goeminne
>            Assignee: Sigert Goeminne
>
> When deploying CloudStack with Nuage VSP (Virtualized Services 
> Plugin/Platform), the Cloud/Network Administrator has the ability to define 
> “Domain Templates” in the Nuage VSP Platform and reuse (and instantiate) 
> those when creating networks inside CloudStack. This allows for predefining 
> advanced networking topologies in the SDN platform, and integrate those 
> seamlessly within the CloudStack workflows, without the need of porting all 
> those SDN capabilities (e.g. GRT leaking, Advanced ACL’s, Service Chaining, 
> ...) into CloudStack.
> Today this mechanism works via global settings and allows for one Nuage VSP 
> Domain Template to be specified per CloudStack Network type (Shared, 
> Isolated, VPC). This is fine for most deployments but it doesn’t leave room 
> for hybrid deployments in which different CloudStack networks need 
> individually differentiated SDN capabilities. Especially for VPC’s it would 
> be nice to have finer grained domain template control.
> With the proposed new features, we add the ability to configure a domain 
> template per VPC, i.e. each VPC created in CloudStack can be configured with 
> a different domain template. We will make this option accessible through the 
> UI also, but applicable to Nuage supporting zones only.
> [Design 
> Document|https://cwiki.apache.org/confluence/display/CLOUDSTACK/Nuage+domain+template+selection+per+VPC]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to