Thanks Daniele that worked perfectly
On Monday, 22 February 2016 15:08:01 UTC, Daniele Testa wrote:
>
> Try something like this:
>
> app[:configuration] = {
> "scalr" => {
> "aws" => {
> "instances_connection_policy" => "local"
> },
> "gce" => {
> "instances_connection_policy" => "auto"
> }
> }
> }
>
>
> On Monday, February 22, 2016 at 9:42:05 PM UTC+8, Michael Kelly wrote:
>>
>> Hi Thomas,
>>
>> If you wanted to control connectivity on a per cloud basis is this
>> another entry in /etc/scalr-server/scalr-server.rb ?
>>
>>
>> I'm pretty sure this is possible but not sure what should go in the
>> config file
>> https://scalr-wiki.atlassian.net/wiki/display/docs/Advanced+Configuration
>> scalr.<cloud>.instances_connection_policy
>>
>> Thanks
>> Mihcael
>>
>>
>>
>> On Tuesday, 17 February 2015 14:21:09 UTC, Thomas Orozco wrote:
>>>
>>> Hi Michele,
>>>
>>> The best approach then would be to configure Scalr to use private IPs to
>>> connect to your instances (which will not require a VPC Router).
>>>
>>> Add this to */etc/scalr-server/scalr-server.rb *(create the file if
>>> necessary):
>>>
>>> *app[:instances_connection_policy] = 'local'*
>>>
>>> Then run:
>>>
>>> *scalr-server-ctl reconfigure*
>>>
>>> Cheers,
>>>
>>> On Tuesday, February 17, 2015 at 6:09:09 AM UTC-8, Michele Viviani wrote:
>>>>
>>>> Hi Thomas,
>>>>>>
>>>>> same VPC (for now) just to take confident with the tool. I will than
>>>> have a need of deploying in 2 (or more) VPCs
>>>>
>>>> Mike
>>>>
>>>>>
>>>>>>
>>>>>
--
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.
