Hi Thomas, I've been working with Scalr today and I have a couple of questions more related to VPCs, I hope you don't mind.
* The easy one: Is there any way to config aws-tags in a VCP router role from control panel? There are just a couple of options to configure, so I suppose it is not possible from there. * The difficult one ;) I have seen in documentation that if you want to deploy a farm in the same VPC as Scalr, it is neccesary to configure some settings in the config: https://scalr-wiki.atlassian.net/wiki/display/docs/Using+VPC+-+Internal+Scalr+Deployment Well, what if I would like to launch farms in both, I mean, in my own VPC and in a external VPC? Should I configure as well a VPC router role in my own VPC? From control pannel it is impossible to launch a farm in a private subnet without configure a vpc role (parameter "scalr.instances_connection_policy = auto (or public)") and if I change this parameter to local it works, but it is impossible to launch farms in external VPCs. what should I do? Thank you in advance. 2015-02-10 10:42 GMT+01:00 Adrián Fuentes < [email protected]>: > It makes sense! > > Thank you again! > > 2015-02-10 10:39 GMT+01:00 Thomas Orozco <[email protected]>: > >> Hi, >> >> Since creating and configuring a VPC is a one-time thing, we do our users >> do so from the AWS console (there is limited value in having Scalr >> reproduce this functionality). >> >> Hope this makes sense, >> >> Cheers, >> >> >> On Tuesday, February 10, 2015 at 10:33:51 AM UTC+1, >> [email protected] wrote: >>> >>> Hi Thomas, >>> >>> Thank you very much for being so fast. >>> >>> You were right, I hadn't selected the option for selecting in VPC. >>> >>> Just one more question, is there any way to configure a route table in >>> aws from scalr control panel? I'm trying to do all work from scalr, I mean, >>> creating a vpc with two subnets, one public and one private, and then >>> configuring vpc router role for accessing all instances I want to create in >>> my private subnet. Is it possible to do it all this work from scalr or >>> should I create all the network intraestructure firstly from aws console? >>> >>> I have checked your documentation about this: https://scalr-wiki. >>> atlassian.net/wiki/display/docs/Using+VPC+-+External+Scalr+Deployment >>> >>> and I think that the only way is to configure all route tables from aws >>> console. Just to be sure. >>> >>> Thank you in advance. >>> >>> El martes, 3 de febrero de 2015, 9:53:03 (UTC+1), Thomas Orozco escribió: >>>> >>>> Hi, >>>> >>>> I'm not sure what exactly your issue is here. Are you: >>>> - Unable to *create a VPC*? >>>> - Unable to find the VPC Router Role? >>>> >>>> Note that the VPC Router Role is only available when launching in a >>>> VPC, so, if you're unable to create a VPC, it makes sense that you would >>>> not see it. >>>> >>>> Cheers, >>>> >>>> On Monday, February 2, 2015 at 9:10:15 AM UTC+1, adrian.fuent...@ >>>> innovation4security.com wrote: >>>>> >>>>> Hi all, >>>>> >>>>> This is my environment: >>>>> >>>>> * 5.1 OpenSource Scalr >>>>> * Scalr 5.1 deployed in a Amazon VPC >>>>> * Roles imported as: php sync_shared_roles.php >>>>> >>>>> I am able to launch any ec2 properly in my vpc but I can't find the >>>>> way to create new vpcs in Amazon. In fact, I am not able to find "VPC >>>>> router" as role as it is described in http://www.scalr.com/blog/ >>>>> announcing-custom-vpc-support >>>>> >>>>> Can anyone help me? >>>>> >>>>> Thank you in advance. >>>>> >>>>> -- >> 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/NQHb-4b-1iw/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. >> > > > > -- > Adrian Fuentes > -- Adrian Fuentes -- 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.
