Hi Daniele, Honestly this is the first time hearing of and using scalr. Our setup is consist of a chef and jenkins servers to automate deployments. The missing part is creating instance and orchestrate the desirable jobs.
Also we have 2 ~ 3 VPC in 3 regions. And it seems I can't launch instances inside the vpcs I need. I Select "Launch this Farm inside Amazon VPC" , I click on the vpc ID, and save my changes. I have an AMI register that I associate to an app role. I then add that role to my demo farm when I configure network I can see my private subnets but when I select them it detects they are private but I can't select the vpc router, or my own NAT severs, any suggestions or documentation that is more clear instruction than scalr's own wiki. On Fri, Aug 14, 2015 at 5:53 PM, Daniele Testa <[email protected]> wrote: > Hi! > > Did you try to login to your Scalr server and verify that it can access > your instance on port 8013? > Your should be able to do this by simply telnet'ing to the instance and > see if you get a connect. > > Regards, > Daniele > > > On Saturday, August 15, 2015 at 8:04:29 AM UTC+8, Josue Contreras wrote: >> >> I have a scalr running in an ec2 classic instance and have all incoming >> traffic pretty much open. >> >> I installed the agent to an instance behind a vpc and have open the >> necessary ports. I still get the following error >> >> ================================================ >> >> >> Unable to establish outbound (Scalr -> Scalarizr) communication ( >> 10.2.105.239:8013): Connection timed out. >> >> >> ================================================= >> >> the console seems to be trying to login with a user >> >> >> Starting cloud-init: Cloud-init v. 0.7.2 running 'modules:final' at Fri, >> 14 Aug 2015 22:16:10 +0000. Up 18.40 seconds. >> Cloud-init v. 0.7.2 finished at Fri, 14 Aug 2015 22:16:11 +0000. >> Datasource DataSourceEc2. Up 18.62 seconds >> Starting /home/ec2-user/seo/web.js: [ OK ] >> >> [r [H [J >> >> Amazon Linux AMI release 2014.09 >> Kernel 3.14.19-17.43.amzn1.x86_64 on an x86_64 >> >> ip-10-2-105-239 login: >> ================================================= >> >> All of my instances have ec2 user disable is there a way to get around >> this >> >> >> >> >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "scalr-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/scalr-discuss/XsLzeRsDNE8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
