Skip to end of metadata
Go to start of metadata

Understanding the core components and their use will help you get the most out of Scalr.


FarmsLogical units that contain a set of roles. Roles are configured within farms (auto-scaling, deployments etc.)
RolesMachine images with a specific behavior (e.g application server, database, caching server etc.)
ServersInstances of a specific role.
ScalingProvisioning of additional instances of a given role. Can be automated to follow the evolution of various metrics and closely follow the demand curve for your application by adding new servers when you need them and shedding unneeded instances. This is auto-scaling.
DeploymentsA feature that allows you to orchestrate code deployment to your farms. By linking to a source you can tie your application to a farm role.
Orchestration EngineA powerful tool for event-based, manual, or even recurring (with the Task Scheduler) script execution.
ChefAn open-source systems integration framework built specifically for automating the cloud. With Chef, you write abstract definitions as source code to describe how you want each part of your infrastructure to be built and apply these to your servers
Domain Name ManagementOut-of-the-box DNS management tool. DNS zones are automatically updated by Scalr to reflect the instances you are currently running.
Clouds supportedInfrastructure as a service provided by Cloud providers such as Amazon Web Services. A cloud can be public or private. Scalr works on top of cloud APIs.


 

 

 

Labels
  • None