Doesn't support AWS VPC about vagrant-mesos

[everpeace]

InvalidParameterCombination => VPC security groups may not be used for a non-VPC launch

It seems that this error message tells that you tried to spin up an instance in non-VPC area even though you specified VPC security groups. Are you sure to set subnet-id which is associated with security groups which you specified??

[xbeta]

@everpeace Well, because aws.subnet_id is not define in standalone/Vagrantfile. I'll try to add it and see if it works.

[everpeace]

@xbeta oh, you used standalone. Standalone doesn't assume to use VPC. So, you have to set normal security groups.

[xbeta]

@everpeace Sure. I added and it does created the instance in EC2, but the ssh waits seems to be stuck, it waits forever and hang there. Except I could manually ssh in and EC2 console shows that's running. Any thoughts on that?

[everpeace]

@xbeta maybe you have to check your aws_config.yaml again. Did you set ssh_private_key_path correctly??

vagrant's debug mode would also guide you to solve the issue.

$ vagrant up --debug

[xbeta]

@everpeace you are right, it's the bad keypair. It's OK now. The provisioning is running. By the way, why wouldn't standalone be allowed to run within VPC ? (Testing purpose)

[everpeace]

@xbeta Yeah, you're right. Definitely, I should support standalone within VPC. I will take this task in this weekend maybe. I would be really happy if you could issue pull request for this :-)

[everpeace]

I created a task for supporting VPC in standalone. so I closed this.

[xbeta]

@everpeace
btw, I received this error, not sure it's related or not:
https://gist.github.com/xbeta/c72aecb06075fa422984