I pushed a container to docker hub that runs openstack neutron (master
branch) + ovn plugin + ovs daemons on the north bound databases. You
can run it with:
docker run -d --net=host --name ipam ovntest/ipam:v0.1
Once the container starts, from a neutron client (based off openstack
master), you ca
>
> While Neutron IPAM takes care of IP Address Management, you will probably
> also need Neutron's DHCP agent for address distribution, unless you have
> some sort of tool that configures your containers by picking IPAM info from
> the Neutron API.
The second part. The idea is to start with keepin
>
> Does it fail without specifying --tenant-id ?
Yes.
$ neutron net-create dummy3
Running without keystone AuthN requires that tenant_id is specified
>
> --
> Russell Bryant
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listi
On 04/10/2015 04:02 PM, Gurucharan Shetty wrote:
>> How does no-auth mode work? Does it just make it look like every
>> request is done by an admin or something?
> Something like that. For e.g., I have a setup with neutron +
> networking-ovn setup initially with devstack and then I unstack and
> m
> How does no-auth mode work? Does it just make it look like every
> request is done by an admin or something?
Something like that. For e.g., I have a setup with neutron +
networking-ovn setup initially with devstack and then I unstack and
manually start neutron with 'no-auth'. I just need the fol