[
https://issues.apache.org/jira/browse/CLOUDSTACK-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256700#comment-16256700
]
ASF subversion and git services commented on CLOUDSTACK-9450:
-------------------------------------------------------------
Commit 14ab69e19a51886b91d77d01eed96de05eb21393 in cloudstack's branch
refs/heads/debian9-systemvmtemplate from [~fmaximus]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=14ab69e ]
Merge pull request #2005 from nuagenetworks/feature/nw_offering_for_vpc
CLOUDSTACK-9450: Network Offering for VPC based on DB flag
> 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.4.14#64029)
