True Infrastructure On Demand
Article first published at:
We already have Cloud computing systems available, however when will we be able to shopping list order our computing power or infrastructure - consider two pricing models, shared and dedicated:
With shared pricing, you’ll be able to pay a fee for Kb/RAM/s which is a flat fee for every Kilobyte of RAM used per second, a fee per CPU clock cycle and a fee per Kb of space used. Alternatively you could purchase 2 hours access to 32Gb RAM and 3.2GHz for a flat fee.
Cloud computing is being driven forward by service providers such as Amazon, Google, and Yahoo! however I wonder if there will ever be a need or solution for truly instant on demand infrastructure or resources. GoGrid and Amazon EC2 seem close, however they’re not as straight forward or as powerful as you’d expect, and I’d personally be worried about runaway costs.
Pricing of both services seems good - I’d expect prices to be slightly cheaper than their hosted server equivalent. I can only think of a few uses for this kind of technology, primarily short time distributed computing projects, brute forcing, rainbow table generation, large data processing, etc.
I’d really like to see this kind of technology used in place of regular hosting environments though. Possibly in a scenario where your hardware and resource requirements were persistant but evolving on a regular basis. I’m struggling to think of such a scenario though..
For more Tech Talk, Linux HOWTOs & Discussion, PHP, MySQL, visits
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!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- Interview with Patrick Volkerding
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
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