No, really.
It was up until yesterday ns.alsonetworks.net and ns3.alsonetworks.net and it had some other random info on it. I ended up getting three geographically disperse cheap-o VPSes, total cost around $15 and used webmin to clone the DNS stuff on bashful to the new "ns" VPS, and slaved the new "ns2" and "ns3" VPSes. Then I changed DNS A records and re-registered the name servers. After a 24 hour wait, I took down named on bashful, and checked. All is well. Then I converted "ns" to master, and violin's your uncle.
So I sent to softlayer and canceled bashful. It goes down on the 18th.
Next project: drop qm2 / qm3 on softlayer. If the VPSes on burst work out, there's no real reason to keep even a cheap dedicated on softlayer. The qm2 / qm3 server functions as DNS, nagios and pbcs backups. As mentioned above, DNS is now off that box (I did it at the same time as I did bashful). Creating a new Nagios installation will be a bit tedious but will give me an excuse to investigate cool front ends (opsview?) for the tool. Once that's done I'll probably have to upgrade the disk on one of the other VPSes (no reason to keep Nagios and backups on the same box) to accommodate the pbcs backup stuff.
The VPSes: two in USA (Scranton, LA) and one in EU (Manchester). Nicely disperse geographically for DNS. 512MB, 20 GB HDD. Took a bit of tweaking, especially Manchester, but they seem okay.
Can easily put Nagios on one. EU or USA? Don't know, hafta think.
Backups won't fit in 20 GB, choose either to expand or just get a different VPS. Also hafta think.
Anyway next project is Nagios on somewhere outside of qm2 / qm3.
No comments:
Post a Comment