Seperating queues (repost)

repost as i got no answer so far… maybe nobody noticed… ((-;

hello rt users,
i am happy rt user for 2 years or so, and run into a problem recently. i
hope that somebody will know how to solve it.

situation:
one RT2 instance running 4 main queues: TWS, nietypowe, abuse, problem.
first two are used internally and have something like 500 tickets total.
third one is used to catch incoming abuse reports and has 40 000
tickets. fourth is not used anylonger (we developed our own ticketing
system connected to CRM applications), but has 10 000 old tickets.
current db is postgres.

idea:
i want to:

  1. install RT3 on 2 servers and migrate to mysql (it was reported to be
    faster with rt).
  2. import abuse to server 1.
  3. import TWS and nietypowe to server 2.
  4. tar/gzip/rm -rf the rest

problem:
i have no idea how to do it…

hope somebody will show me the tools or procedure on doing this.
best regards,
Alek Cesarz : NOD manager : ALEK1-RIPE
+48 22 860 69 60 : Crowley Data Poland

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew.Tefft@trans.ge.com wrote:

Just a guess, but you can probably use the regular rt2 to rt3 migration
scripts to help with this. Those scripts just extract the data to text
files and then stuff them into the new db. Start with the standard
extract script and modify it to only extract the tickets for the ‘abuse’
queue (have it still extract ALL queues, users, etc. but not all the
tickets). Do the migration to server 1. Then change the script to
extract the TWS and nietypowe tickets and do the migration to server 2.
Then once rt is up and running you should be able to delete or disable
the unusued queues.

thanks for the response.
but your idea will leave me with approximately 30 000 unwanted users -
creators of tickets in “abuse” queue. is it possible to extract only
users who have opened tickets in particular queue and users who have
rights to access RT?
i don’t know if migration script is capable of doing that with just
modification. any of you code-warriors here could probably tell me that
by a quick glance at the script?


Alek Cesarz : NOD manager : ALEK1-RIPE
+48 22 860 69 60 : Crowley Data Poland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/zJ3KC3s32xNJGmERAr6EAKCfS4p48ls/0BjIdAL0WgvTbtpqvgCgpcON
5SCLvzydDyizi2uKxGWm33o=
=7zx2
-----END PGP SIGNATURE-----

Alek Cesarz wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew.Tefft@trans.ge.com wrote:

Just a guess, but you can probably use the regular rt2 to rt3 migration

scripts to help with this. Those scripts just extract the data to text
files and then stuff them into the new db. Start with the standard
extract script and modify it to only extract the tickets for the ‘abuse’
queue (have it still extract ALL queues, users, etc. but not all the
tickets). Do the migration to server 1. Then change the script to
extract the TWS and nietypowe tickets and do the migration to server 2.
Then once rt is up and running you should be able to delete or disable
the unusued queues.

thanks for the response.
but your idea will leave me with approximately 30 000 unwanted users -
creators of tickets in “abuse” queue. is it possible to extract only
users who have opened tickets in particular queue and users who have
rights to access RT?
i don’t know if migration script is capable of doing that with just
modification. any of you code-warriors here could probably tell me that
by a quick glance at the script?
Hello. Alek.

Now as I remember migration sripts don’t have any facility to do
dependent migration except time dependance.
Everything migrate step by step(users, groups, tickets…)
If you want to filter out Tickets and objects linked to them you have to
hack scripts a lot.

I think better idea is do full import then write contribution scripts
for different objects wiping. Contribution section already have one for
wiping out “deleted” Tickets. This scripts can form good package “RT
Shredder”.

So it’s not easy task as I think.

	Good luck. Ruslan.

PS. Everything above is only my opinion.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

people,
rt2 to rt3 import script allows skipping dead tickets. does it also
allow skipping disabled queues?

regards,


Alek Cesarz : NOD manager : ALEK1-RIPE
+48 22 860 69 60 : Crowley Data Poland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/zzXrC3s32xNJGmERAi2GAJ9jHiQhNU4AwoN0M4Ik+LVlUPv8nACgyyJl
RGDANAsDvmMEY0u+RlJ+fUE=
=yGlD
-----END PGP SIGNATURE-----