I moved the PSA server into the cluster, and then figured I would stick with technology that works and research more advanced routing possibilities later. There was a bit of an ARP twiddle, but after I got that moved, I’m happy to say that the move from 14 virtual machines to 6 is complete.
Now that I’ve simplified things, I can actually start on some improvements. That’ll happen a little later, I need to catch up on stuff first.
Indra and tt-dev are now integrated, leaving only the firewall/routers left to integrate. I need to do a bit of research before I can integrate those systems. I believe I will now start on the PSA network, so I can finally shut that system down.
So for the next little while, I’ll have three routers pointing at the same set of systems. Fun!
The tactel and vis.nu web servers are now integrated, leaving just the dev/shell and firewalls left out of the cluster, as well as the PSA server, which, save for mail services, remains separate from the new cluster.
Integration of PSA begins once vis.nu and tactel are fully integrated.
Also, all webmail services are now through https://mail.tacomatelematics.com, including vis.nu mail services. This way, all I have to do is focus on getting one webmail client up to spec. This includes password, domain, and mailing list management.
You’ll note the https, and it is indeed encrypted, but with a self-signed certificate at this time.
I’m going to begin on implementing the other portions now, and then moving on to PSA. Once that’s complete, I’m going to being transitioning all active Wordpress installations into a single multisite system, again to make our lives easier.
The server integration continues apace!
Since the new and old servers are actually on the same physical hardware, stuff gets moved and integrated pretty quickly. Lists, accounts, web clients, and admin stuff is moved off of the old server and onto the new. There are pointers in place to help you find them.
The current URLs are temporary as we continue to move new services. As you’ll note, web clients and stuff all have Tacoma Telematics logos on them, as they’re now the same system. Make no mistake! It’s still vis.nu under the hood.
Hello, seventeen months later. I have news! vis.nu is sort of melting.
In short, I’m administrating three separate systems for mail, web, and what have you, all of which are now virtual machines living on the same server. All in all, I’m talking about thirteen or fourteen different virtual machines, some 32bit, some 64bit, and all of which right now are in serious need of upgrading.
In order to simplify my life, I’m combining all of these systems to run in an entirely new cluster of VMs running under the vis.nu names. This includes all my corporate stuff, and all the stuff I’m doing for that other thing I’ve been up to for the last couple years.
Part one just began– Tacoma Telematics and vis.nu are now using the same database, this time running MariaDB because Oracle is scary. And I’m going to make a real go of it this time, and try to get back a lot of the cool stuff I had on vis.nu before I had to move it.
More as it happens.
vis.nu Networks was down for an extended period of time this weekend for two reasons:
I’ve put a bandaid in place to handle the DNS, but systems that run in Phoenix are offline and will remain offline for some time. No ETR. More as I know.
Dear Tacoma Telematics Clients, Tomorrow, Wednesday 03/31/2010, Tacoma Telematics will experience a down time of approximately six hours. The power company is updating components of the electrical system of the historic building where our main server is located. In order to insure no loss of data, please complete and save any work prior to 6:00 PM PDST (9:00 PM Eastern). We expect to resume services by 12:00 AM PDST Thursday, April 1 (3:00 AM Eastern). We sincerely appreciate your patience and understanding regarding this upgrade to our electrical system...
It goes on from there, but that’s the important part.
As of right now, the old indra is off on an unrelated IP, and a new DNS only server is sitting on the old vis.nu IP. The move is complete. The only thing remaining is to get the integrated Mission Control back up, but unfortunately, that’ll have to wait a little while so I can attend to other pressing matters.
Until then, here are links to management systems:
The main vis.nu systems are moving from Arizona to Washington this week, and there’s a lot going on. If you ‘re looking at this post from the MOTD, I strongly encourage you to to go the website and read further. Aside from the most recent update, I’ll keep everything behind a break for brevity.
Update: 2/25 04:32: On the old system, I’ve turned postfix into a secondary-only backup MX which points at the new server, dovecot and apache have been shut down. Unless you need access to files on the old system, you should be completely pointed at the new system at this time. A placeholder web server which instructs browsers that the system has moved and their DNS is stale is in place.
Read the rest of this entry »
The database server on vis.nu has been shut down, and all connections are being forwarded to the new database server at the new location
To recap, at this point, mail is being saved on the new server and is active via NFS, and all database connections are being forwarded to the new MySQL server. The only remaining active services are shell and web, and movement of those services are underway.