[openstack-dev] [DevStack] neutron config not working
Before I get punted onto the operators list, I post this here because this is the default config and I'd expect the defaults to just work. Running devstack inside a VM with a single NIC configured and this in localrc: disable_service n-net enable_service q-svc enable_service q-agt enable_service q-dhcp enable_service q-l3 enable_service q-meta enable_service neutron Q_USE_DEBUG_COMMAND=True Results in a successful install but no DHCP address assigned to hosts I launch and other oddities like no CIDR in nova net-list output. Is this still the default way to set things up for single node? It is according to https://wiki.openstack.org/wiki/NeutronDevstack thanks rob ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
On 25/06/14 10:59, Rob Crittenden wrote: Before I get punted onto the operators list, I post this here because this is the default config and I'd expect the defaults to just work. Running devstack inside a VM with a single NIC configured and this in localrc: disable_service n-net enable_service q-svc enable_service q-agt enable_service q-dhcp enable_service q-l3 enable_service q-meta enable_service neutron Q_USE_DEBUG_COMMAND=True Results in a successful install but no DHCP address assigned to hosts I launch and other oddities like no CIDR in nova net-list output. Is this still the default way to set things up for single node? It is according to https://wiki.openstack.org/wiki/NeutronDevstack That does look ok: I have an essentially equivalent local.conf: ... ENABLED_SERVICES+=,-n-net ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest I don't have 'neutron' specifically enabled... not sure if/why that might make any difference tho. However instance launching and ip address assignment seem to work ok. However I *have* seen the issue of instances not getting ip addresses in single host setups, and it is often due to use of virt io with bridges (with is the default I think). Try: nova.conf: ... libvirt_use_virtio_for_bridges=False Regards Mark ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
On Tue, Jun 24, 2014 at 06:59:17PM -0400, Rob Crittenden wrote: > Before I get punted onto the operators list, I post this here because > this is the default config and I'd expect the defaults to just work. > > Running devstack inside a VM with a single NIC configured and this in > localrc: > > disable_service n-net > enable_service q-svc > enable_service q-agt > enable_service q-dhcp > enable_service q-l3 > enable_service q-meta > enable_service neutron > Q_USE_DEBUG_COMMAND=True > > Results in a successful install but no DHCP address assigned to hosts I > launch and other oddities like no CIDR in nova net-list output. > > Is this still the default way to set things up for single node? It is > according to https://wiki.openstack.org/wiki/NeutronDevstack I've used something simliar in my local.conf[1] w/ today's git. I get a successfull install too[2]. However, booting an instance is just perpetually stuck in SCHEDULING state: $ nova list +--++++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--++++-+--+ | 425a12e8-0b7e-4ad1-97db-20a912dea7df | f20vm2 | BUILD | scheduling | NOSTATE | | +--++++-+--+ I don't see anything interesting in Scheduler/CPU logs: $ grep ERROR ../data/new/screen-logs/screen-n-cpu.log $ grep ERROR ../data/new/screen-logs/screen-n-sch.log 2014-06-25 02:37:37.674 DEBUG nova.openstack.common.db.sqlalchemy.session [req-62d4dfe1-55f4-46fd-94c6-e1b270eca5e4 None None] MySQL server mode set to STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION _mysql_check_effective_sql_mode /opt/stack/nova/nova/openstack/common/db/sqlalchemy/session.py:562 Examining my install log[2], I only see 3 ERRORs that looked legitimate: (1) A fatal error about 'yaml.h' header file not found: --- [. . .] 2014-06-25 06:22:38.963 | gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c build/temp.linux-x86_64-2.7/check_libyaml.c -o build/temp.linux-x86_64-2.7/check_libyaml.o 2014-06-25 06:22:38.976 | build/temp.linux-x86_64-2.7/check_libyaml.c:2:18: fatal error: yaml.h: No such file or directory 2014-06-25 06:22:38.977 | #include 2014-06-25 06:22:38.977 | ^ 2014-06-25 06:22:38.978 | compilation terminated. 2014-06-25 06:22:38.995 | 2014-06-25 06:22:38.996 | libyaml is not found or a compiler error: forcing --without-libyaml 2014-06-25 06:22:38.996 | (if libyaml is installed correctly, you may need to 2014-06-25 06:22:38.997 | specify the option --include-dirs or uncomment and 2014-06-25 06:22:38.997 | modify the parameter include_dirs in setup.cfg) 2014-06-25 06:22:39.044 | [. . .] --- (2) For some reason, it couldn't connect to Libvirt Hypervisor, as it couldn't find the Libvirt socket file. --- [. . .] 2014-06-25 06:32:08.942 | error: failed to connect to the hypervisor 2014-06-25 06:32:08.943 | error: no valid connection 2014-06-25 06:32:08.943 | error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory 2014-06-25 06:32:08.948 | + instances= [. . .] --- However, the file _does_ exist: $ file /var/run/libvirt/libvirt-sock /var/run/libvirt/libvirt-sock: socket (3) A Neutron complaint that it couldn't find a certain qprobe network namespace: --- [. . .] 2014-06-25 06:37:21.009 | + neutron-debug --os-tenant-name admin --os-username admin --os-password fedora probe-create --device-owner compute 7624586e-120d-45dd-a918-716b942407ff 2014-06-25 06:37:23.435 | 2014-06-25 02:37:23.434 9698 ERROR neutron.agent.linux.utils [-] 2014-06-25 06:37:23.436 | Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qprobe-19193c58-a12d-4910-b38d-cd638714b1df', 'ip', '-o', 'link', 'show', 'tap19193c58-a1'] 2014-06-25 06:37:23.436 | Exit code: 1 2014-06-25 06:37:23.437 | Stdout: '' 2014-06-25 06:37:23.437 | Stderr: 'Cannot open network namespace "qprobe-19193c58-a12d-4910-b38d-cd638714b1df": No such file or directory\n' [. . .] --- Howver, running `ip netns` _does_ enumerate the above qprobe network namespace. Other info -- T
Re: [openstack-dev] [DevStack] neutron config not working
On Wed, Jun 25, 2014 at 01:36:02PM +0530, Kashyap Chamarthy wrote: > On Tue, Jun 24, 2014 at 06:59:17PM -0400, Rob Crittenden wrote: [. . .] > Examining my install log[2], I only see 3 ERRORs that looked legitimate: > > (1) A fatal error about 'yaml.h' header file not found: > --- > [. . .] > 2014-06-25 06:22:38.963 | gcc -pthread -fno-strict-aliasing -O2 -g -pipe > -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong > --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic > -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong > --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic > -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c > build/temp.linux-x86_64-2.7/check_libyaml.c -o > build/temp.linux-x86_64-2.7/check_libyaml.o > 2014-06-25 06:22:38.976 | > build/temp.linux-x86_64-2.7/check_libyaml.c:2:18: fatal error: yaml.h: No > such file or directory > 2014-06-25 06:22:38.977 | #include > 2014-06-25 06:22:38.977 | ^ > 2014-06-25 06:22:38.978 | compilation terminated. > 2014-06-25 06:22:38.995 | > 2014-06-25 06:22:38.996 | libyaml is not found or a compiler error: > forcing --without-libyaml > 2014-06-25 06:22:38.996 | (if libyaml is installed correctly, you may > need to > 2014-06-25 06:22:38.997 | specify the option --include-dirs or uncomment > and > 2014-06-25 06:22:38.997 | modify the parameter include_dirs in setup.cfg) > 2014-06-25 06:22:39.044 | > [. . .] > --- This was resolved after I manually installed PyYAML RPM package on my F20 system. (Thanks Attila Fazekas for pointing that out.) > (2) For some reason, it couldn't connect to Libvirt Hypervisor, as it > couldn't find the Libvirt socket file. > --- > [. . .] > 2014-06-25 06:32:08.942 | error: failed to connect to the hypervisor > 2014-06-25 06:32:08.943 | error: no valid connection > 2014-06-25 06:32:08.943 | error: Failed to connect socket to > '/var/run/libvirt/libvirt-sock': No such file or directory > 2014-06-25 06:32:08.948 | + instances= > [. . .] > --- This too has gone in my second DevStack run. > > However, the file _does_ exist: > > $ file /var/run/libvirt/libvirt-sock > /var/run/libvirt/libvirt-sock: socket > > > (3) A Neutron complaint that it couldn't find a certain qprobe network > namespace: > --- > [. . .] > 2014-06-25 06:37:21.009 | + neutron-debug --os-tenant-name admin > --os-username admin --os-password fedora probe-create --device-owner compute > 7624586e-120d-45dd-a918-716b942407ff > 2014-06-25 06:37:23.435 | 2014-06-25 02:37:23.434 9698 ERROR > neutron.agent.linux.utils [-] > 2014-06-25 06:37:23.436 | Command: ['sudo', '/usr/bin/neutron-rootwrap', > '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', > 'qprobe-19193c58-a12d-4910-b38d-cd638714b1df', 'ip', '-o', 'link', 'show', > 'tap19193c58-a1'] > 2014-06-25 06:37:23.436 | Exit code: 1 > 2014-06-25 06:37:23.437 | Stdout: '' > 2014-06-25 06:37:23.437 | Stderr: 'Cannot open network namespace > "qprobe-19193c58-a12d-4910-b38d-cd638714b1df": No such file or directory\n' > [. . .] > --- > > Howver, running `ip netns` _does_ enumerate the above qprobe network > namespace. This still persists. And, when I boot an instance, it's still at SCHEDULING stage with no useful debug messages. I'll try verbose/debug logging. -- /kashyap ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
Mark Kirkwood wrote: > On 25/06/14 10:59, Rob Crittenden wrote: >> Before I get punted onto the operators list, I post this here because >> this is the default config and I'd expect the defaults to just work. >> >> Running devstack inside a VM with a single NIC configured and this in >> localrc: >> >> disable_service n-net >> enable_service q-svc >> enable_service q-agt >> enable_service q-dhcp >> enable_service q-l3 >> enable_service q-meta >> enable_service neutron >> Q_USE_DEBUG_COMMAND=True >> >> Results in a successful install but no DHCP address assigned to hosts I >> launch and other oddities like no CIDR in nova net-list output. >> >> Is this still the default way to set things up for single node? It is >> according to https://wiki.openstack.org/wiki/NeutronDevstack >> >> > > That does look ok: I have an essentially equivalent local.conf: > > ... > ENABLED_SERVICES+=,-n-net > ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest > > I don't have 'neutron' specifically enabled... not sure if/why that > might make any difference tho. However instance launching and ip address > assignment seem to work ok. > > However I *have* seen the issue of instances not getting ip addresses in > single host setups, and it is often due to use of virt io with bridges > (with is the default I think). Try: > > nova.conf: > ... > libvirt_use_virtio_for_bridges=False Thanks for the suggestion. At least in master this was replaced by a new section, libvirt, but even setting it to False didn't do the trick for me. I see the same behavior. thanks rob ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
Rob Crittenden wrote: > Mark Kirkwood wrote: >> On 25/06/14 10:59, Rob Crittenden wrote: >>> Before I get punted onto the operators list, I post this here because >>> this is the default config and I'd expect the defaults to just work. >>> >>> Running devstack inside a VM with a single NIC configured and this in >>> localrc: >>> >>> disable_service n-net >>> enable_service q-svc >>> enable_service q-agt >>> enable_service q-dhcp >>> enable_service q-l3 >>> enable_service q-meta >>> enable_service neutron >>> Q_USE_DEBUG_COMMAND=True >>> >>> Results in a successful install but no DHCP address assigned to hosts I >>> launch and other oddities like no CIDR in nova net-list output. >>> >>> Is this still the default way to set things up for single node? It is >>> according to https://wiki.openstack.org/wiki/NeutronDevstack >>> >>> >> >> That does look ok: I have an essentially equivalent local.conf: >> >> ... >> ENABLED_SERVICES+=,-n-net >> ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest >> >> I don't have 'neutron' specifically enabled... not sure if/why that >> might make any difference tho. However instance launching and ip address >> assignment seem to work ok. >> >> However I *have* seen the issue of instances not getting ip addresses in >> single host setups, and it is often due to use of virt io with bridges >> (with is the default I think). Try: >> >> nova.conf: >> ... >> libvirt_use_virtio_for_bridges=False > > Thanks for the suggestion. At least in master this was replaced by a new > section, libvirt, but even setting it to False didn't do the trick for > me. I see the same behavior. OK, I've tested the havana and icehouse branches in F-20 and they don't seem to have a working neutron either. I see the same thing. I can launch a VM but it isn't getting a DHCP address. Maybe I'll try in some Ubuntu release to see if this is Fedora-specific. rob ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
Hi Rob: Can you try adding the following config to your local.conf? I'd like to see if this gets you going or not. It will force it to use gre tunnels for tenant networks. By default it will not. ENABLE_TENANT_TUNNELS=True On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden wrote: > Rob Crittenden wrote: >> Mark Kirkwood wrote: >>> On 25/06/14 10:59, Rob Crittenden wrote: Before I get punted onto the operators list, I post this here because this is the default config and I'd expect the defaults to just work. Running devstack inside a VM with a single NIC configured and this in localrc: disable_service n-net enable_service q-svc enable_service q-agt enable_service q-dhcp enable_service q-l3 enable_service q-meta enable_service neutron Q_USE_DEBUG_COMMAND=True Results in a successful install but no DHCP address assigned to hosts I launch and other oddities like no CIDR in nova net-list output. Is this still the default way to set things up for single node? It is according to https://wiki.openstack.org/wiki/NeutronDevstack >>> >>> That does look ok: I have an essentially equivalent local.conf: >>> >>> ... >>> ENABLED_SERVICES+=,-n-net >>> ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest >>> >>> I don't have 'neutron' specifically enabled... not sure if/why that >>> might make any difference tho. However instance launching and ip address >>> assignment seem to work ok. >>> >>> However I *have* seen the issue of instances not getting ip addresses in >>> single host setups, and it is often due to use of virt io with bridges >>> (with is the default I think). Try: >>> >>> nova.conf: >>> ... >>> libvirt_use_virtio_for_bridges=False >> >> Thanks for the suggestion. At least in master this was replaced by a new >> section, libvirt, but even setting it to False didn't do the trick for >> me. I see the same behavior. > > OK, I've tested the havana and icehouse branches in F-20 and they don't > seem to have a working neutron either. I see the same thing. I can > launch a VM but it isn't getting a DHCP address. > > Maybe I'll try in some Ubuntu release to see if this is Fedora-specific. > > rob > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
I¹m seeing similar. Instances launch, they show as having Ips in `neutron list` but I cannot access them via IP. Other thing I¹ve notices is that doing a `neutron agent-list` gives me an empty list, I would assume it should at least show the dhcp agent ? On 7/1/14, 12:00 PM, "Kyle Mestery" wrote: >Hi Rob: > >Can you try adding the following config to your local.conf? I'd like >to see if this gets you going or not. It will force it to use gre >tunnels for tenant networks. By default it will not. > >ENABLE_TENANT_TUNNELS=True > >On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden >wrote: >> Rob Crittenden wrote: >>> Mark Kirkwood wrote: On 25/06/14 10:59, Rob Crittenden wrote: > Before I get punted onto the operators list, I post this here because > this is the default config and I'd expect the defaults to just work. > > Running devstack inside a VM with a single NIC configured and this in > localrc: > > disable_service n-net > enable_service q-svc > enable_service q-agt > enable_service q-dhcp > enable_service q-l3 > enable_service q-meta > enable_service neutron > Q_USE_DEBUG_COMMAND=True > > Results in a successful install but no DHCP address assigned to >hosts I > launch and other oddities like no CIDR in nova net-list output. > > Is this still the default way to set things up for single node? It is > according to https://wiki.openstack.org/wiki/NeutronDevstack > > That does look ok: I have an essentially equivalent local.conf: ... ENABLED_SERVICES+=,-n-net ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest I don't have 'neutron' specifically enabled... not sure if/why that might make any difference tho. However instance launching and ip address assignment seem to work ok. However I *have* seen the issue of instances not getting ip addresses in single host setups, and it is often due to use of virt io with bridges (with is the default I think). Try: nova.conf: ... libvirt_use_virtio_for_bridges=False >>> >>> Thanks for the suggestion. At least in master this was replaced by a >>>new >>> section, libvirt, but even setting it to False didn't do the trick for >>> me. I see the same behavior. >> >> OK, I've tested the havana and icehouse branches in F-20 and they don't >> seem to have a working neutron either. I see the same thing. I can >> launch a VM but it isn't getting a DHCP address. >> >> Maybe I'll try in some Ubuntu release to see if this is Fedora-specific. >> >> rob >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >___ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
On Thu, Jul 3, 2014 at 10:14 AM, Paul Czarkowski wrote: > I¹m seeing similar. Instances launch, they show as having Ips in > `neutron list` but I cannot access them via IP. > > Other thing I¹ve notices is that doing a `neutron agent-list` gives me an > empty list, I would assume it should at least show the dhcp agent ? > Which plugin are you using? For ML2 with OVS or LB, you should have L2 agents on each compute host in addition to the DHCP and L3 agents. I think perhaps your problem is different than Rob's. > On 7/1/14, 12:00 PM, "Kyle Mestery" wrote: > >>Hi Rob: >> >>Can you try adding the following config to your local.conf? I'd like >>to see if this gets you going or not. It will force it to use gre >>tunnels for tenant networks. By default it will not. >> >>ENABLE_TENANT_TUNNELS=True >> >>On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden >>wrote: >>> Rob Crittenden wrote: Mark Kirkwood wrote: > On 25/06/14 10:59, Rob Crittenden wrote: >> Before I get punted onto the operators list, I post this here because >> this is the default config and I'd expect the defaults to just work. >> >> Running devstack inside a VM with a single NIC configured and this in >> localrc: >> >> disable_service n-net >> enable_service q-svc >> enable_service q-agt >> enable_service q-dhcp >> enable_service q-l3 >> enable_service q-meta >> enable_service neutron >> Q_USE_DEBUG_COMMAND=True >> >> Results in a successful install but no DHCP address assigned to >>hosts I >> launch and other oddities like no CIDR in nova net-list output. >> >> Is this still the default way to set things up for single node? It is >> according to https://wiki.openstack.org/wiki/NeutronDevstack >> >> > > That does look ok: I have an essentially equivalent local.conf: > > ... > ENABLED_SERVICES+=,-n-net > ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest > > I don't have 'neutron' specifically enabled... not sure if/why that > might make any difference tho. However instance launching and ip >address > assignment seem to work ok. > > However I *have* seen the issue of instances not getting ip addresses >in > single host setups, and it is often due to use of virt io with bridges > (with is the default I think). Try: > > nova.conf: > ... > libvirt_use_virtio_for_bridges=False Thanks for the suggestion. At least in master this was replaced by a new section, libvirt, but even setting it to False didn't do the trick for me. I see the same behavior. >>> >>> OK, I've tested the havana and icehouse branches in F-20 and they don't >>> seem to have a working neutron either. I see the same thing. I can >>> launch a VM but it isn't getting a DHCP address. >>> >>> Maybe I'll try in some Ubuntu release to see if this is Fedora-specific. >>> >>> rob >>> >>> >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >>___ >>OpenStack-dev mailing list >>OpenStack-dev@lists.openstack.org >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
Paul, you need run the command as admin. If you are sourcing openrc as demo tenant or something it will not list. However, I also face this issue of IP address not getting assigned. On Fri, Jul 4, 2014 at 2:35 AM, Kyle Mestery wrote: > On Thu, Jul 3, 2014 at 10:14 AM, Paul Czarkowski > wrote: > > I¹m seeing similar. Instances launch, they show as having Ips in > > `neutron list` but I cannot access them via IP. > > > > Other thing I¹ve notices is that doing a `neutron agent-list` gives me an > > empty list, I would assume it should at least show the dhcp agent ? > > > Which plugin are you using? For ML2 with OVS or LB, you should have L2 > agents on each compute host in addition to the DHCP and L3 agents. I > think perhaps your problem is different than Rob's. > > > On 7/1/14, 12:00 PM, "Kyle Mestery" wrote: > > > >>Hi Rob: > >> > >>Can you try adding the following config to your local.conf? I'd like > >>to see if this gets you going or not. It will force it to use gre > >>tunnels for tenant networks. By default it will not. > >> > >>ENABLE_TENANT_TUNNELS=True > >> > >>On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden > >>wrote: > >>> Rob Crittenden wrote: > Mark Kirkwood wrote: > > On 25/06/14 10:59, Rob Crittenden wrote: > >> Before I get punted onto the operators list, I post this here > because > >> this is the default config and I'd expect the defaults to just work. > >> > >> Running devstack inside a VM with a single NIC configured and this > in > >> localrc: > >> > >> disable_service n-net > >> enable_service q-svc > >> enable_service q-agt > >> enable_service q-dhcp > >> enable_service q-l3 > >> enable_service q-meta > >> enable_service neutron > >> Q_USE_DEBUG_COMMAND=True > >> > >> Results in a successful install but no DHCP address assigned to > >>hosts I > >> launch and other oddities like no CIDR in nova net-list output. > >> > >> Is this still the default way to set things up for single node? It > is > >> according to https://wiki.openstack.org/wiki/NeutronDevstack > >> > >> > > > > That does look ok: I have an essentially equivalent local.conf: > > > > ... > > ENABLED_SERVICES+=,-n-net > > ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest > > > > I don't have 'neutron' specifically enabled... not sure if/why that > > might make any difference tho. However instance launching and ip > >address > > assignment seem to work ok. > > > > However I *have* seen the issue of instances not getting ip addresses > >in > > single host setups, and it is often due to use of virt io with > bridges > > (with is the default I think). Try: > > > > nova.conf: > > ... > > libvirt_use_virtio_for_bridges=False > > Thanks for the suggestion. At least in master this was replaced by a > new > section, libvirt, but even setting it to False didn't do the trick for > me. I see the same behavior. > >>> > >>> OK, I've tested the havana and icehouse branches in F-20 and they don't > >>> seem to have a working neutron either. I see the same thing. I can > >>> launch a VM but it isn't getting a DHCP address. > >>> > >>> Maybe I'll try in some Ubuntu release to see if this is > Fedora-specific. > >>> > >>> rob > >>> > >>> > >>> ___ > >>> OpenStack-dev mailing list > >>> OpenStack-dev@lists.openstack.org > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >>___ > >>OpenStack-dev mailing list > >>OpenStack-dev@lists.openstack.org > >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
I am using Ubuntu 14.04 and running devstack from top of the tree. Everything goes fine, but I am not able to ping the instance IP addresses. I am not able to log into the VM using novnc, but I am sure the VM is not getting the IP Address. On Fri, Jul 4, 2014 at 4:47 PM, Anant Patil wrote: > Paul, you need run the command as admin. If you are sourcing > openrc as demo tenant or something it will not list. > > However, I also face this issue of IP address not getting assigned. > > > On Fri, Jul 4, 2014 at 2:35 AM, Kyle Mestery > wrote: > >> On Thu, Jul 3, 2014 at 10:14 AM, Paul Czarkowski >> wrote: >> > I¹m seeing similar. Instances launch, they show as having Ips in >> > `neutron list` but I cannot access them via IP. >> > >> > Other thing I¹ve notices is that doing a `neutron agent-list` gives me >> an >> > empty list, I would assume it should at least show the dhcp agent ? >> > >> Which plugin are you using? For ML2 with OVS or LB, you should have L2 >> agents on each compute host in addition to the DHCP and L3 agents. I >> think perhaps your problem is different than Rob's. >> >> > On 7/1/14, 12:00 PM, "Kyle Mestery" wrote: >> > >> >>Hi Rob: >> >> >> >>Can you try adding the following config to your local.conf? I'd like >> >>to see if this gets you going or not. It will force it to use gre >> >>tunnels for tenant networks. By default it will not. >> >> >> >>ENABLE_TENANT_TUNNELS=True >> >> >> >>On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden >> >>wrote: >> >>> Rob Crittenden wrote: >> Mark Kirkwood wrote: >> > On 25/06/14 10:59, Rob Crittenden wrote: >> >> Before I get punted onto the operators list, I post this here >> because >> >> this is the default config and I'd expect the defaults to just >> work. >> >> >> >> Running devstack inside a VM with a single NIC configured and this >> in >> >> localrc: >> >> >> >> disable_service n-net >> >> enable_service q-svc >> >> enable_service q-agt >> >> enable_service q-dhcp >> >> enable_service q-l3 >> >> enable_service q-meta >> >> enable_service neutron >> >> Q_USE_DEBUG_COMMAND=True >> >> >> >> Results in a successful install but no DHCP address assigned to >> >>hosts I >> >> launch and other oddities like no CIDR in nova net-list output. >> >> >> >> Is this still the default way to set things up for single node? It >> is >> >> according to https://wiki.openstack.org/wiki/NeutronDevstack >> >> >> >> >> > >> > That does look ok: I have an essentially equivalent local.conf: >> > >> > ... >> > ENABLED_SERVICES+=,-n-net >> > ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest >> > >> > I don't have 'neutron' specifically enabled... not sure if/why that >> > might make any difference tho. However instance launching and ip >> >address >> > assignment seem to work ok. >> > >> > However I *have* seen the issue of instances not getting ip >> addresses >> >in >> > single host setups, and it is often due to use of virt io with >> bridges >> > (with is the default I think). Try: >> > >> > nova.conf: >> > ... >> > libvirt_use_virtio_for_bridges=False >> >> Thanks for the suggestion. At least in master this was replaced by a >> new >> section, libvirt, but even setting it to False didn't do the trick >> for >> me. I see the same behavior. >> >>> >> >>> OK, I've tested the havana and icehouse branches in F-20 and they >> don't >> >>> seem to have a working neutron either. I see the same thing. I can >> >>> launch a VM but it isn't getting a DHCP address. >> >>> >> >>> Maybe I'll try in some Ubuntu release to see if this is >> Fedora-specific. >> >>> >> >>> rob >> >>> >> >>> >> >>> ___ >> >>> OpenStack-dev mailing list >> >>> OpenStack-dev@lists.openstack.org >> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >>___ >> >>OpenStack-dev mailing list >> >>OpenStack-dev@lists.openstack.org >> >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> > >> > ___ >> > OpenStack-dev mailing list >> > OpenStack-dev@lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] neutron config not working
I did some dhcpdump and I could see that the requests were coming to the DHCP server and replies were sent. I am not able to ping the VMs from anywhere, DHCP namespace or Router namespace. I guess the problem is with interface being configured with the supplied IP address. On Fri, Jul 4, 2014 at 4:49 PM, Anant Patil wrote: > I am using Ubuntu 14.04 and running devstack from top of the tree. > Everything goes fine, but I am not able to ping the instance IP > addresses. I am not able to log into the VM using novnc, but I > am sure the VM is not getting the IP Address. > > > On Fri, Jul 4, 2014 at 4:47 PM, Anant Patil > wrote: > >> Paul, you need run the command as admin. If you are sourcing >> openrc as demo tenant or something it will not list. >> >> However, I also face this issue of IP address not getting assigned. >> >> >> On Fri, Jul 4, 2014 at 2:35 AM, Kyle Mestery >> wrote: >> >>> On Thu, Jul 3, 2014 at 10:14 AM, Paul Czarkowski >>> wrote: >>> > I¹m seeing similar. Instances launch, they show as having Ips in >>> > `neutron list` but I cannot access them via IP. >>> > >>> > Other thing I¹ve notices is that doing a `neutron agent-list` gives me >>> an >>> > empty list, I would assume it should at least show the dhcp agent ? >>> > >>> Which plugin are you using? For ML2 with OVS or LB, you should have L2 >>> agents on each compute host in addition to the DHCP and L3 agents. I >>> think perhaps your problem is different than Rob's. >>> >>> > On 7/1/14, 12:00 PM, "Kyle Mestery" wrote: >>> > >>> >>Hi Rob: >>> >> >>> >>Can you try adding the following config to your local.conf? I'd like >>> >>to see if this gets you going or not. It will force it to use gre >>> >>tunnels for tenant networks. By default it will not. >>> >> >>> >>ENABLE_TENANT_TUNNELS=True >>> >> >>> >>On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden >>> >>wrote: >>> >>> Rob Crittenden wrote: >>> Mark Kirkwood wrote: >>> > On 25/06/14 10:59, Rob Crittenden wrote: >>> >> Before I get punted onto the operators list, I post this here >>> because >>> >> this is the default config and I'd expect the defaults to just >>> work. >>> >> >>> >> Running devstack inside a VM with a single NIC configured and >>> this in >>> >> localrc: >>> >> >>> >> disable_service n-net >>> >> enable_service q-svc >>> >> enable_service q-agt >>> >> enable_service q-dhcp >>> >> enable_service q-l3 >>> >> enable_service q-meta >>> >> enable_service neutron >>> >> Q_USE_DEBUG_COMMAND=True >>> >> >>> >> Results in a successful install but no DHCP address assigned to >>> >>hosts I >>> >> launch and other oddities like no CIDR in nova net-list output. >>> >> >>> >> Is this still the default way to set things up for single node? >>> It is >>> >> according to https://wiki.openstack.org/wiki/NeutronDevstack >>> >> >>> >> >>> > >>> > That does look ok: I have an essentially equivalent local.conf: >>> > >>> > ... >>> > ENABLED_SERVICES+=,-n-net >>> > >>> ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest >>> > >>> > I don't have 'neutron' specifically enabled... not sure if/why that >>> > might make any difference tho. However instance launching and ip >>> >address >>> > assignment seem to work ok. >>> > >>> > However I *have* seen the issue of instances not getting ip >>> addresses >>> >in >>> > single host setups, and it is often due to use of virt io with >>> bridges >>> > (with is the default I think). Try: >>> > >>> > nova.conf: >>> > ... >>> > libvirt_use_virtio_for_bridges=False >>> >>> Thanks for the suggestion. At least in master this was replaced by a >>> new >>> section, libvirt, but even setting it to False didn't do the trick >>> for >>> me. I see the same behavior. >>> >>> >>> >>> OK, I've tested the havana and icehouse branches in F-20 and they >>> don't >>> >>> seem to have a working neutron either. I see the same thing. I can >>> >>> launch a VM but it isn't getting a DHCP address. >>> >>> >>> >>> Maybe I'll try in some Ubuntu release to see if this is >>> Fedora-specific. >>> >>> >>> >>> rob >>> >>> >>> >>> >>> >>> ___ >>> >>> OpenStack-dev mailing list >>> >>> OpenStack-dev@lists.openstack.org >>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >>> >>___ >>> >>OpenStack-dev mailing list >>> >>OpenStack-dev@lists.openstack.org >>> >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> > >>> > >>> > ___ >>> > OpenStack-dev mailing list >>> > OpenStack-dev@lists.openstack.org >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.o
