cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harikrishna Patnala" <>
Subject Review Request: Fix for CLOUDSTACK-2835: Registering router template and usage of router.template.* configuration parameter
Date Mon, 24 Jun 2013 15:39:29 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for cloudstack, Abhinandan Prateek, Kishan Kavala, and Nitin Mehta.


CLOUDSTACK-2835:  VR Deployement from admin registered template is failing because registered
template type is user. 
Additional parameter "isrouter" in register/update template API for the root admin. True if
registered template is of type ROUTING.

A new template type is introduced named "ROUTING" which is used to deploy router. 
Admin registers a ROUTING type template and provides the value zone/global level configuration
parameters in routing.template.xenserver/kvm/hyperv/vmware/lxc So that router deploys using
that template.
By default router can be deployed by the normal SYSTEM template.

Added upgrade case to update the configuration parameter values routing.template.xenserver/kvm/hyperv/vmware/lxc

This addresses bug CLOUDSTACK-2835.


  api/src/com/cloud/storage/ 16ef019 
  api/src/org/apache/cloudstack/api/ 8ac7c3f 
  api/src/org/apache/cloudstack/api/ b01c8d0 
  api/src/org/apache/cloudstack/api/command/user/template/ 6a8e555

  api/src/org/apache/cloudstack/api/command/user/template/ 9f55f9d 
  engine/schema/src/com/cloud/storage/dao/ e7b85f8 
  engine/schema/src/com/cloud/upgrade/dao/ 8f63a6c 
  server/src/com/cloud/server/ 97bac1b 
  server/src/com/cloud/storage/ 00aab4d 
  server/src/com/cloud/template/ d50d45b 
  server/src/com/cloud/template/ c1f0604 
  server/src/com/cloud/template/ 273614c 



Tested locally.

Registered ROUTING template and checked router deployment by setting the configuration parameter
routing.template.xenserver to the new ROUTING template.
Tested the default behavior of router deployment from SYSTEM template.

Tested upgrade case from 4.1 to 4.2  


Harikrishna Patnala

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message