[jira] [Created] (CLOUDSTACK-8276) Changes in Marvin to get free vlan in a setup when vlan is not returned for an existing network

[Gaurav Aradhye (JIRA)]

Gaurav Aradhye created CLOUDSTACK-8276:
--

 Summary: Changes in Marvin to get free vlan in a setup when vlan 
is not returned for an existing network
 Key: CLOUDSTACK-8276
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8276
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
 Fix For: 4.5.0


listNetworks API previously returned the value for vlan as untagged when vlan 
was not assigned to a network.

Now the vlan attribute itself is not returned in this case.

Make according changes in Marvin.



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

[jira] [Created] (CLOUDSTACK-8275) Deploying vApp(Stack of services/instances) with user defined template from CloudStack

[Rajesh Battala (JIRA)]

Rajesh Battala created CLOUDSTACK-8275:
--

 Summary: Deploying vApp(Stack of services/instances) with user 
defined template from CloudStack
 Key: CLOUDSTACK-8275
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8275
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Rajesh Battala
 Fix For: 4.5.0


This idea will help the cloud admin/user to deploy the Stack of instance which 
can act as his service solution. Use Case: Suppose cloud admin/user wants to 
deploy a web service portal and he has presentation template, logic tier 
template and database template. In the present situation, the user had to 
provision Vm from each template and then do the configuration so that they can 
logically act as one service stack. He has to create a network (deployVR)  
then he has to deploy multiple instances from each template and then later 
configure them to act as one solution.



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