cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Maximus (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-9450) Network Offering for VPC based on DB flag
Date Tue, 09 Aug 2016 12:15:20 GMT

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

Frank Maximus reassigned CLOUDSTACK-9450:
-----------------------------------------

    Assignee: Frank Maximus  (was: Kris Sterckx)

> 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
>
> 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.3.4#6332)

Mime
View raw message