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-9450) Network Offering for VPC based on DB flag
Date Tue, 14 Mar 2017 10:12:41 GMT


ASF GitHub Bot commented on CLOUDSTACK-9450:

GitHub user prashanthvarma opened a pull request:

    CLOUDSTACK-9450: Network Offering for VPC based on DB flag

    Co-Authored-By: Prashanth Manthena
    Design Document:

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

    $ git pull feature/nw_offering_for_vpc

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

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

    This closes #2005


> Network Offering for VPC based on DB flag
> -----------------------------------------
>                 Key: CLOUDSTACK-9450
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, UI
>    Affects Versions: 4.9.0
>            Reporter: Frank Maximus
>            Assignee: Frank Maximus
> In the NuageVsp provider, based on the review comments, we don't have a separate Provider
for VPC.
> This means that it's impossible to determine if a network offering is for VPC or not,
purely based on inspection of the services and providers.
> To be able to support Network Offerings for VPC that are not using any service provided
by a VPC specific provider like VpcVirtualRouter,
> we would like to store this information as part of the offering.
> As the response of createNetworkOffering already has a forvpc attribute we use the same
attribute as part of the request,
> and store the value in the database.

This message was sent by Atlassian JIRA

View raw message