From 59c10e18e810a950fe24791fdb877860ac1ed120 Mon Sep 17 00:00:00 2001 From: Joel Friedly Date: Fri, 21 Mar 2014 15:25:04 -0700 Subject: [PATCH] Remove Nova instance metadata limit Rackspace cloud limits instance metadata to 5 key-value pairs, but upstream Nova only sets the limit at 128 by default. This patch removes the limit entirely; the official python clients don't check it and the server is responsible for enforcing it anyway. Fixes: https://issues.apache.org/jira/browse/JCLOUDS-507 --- .../openstack/nova/v2_0/options/CreateServerOptions.java | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/options/CreateServerOptions.java b/apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/options/CreateServerOptions.java index fd19894fe9..05cbd8a870 100644 --- a/apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/options/CreateServerOptions.java +++ b/apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/options/CreateServerOptions.java @@ -295,13 +295,10 @@ public class CreateServerOptions implements MapBinder { * Custom cloud server metadata can also be supplied at launch time. This * metadata is stored in the API system where it is retrievable by querying * the API for server status. The maximum size of the metadata key and value - * is each 255 bytes and the maximum number of key-value pairs that can be - * supplied per server is 5. + * is each 255 bytes. */ public CreateServerOptions metadata(Map metadata) { checkNotNull(metadata, "metadata"); - checkArgument(metadata.size() <= 5, - "you cannot have more then 5 metadata values. You specified: " + metadata.size()); for (Entry entry : metadata.entrySet()) { checkArgument( entry.getKey().getBytes().length < 255,