Language Selection

English French German Italian Portuguese Spanish

Site Migration Imminent (Updatex6)

Filed under
News

Update #1 (Sunday 9PM GMT): We are expecting to have the virtual machine for the site ready some time by the end of the day. It will run CentOS. A complete snapshot of the site's files (not database) has been copied over to San Diego (security- and privacy-oriented host).

Update #2 (Tuesday 10AM GMT): The target VM is now ready.

Update #3 (Thursday 8AM GMT): It seems likely that this migration will be delayed to ensure quality (no downtime) and adequate operation after the migration.

Update #4 (Thursday 6PM GMT): Data is being copied across at the moment.

Update #5 (Thursday 6PM GMT): Databases frozen in their current state to be copied across.

Update #6 (Friday 11AM GMT): The migration is complete. The databases in use are nearly a day old (but identical except statistics). Please report any issues you still find to r@schestowitz.com. DNS servers may take a while longer to synchronise and there will be another short maintenance window for resolving a minor issue.

SOME TIME in the coming week we will attempt to migrate the Web site and upgrade it, bringing improvements and making all the software up to date. This task is complicated because many modules are involved, several content management systems make up the site, a lot of data is being migrated, and replacements for existing modules may be difficult - if not altogether impossible - to find.

To avoid disappointments and in order to keep pressure low, this message is pinned here days in advance. Pessimistically predicting the most dire outcome, it is possible that in the coming day we won't be able to update readers (no new items), it is possible that the site will be down for a few hours (hopefully not days), and the appearance/structure of the site may be in a transitory state. The aim is to change nothing except at the back end.

I took a week off work in order to deal with Tux Machines and I hope to find understanding and sympathy in case the migration is imperfect or slow. I have been testing some parts of the process for well over a month, so I believe it may prove to be smooth sailing, but one can never know for sure until the actual transition (at DNS level) and upgrade (of Drupal, Gallery, etc.).

Regarding the Statistics section, it publicly broadcasts IP addresses of some visitors (interfering with our strict privacy policy that already had ads removed), so we shall look into possible replacements. The Gallery section may take a little longer to migrate because it takes up several gigabytes of database space that we don't yet have on the destination server (CentOS). If during the transition you wish to contact us (e.g. if the site is offline), then try E-mail, IRC, Twitter, etc.

Again, apologies in advance for any disruption of service; please be patient and help by reporting issues to us (e.g. broken links, DNS issues).

Best of luck

Drupal is a beast but 7.xx is stable enough right now. Best of luck Smile

Drupal

Thanks, Hussam.

The migration strategy is still up for debate. One of the British government sites I support runs Drupal 7 (in several areas, intranet and public) and I get a similar experience with it in Techrights (Drupal 7 for front page). However, I don't lack much features here in Drupal 6. Drupal 6 does all that's needed for now.

At this stage, as I am a little paranoid about module compatibility, I still wonder if I should stick with Drupal 6 (for Tux Machines) until Drupal 8 is officially released.

http://drupal.stackexchange.com/questions/42382/drupal-6-end-of-life

This would save us from a two-leap process (6 to 7 and then 8, finding missing modules at each step).

Any advice on this would be appreciated. Messing up themes and functionality (even if temporarily) might not be a risk worth taking for just a few backend changes. Also, Rianne has very little experience with Drupal 7, whereas she's comfortable with this existing setup.

When a new virtual machine is ready (and I have enough DB disk space for Gallery) I will probably attempt a DNS change and revert back if it's a sordid mess. Susan, thankfully, is always around to offer help. She has been super supportive.

You can do it!

You can do it! Big Grin

Good luck with the move! For

Good luck with the move!

For what it's worth, if you can preserve the stories, urls and user base, then I'm happy. I think losing some other modules/functionality to having an up to date and secure version of the software is preferred or at least not a big deal.

Small rant: "security- and privacy-oriented host in San Diego"? I'd look at something in Iceland or Switzerland.

Privacy

Yes, I know that national law is an issue, but I trust the person. I read that a Web host in the US (at least one) was forced to attach some bit of equipment from the NSA (to the server/s) because the NSA couldn't get "sufficient" access.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

5 Kubernetes must-reads: Tips and trends

Kubernetes is having a moment – but don’t look for its popularity to wane anytime soon. As enterprises move beyond experimenting and start working in earnest with containers, the number of containers multiply: So do the manual chores. Orchestration tools like Kubernetes add automated help. “Running a few standalone containers for development purposes won’t rob your IT team of time or patience: A standards-based container runtime by itself will do the job,” Red Hat technology evangelist Gordon Haff recently noted. “But once you scale to a production environment and multiple applications spanning many containers, it’s clear that you need a way to coordinate those containers to deliver the individual services. As containers accumulate, complexity grows. Eventually, you need to take a step back and group containers along with the coordinated services they need, such as networking, security, and telemetry.” (See Haff’s full article, How enterprise IT uses Kubernetes to tame container complexity.) Read more

Australian Securities Exchange completes Red Hat migration

The Australian Securities Exchange (ASX) has completed the migration of "mission-critical" legacy applications to the Red Hat JBoss Enterprise Application Platform (JBoss EAP). ASX first deployed JBoss EAP in 2011 to modernise its legacy technologies and to facilitate the introduction of new web applications after it realised its legacy application server platform was becoming increasingly inconsistent, unstable, and expensive. After the initial ASX Online Company migration was complete in 2012, ASX used JBoss EAP to build the ASX.com API, as well as its Sharemarket Game, which gives players the opportunity to learn how the share market works. Read more

Programming/Development: GAPID 1.0 and Atom 1.23

  • Diagnose and understand your app's GPU behavior with GAPID
  • GAPID 1.0 Released As Google's Cross-Platform Vulkan Debugger
    Back in March we wrote about GAPID as a new Google-developed Vulkan debugger in its early stages. Fast forward to today, GAPID 1.0 has been released for debugging Vulkan apps/games on Linux/Windows/Android as well as OpenGL ES on Android. GAPID is short for the Graphics API Debugger and allows for analyzing rendering and performance issues with ease using its GUI interface. GAPID also allows for easily experimenting with code changes to see their rendering impact and allows for offline debugging. GAPID has its own format and capturetrace utility for capturing traces of Vulkan (or GLES on Android too) programs for replaying later on with GAPID.
  • Hackable Text Editor Atom 1.23 Adds Better Compatibility for External Git Tools
    GitHub released Atom 1.23, the monthly update of the open-source and cross-platform hackable text editor application loved by numerous developers all over the world. Including a month's worth of enhancements, Atom 1.23 comes with the ability for packages to register URI handler functions, which can be invoked whenever the user visits a URI that starts with "atom://package-name/," and a new option to hide certain commands in the command palette when registering them via "atom.commands.add." Atom 1.23 also improves the compatibility with external Git tools, as well as the performance of the editor by modifying the behavior of several APIs to no longer make callbacks more than once in a text buffer transaction. Along with Atom 1.23, GitHub also released Teletype 0.4.0, a tool that allows developers to collaborate simultaneously on multiple files.

Red Hat GNU/Linux and More