Doh!

It looks like i have been able to fix it!

By looking here:

https://github.com/scalr-tutorials/scalr-server-configuration/blob/master/4-server/scalr-server.rb

I found that

app[:instances_connection_policy] = 'local'

should work



On Tuesday, June 23, 2015 at 4:33:15 PM UTC-7, [email protected] 
wrote:
>
> Here's my setup
>
>
> Within AWS, I have a few VPCs that are peered together.
>
> To make things simple, let's say that i have a *DEV* and *TOOLS* vpc.
>
> Scalr 5.3 Open Source edition lives on a private subnet of the *TOOLS* 
> vpc.  I can access this node by IP and hostname from other nodes within the 
> *TOOLS* vpc *and* within the *DEV* vpc.
>
> Scalr is configured to advertise it's FQDN `scalr01.my-org.internal` to 
> all nodes.  
>
> ```
> root@scalr01:/etc/scalr-server# cat scalr-server.rb
> routing[:endpoint_host] = "scalr01.my-org.internal"
> ```
>
> Yet, when I try to get scalr to build a node in a private subnet within 
> the *TOOLS* vpc, I am told that I need to add  vpc router.
>
> When i try to follow the instructions here:
>
> https://scalr-wiki.atlassian.net/wiki/display/docs/Using+VPC+-+Internal+Scalr+Deployment
>
> I see that i need to add
>
> ```
> scalr.instances_connection_policy = local
> ```
>
> to my config file. 
>
>
> Since scalr is now configured with Chef, i have attempted to add 
> the following to my `scalr-server.rb` file:
>
> ```
> root@scalr01:/etc/scalr-server# cat scalr-server.rb
> scalr[:instances_connection_policy] = "local"
> routing[:endpoint_host] ="scalr01.my-org.internal"
> ```
>
> I made the assumption that this would work based on 
> https://scalr-wiki.atlassian.net/wiki/display/docs/Using+VPC+-+Internal+Scalr+Deployment
>
> However, when i check here:
>
> https://scalr-wiki.atlassian.net/wiki/display/docs/Packages+-+Advanced+Usage
>
> There appears to be no way to set the "instances_connection_policy"
>
> Additionally, Chef complains about this when I run reconfigure:
>
>
> ```
> Recipe: scalr-server::_config_dir
>   * directory[/etc/scalr-server] action create (up to date)
>
>   
> ================================================================================
>   Recipe Compile Error in 
> /opt/scalr-server/embedded/cookbooks/scalr-server/recipes/default.rb
>   
> ================================================================================
>
>   Mixlib::Config::UnknownConfigOptionError
>   ----------------------------------------
>   Reading unsupported config value scalr.
>
>   Cookbook Trace:
>   ---------------
>     
> /opt/scalr-server/embedded/cookbooks/scalr-server/libraries/scalr_server.rb:88:in
>  
> `generate_config'
>     
> /opt/scalr-server/embedded/cookbooks/scalr-server/recipes/default.rb:43:in 
> `from_file'
>
>   Relevant File Content:
>   ----------------------
>   
> /opt/scalr-server/embedded/cookbooks/scalr-server/libraries/scalr_server.rb:
>
>    81:      end
>    82:
>    83:      def generate_config(node)
>    84:
>    85:        # Load attributes from the configuration files. Ordering 
> matters here
>    86:        # Main attributes file. Probably where you want global 
> settings, like 'route'
>    87:        if File.exists?(main_config_file_path node)
>    88>>         ScalrServer.from_file(main_config_file_path node)
>    89:        end
>    90:
>    91:        # Alternate config file. Probably where you want local 
> settings, like what to enable
>    92:        if File.exists?(local_config_file_path node)
>    93:          ScalrServer.from_file(local_config_file_path node)
>    94:        end
>    95:
>    96:        # JSON secrets, or dynamically generated
>    97:        generate_secrets node
>
>
>   Running handlers:
> [2015-06-23T23:30:52+00:00] ERROR: Running exception handlers
>     - Raven::Chef::SentryHandler
>   Running handlers complete
> [2015-06-23T23:30:53+00:00] ERROR: Exception handlers complete
>
> ```
>
>
>
> SO what do I need to change?
>

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

Reply via email to