[
https://issues.apache.org/jira/browse/LIBCLOUD-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grischa Meyer updated LIBCLOUD-297:
-----------------------------------
Attachment: network-label.patch
The patch I used as quick fix. Doesn't fully address the issue though
> OpenStack Network label is arbitrary, libcloud wrongly assumes "public" or
> "private"
> ------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-297
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-297
> Project: Libcloud
> Issue Type: Bug
> Reporter: Grischa Meyer
> Attachments: network-label.patch
>
>
> The openstack.py driver in libcloud assumes that all OpenStack installations
> have only three network labels, "public", "internet" and "private".
> However, the label is actually an arbitrary string according to the OpenStack
> specs, and the cloud I happen to be using has assigned a different string to
> their network. As further reference, I looked at the python-novaclient code
> and it assumes the network label to be any arbitrary string as well.
> I have fixed the issue for my personal use with a dirty hack that assigns any
> non-"public" network to the "private" group. However, the false assumption
> that there are pre-defined public and private networks in OpenStack still
> lives on.
> I hope someone with better familiarity with the OpenStack driver and its
> relation to the rest of libcloud can fix this by removing the notion of
> predefined public and private networks, in line with OpenStack specifications.
> I will attach a patch for my quick-fix (same as
> https://github.com/apache/libcloud/pull/95), but I suggest that this be fixed
> more thoroughly.
--
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
