[rt-users] What criteria do you use when deciding the number of instances of RT?

[Bob Goldstein]

  I work in a university computer center.  We try to set up
  an instance per department or other large unit (e.g. college)
  on request.  Part of it is, I can hand the instance to an
  admin and say "have fun".  They can then handle new users,
  privs, new queues, etc.  (I have to connect email addresses
  to new queues, though.)

  There are many ways, all good.  It partly depends on how much
  control a given unit wants over it's RT instance, to a lesser extent
  the security of isolating instances, and the nuissance of wanting
  to transfer tickets between instances.

  A downside of many instances is that you can't transfer tickets
  between them, and you need someone to take care of each instance.
  We do the sysadmin work, but the dept has to deal with adding
  consultants, etc.  

    bobg

>
>Hi All,
>
>My question is both hypothetical and practical.  I've got RT deployed in my
>I.T. department doing what it does best and it's working well.  I've put
>feelers out to some other departments that I think could benefit from RT to
>see if they would be interested in having it setup for them.  I am finely
>getting some positive responses so I'm looking for some guidance on
>deployment options.  I am trying to decide if I should share an instance of
>RT among 1+ departments or create a new instance of RT for each department.
>Hardware is not an issue either way, nor does it look like the traffic
>volume will be an issue.  These are all internally created tickets with no
>Internet access to my RT instance.  If Internet access were required then a
>separate instance of RT would be desirable.
>
>So what I am looking for from people who have either had this issue or
>thought about it is: what factors you would take into account when deciding
>on 1 or more instances of RT and why.
>
>Thanks,
>
>James
>
>------=_Part_21836_23723461.1199922791092
>Content-Type: text/html; charset=ISO-8859-1
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>
>Hi All,<br><br>My question is both hypothetical and practical.  I've 
>got RT deployed in my I.T. department doing what it does best and it's wor
>king well.  I've put feelers out to some other departments that I thi
>nk could benefit from RT to see if they would be interested in having it setup
> for them.  I am finely getting some positive responses so I'm lookin
>g for some guidance on deployment options.  I am trying to decide if I sh
>ould share an instance of RT among 1+ departments or create a new instance of 
>RT for each department.  Hardware is not an issue either way, nor does it
> look like the traffic volume will be an issue.  These are all internally
> created tickets with no Internet access to my RT instance.  If Internet 
>access were required then a separate instance of RT would be desirable.
><br><br>So what I am looking for from people who have either had this issue or
> thought about it is: what factors you would take into account when deciding o
>n 1 or more instances of RT and why.<br><br>Thanks,<br><br>James<br>
>
>------=_Part_21836_23723461.1199922791092--
>
>--===============0413921889==
>Content-Type: text/plain; charset="us-ascii"
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>
>_______________________________________________
>http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
>Community help: http://wiki.bestpractical.com
>Commercial support: sales at bestpractical.com
>
>
>Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
>Buy a copy at http://rtbook.bestpractical.com
>--===============0413921889==--
>