info:devel:gmu
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
info:devel:gmu [2015/11/28 10:13] |
info:devel:gmu [2015/12/31 10:49] (current) |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| ==What you need:== | ==What you need:== | ||
| - | * '//root//' access to a supported export platform (Verio FreeBSD 6.4 or Verio CentOS4.9) | + | * '//root//' access to a supported export platform (Verio FreeBSD 6.4 or Verio CentOS 4.9) |
| * A couple of GB of free space on that server. | * A couple of GB of free space on that server. | ||
| Line 76: | Line 76: | ||
| To do the actual export run one of the two commands: | To do the actual export run one of the two commands: | ||
| - | =To store export locally:= | + | **To store export locally:** |
| export_box# ./verio-to-blueonyx-exporter.pl 2>&1 | tee export.log | export_box# ./verio-to-blueonyx-exporter.pl 2>&1 | tee export.log | ||
| - | =To store export remotely:= | + | **To store export remotely:** |
| On the remote server add '/root/.ssh/id_rsa.pub' from the export server to '/root/.ssh/authorized_keys'. Then create the import directory there: | On the remote server add '/root/.ssh/id_rsa.pub' from the export server to '/root/.ssh/authorized_keys'. Then create the import directory there: | ||
| Line 102: | Line 102: | ||
| ==Setup of the importer:== | ==Setup of the importer:== | ||
| - | The importer is named 'blueonyx-gmu' and is available in the BlueOnyx 5209R YUM repository. To install it on a 5209R run the following command: | + | The RPM that contains the importer is named 'blueonyx-gmu' and is available in the BlueOnyx 5209R YUM repository. To install it on a 5209R run the following command: |
| yum install blueonyx-gmu | yum install blueonyx-gmu | ||
| Line 137: | Line 137: | ||
| | -r | <vsites><users><resellers> | If an import failed for any reason, then you can use '-r vsites' to remove all Vsites (and Users). If you want to only remove all Users (not System-Administrators!), then you can use '-r users'. If you use '-r resellers', then all Reseller accounts (including their Vsites and Users!) will be removed. | | | -r | <vsites><users><resellers> | If an import failed for any reason, then you can use '-r vsites' to remove all Vsites (and Users). If you want to only remove all Users (not System-Administrators!), then you can use '-r users'. If you use '-r resellers', then all Reseller accounts (including their Vsites and Users!) will be removed. | | ||
| | -a | <none> | If specified, no Reseller accounts will be created during import. | | | -a | <none> | If specified, no Reseller accounts will be created during import. | | ||
| + | | -s | <none> | Vsite that already exists on server doesn't get imported. | | ||
| | -e | <none> | Does not perform an import. Instead it will check the integrity of the XML file and the TarBalls in the specified import directory. | | | -e | <none> | Does not perform an import. Instead it will check the integrity of the XML file and the TarBalls in the specified import directory. | | ||
| - | | -q | <none> | Does not perform an import. If with this option, then any Vsite or User that is over quota (or at +90% disk usage) will receive enough additional disk space to end the over-quota situation. This option is used automatically at the end of an import. | | + | | -q | <none> | Does not perform an import. If run with this option, then any Vsite or User that is over quota (or at +90% disk usage) will receive enough additional disk space to end the over-quota situation. This option is used automatically at the end of an import. | |
| + | | -p | <none> | Does not perform an import. This will read the server wide PHP settings and will apply them to all Vsites. | | ||
| | -h | <none> | Display the help text and exit. | | | -h | <none> | Display the help text and exit. | | ||
| Line 267: | Line 269: | ||
| ===== Technical Details ===== | ===== Technical Details ===== | ||
| - | This code is pretty insane. No way around it. Maybe it's my Swansong or my 9th Symphony. Time will tell. What it does on a technical level is this: | + | This [[http://devel.blueonyx.it/trac/browser/BlueOnyx/5209R/utils/blueonyx-gmu|code is pretty insane]]. No way around it: |
| + | |||
| + | * [[http://devel.blueonyx.it/trac/browser/BlueOnyx/5209R/utils/blueonyx-gmu/src/blueonyx-gmu/blueonyx-gmu/verio-to-blueonyx-exporter.pl|Exporter]] | ||
| + | * [[http://devel.blueonyx.it/trac/browser/BlueOnyx/5209R/utils/blueonyx-gmu/src/blueonyx-gmu/blueonyx-gmu/blueonyx-import.pl|Importer]] | ||
| + | |||
| + | Maybe it's my Swansong or my 9th Symphony. Time will tell. What it does on a technical level is this: | ||
| ====The Exporter==== | ====The Exporter==== | ||
| Line 301: | Line 308: | ||
| The importer is supposed to be the "receiving end" of dumps from various export platforms. So it needed to be general enough to handle all eventualities. | The importer is supposed to be the "receiving end" of dumps from various export platforms. So it needed to be general enough to handle all eventualities. | ||
| - | It's only half as complex as the exporter, as the data will have to conform to certain minimum requirements in regards to what is in the XML and the TarBalls. From there it's just the relatively simple task of reading the Exported Hashes out of the XML and turning them into CCEd CREATE and SET transactions that create the desired objects and populate them with the correct data. | + | It's only half as complex as the exporter, as the data will have to conform to certain minimum requirements in regards to what is in the XML and the TarBalls. From there it's just the relatively simple task of reading the exported Hashes out of the XML and turning them into CCEd CREATE and SET transactions that create the desired objects and populate them with the correct data. |
| The only big complexity was to identify anything that could go wrong during an import and to automatically correct these problems instead of throwing an error message. | The only big complexity was to identify anything that could go wrong during an import and to automatically correct these problems instead of throwing an error message. | ||
info/devel/gmu.1448665998.txt.gz · Last modified: 2015/11/28 10:13 by
Page Tools
