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
TXAWS-DISCOVER(1)						   User Commands						 TXAWS-DISCOVER(1)

NAME
txaws-discover - txAWS AWS API discovery tool SYNOPSIS
txaws-discover [--key KEY] [--secret SECRET] [--endpoint ENDPOINT] DESCRIPTION
Purpose: Invoke an EC2 API method with arbitrary parameters. --action ACTION [PARAMETERS, ...] OPTIONS
--key The AWS access key to use when making the API request. --secret The AWS secret key to use when making the API request. --endpoint The region endpoint to make the API request against. --action The name of the EC2 API to invoke. -h, --help Show help message. Description: The purpose of this program is to aid discovery of the EC2 API. It can run any EC2 API method, with arbitrary parameters. The response received from the backend cloud is printed to the screen, to show exactly what happened in response to the request. The --key, --secret, --end- point and --action command-line arguments are required. If AWS_ENDPOINT, AWS_ACCESS_KEY_ID or AWS_SECRET_ACCESS_KEY environment variables are defined the corresponding options can be omitted and the values defined in the environment variables will be used. Any additional parameters, beyond those defined above, will be included with the request as method parameters. EXAMPLES
The following examples omit the --key, --secret and --endpoint command-line arguments for brevity. They must be included unless corresponding values are available from the environment. Run the DescribeRegions method, without any optional parameters: txaws-discover --action DescribeRegions Run the DescribeRegions method, with an optional RegionName.0 parameter: txaws-discover --action DescribeRegions --RegionName.0 us-west-1 txaws-discover 0.2.3 May 2012 TXAWS-DISCOVER(1)