Sponsored Content
The Lounge What is on Your Mind? Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations Post 303045633 by Neo on Sunday 5th of April 2020 03:16:55 AM
Old 04-05-2020
Update (from one hour ago):


Updated the new community sites with latest posts, new users, likes, etc. from legacy site.

Ran an early preprocessing script against the legacy DB.

@Scrutinizer is testing a more refined version of preprocessing which will do even more migration magic. When he is ready, we will run his preprocessing script again the legacy DB and see how it looks.

Thanks for your patience.

We have already fixed the two bugs that we found in the initial launch; but are working to refine more custom bbcode issues.
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shell Script migration issues

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)
Discussion started by: arvindcgi
4 Replies

2. HP-UX

Migration - Compiler Issues.

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)
Discussion started by: helper
2 Replies

3. Programming

How to track table status delete/update/insert status in DB2 V10 z/os?

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)
Discussion started by: Perlbaby
1 Replies

4. What is on Your Mind?

Status of Migration of Moderation Systems

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)
Discussion started by: Neo
1 Replies

5. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Two

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)
Discussion started by: Neo
30 Replies

6. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Four

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
cmmigratepkg(1m)														  cmmigratepkg(1m)

NAME
cmmigratepkg - Migrate Serviceguard legacy Package to a Module Package. SYNOPSIS
cmmigratepkg -p package_name [-x extern_script] [-e] [-s] -o output_filename DESCRIPTION
cmmigratepkg is used to generate a modular package configuration file from a configured legacy package. cmmigratepkg expects the package to be a configured legacy package. The package can be up or down and the cluster can be on-line or off-line. The utility reads the control script of the package, so the package's control script must be located on the node where the command is run. cmmigratepkg can migrate packages created by Serviceguard version A.11.09 through A.11.18. The control script's customer-defined area is any code between "#START CUSTOMER DEFINED FUNCTIONS" and "#END CUSTOMER DEFINED FUNCTION. If the customer-defined area has code that needs to be migrated to the modular package then cmmigratepkg can create an external script by inserting the shell code from the control script into the external_script file. The external script is generated from the external template found in $SGCONF/examples/external_script.template. (See chapter 4 of the Managing Serviceguard manual for more information about the tem- plate.) The external_script_name is the full pathname and file name of the file. The extexternal scriptfile must be copied to each node where the package can run and make sure that the permissions are set to 744, and owned by root. Non-Serviceguard variables defined in the legacy package control script can be converted to user defined parameters called PEV, parameter environment variable. The PEV is defined in the package configuration file and has a prefix of "PEV_". See description under the -e option. The cmmigratepkg displays informational message about the variables which it cannot convert because they are non-Serviceguard variables. If these non-Serviceguard variables are used and defined in the customer defined area then there is no need to convert them to PEV. If they are defined in another location in the control script, and the values should be part of the package, they can be converted to PEV using the -e option. The PEV are defined in the new package configuration file. If non-Serviceguard functions are defined in the legacy package control script, cmmigratepkg lists the non-Serviceguard functions to STD- OUT. These functions are not converted. You must determine if the functions are called and how you want to migrate them to the modular package. You can put them into the new external script file. cmmigratepkg converts legacy failover packages that are configured with: Services, File Systems, Volume groups, Dependencies, EMS Resources, and User Defined Roles to modular packages. cmmigratepkg generates the modular package configuration file in lowercase. The package configuration file has no comments about the pack- age attributes. If the user wants to see comments regarding the package attributes, they can generate a temporary package configuration file using cmmakepkg -v. The following control script parameters are obsolete and the cmmigratepkg gives a warning about them not be able to convert: RAIDSTART, RAIDSTOP, RAIDTAB, MD, GFS, DATA_REP, and DTC_NAME. Note: that cmmigratepkg will not convert CVM3.5 packages or CFS packages. If you are converting packages please see the White paper for more details aboutconverting legacy packages. Options cmmigratepkg supports the following options: -p package_name Name of an existing configured legacy package to convert. -x external_script Name of the external script file to create. -e Generate PEV's from non Serviceguard parameters. All non Serviceguard parameters found in the package control script are con- verted to PEVs. "PEV_" is prepended to the original name. For example, package_root="/srv/colossus", is written as PEV_pack- age_root="/srv/colossus" in the output_file. -s This option comments out service attributes in the output_file. A warning is displayed when the option is used and the package has services defined. When using this option the user should review the output file. -o output_file Name of the output file for the converted package configuration. RETURN VALUE
cmmigratepkg returns the following values: 0 Successful completed. >0 Command failed. EXAMPLES
Converts pkgA writing out new package configuration file. cmmigratepkg -p pkgA -o /etc/cmcluster/pkg/pkgA/pkgA.conf Converts pkgA and also generates an external script. cmmigratepkg -p pkgA -x /etc/cmcluster/pkg/pkgA/external.sh -o /etc/cmcluster/pkg/pkgA/pkgA.conf" AUTHOR
cmmigratepkg was developed by HP. SEE ALSO
cmmakepkg(1m), cmgetconf(1m) Migration White Paper. Requires Optional Serviceguard Software cmmigratepkg(1m)
All times are GMT -4. The time now is 11:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy