nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TeamSite Instances

mmb

Hi

Please could you give me your opinion on this idea.... (I do not think it is a good idea but management are pushing for it and I would appreciate some good technical reasons why not to do it!)

We are going to upgrade our production teamsite system to v6.1 sp1, and implement a dual-server HA cluster using Veritas cluster server.

The idea is to install and run the production instance active on only one of the two nodes at any one time. Management want to install and run a separate development instance of teamsite on the dormant node of the cluster for cost saving purposes.

I have said that it will be a bad idea to try and install 2 teamSite instances on the same server, and this would compromise the integrity of the Production system. Shared files like /etc/iw.cfg would be affected, plus other server dependant configuration files, and possibly other system level utilities.

Personally I am fighting for a stand alone dev teamsite environment on its own server - we have this at the moment but they are trying to decomission it for cost savings!!

Could you please give me your opinions on this idea?

many thanks

- mark

Edited by mmb on 10/20/04 03:58 AM (server time).

Find more posts tagged with

Comments

Michael

Hi Mark

It is like a story straight from Dilbert.... I feel your pain.

IMO it would be suicide to:
a) run two instances of TeamSite on one box
OR
b) perform development on your production server

To try and do a) AND b) is just mad.

If you want an enterprise quality solution than you need to invest in the appropriate systems. Generally you would need at least three standalone environments - dev, test, and prod.

Perhaps if you ask for three environments they will let you keep two?

Best of luck with those management games!

Cheers
Michael

herald10

When we had the same problem of decomissioning due to cost reasons, we decided to go with a development branch on the production teamsite server itself. So far its has not created any problems for us.

hth
-H

Michael

I guess it depends what kind of development you are doing...(if any)

For example, a single server rules out UI customisation development on a 6.x environment as you can't be doing webapp rebuilds on your production server.... unless you have unusually patient and understanding users

.

Cheers
Michael

herald10

Thats true. Actually we are still on Teamsite 5.5.2. Before moving to 6.x we are planning to install it on a temp box and do all the customizations and then move all the Teamsite assets to it. Once its working to our satisfaction we probably will make it our production box removing the old one all together.

Thanks
-H

Adam Stoller

Unless I've missed something in the 6.x docs - you *cannot* have two versions - or two instances of the same version - of TeamSite installed on a single machine. (a) there are kernel issues to deal with (b) there are a bunch of files in /etc to deal with.

I believe that should be sufficient as a technical reason why not to try to do this.

I agree with the other responses - if you cannot afford a separate development server box - use a development branch -- it's not quite the same thing, as you can screw up production work by making changes to any of the centralized config files (iw.cfg, templating.cfg, available_templates.cfg, etc.).

Alternatively - give up the idea of HA clustering and use both existing servers - one for production, one for development.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

mmb

Thanks to all for your replies on this. It all backs up exactly what I was thinking myself.

The sort of development we would be doing would be UI customisations, workflow development, templates & deploy scripts.

It would be madness to tow the management line on this one, so I am going back with these comments as ammo!

thanks again
- mark

TCavanaugh

We ran the HA version of the products on a Windows 2000 cluster (actually, 2 clusters) for about a year and were not "impressed". We reverted these servers from clusters back to standalone servers. There is very little benefit actually realized by adding clustering to a TeamSite installation - keep your environment simple to maintain reliability.