We already have the Angel plan and I currently have a few shell scripts setting
up the site.
But as we get more complex, I am realizing the need for something like
puppet/chef.
We currently have our sites setup in the following setup:
1 LB
2 App (scalable to 5)
Apache2 multiple sites with glusterFS replication layer on each
1 Memcache
2 db
I am currently considering switching to nginx to run our websites instead of
apache.
The setup of glusterFS is the challenging one for me. I am having a difficult
time figuring out how to install gluster on each scaled up host and attache the
correct web folders to it.
My thought is puppet/chef will make my life easier.
John
On Nov 11, 2012, at 8:55 AM, "Srinivasan S" <[email protected]>
wrote:
> If you are signing up for a plan, I guess you can also ask Scalr support for
> help in addition to the community.
>
> Custom role is not possible or too involved. I also had a similar req and
> started on this route but was advised to not do it. So I have taken both app
> and base roles and done addnl customization and use them.
>
> Since my customization needs were not much I actually wrote a couple of shell
> scripts and start them off when the instance boots :) in addition to doing
> other stuff the script also downloads a couple of jars from s3 and deploys
> it.
>
> Srini
> Sent on my BlackBerry® from Vodafone
> From: otherjohn <[email protected]>
> Sender: [email protected]
> Date: Sun, 11 Nov 2012 05:39:33 -0800 (PST)
> To: <[email protected]>
> ReplyTo: [email protected]
> Subject: chef/puppet solo on scalr
>
> Hi all,
> I am trying to look at the best way of going about this with the Angel
> package (10 servers, no scalr chef ability) and I don't want to use
> chef-hosted.
>
> I would like to use chef or puppet to automatically setup my servers as they
> load up and I am looking for suggestions.
>
> 1. modify current roles (like app role) and add chef or puppet that fires off
> onhostup and does the rest.
> 2. create from base role everything from scratch (custom app role from base)
> that fires off from scratch. This seems like too much work.
> 3. create a server/client setup with chef or puppet and dedicate one of my 10
> servers as the chef/puppet master server. In this method, I will have the
> master server configure the clients on them starting up, but I am not sure
> how to effectively communicate back and forth on a newly created server.
> 4. something completely different suggested by one of you!
>
> What I don't want is to loose any of scalr's functionality like VHost setup.
>
> Any suggestions?
> john
>
> --
> 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/-/lT8wFh85huYJ.
> 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.
--
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.
