Hugo,
In the current model, components that are not needed by default are not
present in componentContext.xml. Just in case if you have not noticed, in
4.1, NiciraNvp bean is not enabled by default :). Admin needs to edit
componentContext.xml, to enable a optional component.
Thanks!
On 26/02/13
On Tue, Feb 26, 2013 at 2:55 PM, Hugo Trippaers
wrote:
> Heya Rohit,
>
> Why would a sysadmin need to change this? They should be considered part of
> the source code, any configuration should be done via the config in the
> database or with the *.properties files.
But either way I'm fine, we c
Hey Hugo!
On Tue, Feb 26, 2013 at 2:55 PM, Hugo Trippaers
wrote:
> Heya Rohit,
>
> Why would a sysadmin need to change this? They should be considered part of
> the source code, any configuration should be done via the config in the
> database or with the *.properties files.
I thought we wante
Hi,
For what it's worth, I was under the same impression as Rohit - that
administrators would edit components.xml to fit their deployment.
See for example this snippet from "Extending CloudStack Networking" [1]:
> "Generally, it is expected that the cloud administrator will configure
components.
Heya Rohit,
Why would a sysadmin need to change this? They should be considered part of the
source code, any configuration should be done via the config in the database or
with the *.properties files.
Cheers,
Hugo
> -Original Message-
> From: rohityada...@gmail.com [mailto:rohityada..
