Open Stack

Hello Mike,

I am so sorry for the late response.
The UCSM (VM-FEX) plugin does not have fully functional support for Quantum V2. It does indeed include fake drivers in order to let all unit test for Quantum V2 to pass successfully and you can find them in:
quantum/etc/quantum/plugins/cisco/cisco_plugins.ini
quantum/etc/quantum/plugins/cisco/ucs.ini

OpenStack at Cisco team is evaluating whether we will provide fully functional support for UCSM in Grizzly or not.
This decision will be taken between the next week or so because we should be sending out the corresponding BP for Grizzly-3.

So, you should not have any issues testing V2 REST APIs, I just downloaded the code, modify the corresponding config files as per documentation and ran all unit tests successfully.

I don’t see the import issue that you are experiencing, I wanted to reproduce it to file a bug but just couldn't find it.
Please, let me know if you need to work offline in your set up.

Thanks,
Edgar

From: Mike Kolesnik <mkolesni at redhat.com<mailto:mkolesni at redhat.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, November 6, 2012 2:14 AM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [Quantum] Questions about v2.0 + UCSM Plugin

Hi All,

I've downloaded the latest version (2012.2) from launchpad and tried to use it to integrate with UCSM.

I've hit a few bumps on the road, and was wondering:

1. Is there going to be a FakePlugin for v2.0?
    I see that it was removed from the release due to incompatibility, but it is still referenced in the docs & the conf file..

2. Is UCSM plugin working in v2.0?
    The plugin is not working out of the box due to a bad import, and the UCSMDriver doesn't seem to work either (Fake Driver worked after fixing the import issue).

3. Is the root resource of 'v2.0' for the REST API supposed to work?
    I am getting a status code 500 in the response header, on the server output I see 'RoutesException: URL or environ must be provided'.

Regards,
Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121114/2d73845e/attachment.html>