Re: [openstack-dev] [mistral][oslo][messaging] Removing “blocking” executor from oslo.messaging

On 10/18/18 9:59 AM, Ken Giusti wrote: Hi Renat, The biggest issue with the blocking executor (IMHO) is that it blocks the protocol I/O while  RPC processing is in progress.  This increases the likelihood that protocol processing will not get done in a timely manner and things start to

Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur wrote: > Hi all, > > Sorry for chiming in really late in this topic, but I think $subj is worth > discussing until we settle harder on the potentially confusing terminology. > > I think the difference between "Edge" and "Far Edge" is too vague to

Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

Love the idea to have clearer terminology. Suggest we let telco folks to suggest terminology to use. This is not a 3 level hierarchy but much more. There are several layers of aggregation from local to metro, to regional, to DC. And potential multiple layers in each. -Original Message-

Re: [openstack-dev] [Openstack-sigs] [all] Naming the T release of OpenStack

Sorry, I'm opposed to this idea. I admit I don't understand the political framework, nor have I read the governing documents beyond [1], but that document makes it clear that this is supposed to be a community-wide vote. Is it really legal for the TC (or whoever has merge rights on [2]) to merge

Re: [openstack-dev] [Openstack-sigs] [all] Naming the T release of OpenStack

Michal, that will never work it’s 11 characters long > On Oct 18, 2018, at 09:43, Eric Fried wrote: > > Sorry, I'm opposed to this idea. > > I admit I don't understand the political framework, nor have I read the > governing documents beyond [1], but that document makes it clear that >

Re: [openstack-dev] [tripleo] TripleO CI Summary: Sprint 20

Oops. Missing footer info. [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/sprint-20-193 [2] https://review.rdoproject.org/etherpad/p/ruckrover-sprint20.1 On Thu, Oct 18, 2018 at 2:05 PM Rafael Folco wrote: > Greetings, > > The TripleO CI team has just completed Sprint 20 (Sep-27

[openstack-dev] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

Hi all, Sorry for chiming in really late in this topic, but I think $subj is worth discussing until we settle harder on the potentially confusing terminology. I think the difference between "Edge" and "Far Edge" is too vague to use these terms in practice. Think about the "edge" metaphor

[openstack-dev] [senlin] Meeting cancelled for this week

Everyone, I’m canceling the Senlin meeting this week because I’m unavailable. We will resume at the scheduled time next week. Duc (dtruong) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Openstack-sigs] [all] Naming the T release of OpenStack

and any talks I give in Denver (Forum, Ops, Main) will include "sl". It's handy in a variety of ways. On Thu, Oct 18, 2018 at 9:39 AM David Medberry wrote: > I'm fine with Train but I'm also fine with just adding it to the list and > voting on it. It will win. > > Also, for those not familiar

[openstack-dev] [tripleo] TripleO CI Summary: Sprint 20

Greetings, The TripleO CI team has just completed Sprint 20 (Sep-27 thru Oct-17). The following is a summary of completed work during this sprint cycle: - Bootstrapped upstream standalone job on Fedora 28. - Migrated RDO jobs in Software Factory to native Zuul v3. -

Re: [openstack-dev] [all] Naming the T release of OpenStack

On 2018-10-18 08:35:21 -0500 (-0500), Jay S Bryant wrote: [...] > When OpenStack developers think Denver, we think Trains.  :-) [...] As, presumably, do many OpenStack operators now since the Ops Mid-Cycle event was co-located with the most recent PTG. -- Jeremy Stanley signature.asc

Re: [openstack-dev] [mistral][oslo][messaging] Removing “blocking” executor from oslo.messaging

Hi Renat, The biggest issue with the blocking executor (IMHO) is that it blocks the protocol I/O while RPC processing is in progress. This increases the likelihood that protocol processing will not get done in a timely manner and things start to fail in weird ways. These failures are timing

Re: [openstack-dev] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On 10/18/2018 10:23 AM, Dmitry Tantsur wrote: Hi all, Sorry for chiming in really late in this topic, but I think $subj is worth discussing until we settle harder on the potentially confusing terminology. I think the difference between "Edge" and "Far Edge" is too vague to use these terms

Re: [openstack-dev] [Openstack-sigs] [all] Naming the T release of OpenStack

I'm fine with Train but I'm also fine with just adding it to the list and voting on it. It will win. Also, for those not familiar with the debian/ubuntu command "sl", now is the time to become so. apt install sl sl -Flea #ftw On Thu, Oct 18, 2018 at 12:35 AM Tony Breeds wrote: > Hello all, >

[openstack-dev] [tc][all] TC office hours is started now on #openstack-tc

Hi All, TC office hour is started on #openstack-tc channel. Feel free to reach to us for anything you want discuss/input/feedback/help from TC. -gmann __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [all] Naming the T release of OpenStack

On Thu, 2018-10-18 at 17:35 +1100, Tony Breeds wrote: > Hello all, > As per [1] the nomination period for names for the T release have > now closed (actually 3 days ago sorry). The nominated names and any > qualifying remarks can be seen at2]. > > Proposed Names > * Tarryall > * Teakettle

Re: [openstack-dev] [Openstack-sigs] [horizon][nova][cinder][keystone][glance][neutron][swift] Horizon feature gaps

Theres also this document with very detailed information: https://docs.google.com/spreadsheets/d/18ZtWC75BNCwFqLfFpCGGJ9uPVBvUXX0xuXP1yYG0NDA/edit#gid=0 Erlon Em qui, 18 de out de 2018 às 10:30, Jay S Bryant escreveu: > > > On 10/18/2018 7:21 AM, Sean McGinnis wrote: > > On Wed, Oct 17, 2018

[openstack-dev] [zun][zun-ui] How to get "host" attribute for image

Hi folks, I found the following commit to show "host" attribute for image. https://github.com/openstack/zun/commit/72eac7c8f281de64054dfa07e3f31369c5a251f0 But I could not get the "host" for image with zun-show. I think image-list and image-show need to show "host" for admin, so I'd like to

Re: [openstack-dev] [mistral][oslo][messaging] Removing “blocking” executor from oslo.messaging

Hi, @Ken, I understand your considerations. I get that. I’m only asking not to remove it *for now*. And yes, if you think it should be discouraged from using it’s totally fine. But practically, it’s been the only reliable option for Mistral so far that may be our fault, I have to admit,

Re: [openstack-dev] [zun][zun-ui] How to get "host" attribute for image

Shu, It looks the 'host' field was added to the DB table but not exposed via REST API by mistake. See if this patch fixes the issue: https://review.openstack.org/#/c/611753/ . Best regards, Hongbin On Thu, Oct 18, 2018 at 10:50 PM Shu M. wrote: > Hi folks, > > I found the following commit to

[openstack-dev] [cinder] [nova] Problem of Volume(in-use) Live Migration with ceph backend

Hi folks, When I use the LVM backend to create the volume, then attach it to a vm. I can migrate the volume(in-use) from one host to another. The nova libvirt will call the 'rebase' to finish it. But if using ceph backend, it raises exception 'Swap only supports host devices'. So now it

[openstack-dev] 答复: [senlin] Meeting cancelled for this week

ok. 原始邮件 发件人：DucTruong; 收件人：openstack-dev@lists.openstack.org; 日期：2018-10-19 01:08:18 主题：[openstack-dev] [senlin] Meeting cancelled for this week __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Searchlight] Workshop at the Korea User Group monthly meetup tonight

Hi all, I will have a small session at the OpenStack Korea User Group monthly meetup (October 2018) tonight. Stop by if you're around the Gangnam (Seoul, South Korea) area :) - *Location:* TOZ Gangnam Tower, near to Gangnam station (near to exit 2, https://goo.gl/maps/CVYDpgYdF5J2 or

Re: [openstack-dev] [all] Naming the T release of OpenStack

On Oct 18, 2018, at 11:43 AM, Michał Dulko wrote: > > I'm totally supportive for OpenStack Train, but got to say that > OpenStack Troublesome is a wonderful name as well. :) Yeah, I’m sure that the marketing people won’t have a problem vetting that name. :) -- Ed Leafe

Re: [openstack-dev] [Openstack-sigs] [all] Naming the T release of OpenStack

> Wiadomość napisana przez Remo Mattei w dniu 18.10.2018, o godz. > 19:08: > > Michal, that will never work it’s 11 characters long Shorter could be Openstack Trouble ;) > > > > >> On Oct 18, 2018, at 09:43, Eric Fried wrote: >> >> Sorry, I'm opposed to this idea. >> >> I admit I

Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen wrote: > > On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur wrote: >> >> Hi all, >> >> Sorry for chiming in really late in this topic, but I think $subj is worth >> discussing until we settle harder on the potentially confusing terminology. >> >>

Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On Thu, Oct 18, 2018 at 4:45 PM John Fulton wrote: > On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen > wrote: > > > > On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur > wrote: > >> > >> Hi all, > >> > >> Sorry for chiming in really late in this topic, but I think $subj is > worth > >>

[openstack-dev] [neutron] [drivers] Cancelling drivers meeting on October 19th

Dear Neutron team, We don't have triaged RFEs to be discussed during the drivers meeting on October 19th. So let's skip that meeting and we will resume normally on the 26th. Best regards Miguel __ OpenStack Development

[openstack-dev] [all] Naming the T release of OpenStack

Hello all, As per [1] the nomination period for names for the T release have now closed (actually 3 days ago sorry). The nominated names and any qualifying remarks can be seen at2]. Proposed Names * Tarryall * Teakettle * Teller * Telluride * Thomas * Thornton * Tiger * Tincup *

[openstack-dev] [mistral][oslo][messaging] Removing “blocking” executor from oslo.messaging

Hi Oslo Team, Can we retain “blocking” executor for now in Oslo Messaging? Some background.. For a while we had to use Oslo Messaging with “blocking” executor in Mistral because of incompatibility of MySQL driver with green threads when choosing “eventlet” executor. Under certain conditions

Re: [openstack-dev] [oslo][taskflow] Thoughts on moving taskflow out of openstack/oslo

On 10/17/18 5:59 PM, Joshua Harlow wrote: Dmitry Tantsur wrote: On 10/10/18 7:41 PM, Greg Hill wrote: I've been out of the openstack loop for a few years, so I hope this reaches the right folks. Josh Harlow (original author of taskflow and related libraries) and I have been discussing the

[openstack-dev] [nova] API updates week 18-42

Hi All, Please find the Nova API highlights of this week. Weekly Office Hour: === What we discussed this week: - Discussed about API extensions works. - Discussed on 2 new bugs which needs more log for further debugging. added bug comments. Planned Features :

Re: [openstack-dev] [tripleo][ui][tempest][oooq] Refreshing plugins from git

On 10/18/18 2:17 AM, Honza Pokorny wrote: Hello folks, I'm working on the automated ui testing blueprint[1], and I think we need to change the way we ship our tempest tests. Here is where things stand at the moment: * We have a kolla image for tempest * This image contains the tempest rpm,

Re: [openstack-dev] [requirements][vitrage][infra] SQLAlchemy-Utils version 0.33.6 breaks Vitrage gate

On 18/10/2018 14.15, Ifat Afek wrote: Hi, In the last three days Vitrage gate is broken due to the new requirement of SQLAlchemy-Utils==0.33.6. We get the following error [1]: [...] > Can we move back to version 0.33.5? or is there another solution? We discussed that on #openstack-infra,

Re: [openstack-dev] [Openstack-sigs] [horizon][nova][cinder][keystone][glance][neutron][swift] Horizon feature gaps

On Wed, Oct 17, 2018 at 10:41:36AM -0500, Matt Riedemann wrote: > On 10/17/2018 9:24 AM, Ivan Kolodyazhny wrote: > > > > As you may know, unfortunately, Horizon doesn't support all features > > provided by APIs. That's why we created feature gaps list [1]. > > > > I'd got a lot of great

[openstack-dev] [requirements][vitrage] SQLAlchemy-Utils version 0.33.6 breaks Vitrage gate

Hi, In the last three days Vitrage gate is broken due to the new requirement of SQLAlchemy-Utils==0.33.6. We get the following error [1]: 2018-10-18 09:21:13.946 |

Re: [openstack-dev] [requirements][vitrage][infra] SQLAlchemy-Utils version 0.33.6 breaks Vitrage gate

On 2018-10-18 14:57:23 +0200 (+0200), Andreas Jaeger wrote: > On 18/10/2018 14.15, Ifat Afek wrote: > > Hi, > > > > In the last three days Vitrage gate is broken due to the new requirement > > of SQLAlchemy-Utils==0.33.6. > > We get the following error [1]: > > > > [...] > > > Can we move back

[openstack-dev] [release] Release countdown for week R-24 and R-23, October 22 - November 2

Development Focus - Team focus should be on spec approval and implementation for priority features. General Information --- Projects that have been following the cycle-with-milestone release model will be switched over to cycle-with-rc soon [0]. Just a reminder

Re: [openstack-dev] [all] Naming the T release of OpenStack

On 10/18/2018 1:35 AM, Tony Breeds wrote: Hello all, As per [1] the nomination period for names for the T release have now closed (actually 3 days ago sorry). The nominated names and any qualifying remarks can be seen at2]. Proposed Names * Tarryall * Teakettle * Teller *

Re: [openstack-dev] [all] Naming the T release of OpenStack

FWIW, I've have no clue if this is serious or not, or what 'Train' refers to... On Thu, Oct 18, 2018 at 2:25 PM Jay S Bryant wrote: > On 10/18/2018 1:35 AM, Tony Breeds wrote: > > Hello all, > As per [1] the nomination period for names for the T release have > now closed (actually 3 days

Re: [openstack-dev] [Openstack-sigs] [horizon][nova][cinder][keystone][glance][neutron][swift] Horizon feature gaps

On 10/18/2018 7:21 AM, Sean McGinnis wrote: On Wed, Oct 17, 2018 at 10:41:36AM -0500, Matt Riedemann wrote: On 10/17/2018 9:24 AM, Ivan Kolodyazhny wrote: As you may know, unfortunately, Horizon doesn't support all features provided by APIs. That's why we created feature gaps list [1]. I'd

Re: [openstack-dev] [all] Naming the T release of OpenStack

On 10/18/2018 8:29 AM, Neil Jerram wrote: FWIW, I've have no clue if this is serious or not, or what 'Train' refers to... Neil, The two Project Team Gathering events in Denver were held at a hotel next to the train line from downtown to the airport.  The crossing signals there had some

Re: [openstack-dev] [all] Naming the T release of OpenStack

On Thu, Oct 18, 2018 at 2:35 PM Jay S Bryant wrote: > > > > On 10/18/2018 8:29 AM, Neil Jerram wrote: > > FWIW, I've have no clue if this is serious or not, or what 'Train' refers > to... > > Neil, > > The two Project Team Gathering events in Denver were held at a hotel next to > the train line

Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On 10/18/18 4:33 PM, arkady.kanev...@dell.com wrote: Love the idea to have clearer terminology. Suggest we let telco folks to suggest terminology to use. This is not a 3 level hierarchy but much more. There are several layers of aggregation from local to metro, to regional, to DC. And