It doesn’t sound like you have the stack running with your drivers. Here’s what
I remember happens with DevStack…
When stack.sh is run, it will take the /opt/stack/neutron/etc/vpn_agent.ini
file and copy it to /etc/neutron/vpn_agent.ini. If prior to stacking, you have
not added and uncommented
I have in my q-svc log this line:
2014-07-27 19:46:02.243 DEBUG neutron.service [-]
service_providers.service_provider =
['VPN:fake_junos_vpnaas:neutron.services.vpn.service_drivers.fake_service_driver.FakeServiceDriver:default']
from (pid=2770) log_opt_values
Hi again.
With previous days code, we don't experience any error in our logs, but we
don't see any logs in q-svc nor q-vpn. When we execute any Neutron VPN
command like neutron vpn-ikepolicy-list we receive:
404 Not Found
The resource could not be found.
And in q-svc logs we see:
2014-07-24
Check /etc/neutron/neutron.conf and see if your service driver is correctly
specified for VPN. You can also check the q-svc and q-vpn logs at the beginning
to see if the service and device drivers were actually loaded by the plugin and
agent, respectively. You can check vpn_agent.ini in same
Is there any documentation about these RPC messages? Or de we need to use
examples as guide?
Once again, thank you Paul.
http://dana.i2cat.net http://www.i2cat.net/en
Julio C. Barrera Juez [image: View my profile on LinkedIn]
http://es.linkedin.com/in/jcbarrera/en
Office phone: (+34) 93 357
Hi julio
There are not many documents currently. The only one on neutron I can
find is http://docs.openstack.org/developer/neutron/devref/index.html.
From what you described, I suggest you have a look of the neutron.
services.vpn code as an example.
And from my experience, those
I have __init__.py in the directory. Sorry my code is not public, but I can
show you some contents, anyway is an experiment with no functional code.
My /etc/neutron/vpn_agent.ini:
[DEFAULT]
[vpnagent]
# implementation location:
See line @PCM
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pcm_ (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
On Jul 17, 2014, at 6:32 AM, Julio Carlos Barrera Juez
juliocarlos.barr...@i2cat.net
We have followed your advices:
- We created our fake device driver located in the same level as other
device drivers
(/opt/stack/neutron/neutron/services/vpn//device_drivers/fake_device_driver.py):
import abc
import six
from neutron.openstack.common import log
from neutron.services.vpn import
So you have your driver loading… great!
The service driver will log in screen-q-svc.log, provided you have the service
driver called out in neutron.conf (as the only one for VPN).
Later, you’ll need the supporting RPC classes to send messages from service
driver to device driver…
Regards,
QQ: do you have __init__.py in the directory?
2014-07-16 11:43 GMT-07:00 Julio Carlos Barrera Juez
juliocarlos.barr...@i2cat.net:
I am fighting with this for months. I want to develop a VPN Neutron
plugin, but it is almost impossible to realize how to achieve it. this is a
thread I opened
Do you have a repo with the code that is visible to the public?
What does the /etc/neutron/vpn_agent.ini look like?
Can you put the log output of the actual error messages seen?
Regards,
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pcm_ (irc.freenode.com)
TW ………... @pmichali
GPG Key
12 matches
Mail list logo
