cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Meier (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-9445) System offering for VPC VR should be associated to a VPC offering not to Network offering
Date Thu, 04 Aug 2016 13:26:20 GMT

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

Christian Meier updated CLOUDSTACK-9445:
----------------------------------------
    Description: 
A VPC only consists of only one VR (ignoring redundant setups).

Currently, the system offering of a VPC is associated to a network offering, that is instantiated
behind a VPC.
However this behavior is undefined when more than one network with different network offerings
with for example distinctly host tagged system offering are used.

System offerings for VPC VRs should be associated to a VPC through the VPC offering instead
of relying on the network offerings behind the VPC VR.

  was:
A VPC only consists of only one VR (ignoring redundant setups).

Currently, the system offering of a VPC is defined to a network offering, that is instantiated
behind a VPC.
However this behavior is undefined when more than one network with different network offerings
with for example distinctly host tagged system offering are used.

System offerings for VPC VRs should be associated to a VPC through the VPC offering instead
of relying on the network offerings behind the VPC VR.


> System offering for VPC VR should be associated to a VPC offering not to Network offering
> -----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9445
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9445
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.8.0
>            Reporter: Christian Meier
>
> A VPC only consists of only one VR (ignoring redundant setups).
> Currently, the system offering of a VPC is associated to a network offering, that is
instantiated behind a VPC.
> However this behavior is undefined when more than one network with different network
offerings with for example distinctly host tagged system offering are used.
> System offerings for VPC VRs should be associated to a VPC through the VPC offering instead
of relying on the network offerings behind the VPC VR.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message