If your back-end servers are using HTTP, then you can use our HAProxy role for this. If it's using other protocols, you have to build your own custom role together with Scalr Orchestration. I'm afraid we don't have step-by-step instructions how to handle all possible scenarios with Scalr.
On Wed, Feb 24, 2016 at 2:38 PM, kakarla sreekanth <[email protected]> wrote: > Hi Daniele and Team, > > Here in Scalr site, it explains about the Autoscale for a sample app. But, > I would like to know for a general setup. As I said, First, I need a have a > LB and one Server running. If it got a high CPU/Memory usage, it should > launch another server and get configured to the LB automatically. later, if > the metrics gets reduced, the launched server should get terminated. This > is the workflow, I'm looking for. > > Provide me a step by step assistance to achieve this. > > -- > Regards, > Sreekanth Kakarla > > On Wednesday, February 24, 2016 at 11:16:23 AM UTC+5:30, Daniele Testa > wrote: >> >> Hi Kakarla! >> >> As a new user of Scalr, it will be beneficial for you to read through the >> documentation found in our Wiki. It will explain the concepts of Scalr and >> help you achieve the setup you are looking for, which is fully built-in to >> Scalr out of the box. >> >> https://scalr-wiki.atlassian.net/wiki/x/yw8b >> >> >> On Wed, Feb 24, 2016 at 1:29 PM, kakarla sreekanth <[email protected]> >> wrote: >> >>> Hi Jay, >>> >>> Thanks for your response, We are using Rackspace account with Scalr. >>> Our goal is to do a Autoscale of Server using CPU & Memory usage. Would >>> be good, if you give me a step by step instructions to achieve it. >>> First, I need a have a LB and one Server running. If it got a high >>> CPU/Memory usage, it should launch another server and get configured to the >>> LB automatically. later, if the metrics gets reduced, the launched server >>> should get terminated. This is the workflow I'm looking for. Provide me a >>> step by step assistance to achieve this. >>> >>> >>> >>> >>> On Tuesday, February 23, 2016 at 9:00:27 PM UTC+5:30, Jay Farschman >>> wrote: >>>> >>>> Sreekanth, >>>> >>>> Scaling is built in and easy to use. I'm not sure what metric you want >>>> to use, but it works as described here: >>>> >>>> >>>> https://scalr-wiki.atlassian.net/wiki/display/docs/Autoscaling+Algorithms >>>> >>>> From an AWS standpoint, you would build a Farm and then Farm Roles. >>>> Farm Roles describe the characteristics of the VM/Instance including which >>>> AMI to start, what security groups to use how to network, how to auto-scale >>>> etc. >>>> >>>> It's a fun system and it's been surprisingly flexible. >>>> >>>> Hope that helps, if not let me know. >>>> >>>> On Tuesday, February 23, 2016 at 3:03:29 AM UTC-7, kakarla sreekanth >>>> wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> I am looking for Dynamic Autoscaling Script in Scalr, based on Scalr >>>>> will remove Servers when the metric's value is lower than this threshold >>>>> (Scale-down threshold), Scalr will add Servers when the metric's value is >>>>> higher than this threshold (Scale-up threshold). >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "scalr-discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Regards, >> Daniele Testa | Solutions Engineer @ Scalr | [email protected] | >> www.scalr.com | blog.scalr.com >> > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Regards, Daniele Testa | Solutions Engineer @ Scalr | [email protected] | www.scalr.com | blog.scalr.com -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
