[openstack-dev] [Octavia] Proposal to support multiple listeners on one HAProxy instance

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

Re: [openstack-dev] [Octavia] Octavia VM image design

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 open

[openstack-dev] [GSLB][LBaaS] Call for GSLB project driver nominations

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

Re: [openstack-dev] [Kosmos] Meeting tomorrow

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:

Re: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for neutron-lbaas core team

so my +1 is more like a +2 > > On Sep 17, 2015 12:59 PM, Edgar Magana <edgar.mag...@workday.com> wrote: > Not a core but I would like to share my +1 about Michael. > > Cheers, > > Edgar > > > > > On 9/16/15, 3:33 PM, "Doug Wiegley" <doug...@parksidesoftw

[openstack-dev] [lbaas] [octavia] Octavia meetings will resume January 6th

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:

Re: [openstack-dev] [lbaas] [octavia] Proposing Bertrand Lallau as Octavia Core

+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

Re: [openstack-dev] [octavia] enabling new topologies

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.

Re: [openstack-dev] [octavia] is l7 rule using routed L3 connectivity

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! > >

Re: [openstack-dev] [Octavia] Unable to plug VIP

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

Re: [openstack-dev] [octavia][neutron] Fwd: [Openstack-stable-maint] Stable check of openstack/octavia failed

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,

[openstack-dev] [Octavia] [lbaas] Mid-Cycle proposed for the week of August 22nd

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

Re: [openstack-dev] [lbaas][octavia] Security/networking questions

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

Re: [openstack-dev] [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core

oftware.com<mailto:doug...@parksidesoftware.com>> wrote: > +1 > > Doug > > >> On Feb 4, 2016, at 7:06 PM, Brandon Logan >> <brandon.lo...@rackspace.com<mailto:brandon.lo...@rackspace.com>> wrote: >> >> +1 >> >>> On Fri, 2016

[openstack-dev] [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core

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]

Re: [openstack-dev] [kosmos] IRC Meeting this week

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

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Should subnet be optional on member create?

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

Re: [openstack-dev] [Octavia] [Tempest] Tempest tests using tempest-plugin

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]

[openstack-dev] [lbaas] [octavia] Proposing Bharath Munirajulu as Octavia Core

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

Re: [openstack-dev] [Neutron] Newton Design summit schedule - Draft

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.

Re: [openstack-dev] [lbaas] [octavia] Proposing Bharath Munirajulu as Octavia Core

...@rackspace.com> >> > Sent: Thursday, March 31, 2016 8:04 AM >> > To: openstack-dev@lists.openstack.org >> > Subject: Re: [openstack-dev] [lbaas] [octavia] Proposing Bharath >> > Munirajulu as Octavia Core >> > >> > +1 >> > >&g

Re: [openstack-dev] [oslo][all] What would you like changed/fixed/new in oslo??

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]

[openstack-dev] [docs] Octavia configuration options were deleted but needed for Mitaka

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

[openstack-dev] [lbaas][octavia] No Octavia IRC meeting 4/27/16

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:

Re: [openstack-dev] [neutron] Social at the summit

+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

Re: [openstack-dev] [Magnum][Octavia] Need help for LBaaS v2

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

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

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.

Re: [openstack-dev] [octavia] amphora flavour and load balancer topology

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

Re: [openstack-dev] [octavia] ssl re-encryption in octavia

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

Re: [openstack-dev] [octavia]redirection and barbican config

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

Re: [openstack-dev] The future of OpenStack documentation

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

Re: [openstack-dev] [octavia]redirection and barbican config

> working. But for a similar future 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 <johnso...@gmail

Re: [openstack-dev] [octavia] Multi-node controller testing

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

Re: [openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

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

Re: [openstack-dev] [ocatvia]Newton Octavia lbaas creation error

ystone on http://127.0.0.1:5000 Maybe there is a bad security group or keystone isn’t running? Michael From: Santhosh Fernandes [mailto:santhosh.fernan...@gmail.com] Sent: Sunday, January 22, 2017 10:48 AM To: openstack-dev@lists.openstack.org; Michael Johnson <johnso...@gmail.com

Re: [openstack-dev] [octavia] Nominating German Eichberger for Octavia core reviewer

community. Welcome! On Fri, Jan 20, 2017 at 1:26 PM, Brandon Logan <brandon.lo...@rackspace.com <mailto:brandon.lo...@rackspace.com> > wrote: +1, yes welcome back German. On Fri, 2017-01-20 at 09:41 -0800, Michael Johnson wrote: > Hello Octavia Cores, > > I would like

[openstack-dev] [octavia] PTL candidacy for Pike series

Hello Octavia folks, I wanted to let you know that I am running for the PTL position again for Pike. My candidacy statement is available here: https://git.openstack.org/cgit/openstack/election/plain/candidates/pike/Octa via/johnsom.txt Thank you for your consideration, Michael

[openstack-dev] [octavia] Reminder Boston Summit voting ends next week

Voting for presentations closes next Tuesday/Wednesday (TUESDAY, FEBRUARY 21 AT 11:59PM PST / WEDNESDAY, FEBRUARY 22 AT 6:59AM UTC). If you have not already voted for sessions of interest, please do here: https://www.openstack.org/summit/boston-2017/vote-for-speakers Somehow this announcement

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

+1 Thanks for setting this up, Michael From: Kevin Benton [mailto:ke...@benton.pub] Sent: Friday, February 17, 2017 11:19 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday Hi all, I'm organizing a Neutron

Re: [openstack-dev] [octavia][sdk] service name for octavia

Funny, I had posted a patch to fix the devstack plugin earlier the same day you sent this e-mail. https://review.openstack.org/#/c/433817/ I also found that it was using "octavia" for the service type and wanted to fix it. I had picked "loadbalancing" but I am fine with "load-balancing" as

[openstack-dev] [octavia] Nominating German Eichberger for Octavia core reviewer

Hello Octavia Cores, I would like to nominate German Eichberger (xgerman) for reinstatement as an Octavia core reviewer. German was previously a core reviewer for Octavia and neutron-lbaas as well as a former co-PTL for Octavia. Work dynamics required him to step away from the project for a

Re: [openstack-dev] [LBaaS][Octavia] Health manager does not create standby amphora VM

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,

Re: [openstack-dev] [ansible]Octavia ansible script

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

Re: [openstack-dev] [neutron][LBaaS v2]Quota Update for LBaaS v2 Members

Hi Reedip, As you noted with the linked bug, we have noticed some inconsistencies in the neutron-lbaas quota implementation as we are working on implementing quotas native in the Octavia API. The neutron-lbaas code does support a quota for members, but as you have observed I don't see it in the

Re: [openstack-dev] [neutron][lbaas][heat][octavia] Heat engine doesn't detect lbaas listener failures

Hi folks, Yes, I think there are some discrepancies around the provisioning status being exposed. Currently I think the only way to get visibility to those is through the status api: http://developer.openstack.org/api-ref/networking/v2/#show-load-balancer-status-tree Which, frankly, I think

[openstack-dev] [lbaas] [octavia] Proposing Lubosz Kosnik (diltram) as Octavia Core

Greetings Octavia and developer mailing list folks, I propose that we add Lubosz Kosnik (diltram) as an OpenStack Octavia core reviewer. His contributions [1] are in line with other cores and he has been an active member of our community. He regularly attends our weekly meetings, contributes

Re: [openstack-dev] [neutron] [neutron-lbaas][octavia] Error in installing octavia via devstack on ubuntu stable/mitaka

Nope, we included these changes in Newton. Michael On Tue, Nov 1, 2016 at 4:11 AM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > Michael Johnson <johnso...@gmail.com> wrote: > >> Hi Wanjing, >> >> I responded to you in IRC but you may have logged off

Re: [openstack-dev] [Neutron][neutron-lbaas][octavia] Not be able to ping loadbalancer ip

Hi Wanjing, You are not seeing the network interfaces for the VIP and member networks because they are inside a network namespace for security reasons. You can see these by issuing "sudo ip netns exec amphora-haproxy ifconfig -a". I'm not sure what version of octavia and neutron you are using,

Re: [openstack-dev] [openstack-ansible][octavia] Spec: Deploy Octavia with OpenStack-Ansible

Thank you Major! I will try to get a pass on this early in the week. I agree with you that taking this one step at a time is probably best. TLS offloading (requiring barbican) is a common use case, but we can work on that as a follow up. Michael On Wed, Nov 2, 2016 at 6:42 AM, Major Hayden

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

t; cannot even indicate to our community/consumers what to use/expect. > Thanks > Gary > > On 11/8/16, 1:36 AM, "Michael Johnson" <johnso...@gmail.com> wrote: > > Ocata LBaaS retrospective and next steps recap >

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

s what to use/expect. >> Thanks >> Gary > > > http://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html > >> >> >> On 11/8/16, 1:36 AM, "Michael Johnson" <johnso...@gmail.com> wrote: >> >&

[openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

Ocata LBaaS retrospective and next steps recap -- This session lightly touched on the work in the newton cycle, but primarily focused on planning for the Ocata release and the LBaaS spin out of neutron and merge into the octavia

Re: [openstack-dev] [Neutron][neutron-lbaas][octavia] Not be able to ping loadbalancer ip

vm launched per loadbalancer. > And did anybody benchmark this octtavia against vender box? > > Regards! > > Wanjing > > On 11/7/16, 10:02 AM, "Michael Johnson" <johnso...@gmail.com> wrote: > >>Hi Wanjing, >> >>You are not seeing the network inter

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

n? > Sorry for the pessimism but I feel that things are very unclear and that we > cannot even indicate to our community/consumers what to use/expect. > Thanks > Gary > > > > http://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html > > &

[openstack-dev] [lbaas] [octavia] Next LBaaS/Octavia meeting will be November 9th

Hi OpenStack Devs, Since a large number of team members are attending the OpenStack Summit, we have decided to cancel the next two LBaaS/Octavia IRC meetings. We will resume our regular meetings November 9th. Michael __

Re: [openstack-dev] [lbaas] [octavia] Proposing Lubosz Kosnik (diltram) as Octavia Core

That is quorum from the cores, welcome Lubosz! Michael On Wed, Oct 12, 2016 at 1:26 PM, Doug Wiegley <doug...@parksidesoftware.com> wrote: > +1 > >> On Oct 10, 2016, at 3:40 PM, Brandon Logan <brandon.lo...@rackspace.com> >> wrote: >> >> +1 >&g

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

+1 On Fri, Oct 14, 2016 at 11:30 AM, Miguel Lavalle wrote: > Dear Neutrinos, > > I am organizing a social event for the team on Thursday 27th at 19:30. After > doing some Google research, I am proposing Raco de la Vila, which is located > in Poblenou:

Re: [openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

Hi Ganpat, FYI, we are on freenode IRC: #openstack-lbaas if you would like to chat interactively. So, I see the amp is expecting systemd, which probably means you are using a "master" version of diskimage-builder with a stable/newton version of Octavia. On November 2nd, they switched

Re: [openstack-dev] [neutron][lbaasv2][octavia] Not able to create loadbalancer

Hi Ganpat, Yes, as hzhao mentioned, this error means that the controller was unable to connect to the amphora over the management network. Please check that this section is properly setup: http://docs.openstack.org/developer/octavia/guides/dev-quick-start.html#load-balancer-network-configuration

Re: [openstack-dev] [neutron-lbaas][octavia] About playing Neutron LBaaS

Hi Yipei, A note, that you probably want to use the tags [neutron-lbaas] and [octavia] instead of [tricicle] to catch the LBaaS team attention. Since you are using the octavia driver, can you please include a link to your o-cw.log? This will tell us why the load balancer create failed. Also, I

Re: [openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

npat > > > > On Wed, Nov 16, 2016 at 10:20 PM, Michael Johnson <johnso...@gmail.com> > wrote: >> >> Hi Ganpat, >> >> FYI, we are on freenode IRC: #openstack-lbaas if you would like to >> chat interactively. >> >> So, I see the amp is

Re: [openstack-dev] [neutron-lbaas][octavia] About running Neutron LBaaS

Hi Yipei, That error means the controller worker process was not able to reach the amphora REST API. I am guessing this is the issue with diskimage-builder which we have patches up for, but not all of them have merged yet [1][2]. Try running my script:

Re: [openstack-dev] [LBaaS][Octavia] Pools are not deleted when running neutron lbaas-pool-delete

Hi Ravi, It's best to report these as new bugs in launchpad so that you can attach the full logs and we can track comments, etc. It is very odd that the neutron database went into Active. I would have expected it to be stuck in PENDING_UPDATE as well. To keep them in sync as best we can (until

Re: [openstack-dev] [neutron] [neutron-lbaas][octavia] Error in installing octavia via devstack on ubuntu stable/mitaka

Hi Wanjing, I responded to you in IRC but you may have logged off by the time I was able to respond. You are correct that this is an issue. We just this week noticed it. It was an oversight that is causing the amphora agent to clone the master branch amphora agent code instead of the

[openstack-dev] [octavia] Meeting time and cancellations

Hello Octavia folks! I wanted to remind folks to enter their timezone information in the etherpad to help us come up with a meeting time that works for everyone. Please do so here: https://etherpad.openstack.org/p/octavia-weekly-meeting-time At the octavia IRC meeting today we agreed to take a

Re: [openstack-dev] [octavia] Re: [infra][neutron] RADWARE CI voting permission in Neutron

I have talked with Izik on IRC and have started work to get this fixed. I will be setting up the octavia-ci group and fixing the permissions. Michael On Wed, Dec 14, 2016 at 12:49 AM, Ihar Hrachyshka wrote: > Izik Penso wrote: > >> Hi Neutron, Infra

Re: [openstack-dev] [ocatvia]Newton Octavia multinode setup

Hi Santhosh, Currently there is not an OpenStack Ansible (OSA) role for Octavia, but one is under development now. Keep an eye on the OSA project for updates. Michael From: Santhosh Fernandes [mailto:santhosh.fernan...@gmail.com] Sent: Thursday, January 12, 2017 10:13 PM To:

Re: [openstack-dev] [neutron] Confusion around the complexity

Actually we have a single call create for load balancers[1], so I think that addresses Josh's concern about complexity in the number of required calls. As for the complexity of the "concept" of a load balancer, I think we have improved that greatly with the LBaaSv2 API. That said, if there are

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Hi Flavio, These tags don't seem to be rendering/laying out well for octavia: https://github.com/openstack/octavia/blob/master/README.rst Any pointers to get this corrected or is this part of the backend rendering work you mentioned in the keystone message above? Michael On Wed, Nov 30, 2016

Re: [openstack-dev] [neutron][octavia] Neutron LBaaS governance change and Octavia to the big tent

There are a lot more than just those three (which are under packaging and not neutron btw). I will start working on moving/scrubbing the bugs today. Michael On Thu, Dec 1, 2016 at 7:30 AM, Brian Haley wrote: > On 12/01/2016 08:54 AM, Ihar Hrachyshka wrote: >> >> Armando M.

Re: [openstack-dev] [Neutron][neutron-lbaas][octavia] Not be able to ping loadbalancer ip

r using vrrp protocol, like using multicast vrrp IP? > 2) How do we install/configure the Octavia so that amphorae instances are > spun as containers or on bare metal? > > Thanks! > > Wanjing > > On 11/10/16, 5:12 PM, "Michael Johnson" <johnso...@gmail.c

Re: [openstack-dev] [neutron] Where will Neutron go in future?

Hi Zhi, LBaaSv2 as an API will live on. We are in the process of merging that API into the octavia repository to merge the two load balancing projects into one and remove our dependency on the neutron API process/endpoint. Functionally it is our goal to allow the LBaaSv2 API to continue to

Re: [openstack-dev] [neutron][lbaas] New extensions for HAProxy driver based LBaaSv2

Lubosz, I would word that very differently. We are not dropping LBaaSv2 support. It is not going away. I don't want there to be confusion on this point. We are however, moving/merging the API from neutron into Octavia. So, during this work the code will be transitioning repositories and you

Re: [openstack-dev] Project Navigator Updates - Feedback Request

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

Re: [openstack-dev] [lbaas][neutron] Is possible the lbaas commands are missing completely from openstack cli ?

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

Re: [openstack-dev] [neutron][lbaasv2] Migrate LBaaS instance

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

Re: [openstack-dev] [barbican] How to update cert in the secret

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

Re: [openstack-dev] OpenStack "R" Release Naming Preliminary Results

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)

Re: [openstack-dev] [Taskflow] Current state or the project ?

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

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

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

Re: [openstack-dev] [Neutron][LBaaS][heat] Removing LBaaS v1 - are weready?

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

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

, 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 for th

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

@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. >

[openstack-dev] [octavia] Octavia PTG summary - Octavia team discussions (e-mail 2 of 2)

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

[openstack-dev] [octavia] Octavia PTG summary - Cross-project teams (e-mail 1 of 2)

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

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

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

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

to V2 is explained ? thank you Saverio 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 ow

Re: [openstack-dev] [glance][ironic][octavia] oslo.config 4.0 will break projects' unit test

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)

[openstack-dev] [octavia] PTL nomination

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

[openstack-dev] [python-openstacksdk] Status of python-openstacksdk project

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

[openstack-dev] [octavia] Weekly meeting time and channel change

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

Re: [openstack-dev] [octavia] fail to plug vip to amphora

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

Re: [openstack-dev] [python-openstacksdk] Status of python-openstacksdk project

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

[openstack-dev] [LBaaS][octavia] Weekly IRC meeting cancelled for three weeks

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.

Re: [openstack-dev] [octavia] fail to plug vip to amphora

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

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

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.

Re: [openstack-dev] Garbage patches for simple typo fixes

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

Re: [openstack-dev] [Neutron] Denver Team Dinner

+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

[openstack-dev] [octavia] Proposing Nir Magnezi as Octavia core reviewer

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.

Re: [openstack-dev] Odp.: Odp.: [neutron][lbaasv2][agent implementation] L7 policy support

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

  1   2   >