On 17.06.2011, at 10:30, Deepak Anupalli wrote:
> From: "Bill Shannon" <bill.shannon_at_oracle.com>
>
>
>> Jevgeni Kabanov wrote on 06/15/2011 11:21 AM:
>>> 2. Also, please let me pass parameters to the JVM, e.g. managing Glassfish
>>> through scripts is impossible. Being able to tune the app server and its JVM
>>> centrally is a must for the cloud.
>>
>> To make standardizing this really useful, we'd want standardized JVM
>> parameters. There are none. A standardized way to pass non-standard
>> parameters isn't as interesting, and encourages non-portable applications.
>>
>> Passing JVM parameters with an application when you deploy the application
>> to the cloud assumes a certain deployment model (one application per JVM)
>> that we're unlikely to require.
>>
>> If people think there's value in standardizing a way to pass non-standard
>> JVM parameters, with no requirement that the application server do anything
>> with them, I suppose we could consider that.
>>
>> Oh, and you *can* set JVM parameters for GlassFish using a script so I'm
>> not sure what your issue is there.
>
> I guess it would make more sense to take up these as part of the standard Configuration model which we have be discussing in the other thread. As part of this configuration, we can consider
> - JVM parameters
> - Deployment/Staging specific properties
> - Multi-tenant model (if we tend to standardize a model for multi-tenancy!)
>
>>
>>> 3. REST API layered over JMX API for deployment, configuration management and
>>> app management. Can't stress that enough.
>>
>> JSR-77 is an EJB API for management. It gave us a standardized protocol
>> for management that wasn't Java specific. Still, JMX proved more popular.
>> There is still no cross-platform standardized protocol for management
>> using JMX. We've been asking for years for a Web Services / SOAP mapping
>> for JMX. Today, using a REST-based protocol might be a better choice.
>>
>> Again, this is a ton of work that we won't be able to do for EE 7.
>
> REST based API for deployment/start/stop is very essential for building a PaaS solution for Java EE. May be this JSR may not be able to build an entire parallel Web Service API for JSR-77 or 88, but still we should expose essential deployment and configuration management functionality required for the Deployer/Application Administrator roles as Web Services in this JSR.
+1. Clouds without REST management / deployment are questionable from practical point of view. And Sun had already a great sample with Hello Clouds at kenai.com