Hey guys,
 
We've had an internal discussion on this, and I'd like to share our 
thoughts with you, so you understand where we come from.

In essence, our software is free, but our time isn't. I think we can all 
agree that it's in our best interest as users that we charge for our 
services and reinvest for a better product.

I understand that it's hard to justify getting a support contract for the 
occasional small issue that shouldn't take "more than 5 minutes to fix". 
But if we give out our software and support for free, what's left?

With this, I'd like to propose that this forum is here for the community to 
help itself, but that we avoid requests *specifically *made to the Scalr 
company or Scalr staff. We prefer a *karma-based* system where the more an 
individual answers others' questions, contributes to documentation, and 
adds value for others, and more likely we'll set time aside to investigate 
an issue, try to reproduce, or develop a fix for them.

If any of you know any community management software that would facilitate 
this, kind of like ohloh.net's kudos (http://meta.ohloh.net/kudos/), please 
let us know.

Thoughts?

On Tuesday, April 3, 2012 3:20:53 AM UTC-7, Srini wrote:
>
> Hi
>
> Is anyone in the community using ELB with Scalr?  Have you come across the 
> problem i detailed?  Maybe i am the only one facing it since Scalr monitors 
> port 80 but my app runs on 8080 and ELB is also monitoring it on 8080.
>
> Can some one from Scalr please confirm if this is supposed to work with my 
> config or not?  I just need a confirmation .. based on the reply I will 
> handle the refreshing of the instances somehow.
>
> Thanks
> Srini
>
> On Tuesday, March 27, 2012 12:10:48 PM UTC+5:30, Srini wrote:
>>
>>   I use the ELB (instead of the nginx role) for load balancing.  When 
>> the instance is marked unhealthy on the ELB by AWS, Scalr is not detecting 
>> this and creating a new instance.  Instead ELB indicates its out of service 
>> and Scalr is just running the old instance.
>>  
>> Is this a bug or some setup issue in my landscape?  If the unhealthy 
>> instance is not detected and a new instance recreated, ELB would turn out 
>> to be useless right?
>>
>> Cheers
>> Srini
>>
>

-- 
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/-/XbQl4Ol9SnkJ.
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.

Reply via email to