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!
According to ipsec.conf manual:
pfs
whether Perfect Forward Secrecy of keys is desired on the connection's keying
channel (with PFS, penetration of the key-exchange protocol does not compromise
keys negotiated earlier); Since there is no reason to ever refuse PFS, Openswan
will allow a connection defined with pfs=no to use PFS anyway. Acceptable values
are yes (the default) and no.
Found removing the option would make it impossible to work with no PFS setting
router. It may related to CS-15511.
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'
})
[Dropped Vmware support in this commit, due to lack of VMware support in VPC now]
Conflicts:
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
Issue happens when ROOT volume gets created and there is subsequent failure in starting the VM. During retry if allocator assigns a different storage pool the scenario was not handled. Now in case of local storage the volume get recreated on the newly assigned pool and old one gets cleaned up. In case of shared storage the existing volume is migrated to new storage pool.
Brian Federle
bfederle
David Nalley
Pranav Saxena
Edison Su
Wido den Hollander
Hugo Trippaers
Alena Prokharchyk
Sheng Yang
Likitha Shetty
prachi
Koushik Das