Subversion Maintenance – Adding Users

1. SSH to the subversion server
Putty to halsvn01.hq.halw.com

sudo to root:
The Unix team added sudoers file for mlr, ezf, and sst to be able to do the following, additional users would needed added by Unix team:

sudo /usr/bin/htpasswd -m /etc/httpd/conf/.htaccess
sudo /bin/vi /etc/httpd/conf/svn_acl
sudo /usr/bin/vim /etc/httpd/conf/svn_acl

originally Guillaume used:
sudo su -

2. Edit the configuration files

The following will allow you to enter the user's password:

cd /etc/httpd/conf
ls -la
htpasswd -m /etc/httpd/conf/.htaccess user-account

The following will allow defines access control in subversion:
vim svn_acl

vim command
[Esc] [:] [q] to quit without saving
[Esc] [:] "wq" to write (save) and quit

[i] - Insert

You will change users in groups which propagate down through the rest of the script, here's the start of the script:

[groups]

## For HAL
#developers
dev = aja, szb, ezf, sst, mlr, sxp, kxs, wgh, mad, mwm, c-rgong, c-rsmith, jeff, c-rradhakrishnan, jay, guillaume, c-mhartman, c-fcastro, c-dgreca, @rm, @rev, @qa

Searching for files

Use the attached Perl script in conjunction with the following example bash command:

for i in `perl findfiles.pl /home/jboss1/workspace_maven/hal-parent/hal-web/ .jsp`; do grep -il 'look for something'  $i; done

findfiles.pl (txt)

Cloning a VM Fixes

We had two configuration files that required changes after Brian received a cloned VM.  The haldevjbs04 (source) was changed to haldevjbs06 (target) and all was good again.

/etc/httpd/conf/httpd.conf
/etc/httpd/conf/workers.properties

Subversion folder needs deleted:
/home/jboss1/.subversion

Also, browser settings are copied too.

You should no longer have either of the following cron jobs running:

rm /etc/cron.hourly/jboss-config
rm /etc/cron.hourly/svn-update

Using mod_jk to hot cycle servers

-----Original Message-----
From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Sunday, March 25, 2012 5:28 AM
To: Tripp, Donald (HAL)
Cc: HAL DistList: IS UNIX; Flach, Cynthia (HAL); Ruckman, Maurice (HAL); jlindesm@redhat.com; Augustine, Anila (HAL); Hofsetz, Therron (HAL); Fillman, Eric (HAL); Thompson, Sonya (HAL); Phatak, Sheetal (HAL); Bojja, Sridhar (HAL Contractor)
Subject: Re: VMware status

Thanks Don,

If the servers need reboot while live, we can also disable half of the cluster through mod_jk without loosing session or outage. The algorithm will look like this:

a) On halprdjbs01 and halprdjbs02

-Disable halprdjbs01 and halprdjbs02 in halprdweb01 through jkstatus -Disable halprdjbs01 and halprdjbs02 in halprdweb02 through jkstatus -Wait for existing sessions to expire in haljbs01 and haljbs02 (sessions draining, can take several hours depending on usage) -Reboot halprdjbs01 and halprdjbs02 -Re enable halprdjbs01 and halprdjbs02 in halprdweb01 through jkstatus -Re enable halprdjbs01 and halprdjbs02 in halprdweb02 through jkstatus

b) Same on halprdjbs03 and halprdjbs04

-Disable halprdjbs03 and halprdjbs04 in halprdweb01 through jkstatus -Disable halprdjbs03 and halprdjbs04 in halprdweb02 through jkstatus -Wait for existing sessions to expire in halprdjbs03 and haljbs04 (sessions draining) -Reboot halprdjbs03 and halprdjbs04 -Re enable halprdjbs03 and halprdjbs04 in halprdweb01 through jkstatus -Re enable halprdjbs03 and halprdjbs04 in halprdweb02 through jkstatus