On Thu, Jul 3, 2014 at 10:14 AM, Paul Czarkowski <paul.czarkow...@rackspace.com> 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" <mest...@noironetworks.com> 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 <rcrit...@redhat.com> >>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
