[
https://issues.apache.org/jira/browse/JCLOUDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762265#comment-13762265
]
Everett Toews commented on JCLOUDS-273:
---------------------------------------
I see the disconnect here. You're referencing the POST for creating a server,
which does indeed specify metadata (Optional). However, what's causing the
exception in jclouds is (your implementation of) the response. The API docs
make no real specification of the responses and don't mention metadata in the
responses (except for the examples).
POST v2/\{tenant_id\}/servers
GET v2/\{tenant_id\}/servers/detail
GET v2/\{tenant_id\}/servers/\{server_id\}
Let me reach out to some of the OpenStack doc people and see if I can get some
clarification.
> JClouds OpenStack Nova v2.0 Server domian doesn't follow OpenStack formal
> documentation
> ---------------------------------------------------------------------------------------
>
> Key: JCLOUDS-273
> URL: https://issues.apache.org/jira/browse/JCLOUDS-273
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Reporter: Maty Grosz
>
> Using class org.jclouds.openstack.nova.v2_0.domain.Server – look at the
> constructor “protected Server(… parameters)”:
> OpenStack formal documentation says that the metadata attribute is optional.
> The constructor above calls to(checkNotNull(metadata, "metadata")) – and
> fails.
> No need to check that in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
