required to run the app (db hosted on aws rds outside of RightScale). Nothing is really set in the deployment except the name and a brief description. Deployments currently broken up by Availability Zones in EC2 East region.
AWS region, ServerTemplate, IP Address, Instance Type, Security Groups, etc. Server Arrays do the same things but can be scaled horizontally through the RightScale gui or through the alert system.
on boot, during operation, or on shutdown. Set alert actions to perform if the server meets a certain condition (ie. CPU is not responding for 15 minutes).
servers in that deployment to find and communicate with them. Set a tag on a server in a Chef recipe with the following commands: right_link_tag "web:active=true" # tag server es=rightscale_server_collection "elasticsearch" do # find tagged server tags "elasticsearch:active=true" action :nothing end es.run_action(:load)
deployment by using the RemoteRecipe call in a Chef recipe. remote_recipe "update the load balancer" do recipe "ichange-load-balancer::default" recipients_tags "balancer:active=true" end
launched at the same time from the GUI and work. In practice there are some race conditions. Start elastic-search, memcache, and redis. Then start task and web servers. Then start balancer. Run republishfeeds script/recipe on task server. Relaunch web/task servers if there is an issue. Attach elastic IP to balancer.