You are mixing a lot of current and defunct configuration options. I
recommend removing the defunct options and then comparing your
configuration files with the installation guide [1].
[1] http://docs.openstack.org/liberty/install-guide-ubuntu/
On Tue, Nov 1, 2016 at 7:05 AM, Davíð Örn
Does this [1] help?
[1] http://docs.openstack.org/newton/networking-guide/config-lbaas.html
On Tue, Oct 18, 2016 at 10:48 AM, Adam Lawson wrote:
> Greetings fellow stackers.
>
> So I found the list of service extensions [1,] the modular architecture
> [2] and info re the
In that case, you probably need the RBAC features in Mitaka.
On Wed, Oct 5, 2016 at 6:11 AM, Saverio Proto wrote:
> > Alternatively, you could drop the 'external' attribute and attach your
> > instances directly to the provider network (no routers or private
> networks).
>
>
How are you creating the provider (external) network?
On Thu, Sep 29, 2016 at 6:01 AM, Saverio Proto wrote:
> Hello,
>
> Context:
> - openstack liberty
> - ubuntu trusty
> - neutron networking with vxlan tunnels
>
> we have been running Openstack with a single external
>
> On Tue, Sep 20, 2016 at 12:01 PM, Matt Kassawara <mkassaw...@gmail.com>
> wrote:
>
>> Operators use other documentation besides the operations guide, which is
>> arguably more of an overview for potential operators than current
>> operators. Same for the architec
you mean by that? Can you please elaborate?
>
> L
>
> On 20/09/16 13:52, Matt Kassawara wrote:
> > Can we focus on all of the potentially relevant documentation?
> >
> > On Sun, Sep 18, 2016 at 5:34 PM, Lana Brindley <
> openst...@lanabrindley.com <mailto:openst
Can we focus on all of the potentially relevant documentation?
On Sun, Sep 18, 2016 at 5:34 PM, Lana Brindley
wrote:
> Hi Ops,
>
> For the last few Design Summits, I've run a docs session in the Ops track,
> to focus on the Ops Guide (and, to a lesser extent, the
Why isn't this content in the openstack-manuals repository?
On Sun, Aug 21, 2016 at 4:38 PM, Kaustubh Kelkar
wrote:
> I might have missed it entirely, but I wasn't able to find virtual
> resources used by the instances. IMO, it'd be great if one could see
> instance
Don't forget about fixing MTU in neutron. No more confusing options that
don't really do anything.
On Tue, Mar 8, 2016 at 12:12 PM, Matt Jarvis
wrote:
> We've just patched in https://review.openstack.org/#/c/262740/ on Kilo.
>
> On 8 March 2016 at 17:33, Jesse
Did you look at the DVR scenario in the networking guide [1]? DVR and other
architectures that use OVS build tunnels between br-tun bridges.
[1] http://docs.openstack.org/liberty/networking-guide/scenario-dvr-ovs.html
On Tue, Feb 16, 2016 at 12:47 PM, Adam Lawson wrote:
> Hi
Out of curiosity, what do you have for the "external_network_bridge" option
in the L3 agent config?
On Wed, Feb 10, 2016 at 2:42 PM, Bajin, Joseph wrote:
> Clayton,
>
> This is really good information.
>
> I’m wondering how we can help support you and get the necessary dev
Sure, you can use 'neutron router-gateway-set --disable-snat
' to disable NAT... just add routes where necessary.
Seems like implementation of RFC 6598 would occur outside of neutron...
maybe on the service provider network between clouds? Perhaps someone from
a service provider can provide more
Only the controller (running neutron-server) contains the ML2 plug-in
([ml2*] options in ml2_conf.ini) and schedules routers (L3 options
neutron.conf). Use of ml2_conf.ini on other nodes is a bit misleading.
However, prior to Liberty, configuration for L2 agents that reside on
network/compute
; Hi Matt,
> Is the current networking guide for liberty not updated?
> One more thing, where can i find ubuntu installation of openstack with ovs
> as l2 agent?
>
> Thanks,
> Akshay
>
> On Sun, Jan 10, 2016 at 8:32 PM, Matt Kassawara <mkassaw...@gmail.com>
> wrote:
>
&
Did you use tcpdump to see where the pings stop?
On Thu, Jan 7, 2016 at 1:36 PM, Mathieu Gagné wrote:
> On 2016-01-07 3:28 PM, Adam Dibiase wrote:
> > Greetings,
> >
> > I am having connectivity issues to instances after live migrating
> > between compute nodes. Scenario is
ssic, or some other phrasing to indicate lack of HA for
private networks and/or routers.
On Tue, Dec 8, 2015 at 7:33 PM, James Dempsey <jam...@catalyst.net.nz>
wrote:
> Hi Matt,
>
> Commentary in-line.
>
> On 05/12/15 14:03, Matt Kassawara wrote:
> > The networking gu
t the bottom as a separate section?
>
> "If you want to allow tenants to attach directly to these networks as
> well, continue reading."
>
> Then it has one step where you mark the network as 'shared' as well and
> it's done. ;)
>
> On Fri, Dec 4, 2015 at 5:03 PM,
Updates for the Kilo version of the installation guide included adding
support for cinder v2. The initial approach involved disabling cinder v1,
but we quickly found out that broke certain things. However, having two
separate service entries and groups of endpoints didn't make sense because
other
I think 16 UTC works well for most of the US, but doesn't include APAC and
probably not ideal for EU because it bumps into Friday evening. How about
alternating US/EU and APAC meetings every other week (similar to other
documentation meetings) and move the US/EU meeting to another day?
On Sun,
The official documentation would greatly benefit from more practical
information such as tuning... most likely in the administration or
operations guide, at least for now. Ideally, I would like to see a
operators contribute documentation for complete production deployments that
others can use as a
Using DVR, public traffic (generally involving the internet) from instances
with only a fixed IP traverses a conventional network node. See the DVR
scenario in the networking guide [1] for details.
[1] http://docs.openstack.org/networking-guide/scenario_dvr_ovs.html
On Fri, Oct 30, 2015 at 8:10
Take a look at the installation guide for Liberty at docs.openstack.org...
the architecture supports attaching VMs to public/external and
private/project networks.
On Sun, Oct 25, 2015 at 6:39 AM, Neil Jerram
wrote:
> For assigning a routable public IP to a VM, James
Did you review the scenarios in the networking guide [1]?
[1] http://docs.openstack.org/networking-guide/deploy.html
On Fri, Oct 2, 2015 at 2:41 PM, Sławek Kapłoński
wrote:
> Hello,
>
> I'm trying to configure small openstack infra (one network node, 2
> compute nodes)
I think these sorts of general upgrade notes from the trenches should also
belong in the operations guide.
On Tue, Sep 15, 2015 at 2:11 AM, Tom Fifield wrote:
> Hi all,
>
> One of our long mooted tags has been something that captures the ease of
> upgrade for a service.
>
>
You could also try provider networks with either OVS [1] or Linux bridge
[2].
[1] http://docs.openstack.org/networking-guide/deploy_scenario4a.html
[2] http://docs.openstack.org/networking-guide/deploy_scenario4b.html
On Tue, Jun 9, 2015 at 8:18 AM, Anne Gentle annegen...@justwriteclick.com
challenges?
-matt
On Thu, May 14, 2015 at 12:06 PM, Matt Kassawara mkassaw...@gmail.com
wrote:
I propose that we spend more time discussing how to improve the
networking guide for operators. Can we enhance the structure/content of
existing deployment scenarios to appeal to more operators
Does vlan81 between bond0 and br-vlan reflect a VLAN subinterface on the
host? If so, you need to remove it and attach bond0 directly to br-vlan
because Open vSwitch performs the tagging for you.
On Fri, Apr 10, 2015 at 3:13 PM, Gustavo Randich gustavo.rand...@gmail.com
wrote:
Hi,
I've tried
27 matches
Mail list logo