[Labs-l] Tool Labs migration instructions

Alex Brollo alex.brollo at gmail.com
Tue Mar 4 21:24:46 UTC 2014


I successfully migrates itsource tool (owned by user alebot); our files are
into their right place BUT...
we lost out local installation of
https://pypi.python.org/pypi/internetarchive , the key module to run a
experimental, running  tool to upload into Internet Archive pdf files and
good metadata from a very interesting and large Italian library.

Some days ago I opened a bugzilla ticket to ask for global installation of
internetarchive module, but experienced users suggest to locally install
the module into the tool.

Can I ask you to push a little bit global installation of such an
interesting module? I tryed pip from new environment, with no success.

Alex brollo


2014-03-04 19:40 GMT+01:00 Marc A. Pelletier <marc at uberbox.org>:

> Hello All,
>
> As should come as no surprise given the number of advance warnings sent
> over the past couple months, the time for migration of the tool labs
> project from pmtpa to eqiad is at hand!
>
> [This email applies to tools on the Tool Labs /only/; if you have
> projects in labs, then you want to refer to the instructions given by
> Andrew Bogott in his previous email.]
>
> For roughly the following two weeks maintainers are encouraged to
> migrate their tools to the new eqiad datacenter by themselves.  At the
> end of that "free" migration period, we will migrate the remaining tools
> automatically but keep them disabled until the maintainers have the
> opportunity to look them over.
>
> You can find status and notes about the Tool Labs migration at:
>
> https://wikitech.wikimedia.org/wiki/Tool_Labs/Migration_to_eqiad
>
> == Migrating Tools ==
>
> Scripts have been provided to ease the transition.  From your *user*
> account on tools-login.wmflabs.org, you can do:
>
> $ migrate-tool <toolname>
>
> This will prepare your tool for migration, and schedule the data copy.
> More details are provided on-screen.  Do this for every tool for which
> you are the maintainer.  (If there is more than one maintainer, any one
> of them can perform the migration).
>
> This will also stop any jobs, webservice or cron entries.
>
> Once the copy is complete (you can check the status of the copy by
> issuing the migrate-tool command again) you can issue the following
> command from tools-login-eqiad.wmflabs.org:
>
> $ finish-migration <toolname>
>
> this will do the eqiad end of the migration.  Please be aware that it
> may take some time before the copy is started, as they are queued.
>
> Please also note that, to preserve space and bandwidth, log files are
> not copied over (that includes files ending in .out, .err and .log).  If
> you absolutely need to copy them over, then you can compress them first
> with gzip.
>
> *** IMPORTANT ***
>
> Migrating tools with those scripts carefully preserves all data IF IT IS
> ONLY ATTEMPTED ONCE.  If you run into troubles or issues, please contact
> me, and we'll fix you up.  They will not allow you to try again if
> something went wrong unless you work hard at it.  Don't.
>
> == Migrating Users ==
>
> You can migrate the contents of your home in pretty much the same way:
>
> $ migrate-user
>
> This will schedule a copy of your home directory to eqiad.  There is no
> second half of the script to run once it is complete.
>
> == Advanced Users ==
>
> If there are details you want to handle manually, you can 'ssh eqiad'
> from either tools-login or tools-dev (that includes being able to scp).
>
> == In case of panic ==
>
> Do not break glass; come on freenode IRC to the #wikimedia-labs channel
> and help can be found.  :-)
>
> -- Marc
>
> _______________________________________________
> Labs-l mailing list
> Labs-l at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/labs-l/attachments/20140304/f83c4ea4/attachment.html>


More information about the Labs-l mailing list