Re: [openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

+1 ! On Wed, Aug 1, 2018 at 2:31 PM, Giulio Fidente wrote: > Hi, > > I would like to propose Lukas Bezdicka core on TripleO. > > Lukas did a lot work in our tripleoclient, tripleo-common and > tripleo-heat-templates repos to make FFU possible. > > FFU, which is meant to permit upgrades from

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

If I could, I would have something *like* the EXPLAIN syntax for looking at a sql query, but instead of telling me the query plan for a sql query, it would tell me the decisions (placement plan?) that resulted in a given resource being placed at a certain location. And I would be able to say

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

2018-08-02 4:09 GMT+08:00 Jay Pipes : > On 08/01/2018 02:02 PM, Chris Friesen wrote: > >> On 08/01/2018 11:32 AM, melanie witt wrote: >> >> I think it's definitely a significant issue that troubleshooting "No >>> allocation >>> candidates returned" from placement is so difficult. However, it's

Re: [openstack-dev] OpenStack lagging behind 2 major python versions: we need a Python 3.7 gate

On 07/12/2018 10:38 PM, Thomas Goirand wrote: > Hi everyone! > > [...] Here's more examples that shows why we should be gating earlier with newer Python versions: Nova: https://review.openstack.org/#/c/584365/ Glance: https://review.openstack.org/#/c/586716/ Murano:

Re: [openstack-dev] [tricircle] Tricircle or Trio2o

HI Andrea ! Yes, just as you said.The tricircle is now only work for network.Because the trio2o do not as the openstack official project. so it is a long time nobody contribute to it. But recently In the next openstack stein circle. we have plan to make tricircle and trio2o work together in

Re: [openstack-dev] [Tacker] - TACKER + NETWORKING_SFC + NSH

William, tacker is just using network-sfc API, we have tested the ovs driver of it. regards, yong sheng gong -- 龚永生 九州云信息科技有限公司 99CLOUD Co. Ltd. 邮箱（Email）：gong.yongsh...@99cloud.net 地址：北京市海淀区上地三街嘉华大厦B座806 Addr : Room 806, Tower B, Jiahua Building, No. 9 Shangdi 3rd Street, Haidian

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

Hello Sebastian, Korean has also currently 100% translation now. About two weeks ago, there were a discussion how to include the list of translators per translated document. My proposal is mentioned in [1] - do you think it is a good idea and it is under implementation, or parsing the name

Re: [openstack-dev] [all][election][tc] Lederless projects.

The trove team had our weekly meeting last night, all attended core members and the new contributors from Samsung R Center in Krakow, Poland were agreed on that we only have Dariusz Krol as an PTL candidate and hope he could be accepted as a valid candidate [1]. Tony has pointed to me that the

[openstack-dev] Candidacy  to continue my work as the Senlin PTL  for theStein cycle

Hi all, This is my candidacy to continue my work as the Senlin PTL for the Stein cycle. In Rocky cycle, we finished many features, testing and bug fixing works. For example: * Kubernetes: Added dependency relationship between the master cluster and the worker cluster created for

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya wrote: > On 7/6/18 7:02 PM, Ben Nemec wrote: >> >> >> >> On 07/05/2018 01:23 PM, Dan Prince wrote: >>> >>> On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by service

[openstack-dev] [tripleo] Patches to speed up plan operations

Hey folks! So I've been working on some patches to speed up plan operations in TripleO. This was originally driven by the UI needing to be able to perform a 'plan upload' in something less than several minutes. :) https://review.openstack.org/#/c/581153/ https://review.openstack.org/#/c/581141/

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 8/1/2018 3:55 PM, Ben Nemec wrote: I changed disk_allocation_ratio to 2.0 in the config file and it had no effect on the existing resource provider.  I assume that is because I had initially deployed with it unset, so I got 1.0, and when I later wanted to change it the provider already

Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition

On Tue, 2018-07-31 at 07:38 -0400, Pradeep Kilambi wrote: > > > On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau wrote: > > On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote: > > >  > > >  > > > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz > > > > > wrote: > > > > On Mon, Jul 30, 2018 at

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 02:22 PM, Matt Riedemann wrote: On 8/1/2018 12:06 PM, Ben Nemec wrote: To close the loop on the problem I was having, it looks like the allocation_ratio config opts are now just defaults, and if you want to change ratios after the initial deployment you need to do so with the

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 02:02 PM, Chris Friesen wrote: On 08/01/2018 11:32 AM, melanie witt wrote: I think it's definitely a significant issue that troubleshooting "No allocation candidates returned" from placement is so difficult. However, it's not straightforward to log detail in placement when the

Re: [openstack-dev] [Nova] [Cyborg] Updates to os-acc proposal

Sundar- > On an unrelated note, thanks for the > pointer to the GPU spec > (https://review.openstack.org/#/c/579359/10/doc/source/specs/rocky/device-passthrough.rst). > I will review that. Thanks. Please note that this is for nova-powervm, PowerVM's *out-of-tree* compute driver. We hope to bring

[openstack-dev] [all] Gerrit project renaming Friday August 3 at 16:00UTC

Hello everyone, The infra team will be renaming a couple of projects in Gerrit on Friday starting at 16:00UTC. This requires us to restart Gerrit on review.openstack.org. The total noticeable downtime should be no more than about 10 minutes. If you would like to follow along, the current

Re: [openstack-dev] [Nova] [Cyborg] Updates to os-acc proposal

Hi Eric,     Please see my responses inline. On an unrelated note, thanks for the pointer to the GPU spec (https://review.openstack.org/#/c/579359/10/doc/source/specs/rocky/device-passthrough.rst). I will review that. On 7/31/2018 10:42 AM, Eric Fried wrote: Sundar- * Cyborg drivers

[openstack-dev] [tc] Technical Committee update for 1 Aug 2018

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 8/1/2018 12:06 PM, Ben Nemec wrote: To close the loop on the problem I was having, it looks like the allocation_ratio config opts are now just defaults, and if you want to change ratios after the initial deployment you need to do so with the client. You mean how

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 8/1/2018 12:32 PM, melanie witt wrote: I think it's definitely a significant issue that troubleshooting "No allocation candidates returned" from placement is so difficult. However, it's not straightforward to log detail in placement when the request for allocation candidates is essentially

Re: [openstack-dev] [sahara] Anti-Affinity Broke

Thanks, that is what I did as well. On Wed, Aug 1, 2018 at 3:50 PM Joe Topjian wrote: > Hello, > > Yes, those workarounds were able to get anti-affinity working. In my > original email I noted the uninitialized key issue. We're getting around > this by doing the following: > >

Re: [openstack-dev] [sahara] Anti-Affinity Broke

Hello, Yes, those workarounds were able to get anti-affinity working. In my original email I noted the uninitialized key issue. We're getting around this by doing the following: properties[SERVER_GROUP_NAMES] = [] Thanks, Joe On Wed, Aug 1, 2018 at 12:39 PM, Telles Nobrega wrote: > Hi Joe,

Re: [openstack-dev] [sahara] Anti-Affinity Broke

Hi Joe, sorry for only replying to this now, but I just got time to work on it today. When you did those workarounds, did it all work properly? I'm hitting an issue with a KeyError whili trying to add the resource to the properties. properties[SERVER_GROUP_NAMES].insert(i,

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 11:32 AM, melanie witt wrote: I think it's definitely a significant issue that troubleshooting "No allocation candidates returned" from placement is so difficult. However, it's not straightforward to log detail in placement when the request for allocation candidates is essentially

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On Wed, 1 Aug 2018 12:17:36 -0500, Ben Nemec wrote: On 08/01/2018 11:23 AM, Chris Friesen wrote: On 08/01/2018 09:58 AM, Andrey Volkov wrote: Hi, It seems you need first to check what placement knows about resources of your cloud. This can be done either with REST API [1] or with

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 2018-08-01 12:48:39 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Monty Taylor's message of 2018-08-01 09:58:03 -0500: > > On 08/01/2018 08:38 AM, Jeremy Stanley wrote: > > > On 2018-08-01 09:58:48 -0300 (-0300), Rafael Weingärtner wrote: > > >> What about Rocket chat instead of Slack? It

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 11:17 AM, Ben Nemec wrote: On 08/01/2018 11:23 AM, Chris Friesen wrote: The fact that there is no real way to get the equivalent of the old detailed scheduler logs is a known shortcoming in placement, and will become more of a problem if/when we move more complicated things

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 11:23 AM, Chris Friesen wrote: On 08/01/2018 09:58 AM, Andrey Volkov wrote: Hi, It seems you need first to check what placement knows about resources of your cloud. This can be done either with REST API [1] or with osc-placement [2]. For osc-placement you could use: pip

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

Aha, thanks! That explains why I couldn't find any client commands for placement before. To close the loop on the problem I was having, it looks like the allocation_ratio config opts are now just defaults, and if you want to change ratios after the initial deployment you need to do so with

[openstack-dev] [all][python3] approved python3-first goal for stein

The goal to run jobs under python3 first has been approved for Stein [1]. We are going to be using storyboard for tracking work on the goal, so I have started creating the stories and tasks. Because of the complexity of the work, I am setting up 1 story for each team, with 1 task for each

[openstack-dev] [tricircle] Tricircle or Trio2o

Hello All, While I was looking for multisite openstack solutions I stumbled on Tricircle project which seemed fairly perfect for the job except that l it was split in two parts, tricircle itself for the network part and Trio2o for all the rest. Now it seems that the Trio2o project is no longer

Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to VF mirroring

Hi, Yes, we need to refine spec for sure, once a consensus is reached focus will be on implementation, Here’s implementation patch (WIP) https://review.openstack.org/#/c/584892/ , we can’t really review api part until spec if finalized but, other stuff like config and common issues can still

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Excerpts from Monty Taylor's message of 2018-08-01 09:58:03 -0500: > On 08/01/2018 08:38 AM, Jeremy Stanley wrote: > > On 2018-08-01 09:58:48 -0300 (-0300), Rafael Weingärtner wrote: > >> What about Rocket chat instead of Slack? It is open source. > >> https://github.com/RocketChat/Rocket.Chat >

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On Wed, Aug 1, 2018 at 5:21 AM, Andrey Kurilin wrote: > I can make an assumption that for marketing reasons, Slack Inc can propose > extended Free plan. > But anyway, even with default one the only thing which can limit us is > `10,000 searchable messages` which is bigger than 0 (freenode doesn't

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 09:58 AM, Andrey Volkov wrote: Hi, It seems you need first to check what placement knows about resources of your cloud. This can be done either with REST API [1] or with osc-placement [2]. For osc-placement you could use: pip install osc-placement openstack allocation candidate

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 08:17 AM, Andrey Kurilin wrote: ср, 1 авг. 2018 г. в 15:37, Monty Taylor >: On 08/01/2018 06:22 AM, Luigi Toscano wrote: > On Wednesday, 1 August 2018 12:49:13 CEST Andrey Kurilin wrote: >> Hey Ian and stackers! >> >> ср, 1

Re: [openstack-dev] [requirements][ffe] Critical bug found in python-cinderclient

On 18-07-31 15:50:42, Doug Hellmann wrote: > Excerpts from Sean McGinnis's message of 2018-07-31 14:15:08 -0500: > > A critical bug has been found in python-cinderclient that is impacting both > > horizon and python-openstackclient (at least). > > > >

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

Hi, It seems you need first to check what placement knows about resources of your cloud. This can be done either with REST API [1] or with osc-placement [2]. For osc-placement you could use: pip install osc-placement openstack allocation candidate list --resource DISK_GB=20 --resource

Re: [openstack-dev] [requirements][ffe] Critical bug found in python-cinderclient

Hi, I'm OK with this release both from Cinder and Horizon perspective. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 31, 2018 at 10:50 PM, Doug Hellmann wrote: > Excerpts from Sean McGinnis's message of 2018-07-31 14:15:08 -0500: > > A critical bug has been found in

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Monty Taylor writes: > On 08/01/2018 12:45 AM, Ian Wienand wrote: >> Hello, >> I'd suggest to start, people with an interest in a channel can request >> +r from an IRC admin in #openstack-infra and we track it at [2] > > To mitigate the pain caused by +r - we have created a channel called >

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

On 08/01/2018 09:27 AM, Doug Hellmann wrote: Moisés Guimarães (moguimar) did quite a bit of work on oslo.config during the Rocky cycle to add driver support. Based on that work, and a discussion we have had since then about general cleanup needed in oslo.config, I think he would make a good

[openstack-dev] [horizon] PTL on vacation: what to do with meeting and RC1?

Hi team, I'll be on PTO next week. Are we OK to cancel the next meeting? I remember that next week is a deadline for RC1, so I'm going to propose a patch to release it a bit later next week: Tuesday or Wednesday. In an emergency case, please, reach me via e-mail because I'll have a limited

[openstack-dev] [nova] How to debug no valid host failures with placement

Hi, I'm having an issue with no valid host errors when starting instances and I'm struggling to figure out why. I thought the problem was disk space, but I changed the disk_allocation_ratio and I'm still getting no valid host. The host does have plenty of disk space free, so that shouldn't

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 2018-08-01 09:24 AM, Monty Taylor wrote: On 08/01/2018 12:45 AM, Ian Wienand wrote: Hello, It seems freenode is currently receiving a lot of unsolicited traffic across all channels.  The freenode team are aware [1] and doing their best. There are not really a lot of options.  We can set

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 08:38 AM, Jeremy Stanley wrote: On 2018-08-01 09:58:48 -0300 (-0300), Rafael Weingärtner wrote: What about Rocket chat instead of Slack? It is open source. https://github.com/RocketChat/Rocket.Chat Monty, what kind of evaluation would you guys need? I might be able to help.

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

+1 On Wed, Aug 1, 2018 at 11:49 AM Ben Nemec wrote: > +1 > > On 08/01/2018 08:27 AM, Doug Hellmann wrote: > > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > > during the Rocky cycle to add driver support. Based on that work, > > and a discussion we have had since then

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

+1 On 08/01/2018 08:27 AM, Doug Hellmann wrote: Moisés Guimarães (moguimar) did quite a bit of work on oslo.config during the Rocky cycle to add driver support. Based on that work, and a discussion we have had since then about general cleanup needed in oslo.config, I think he would make a good

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

+1 from me! On Wed, Aug 1, 2018 at 6:27 AM Doug Hellmann wrote: > > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > during the Rocky cycle to add driver support. Based on that work, > and a discussion we have had since then about general cleanup needed > in oslo.config, I

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

Yeah! +1 Moisés has been doing a great job there On Wed, 1 Aug 2018, 16:27 Doug Hellmann, wrote: > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > during the Rocky cycle to add driver support. Based on that work, > and a discussion we have had since then about general

Re: [openstack-dev] [cinder] about block device driver

On Fri, Jul 27, 2018 at 8:44 AM Matt Riedemann wrote: > On 7/16/2018 4:20 AM, Gorka Eguileor wrote: > > If I remember correctly the driver was deprecated because it had no > > maintainer or CI. In Cinder we require our drivers to have both, > > otherwise we can't guarantee that they actually

[openstack-dev] [ironic] August bug day tomorrow! (August 2nd 13:00 UTC to 14:00 UTC)

Hey all, Welcome to August! Tomorrow is the first Thursday of the month so bug day is once again upon us. For details please see the etherpad [0]. If you have ideas for how we can improve Bug Day, or how the agenda should be structured, let me know! I hope to see you there tomorrow Thanks,

Re: [openstack-dev] [neutron] Credentials for a Keystone DB lookup from Neutron

Hoping I can leverage the wisdom of the ML for a follow-up point on this topic... I've coded this up now following Aditya's suggestion, but the issue now is about the Neutron user (or more generally, whatever is configured in neutron.conf's [keystone_authtoken] section) being authorized to do a

Re: [openstack-dev] [tripleo][ci][metrics] Stucked in the middle of work because of RDO CI

On 07/31/2018 04:51 PM, Wesley Hayutin wrote: On Tue, Jul 31, 2018 at 7:41 AM Sagi Shnaidman > wrote: Hi, Martin I see master OVB jobs are passing now [1], please recheck. [1] http://cistatus.tripleo.org/ Things have improved and I see a lot of

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

On Wed, Aug 1, 2018 at 9:28 AM Doug Hellmann wrote: > > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > during the Rocky cycle to add driver support. Based on that work, > and a discussion we have had since then about general cleanup needed > in oslo.config, I think he would

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Monty Taylor wrote: [...] However, it's worth noting that matrix is not immune to spam. As an open federated protocol, it's a target as well. Running our own home server might give us some additional tools - but it might not, and we might be in the same scenario except now we're running

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 2018-08-01 16:17:47 +0300 (+0300), Andrey Kurilin wrote: [...] > If the alternative doesn't feet these criteria, a lot of people > will stay at Freenode and migration will fail. [...] We've had discussions off and on for years about moving from Freenode to OFTC (whose ideals more closely

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 2018-08-01 09:58:48 -0300 (-0300), Rafael Weingärtner wrote: > What about Rocket chat instead of Slack? It is open source. > https://github.com/RocketChat/Rocket.Chat > > Monty, what kind of evaluation would you guys need? I might be > able to help. Consider reading and possibly resurrecting

[openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

Moisés Guimarães (moguimar) did quite a bit of work on oslo.config during the Rocky cycle to add driver support. Based on that work, and a discussion we have had since then about general cleanup needed in oslo.config, I think he would make a good addition to the oslo.config review team. Please

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 12:45 AM, Ian Wienand wrote: Hello, It seems freenode is currently receiving a lot of unsolicited traffic across all channels.  The freenode team are aware [1] and doing their best. There are not really a lot of options.  We can set "+r" on channels which means only nickserv

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

ср, 1 авг. 2018 г. в 15:37, Monty Taylor : > On 08/01/2018 06:22 AM, Luigi Toscano wrote: > > On Wednesday, 1 August 2018 12:49:13 CEST Andrey Kurilin wrote: > >> Hey Ian and stackers! > >> > >> ср, 1 авг. 2018 г. в 8:45, Ian Wienand : > >>> Hello, > >>> > >>> It seems freenode is currently

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

What about Rocket chat instead of Slack? It is open source. https://github.com/RocketChat/Rocket.Chat Monty, what kind of evaluation would you guys need? I might be able to help. On Wed, Aug 1, 2018 at 9:54 AM, Monty Taylor wrote: > On 08/01/2018 07:44 AM, Doug Hellmann wrote: > >> Excerpts

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 07:44 AM, Doug Hellmann wrote: Excerpts from Andrey Kurilin's message of 2018-08-01 15:21:37 +0300: ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur : On 08/01/2018 12:49 PM, Andrey Kurilin wrote: Hey Ian and stackers! ср, 1 авг. 2018 г. в 8:45, Ian Wienand

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 01/08/2018 13:21, Andrey Kurilin wrote: > > > The second link from google search gives an opensource client written in > python https://github.com/raelgc/scudcloud . Also, there is something > which is written in golang. >   > > complete lack of any console clients (ditto), > > >

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 02:21 PM, Andrey Kurilin wrote: ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur >: On 08/01/2018 12:49 PM, Andrey Kurilin wrote: > Hey Ian and stackers! > > ср, 1 авг. 2018 г. в 8:45, Ian Wienand mailto:iwien...@redhat.com> >

Re: [openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

+1 On Wed, Aug 01, 2018 at 01:31:40PM +0200, Giulio Fidente wrote: > Hi, > > I would like to propose Lukas Bezdicka core on TripleO. > > Lukas did a lot work in our tripleoclient, tripleo-common and > tripleo-heat-templates repos to make FFU possible. > > FFU, which is meant to permit upgrades

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Excerpts from Andrey Kurilin's message of 2018-08-01 15:21:37 +0300: > ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur : > > > On 08/01/2018 12:49 PM, Andrey Kurilin wrote: > > > Hey Ian and stackers! > > > > > > ср, 1 авг. 2018 г. в 8:45, Ian Wienand > > >: > > > > > >

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 06:22 AM, Luigi Toscano wrote: On Wednesday, 1 August 2018 12:49:13 CEST Andrey Kurilin wrote: Hey Ian and stackers! ср, 1 авг. 2018 г. в 8:45, Ian Wienand : Hello, It seems freenode is currently receiving a lot of unsolicited traffic across all channels. The freenode team are

Re: [openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

On Wed, Aug 1, 2018 at 7:33 AM Giulio Fidente wrote: > I would like to propose Lukas Bezdicka core on TripleO. > Thanks Giulio for proposing him. I agree Lukas's technical level has been quite impactful in the Fast-Forward-Upgrades effort, and upgrades in general. Also his strong experience

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur : > On 08/01/2018 12:49 PM, Andrey Kurilin wrote: > > Hey Ian and stackers! > > > > ср, 1 авг. 2018 г. в 8:45, Ian Wienand > >: > > > > Hello, > > > > It seems freenode is currently receiving a lot of unsolicited

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On Wednesday, 1 August 2018 13:12:49 CEST András Kövi wrote: > These are not just spam messages. At least the ones hitting Mistral are > pedophile content. This must be reported. Can someone help me where? > THX, > A They are already known: https://freenode.net/news/spambot-attack -- Luigi

Re: [openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

+1! On 1.8.2018 13:31, Giulio Fidente wrote: Hi, I would like to propose Lukas Bezdicka core on TripleO. Lukas did a lot work in our tripleoclient, tripleo-common and tripleo-heat-templates repos to make FFU possible. FFU, which is meant to permit upgrades from Newton to Queens, requires in

Re: [openstack-dev] [Tacker] - TACKER + NETWORKING_SFC + NSH

Currently, Tacker does not support NSH. This feature will implement in the future. On Wed, Aug 1, 2018 at 3:17 AM william sales wrote: > Hello guys, > > is there any version of Tacker that allows the use of networking_sfc with > NSH? > > Thankful. > > William Sales >

Re: [openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

+1 I thought he was already core. On Wed, Aug 1, 2018 at 7:33 AM Giulio Fidente wrote: > > Hi, > > I would like to propose Lukas Bezdicka core on TripleO. > > Lukas did a lot work in our tripleoclient, tripleo-common and > tripleo-heat-templates repos to make FFU possible. > > FFU, which is meant

[openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

Hi, I would like to propose Lukas Bezdicka core on TripleO. Lukas did a lot work in our tripleoclient, tripleo-common and tripleo-heat-templates repos to make FFU possible. FFU, which is meant to permit upgrades from Newton to Queens, requires in depth understanding of many TripleO components

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On Wednesday, 1 August 2018 12:49:13 CEST Andrey Kurilin wrote: > Hey Ian and stackers! > > ср, 1 авг. 2018 г. в 8:45, Ian Wienand : > > Hello, > > > > It seems freenode is currently receiving a lot of unsolicited traffic > > across all channels. The freenode team are aware [1] and doing their

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

These are not just spam messages. At least the ones hitting Mistral are pedophile content. This must be reported. Can someone help me where? THX, A Andrey Kurilin ezt írta (időpont: 2018. aug. 1., Sze, 12:49): > Hey Ian and stackers! > > ср, 1 авг. 2018 г. в 8:45, Ian Wienand : > >> Hello, >>

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 12:49 PM, Andrey Kurilin wrote: Hey Ian and stackers! ср, 1 авг. 2018 г. в 8:45, Ian Wienand >: Hello, It seems freenode is currently receiving a lot of unsolicited traffic across all channels.  The freenode team are aware [1] and doing

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Hey Ian and stackers! ср, 1 авг. 2018 г. в 8:45, Ian Wienand : > Hello, > > It seems freenode is currently receiving a lot of unsolicited traffic > across all channels. The freenode team are aware [1] and doing their > best. > > There are not really a lot of options. We can set "+r" on

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Is it possible to ignore message or kick users by keywords? It seems that most messages are more or less the same and include a few URLs that are unlikely to appear in a normal conversation. On 08/01/2018 07:45 AM, Ian Wienand wrote: Hello, It seems freenode is currently receiving a lot of

[openstack-dev] [mistral] Mistral Monthly August 2018

Hey everyone! It is time to wrap-up the last month and have a look and see what has happened. # General News We are now close to the end of the Rocky release cycle! It has been a pleasure serving at the PTL and it looks like you are stuck with me for Stein :) -

Re: [openstack-dev] [openstack-ansible] Change in our IRC channel

Maybe such change should be considered to be done globally on all OpenStack channels? > Wiadomość napisana przez jean-phili...@evrard.me w dniu 01.08.2018, o godz. > 10:13: > > Hello everyone, > > Due to a continuously increasing spam [0] on our IRC channels, I have decided > to make our

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On Wednesday, 1 August 2018 07:45:02 CEST Ian Wienand wrote: > Hello, > > It seems freenode is currently receiving a lot of unsolicited traffic > across all channels. The freenode team are aware [1] and doing their > best. > > There are not really a lot of options. We can set "+r" on channels

[openstack-dev] [openstack-ansible] Change in our IRC channel

Hello everyone, Due to a continuously increasing spam [0] on our IRC channels, I have decided to make our channel (#openstack-ansible on freenode) only joinable by Freenode's nickserv registered users. I am sorry for the inconvenience, as it will now be harder to reach us (but it's not that

[openstack-dev] [watcher] no weekly meeting today

Hi folks, I’m not able to run weekly meeting today because of vacation. Let’s meet in the next week on Wednesday. Best regards, Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [taas] cancel the weekly meeting officially

hi, please see https://review.openstack.org/#/c/578328/ and comment on it if you have any opinions. thank you. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: