Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ace-dev@incubator.apache.org
Date: Thu, 27 Oct 2011 12:50:32 +0000 (UTC)
From: "Denis Koelewijn (Commented) (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Message-ID: 
 <1237156495.24294.1319719832232.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1503434333.11923.1319053511209.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (ACE-191) Provision Glassfish servers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137048#comment-13137048 ] 

Denis Koelewijn commented on ACE-191:
-------------------------------------

The current composition of the ace-target-devserver always includes de amazon-nodelauncher. This component, on startup, always connects directly to amazon, with in my case, incorrect credentials. This gives a nasty and lengthy stacktrace in the logfile:
2011.10.27 14:24:29 WARNING - Bundle: org.apache.ace.nodelauncher.amazon - Invocation of 'start' failed. - org.jclouds.rest.AuthorizationException: POST https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 -> HTTP/1.1 401 Unauthorized
	at org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.refineException(ParseAWSErrorFromXmlContent.java:117)
(....) 

Is this as it should be ? I can image Ace being used without deployment to Amazon.... Is the idea to have a separate assembly for deployment to Amazon and for non-Amazon deployment, or will there be one Ace assembly for all kinds of deployments ? In the latter case, it might not be desirable to always connect directly to Amazon on the startup ?
                
> 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: ace-191-pom.patch, ace-nodelauncher-amazon-cfg.patch, 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