Here is a rough plan for Kitsune EOL! It is still draft and the details will be sorted and summarized somewhere (maybe in this thread or maybe in a Google doc linked from this thread).
content wise: copy the mysql database(s) somewhere, keep it around in case employees (not volunteers since it unfortunately has personally identifying information like email addresses) need it
site wise: Lithium will be taking over the domain (support.mozilla.org) and there will be redirects in place from old pages to new pages in order to preserve SEO. Once DNS kicks in we should plan to have the current site live for say n weeks (exact number of weeks To Be Determined, n = 2 weeks seems reasonable). It won't be reachable due to the redirects but if we needed to rollback, we could. Once that n week period passes we (Mozilla employees I guess, I don't think volunteers have the keys to the current site) officially begin to decommission the site.
code wise: as for the code, it's already open on github and docs for the code are open and are on readthedocs
Cheers!
..Roland
Hi all!
Here is a rough plan for Kitsune EOL! It is still draft and the details will be sorted and summarized somewhere (maybe in this thread or maybe in a Google doc linked from this thread).
# content wise: copy the mysql database(s) somewhere, keep it around in case employees (not volunteers since it unfortunately has personally identifying information like email addresses) need it
# site wise: Lithium will be taking over the domain (support.mozilla.org) and there will be redirects in place from old pages to new pages in order to preserve SEO. Once DNS kicks in we should plan to have the current site live for say n weeks (exact number of weeks To Be Determined, n = 2 weeks seems reasonable). It won't be reachable due to the redirects but if we needed to rollback, we could. Once that n week period passes we (Mozilla employees I guess, I don't think volunteers have the keys to the current site) officially begin to decommission the site.
# code wise: as for the code, it's already open on github and docs for the code are open and are on [https://kitsune.readthedocs.io/en/latest/ readthedocs]
Cheers!
..Roland
I suggest few changes, mostly about the sequence of the steps.
Import data to Lithium.
Set up corresponding redirects on Lithium side (use 302 or 307 HTTP response).
Change DNS to Lithium. This change will take effect for the whole internet in the time of A records TTL (time to live) before the change.
Prevent Kitsune from writing to the database (e.g. DB permissions) in case someone accidentally gets there (which is very unlikely, but not all DNS caches and devices respect the TTL completely).
Import to Lithium everything, what might happen on Kitsune during the time between the last import and this step (+ add corresponding redirects).
Backup the database.
After the n-week period, stop Kitsune servers (and make another db backup, if you want).
Change the redirect HTTP code to 301.
This procedure should result in no outage and in the worst case, new questions, changes or user accounts will be temporarily unavailable if they were created between the two import steps.
In case of rollback:
Allow database writes to Kitsune.
Import data from Lithium + set up corresponding redirects.
Change DNS to Kitsune and wait the time of A records TTL before this change.
Prevent Lithium from writing to its database in case someone accidentally gets there.
Import from Lithium everything, what might happen there during the time between the last import and this step (+ add corresponding redirects).
Backup from Lithium, if it's needed.
Hi Roland.
I suggest few changes, mostly about the sequence of the steps.
# Import data to Lithium.
# Set up corresponding redirects on Lithium side (use 302 or 307 HTTP response).
# Change DNS to Lithium. This change will take effect for the whole internet in the time of A records TTL (time to live) before the change.
# Prevent Kitsune from writing to the database (e.g. DB permissions) in case someone accidentally gets there (which is very unlikely, but not all DNS caches and devices respect the TTL completely).
# Import to Lithium everything, what might happen on Kitsune during the time between the last import and this step (+ add corresponding redirects).
# Backup the database.
# After the n-week period, stop Kitsune servers (and make another db backup, if you want).
# Change the redirect HTTP code to 301.
This procedure should result in no outage and in the worst case, new questions, changes or user accounts will be temporarily unavailable if they were created between the two import steps.
In case of rollback:
# Allow database writes to Kitsune.
# Import data from Lithium + set up corresponding redirects.
# Change DNS to Kitsune and wait the time of A records TTL before this change.
# Prevent Lithium from writing to its database in case someone accidentally gets there.
# Import from Lithium everything, what might happen there during the time between the last import and this step (+ add corresponding redirects).
# Backup from Lithium, if it's needed.
A non-technical side note: we will add an explanation to both the GitHub repository and the documentation on readthedocs to make sure it's clear we no longer actively develop Kitsune and that everyone is welcome to use it and hack on it.
A non-technical side note: we will add an explanation to both the GitHub repository and the documentation on readthedocs to make sure it's clear we no longer actively develop Kitsune and that everyone is welcome to use it and hack on it.
Thanks for those steps, I believe those steps are actually what is going to be followed (or something every similar). My steps were vague, sorry about that :-)
I will ping the super helpful Giorgos Logiotatidis Mozilla web developer who's been helping us along with his fab manager Ben Sternthal to check out your steps. Lithium will do most of the steps for us except for the obvious Mozilla ones (like setting Kitsune to read only and providing a database dump to Lithium for the migration, etc).
Finally there will be no outage, my apologies if my vague steps implied that!
Cheers!
....Roland
Hi Michal:
Thanks for those steps, I believe those steps are actually what is going to be followed (or something every similar). My steps were vague, sorry about that :-)
I will ping the super helpful Giorgos Logiotatidis Mozilla web developer who's been helping us along with his fab manager Ben Sternthal to check out your steps. Lithium will do most of the steps for us except for the obvious Mozilla ones (like setting Kitsune to read only and providing a database dump to Lithium for the migration, etc).
Finally there will be no outage, my apologies if my vague steps implied that!
Cheers!
....Roland
Important: We should plan to keep the redirects operating for at least a year, since we have tons of thread-to-thread and thread-to-KB links. It's very discouraging to find a solution in web search and discover the critical links in it broken. Someday, they will break, but hopefully not in the first year.
Important: We should plan to keep the redirects operating for at least a year, since we have tons of thread-to-thread and thread-to-KB links. It's very discouraging to find a solution in web search and discover the critical links in it broken. Someday, they will break, but hopefully not in the first year.
''Matt [[#post-70575|said]]''
<blockquote>
Is there a test site to actually see what i being developed?
</blockquote>
This would be a good place:<BR>
https://developer.mozilla.org/en-US/
''Matt [[#post-70575|said]]''
<blockquote>
Is there a test site to actually see what i being developed?
</blockquote>
it's more of a construction zone at the moment, but if you want to get access to the staging site of the new sumo platform get in contact with madalina about it: https://support.mozilla.org/en-US/forums/contributors/712179
''cor-el [[#post-71177|said]]''
<blockquote>
What will be the future of the current API (Django REST)?
Will there still be raw data in JSON format available (questions,answers,users)?
</blockquote>
Sorry for the late reply Cor-el, I post a reply in the API thread at:
https://support.mozilla.org/en-US/forums/contributors/712382?last=71348#post-71348
