We can always put out a OSS components.xml and a full components.xml. components.xmls can inherit from each other so the full componetns.xml won't have to redefine everything just the things that changed.
The user can specify which one to use via an environment variable, "cloud-stack-components-specification". Put this in the properties file and set the value to the path to components.xml cloudstack should use. --Alex > -----Original Message----- > From: Hugo Trippaers [mailto:[email protected]] > Sent: Thursday, September 06, 2012 10:02 AM > To: [email protected] > Subject: [DISCUSS] how about components.xml > > Hey, > > While testing the my fresh RPMs I ran into some trouble starting the > management server. The components.xml.in file references the elements > and classes for components that we put on the nonoss list. So they might not > be available after installation and should not be used by default I think. > > I would propose to strip them from the components.xml. However I have no > easy solution on how an end-user would add them later other than editing > the file by hand. > > Any ideas? > > Cheers, > > Hugo
