You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Joel Friedly (JIRA)" <ji...@apache.org> on 2014/03/24 18:04:45 UTC

[jira] [Resolved] (JCLOUDS-507) Nova instance metadata is not limited to 5 pairs

     [ https://issues.apache.org/jira/browse/JCLOUDS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Friedly resolved JCLOUDS-507.
----------------------------------

    Resolution: Fixed

> 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.7.0, 1.8.0, 1.7.1, 1.7.2
>            Reporter: Joel Friedly
>            Priority: Minor
>             Fix For: 1.8.0, 1.7.2
>
>
> 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 OpenStack.
> 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
(v6.2#6252)