Scalrized Tomcat role?

[RichBos]

Hi all

I could do with a Tomcat app based role, just wondering if I build one in EC2 and 'scalrize' it (import non Scalr server) if that would do the trick? i.e and become manageable for vhosts etc? I've seen the tutorial for creating such using chef but didn't really want to go down that route.

Any thoughts appreciated.

Richard

[Srinivasan Subramanian]

Hi Richard

Starting from scratch and creating a new role is not recommended by the
Scalr team (this was the answer when i wanted to do the same a year ago,
dont know if it has changed, if you search this forum you may find the
old answer!)

Also the scalrizr script depends in an app role on the fact that Apache
is running (not sure if its just port 80 or apache) .. I had a need for
a JBoss role and I simply installed JBoss also in the standard App
role. On that instance i have opened only the JBoss port and apache in
that sense is hidden but Scalr is happy. The disadvantage is that if
Apache is running but JBoss crashes, scalrizr does not recognize it.
This is managed separately by detecting it and using the Scalr API to
terminate the instance so a new one will replace it.

In a nutshell, not straight forward but doable with a few tweaks.

Regards
Srini

> --
> You received this message because you are subscribed to the Google
> Groups "scalr-discuss" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/scalr-discuss/-/oaYw7QvK35UJ.
> To post to this group, send email to scalr-...@googlegroups.com.
> To unsubscribe from this group, send email to
> scalr-discus...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/scalr-discuss?hl=en.

[RichBos]

Ok, I see, that's a shame, I did think the 'import non Scalr server' option would be more accommodating, and it's also a shame there is no Scalr provided Tomcat-app role (when I think there used to be?). 

At present (for this particular project, or even for Tomcat in general) it's looking like AWS Elastic Beanstalk is a better and easier option, unless I went down the chef route, which I don't really want to at this stage.

Many thanks for the advice, it's very much appreciated.

Best regards

Richard.

[Srinivasan Subramanian]

If any of my statements below are incorrect or misleading, I am sure the Scalr team will jump in:)  So please do wait a day or so before deciding on any route you may take.

Cheers
Srini

To view this discussion on the web visit https://groups.google.com/d/msg/scalr-discuss/-/dIYQsr7auWAJ.

[RichBos]

Hi, yes, ideally that would be my preference also however the client in this instance is wanting immediate take-up and I can't afford to spend time on development. As things have transpired I just directed them to Elastic Beanstalk.

Richard

On Sunday, 16 December 2012 22:30:21 UTC, UAflyer wrote:

I would drop it into a sandbox and test it.

we have not put anything in production without this confidence first.

Then we ask questions, but of course answers to questions might make you do it in the first place to help you and the Community