I am proposing that Octavia should support deployment models that
enable multiple listeners to be configured inside the HAProxy
instance.
The model I am proposing is:
1. One or more VIP per Octavia VM (propose one VIP in 0.5 release)
2. One or more HAProxy instance per Octavia VM
3. One or more l
I am investigating building scripts that use diskimage-builder
(https://github.com/openstack/diskimage-builder) to create a "purpose
built" image. This should allow some flexibility in the base image
and the output image format (including a path to docker).
The definition of "purpose built" is op
We decided to cancel the weekly Octavia IRC meeting next week due to
the OpenStack Summit in Berlin.
Some of the Octavia related sessions:
Octavia - Project Onboarding - Tue 13, 3:20pm - 4:00pm
Extending Your OpenStack Troubleshooting Tool Box - Digging deeper
into network operations - Wed 14, 11
At the moment that is all we have for a setup guide.
That said, all of the Octavia controller processes are fully HA
capable. The one setting I can think of is the controller_ip_port_list
setting mentioned above. It will need to contain an entry for each
health manager IP/port as Sa Pham mentioned
I will chair the meeting. With Graham and Doug not available I
suspect it will be quick, but I want to have the meeting in case there
is followup from the summit.
Michael
On Mon, Nov 2, 2015 at 3:01 PM, Hayes, Graham wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi All,
>
> I wil
+1
On Thu, Nov 19, 2015 at 9:35 AM, Eichberger, German
wrote:
> All,
>
>
>
> As I said in a previous e-mail I am really excited about the deep talent in
> the Octavia sub-project. So it is my pleasure to propose Bertrand Lallau (irc
> blallau) as a new core for the OpenStack Neutron Octavia sub
Hi Wanghua,
From the o-cw log, it looks like the amphora service VM did not boot
properly or the network is not configured correctly. We can see that
Nova said the VM went active, but the amphora-agent inside the image
never became reachable. I would check the nova instance console log
to make s
I agree that if this occurred it is a bug. Please open a bug for us
in launchpad and include your controller worker logs and amphora-agent
log from the impacted amphora.
Thanks,
Michael
On Wed, Jun 1, 2016 at 9:55 AM, Stephen Balukoff wrote:
> Hello Yong Sheng Gong!
>
> Apologies for the laten
Hi Sergey, Welcome to working on Octavia!
I'm not sure I fully understand your proposals, but I can give my
thoughts/opinion on the challenge for Active/Active.
In general I agree with Stephen.
The intention of using TaskFlow is to facilitate code reuse across
similar but different code flows.
Hi Matt,
We are aware of the issue and have cherry picked patches pending
review by the neutron stable team:
https://review.openstack.org/#/q/openstack/octavia+status:open+branch:stable/mitaka
https://review.openstack.org/#/q/openstack/octavia+status:open+branch:stable/liberty
Michael
On Mon, Ju
I have not seen this. Can you please open a bug in launchpad and
include your o-cw.log and /var/log/upstart/amphora-agent.log from the
affected amphora?
Thank you,
Michael
On Tue, Jun 7, 2016 at 5:09 AM, Babu Shanmugam wrote:
> Hi,
> I am using octavia deployed using devstack. I am *never* abl
Just a reminder, we have a proposed mid-cycle meeting set for the week
of August 22nd in San Antonio.
If you would like to attend and have not yet signed up, please add
your name to the list on our etherpad:
https://etherpad.openstack.org/p/lbaas-octavia-newton-midcycle
Thank you,
Michael
_
Hi Ihar,
I think the biggest issue I see with the FIP and new amphora approach
is the the persistence tables would be lost. This is not an issue in
the Active/Standby scenario, but would be in the failover scenario.
Michael
On Wed, Jun 29, 2016 at 9:14 AM, Ihar Hrachyshka wrote:
> Hi all,
>
>
I would like to nominate Bharath Munirajulu (bharathm) as a OpenStack
Octavia core reviewer.
His contributions [1] are in line with other cores and he has been an
active member of our community. I have been impressed with the
insight and quality of his reviews.
Current Octavia cores, please vote
; Subject: Re: [openstack-dev] [lbaas] [octavia] Proposing Bharath
>> > Munirajulu as Octavia Core
>> >
>> > +1
>> >
>> > On Wed, 2016-03-30 at 13:56 -0700, Michael Johnson wrote:
>> >> I would like to nominate Bharath Munirajulu (bharathm) as
Armando,
Is there any way we can move the "Neutron: Development track: future
of *-aas projects" session? I overlaps with the LBaaS talk:
https://www.openstack.org/summit/austin-2016/summit-schedule/events/6893?goback=1
Michael
On Mon, Apr 11, 2016 at 9:56 PM, Armando M. wrote:
> Hi folks,
>
Since most of us will be attending the summit next week I am canceling
the Octavia IRC meeting on April 27th.
Michael
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.op
+1
Michael
On Monday, April 25, 2016, Ananth wrote:
> Would be great to connect..
> +1
>
> Regards
> Ananth
> Cloud & Network Solutions
> Cisco Systems
>
> On Mon, Apr 25, 2016 at 2:13 PM, Zhipeng Huang > wrote:
>
>> +1
>>
>> On Mon, Apr 25, 2016 at 1:07 PM, Kyle Mestery > > wrote:
>>
>>> OK,
Hi Lingxian,
For #1, we create a nova flavor for the amphora in the devstack
plugin. It is currently:
nova flavor-create --is-public False m1.amphora
${OCTAVIA_AMP_FLAVOR_ID} 1024 2 1
I have not done extensive testing with these settings to optimize it.
We were shooting for the minimum viable co
Just to chime in from an Octavia perspective as we were added to the
subject.
We have not had issues with DIB. There are things about the elements that
could be improved, and we have been working on those over time. Currently
we build the image with DIB for our scenario test runs and devstack.
We are taking a break from meetings until the new year. Our regular
Octavia meetings will resume January 6th.
Michael
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.op
I feel that the subnet should be mandatory as there are too many
ambiguity issues due to overlapping subnets and multiple routes.
In the case of an IP being outside of the tenant networks, the user
would specify an external network that has the appropriate routes. We
cannot always assume which ten
Octavia Team,
I would like to nominate Stephen Balukoff as a core reviewer for the
OpenStack Octavia project. His contributions[1] are in line with
other cores and he has been an active member of our community.
Octavia cores please vote by replying to this e-mail.
Michael
[1] http://stackalyti
ndon.lo...@rackspace.com>> wrote:
>>
>> +1
>>
>>> On Fri, 2016-02-05 at 01:07 +, Adam Harwell wrote:
>>> +1 from me!
>>>
>>> From: Michael Johnson mailto:johnso...@gmail.com>>
>>> Sent: Thur
1. Octavia can run under it's own account with the required roles
added to that account.
2. Currently the process would be to update the amphora image in
glance and trigger a failover of the amphora.
3. It is required. It is a private network between the Octavia
controller and the amphora. We wou
Yes, I will take it. I'm guessing it will be very short.
Michael
On Sun, Feb 7, 2016 at 9:08 AM, Hayes, Graham wrote:
> Hi,
>
> As I am at the Designate mid cycle this week I will not make the IRC
> meeting this week.
>
> Can dougwig / johnsom take over, or will we skip this week?
>
> Thanks,
>
Hello OpenStack,
We are starting up a project for Global Server Load Balancing (GSLB).
The Wiki page is here: https://wiki.openstack.org/wiki/GSLB
We are soliciting for project driver nominations for the initial team.
Drivers are expected to file, maintain, prioritize, and target
blueprints and
I would like to share my +1 about Michael.
>
> Cheers,
>
> Edgar
>
>
>
>
> On 9/16/15, 3:33 PM, "Doug Wiegley" wrote:
>
>>Hi all,
>>
>>As the Lieutenant of the advanced services, I nominate Michael Johnson to
>> be a member of the ne
I really do not want to see tempest code copied into the Octavia
repository. We cannot keep them in sync and maintain the tests that
way. It has been a recurring problem with neutron-lbaas that we are
trying to get back out of[1], so I really do not want to repeat that
with Octavia.
[1] https://
This is in reference to bug:
https://bugs.launchpad.net/openstack-manuals/+bug/1552797
The liberty documentation set has the octavia.conf section:
http://docs.openstack.org/liberty/config-reference/content/networking-plugin-lbaas.html
The current Mitaka documentation does not have an octavia.con
Does Oslo provide a consistent hashing library?
I think a number of projects (swift [1] and ironic [2] for example)
are using various implementations and Octavia may need to start using
consistent hashing soon.
[1] http://docs.openstack.org/developer/swift/ring.html
[2]
https://blueprints.launch
Hi Santhosh,
The correct path to the git repo is:
http://git.openstack.org/cgit/openstack/openstack-ansible-os_octavia/
Though at this point the code has not merged, so you will need to pull from the
patch if you want to try it out:
https://review.openstack.org/#/c/417210/
Michael
Some of the Octavia team attended the first OpenStack Project Team Gathering
(PTG) held in Atlanta the week of February 27th. Below is a summary of the
notes we kept in the Octavia etherpad here:
https://etherpad.openstack.org/p/octavia-ptg-pike
This e-mail details discussions we had with the cro
Some of the Octavia team attended the first OpenStack Project Team Gathering
(PTG) held in Atlanta the week of February 27th. Below is a summary of the
notes we kept in the Octavia etherpad here:
https://etherpad.openstack.org/p/octavia-ptg-pike
This e-mail details discussions we had about Octavi
Hi Saverio,
I think the confusion is coming from neutron/neutron-lbaas/octavia.
Neutron-lbaas, prior to the Ocata series was a sub-project of neutron and as
such has it's own release notes:
https://docs.openstack.org/releasenotes/neutron-lbaas/
As of Ocata, neutron-lbaas is part of the Octavia p
On 07/03/17 17:33, Michael Johnson wrote:
> Hi Saverio,
>
> I think the confusion is coming from neutron/neutron-lbaas/octavia.
>
> Neutron-lbaas, prior to the Ocata series was a sub-project of neutron
> and as such has it's own release notes:
> https://docs.open
Yes, folks have recently deployed the dashboard with success. I think you
had that discussion on the IRC channel, so I won't repeat it here.
Please note, the neutron-lbaas-dashboard does not support LBaaS v1, you must
have LBaaS v2 deployed for the neutron-lbaas-dashboard to work. If you are
try
Hi Syed,
To my knowledge the LBaaS team did not create any upgrade plan or tools to move
load balancers from V1 to V2. The data model is significantly different (and
better) with V2 and I suspect that caused some challenges.
I know there was a, as-is, database conversion script contributed
@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from
LBaaS v1 to v2
On 10/03/17 17:49, Michael Johnson wrote:
> Yes, folks have recently deployed the dashboard with success. I think
> you had that discussion on the IRC channel, so I won't repeat it here.
, Michael Johnson wrote:
> Yes, folks have recently deployed the dashboard with success. I think
> you had that discussion on the IRC channel, so I won't repeat it here.
>
> Please note, the neutron-lbaas-dashboard does not support LBaaS v1,
> you must have LBaaS v2 deployed f
Yes, as previously announced, we deferred development of the OpenStack
Client (OSC) until Pike.
Work has started on the OSC plugin for Octavia and we expect it to be
available in Pike.
Neutron CLI is deprecated which means it will go away in the future, but is
still available for use and is still
Hi Saverio,
First, please note, in the future the best tag for load balancing is
[octavia] as it is no longer part of the neutron project.
I am sorry that you are so anxious and confused about the current state of
load balancing for OpenStack. Let me clarify a few things:
1. LBaaSv2 is not goin
I have a few comments on the updated Project Navigator.
1. I hope this is mostly automated at this point? The current content for
Project Navigator is very out of date (Mitaka?) and folks have asked why
projects are not listed there.
2. What is the policy around the tags? For octa
Hi Andrey,
As we discussed on IRC, the listeners in LBaaS v2 allow you to update the
barbican container IDs. This will start the certificate update process on the
load balancers with the new content from barbican.
The neutron client, as you noted, does not appear to have this capability,
Thank you ChangBo, I have resolved the issues in octavia in this patch:
https://review.openstack.org/457356 up for review.
Michael
From: ChangBo Guo [mailto:glongw...@gmail.com]
Sent: Sunday, April 16, 2017 12:32 AM
To: OpenStack Development Mailing List (not for usage questions)
Subjec
Hi Robin,
The Octavia project (shameless plug:
https://docs.openstack.org/developer/octavia/) relies on TaskFlow for the core
workflow. For us, the TaskFlow project is very stable.
Michael
From: Robin De-Lillo [mailto:rdeli...@rodeofx.com]
Sent: Wednesday, April 19, 2017 11:14 AM
To
Hmm, I never received an email to vote for the name, just for the TC election.
Michael
-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com]
Sent: Friday, April 21, 2017 5:12 AM
To: OpenStack Development Mailing List (not for usage questions)
; Openstack Users
Subject:
Hi Octavia team,
At today's weekly LBaaS/Octavia IRC meeting we decided to cancel the next
three meetings due to the OpenStack summit, other conflicts, and vacations.
We just won't have quorum these weeks.
Safe travels for those attending the OpenStack summit and we will meet again
5/31/17.
Mic
Hi Alex,
As you know I am a strong proponent of moving the docs into the project team
repositories [1].
Personally I am in favor of pulling the Band-Aids off and doing option 1. I
think centralizing the documentation under one tree and consolidating the build
into one job has benefits.
Hello Yipei,
You are on the track to debug this.
When you are logged into the amphora, please check the following logs to see
what the amphora-agent error is:
/var/log/amphora-agent.log
And
/var/log/syslog
One of those two logs will have the error information.
Michael
Fro
Hi Yipei,
I have meant to add this as a config option, but in the interim you can do the
following to disable the automatic cleanup by disabling the revert flow in
taskflow:
octavia/common/base_taskflow.py line 37 add “never_resolve=True,” to the engine
load parameters.
Michael
F
As discussed in today's octavia IRC meeting we are changing the meeting time
and IRC channel for the weekly meeting.
Starting next week we will now be meeting at 17:00 UTC on Wednesdays in
channel #openstack-meeting.
This is the same day, just three hours earlier to accommodate team members
in d
plugin for Octavia. I also want to
maintain our priority on providing onboarding support for new contributors
to
get involved with Octavia.
Thank you for your support of Octavia during Pike and your consideration for
Queens,
Michael Johnson (johnsom
Hi OpenStack developers,
I was wondering what is the current status of the python-openstacksdk
project. The Octavia team has posted some patches implementing our new
Octavia v2 API [1] in the SDK, but we have not had any reviews. I have also
asked some questions in #openstack-sdks with no respo
Awesome Monty. This is a great proposal. I have no preference on which way
these merge, but see huge value in straightening this out. Frankly I think
some of the tempest plugin work could benefit from having an official and well
maintained SDK as well.
So, I am in favor of getting the ball r
Hi,
Flavors are intended to be setup by the operator/admin only. They
capture details of the load balancer offering and any local specific
configuration. The intent here is the flavor options and descriptions
will be visible to end users, but creation/modification would require
an admin role. E
FYI, code in Octavia that checks for the extensions you could borrow:
https://github.com/openstack/octavia/blob/master/octavia/network/drivers/neutron/base.py#L49
On Mon, Sep 4, 2017 at 11:18 PM, Gary Kotton wrote:
>
>
> On 9/4/17, 3:47 PM, "Stephen Finucane" wrote:
>
> On Mon, 2017-09-04 at
Yes, you can redirect to a pool. Multiple pools can be created under
the load balancer object and then referenced from the L7 Policy.
This example shows a load balancer with a redirect to pool L7 policy:
https://docs.openstack.org/octavia/latest/user/guides/l7-cookbook.html#send-requests-starting
Hi Liping,
FYI, Neutron LBaaS is no longer part of Neutron. Load balancing has
been consolidated under the Octavia project. I have added that tag to
the subject.
We currently do not have plans to add HA capabilities to the haproxy
namespace driver. The intention behind building the octavia drive
+1 Miguel, thanks for putting this together!
Michael
On Wed, Sep 13, 2017 at 9:09 PM, Akihiro Motoki wrote:
> +1 thanks for organizing this
>
> 2017-09-12 17:23 GMT-06:00 Miguel Lavalle :
>> Dear Neutrinos,
>>
>> Our social event will take place on Thursday September 12th at 7:30pm. The
>> venue
A recent extreme example:
https://review.openstack.org/#/c/494981/1/specs/version0.8/active_passive_loadbalancer.rst
I would love to have a boilerplate statement I can use as a template
for things like this. I feel bad -1/-2 these as I want to encourage
involvement, but they are a drain on the sy
Hi Yipei,
I just tried to reproduce this and was not successful.
I setup a tenant network, added a web server to it, created a
loadbalancer VIP on the tenant network, added the webserver as a
member on the load balancer. I can curl from the tenant network
qdhcp- netns without issue.
Are you run
Hi Yipei,
I ran this scenario today using octavia and had success. I'm not sure
what could be different.
I see you are using neutron-lbaas. I will build a devstack with
neutron-lbaas enabled and try that, but I can't think of what would
impact this test case by going through the neutron-lbaas pa
Hi Yipei,
Even running through neutron-lbaas I get the same successful test.
Just to double check, you are using the Octavia driver?
stack@devstackpy27-2:~$ sudo ip netns exec
qdhcp-4bcefe3e-038f-4a77-af4f-a560b6316a7a curl 172.21.1.16
Welcome to 172.21.1.17 connection 3
Michael
On Thu, Sep 28,
Hi Mihaela,
The old neutron-lbaas haproxy namespace driver does not have L7
support. Only the Octavia driver and some vendor provider drivers have
L7 support.
Michael
On Tue, Oct 3, 2017 at 11:35 PM, Pawel Suder wrote:
> Hello,
>
>
> It seems that HaproxyOnHostPluginDriver from
> https://githu
Hello OpenStack folks,
I would like to propose Nir Magnezi as a core reviewer on the Octavia project.
He has been an active contributor to the Octavia projects for a few
releases and has been providing solid patch review comments. His
review stats are also in line with other core reviewers.
Octa
Hello OpenStack load balancing folks,
Summary: Octavia/neutron-lbaas weekly IRC meeting will be 20:00 UTC on
Wednesdays in the #openstack-lbaas channel.
As discussed at the last two weekly meetings[1], we are moving our
meeting time back to the previous time slot. Unfortunately the
earlier time
3:51 AM, German Eichberger wrote:
>> > +1
>> >
>> > Welcome Nir, well earned.
>> >
>> > German
>> >
>> > On 10/4/17, 4:28 PM, "Michael Johnson" wrote:
>> >
>> > Hello OpenStack folks,
>> >
>>
Hi Mihaela,
Welcome to the Octavia club!
In an Ocata release you are correct that there is no API way to
identify amphora related to a given load balancer.
In the queens release we have introduced a new administrator API for
amphora that provides the functionality you are looking for:
https://de
I think we helped you get going again in the IRC channel. Please ping
us again in the IRC channel if you need more assistance.
Michael
On Thu, Nov 2, 2017 at 4:42 AM, Kim-Norman Sahm
wrote:
> Hi,
>
> after a rabbitmq problem octavia has removed all amphora instances.
> the loadbalancers are in
Hi Yipei,
I need some more information to help you out. Can you provide the following?
1. What version of Octavia you are using.
2. "openstack server list" output for the amphora.
3. "openstack loadbalancer show" for the load balancer.
4. "openstack loadbalancer listener show" for the listener.
hael
On Wed, Nov 8, 2017 at 2:07 AM, wrote:
> I am also interested how to fix this. If you can describe shortly the
> procedure.
>
> Thanks,
> Mihaela
>
> -Original Message-
> From: Michael Johnson [mailto:johnso...@gmail.com]
> Sent: Monday, November 06, 2017 6
Hi Yipei,
I see a few things that are odd:
stack@devstack-1:/opt/stack/octavia$ sudo ip netns exec
qdhcp-310fea4b-36ae-4617-b499-5936e8eda842 curl 10.0.1.4
curl: (7) Failed to connect to 10.0.1.4 port 80: Connection timed out
This means that the connection is not working between curl and the
HAPr
The actual gateway address does not matter to Octavia/amphora. It
gets that value from DHCP or from neutron if a static address was
assigned from neutron.
My concern is that the subnet gateway 10.0.1.10 does not match the
gateway address DHCP gave us 10.0.1.1.
Technically, since the two addresses
The Octavia project has a few graphviz diagrams in it's documentation.
You can reference that project to see how it is done.
That said, we have seen a decline in the stability of the graphviz
code over the last few years (cylinder object disappeared, graphviz
dot crashes on Ubuntu, etc.) that we ha
Yipei,
I am struggling to follow some of the details as I see different information:
+---+-+
| Field | Value |
+---+-+
| alloca
Yipei,
Yeah, we have clearly identified the problem. Those two default route
lines should not be different. See my devstack:
sudo: unable to resolve host amphora-20a717b4-eb97-4b5c-a11a-0633fe61f135
default via 10.0.0.1 dev eth1 table 1 onlink
default via 10.0.0.1 dev eth1 onlink
So the issue
Is there a template for this? I wouldn't want to have 12 different
formatting styles for the page (Yes, I'm looking at Amrith and the
blinking red text. grin)
Michael
On Tue, Nov 21, 2017 at 6:28 AM, Amrith Kumar wrote:
> Very cool, thanks Sean!
>
>
> -amrith
>
>
> On Mon, Nov 20, 2017 at 12:1
Hello Volodymyr,
You have two options:
1. When you create your VIP, simply put in your external network as
the vip-subnet-id or vip-network-id. This will allocate a public IP to
the VIP.
2. Use neutron to assign a floating IP to the VIP address of the load
balancer. From your example, let's say t
Hi Volodymyr,
This is a known issue with the neutron (neutron-lbaas) database
getting out of sync and/or not properly handling driver errors.
This is one reason we are moving to deprecate neutron-lbaas. If you
can, we recommend you move to exclusively using Octavia without
neutron-lbaas.
The fun
I think the steps listed in that document seem reasonable. There are
a few typos here and there, but in general it looks ok.
Michael
On Mon, Dec 4, 2017 at 10:14 PM, Yipei Niu wrote:
> Hi, all
>
> Tricircle team has already enabled LBaaS with tricircle. Here is the guide
> https://github.com/op
Hi Kim,
Sorry you are having trouble after your upgrade.
From the log it appears that the neutron-lbaas Octavia driver is
unable to reach keystone to request an auth token.
Please make sure there is a [service_auth] section configured in your
neutron_lbaas.conf/neutron.conf file(s).
An example:
Hi everyone,
With many member of the Octavia team taking an end-of-year vacation we
are cancelling the next weekly meeting on 12/27/2017. We will resume
our regular weekly meetings on 1/3/18.
Michael
__
OpenStack Developmen
This sounds great Ihar!
Let us know when we should make the changes to the neutron-lbaas projects.
Michael
On Wed, Jan 17, 2018 at 11:26 AM, Ihar Hrachyshka wrote:
> Hi all,
>
> tl;dr I propose to switch to lib/neutron devstack library in Queens. I
> ask for buy-in to the plan from release and
Should be no issues with python-octaviaclient, we do not use the short options.
Michael
On Fri, Jan 26, 2018 at 1:03 PM, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2018-01-18 10:15:16 -0500:
>> We've been working this week to resolve an issue between cliff and
>> barbicancli
I support putting infrastructure in place to allow the project
documentation to be in the project's repository. We had problems in
the Mitaka release with documentation getting deleted without the
project team knowing it was happening until users were asking us where
the documentation was located.
Brandon,
You are correct, TLS re-encryption has not yet been implemented. It
is still a feature we would like to have, but no one has done the
coding yet.
Michael
On Fri, Jul 22, 2016 at 8:21 PM, Brandon Logan
wrote:
> I do not believe it is in it and I don't know if anyone is working on
> it
Hi Akshay,
For 80 to 443 redirection, you can accomplish this using the new L7
rules capability. You would setup a listener on port 80 that has a
redirect rule to the 443 URL.
On the barbican question, if you are using the octavia driver, you
will need to set the required settings in the octavia
Miguel,
Thank you for your work here. I would support an effort to setup a
multi-node gate job.
Michael
On Mon, Aug 8, 2016 at 5:04 AM, Miguel Angel Ajo Pelayo
wrote:
> Recently, I sent a series of patches [1] to make it easier for
> developers to deploy a multi node octavia controller with
>
re scenario, how should i figure out where
> things went wrong or where the packet is dropped. Is it possible to login to
> the amphora vm?
>
> Thanks
> Akshay
>
> On Sat, Jul 30, 2016 at 11:45 PM, Michael Johnson
> wrote:
>>
>> Hi Akshay,
>>
>> For
Hi Koteswara,
This is not normal behavior, but there was a reported bug that was recent fixed.
Please see: https://bugs.launchpad.net/octavia/+bug/1577963
If you are still seeing an issue after using a patched version, please
open a bug for the issue.
Michael
On Mon, Aug 22, 2016 at 6:10 AM, K
27;
Thank you for your support and patience during this transition,
Michael Johnson
Octavia PTL
[1]
http://specs.openstack.org/openstack/neutron-specs/specs/newton/neutron-stadium.html
[2]
http://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html
Hi Mihaela,
The polling logic that the neutron-lbaas octavia driver uses to update
the neutron database is as follows:
Once a Create/Update/Delete action is executed against a load balancer
using the Octavia driver a polling thread is created.
On every request_poll_interval the thread queries the
and additional operator
tooling. I plan to continue working on improving our documentation,
specifically with detailed installation, high availability, and neutron-lbaas
migration guides.
Thank you for your support of Octavia during Queens and your consideration for
Rocky,
Michael Johnson (johnsom
I am interested in contributing to this discussion.
Michael
On Wed, Feb 7, 2018 at 3:42 AM, Thierry Carrez wrote:
> Hi everyone,
>
> I was wondering if anyone would be interested in brainstorming the
> question of how to better align our release cycle and stable branch
> maintenance with the Op
Hi Kendall,
Can you put Octavia down for 2:10 on Thursday after neutron?
Thanks,
Michael
On Wed, Feb 7, 2018 at 9:15 PM, Kendall Nelson wrote:
> Hello PTLs and SIG Chairs!
>
> So here's the deal, we have 50 spots that are first come, first served. We
> have slots available before and after lunc
Hi Gary,
All of the answers to your questions are on the FAQ linked in the announcement.
1: If you are already using the Octavia driver or the neutron-lbaas
proxy driver, you are already migrated. We will provide a port
migration tool to migrate the neutron port ownership from
neutron-lbaas if ne
FYI, Octavia has started to use the new devstack-tempest parent here:
https://review.openstack.org/#/c/543034/17/zuul.d/jobs.yaml
There is a lot of work still left to do on our tempest-plugin but we
are making progress.
Thanks for the communication out!
Michael
On Tue, Feb 20, 2018 at 1:22 PM,
Hi Vadim,
Yes, currently the only network driver available for Octavia (called
allowed-address-pairs) uses the allowed-address-pairs feature of
neutron. This allows active/standby and VIP migration during failover
situations.
If you need to run without that feature, an non-allowed-address-pairs
d
Hello Octavia community,
I would like to propose Jacky Hu (dayou) as a core reviewer on the
Octavia project.
Jacky has done amazing work on Octavia dashboard, specifically
updating the look and feel of our details pages to be more user
friendly. Recently he has contributed support for L7 policie
1 - 100 of 178 matches
Mail list logo
