Hi,
I am running Eucalyptus currently on two machines. (one NC and rest on other)
The systems are currently connected to a router and I want to remove the router now. What do I need to change/re-configure in order to make it work properly after the change?
Also, I need to for example deploy a test web service on instances, how do I assign them an IP such that the service becomes accessible from any public machines.
Thanks,
Usman
Hello Usman,
I suggest you to read our networking guide: we just reworked it for our 2.0 release and we added examples: if you still have questions afterward feel free to follow up.
Also look for elastic IP: that should take care of the known IP for your web server.
cheers
graziano
Hello and thanks for the reply.
I have corrected the network setup and it is working. The problem is still with the IP issue, I cannot find any document resource where elastic IP implementation is explained. I can assign public IP (actual public IP) to instances but still cannot ssh them from outside the cloud controller. The best solution for me is to have one account wide elastic IP which I can use to access same service running on multiple instances (i.e. the same EMI+Service/data image having multiple instances).
So the questions here are:
1. Can I associate the same public IP with multiple instances and just use the private IP to configure them, copy data etc. And use some load balancing to route requests to the appropriate instance.
2. If no such single "Elastic" IP is possible, can I still have separate public IPs for instances (which I know how to do) and make them accessible from everywhere (this is the biggest hurdle as yet, making them accessible from anywhere!).
Any guideline you may have will be very helpful. The security groups are ok with correct permissions.
Best regards,
Usman
Hello, I'll just try to answer your questions based on my own experience. Any correction would be appreciated.
answer to q1: no & yes.
The relationship between a public ip and an instance is "one-one-relationship", which means you can only assign one public ip to an instance once at a time. Eucalyptus will "not" do any load-balancing techniques between instances, the matter about how to use these instances is up to yourself.
In short, any computing node (not only but also eucalyptus instances) could be the load balancer as long as it can access instances via private or public ip. (Or, "routable") And thus almost all SLB techniques can be used.
In my case, we have a F5-Bigip SLB on top of the eucalyptus cloud. We configure it to be in the same VLAN with instances. And then we can route the request to instances based on requested http-host, port, etc... We've also tried the opensource LVS balancing techniques and it worked perfectly. I mean, there are many SLB software and hardware solutions and it's not so hard to choose and implement one.
answer to q2: definitely yes.
I think there are two configurations which you should validate again: the network and the security groups. Maybe you missed the security group part. You may check the doc which has a very detailed explanation.