libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Wilson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LIBCLOUD-548) Linode API - linode.update label limited to 32 chars
Date Thu, 01 May 2014 21:08:14 GMT
Gary Wilson created LIBCLOUD-548:
------------------------------------

             Summary: Linode API - linode.update label limited to 32 chars
                 Key: LIBCLOUD-548
                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-548
             Project: Libcloud
          Issue Type: Bug
          Components: Compute
    Affects Versions: 0.14.0-beta3
            Reporter: Gary Wilson


Somewhat related to https://issues.apache.org/jira/browse/LIBCLOUD-547

All cloud not being created equal and all.

In terms of automation and abstraction it is pretty standard to create the hostnames based
on variables that are based on roles, location, etc, etc.

In relation to the linode.update label API call e.g. the name object normally the hostname
- https://www.linode.com/api/linode/linode.update - (Label - string (optional) This Linode's
label) 

This is limited to 32 chars - not documented in the API docs (no linode API string constraints
are documented as far as I have seen).  This in not RFC 1034 compliant in terms of the 63
chars allowed for hostnames, although Linode do not relate this object to hostname, in terms
of abstraction, it arguably is (seeing as AWS, Rackspace and Digitalocean do not seem to have
this 32 char name object limit).

So this is not a libcloud bug per se, but it is more a thing to note or add to libcloud documentation.
 Linode have been advised of this issue and hopefully it will be fixed on the Linode API side
and this will not be an issue that many bump into using libcloud.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message