Hi Adam –
Please email me directly w/ the log information.
Thanks,
Rich
From: Adam Lawson [mailto:alaw...@aqorn.com]
Sent: Sunday, March 01, 2015 11:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] Fwd: [Neutron] ML2 + Nexus :: update_port_precommit
Hi Paul -
I noticed the same issue a while back and looked into adding additional info
(specific to the exception found in a mech driver) to the existing
MechanismDriverError.
I ended up not going in that direction and starting coding up some additional
common type mech driver exceptions in ml
Hi Luke -
Make sure you have the latest devstack which contains the ml2 hooks.
Remove the comments on the ML2 info below. Note that the mech driver keyword
for the logger is "logger", not "log".
Thanks,
Rich
From: Luke Gorrie [mailto:l...@tail-f.com]
Sent: Friday, September 06, 2013 11:33 AM
T
hat to make it clear that these are variables for
mechanism drivers? Something like:
[ML2_MECH_CISCO_NEXUS:
...
[ML2_MECH_ARISTA:]
...
As I said before, am fine with either of the proposals below too.
Andre
On Wed, Jun 19, 2013 at 8:59 AM, Rich Curran (rcurran)
mailto:rcur...@cisco.c
Hi All -
Regarding the configuration (ml2_conf.ini) of mechanism devices. Cisco defines
external devices in our INI file like this:
# Nexus Switch Format.
# [NEXUS_SWITCH:]
# = <- for cisco nexus devices a port would be in the form
"/"
# ssh_port=
# username= <- used as login username to the sw
