Hi James,
I was asking for the tunnel ports on br-tun on every compute.
sudo ovs-vsctl list-ifaces br-tun
patch-int
*vxlan-c0a80265vxlan-c0a802b1*
On Fri, Apr 28, 2017 at 8:41 PM, James Denton
wrote:
> Hi Vikash,
>
>
>
> The VXLAN tunnel endpoint address is listed in the output of a neut
It would be nice if there was a bit more transparency on the "legal
risk" (conflicts with another project, etc), but thanks for passing on
the information none-the-less. I, for one, welcome our new "Rocky"
overlord project name :)
Cheers,
--Morgan
On Fri, Apr 28, 2017 at 2:54 PM, Monty Taylor wr
Hey everybody!
There isn't a ton more to say past the subject. The "R" release of
OpenStack shall henceforth be known as "Rocky".
I believe it's the first time we've managed to name a release after a
community member - so please everyone buy RockyG a drink if you see her
in Boston.
For tho
With the network down, does ovs-vsctl show that it is connected to the
controller?
On Fri, Apr 28, 2017 at 2:21 PM, Gustavo Randich
wrote:
> Exactly, we access via a tagged interface, which is part of br-ex
>
> # ip a show vlan171
> 16: vlan171: mtu 9000 qdisc noqueue
> state UNKNOWN group defa
Exactly, we access via a tagged interface, which is part of br-ex
# ip a show vlan171
16: vlan171: mtu 9000 qdisc noqueue state
UNKNOWN group default qlen 1
link/ether 8e:14:8d:c1:1a:5f brd ff:ff:ff:ff:ff:ff
inet 10.171.1.240/20 brd 10.171.15.255 scope global vlan171
valid_lft fore
Ok, that's likely not the issue then. I assume the way you access each host
is via an IP assigned to an OVS bridge or an interface that somehow depends
on OVS?
On Apr 28, 2017 12:04, "Gustavo Randich" wrote:
> Hi Kevin, we are using the default listen address of loopback interface:
>
> # grep -r
Great question. There's not a simple yes/no answer, so let me go into some
detail about the different ways storage nodes can be selected to handle a
request.
There are a few config settings in the proxy server config that can affect how
nodes are selected for reads. Instead of describing these
Hi Kevin, we are using the default listen address of loopback interface:
# grep -r of_listen_address /etc/neutron
/etc/neutron/plugins/ml2/openvswitch_agent.ini:#of_listen_address =
127.0.0.1
tcp/127.0.0.1:6640 -> ovsdb-server /etc/openvswitch/conf.db
-vconsole:emer -vsyslog:err -vfile:i
Hi Vikash,
The VXLAN tunnel endpoint address is listed in the output of a neutron
agent-show :
$ neutron agent-show cb45e3f8-4a28-475a-994d-83bc27806c38
+-++
| Field | Value |
+
Hi Amit,
You can create a port on a particular subnet using the neutron/openstack CLI,
and then boot the instance using the port rather than the network. The
difference being nova boot --port-id versus --net-id.
James
From: Amit Uniyal
Date: Friday, April 28, 2017 at 4:12 AM
To: openstack
Su
Is there any neutron API, which returns the tunnel port details connected
to other host ?
For eg. I have Host-A and Host-B. Is there a way to know what is the
tunnel-port on Host-A which connects Host-B ?
Can't use OVS commands directly.
--
Regards,
Vikash
__
Hi All,
I had a doubt regarding the work-flow of Swift.
*'For read operation, we need to read from one of the three replicas. We
are aware that geographical origin of request is one of the factors to
decide which replica to read from(usually the nearest replica). But is also
the load on the nodes
Hi all,
How to launch a VM on particular subnet in network.
We have a option of creating more then one subnets in networks. but how to
launch a VM on particular subnet.
[image: Inline image 3]
In above image, I have a network parent-network, and this network has
sub-networks. My objective is
Are you using an of_listen_address value of an interface being brought
down?
On Apr 25, 2017 17:34, "Gustavo Randich" wrote:
> (using Mitaka / Ubuntu 16 / Neutron DVR / OVS / VXLAN / l2_population)
>
> This sounds very strange (to me): recently, after a switch outage, we lost
> connectivity to a
14 matches
Mail list logo
