topic Re: S/W Deployment in Operating System - HP-UX

S/W Deployment

william_39 — Sun, 14 Apr 2002 12:07:54 GMT

Dear all,
I need one help for distributing my ProC source code's executables on hp servers, which are geogrphically distributed on different different locations.

For this i need to compile source code on each server, condition is i dont want onsite team to have any control on source code, infact source code should not go in their hand, only executables be with them.

Any suggestion to achive this task ?

Thanks & Regards
william

Re: S/W Deployment

steven Burgess_2 — Sun, 14 Apr 2002 12:28:51 GMT

Hi

Have a read of the following

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90127/B2355-90127_top.html&con=/hpux/onlinedocs/B2355-90127/00/00/5-con.html&toc=/hpux/onlinedocs/B2355-90127/00/00/5-toc.html&searchterms=software%7cinstall%7cremote&queryid=20020414-063032

I'ts regarding the software distributor that comes with HP and advises what is required to enable you to distribute software remotely

Is this what you were looking at ?

Hope this helps

Regards

Steve

Re: S/W Deployment

Sridhar Bhaskarla — Sun, 14 Apr 2002 17:22:52 GMT

Hi William,

You do not need to copy the source code to every system and compile. You can build executables on one system, build a depot containing the executables using swpackage command and then install it through swinstall. Look at the following URL for documentation on SD-UX

http://docs.hp.com/hpux/onlinedocs/B2355-90154/B2355-90154.html

Look at the section "creating software packages"

And remember, you may need to build executables suitable to each platform if you don't have similar kind of systems.

-Sri

Re: S/W Deployment

Duncan Edmonstone — Sun, 14 Apr 2002 17:51:53 GMT

You could take a look at rdist (just type man rdist), which will allow you to push files out to many systems, and call commands after they are pushed out.

Do your on-site teams have root access? if so, there's not really any simple way to protect the source code on the local systems, as they will be able to get access one way or another. In this scenario you would need to copy the code just for the time period you need to compile, and then remove it - even then, a smart admin at a local site could get at it. The best answer is (as Sridhar stated) to compile everything at your site, and then distribute.

If the local teams don't have root access then simply distribute everything to a root-only accessible staging area, compile the code, delete the source, and move the code out to its final location.

HTH

Duncan

Re: S/W Deployment

Wodisch — Sun, 14 Apr 2002 18:40:20 GMT

Hi,

I would go for "rsync" (see: http://rsync.samba.org ) and use it do distribute only the binaries. The nice thing about "rsync" is that it does check wether the transfer is neccessary and only then do it - could save you a lot of time and bandwidth...

Just my $0.02,
Wodisch