Re: [openstack-dev] [nova] vendordata plugin for freeIPA host enrollment

I was thinking about this the other day... How do you de-register instances from freeipa when the instance is deleted? Is there a missing feature in vendordata there that you need? Michael On Fri, Nov 11, 2016 at 2:01 AM, Rob Crittenden <rcrit...@redhat.com> wrote: > Wanted to let you

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

r a five minute wait). There are still no logs in /var/log/ironic, and grepping for the node's uuid in /var/log/syslog returns zero log items. Your thoughts? Michael On Mon, Mar 5, 2018 at 7:04 AM, Mark Goddard <m...@stackhpc.com> wrote: > The ILO hardware type was also not loading be

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

with "ucs" as a hardware type. I've removed ucs entirely from that list and restarted conductor, but that didn't help. I suspect https://review.openstack.org/#/c/549318/3 is more subtle than that. I will patch in that change and see if I can get things to work after a redeploy. Michael

[openstack-dev] [Ironic][Bifrost] Manually enrolling a node

get this error: No valid host was found. Reason: No conductor service registered which supports driver agent_ipmitool. (HTTP 400) I can't see anything helpful in the logs. What driver should I be using for bifrost? agent_ipmitool seems to be enabled in ironic.conf. Thanks heaps, Michael

Re: [openstack-dev] [QA][all] Migration of Tempest / Grenade jobs to Zuul v3 native

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

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

://review.openstack.org/545874 Glance: https://review.openstack.org/545878 Glare: https://review.openstack.org/545883 On Mon, Feb 19, 2018 at 11:32 AM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Michael Bayer's message of 2018-02-19 10:55:52 -0500: >> wow that's heavy-

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

exclude` option which should solve the issue as > well. > > > > 2018-02-19 17:41 GMT+02:00 Michael Bayer <mba...@redhat.com>: >> >> On Mon, Feb 19, 2018 at 10:39 AM, Andrey Kurilin <andr.kuri...@gmail.com> >> wrote: >> > Can someone explain me th

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

wow that's heavy-handed. should that be in an oslo utility package of some kind ? On Mon, Feb 19, 2018 at 10:52 AM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Doug Hellmann's message of 2018-02-19 10:15:34 -0500: >> Excerpts from Michael Bayer's message of 2018

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

te against packaged dependencies, which fails because we don't package oslo_db.tests. > > > 2018-02-19 17:00 GMT+02:00 Michael Bayer <mba...@redhat.com>: >> >> Hi list - >> >> Apparently Cinder was misled by my deprecations within the >> oslo

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

On Mon, Feb 19, 2018 at 10:15 AM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500: >> Hi list - >> >> Apparently Cinder was misled by my deprecations within the >> oslo_db.sqlalchemy.test_base pa

[openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

Hi list - Apparently Cinder was misled by my deprecations within the oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and in https://review.openstack.org/#/c/522290/ the assumption was made that these should be imported from oslo_db.tests.sqlalchemy.This is an immense mistake

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was brief and primarily covered planning for the PTG. Here's a quick recap. We began by continuing to discuss the bug [8] that is the result of the Nova API not properly including caching information in the headers of its replies. Dmitry

Re: [openstack-dev] [neutron][lbaas][neutron-lbaas][octavia] Announcing the deprecation of neutron-lbaas and neutron-lbaas-dashboard

sessions, summits, and weekly meetings since then. The team vote that we are ready to announce was unanimous at our 1/24/2018 IRC meeting. I hope you will join us going forward to make this deprecation a success. We meet weekly on IRC and will be at the PTG. Michael On Mon, Feb 12, 2018 at 4:12 AM

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

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 <kennelso...@gmail.com> wrote: > Hello PTLs and SIG Chairs! > > So here's the deal, we have 50 spots that are first come, first served.

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

I am interested in contributing to this discussion. Michael On Wed, Feb 7, 2018 at 3:42 AM, Thierry Carrez <thie...@openstack.org> wrote: > Hi everyone, > > I was wondering if anyone would be interested in brainstorming the > question of how to better align our release cycle

[openstack-dev] [Octavia] Rocky Octavia PTL candidacy

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

Re: [openstack-dev] [neutron-lbaas][octavia]Octavia request poll interval not respected

thread is located here: https://github.com/openstack/neutron-lbaas/blob/stable/ocata/neutron_lbaas/drivers/octavia/driver.py#L66 Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-d

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was primarily focused on a request for guidance related to action endpoints and on planning topics for the upcoming PTG. Tommy Hu has sent an email to the developer list[7] describing how several types of actions are currently being handled

[openstack-dev] [neutron][lbaas][neutron-lbaas][octavia] Announcing the deprecation of neutron-lbaas and neutron-lbaas-dashboard

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 [3] https

Re: [openstack-dev] [all] [tc] Community Goals for Rocky -- privsep

be a supported mechanism for launching the privsep helpers. Michael On Fri, Jan 12, 2018 at 1:20 AM, Thierry Carrez <thie...@openstack.org> wrote: > Emilien Macchi wrote: > > [...] > > Thierry mentioned privsep migration (done in Nova and Zun). (action, > > ping mikal ab

Re: [openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

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 <d...@doughellmann.com> wrote: > Excerpts from Doug Hellmann's message of 2018-01-18 10:15:16 -0500: >> We've been working this week to resolve a

Re: [openstack-dev] [gate][devstack][neutron][qa][release] Switch to lib/neutron in gate

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 <ihrac...@redhat.com> wrote: > Hi all, > > tl;dr I propose to switch to lib/neutron devstack library in Queens.

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Happy new year to all and welcome to the first API-SIG meeting of 2018. As the SIG is ramping back up after the holiday break we had a few topics to kick off the new year and get the ball rolling. The SIG is working to complete our year in review report that

[openstack-dev] [octavia] Weekly IRC meeting 12/27/17 cancelled

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

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was relatively short and covered a few topics surrounding OpenStack SDKs and expanding the meeting times. On the topic of OpenStack SDKs, there is a proposal [7] being crafted for an SDK certification program. Our discussions mainly centered

Re: [openstack-dev] [all] Switching to longer development cycles

Do we continue to support the previous two releases as stable branches? Doesn't that mean we double the amount of time we need to keep older CI setups around? Isn't that already a pain point for the stable teams? Michael On Wed, Dec 13, 2017 at 8:17 AM, Thierry Carrez <thie...@openstack.

Re: [openstack-dev] [neutron][l2gw] Preventing DB out-of-sync

On Wed, Dec 6, 2017 at 3:46 AM, Peng Liu wrote: > Hi, > > During working on this patch[0], I encounter some DB out-of-sync problem. I > think maybe the design can be improved. Here is my thought, all comments are > welcome. see also https://review.openstack.org/#/c/490834/

Re: [openstack-dev] [octavia] cannot create loadbalancer on pike

: [service_auth] auth_version = 3 admin_password = password admin_user = admin admin_tenant_name = admin auth_url = http://172.21.21.134/identity/v3 Michael On Thu, Dec 7, 2017 at 3:02 AM, Kim-Norman Sahm <kis...@t-online.de> wrote: > after pupgrading ocata to pike i'm unable

Re: [openstack-dev] [octavia][tricircle] About enabling automatic installation of octavia with tricircle

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 <newy...@gmail.com> wrote: > Hi, all > > Tricircle team has already enabled LBaaS with tricircle. He

Re: [openstack-dev] [api] api-sig weekly meeting time change request

On 12/03/2017 10:26 PM, Gilles Dubreuil wrote: Hi, Could we please change the API SIG weekly meeting time from 16pm UTC to 19pm UTC  [1]? To give a chance for those down under to attend? hey Gilles, we have proposed adding another meeting time to make things easier for folks in the APAC

[openstack-dev] [Kolla][Kubernetes][Doomed] So close but yet so far

-18e1b83943fe" image="cirros (04053309-9a5c-4f25-8dda-2ff898f5a400)" key_name="mykey" name="demo1" progress="0" project_id="d0a64448a0d940b48c579f8fbb774827" properties="" status="BUILD" updated="2017-11-30T10:34:45Z"

Re: [openstack-dev] [octavia] openstack CLI output don't match neutron lbaas-* output

/configuration/configref.html#health_manager.event_streamer_driver This tells octavia to be aggressive at pushing status information back up to the neutron database getting it back in sync with reality. Michael On Wed, Nov 29, 2017 at 4:41 AM, Volodymyr Litovka <doka...@gmx.com> wrote: > Hi c

Re: [openstack-dev] [octavia] connection to external network

erformance as there is no NAT occurring like there is with a floating IP. Michael On Mon, Nov 27, 2017 at 1:30 AM, Volodymyr Litovka <doka...@gmx.com> wrote: > Hello colleagues, > > I think I'm missing something architectural in LBaaS / Octavia, thus asking > there - how to conne

Re: [openstack-dev] [ironic] Summary of ironic sessions from Sydney

than one machine off a volume at once? Michael On Wed, Nov 15, 2017 at 3:18 AM, Julia Kreger <juliaashleykre...@gmail.com> wrote: > Greetings ironic folk! > > Like many other teams, we had very few ironic contributors make it to > Sydney. As such, I wanted to go ahead and

Re: [openstack-dev] [release][ptl] Improving the process for release marketing

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 <amrith.ku...@gmail.com> wrote: > Very cool, thanks Sean! >

Re: [openstack-dev] [octavia] amphora fails to send request to members

he gateway for the subnet changed after the amphora was booted? Was the amphora live-migrated? Was there a host route on that subnet? Michael On Tue, Nov 14, 2017 at 12:29 AM, Yipei Niu <newy...@gmail.com> wrote: > Hi, Michael, > > Please ignore my last two mails. Sorry about that. &

Re: [openstack-dev] [octavia] amphora fails to send request to members

P, which would not impact local subnet traffic, but it is the only change I can think of that might be related. Can you send the output of: sudo ip netns exec amphora-haproxy ip route show table all and sudo ip netns exec amphora-haproxy ip rule show from the failing amphora? Michael On Fri,

Re: [openstack-dev] [infra] support graphviz in document publishing

have had to work around to get the diagrams to continue to render. Because of that I would recommend you use it sparingly. Michael On Mon, Nov 13, 2017 at 2:08 AM, Sean McGinnis <sean.mcgin...@gmx.com> wrote: > On Mon, Nov 13, 2017 at 09:16:59AM +, Yujun Zhang (ZTE) wrote: &

Re: [openstack-dev] [octavia] amphora fails to send request to members

, can you curl/ping your member 10.0.1.3? I am thinking that the host qdhcp-310fea4b-36ae-4617-b499-5936e8eda842 namespace does not have connectivity to to the nova instances somehow. Michael On Fri, Nov 10, 2017 at 1:24 AM, Yipei Niu <newy...@gmail.com> wrote: > Hi, Michael, > &g

Re: [openstack-dev] [octavia] amphora fails to send request to members

interface eth1. Michael On Wed, Nov 8, 2017 at 10:50 PM, Yipei Niu <newy...@gmail.com> wrote: > Hi, Michael, > > Based on your mail, the information is as follows. > > 1. The version of Octavia I used is Queens, and the latest commit message is > commit 2ab2836d0ebdd0fd

Re: [openstack-dev] [octavia] how to recreate amphora instances

n for that VIP address are not available for the failover process to rebuild. In this case, before you start the above process you will need to recreate the amphora records from your logs, either adding the port information if the ports are still live in neutron, or creating replacement ports.

Re: [openstack-dev] [octavia] amphora fails to send request to members

p two commit messages. That should help us see what your configuration is and narrow down what is going on. As always, you can also try to have an interactive session with us in #openstack-lbaas on IRC. However, with the summit the hours folks are available to answer questions may be a bit limited

Re: [openstack-dev] [Nova] Moving the virt_mkfs flags to privsep

That does work for me, except it means I'll still need to port it to privsep to hit my goal of no rootwrap in Queens. I can live with that. Michael On Wed, Nov 8, 2017 at 4:54 PM, Matt Riedemann <mriede...@gmail.com> wrote: > On 11/8/2017 12:24 PM, Michael Still wrote: > >>

[openstack-dev] [Nova] Moving the virt_mkfs flags to privsep

actually uses this functionality, or if we should just deprecate it all? I'd appreciate your thoughts. Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [octavia] how to recreate amphora instances

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 <kim-norman.s...@noris.de> wrote: > Hi, > > after a rabbitmq problem octavia has removed all am

Re: [openstack-dev] [Nova] Privsep transition state of play

ion on the removal of cellsv2 and nova-network, so > personally I'm not opposed to privsepping those bits if you're > willing. I also agree that the lack of breakage thus far should give us > more confidence that we're safe to continue applying t

Re: [openstack-dev] [forum] Sydney Forum etherpad list

The privsep session doesn't appear to be in that list. Did it get dropped or something? Michael On Wed, Nov 1, 2017 at 12:04 AM, Thierry Carrez <thie...@openstack.org> wrote: > Hi everyone, > > Etherpads for the Forum sessions in Sydney can be found here: > > https://wi

[openstack-dev] [Nova] Privsep transition state of play

catchup. So we could also go all in and get this thing done fully in Queens. So where to from here? Michael 1: Its possibly called a pub. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

Re: [openstack-dev] [octavia] how to list/find the amphoras serving a load balancer

://developer.openstack.org/api-ref/load-balancer/v2/index.html#list-amphora By using the filter capabilities of our Octavia v2 API you can query the API for a list of amphora that are associated to a load balancer ID. Michael On Fri, Oct 13, 2017 at 1:51 AM, <mihaela.ba...@orange.com> wrote

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

Ok, that is quorum. Congratulations Nir! Michael On Mon, Oct 9, 2017 at 3:18 PM, Adam Harwell <flux.a...@gmail.com> wrote: > +1 > > > On Thu, Oct 5, 2017, 05:48 Daniel Mellado <daniel.mellado...@ieee.org> > wrote: >> >> +1 >> >> Go, Nir, Go! &

[openstack-dev] [octavia] New meeting time and channel

[3] we will be having the weekly IRC meeting in the #openstack-lbaas channel. The core team is also available in the #openstack-lbaas channel covering a wide time window, so please feel free to utilize the #openstack-lbaas channel if you are unable to attend the weekly meeting. Michael (johnsom

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was relatively short, with a few important topics taking the spotlight. cdent has posted a message[5] seeking feedback and discussion about a session for the SIG at the upcoming Sydney Forum. If you will be in Sydney, or have topics that should

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

. Octavia cores, please reply to this e-mail with your agreement/disagreement to this proposal. Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

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 <pawel.su...@corp.ovh.com> wrote: > Hello, >

Re: [openstack-dev] [nova] key_pair update on rebuild (a whole lot of conversations)

way. So yes, I think you've reached the right conclusion here. Thanks for your work Sean. Michael On Wed, Oct 4, 2017 at 9:06 AM, Matt Riedemann <mriede...@gmail.com> wrote: > On 10/3/2017 3:16 PM, Sean Dague wrote: > >> There is currently a spec up for being able to spec

Re: [openstack-dev] OpenStack-Ansible testing with OpenVSwitch

deployed an AIO with the Magnum add-on to do a Kubernetes demo during an innovation day. Michael On Mon, Oct 2, 2017 at 4:13 AM, Jean-Philippe Evrard < jean-phili...@evrard.me> wrote: > Well, there are ppl already running OpenVSwitch on openstack-ansible, > so I guess it's just a quest

Re: [openstack-dev] [nova] Forum topics brainstorming

discuss anything in flight for Queens, what > we're working on, and have a chance to ask questions of operators/users for > feedback. For example, we plan to add vGPU support but it will be quite > simple to start, similar with volume multi-attach. > > 4. Michael Still had an item

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

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

Re: [openstack-dev] OpenStack-Ansible testing with OpenVSwitch

Hello JP, Ok, I will do some more testing against the blog post and then hit up the #openstack-ansible channel. I need to finish a presentation on SFC first which is why I am looking into OpenVSwitch. Thanks Michael On Wed, Sep 27, 2017 at 6:25 AM, Jean-Philippe Evrard < jean-ph

Re: [openstack-dev] OpenStack-Ansible and Trove support

. Michael On Wed, Sep 27, 2017 at 6:29 AM, Jean-Philippe Evrard < jean-phili...@evrard.me> wrote: > Hello Michael, > > On top of that, we intend to have a "role maturity" that will include > when the role was proposed and it's current maturity phase, for more > clarit

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

path. Michael On Tue, Sep 26, 2017 at 7:27 PM, Yipei Niu <newy...@gmail.com> wrote: > Hi, Michael, > > The instructions are listed as follows. > > First, create a net1. > $ neutron net-create net1 > $ neutron subnet-create net1 10.0.1.0/24 --name subnet1 > > Seco

Re: [openstack-dev] [nova] reset key pair during rebuilding

? The scenario I can think of is that there's data in that instance that I want, and I've lost the keypair somehow. Unless that data is on an ephemeral, its gone if we do a rebuild. Michael On Wed, Sep 27, 2017 at 4:05 PM, LIU Yulong <liuyulong...@gmail.com> wrote: > On Wed, Sep 27, 2017

[openstack-dev] OpenStack-Ansible testing with OpenVSwitch

of OpenStack AIO with OpenVSwitch would help me a lot. Thanks Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

[openstack-dev] OpenStack-Ansible and Trove support

? Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

dev eth1 onlink It could be that since they are all on the same subnet there is a return path issue in the kernel which this patch fixes with a policy based route. Michael On Mon, Sep 25, 2017 at 1:33 AM, Yipei Niu <newy...@gmail.com> wrote: > Hi, all, > > I encounter some prob

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

on the system. Michael On Fri, Sep 22, 2017 at 4:18 PM, Zhipeng Huang <zhipengh...@gmail.com> wrote: > Hi Doug, > > Absolutely glad to help on this matter. We could take this offline first via > email or irc chat and then comes up with a solution for the broader > community to revi

[openstack-dev] [Nova][Privsep] Heads up: privsep conversion for nova-compute

has already started, with a few patches already landed. Please let me know, perhaps by replying to this email, if you find issues caused by the conversion and I will do my best to work through them with you. Thanks, Michael

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, This week's meeting was primarily focused on reviewing the discussions and plans that were proposed at the PTG. We also merged one new guideline which was frozen prior to the PTG. For a review of PTG activity, please see the etherpad[4] One of the big

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

us end up in another "managed cut and paste" like early oslo where nova continues to develop these and mogan doesn't notice the changes. I'm not sure how we resolve that. One option would be to refactor these files into a shared library. Michael On Wed, Sep 20, 2017 at 5:51 AM, Da

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 <amot...@gmail.com> wrote: > +1 thanks for organizing this > > 2017-09-12 17:23 GMT-06:00 Miguel Lavalle <mig...@mlavalle.com>: >> Dear Neutrinos, >> &g

Re: [openstack-dev] [neutron] [octavia] Neutron LBaaS V2 with haproxy namespace driver HA

driver was to enable a scalable and HA load balancing driver. There would be a number of complications to enabling this and given the limitations of the haproxy namespace driver most environments with HA requirements use the octavia driver. Michael On Sun, Sep 10, 2017 at 6:44 AM, Liping Mao (limao

Re: [openstack-dev] [octavia][l7policy] Is redirect to pool supported?

-starting-with-js-or-images-to-static-pool Note that the first step in the example is to create the pool on the load balancer. Michael (johnsom) On Fri, Sep 8, 2017 at 12:09 AM, <mihaela.ba...@orange.com> wrote: > Sorry, I forgot the link to this documentation: > https://docs.openstack.org/oc

Re: [openstack-dev] [neutron][oslo.db] db retry madness

. It's copying things passed into the API > request so they are usually dictionaries with fewer than 10 keys and values > with small strings or lists of only a few entries, making the copy > operations cheap. > > If we did want to get rid of the copy operation, it would probably be >

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, This week's meeting was mainly focused on discussion of plans for the PTG and about improving the outreach efforts of the SIG. The API-SIG will have a room on Monday and Tuesday at the PTG. In addition to the guided review process [6] we've mentioned before,

[openstack-dev] [neutron][oslo.db] db retry madness

I'm trying to get a handle on neutron's retry decorators.I'm assisting a developer in the networking_odl project who wishes to make use of neutron's retry_if_session_inactive decorator. The developer has run into several problems, including that networking_odl methods here seem to accept a

Re: [openstack-dev] [oslo][oslo.db][keystone] A POC of Keystone over CockroachDB

On Mon, Sep 4, 2017 at 12:06 PM, Ronan-Alexandre Cherrueau wrote: > Hi folks, > > Recently in the Inria's Discovery initiative[1], we got in touch with > CockroachLabs guys with an idea: make Keystone supports CockorachDB. So > we give it a try and you can find

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

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"

Re: [openstack-dev] Minimum version of shred in our supported distros?

But to do that I'd have to learn how to use git and then you wouldn't be forced to take the 17 unrelated patches! You see where I'm going with this right? An alternative would be to move it to the start of that series before the -2 of doom. Michael On 22 Aug. 2017 2:55 am, "Matt Ried

Re: [openstack-dev] Minimum version of shred in our supported distros?

If there's really only one distro which hasn't updated, I'd also be inclined to try and push them to update before they move to Queens. Surely that's a thing we can ask them nicely to do? Michael On Mon, Aug 21, 2017 at 10:20 AM, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Su

Re: [openstack-dev] [Nova] On idmapshift deprecation

I'm going to take the general silence on this as permission to remove the idmapshift binary from nova. You're welcome. Michael On Sat, Jul 29, 2017 at 10:09 AM, Michael Still <mi...@stillhq.com> wrote: > Hi. > > I'm working through the process of converting the libvirt

Re: [openstack-dev] Minimum version of shred in our supported distros?

Specifically we could do something like this: https://review.openstack.org/#/c/495532 Michael On Sun, Aug 20, 2017 at 3:43 PM, Michael Still <mi...@stillhq.com> wrote: > Hi, > > nova.virt.libvirt.storage.lvm.clear_volume() has a comment that we could > use shred to zero out v

[openstack-dev] Minimum version of shred in our supported distros?

for example. If so, we could drop a reasonably complicated caller of dd, and it would make moving to privsep a tiny bit easier. Thanks, Michael 1: https://git.openstack.org/cgit/openstack/nova/tree/nova/virt/libvirt/storage/lvm.py#n219 2: http://savannah.gnu.org/forum/forum.php?forum_id=7815

Re: [openstack-dev] [Octavia]Questions about octavia flavors spec

and create the providers interface during the Queens series. Michael On Tue, Aug 15, 2017 at 7:09 PM, 何庆 <tsingh...@gmail.com> wrote: > Hi, I'm trying to figure out how the flavor will be implemented and have few > questions about the flavor spec[1] > > 1. What does "R

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, This week's meeting centered around two main topics; the Guided Review Process[0] and the inclusion of guidance to discourage extension usage[4]. As the working group has now become a Special Interest Group, we have begun the work of changing the documentation

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

rolling here. I was really hoping to be able to use this for our dashboard work in Queens, but giving the work here I may need to do something in the interim. Maybe if these patches merge for python-openstacksdk I can use that for now and migrate as new SDK becomes available. Michael

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

decided to ping the dev mailing list. My questions: 1. Is this project abandoned? 2. Is there a plan to make it an official project? 3. Should we continue to develop for it? Thanks, Michael (johnsom) [1] https://review.openstack.org/#/q/project:openstack/python-openstacksdk+statu s:open+topic

[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] [Nova] On idmapshift deprecation

of deprecation first? Or because its "internal only" just remove it? Discuss. Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u

Re: [openstack-dev] [Nova] Broken nova-lxd

lxd is going to move to privsep in lockstep with nova, your best bet would be to duplicate this utility method in the nova-lxd codebase. Michael On Thu, Jul 27, 2017 at 11:25 PM, Kharkov Alexander < kharkovalexan...@gmail.com> wrote: > Hi, Michael > I recently found that you commit t

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Today's meeting continued the discussion about the newly posted gerrit review for the Guided Review Process[0]. There is still some work to be done before the process is in shape to announce for the Denver PTG, but the group is confident about having the process

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

proposed: https://review.openstack.org/#/c/487902/ On Thu, Jul 27, 2017 at 9:46 AM, Michael Bayer <mba...@redhat.com> wrote: > On Wed, Jul 26, 2017 at 8:06 PM, Jay Pipes <jaypi...@gmail.com> wrote: >> Isn't that exactly what I'm proposing below? :) > >

Re: [openstack-dev] [oslo][oslo.db] nominating Jay Pipes for oslo-db-core

Yeah if Jay has the time that's a big +1 from me! On Thu, Jul 27, 2017 at 10:04 AM, Doug Hellmann wrote: > I have noticed that Jay has been very deeply involved in several > recent design discussions about oslo.db, and he obviously has a > great deal of experience in the

Re: [openstack-dev] [all] [oslo.db] [relational database users] heads up for a MariaDB issue that will affect most projects

aybe* mariadb's CHECK constraint here already has a predictable name. I'd have to get a 10.2 instance running and see what it comes up with. > > 2017-07-24 23:21 GMT+08:00 Michael Bayer <mba...@redhat.com>: >> >> hey good news, the owner of the issue upstream found that th

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Wed, Jul 26, 2017 at 8:06 PM, Jay Pipes wrote: > Isn't that exactly what I'm proposing below? :) yes, I'm agreeing with you! __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Jul 26, 2017 7:45 PM, "Jay Pipes" <jaypi...@gmail.com> wrote: On 07/26/2017 07:06 PM, Octave J. Orgeron wrote: > Hi Michael, > > On 7/26/2017 4:28 PM, Michael Bayer wrote: > >> >> it at all. >> thinking out loud >> >> o

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Jul 26, 2017 6:28 PM, "Michael Bayer" <mba...@redhat.com> wrote: On Wed, Jul 26, 2017 at 6:19 PM, Michael Bayer <mba...@redhat.com> wrote: > On Wed, Jul 26, 2017 at 5:30 PM, Michael Bayer <mba...@redhat.com> wrote: >> >> There is a bigger problem

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Wed, Jul 26, 2017 at 6:19 PM, Michael Bayer <mba...@redhat.com> wrote: > On Wed, Jul 26, 2017 at 5:30 PM, Michael Bayer <mba...@redhat.com> wrote: >> >> There is a bigger problem with this entire series of changes, whether >> or not the "ndb" keywo

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Wed, Jul 26, 2017 at 5:30 PM, Michael Bayer <mba...@redhat.com> wrote: > > There is a bigger problem with this entire series of changes, whether > or not the "ndb" keyword is present. Which is that projects need to > add new columns, tables, and make d

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

hecks need to be put in place in oslo.db that would sum the total row size of any given table and raise an error if the limit is surpassed. On Wed, Jul 26, 2017 at 5:40 PM, Octave J. Orgeron <octave.orge...@oracle.com> wrote: > Hi Michael, > > Comments below.. > >

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

flags, which is a more lengthy process than the rest of > this. > > I don't see the point in trying to make this stuff anymore complicated. > > Octave > > > On 7/25/2017 12:20 PM, Michael Bayer wrote: >> >> On Mon, Jul 24, 2017 at 5:41 PM, Michael Bayer

<    1   2   3   4   5   6   7   8   9   10   >