Migrating "vb thanks" to "discourse likes" (have not found a reliable simple solution to this yet except, of course pattern matching in the postgres DB is always an option, but this will be painfully slow).
Not sure how all the various kinds of attachments will migrate, since the vb site has many different legacy attachment methods, so we may not migrate over most of them.
Will not migrate the following:
PMs (no reason to migrate these).
Passwords (the hash functions are different so better to reset using "lost password", which works fine and all password will follow the discourse rules),
Please note, this information was copied from vbseo.com, now showing a database error. This is posted for reference since vbSEO seems to be going out of business:
If you ever need to uninstall vBSEO , you can use the following instructions. Make sure you carefully follow each step.
Login... (37 Replies)
Recently i found this for give to docker a "personal" ip
ip addr del 10.1.1.133/24 dev eth0
ip link add link eth0 dev eth0m type macvlan mode bridge
ip link set eth0m up
ip addr add 10.1.1.133/24 dev eth0m
route add default gw 10.1.1.1On container i did
... (0 Replies)
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Actually I was facing the following issue while building my Yocto SDK on Docker container
sudo docker build --tag="akash/eclipse-che:6.5.0-1" --tag="akash/eclipse-che:latest" /home/akash/dockerimage.yocto.support/
Sending build context to Docker daemon 26.93MB
Step 1/5 : FROM eclipse/cpp_gcc
... (3 Replies)
Hello All,
I had recently learnt a bit of Docker(which provides containerization process).
Here are some of my learning points from it.
Let us start first with very basic question:
What is Docker:
Docker is a platform for sysadmins and developers to DEPLOY, DEVELOP and RUN applications ... (7 Replies)
OK.
Like we all do, we learn a lot from tests, test migrations, and so forth.
Today, I started from scratch on test migration 2, armed with a lot more knowledge,
The main differences are as follows:
Installed discourse plugin ruby-bbcode-to-md before starting the install
Modified... (30 Replies)
Dear All,
After being active on the Node-RED forum for the last few weeks, I have been very impressed with Discourse, and my eyes have been opened.
https://www.discourse.org/
but not the paid /hosted offering, but using the open distribution:
https://github.com/discourse/discourse
... (52 Replies)
Discussion started by: Neo
52 Replies
LEARN ABOUT DEBIAN
vzmigrate
vzmigrate(8) Containers vzmigrate(8)NAME
vzmigrate - migrate a container between two OpenVZ servers
SYNOPSIS
vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID
DESCRIPTION
This utility is used to migrate a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate
either stopped or running container. For a stopped container, simple CT private area transfer is performed (rsync(1) is used for file
transfer). For running containers, migration may be offline (default) or online.
This program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without
entering password.
OPTIONS -r, --remove-area yes | no
Whether to remove a container area on source HN for the successfully migrated container. Default is yes.
--ssh=options
Additional options that will be passed to ssh while establishing connection to destination HN.
--rsync=options
Additional options that will be passed to rsync(8). You may add options like -z to enable data compression if you are migrating
over a slow link.
--keep-dst
Do not clean synced destination container private area in case of some error. It makes sense to use this option on big container
migration to avoid syncing container private area again in case some error (on container stop for example) occurs during first
migration attempt.
--online
Perform online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues
working as though nothing has happened.
-v Verbose mode. Causes vzmigrate to print debugging messages about its progress. Multiple -v options increase the verbosity. The
maximum is 3.
EXAMPLES
Migration of CT 101 to 192.168.1.130 with downtime:
vzmigrate 192.168.1.130 101
Online migration of CT 102 to 192.168.1.130:
vzmigrate --online 192.168.1.130 102
EXIT STATUS
0 EXIT_OK
Command completed successfully.
1 EXIT_USAGE
Bad command line options.
2 EXIT_VE_STOPPED
Container is stopped.
4 EXIT_CONNECT
Can't connect to destination (source) HN.
6 EXIT_COPY
Container private area copying/moving failed.
7 EXIT_VE_START
Can't start or restore destination CT.
8 EXIT_VE_STOP
Can't stop or checkpoint source CT.
9 EXIT_EXISTS
Container already exists on destination HN.
10 EXIT_NOTEXIST
Container does not exists on source HN.
12 EXIT_IP_INUSE
You attempt to migrate CT which IP address(es) are already in use on the destination node.
13 EXIT_QUOTA
Operation with CT quota failed.
SEE ALSO rsync(1).
COPYRIGHT
Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL.
OpenVZ 28 Jun 2011 vzmigrate(8)