[
https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135415#comment-13135415
]
Paul Bakker commented on ACE-191:
---------------------------------
I agree this shouldn't be hardcode. After discussing some options today I
changed the amazon launcher to have more configuration options. With these
changes, the code is completely generic as before, but can now be configured to
download extra files from either the ACE obr or any external url. This is
sufficient to bootstrap Glassfish, and I expect most other servers too.
WDYT?
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix
> instance. Glassfish contains Felix and in recent versions you can directly
> deploy OSGI bundles as you would do in a normal OSGI container. There are
> some extra features however; for example you can use EJB, JPA and CDI from
> bundles and use the WAB as deployment type besides normal bundles. In the
> future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It
> downloads and unzips GF, changes it's configuration files and installs the
> Ace Management Agent. GF is started using asadmin after that. Besides this I
> changed the Amazon Node Laucher. You can now configure a serverType to either
> DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup
> script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created
> because the official download server is extremely slow. We have to come up
> with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
