We also exit earlier, we don't display that we are even trying to start.
When we detect the agent is already running we exit right away with a message.
Although this master branch doesn't contain 3.0.2 since we moved passed that
it didn't feel apprioriate to bump the version to 4.0.0 (yet).
This file should be updated to 4.0.0 at the point where we release 4.0
No need for these packages to depend on any cloud-agent package.
If they need files from this packages, then we need to move those files.
The client/management server should never depend on agent packages.
With LSB there is no need for having different init script for different distributions.
This init script should be fully LSB compliant and should work on all Linux platforms we support.
RHEL, (Open)SUSE, Debian and Ubuntu all support at least LSB 3.1
This was reverted, as another commit fixed the issue already:
commit 2b2e491f27
Author: bfederle <bfederle@gmail.com>
Date: Tue Jul 17 11:38:56 2012 -0700
CS-15572: Fix page index for list view filters
This reverts commit 374be31b63.
Although these bindings have to be removed for the first Apache release
we place the upstream JAR here.
The 0.4.5 bindings were homebrew and contained own code which wasn't sent upstream.
These changes were sent upstream and got into 0.4.8.
For now we keep the 0.4.8 bindings in the repo until we have a new build system in place
which handles this.
This is still however a release blocker since we can't distribute these bindings from the Apache servers!
The negative cases for which the error handling is improved,
1. run ec2-register with incorrect field separator for architecture parameter.
2. run ec2-register without providing required parameters.
Tags support has been added to 3 EC2Describe* API's(DescribeInstances, DescribeVolumes and DescribeSnapshots). Hence for the same 3 EC2Describe* API's filter support has been modified to included 3 tag related filters: tag-key,
tag-value and tag:key.
Adds a helper to return an object to pass to the 'tagger' widget,
including all required data and action functions.
Syntax is as follows, just include anywhere were the tags widget is
supported:
tags: cloudStack.api.tags({
resourceType: 'Project',
contextId: 'projects'
})