Introducing Linux into the Enterprise
So now it's time for some of those cool tricks I promised. Would you believe me if I said that you can build a complete Windows 2000 or NT 4.0 server in just a few minutes under GSX? Or, how about multiple servers at the same time in under an hour? Here's how it works. The first build of an operating systems in GSX takes the usual amount of time to complete and configure, but if you need multiple servers with the same base build or similar configuration, you can copy the files created after the initial build to subsequent virtual server directories. Simply create the new servers in the web admin console as before, copy the server files, then change a few lines of information (such as server name and the pointers to the new server's disk files, *.dsk) in a config file (i.e., win2000.cfg). After that, power on the new servers and change their IP address, machine name, etc. It's a good idea to tarball the files, name them appropriately and copy them off to a DLT, CD burner, etc. Now pat yourself on the back because you built multiple identical servers in minutes. At this point you can customize your servers to be SQL, web, e-mail, etc.
In addition, GSX gives you a fast way to build multiple servers and a much quicker way to recover from a serious crash. In the event of an unrecoverable OS failure (you were backing up, weren't you?), rather than having to rebuild the OS and then restore your data, copy the server files from the tarballs that you created. Now restore your data and calmly say to yourself, "life is really, really good".
So there you have it--a high-powered Linux server that can host as many virtual servers as you have the memory and the horsepower for. I encourage you to visit the VMware site and check out the GSX Server product (there is also an ESX Server product that runs directly on top of the hardware--no OS), and give the 30-day demo a spin. For our purposes, Linux combined with VMware's GSX Server have been a real blessing.
Jeffrey McDonald works as a systems engineer for a California-based Fortune 500 company. He has been working with Linux for the past five years and enjoys promoting Linux.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide