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
On 12/14/2012 2:40 PM, RichBos wrote:
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
--
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/scalr-discuss?hl=en.
--
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/scalr-discuss?hl=en.
