[rt-users] RT-Extention-Assets (1.05) - Lifecycle Question

[Carl van Litsenborgh]

Hi,

I have updated my Assets_Config.pm file to include a second Asset Lifecycle as 
follow (added a new state called "devel" under active):

Set(%Lifecycles,
assets2 => {
type => "asset",
initial  => [
'new' # loc
],
active   => [
'allocated', # loc
'devel',
'in-use' # loc
],
inactive => [
'recycled', # loc
'stolen', # loc
'deleted' # loc
],

defaults => {
on_create => 'new',
},

transitions => {
''=> [qw(new allocated in-use)],
new   => [qw(allocated in-use stolen deleted)],
allocated => [qw(in-use recycled stolen deleted)],
devel => [qw(allocated in-use)],
"in-use"  => [qw(allocated recycled stolen deleted)],
recycled  => [qw(allocated)],
stolen=> [qw(allocated)],
deleted   => [qw(allocated)],
},
rights => {
'* -> *'=> 'ModifyAsset',
},
actions => {
'* -> allocated' => {
label => "Allocate" # loc
},
'* -> in-use'=> {
label => "Now in-use" # loc
},
'* -> recycled'  => {
label => "Recycle" # loc
},
'* -> devel' => {
label => "Under Development"
},
'* -> stolen'=> {
label => "Report stolen" # loc
},
},
},
);

When I create a new Catalog, this new lifecycle is shown, and I can create a 
new Catalog "linked" to this lifecycle (i.e. assets2).

When I create a new asset, all is OK, BUT the new status "devel" is NOT in the 
drop-down list! WHY?
Even after creation, I cannot change to this state!

Any help is appreciated.

Thank you.

Carl van Litsenborgh

[rt-users] Allowing Users to add other users from Self Service

[Scott Undercofler]

Hi all:

	I have an RT installation that we are expanding to encompass some 
"hosted" ticketing as part of a larger project. In effect, we have a 
dozen groups with RT that are part of one company. They have requested 
that we allow them to add other people within their groups to a ticket.


	I see the watchAsAdminCC there, but I don't see any way for them to add 
others. I was wondering if anyone had any suggestions.


	The groups are set up in a hierarchy where there are a few "core" 
members that belong to the core group, then a dozen other "team" groups 
that report to the core group. The core group members are also members 
of every team group so they get added to every ticket.


 	The only thing I could think of without getting too fancy was to add 
a customfield to the ticket that only members of these two groups had 
rights to, and allow the core team the ability to choose one of the 
other teams from a drop down, then add a scrip to recognize changes to 
this field and add groups. That seems very cumbersome.


Thanks in advance!

Re: [rt-users] RT 4.2.12 and CentOS 7

[Landon Stewart]

On Sep 2, 2015, at 10:23 AM, Tom Misilo 
> wrote:

Hi,

I was wondering if anyone has successfully used “make fixdeps” with Request 
Tracker on CentOS 7? As it seems like cpan only installs to the local users 
home directory in a ~/perl5 folder and not systemwide. Which when using Request 
Tracker and mod_fcgid  apache does not find any of the modules.

Are you running 'make fixdeps' as root privileges?



Landon Stewart : lstew...@iweb.com
Lead Specialist, Abuse and Security Management
Spécialiste principal, gestion des abus et sécurité
http://iweb.com : +1 (888) 909-4932

[rt-users] RT and Disaster Recovery - problem

[Guadagnino Cristiano]

Hi all,
are you using some kind of DR solution with RT?

Our RT servers are virtualized on VMware. As a DR solution, we keep 
virtual machines on our second datacenter in sync with the first one.
VMs on the second data center are switched off.

If we have problems on the first data center, we power on the VMs on the 
second and then change our DNS to point to the new VMs.
The only difference on the mirrored VMs is that thay have different IPs.

So, right after powering them up, we have to connect and change the 
configuration of those VMs to use the new IPs (at least in those cases 
where we cannot use DNS aliases).

This is acceptable for us, because RT is not such a critical asset that 
we cannot afford a downtime of a few minutes.

However, the problem is that - after reconfiguring the VMs - RT becomes 
slow as a snail (tens of seconds for each page change/refresh).

I lost a couple of days building an exact copy of our production VMs and 
experimenting with varying IPs and reconfiguring, and I am not able to 
overcome the problem, nor understand where it comes from.

Has anybody ever heard of such a problem?

T.I.A.
Cris

Re: [rt-users] RT and Disaster Recovery - problem

[Alex Vandiver]

On Wed, Sep 02, 2015 at 03:11:52PM +, Guadagnino Cristiano wrote:
> Our RT servers are virtualized on VMware.
> [snip]
> However, the problem is that - after reconfiguring the VMs - RT becomes 
> slow as a snail (tens of seconds for each page change/refresh).

Do the VMs have any snapshots enabled?  I know that historically, at
least, the mere presence of a snapshot file caused all I/O to be COW,
which caused order-of-magnitude I/O bandwidth degradation.
 - Alex

Re: [rt-users] RT and Disaster Recovery - problem

[Guadagnino Cristiano]

Hi Aaron,
and thank you for the quick reply.


 > What OS/distro are you running?
Centos 6.7

 > Are you using Apache, Nginx or something else to serve up RT?
Apache/2.2.15 (CentOS) Server at localhost Port 80

 > Have you checked that DNS is resolving properly on your machine?
Yes, DNS is warking properly and very fast. However, on my test VMs I
have used only IPs to avoid putting the DNS into the equation.

 > Are commands you run from the shell taking a long time to run, or is
it just RT?
Apparently it is just RT


Thank you!
Cris


Cristiano Guadagnino

Servizio Sistemi Dipartimentali, Periferici e DB
___
Bankadati Servizi Informatici Soc.Cons.P.A.
Gruppo bancario Credito Valtellinese
VIA TRENTO, 22 - 23100 SONDRIO
tel +39 0342522172  - fax +39 0342522997
guadagnino.cristi...@creval.it
www.creval.it

Il presente messaggio non è di natura personale ma inviato per esigenze 
lavorative; l’eventuale messaggio di risposta potrà essere conosciuto anche da 
altri soggetti diversi dall’originatore di questo messaggio per dette esigenze 
o per controllo aziendale. Questo messaggio, corredato dei relativi allegati, 
contiene informazioni da considerarsi strettamente riservate, ed è destinato 
esclusivamente al destinatario sopra indicato, il quale è l'unico autorizzato 
ad usarlo, copiarlo e, sotto la propria responsabilità, diffonderlo. Chiunque 
ricevesse questo messaggio per errore o comunque lo leggesse senza esserne 
legittimato è avvertito che trattenerlo, copiarlo, divulgarlo, distribuirlo a 
persone diverse dal destinatario è severamente proibito, ed è pregato di 
rinviarlo immediatamente al mittente distruggendone l'originale.

-Messaggio originale-
Da: Aaron C. de Bruyn 
Inviato: Wed Sep 02 2015 17:26:02 GMT+0200 (CEST)
A: Guadagnino Cristiano 
Cc: "rt-users@lists.bestpractical.com" 
Oggetto: Re: [rt-users] RT and Disaster Recovery - problem

> I have not run into the issue, but we can try and figure out where the
> slowness is coming from.
>
> What OS/distro are you running?
>
> Are you using Apache, Nginx or something else to serve up RT?
>
> Have you checked that DNS is resolving properly on your machine?
> (type: host google.com and see how long it takes for an answer)
>
> Are commands you run from the shell taking a long time to run, or is it just 
> RT?
>
> -A
>
>
> On Wed, Sep 2, 2015 at 8:11 AM, Guadagnino Cristiano
>  wrote:
>> Hi all,
>> are you using some kind of DR solution with RT?
>>
>> Our RT servers are virtualized on VMware. As a DR solution, we keep
>> virtual machines on our second datacenter in sync with the first one.
>> VMs on the second data center are switched off.
>>
>> If we have problems on the first data center, we power on the VMs on the
>> second and then change our DNS to point to the new VMs.
>> The only difference on the mirrored VMs is that thay have different IPs.
>>
>> So, right after powering them up, we have to connect and change the
>> configuration of those VMs to use the new IPs (at least in those cases
>> where we cannot use DNS aliases).
>>
>> This is acceptable for us, because RT is not such a critical asset that
>> we cannot afford a downtime of a few minutes.
>>
>> However, the problem is that - after reconfiguring the VMs - RT becomes
>> slow as a snail (tens of seconds for each page change/refresh).
>>
>> I lost a couple of days building an exact copy of our production VMs and
>> experimenting with varying IPs and reconfiguring, and I am not able to
>> overcome the problem, nor understand where it comes from.
>>
>> Has anybody ever heard of such a problem?
>>
>> T.I.A.
>> Cris
>

--

[rt-users] RT 4.2.12 and CentOS 7

[Tom Misilo]

Hi,

I was wondering if anyone has successfully used "make fixdeps" with Request 
Tracker on CentOS 7? As it seems like cpan only installs to the local users 
home directory in a ~/perl5 folder and not systemwide. Which when using Request 
Tracker and mod_fcgid  apache does not find any of the modules.

Thank you,

Tom

Re: [rt-users] RT and Disaster Recovery - problem

[Aaron C. de Bruyn]

I have not run into the issue, but we can try and figure out where the
slowness is coming from.

What OS/distro are you running?

Are you using Apache, Nginx or something else to serve up RT?

Have you checked that DNS is resolving properly on your machine?
(type: host google.com and see how long it takes for an answer)

Are commands you run from the shell taking a long time to run, or is it just RT?

-A


On Wed, Sep 2, 2015 at 8:11 AM, Guadagnino Cristiano
 wrote:
> Hi all,
> are you using some kind of DR solution with RT?
>
> Our RT servers are virtualized on VMware. As a DR solution, we keep
> virtual machines on our second datacenter in sync with the first one.
> VMs on the second data center are switched off.
>
> If we have problems on the first data center, we power on the VMs on the
> second and then change our DNS to point to the new VMs.
> The only difference on the mirrored VMs is that thay have different IPs.
>
> So, right after powering them up, we have to connect and change the
> configuration of those VMs to use the new IPs (at least in those cases
> where we cannot use DNS aliases).
>
> This is acceptable for us, because RT is not such a critical asset that
> we cannot afford a downtime of a few minutes.
>
> However, the problem is that - after reconfiguring the VMs - RT becomes
> slow as a snail (tens of seconds for each page change/refresh).
>
> I lost a couple of days building an exact copy of our production VMs and
> experimenting with varying IPs and reconfiguring, and I am not able to
> overcome the problem, nor understand where it comes from.
>
> Has anybody ever heard of such a problem?
>
> T.I.A.
> Cris

Re: [rt-users] RT 4.2.12 and CentOS 7

[Joseph D. Wagner]

I got it working by doing a complete gut and replacement with the Perl
packages from Fedora 21.

 

From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf
Of Tom Misilo
Sent: Wednesday, September 02, 2015 10:24 AM
To: 'rt-users@lists.bestpractical.com'
Subject: [rt-users] RT 4.2.12 and CentOS 7

 

Hi,

 

I was wondering if anyone has successfully used "make fixdeps" with Request
Tracker on CentOS 7? As it seems like cpan only installs to the local users
home directory in a ~/perl5 folder and not systemwide. Which when using
Request Tracker and mod_fcgid  apache does not find any of the modules.

 

Thank you,

 

Tom

 

 

Re: [rt-users] RT 4.2.12 and CentOS 7

[Andrew Marosi]

I go it working - wasn't the easiest; but it's working great:

[root@uslaxrt ~]# uname -a
Linux uslaxrt.corp.x.com 3.10.0-229.1.2.el7.x86_64 #1 SMP Fri Mar 27 
03:04:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@uslaxrt ~]# cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)

MySQL  + Index tables
mysqld (mysqld 5.5.43-MariaDB)

[root@uslaxrt ~]# perl -V
Summary of my perl5 (revision 5 version 16 subversion 3) configuration:
Built under linux
  Compiled at Mar  6 2015 05:05:52
  @INC:
/usr/local/lib64/perl5
/usr/local/share/perl5
/usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl
/usr/lib64/perl5
/usr/share/perl5

From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Tom Misilo
Sent: Wednesday, September 2, 2015 10:24 AM
To: 'rt-users@lists.bestpractical.com' 
Subject: [rt-users] RT 4.2.12 and CentOS 7

Hi,

I was wondering if anyone has successfully used "make fixdeps" with Request 
Tracker on CentOS 7? As it seems like cpan only installs to the local users 
home directory in a ~/perl5 folder and not systemwide. Which when using Request 
Tracker and mod_fcgid  apache does not find any of the modules.

Thank you,

Tom