You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Frank Maximus (JIRA)" <ji...@apache.org> on 2017/11/17 10:36:01 UTC

[jira] [Resolved] (CLOUDSTACK-9450) Network Offering for VPC based on DB flag

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frank Maximus resolved CLOUDSTACK-9450.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.11.0.0

> Network Offering for VPC based on DB flag
> -----------------------------------------
>
>                 Key: CLOUDSTACK-9450
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9450
>             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
>             Fix For: 4.11.0.0
>
>
> 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
(v6.4.14#64029)