[openstack-dev] FW: how to configure cisco plugin in devstack environment
Yuling_C at DELL.com
Yuling_C at DELL.com
Thu May 16 01:19:14 UTC 2013
Hi Rich,
The original problem that I had was if I do not enable Q_PLUGIN=cisco, the core_plugin will always be OVS plugin instead of Cisco plugin.
I don't have a Cisco device yet, however, I will eventually test on Cisco Nexus switch. I do want to go as far as possible with Nexus fake driver. So, do you think with Q_PLUGIN=cisco, am I going to see pretty much the same environment as that of plugging a real device? I thought at least the data base tables would be the same as what I will see with a real switch...
So, if I would like to go as far as possible, do I need to follow your instruction to set subplugins, i.e. declare -a Q_CISCO_PLUGIN_SUBPLUGINS=(openvswitch nexus)?
Thanks,
YuLing
-----Original Message-----
From: Rich Curran (rcurran) [mailto:rcurran at cisco.com]
Sent: Tuesday, May 14, 2013 5:42 PM
To: C, Yuling; openstack-dev at lists.openstack.org; Robert Li (baoli)
Subject: RE: [openstack-dev] FW: how to configure cisco plugin in devstack environment
Hi Yuling -
Are you now using either an external nexus switch and/or the Nexus 1000 in your topology?
If not then I don't know why you would enable Q_PLUGIN=cisco in devstack's localrc.
But if you want to move forward regardless of available Cisco devices then you would have to follow the instructions listed in that web link below or you can add some additional information to the localrc file. Robert has put this info on a Cisco internal webpage so I'll cut/paste here. At some point (if he hasn't already) we should add this info to the devstack.org documentation.
=====================================================
Customization in localrc
In addition to existing DevStack variables, DevStack with Cisco plugin supports the following bash variables that can be defined in localrc.
declare -a Q_CISCO_PLUGIN_SUBPLUGINS
Supported values are:
(openvswitch)
(openvswitch nexus)
(n1kv)
(n1kv nexus)
Defines the subplugins that will be deployed with this DevStack. For example:
declare -a Q_CISCO_PLUGIN_SUBPLUGINS=(openvswitch nexus)
------------------------------------------------------
declare -A Q_CISCO_PLUGIN_SWITCH_INFO
The value has the following format:
({<switch_ip>=<username>:<password>:<ssh_port>[:<compute-host-name>:<nexus-port-connected-with>] })
Defines the nexus switch information used in the deployment. This is a bash associative array with nexus switch ip addresses as keys. Essentially, it defines the switch's access information, and the compute hosts that are connected to the switch. An example looks like
declare -A Q_CISCO_PLUGIN_SWITCH_INFO= ([1.1.1.1]=admin:mySecretPassword:22:compute1:1/1:compute2:1/2)
If Q_CISCO_PLUGIN_SWITCH_INFO is not defined in localrc, it assumes no switch is used in the deployment. In that case, if the nexus subplugin is deployed (as indicated by the Q_CISCO_PLUGIN_SUBPLUGINS array), a fake switch (with a fake driver) will be deployed.
**** - Note - since you're not using any cisco devices I wouldn't declare this variable and have the fake nexus driver configured.
======================================================
Thanks,
Rich
-----Original Message-----
From: Yuling_C at DELL.com [mailto:Yuling_C at DELL.com]
Sent: Tuesday, May 14, 2013 5:52 PM
To: Rich Curran (rcurran); openstack-dev at lists.openstack.org
Subject: RE: [openstack-dev] FW: how to configure cisco plugin in devstack environment
Hi Rich,
I was able to use Robert's file of lib/quantum_plugins/cisco to run cisco plugin in devstack environment. However, I'm not sure if everything was set up correctly in my environment. I thought this configuration using Q_plugin=cisco in localrc would set up exactly the same environment as what the instructions on the following attached link describes. However, I was not able to see the 'quantum_l2network' database at all. All I saw was database 'cisco_quantum'. Is there anything wrong in my set up? Should I see 'quantum_l2network' at all?
https://wiki.openstack.org/wiki/Cisco-quantum#A_Cisco_Plugin_Framework_for_Quantum_L2_Network_Overlays_Spanning_Multiple_Physical_Switches_.28Havana_Release.29
Thanks,
YuLing
-----Original Message-----
From: C, Yuling
Sent: Tuesday, May 07, 2013 11:40 AM
To: 'Rich Curran (rcurran)'; OpenStack Development Mailing List
Subject: RE: [openstack-dev] FW: how to configure cisco plugin in devstack environment
B.T.W., I'm not planning to use a Nexus switch in my testing environment for now...just would like to use the fake driver to see how it goes...will plugin a real switch later:-)
Thanks very much,
YuLing
-----Original Message-----
From: Rich Curran (rcurran) [mailto:rcurran at cisco.com]
Sent: Tuesday, May 07, 2013 11:13 AM
To: OpenStack Development Mailing List; C, Yuling
Subject: RE: [openstack-dev] FW: how to configure cisco plugin in devstack environment
HI Yuling -
Actually if you change the localrc as described below you won't have to install configobj (I don't think).
So change the localrc first, unstack, stack. I don't think at that point you'll have the configobj issue.
Thanks,
Rich
-----Original Message-----
From: Rich Curran (rcurran)
Sent: Tuesday, May 07, 2013 2:09 PM
To: Yuling_C at DELL.com; openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] FW: how to configure cisco plugin in devstack environment
Hi Yuling -
Here are instructions I found on installing configobj: http://www.voidspace.org.uk/python/articles/configobj.shtml
Also, you didn't get the latest (master) cisco quantum code.
In localrc please add/change:
OFFLINE=False
RECLONE=yes
Also, are you using a nexus hardware switch in your topology?
Thanks,
Rich
-----Original Message-----
From: Yuling_C at DELL.com [mailto:Yuling_C at DELL.com]
Sent: Tuesday, May 07, 2013 1:46 PM
To: openstack-dev at lists.openstack.org
Cc: Rich Curran (rcurran)
Subject: RE: [openstack-dev] FW: how to configure cisco plugin in devstack environment
Thanks very much for the information... I just tried commenting out #QUANTUM_BRANCH=stable/grizzly. However, when I ran 'stack.sh' again, I still hit the same issue.
>From reading the log, I can see quantum was trying to pick up cisco plugin. However, it failed at importing configobj at cisco_configparser.py. Could this be PYTHONPATH issue? (However, I don't see any instructions for changing this environment variable)
When you mentioned that
>' this assumes another
>change (cisco-single-config blueprint) that was committed to the
>openstack master branch but didn't make it into stable/grizzly'.
Do I need to pick up this change as well? The only thing I picked up was Robert's file of lib/quantum_plugins/cisco...the rest running on my environment was devstack grizzly release...
Thanks,
YuLing
-----Original Message-----
From: Robert Li (baoli) [mailto:baoli at cisco.com]
Sent: Tuesday, May 07, 2013 6:42 AM
To: OpenStack Development Mailing List
Cc: Rich Curran (rcurran)
Subject: [openstack-dev] FW: how to configure cisco plugin in devstack environment
Hi Yuling,
See below for the response from Rich.
Thanks,
Robert
On 5/7/13 9:33 AM, "Rich Curran (rcurran)" <rcurran at cisco.com> wrote:
>
>
>-----Original Message-----
>From: Rich Curran (rcurran)
>Sent: Tuesday, May 07, 2013 9:29 AM
>To: Kyle Mestery (kmestery); OpenStack Development Mailing List
>Subject: RE: [openstack-dev] how to configure cisco plugin in devstack
>environment
>
>Hi Yuling -
>
>I think there's at least one major mismatch going on here.
>
>If you're using Robert's devstack change
>(https://review.openstack.org/#/c/25378/) then this assumes another
>change (cisco-single-config blueprint) that was committed to the
>openstack master branch but didn't make it into stable/grizzly.
>
>If you want to continue to use Robert's devstack changes then please
>comment out this line from your localrc file:
>#QUANTUM_BRANCH=stable/grizzly
>
>./unstack.sh and then ./stack.sh again
>
>This should pick up the master version of quantum. To check verify that
>the only file under:
>etc/quantum/plugins/cisco/ is the cisco_plugins.ini file.
>
>Thanks,
>Rich
>
>-----Original Message-----
>From: Kyle Mestery (kmestery)
>Sent: Tuesday, May 07, 2013 9:07 AM
>To: OpenStack Development Mailing List
>Cc: Rich Curran (rcurran)
>Subject: Re: [openstack-dev] how to configure cisco plugin in devstack
>environment
>
>Did you do a "git fetch"? I think you may want to do that to ensure you
>get the entire change set.
>
>Can you paste the contents of your
>/etc/quantum/plugins/cisco/cisco_plugins.ini file?
>
>On May 7, 2013, at 1:39 AM, Yuling_C at DELL.com wrote:
>
>> Actually, I just followed the instruction on devstack grizzly
>>installation
>>link:http://networkstatic.net/installing-openstack-grizzly-with-devsta
>> ck/ and installed again. I copied over the 'cisco' file from the link
>>https://review.openstack.org/#/c/25378/ to lib/quantum_plugins/ and
>>set Q_plugin = cisco.
>>
>> However, when I run stack.sh, Quantum server was not able to start
>>with the following error in screen-q-svc.log:
>>
>> __import__(mod_str)
>> File "/opt/stack/quantum/quantum/plugins/cisco/network_plugin.py",
>>line 30, in <module>
>> from quantum.plugins.cisco.common import cisco_utils as cutil File
>>"/opt/stack/quantum/quantum/plugins/cisco/common/cisco_utils.py", line 23, in <module>
>> from quantum.plugins.cisco.db import l2network_db as cdb File
>>"/opt/stack/quantum/quantum/plugins/cisco/db/l2network_db.py", line
>>24, in <module>
>> from quantum.plugins.cisco import l2network_plugin_configuration
>>as conf File
>>"/opt/stack/quantum/quantum/plugins/cisco/l2network_plugin_configuration.
>>py", line 21, in <module>
>> from quantum.plugins.cisco.common import cisco_configparser as
>>confp File
>>"/opt/stack/quantum/quantum/plugins/cisco/common/cisco_configparser.py
>>",
>>line 19, in <module>
>> from configobj import ConfigObj
>> ImportError: No module named configobj
>> ERROR: Unable to load quantum from configuration file
>>/etc/quantum/api-paste.ini.
>>
>> Any idea why there's an input error for loading 'configobj'? this
>>file should be under /usr/lib/python2.7/dist-packages/landscape/lib.
>>Why quantum cannot load this file?
>>
>> Thanks,
>>
>> YuLing
>>
>> ________________________________________
>> From: C, Yuling
>> Sent: Monday, May 06, 2013 7:58 PM
>> To: openstack-dev at lists.openstack.org
>> Cc: rcurran at cisco.com
>> Subject: Re: [openstack-dev] how to configure cisco plugin in
>> devstack environment
>>
>> Thanks Kyle and Robert very much for all these information.
>>
>> So, it seems that the new devstack version that contains Cisco plugin
>>support is already available at https://review.openstack.org/#/c/25378/?
>>Should I just use 'git fetch' to download it and install? Is this
>>Havana version(release)?
>>
>> After I download, can I just use Q_plugin to configure the core plugin?
>>Do I still need to follow the manual set up steps on
>>https://wiki.openstack.org/wiki/Cisco-quantum#A_Cisco_Plugin_Framework
>>_fo
>>r_Quantum_L2_Network_Overlays_Spanning_Multiple_Physical_Switches_.28H
>>ava
>>na_Release.29?
>>
>> Thanks,
>>
>> YuLing
>>
>>
>> -----Original Message-----
>> From: Kyle Mestery (kmestery) [mailto:kmestery at cisco.com]
>> Sent: Monday, May 06, 2013 2:09 PM
>> To: OpenStack Development Mailing List
>> Cc: Rich Curran (rcurran)
>> Subject: Re: [openstack-dev] how to configure cisco plugin in
>> devstack environment
>>
>> I should note Robert's review for adding support to devstack for the
>>Cisco plugin is here:
>>
>> https://review.openstack.org/#/c/25378/
>>
>> I've been running with it for a few weeks and it works great!
>>
>> Thanks,
>> Kyle
>>
>> On May 6, 2013, at 3:54 PM, Robert Li (baoli) <baoli at cisco.com> wrote:
>>
>>> Hi YuLing,
>>>
>>> My guess is that you pulled the code from the master. So please
>>>follow this link
>>>https://wiki.openstack.org/wiki/Cisco-quantum#A_Cisco_Plugin_Framewor
>>>k_f
>>>or_Quantum_L2_Network_Overlays_Spanning_Multiple_Physical_Switches_.2
>>>8Ha
>>>vana_Release.29 instead.
>>>
>>> Currently, configuring Q_PLUGIN to use cisco plugin is not available
>>>in devstack yet, and it's being worked on. Therefore you have to
>>>manually configure it with instructions given in the above link.
>>>
>>> Thanks,
>>> Robert
>>>
>>> On 5/6/13 1:50 PM, "Yuling_C at DELL.com" <Yuling_C at DELL.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I'm new to devstack and would need to configure cisco plugin to
>>>>work in devstack environment. I followed the instruction in the
>>>>webpage
>>>>(https://wiki.openstack.org/wiki/Cisco-quantum#A_Cisco_Plugin_Framew
>>>>ork
>>>>_for_Quantum_L2_Network_Overlays_Spanning_Multiple_Physical_Switches
>>>>_.2
>>>>8Grizzly_Release.29) to configure cisco plugin. However, devstack
>>>>seems to always pick up OVSQuantumPluginV2 as 'core_plugin'. Any idea?
>>>>
>>>> I tried to set up Q_plugin in localrc. However, it seems cisco is
>>>>not one of the plugins supported under
>>>>/opt/stack/devstack/lib/quantum_plugins...do I need to configure
>>>>this variable in localrc? If not, what else I need to do in order
>>>>for openstack to pick up Cisco plugin in devstack environment?
>>>>
>>>> Thanks,
>>>>
>>>> YuLing
>>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list