You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Andrija Panic (JIRA)" <ji...@apache.org> on 2015/05/25 14:55:17 UTC
[jira] [Created] (CLOUDSTACK-8510) Last choosen VR Service Offering
not taken into consideration while restarting VPC
Andrija Panic created CLOUDSTACK-8510:
-----------------------------------------
Summary: Last choosen VR Service Offering not taken into consideration while restarting VPC
Key: CLOUDSTACK-8510
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8510
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller, Virtual Router
Affects Versions: 4.4.3
Environment: NA
Reporter: Andrija Panic
We can have different/multiply System Offerings for VR, to i.e. provide differenet VR/NICs speed and different CPU/RAM speed as an option for customer to upgrade, from defauts.
If we change VR System Offering (while VR is stoped) - it gets changed, fine.
BUT when we/user restart VPC, then new VR gets created for customer, but with default Service Offering being selected.
Improvement: When restarting VPC, first check existing Service Offering for existing VR, and then destroy/provision new VR with same Service Offering.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)