[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257325#comment-16257325 ] ASF GitHub Bot commented on CLOUDSTACK-9806: rhtyd commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-345317418 @fmaximus thanks for merging, kindly squash merge or rebase/merge in future. 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256805#comment-16256805 ] ASF subversion and git services commented on CLOUDSTACK-9806: - Commit 3eafd0ce52d6c60ac2da812a5b44f2e4e4711cee in cloudstack's branch refs/heads/master from [~fmaximus] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3eafd0c ] Merge pull request #1981 from nuagenetworks/feature/nuage_vpc_selectable_domain_template CLOUDSTACK-9806: Nuage domain template selection per VPC > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256804#comment-16256804 ] ASF subversion and git services commented on CLOUDSTACK-9806: - Commit 880e475f4095908817048d5cfd113dac0732a2fb in cloudstack's branch refs/heads/master from [~sgoeminn] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=880e475 ] CLOUDSTACK-9806: Nuage domain template selection per VPC Co-Authored-By: Prashanth Manthena Co-Authored-By: Frank Maximus Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-9806 Design Document: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Nuage+domain+template+selection+per+VPC > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256803#comment-16256803 ] ASF subversion and git services commented on CLOUDSTACK-9806: - Commit 880e475f4095908817048d5cfd113dac0732a2fb in cloudstack's branch refs/heads/master from [~sgoeminn] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=880e475 ] CLOUDSTACK-9806: Nuage domain template selection per VPC Co-Authored-By: Prashanth Manthena Co-Authored-By: Frank Maximus Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-9806 Design Document: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Nuage+domain+template+selection+per+VPC > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255796#comment-16255796 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-345029232 Trillian test result (tid-1656) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 29407 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1981-t1656-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_host_annotations.py Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py Test completed. 59 look OK, 4 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_01_vpc_remote_access_vpn | `Failure` | 55.98 | test_vpc_vpn.py test_02_redundant_VPC_default_routes | `Failure` | 863.82 | test_vpc_redundant.py test_04_rvpc_privategw_static_routes | `Failure` | 248.42 | test_privategw_acl.py test_03_vpc_privategw_restart_vpc_cleanup | `Failure` | 162.87 | test_privategw_acl.py test_02_vpc_privategw_static_routes | `Failure` | 167.90 | test_privategw_acl.py test_01_vpc_privategw_acl | `Failure` | 51.56 | test_privategw_acl.py test_05_add_annotation_for_invalid_entityType | `Error` | 0.07 | test_host_annotations.py test_change_service_offering_for_vm_with_snapshots | Skipped | 0.00 | test_vm_snapshots.py test_09_copy_delete_template | Skipped | 0.01 | test_templates.py test_06_copy_template | Skipped | 0.00 | test_templates.py test_static_role_account_acls | Skipped | 0.03 | test_staticroles.py test_11_ss_nfs_version_on_ssvm | Skipped | 0.03 | test_ssvm.py test_01_scale_vm | Skipped | 0.00 | test_scale_vm.py test_01_primary_storage_iscsi | Skipped | 0.09 | test_primary_storage.py test_vm_nic_adapter_vmxnet3 | Skipped | 0.00 | test_nic_adapter_type.py test_03_nic_multiple_vmware | Skipped | 1.24 | test_nic.py test_nested_virtualization_vmware | Skipped | 0.00 | test_nested_virtualization.py test_06_copy_iso | Skipped | 0.00 | test_iso.py test_list_ha_for_host_valid | Skipped | 0.02 | test_hostha_simulator.py test_list_ha_for_host_invalid | Skipped | 0.02 | test_hostha_simulator.py test_list_ha_for_host | Skipped | 0.02 | test_hostha_simulator.py test_hostha_enable_feature_without_setting_provider | Skipped | 0.02 | test_hostha_simulator.py test_hostha_enable_feature_valid | Skipped | 0.02 | test_hostha_simulator.py test_hostha_disable_feature_valid | Skipped | 0.02 | test_hostha_simulator.py test_hostha_configure_invalid_provider | Skipped | 0.02 | test_hostha_simulator.py test_hostha_configure_default_driver | Skipped | 0.02 | test_hostha_simulator.py test_ha_verify_fsm_recovering | Skipped | 0.02 | test_hostha_simulator.py test_ha_verify_fsm_fenced | Skipped | 0.02 | test_hostha_simulator.py test_ha_verify_fsm_degraded | Skipped | 0.02 | test_hostha_simulator.py test_ha_verify_fsm_available | Skipped | 0.02 | test_hostha_simulator.py test_ha_multiple_mgmt_server_ownership | Skipped | 0.02 | test_hostha_simulator.py test_ha_list_providers | Skipped | 0.02 | test_hostha_simulator.py test_ha_enable_feature_invalid | Skipped | 0.02 | test_hostha_simulator.py test_ha_disable_feature_invalid | Skipped | 0.02 | test_hostha_simulator.py test_ha_configure_enabledisable_across_clusterzones | Skipped | 0.02 | test_hostha_simulator.py test_configure_ha_provider_valid | Skipped | 0.02 | test_hostha_simulator.py test_configure_ha_provider_invalid | Skipped | 0.02 | test_hostha_simulator.py test_deploy_vgpu_enabled_vm | Skipped | 0.03 | test_deploy_vgpu_enabled_vm.py test_3d_gpu_support | Skipped | 0.03 | test_deploy_vgpu_enabled_vm.py 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 > 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 (Virtua
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255121#comment-16255121 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-344887776 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255120#comment-16255120 ] ASF GitHub Bot commented on CLOUDSTACK-9806: borisstoyanov commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-344887676 @blueorangutan test 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255118#comment-16255118 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-344887369 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1262 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255083#comment-16255083 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-344881598 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255082#comment-16255082 ] ASF GitHub Bot commented on CLOUDSTACK-9806: borisstoyanov commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-344881413 @blueorangutan package 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253706#comment-16253706 ] ASF GitHub Bot commented on CLOUDSTACK-9806: sgoeminn commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-344641295 @rhtyd Thanks for reviewing! I addressed all your comments. 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253148#comment-16253148 ] ASF GitHub Bot commented on CLOUDSTACK-9806: rhtyd commented on a change in pull request #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#discussion_r151065901 ## File path: plugins/network-elements/nuage-vsp/src/com/cloud/api/commands/ListNuageVspDomainTemplatesCmd.java ## @@ -0,0 +1,118 @@ +// +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. +// + +package com.cloud.api.commands; + +import com.cloud.api.response.NuageVspDomainTemplateResponse; +import com.cloud.exception.ConcurrentOperationException; +import com.cloud.exception.InsufficientCapacityException; +import com.cloud.exception.InvalidParameterValueException; +import com.cloud.exception.ResourceAllocationException; +import com.cloud.exception.ResourceUnavailableException; +import com.cloud.network.manager.NuageVspManager; +import com.cloud.utils.exception.CloudRuntimeException; +import org.apache.cloudstack.acl.RoleType; +import org.apache.cloudstack.api.APICommand; +import org.apache.cloudstack.api.ApiConstants; +import org.apache.cloudstack.api.ApiErrorCode; +import org.apache.cloudstack.api.BaseCmd; +import org.apache.cloudstack.api.BaseResponse; +import org.apache.cloudstack.api.Parameter; +import org.apache.cloudstack.api.ServerApiException; +import org.apache.cloudstack.api.response.DomainResponse; +import org.apache.cloudstack.api.response.ListResponse; +import org.apache.cloudstack.api.response.PhysicalNetworkResponse; +import org.apache.cloudstack.api.response.ZoneResponse; + +import javax.inject.Inject; +import java.util.List; Review comment: @sgoeminn newline here please, thanks. 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253147#comment-16253147
]
ASF GitHub Bot commented on CLOUDSTACK-9806:
rhtyd commented on a change in pull request #1981: CLOUDSTACK-9806: Nuage
domain template selection per VPC
URL: https://github.com/apache/cloudstack/pull/1981#discussion_r151065868
##
File path:
plugins/network-elements/nuage-vsp/src/com/cloud/api/commands/ListNuageVspDomainTemplatesCmd.java
##
@@ -0,0 +1,118 @@
+//
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+//
+
+package com.cloud.api.commands;
+
+import com.cloud.api.response.NuageVspDomainTemplateResponse;
+import com.cloud.exception.ConcurrentOperationException;
+import com.cloud.exception.InsufficientCapacityException;
+import com.cloud.exception.InvalidParameterValueException;
+import com.cloud.exception.ResourceAllocationException;
+import com.cloud.exception.ResourceUnavailableException;
+import com.cloud.network.manager.NuageVspManager;
+import com.cloud.utils.exception.CloudRuntimeException;
+import org.apache.cloudstack.acl.RoleType;
+import org.apache.cloudstack.api.APICommand;
+import org.apache.cloudstack.api.ApiConstants;
+import org.apache.cloudstack.api.ApiErrorCode;
+import org.apache.cloudstack.api.BaseCmd;
+import org.apache.cloudstack.api.BaseResponse;
+import org.apache.cloudstack.api.Parameter;
+import org.apache.cloudstack.api.ServerApiException;
+import org.apache.cloudstack.api.response.DomainResponse;
+import org.apache.cloudstack.api.response.ListResponse;
+import org.apache.cloudstack.api.response.PhysicalNetworkResponse;
+import org.apache.cloudstack.api.response.ZoneResponse;
+
+import javax.inject.Inject;
+import java.util.List;
+@APICommand(name = ListNuageVspDomainTemplatesCmd.APINAME, responseObject =
BaseResponse.class, description = "Lists Nuage VSP domain templates", since =
"4.11", responseHasSensitiveInfo = false, authorized = {RoleType.Admin,
RoleType.DomainAdmin, RoleType.User})
+public class ListNuageVspDomainTemplatesCmd extends BaseCmd {
+static final String APINAME = "listNuageVspDomainTemplates";
Review comment:
@sgoeminn thanks, LGTM. Please follow the same across other Cmd
implementations.
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
> 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 creat
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253149#comment-16253149
]
ASF GitHub Bot commented on CLOUDSTACK-9806:
rhtyd commented on a change in pull request #1981: CLOUDSTACK-9806: Nuage
domain template selection per VPC
URL: https://github.com/apache/cloudstack/pull/1981#discussion_r151065954
##
File path:
plugins/network-elements/nuage-vsp/src/com/cloud/api/commands/ListNuageVspDomainTemplatesCmd.java
##
@@ -0,0 +1,118 @@
+//
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+//
+
+package com.cloud.api.commands;
+
+import com.cloud.api.response.NuageVspDomainTemplateResponse;
+import com.cloud.exception.ConcurrentOperationException;
+import com.cloud.exception.InsufficientCapacityException;
+import com.cloud.exception.InvalidParameterValueException;
+import com.cloud.exception.ResourceAllocationException;
+import com.cloud.exception.ResourceUnavailableException;
+import com.cloud.network.manager.NuageVspManager;
+import com.cloud.utils.exception.CloudRuntimeException;
+import org.apache.cloudstack.acl.RoleType;
+import org.apache.cloudstack.api.APICommand;
+import org.apache.cloudstack.api.ApiConstants;
+import org.apache.cloudstack.api.ApiErrorCode;
+import org.apache.cloudstack.api.BaseCmd;
+import org.apache.cloudstack.api.BaseResponse;
+import org.apache.cloudstack.api.Parameter;
+import org.apache.cloudstack.api.ServerApiException;
+import org.apache.cloudstack.api.response.DomainResponse;
+import org.apache.cloudstack.api.response.ListResponse;
+import org.apache.cloudstack.api.response.PhysicalNetworkResponse;
+import org.apache.cloudstack.api.response.ZoneResponse;
+
+import javax.inject.Inject;
+import java.util.List;
+@APICommand(name = ListNuageVspDomainTemplatesCmd.APINAME, responseObject =
BaseResponse.class, description = "Lists Nuage VSP domain templates", since =
"4.11", responseHasSensitiveInfo = false, authorized = {RoleType.Admin,
RoleType.DomainAdmin, RoleType.User})
+public class ListNuageVspDomainTemplatesCmd extends BaseCmd {
+static final String APINAME = "listNuageVspDomainTemplates";
+
+@Inject
+private NuageVspManager _nuageVspManager;
+
+/
+ API parameters /
+/
+
+@Parameter(name = ApiConstants.DOMAIN_ID, type = CommandType.UUID,
entityType = DomainResponse.class,
+description = "the domain ID")
+private Long domainId;
+
+@Parameter(name = ApiConstants.PHYSICAL_NETWORK_ID, type =
CommandType.UUID, entityType = PhysicalNetworkResponse.class,
+description = "the physical network ID")
+private Long physicalNetworkId;
+
+@Parameter(name = ApiConstants.ZONE_ID, type = CommandType.UUID,
entityType = ZoneResponse.class,
+description = "the zone ID")
+private Long zoneId;
+
+@Parameter(name = ApiConstants.KEYWORD, type = CommandType.STRING,
+description = "filters the domain templates which contain the keyword")
+private String keyword;
+
+/
+/// Accessors ///
+/
+
+public String getKeyword() {
+return keyword;
+}
+
+public Long getDomainId() {
+return domainId;
+}
+
+public Long getPhysicalNetworkId() {
+return physicalNetworkId;
+}
+
+public Long getZoneId() { return zoneId; }
+/
Review comment:
@sgoeminn fix indents and newlines please.
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
> Nuage domain template selection per VPC
> ---
>
> Ke
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253146#comment-16253146
]
ASF GitHub Bot commented on CLOUDSTACK-9806:
rhtyd commented on a change in pull request #1981: CLOUDSTACK-9806: Nuage
domain template selection per VPC
URL: https://github.com/apache/cloudstack/pull/1981#discussion_r151065766
##
File path:
plugins/network-elements/nuage-vsp/src/com/cloud/api/commands/AssociateNuageVspDomainTemplateCmd.java
##
@@ -0,0 +1,113 @@
+//
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+//
+
+package com.cloud.api.commands;
+
+import com.cloud.exception.ConcurrentOperationException;
+import com.cloud.exception.InsufficientCapacityException;
+import com.cloud.exception.InvalidParameterValueException;
+import com.cloud.exception.ResourceAllocationException;
+import com.cloud.exception.ResourceUnavailableException;
+import com.cloud.network.manager.NuageVspManager;
+import com.cloud.utils.exception.CloudRuntimeException;
+
+import org.apache.cloudstack.acl.RoleType;
+import org.apache.cloudstack.api.APICommand;
+import org.apache.cloudstack.api.ApiConstants;
+import org.apache.cloudstack.api.ApiErrorCode;
+import org.apache.cloudstack.api.BaseCmd;
+import org.apache.cloudstack.api.Parameter;
+import org.apache.cloudstack.api.ServerApiException;
+import org.apache.cloudstack.api.response.PhysicalNetworkResponse;
+import org.apache.cloudstack.api.response.SuccessResponse;
+import org.apache.cloudstack.api.response.VpcResponse;
+import org.apache.cloudstack.api.response.ZoneResponse;
+import org.apache.cloudstack.context.CallContext;
+import org.apache.log4j.Logger;
+
+import javax.inject.Inject;
+
+@APICommand(name = "associateNuageVspDomainTemplate", responseObject =
SuccessResponse.class, description = "associate a vpc with a domain template",
authorized = {RoleType.Admin, RoleType.DomainAdmin, RoleType.User})
+public class AssociateNuageVspDomainTemplateCmd extends BaseCmd {
+private static final Logger s_logger =
Logger.getLogger(AssociateNuageVspDomainTemplateCmd.class.getName());
+private static final String s_name =
"associatenuagevspdomaintemplateresponse";
Review comment:
@sgoeminn this still does not declare use `APINAME` as a reference/usage
pattern as seen in recent/modern API implementations such as ListRolesCmd etc.
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
> 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 templ
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253144#comment-16253144 ] ASF GitHub Bot commented on CLOUDSTACK-9806: rhtyd commented on a change in pull request #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#discussion_r151065651 ## File path: plugins/network-elements/nuage-vsp/src/com/cloud/api/commands/AssociateNuageVspDomainTemplateCmd.java ## @@ -0,0 +1,113 @@ +// +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. +// + +package com.cloud.api.commands; + +import com.cloud.exception.ConcurrentOperationException; +import com.cloud.exception.InsufficientCapacityException; +import com.cloud.exception.InvalidParameterValueException; +import com.cloud.exception.ResourceAllocationException; +import com.cloud.exception.ResourceUnavailableException; +import com.cloud.network.manager.NuageVspManager; +import com.cloud.utils.exception.CloudRuntimeException; + +import org.apache.cloudstack.acl.RoleType; +import org.apache.cloudstack.api.APICommand; +import org.apache.cloudstack.api.ApiConstants; +import org.apache.cloudstack.api.ApiErrorCode; +import org.apache.cloudstack.api.BaseCmd; +import org.apache.cloudstack.api.Parameter; +import org.apache.cloudstack.api.ServerApiException; +import org.apache.cloudstack.api.response.PhysicalNetworkResponse; +import org.apache.cloudstack.api.response.SuccessResponse; +import org.apache.cloudstack.api.response.VpcResponse; +import org.apache.cloudstack.api.response.ZoneResponse; +import org.apache.cloudstack.context.CallContext; +import org.apache.log4j.Logger; + +import javax.inject.Inject; Review comment: @sgoeminn fix indent please. 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253108#comment-16253108 ] ASF GitHub Bot commented on CLOUDSTACK-9806: smeetsr commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-344521891 After above commit , again I did a rerun of test_nuage_vpc_domain_template.py and all tests were successful. 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 5290.439s OK 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 > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253105#comment-16253105
]
ASF GitHub Bot commented on CLOUDSTACK-9806:
sgoeminn commented on a change in pull request #1981: CLOUDSTACK-9806: Nuage
domain template selection per VPC
URL: https://github.com/apache/cloudstack/pull/1981#discussion_r151059953
##
File path:
plugins/network-elements/nuage-vsp/src/com/cloud/api/commands/ListNuageVspDomainTemplatesCmd.java
##
@@ -0,0 +1,110 @@
+//
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+//
+
+package com.cloud.api.commands;
+
+import com.cloud.api.response.NuageVspDomainTemplateResponse;
+import com.cloud.exception.ConcurrentOperationException;
+import com.cloud.exception.InsufficientCapacityException;
+import com.cloud.exception.InvalidParameterValueException;
+import com.cloud.exception.ResourceAllocationException;
+import com.cloud.exception.ResourceUnavailableException;
+import com.cloud.network.manager.NuageVspManager;
+import com.cloud.utils.exception.CloudRuntimeException;
+import org.apache.cloudstack.acl.RoleType;
+import org.apache.cloudstack.api.APICommand;
+import org.apache.cloudstack.api.ApiConstants;
+import org.apache.cloudstack.api.ApiErrorCode;
+import org.apache.cloudstack.api.BaseListCmd;
+import org.apache.cloudstack.api.BaseResponse;
+import org.apache.cloudstack.api.Parameter;
+import org.apache.cloudstack.api.ServerApiException;
+import org.apache.cloudstack.api.response.DomainResponse;
+import org.apache.cloudstack.api.response.ListResponse;
+import org.apache.cloudstack.api.response.PhysicalNetworkResponse;
+import org.apache.cloudstack.api.response.ZoneResponse;
+import org.apache.log4j.Logger;
+
+import javax.inject.Inject;
+import java.util.List;
+
+@APICommand(name = "listNuageVspDomainTemplates", responseObject =
BaseResponse.class, description = "Lists Nuage VSP domain templates",
authorized = {RoleType.Admin, RoleType.DomainAdmin, RoleType.User})
+public class ListNuageVspDomainTemplatesCmd extends BaseListCmd {
Review comment:
@rhtyd I made it aligned with the ListRolesCmd implementation.
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
> 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 ac
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238530#comment-16238530 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-341845861 Trillian test result (tid-1609) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 28080 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1981-t1609-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_host_annotations.py Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py Test completed. 60 look OK, 3 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_01_vpc_remote_access_vpn | `Failure` | 60.90 | test_vpc_vpn.py test_04_rvpc_privategw_static_routes | `Failure` | 243.34 | test_privategw_acl.py test_03_vpc_privategw_restart_vpc_cleanup | `Failure` | 117.63 | test_privategw_acl.py test_02_vpc_privategw_static_routes | `Failure` | 173.01 | test_privategw_acl.py test_01_vpc_privategw_acl | `Failure` | 56.67 | test_privategw_acl.py test_05_add_annotation_for_invalid_entityType | `Error` | 0.07 | test_host_annotations.py test_change_service_offering_for_vm_with_snapshots | Skipped | 0.00 | test_vm_snapshots.py test_09_copy_delete_template | Skipped | 0.02 | test_templates.py test_06_copy_template | Skipped | 0.00 | test_templates.py test_static_role_account_acls | Skipped | 0.02 | test_staticroles.py test_11_ss_nfs_version_on_ssvm | Skipped | 0.02 | test_ssvm.py test_01_scale_vm | Skipped | 0.00 | test_scale_vm.py test_01_primary_storage_iscsi | Skipped | 0.09 | test_primary_storage.py test_vm_nic_adapter_vmxnet3 | Skipped | 0.00 | test_nic_adapter_type.py test_03_nic_multiple_vmware | Skipped | 1.07 | test_nic.py test_nested_virtualization_vmware | Skipped | 0.00 | test_nested_virtualization.py test_06_copy_iso | Skipped | 0.00 | test_iso.py test_list_ha_for_host_valid | Skipped | 0.03 | test_hostha_simulator.py test_list_ha_for_host_invalid | Skipped | 0.02 | test_hostha_simulator.py test_list_ha_for_host | Skipped | 0.03 | test_hostha_simulator.py test_hostha_enable_feature_without_setting_provider | Skipped | 0.04 | test_hostha_simulator.py test_hostha_enable_feature_valid | Skipped | 0.03 | test_hostha_simulator.py test_hostha_disable_feature_valid | Skipped | 0.03 | test_hostha_simulator.py test_hostha_configure_invalid_provider | Skipped | 0.02 | test_hostha_simulator.py test_hostha_configure_default_driver | Skipped | 0.03 | test_hostha_simulator.py test_ha_verify_fsm_recovering | Skipped | 0.03 | test_hostha_simulator.py test_ha_verify_fsm_fenced | Skipped | 0.02 | test_hostha_simulator.py test_ha_verify_fsm_degraded | Skipped | 0.02 | test_hostha_simulator.py test_ha_verify_fsm_available | Skipped | 0.02 | test_hostha_simulator.py test_ha_multiple_mgmt_server_ownership | Skipped | 0.02 | test_hostha_simulator.py test_ha_list_providers | Skipped | 0.02 | test_hostha_simulator.py test_ha_enable_feature_invalid | Skipped | 0.02 | test_hostha_simulator.py test_ha_disable_feature_invalid | Skipped | 0.02 | test_hostha_simulator.py test_ha_configure_enabledisable_across_clusterzones | Skipped | 0.02 | test_hostha_simulator.py test_configure_ha_provider_valid | Skipped | 0.03 | test_hostha_simulator.py test_configure_ha_provider_invalid | Skipped | 0.03 | test_hostha_simulator.py test_deploy_vgpu_enabled_vm | Skipped | 0.05 | test_deploy_vgpu_enabled_vm.py test_3d_gpu_support | Skipped | 0.04 | test_deploy_vgpu_enabled_vm.py 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 > 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 >Priority: Major > > 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
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237699#comment-16237699 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-341728270 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests 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 > 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 >Priority: Major > > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237698#comment-16237698 ] ASF GitHub Bot commented on CLOUDSTACK-9806: rhtyd commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-341728142 @blueorangutan test 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 > 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 >Priority: Major > > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237697#comment-16237697
]
ASF GitHub Bot commented on CLOUDSTACK-9806:
rhtyd commented on a change in pull request #1981: CLOUDSTACK-9806: Nuage
domain template selection per VPC
URL: https://github.com/apache/cloudstack/pull/1981#discussion_r148805980
##
File path:
plugins/network-elements/nuage-vsp/src/com/cloud/api/commands/ListNuageVspDomainTemplatesCmd.java
##
@@ -0,0 +1,110 @@
+//
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+//
+
+package com.cloud.api.commands;
+
+import com.cloud.api.response.NuageVspDomainTemplateResponse;
+import com.cloud.exception.ConcurrentOperationException;
+import com.cloud.exception.InsufficientCapacityException;
+import com.cloud.exception.InvalidParameterValueException;
+import com.cloud.exception.ResourceAllocationException;
+import com.cloud.exception.ResourceUnavailableException;
+import com.cloud.network.manager.NuageVspManager;
+import com.cloud.utils.exception.CloudRuntimeException;
+import org.apache.cloudstack.acl.RoleType;
+import org.apache.cloudstack.api.APICommand;
+import org.apache.cloudstack.api.ApiConstants;
+import org.apache.cloudstack.api.ApiErrorCode;
+import org.apache.cloudstack.api.BaseListCmd;
+import org.apache.cloudstack.api.BaseResponse;
+import org.apache.cloudstack.api.Parameter;
+import org.apache.cloudstack.api.ServerApiException;
+import org.apache.cloudstack.api.response.DomainResponse;
+import org.apache.cloudstack.api.response.ListResponse;
+import org.apache.cloudstack.api.response.PhysicalNetworkResponse;
+import org.apache.cloudstack.api.response.ZoneResponse;
+import org.apache.log4j.Logger;
+
+import javax.inject.Inject;
+import java.util.List;
+
+@APICommand(name = "listNuageVspDomainTemplates", responseObject =
BaseResponse.class, description = "Lists Nuage VSP domain templates",
authorized = {RoleType.Admin, RoleType.DomainAdmin, RoleType.User})
+public class ListNuageVspDomainTemplatesCmd extends BaseListCmd {
Review comment:
@prashanthvarma have a look at ListRolesCmd and other newer
implemented/added API for refering to a more modern CloudStack API
implementation pattern.
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
> 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
>Priority: Major
>
> 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.
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236110#comment-16236110 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-341486391 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1192 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 > 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 >Priority: Major > > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236059#comment-16236059 ] ASF GitHub Bot commented on CLOUDSTACK-9806: blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-341478156 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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 > 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 >Priority: Major > > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236057#comment-16236057 ] ASF GitHub Bot commented on CLOUDSTACK-9806: rhtyd commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-341477821 @blueorangutan package 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 > 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 >Priority: Major > > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235900#comment-16235900 ] ASF GitHub Bot commented on CLOUDSTACK-9806: fmaximus commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per VPC URL: https://github.com/apache/cloudstack/pull/1981#issuecomment-341457355 retest this please 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 > 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 >Priority: Major > > 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.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897122#comment-15897122 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1981 @borisstoyanov yes, I also did cross check the test failures. Thanks for the investigation. > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895814#comment-15895814 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1981 Thanks, the tests failures looks to be not related to these changes. @prashanthvarma > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892653#comment-15892653 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1981 Trillian test result (tid-923) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 28590 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1981-t923-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py Test completed. 47 look ok, 2 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_04_rvpc_privategw_static_routes | `Failure` | 340.82 | test_privategw_acl.py test_02_list_snapshots_with_removed_data_store | `Error` | 0.04 | test_snapshots.py test_01_vpc_site2site_vpn | Success | 155.14 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 66.11 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 250.96 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 289.26 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 538.34 | test_vpc_router_nics.py test_05_rvpc_multi_tiers | Success | 518.24 | test_vpc_redundant.py test_04_rvpc_network_garbage_collector_nics | Success | 1420.40 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 539.12 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 749.50 | test_vpc_redundant.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1281.13 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 156.50 | test_volumes.py test_08_resize_volume | Success | 156.75 | test_volumes.py test_07_resize_fail | Success | 161.45 | test_volumes.py test_06_download_detached_volume | Success | 156.25 | test_volumes.py test_05_detach_volume | Success | 155.81 | test_volumes.py test_04_delete_attached_volume | Success | 151.22 | test_volumes.py test_03_download_attached_volume | Success | 156.33 | test_volumes.py test_02_attach_volume | Success | 124.19 | test_volumes.py test_01_create_volume | Success | 711.30 | test_volumes.py test_03_delete_vm_snapshots | Success | 275.23 | test_vm_snapshots.py test_02_revert_vm_snapshots | Success | 95.75 | test_vm_snapshots.py test_01_create_vm_snapshots | Success | 158.74 | test_vm_snapshots.py test_deploy_vm_multiple | Success | 273.07 | test_vm_life_cycle.py test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.03 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 26.66 | test_vm_life_cycle.py test_09_expunge_vm | Success | 125.24 | test_vm_life_cycle.py test_08_migrate_vm | Success | 56.02 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.10 | test_vm_life_cycle.py test_06_destroy_vm | Success | 130.86 | test_vm_life_cycle.py test_03_reboot_vm | Success | 125.88 | test_vm_life_cycle.py test_02_start_vm | Success | 10.17 | test_vm_life_cycle.py test_01_stop_vm | Success | 40.33 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 50.53 | test_templates.py test_08_list_system_templates | Success | 0.03 | test_templates.py test_07_list_public_templates | Success | 0.06 | test_templates.py test_05_template_permissions | Success | 0.06 | test_templates.py test_04_extract_template | Success | 5.15 | test_templates.py test_03_delete_template | Success | 5.11 | test_templates.py test_02_edit_template | Success | 90.18 | test_templates.py test_01_create_template | Success | 25.38 | test_templates.py test_10_destroy_cpvm | Success | 161.81 | test_ssvm.py test_09_destroy_ssvm | Success | 163.58 | test_ssvm.py test_08_reboot_cpvm | Success | 131.62 | test_ssvm.py test_07_reboot_ssvm | Success | 133.82 | test_ssvm.py test_06_stop_cpvm | Success | 131.78 | test_ssvm.py test_05_stop_ssvm | Success | 134.30 | test_ssvm.py test_04_cpvm_internals | Success | 1.35 | test_ssvm.py test_03_ssvm_internals | Success | 3.34 | test_ssvm.py test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py test_01_list_sec_storage_vm | Success | 0.14 | test_ssvm.py test_01_snapshot_root_disk | Success | 11.12 | test_snapshots.py test_04_change_offering_small | Success | 239.71 | test_service_offerings.py test_03_delete_service_offering | Success | 0.05 | test_service_offerings.py test_02_edit_service_offering | Success | 0.06 | test_service_offerings.py test_01_create_service_offering | Success | 0.11 | test_service_offering
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892024#comment-15892024 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1981 @borisstoyanov I am glad you liked the PR, we (@nuagenetworks) made it a practice to add and run integration tests that test the changes we propose/make in a PR. Moreover, we internally qualify through regressions the whole system with those changes for both Nuage VSP and native ACS setups/environments where necessary. Thank you for kicking the regression tests. Please do also code review the PR. > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891938#comment-15891938 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1981 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891933#comment-15891933 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1981 @blueorangutan test > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891814#comment-15891814 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1981 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-555 > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891786#comment-15891786 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1981 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891785#comment-15891785 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1981 Thanks for this good looking PR @prashanthvarma, it's really great that you provided integration tests. I'll package and kick regression tests to check if everything else is working fine with these changes. @blueorangutan package > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ 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 Atlassi
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889972#comment-15889972 ] ASF GitHub Bot commented on CLOUDSTACK-9806: Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1981 Design document for this feature: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Nuage+domain+template+selection+per+VPC > 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)
[jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889971#comment-15889971 ] ASF GitHub Bot commented on CLOUDSTACK-9806: GitHub user prashanthvarma opened a pull request: https://github.com/apache/cloudstack/pull/1981 CLOUDSTACK-9806: Nuage domain template selection per VPC Co-Authored-By: Prashanth Manthena Co-Authored-By: Frank Maximus You can merge this pull request into a Git repository by running: $ git pull https://github.com/nuagenetworks/cloudstack feature/nuage_vpc_selectable_domain_template Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1981.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 #1981 commit 55ce0d91805fc4807952ead3f8160eae589038ab Author: Sigert Goeminne Date: 2016-10-06T12:30:59Z CLOUDSTACK-9806: Nuage domain template selection per VPC Co-Authored-By: Prashanth Manthena Co-Authored-By: Frank Maximus > 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)
