incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: [DISCUSS] how about components.xml
Date Thu, 06 Sep 2012 17:14:39 GMT
On Thu, Sep 6, 2012 at 1:11 PM, Alex Huang <Alex.Huang@citrix.com> wrote:
> CloudStack automatically looks for components.xml in the classpath if the property is
not defined.  So we can put out the OSS version, it will be the default.
>
> We just need a way for people to download the full (non compliant) version and give instructions
on how to set the property.

There's no reason to not distribute it with the release, we would just
need instructions (like you said) for how to swap it in.

> --Alex
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Thursday, September 06, 2012 10:08 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] how about components.xml
>>
>> On Thu, Sep 6, 2012 at 1:05 PM, Alex Huang <Alex.Huang@citrix.com> wrote:
>> > 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.
>>
>> And could we default to the OSS version?
>>
>> > --Alex
>> >
>> >> -----Original Message-----
>> >> From: Hugo Trippaers [mailto:HTrippaers@schubergphilis.com]
>> >> Sent: Thursday, September 06, 2012 10:02 AM
>> >> To: cloudstack-dev@incubator.apache.org
>> >> 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
>> >
>

Mime
View raw message