jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-507) Nova instance metadata is not limited to 5 pairs
Date Mon, 24 Mar 2014 15:44:46 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945236#comment-13945236

ASF subversion and git services commented on JCLOUDS-507:

Commit 59c10e18e810a950fe24791fdb877860ac1ed120 in jclouds's branch refs/heads/1.7.x from
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=59c10e1 ]

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

> Nova instance metadata is not limited to 5 pairs
> ------------------------------------------------
>                 Key: JCLOUDS-507
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-507
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.8.0
>            Reporter: Joel Friedly
>            Priority: Minor
>             Fix For: 1.8.0
> The ``CreateServerOptions.metadata`` docs and method both say that only up to 5 key-value
metadata pairs are allowed.  This is a requirement of Rackspace cloud, but not of upstream
> There is a configurable metadata limit, the ``maxServerMeta`` nova absolute limit, but
the default value is 128.  The python nova client just sends requests up to nova though and
the server enforces the limit.

This message was sent by Atlassian JIRA

View raw message