It has been a few days since my last status update, so here is a new, quick one:
@Scrutiziner and @Neo continue to work on the migration and are getting closer. The migration script provided OOTB by Discourse (the various BBCODE converters) mangled a lot of text; and @Scrutinzer has been leading the effort to get the various bbcode conversions as error free as practical. So far, so good.
Today, after more discussions with @Scrutinzer, I modified a Discourse theme component and added four new editor / composer buttons:
This was my first Discourse theme component modification, and frankly speaking, it was really easy (orders of magnitude easier, and infinitely faster debugging, than Discourse plugin development and testing).
Frankly, we don't want to get too much into editor / composer button modifications until people use it more; so this will probably be the only changes to the composer before going live (sooner than later). We can look for better icons on FontAwesome and get input from the people who matter the most, all of you!
@Scruitizer informs that he is getting closer to have his new Ruby preprocessing script ready for testing against the database, and he says he has been having a lot of fun with Ruby as well!
Hi All,
We will be doing a Solaris 8 to Solaris 10 migration migration, just wanted to know if there are any known / common issues arise from this migration from Shell script point of view.
I tried searching this site but mostly post are related to SA's question and jumpstart, etc. If there's... (4 Replies)
All,
We are migrating an application from HP-UX B.11.00 to HP-UX B.11.31 and both of them have the same informix version - 7.25se. However the compilers are different on both servers.
HP-UX B.11.00 - has B3913DB C.03.33 HP aC++ Compiler (S800)
HP-UX B.11.31 - has PHSS_40631 1.0 HP C/aC++... (2 Replies)
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
First a bit of history ....
A number of years ago one of our admins built a number of plugin systems for moderation, including (1) a voting system, (2) a "user feelings" system and (3) a confidential posting system. During this time, I was busy on other projects, not very active in the forums,... (1 Reply)
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)
Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily:
Insuring ruby-bbcode-to-markdown is enabled.
Removing line breaks from ICODE to markdown in migration script.
Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 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)
04-09-2020
