Ahmed Kamal: Advanced cloud-init custom handlers


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Ahmed Kamal: Advanced cloud-init custom handlers
# 1  
Old 01-03-2011
Ahmed Kamal: Advanced cloud-init custom handlers

I love cloud-init, the Ubuntu cloud technology that enables a cloud instance to bootstrap itself and customize itself into whatever you want it to be (coming from a generic image). I had previously created a screencast introducing cloud-init, and written an article on running cloud-init locally over KVM.

read more



More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Programming

How is it work the event handlers!?

I just have started studying perl and I can not figure out what is the exact strategy used in the following script to handle events. Precisely, what I do not understand is if the loop that is in charge to control the state of the socket, is managed at the system level (where the process will be... (2 Replies)
Discussion started by: flaviofachin
2 Replies

2. Shell Programming and Scripting

Considered basic but advanced outcome (Custom Backup Solution)

Ive a problem that I'm reaching out for help. Ive written (With bits and pieces) of script that is not running as expected or is having an issue causing processes to spiral out of control. The script does this: Unloads a UV database server Tars up a few folders Transfers the file to... (11 Replies)
Discussion started by: coastdweller
11 Replies

3. Red Hat

init-script failing because of /etc/rc.d/init.d/functions

I encountered a problem on one of our database servers. OS: CentOS 5.5 final Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel) We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies

4. Programming

Signal Handlers using sigwait

After an extensive search, I haven't found a definitive answer to my question. "And what is your question you frackking noob", you may ask. Ok, here goes: When using sigwait to wait for SIGUSR1 or SIGUSR2, can you have it trigger a signal handler? The following code did NOT, and the example I got... (2 Replies)
Discussion started by: bcfd36
2 Replies

5. Debian

Iomega ix2-200 Custom Debian - Autostart script in init.d not Working

!!Hello Everyone!! I Recently purchased a Iomega iX2-200 NAS that runs a custom debian installed by Iomega (Linux Debian 5.0.2 ( 2.6.22.18 armv5tejl)) . I have SSH access. I installed Transmission since the factory installed torrents manager that Iomega uses is terrible. Transmission-daemon... (1 Reply)
Discussion started by: stejimenez
1 Replies

6. Linux

How to I change init levels after typing init 1

Dear all, I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel): 1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies
Login or Register to Ask a Question
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)