Just a quick heads up - I'm currently working on a proposal for a new base networking API.
You can find some of the existing code which is based on some of the changes we use at DivvyCloud here - https://github.com/apache/libcloud/pull/345 Keep in mind that the whole thing is still very much unfinished and W.I.P and things are subject to change. My goal is to finish it up and submit a proposal and RFC with a reference implementation for OpenStack Nova, OpenStack Quantom, OpenStack Neutron and EC2 networking driver some time next week. On Wed, Jun 25, 2014 at 11:59 AM, Markos Gogoulos <[email protected]> wrote: > > > Hi all, > > I have issues with the HP Cloud driver and network tasks. > The driver sets 2 compute endpoints and derives from > OpenStack_1_1_NodeDriver. For compute related tasks this works, but not > for network related tasks, since a network endpoint has to be called. > > > For example, ex_list_networks is called from openstack.py which > queries self.connection.request(self._networks_url_prefix). This seems > to call the compute endpoint, which is different from the network > endpoint in hp's case, so it fails (the network endpoint is > https://region-b.geo-1.network.hpcloudsvc.com > -https://docs.hpcloud.com/api/v13/networking/) > > So the question is: can > openstack drivers combine network and compute endpoints, if these are > different? > > Thanks and regards >
