e the instance, let Scalr spin up a
> replacement, and verify that your hostname format is correctly applied on
> the replacement instance?
>
> Many thanks,
> Wm. Marc O'Brien
> Scalr Technical Support
>
>
>
>
> On Monday, November 14, 2016 at 11:51:07 AM UTC-7, Ben
It looks like changes to "Server Hostname Format" are not applied to a
running Server in AWS, even if I put that machine through suspend/resume
cycle. Changing the hostname locally on the machine is possible via
hostnamectl, but it looks like scalarizr is still coming in and reverting
it at
Following up that I created an issue on Scalr github:
https://github.com/Scalr/scalr/issues/80
On Tuesday, October 11, 2016 at 1:56:09 PM UTC-5, Ben West wrote:
>
> Actually, turns out the issue is with Scalr web UI stripping newlines from
> default variable values populated at low
echo" to print the variable, make sure that you use "echo -e"
> to enable new-line conversion.
>
> On Tue, Oct 11, 2016 at 4:07 AM, Ben West <westbyw...@gmail.com> wrote:
>
>> I'm curious if there is a way to preserve '\n' line returns in a Global
>> Varia
I'm curious if there is a way to preserve '\n' line returns in a Global
Variable, specifically so that one can pass YAML to launched servers.
Testing on a copy of Scalr v5.10 seems to indicate the line returns being
stripped, and it looks like the printf format string field can't be used
I am trying out this Route53 / AWS Lambda tutorial that was recently
published on the wiki:
https://scalr-wiki.atlassian.net/wiki/display/docs/Integrate+Route53+with+Scalr+using+Lambda
https://github.com/scalr-tutorials/scalr-lambda-route53
I've walked through all the steps in that tutorial, but
On Chromium v45.0.2454.101 running under Ubuntu v14.04, I see this message
when attempt to open an SSH console to a server in Scalr v5.8.29 (Open
Source Edition):
"Chrome 42 (and greater) users need to enable NPAPI Plugins for the SSH
Launcher to function. More information"
However, it looks
at 5:56:30 PM UTC-5, Ben West wrote:
>
> I am trying out the open source edition of Scalr v5.8.29 on AWS,
> specifically testing the ability to deploy farms in private subnets in
> different VPCs.
>
> I found a couple posts on this group suggesting the use of VPC peering
&g
I noticed these inbound rules on the scalr.vpc-router security group which
Scalr creates for VPC Router instances deployed in AWS:
Type
Protocol
Port Range
Source
All TCP
TCP
0 - 65535
Custom TCP Rule
TCP
8008 - 8013
0.0.0.0/0
All UDP
UDP
0 - 65535
HTTPS
TCP
443
0.0.0.0/0
HTTP
TCP
80
I am trying out the open source edition of Scalr v5.8.29 on AWS,
specifically testing the ability to deploy farms in private subnets in
different VPCs.
I found a couple posts on this group suggesting the use of VPC peering
between that where the Scalr server resides and any VPCs containing
I see from this wiki page there is the ability to import pre-defined,
shared roles provided by Scalr.net:
https://scalr-wiki.atlassian.net/wiki/display/docs/Packages+-+Sync+Shared+Roles
This appears to be the underlying PHP code, with hardcoded pointer to
I am trying out the open source edition of Scalr v5.8.29 on AWS.
Specifically, I'm trying out deployment of a farm inside the private subnet
of a VPC. For now, I'm limiting all instances launched to us-east-1d.
The VPC has two subnets in the same availability zone (us-east-1d), one
public
12 matches
Mail list logo
