Andrew Bayer created JCLOUDS-1018:
-
Summary: Add support for EC2 spot fleets
Key: JCLOUDS-1018
URL: https://issues.apache.org/jira/browse/JCLOUDS-1018
Project: jclouds
Issue Type
Andrew Bayer created JCLOUDS-1019:
-
Summary: Add support for EC2 spot instance defined duration
Key: JCLOUDS-1019
URL: https://issues.apache.org/jira/browse/JCLOUDS-1019
Project: jclouds
+1, cherry picking it around myself now.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/816#issuecomment-125901695
Closed #816.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/816#event-368164389
Andrew Bayer created JCLOUDS-972:
Summary: Failed EC2 spot instance requests through compute service
never return correctly
Key: JCLOUDS-972
URL: https://issues.apache.org/jira/browse/JCLOUDS-972
Get the faultCode and faultMessage to actually be parsed (though I'm
not sure they're ever used), add statusCode, statusMessage and
statusUpdateTime, and have AWSEC2TemplateOptions default to a sane 30
minute lifetime for spot instance requests, so they don't get orphaned
forever if the price is
Get the faultCode and faultMessage to actually be parsed (though I'm
not sure they're ever used), add statusCode, statusMessage and
statusUpdateTime, and have AWSEC2TemplateOptions default to a sane 30
minute lifetime for spot instance requests, so they don't get orphaned
forever if the price is
[
https://issues.apache.org/jira/browse/JCLOUDS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-972.
--
Resolution: Fixed
Pushed to 1.9.x and master.
Failed EC2 spot instance requests through
[
https://issues.apache.org/jira/browse/JCLOUDS-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer updated JCLOUDS-939:
-
Fix Version/s: (was: 1.9.1)
Removed 1.9.1 from the fix version - I'll need to read through
Andrew Bayer created JCLOUDS-960:
Summary: testDescribeSpotPriceHistoryInRegion shouldn't have a
hardcoded list of instance types to check against
Key: JCLOUDS-960
URL: https://issues.apache.org/jira/browse
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/807
-- Commit Summary --
* JCLOUDS-961 - Add d2, m4, t2 instance types for EC2
-- File Changes --
M
apis/ec2/src/main/java/org/jclouds/ec2/compute/domain/EC2HardwareBuilder.java
Andrew Bayer created JCLOUDS-961:
Summary: Add d2, m4, t2 instance types for EC2
Key: JCLOUDS-961
URL: https://issues.apache.org/jira/browse/JCLOUDS-961
Project: jclouds
Issue Type
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/808
-- Commit Summary --
* JCLOUDS-961 - Add d2, m4, t2 instance types for EC2
-- File Changes --
M
apis/ec2/src/main/java/org/jclouds/ec2/compute/domain/EC2HardwareBuilder.java
[
https://issues.apache.org/jira/browse/JCLOUDS-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-961.
--
Resolution: Fixed
Pushed to master and 1.9.x.
Add d2, m4, t2 instance types for EC2
[
https://issues.apache.org/jira/browse/JCLOUDS-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-936.
--
Resolution: Fixed
Move to a LoadingCache for GCE disk-image mapping
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-google/pull/157
-- Commit Summary --
* JCLOUDS-936: Switch to LoadingCache for disk-image
-- File Changes --
M
Backporting from master.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-google/pull/158
-- Commit Summary --
* JCLOUDS-934. Add support for specifying boot disk type in compute service
-- File Changes --
M
Done.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/157#issuecomment-113092023
Closed #155.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/155#event-333995484
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/155#issuecomment-113081137
[
https://issues.apache.org/jira/browse/JCLOUDS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-935.
--
Resolution: Fixed
Committed to master and 1.9.x.
Specify disk type
[
https://issues.apache.org/jira/browse/JCLOUDS-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-934.
--
Resolution: Fixed
Committed to master and 1.9.x.
Add support for specifying GCE disk type
Andrew Bayer created JCLOUDS-939:
Summary: Add support for additional disks on ComputeService
instance in GCE
Key: JCLOUDS-939
URL: https://issues.apache.org/jira/browse/JCLOUDS-939
Project: jclouds
Pushed the two changes to the live test - waiting for your thoughts on the disk
type constant.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/154#issuecomment-112232762
[
https://issues.apache.org/jira/browse/JCLOUDS-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587147#comment-14587147
]
Andrew Bayer commented on JCLOUDS-939:
--
...this is not as trivial as I'd hoped
@@ -67,6 +74,34 @@ public void testListHardwareProfiles() throws Exception {
}
}
+ public void testCreateNodeWithSsd() throws Exception {
+ String group = this.group + ssd;
+ try {
+ TemplateOptions options = client.templateOptions();
+
+
+
options.as(GoogleComputeEngineTemplateOptions.class).bootDiskType(pd-ssd);
+
+ // create a node
+ Set? extends NodeMetadata nodes =
+ client.createNodesInGroup(group, 1, options);
+ assertEquals(nodes.size(), 1, One node should have been
@@ -67,6 +74,34 @@ public void testListHardwareProfiles() throws Exception {
}
}
+ public void testCreateNodeWithSsd() throws Exception {
+ String group = this.group + ssd;
+ try {
+ TemplateOptions options = client.templateOptions();
+
+
Well that was dumb. I forgot what repo I was in and merged it. Oops. Will push
by hand.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/153#issuecomment-111539592
Backporting to 1.9.x.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-google/pull/155
-- Commit Summary --
* JCLOUDS-935. Move AttachDisk.InitializeParams to URI for diskType
-- File Changes --
M
The failing tests - https://gist.github.com/abayer/72554e8861873b3f4750 -
sometimes they seem to pass, sometimes they don't, and I can't figure out why.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/153#issuecomment-111539176
Merged #153.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/153#event-329711798
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-google/pull/154
-- Commit Summary --
* JCLOUDS-934. Add support for specifying boot disk type in compute service
-- File Changes --
M
Andrew Bayer created JCLOUDS-935:
Summary: Specify disk type in AttachDisk.InitializeParams as a URL
Key: JCLOUDS-935
URL: https://issues.apache.org/jira/browse/JCLOUDS-935
Project: jclouds
Note that two tests are failing right now with or without this.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-google/pull/153
-- Commit Summary --
* JCLOUDS-935. Move AttachDisk.InitializeParams to URI for diskType
-- File Changes
Andrew Bayer created JCLOUDS-934:
Summary: Add support for specifying GCE disk type in compute
abstraction
Key: JCLOUDS-934
URL: https://issues.apache.org/jira/browse/JCLOUDS-934
Project: jclouds
Yeah, those ghost failures hit me too - not sure where they came from. But hey.
Lemme know when this gets to 1.9.x so I can pull it into our internal app. =)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#issuecomment-110168828
yy - passes with that changed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#issuecomment-109359455
Ok, https://cloud.google.com/compute/docs/instances/#stop_job seems to explain
it - TERMINATED is actually stopped here.
Closed #147.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/147#event-323723559
Closing since I hit the same live test failure.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/147#issuecomment-109349101
Not sure why these were still unimplemented, since stop/start has been
in GCE for ages. Probably my bad. =) Anyway, unit tests pass, live
tests...run? Took a bunch of work to get them to actually launch,
which was odd.
You can view, comment on, or merge this pull request online at:
Andrew Bayer created JCLOUDS-925:
Summary: GCE ComputeServiceAdapter should support suspendNode and
resumeNode
Key: JCLOUDS-925
URL: https://issues.apache.org/jira/browse/JCLOUDS-925
Project: jclouds
+1 once it passes!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/593#issuecomment-61001947
+1 - see my comment on https://github.com/jclouds/jclouds-labs/pull/97
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/63#issuecomment-60411824
+1 - we really need to be able to backport trivially from master to 1.8.x given
the Java 7 thing, so this is an absolute requirement in my mind, even beyond my
general conservatism on library dependency versions.
---
Reply to this email directly or view it on GitHub:
+1 - see my comment on https://github.com/jclouds/jclouds-labs/pull/97
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/583#issuecomment-60411873
+1 - see my comment on https://github.com/jclouds/jclouds-labs/pull/97
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/164#issuecomment-60411854
[
https://issues.apache.org/jira/browse/JCLOUDS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183264#comment-14183264
]
Andrew Bayer commented on JCLOUDS-664:
--
I'll try to take a look at #1.
Azure
[
https://issues.apache.org/jira/browse/JCLOUDS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-756.
--
Resolution: Fixed
Fix Version/s: 1.8.2
Cherry-picked to 1.8.x as well.
Add support
[
https://issues.apache.org/jira/browse/JCLOUDS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183596#comment-14183596
]
Andrew Bayer commented on JCLOUDS-664:
--
Oh, you meant it had *none* of the compute
[
https://issues.apache.org/jira/browse/JCLOUDS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183761#comment-14183761
]
Andrew Bayer commented on JCLOUDS-664:
--
Sure thing. I just spent a couple hours
+networktype: Advanced,
+securitygroupsenabled: false,
+tags: []
+},
+{
+id: 2,
+name: Chicago,
+networktype: Advanced,
+securitygroupsenabled: true,
+tags: [
+
@@ -11,7 +11,8 @@
ipaddress: 10.27.27.64,
startport: 22,
endport: 22,
-state: Active
+state: Active,
+
tags:[{account:1,domain:ROOT,domainid:1,key:some-tag,resourceid:66,
resourcetype:PortForwardingRule,
@@ -166,6 +183,13 @@ public static ListSnapshotsOptions volumeId(String
volumeId) {
public static ListSnapshotsOptions projectId(String projectId) {
return new ListSnapshotsOptions().projectId(projectId);
}
+
+ /**
+ * @see
+public interface TagApi {
+
+ /**
+* Lists tags
+*
+* @param options
+* if present, how to constrain the list.
+* @return tags matching query, or empty set, if no tags are found
+*/
+ @Named(listTags)
+ @GET
+ @QueryParams(keys = { command,
+
+ public static ResourceType fromValue(String resourceType) {
+ Integer code = Integer.valueOf(checkNotNull(resourceType,
resourcetype));
+ return INDEX.containsKey(code) ? INDEX.get(code) : UNRECOGNIZED;
+ }
+ }
+
+ public static Builder? builder() {
+
+import com.google.common.base.MoreObjects;
+import com.google.common.base.MoreObjects.ToStringHelper;
+import com.google.common.base.Objects;
+import com.google.common.collect.ImmutableSet;
+import com.google.common.collect.Maps;
+import org.jclouds.javax.annotation.Nullable;
+
+/**
+ *
The tags aren't really confusing - they're just overly verbose, as it were. And
yeah, as a copy-paste-coder, I always just use the style in place in the
existing code in the API rather than diverging - maybe not ideal, but makes it
much easier to read and maintain, IMO.
---
Reply to this email
Ah, but it is easier to maintain an API when the entire API is doing the same
thing, even if that thing is a bit wonky. =)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/578#issuecomment-59957942
..that too, yes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/578#issuecomment-59962160
+
+ public static ResourceType fromValue(String resourceType) {
+ Integer code = Integer.valueOf(checkNotNull(resourceType,
resourcetype));
+ return INDEX.containsKey(code) ? INDEX.get(code) : UNRECOGNIZED;
+ }
+ }
+
+ public static Builder? builder() {
+
Ok, live tests added and they pass - I think that suffices. Squashing now.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/578#issuecomment-6354
Ok, added the tags/userMetadata to NodeMetadata, ComputeService-driven node
creation, etc. I'm calling this done with another PR to come later on general
live test cleanup/fixes.
---
Reply to this email directly or view it on GitHub:
Andrew Bayer created JCLOUDS-756:
Summary: Add support for tags to CloudStack
Key: JCLOUDS-756
URL: https://issues.apache.org/jira/browse/JCLOUDS-756
Project: jclouds
Issue Type: Improvement
Note - this is just a preliminary PR, not ready for merge yet. I still have to
add a couple more expect tests, update a couple more, add live tests and update
one or two other live tests, but I wanted to throw this up so others could see
it.
Note also that yeah, I went a little nutty and
+1 lgtm
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/60#issuecomment-58094608
Andrew Bayer created JCLOUDS-664:
Summary: Azure compute support
Key: JCLOUDS-664
URL: https://issues.apache.org/jira/browse/JCLOUDS-664
Project: jclouds
Issue Type: New Feature
You can merge this Pull Request by running:
git pull https://github.com/abayer/jclouds-1 jclouds-602-for-1.7.x
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/416
-- Commit Summary --
* JCLOUDS-602 - Add support for volumeType, iops and
Transient noise on that failure, I'm pretty sure.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/416#issuecomment-46722397
[
https://issues.apache.org/jira/browse/JCLOUDS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-602.
--
Resolution: Fixed
Committed to master and 1.7.x
Add support for Iops, Encrypted
@@ -159,11 +159,18 @@ public static ImageType fromValue(String v) {
private final String snapshotId;
private final long volumeSize;
private final boolean deleteOnTermination;
+ private final String volumeType;
+ private final Integer iops;
+ private final
Review comments addressed - it's still a little wishy-washy on
primitive/non-primitive for encrypted, because there are a few places where it
frankly makes sense to go with nullable Booleans, but it's much more consistent
now.
---
Reply to this email directly or view it on GitHub:
Live tests are added and passing.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/408#issuecomment-46617134
Oops, one test was a bit flaky. Fixed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/408#issuecomment-46618857
Whoops again - ran the full battery of live tests, found another problem - we
do need the truthy dance for now, unless we switch BlockDeviceMapping to
primitives for encrypted, and I'm not going to do that unless I know why
deleteOnTermination's a non-primitive there.
---
Reply to this email
Add CreateVolumeOptions, modified everything that I could find that cares about
parsing or creating volumes (and EBS-backed images, since that's connected) to
support the new fields as well. Live tests and unit tests should be updated.
---
Reply to this email directly or view it on GitHub:
The jclouds-pull-requests build 906 failure looks spurious - will wait and see
if the others barf too.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/408#issuecomment-46509445
- public EbsBlockDevice(@Nullable String snapshotId, long volumeSize,
boolean deleteOnTermination) {
+ public EbsBlockDevice(@Nullable String snapshotId, long volumeSize,
boolean deleteOnTermination,
For new classes, oh yeah, lots of wonderful new things without even going
- .id(vol-2a21e543)
- .status(Volume.Status.CREATING)
- .availabilityZone(us-east-1a)
- .region(us-east-1)
- .id(vol-2a21e543)
-
@@ -160,6 +163,24 @@ void testCreateVolumeFromSnapshotInAvailabilityZone() {
}
@Test(dependsOnMethods = testCreateSnapshotInRegion)
+ void testCreateVolumeFromSnapshotInAvailabilityZoneWithOptions() {
+ Volume volume = client.createVolumeInAvailabilityZone(defaultZone,
+
Andrew Bayer created JCLOUDS-602:
Summary: Add support for Iops, Encrypted and VolumeType fields for
EC2 BlockDeviceMapping
Key: JCLOUDS-602
URL: https://issues.apache.org/jira/browse/JCLOUDS-602
Note - still missing adding these to the createVolume* methods, but
that#39;s going to involve a non-trivial change to something like
CreateVolumeOptions.class rather than the current simple arguments.
You can merge this Pull Request by running:
git pull https://github.com/abayer/jclouds-1
Andrew Bayer created JCLOUDS-600:
Summary: runScriptOnNode's sftp put can hang
Key: JCLOUDS-600
URL: https://issues.apache.org/jira/browse/JCLOUDS-600
Project: jclouds
Issue Type: Bug
Andrew Bayer created JCLOUDS-601:
Summary: Allow RunScriptOptions to specify timeout to override
global timeout
Key: JCLOUDS-601
URL: https://issues.apache.org/jira/browse/JCLOUDS-601
Project
Closed #24.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/24#event-128980382
Reopened #24.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/24#event-128980387
Ignore me reopening this and the new build comment - I'm verifying PR building
at https://builds.apache.org. =)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/24#issuecomment-45386127
Reopened #24.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/24#event-128982654
[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010043#comment-14010043
]
Andrew Bayer commented on JCLOUDS-576:
--
So I'm fiddling around with ways of dealing
[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010043#comment-14010043
]
Andrew Bayer edited comment on JCLOUDS-576 at 5/27/14 6:36 PM
[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010085#comment-14010085
]
Andrew Bayer commented on JCLOUDS-576:
--
Still got a few issues with labs, labs-aws
[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010091#comment-14010091
]
Andrew Bayer commented on JCLOUDS-576:
--
Ah, and we'll need to work in the property
[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010043#comment-14010043
]
Andrew Bayer edited comment on JCLOUDS-576 at 5/27/14 6:51 PM
[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010091#comment-14010091
]
Andrew Bayer edited comment on JCLOUDS-576 at 5/27/14 6:55 PM
[
https://issues.apache.org/jira/browse/JCLOUDS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-450.
--
Resolution: Fixed
Support min/max count and client token fields for AWS EC2 RunInstances
You can merge this Pull Request by running:
git pull https://github.com/abayer/jclouds-1 fix-disks-on-m3s
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/363
-- Commit Summary --
* JCLOUDS-564. Add ephemeral disks for m3.xlarge and
Yeah, I was trying to think of a test to add, but really, all the tests could
do would be to say Yup, we say what we said we say. Not particularly useful.
=)
I have tested it against EC2 with both instance sizes, and my tooling worked
fine, so yes, it looks good. I'll backport this to the
Andrew Bayer created JCLOUDS-564:
Summary: m3.xlarge and m3.2xlarge sizes don't include ephemeral
disks
Key: JCLOUDS-564
URL: https://issues.apache.org/jira/browse/JCLOUDS-564
Project: jclouds
[
https://issues.apache.org/jira/browse/JCLOUDS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer resolved JCLOUDS-564.
--
Resolution: Fixed
Pushed to master and 1.7.x.
m3.xlarge and m3.2xlarge sizes don't include
1 - 100 of 160 matches
Mail list logo
