%20copy.png)
Join 10K+ people getting helpful guides, exciting case studies and much more in our newsletter.
Don't worry, we'll never share your email with anyone.
Oops! Something went wrong while submitting the form.
Connect with Yeti
With a couple of our projects we've had to move out a database, do replication and start doing load balancing recently. Django makes this incredibly easy and all you really have to do is point it to the correct IP address.
About two years ago we learned a fairly large lesson when we set this up for the first time. We set the IP addresses to the public ones we use in our DNS.
DO NOT SET YOUR APPLICATION UP TO USE EXTERNAL IPs. We ended up with a huge bill that month since it turns out we were routing all our traffic outside of Rackspace's cloud and then back in, which significantly upped our outgoing bandwidth which rackspace is now currently charging at 18cents/GB. In a high traffic environment this can add up to some high numbers which are not good for your bank account.
After spending some time talking to Rackspace Support, the solution, as you can probably tell, was to route traffic inside the Rackspace cloud and behind their subnet mask. So to find the IPs to use ssh into each server and run...
ifconfig eth1
...and that's it. This will spit you back what Rackspace uses internal and thusly what you won't be charged for. Eth0 will be your external IP. Change this in all the appropriate locations.
Note: if you're running VPNs/firewalls be sure to change your iptables as well
Don't worry, we'll never share your email with anyone.
©2024 Yeti Technologies LLC
