Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Data Storage Software

Distributing In-House Engineering Code? 49

caswelmo asks: "My company has recently moved from Solaris workstations to Windows workstations (Ohhh, the humanity). As an engineering focused company, we use our computers to run many in-house (command line) codes to analyze and design our products. We currently use NAS storage to store everything and use batch files and init scripts to run the correct codes over the network. This makes sure everyone is running the latest version. This also stinks. I know this isn't an original problem, so what are some other solutions for rolling out lots of simple codes like this?"
This discussion has been archived. No new comments can be posted.

Distributing In-House Engineering Code?

Comments Filter:
  • by MerlynEmrys67 ( 583469 ) on Sunday December 05, 2004 @01:02AM (#10999900)
    You did a platform migration before you had even a clue how to perform business critical functionality ?

    I don't know what is worse - that you went to Windows, or you had no idea how the heck to go to windows.

  • Heh (Score:3, Funny)

    by NanoGator ( 522640 ) on Sunday December 05, 2004 @01:04AM (#10999908) Homepage Journal
    "Distributing In-House Engineering Code?"

    I read that as "Disturbing In-House Engineering Code". Any chance we can talk about that, too?
  • Too easy (Score:2, Funny)

    by Frac ( 27516 )
    Wait a second.. you want to know what's the easiest and most efficient way to distribute code on Windows workstations?

    Spyware, worms, and IE exploits. DUH!!
  • by bergeron76 ( 176351 ) * on Sunday December 05, 2004 @01:13AM (#10999941) Homepage
    I think that Windows ships with the QBasic scripting / operating system language.

    From what I hear, it's quite capable for simple "shell scripting" style tasks in Windows like:

    "command.com /e command.com > com1"
    and
    "echo ^G"

    Have fun!

  • cygwin (Score:5, Informative)

    by blackcoot ( 124938 ) on Sunday December 05, 2004 @01:17AM (#10999957)
    step 1: move all that stuff into cvs / source control system of your choice.

    step 2: install cygwin on all the machines (http://sources.redhat.com/ [redhat.com])

    alternately: use ms's unix system services (go digging on the m$ website) theoretically this will give you a "real unix" running inside windows.

    at least this way you don't have to spend as much effort porting your old tools.
    • Seriously. Source code control systems are good for any kind of in-house content distribution. Check in your .mp3 collection, a live binaries, a working install of everything... Cygwin...
    • Re:cygwin (Score:5, Informative)

      by foote ( 441858 ) on Sunday December 05, 2004 @01:11PM (#11001719)

      Simon Peyton Jones, a Microsoft researcher in England who does a lot of work on Haskell (for Microsoft?), has a cheat sheet that "summarises all the things I do to make my Win2k machine more useful to me."

      www.research.microsoft.com/~simonpj/win32-cheat.ht ml [microsoft.com]

      It's rather funny, as much of what he does is make the system more like Unix, with tools like:

      • Emacs, ispell for Emacs, Emacs tags tables
      • Latex
      • A good Telnet client
      • Cygwin
      • Services for Unix
      • CVS
      • GHC (Glasgow Haskell Compiler)

      He describes how to set things up so he can:

      • Export Postscript from a Word, Excel, or Powerpoint document
      • Include LaTeX equations in Powerpoint slides
      • Draw a Powerpoint/Visio picture and include it in a LaTeX document
      • Convert between Word and LaTeX
      • Include typeset material from Postscript into a Powerpoint slide
      • Include mathematical symbols in Word documents

      And more. Useful stuff in general for when you're forced to work on Win machines.

    • You forgot steps 3 and 4...

      Step 3: ???
      Step 4: Profit!
    • Why in good grief's name would one move to a Windows desktop and run UNIX emulators, instead of using the Real Thing(TM) in the first place? The answer "to be able to run Word 2003" is not correct, sorry... (see Open Office, AbiWord, StarOffice, etc).
  • Huh? (Score:2, Funny)

    by Anonymous Coward
    They switched from Solaris to Windows? You don't work for this company [sadomasicism.com] do you?
  • by eyepeepackets ( 33477 ) on Sunday December 05, 2004 @01:53AM (#11000067)
    "My company has recently moved from Solaris workstations to Windows workstations..."

    Didn't check it first to see if critical work could be done?

    Okay, here's what you do:

    1. Send the person who made this decision to Singapore to be caned;
    2. Send his boss to Singapore to be caned and send the boss' dog for caning too as the dog may be the true decision-maker here;
    3. Get yourselves someone who has more than a two digit I.Q. to be your boss;
    4. Profit!

    Ciao.

    • And learn to spell canned properly. :)
      • i'm pretty sure he means caned. there was a pretty famous case a couple years back where an american kid (micheal something or other) littered and was sentenced to a caning. huge american indignation followed
      • New York, Tribune, 23 May 1856

        By the news from Washington it will be seen that Senator Sumner has been savagely and brutally assaulted, while sitting in his seat in the Senate chamber, by the Hon. Mr. Brooks of South Carolina, the reason assigned therefore being that the Senator's remarks on Mr. Butler of South Carolina, who is uncle to the man who made the attack. The particulars show that Mr. Sumner was struck unawares over the head by a loaded cane and stunned, and then the ruffianly attack was continu


    • Didn't check it first to see if critical work could be done?

      Those responsible have been sacked!

    • You just figured out the critical second-to-last step!
  • ...anything about code:

    As an engineering focused company, we use our computers to run many in-house (command line) codes to analyze and design our products. We currently use NAS storage to store everything and use batch files and init scripts to run the correct codes over the network. This makes sure everyone is running the latest version. This also stinks. I know this isn't an original problem, so what are some other solutions for rolling out lots of simple codes like this?"

    ...he/she refers to source code as "codes". At least that's what the rumors on the internets tell me!
    • Refering to programs as "codes" is pretty common in the engineering world: CFD codes, FEA codes, etc.
    • by Anonymous Coward
      Actually, that indicates that it is really an engineering company. Among people whose first interest is science and programming is only a tool to solve scientific problems, it is common to refer to programs and libraries that solve specific problems as "codes". It is also a good bet that if it's called "a code", it's written in FORTRAN. And due to their science education, the authors were probably oblivious about principles of good software engineering.
    • ...he/she refers to source code as "codes".

      Old-school FORTRAN types often refer to single-purpose batch programs, like FEA jobs, as "codes". If you look in engineering magazines, HPC vendors often promise to run your "codes" faster than ever, etc.
    • I've seen the words 'codes' used quite frequently to refer to multipel variants of a given algorithm. This is especially the case with FEA analysis where there might there might be different versions of an algorithm depending on what type(s) of symmentry are exploited to simplify the problem and whether or not the analysis requires the use of complex numbers.
    • Sorry to burst your bubble, but referring to engineering programs as "codes" dates back at least to Fortran 66. It's still pretty common in the HPC world, and pretty much anywhere the focus is on getting engineering tasks done, and not on programming.
  • I'll assume speed or CIFS creates the pain..

    If you really need the speed, you can push out the code to the client machines and put a system in place to audit the distribution. It can end up being a bitch to maintain depending on how you dist and audit. You can write a script with rsync/robocopy and log errors and fix them or buy a commercial software package and check errors and fix them.

    You spend the money to go to Copper Gbit and get some more speed, and keep the code centralized over CIFS. If you o
    • I diagree that CIFS is the problem. More likely rsync over cifs is encountering an iSCSI bug that is reducing NAS performance because the LUN queues on the ATA logical array.

      If he has the money, Copper Gbit with journaling RAID and FC drivers from VRTS and you're LUNS will hum.

      YMMV, and you may LOL, but I still thing detached NAS is the best solution.
  • by chris_mahan ( 256577 ) <chris.mahan@gmail.com> on Sunday December 05, 2004 @02:43AM (#11000191) Homepage
    Make python executable (with py2exe) on shared drive, linked from win desktops as shortcut and launch on startup.

    said script has dedicated local directory like: c:\ourscripts\
    and synchs everything from the network at launch. Script remains running and checks via xml-rpc for updates and will throughout the day get updates to particular files. If you do the xml-rpc check every minute, you'll have near-realtime distribution of cli scripts to windows clients.

    I am assuming you have less than 1k people to do that with in your org. One server could easily handle it.

    by the way, redhat autoupdate uses xml-rpc.

    This has the advantage not to need any local machine deployments of software packages.

    Let me know privately if you need this sort of solution built. Or ask the python mailing list.
  • by imsmith ( 239784 ) on Sunday December 05, 2004 @02:46AM (#11000199)
    just put all your scripts and whatnot into cvs, then write a nice little webservice interface to your cvs server and have your windows admin write a group policy to reference the URI of the script as a desktop icon via the Windows .NET framework and Active Desktop. The current/stable version is always called when the icon is executed and the user gets all the in-house widgets they need as part of the login process. All you have to do is manage your Active Directory and group membership.
  • by mnmn ( 145599 ) on Sunday December 05, 2004 @04:02AM (#11000371) Homepage
    Ok so the Solaris 'code' is on a NAS server, and it is run remotely. You also mentioned you recently moved to Win32.

    Hmmm. It couldnt have been more unclear. Solaris most frequently runs on sparc architectures. Surely the code must be sitting one place, executing on another machine, and somehow the windows machines grab hold of the results...

    So depending on your REAL situation:

    (1) Run apache on the solaris box and display results.

    (2) Run the code on a terminal server machine (Windows2000 terminal services or X11)

    (3) Use rsync or the windows equivalent to redistribute code to all machines

    (4) Use CVS

    (5) Recompile the code for win32.

    To get any more useful advice from slashdot, specify your problem better.
  • Well.... (Score:2, Interesting)

    by FooAtWFU ( 699187 )
    Remember: A "Windows" workstation just means "we haven't reformatted and installed something better yet". Why not reformat/reinstall yourself a Linux, BSD or even (!) Solaris [sun.com] (x86) distribution? Heck, you could probably put together a CD which would automagically setup and install that sort of thing, and then you can go back and do exactly the same method you used before.

    Why did you switch to Windows workstations? Is it the Windows operating system itself, or is the hardware just cheaper? Surely it's not

  • My company has recently moved from Solaris workstations to Windows workstations

    One giant step backwards. You will find your admin costs are going to be higher with Windows. Life is no longer going to be as simple as "install_cluster" or "pkgadd".

    To address some of your problems consider Linux/VMWare underneath Windows. This does a couple of things. You can then backup and recover windows in a short period of time. Especially important to recover windows as it becomes as simple as copying in the old f

  • CVS or Subversion [tigris.org] for source control. Either the CLI versions of these if you prefer or Tortise SVN [tigris.org] or Tortise CVS [tortoisecvs.org] for a good UI for these apps.

    WSH (a brand new Windows shell, sort-of available now) may be an option, but you can just as well download Cygwin as someone mentioned and just use the tools you're familiar with.

    --(())

  • Or, I guess your Windows equivalent, which is an shared volume automatically mounted by whatever method seems most reasonable.

    Sorry, what's the interesting/difficult part of this question, other than you moved an engineering shop from Unix to Windows and are thus having issues?

It is easier to write an incorrect program than understand a correct one.

Working...