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 Wed, 15 Nov 2017 14:57:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-9450:

fmaximus commented on issue #2005: CLOUDSTACK-9450: Network Offering for VPC based on DB flag
   Our internal CI was OK, and the errors reported by Trillian don't seem related to the changes,

   and the XenServer errors are the same as in the baseline #2289.

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:

> 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