Basically +1, just wondering if there should be a statement on long-term availability of services offered on wmflabs, or if the current Etherpad instance should be replaced by Etherpad Lite.

If this were to be done, please ensure that it is communicated widely, and emough time is given to users to move elsewhere from etherpad.wikimedia.org. I suggest a month at least.

Bug 46637 is a blocker. I'd mark this LATER but I can't, so Lowest.

http://epl.wikimedia.org

going to redirect this URL to the new installation soon and after that this can be closed

(In reply to comment #5)

going to redirect this URL to the new installation soon and after that this
can
be closed

Meaning that the pads will be migrated there?

01:29 < mutante> importing Etherpads to Etherpad lite using convert script.. fail
01:29 < mutante> TypeError: undefined is not a function
..
01:40 < LeslieCarr> i don't know if ti will actually be possible
01:40 < LeslieCarr> are we seriously against just making a clean sweep
01:40 < LeslieCarr> warning folks that it's all going away in 30 days
...
01:41 < mutante> LeslieCarr: i hope that's an option, yea
01:41 < mutante> still trying to ask #etherpad-lite-dev though
01:41 < mutante> or well.. at least report the bug
..
01:44 < mutante> at Object.<anonymous> (/usr/share/etherpad-lite/bin/convert.js:37:17)
..

01:40 < mutante> helo. trying to import from classic Etherpad to Etherpad-lite using the convert script and i get:
01:40 < mutante> TypeError: undefined is not a function at Object.<anonymous> (/usr/share/etherpad-lite/bin/convert.js:37:17)
01:55 < marktraceur> Hi mutante!
01:55 * marktraceur looks
01:56 < marktraceur> mutante: Are we running the latest master?
01:56 < marktraceur> If not, which version?
02:07 < marktraceur> It might be because the newer versions of node-mysql don't have a Client constructor, but the version we're using would help make sure
02:08 < marktraceur> Alternatively there's no library for mysql on the machine, because it's not (maybe) in the package.json
02:12 < marktraceur> I take that back, it's part of the ueberdb dependencies
02:13 < marktraceur> So yeah, what version?
..
03:15 < mutante> hi marktraceur , back
03:16 < mutante> etherpad-lite 1.0-wm2

..

Updating summary per comment 7.

More info from #wikimedia-operations:

13.22 < mutante> here's the good thing:
13.22 < mutante> 03:48 < JohnMcLear2> mutante: so i might be able to free up a few hours on Sunday, I will keep Mark posted
13.22 < mutante> and that is somebody who is a #etherpad-lite-dev and will be in HKG
13.23 < mutante> maybe we'll also get a newer version than http://apt.wikimedia.org/wikimedia/pool/main/e/etherpad-lite/
13.23 < mutante> and i still need to get this to build: https://gerrit.wikimedia.org/r/#/c/76654/ sigh

• Bug 28601 has been marked as a duplicate of this bug. ***

(From bug 52831 comment #6)

Most of etherpad.wikimedia.org running etherpad was automatically imported to
etherpad-lite using the (patched by me to actually run, more info at
https://rt.wikimedia.org/Ticket/Display.html?id=5464 ) convert.js script
provided by etherpad-lite.

The old pads are still available at etherpad-old.wikimedia.org (albeit as
read-only)

I don't think that "Disable etherpad.wikimedia.org after migrating content to Etherpad Lite" makes sense as we will NOT disable that URL.

(In reply to comment #5)

going to redirect this URL to the new installation soon and after that this
can be closed

This seems to have happened already?

(In reply to comment #11)

I don't think that "Disable etherpad.wikimedia.org after migrating content to
Etherpad Lite" makes sense as we will NOT disable that URL.

The summary refers to the Etherpad installation then named after the URL, not to the URL in itself. Is there a more specific name than "Etherpad" for it?

(In reply to comment #5)

going to redirect this URL to the new installation soon and after that this
can be closed

This seems to have happened already?

I don't know, but this bug is not fixed until bug 52831 is fixed; I suppose a new import may be needed, among other things.
We also lack information on whether etherpad.wflabs.org content will be merged to the new etherpad lite; this bug assumed that the old etherpad lite was going to survive.

(In reply to comment #12)

I don't know, but this bug is not fixed until bug 52831 is fixed; I suppose a
new import may be needed, among other things.

For the records, it was needed and edits made between the first and the new import were lost.

We also lack information on whether etherpad.wflabs.org content will be
merged
to the new etherpad lite; this bug assumed that the old etherpad lite was
going
to survive.

Still lacking. The situation will not be clean (bug 46539) as long as we have multiple etherpad installations in use.

Since now etherpad.wikimedia.org is Etherpad-Lite and epl.wikimedia.org is merely a redirect to the same thing there is no old Etherpad (non-Lite) anymore, so i'd say the ticket is resolved.

Wait, not correct, technically there is http://etherpad-old.wikimedia.org/ so there is an old installation we will keep, the question is just how long.

(In reply to comment #15)

Wait, not correct, technically there is http://etherpad-old.wikimedia.org/ so
there is an old installation we will keep, the question is just how long.

How about the wmflabs instance which has been recommended for use by some for a while? I know it's not ops' realm/responsibility as a production website, but how hard it is to merge the two etherpad lite DBs?

etherpad.wikimedia.org is the way to go.
etherpad.wmflabs.org is dead and tells you so.
epl.wikimedia.org redirects to etherpad.wikimedia.org.

Closing as FIXED.

Found a bug in the migration/conversion script: https://github.com/ether/etherpad-lite/issues/1954 (convert.js doesn't migrate saved revisions from etherpad to etherpad lite)