Jump to content
C3 Forums

IMPORTANT: Migration to the new database and outages


Recommended Posts

As you probably all know by now, we are migrating to the new database, and this will cause some prolonged outages. The move, which is very delicate and complex, will require 5 steps:

 

1. Shutting down the current database and C3U authors access

During this phase, authors will not be able to upload new content and will not be able to access the C3U Dashboard and related pages. Players will not be able to access the database but they will be able to download content from the current links if hosted on C3U. Obviously any content hosted outside C3U will not be affected.

 

2. Migrate all content to the new infrastructure

We need to move all data currently hosted on the old infrastructure to the new one, converting all data to the new format. Everything from step 1 still applies. We can't allow access again until we have verified that all data has been properly imported.

 

3. Open up the new DB in read-only format

Once migration is done, the new DB will be accessible to anyone but only to browse, not to add any content. During this phase we need authors to do a thorough check of their content. Everything from step 1 except database browsing still applies.

 

4. Move C3U Dashboard to the new framework

Before we can once again allow uploads we need to move C3U to the new framework. Everything from step 1 except database browsing still applies.

 

5. Go back to full access

Once everything works as expected we can allow once again uploading, C3U access, etc.

 

Step 1 will begin in 1 to 7 days, meaning it can start from today up to next Saturday. We can't say how many days of restricted access we're gonna have: the more we get help identifying issues in step 3, the sooner we can open access.

 

After all of this is done, the new DB will still have some limitations in terms of options and functions that we will remove during the following weeks.

 

Thank you for your patience and see you all on the other side of the DB!

Link to post
Share on other sites

I know I've said this a lot but I think it's very important to reiterate. Thank you very much for all this work that you've put into the new DB. Between your regular job and home life I can't imagine the amount of time and resources you've been managing to make it all work. I know this has taken a lot of effort and I cannot express how much I appreciate all you've done to not only keep supporting C3, but to continue upgrading and improving an already great resource for customs.

 

Again thank you for all your work and for keeping customs alive!

 

Also thanks to all of those who have helped test the new DB. The time you guys have taken to make sure the bugs are ironed out is also much appreciated.

Link to post
Share on other sites
  • 3 months later...

IMPORTANT ANNOUNCEMENT

 

So, a long time has passed and no new DB is available: what's happened?

First of all, I make it a point to always deliver when I commit so I'm very frustrated that this has not happened yet. It's entirely on me and I feel really bad I didn't deliver. With that said, back to "what's happened?"...

What happened is that after laying out the path to switch over to the new DB I realized a number of things needed more attention simply to detach the whole system from the old DB to port it to the new DB. I also realized that there was no going back: once we are off to the new DB we can't switch back. All of the above, combined with the fact that the new system is 10 times more complex and all integrated than the current one, made me realize that from the moment we switch to the new DB to the moment when everything is set up and working perfectly I have to essentially be on call for any issue. If I can't address an issue and fix it quickly, people can't upload new songs or, even worse, songs are uploaded with issues that we carry over for all songs until I realize something is wrong.

All of this has happened while I had to devote even more time to work and I had to choose:
1) leave the current DB for the new one which is cooler, more complete, etc. but jeopardize daily/weekly releases and possibly block new releases for a while if anything goes wrong
2) keep the current DB and not risk anything

As you already know I had to choose option 2 for now. So what now? The next window is realistically at the end of Leg 2 and I’ll try to free some time in case of emergencies then. I’ll do my best, I just need to put work first though because this is a critical moment for me and I can’t lose focus there.

So, finally, I’m very sorry I couldn’t deliver on the promise I made: I always deliver if I commit so I’m very frustrated, also because of the time other people spent helping me out. However I couldn’t foresee both problems that intervened and if I could I wouldn’t even have started development. Come May we'll readdress this and hopefully things are better than they are now...

Thank you for your patience

Link to post
Share on other sites

I get the personal letdown feeling since I'm the same way, but honestly, you made the right choice and this can wait. You continue to do a ton of work when most would have abandoned it. So as far as I'm concerned, nothing to apologize for (but you'll still feel the need out of integrity 😊). I still look forward to the new changes WHENEVER they come. Thanks again for your work.

Link to post
Share on other sites

I get the personal letdown feeling since I'm the same way, but honestly, you made the right choice and this can wait. You continue to do a ton of work when most would have abandoned it. So as far as I'm concerned, nothing to apologize for (but you'll still feel the need out of integrity ). I still look forward to the new changes WHENEVER they come. Thanks again for your work.

 

This. The current database is the cake we all know and rely on to get our fix of the sweet songs and tasty tunes we crave. A new database is just icing. Yeah, I'll gorge myself on the whole container and develop adult-onset diabetes when it arrives, but I can wait. If you're gonna do something, do it right. Let that bitty bake s'more.

Link to post
Share on other sites

You've put an incredible amount of time and work into this and we're very grateful for your efforts to keep C3 not only alive but thriving. You live a super busy life, it's completely understandable that this can't be committed right now. We'll get that awesome database, just may take a bit but it's well worth the wait.

 

Thank you again for all you do. :)

Link to post
Share on other sites

I eagerly await the new database as well. But as far as I'm concerned this is just a hobby for most of us on here and work should come first.

 

I completely understand the feeling of not delivering as promised, but like I said this is just a hobby, and we can wait for the stars to align again.

Link to post
Share on other sites
  • 1 month later...

In most cases, customs disappear from the database when the same songs have been released as official DLC for one of the Rock Band games. In a few rare cases, a customs author has requested their songs be pulled.

 

When you see a missing song, first make sure it wasn't official DLC, and if not, then you can ask what became of it.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...