cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9806) Nuage domain template selection per VPC
Date Fri, 03 Nov 2017 15:01:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-9806:

blueorangutan commented on issue #1981: CLOUDSTACK-9806: Nuage domain template selection per
   @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:

> Nuage domain template selection per VPC
> ---------------------------------------
>                 Key: CLOUDSTACK-9806
>                 URL:
>             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|]

This message was sent by Atlassian JIRA

View raw message