Hi together,
is there a way to use Environment variables in the local.conf
post-config section?
On my system (stable/juno devstack) not the content of the variable, but
the variable name itself is being inserted into the config file.
So e.g.
[[post-config|$NOVA_CONF]]
[DEFAULT]
vncserver_proxy
Thanks for the feedback.
OK, got it, nova networking is not a requirement for a CI. Then I'll see
not a single reason to support it. We will investigate in the neutron
way for our CI and also for production.
Now coming back to the Hypervisorsupportmatrix
( https://wiki.openstack.org/wiki/Hypervi
Hi,
we're preparing to add a new platform, libvirt-kvm on system z
(https://blueprints.launchpad.net/nova/+spec/libvirt-kvm-systemz), to
the HypervisorSupportMatrix
https://wiki.openstack.org/wiki/HypervisorSupportMatrix .
This matrix also lists a number of networking features (e.g. vlan
network
I'm not sure about the exact reason, but this is what I think:
It's intended behavior, as adding an interface to a bridge is a
disruptive task. Here an example.
You want to add your eth0 interface that has an ip address assigned to
your bridge br-p1p1. You could do this with ovs-vsctl add-port b
Hi together,
I'm wondering why ovs was integrated into openstack in the way it is
today
(http://docs.openstack.org/grizzly/openstack-network/admin/content/under_the_hood_openvswitch.html)
Especially I would like to understand
- why does every physical interface have its own bridge? (I guess you
c
Hi Ageeleshwar,
the links you provided are wordpress admin links and require a login. Is
there also a public link available?
Thanks
--
Andreas
(irc: scheuran)
On Tue, 2014-09-30 at 09:33 +0530, Akilesh K wrote:
> Hi,
>
> I saw the table of contents. I have posted documents on configuring
> op
Hi
I just was playing around with various neutron-openvswitch-agent vxlan
configurations. The default port for vxlan traffic is 4789. I had
expected that when the neutron-openvswitch-agent reads the configured
vxlan port (or gets the default) it also would add an iptables rule to
allow incoming tra
Hi Mathieu,
please see my comments below.
On Wed, 2014-08-27 at 16:13 +0200, Mathieu Rohon wrote:
> hi irena,
>
> in the proposal of andreas you want to enforce the non-promisc mode
> per l2-agent?
yes, kind of. We're currently not yet sure how to figure out the right
interface for the registr
uld just make the kilo folder in your commit and then
> rebase it once Kilo is open.
>
>
> On Thu, Aug 28, 2014 at 12:07 AM, Andreas Scheuring
> wrote:
> Hi,
> is it already possible to subm
Hi,
is it already possible to submit specs (nova & neutron) for the K
release? Would be great for getting early feedback and tracking
comments. Or should I just commit it to the juno folder?
Thanks,
Andreas
___
OpenStack-dev mailing list
OpenStack-de
r, which also requires mac addresses registration of OVS ports.
> Please let me know if you would like to collaborate on this effort.
>
> BR,
> Irena
>
> -Original Message-
> From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> Sent: Friday, August 22, 201
oking for a developer to help implement it?
>
>
> On Thu, Aug 21, 2014 at 8:45 AM, Andreas Scheuring
> wrote:
> Hi,
> last week I started discussing an extension to the existing
> neutron
> openvswitch agent to support network adapters that are not i
Hi,
last week I started discussing an extension to the existing neutron
openvswitch agent to support network adapters that are not in
promiscuous mode. Now I would like to enhance the round to get feedback
from a broader audience via the mailing list.
The Problem
When driving vlan or flat networ
Hi together,
I found two blueprint templates for neutron
The .rst file on github
http://git.openstack.org/cgit/openstack/neutron-specs/tree/specs/template.rst
and the one on the openstack wiki page
https://wiki.openstack.org/wiki/Neutron/BlueprintTemplate
Are both templates still valid or is th
101 - 114 of 114 matches
Mail list logo
