by Eric Knorr, InfoWorld.comSo many vendors have jumped on the cloud computing bandwagon, the phrase already risks jumping the shark. The problem is that “cloud computing” has two distinctly different meanings: The use of commercial Internet-based services, and the architecture for building and deploying such services.InfoWorld has adopted the former definition. Last April we boiled [...]
Hi,
I am working as Linux system administrator now I want to learn cloud computing too. I tried Googling but couldn't find appropriate information so thought to ask people here.
Can somebody suggest me correct path along with tutorials/PDF/HTMLs?
Really appreciate your help.
thx
Pras (1 Reply)
I work for a British based company.
We are looking for a cloud computing provider enabling us to use
HP on Itanium and HP hardware.
anyone know of any?
cheers. (0 Replies)
Tim Bass
Thu, 15 Nov 2007 23:55:07 +0000
*I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
GLANCE-CACHE-CLEANER(1) Glance GLANCE-CACHE-CLEANER(1)NAME
glance-cache-cleaner - Glance Cache Cleaner
GLANCE IMAGE CACHE INVALID CACHE ENTRY AND STALLED IMAGE CLEANER
Author glance@lists.launchpad.net
Date 2012-01-03
Copyright
OpenStack LLC
Version
2012.1-dev
Manual section
1
Manual group
cloud computing
SYNOPSIS
glance-cache-cleaner [options]
DESCRIPTION
This is meant to be run as a periodic task from cron.
If something goes wrong while we're caching an image (for example the fetch times out, or an exception is raised), we create an 'invalid'
entry. These entires are left around for debugging purposes. However, after some period of time, we want to clean these up.
Also, if an incomplete image hangs around past the image_cache_stall_time period, we automatically sweep it up.
OPTIONS
--version
show program's version number and exit
-h, --help
show this help message and exit
--config-file=PATH
Path to a config file to use. Multiple config files can be specified, with values in later files taking precedence. The default
files used are: []
-d, --debug
Print debugging output
--nodebug
Do not print debugging output
-v, --verbose
Print more verbose output
--noverbose
Do not print verbose output
--log-config=PATH
If this option is specified, the logging configuration file specified is used and overrides any other logging options specified.
Please see the Python logging module documentation for details on logging configuration files.
--log-format=FORMAT
A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes. Default: none
--log-date-format=DATE_FORMAT
Format string for %(asctime)s in log records. Default: none
--log-file=PATH
(Optional) Name of log file to output to. If not set, logging will go to stdout.
--log-dir=LOG_DIR
(Optional) The directory to keep log files in (will be prepended to --logfile)
--use-syslog
Use syslog for logging.
--nouse-syslog
Do not use syslog for logging.
--syslog-log-facility=SYSLOG_LOG_FACILITY
syslog facility to receive log lines
SEE ALSO
o OpenStack Glance
BUGS
o Glance is sourced in Launchpad so you can view current bugs at OpenStack Glance
AUTHOR
OpenStack
COPYRIGHT
2010-present, OpenStack, LLC.
2012.1.1 March 14, 2013 GLANCE-CACHE-CLEANER(1)