Wan Optimization Support
Technical => Deployment => : Waroon June 19, 2016, 07:06:09 PM
-
Edit: Amazon AWS deploy guide (http://wanos.co/docs/docs/wanos-admin-guide/installation/amazon-aws/)
Hi. wanos support
i import Ec2-import-instance wanos-3.0.4-disk1.vmdk to AWS instance success but can not star Error
Error starting instances
Invalid value 'i-071b13a3' for instanceId. Instance does not have a volume attached at root (/dev/sda1
How to step import wanos in to AWS
-
Hi, is this the MicroCore or Ubuntu version?
-
Ubuntu version
Ec2-import-instance wanos-3.0.4-disk1.vmdk -f VMDK -t c3.large -a x86_64 -p Linux -region ap-southeast-1 --subnet subnet-xxxxxxx --private-ip-address 192.168.1.200
-
According to the AWS documentation:
Error starting instances: Invalid value <instance ID> for instanceId. Instance does not have a volume attached at root (/dev/sda1).
You attempted to start the instance before the VM import process and all conversion tasks were complete.
Resolution
Wait for the VM import process and all conversion tasks to completely finish, and then start the instance.
I am not sure if this is accurate though and whether it will be the only snag you run into.
The AMI image is on the road map, so we can accelerate this if you have a specific use case that requires Wanos on AWS.
-
Success?
-
Waroon, there is an image on AWS:
Via advance EC2 launch, search for the community ami "Wanos" in the N.Virginia region
Add Wanos AMI image
Security Group rules add SSH, HTTPS and UDP port 4050
Launch
-
Steps to deploy on Amazon has been posted in the documentation:
Wanos Amazon AMI install (http://wanos.co/docs/docs/wanos-admin-guide/installation/amazon-aws/)
-
Hi
I'd like to add some additional info as discovered:
Elastic IP is only required when direct tunnels are used over public internet.
Elastic IP is not required when peering on private address e.g. over IPsec handled by routers
To tunnel traffic over Wanos out to the Internet e.g. for Office 365 acceleration, then the router in the VPC needs to NAT the traffic out