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] Hosting CS System Offerings using Oralce/Sun Java VS OpenJDK
Date Thu, 10 Jan 2013 14:56:15 GMT
On Wed, Jan 9, 2013 at 12:51 AM, David Nalley <david@gnsa.us> wrote:
> On Wed, Jan 9, 2013 at 12:46 AM, Prasanna Santhanam <tsp@apache.org> wrote:
>> On Tue, Jan 08, 2013 at 02:51:32PM -0500, Musayev, Ilya wrote:
>>> Alex,
>>>
>>> It's a bit more complex, here is why:
>>>
>>> 1) The build process for CentOS - uses system specific commands that
>>> are only available in RedHat like system (i.e. yum and others).  2)
>>> The build process for Debian - has its own system specific commands
>>> like apt-get, debootstrap and others.
>>>
>>> In order to build the system offering - you CS management server
>>> will be either CentOS/Debian which means you will be successful at
>>> only building one type of system offering - by default.
>>
>> How about puppetize the configuration and installation of these
>> systemvm packages? You could provide those to people who want to
>> build-their-own and pre-built binaries for others.
>>
>>
>
> Yes, this is what we should do IMO, distribute puppet manifests that
> permit creation of the template (including installing the ACS-specific
> bits.

+1 - Puppet or Chef, doesn't really matter to me.  But being able to
specify the config for the system VM seems like the best way to stay
flexible.

Mime
View raw message