Re: [openstack-dev] [sahara] PTL out for a week

On Wednesday, 10 October 2018 22:42:03 CEST Telles Nobrega wrote: > Hi all, > > I'm taking PTO from tomorrow until Monday Oct 22nd. I won't cancel the > meeting yet but let me know if you want me to. No strong opinions about it. I will be around; if there are people asking for it, I can start

Re: [openstack-dev] [placement] [infra] [qa] tuning some zuul jobs from "it works" to "proper"

On Thursday, 20 September 2018 04:47:20 CEST Matthew Treinish wrote: > On Thu, Sep 20, 2018 at 11:11:12AM +0900, Ghanshyam Mann wrote: > > On Wed, 19 Sep 2018 23:29:46 +0900 Monty Taylor > > wrote > > > > On 09/19/2018 09:23 AM, Monty Taylor wrote: > > > > On 09/19/2018 08:25 AM,

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

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

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

On Tuesday, 26 June 2018 11:52:53 CEST Ghanshyam Mann wrote: > On Tue, 26 Jun 2018 18:28:03 +0900 Luigi Toscano > wrote > > On Tuesday, 26 June 2018 11:18:52 CEST Ghanshyam Mann wrote: > > > Hello Everyone, > > > > > > In Queens cycle, com

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

On Tuesday, 26 June 2018 11:18:52 CEST Ghanshyam Mann wrote: > Hello Everyone, > > In Queens cycle, community goal to split the Tempest Plugin has been > completed [1] and i think almost all the projects have separate repo for > tempest plugin [2]. Which means each tempest plugins are being

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

On Friday, 22 June 2018 05:00:16 CEST Joe Topjian wrote: > Hello, > > I originally posted this to the general openstack list to get a sanity > check on what I was seeing. Jeremy F reached out and confirmed that, so I'm > going to re-post the details here to begin a discussion. Hi, thanks for

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

On Wednesday, 30 May 2018 17:13:41 CEST Zane Bitter wrote: > On 30/05/18 00:52, Cédric Jeanneret wrote: > >> Another issue is that if the original author needs to rev the patch > >> again for any reason, they then need to figure out how to check out the > >> modified patch. This requires a fairly

Re: [openstack-dev] [infra][qa][requirements] Pip 10 is on the way

On Thursday, 5 April 2018 22:44:32 CEST Jeremy Stanley wrote: > On 2018-04-05 13:27:13 -0700 (-0700), Clark Boylan wrote: > [...] > > > I'm not sure what the best option is here but if we can show that > > system site packages with virtualenvs is viable with pip10 and > > people want to move

[openstack-dev] [sahara] FFE - Adding Ambari 2.4.2.0 to image gen

Hi, I'd like to request a feature exception for https://review.openstack.org/#/c/529442/ I finally managed to test it, and the generated image with Ambari 2.4.2.0 can spawn clusters with both HDP 2.4 and HDP 2.3. There are some issues when Hive is involved, but I think that they are not

Re: [openstack-dev] [sahara] Pre-PTG Doc Day

On Tuesday, 6 February 2018 12:53:17 CET Telles Nobrega wrote: > Hi folks, > > as we discussed in our last meeting, tomorrow (Wednesday 7th) we are going > to do a first overview of our documentation in order to gather the maximum > information of where we need to fix, add or remove stuff so we

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On Thursday, 11 January 2018 23:52:00 CET Matt Riedemann wrote: > On 1/11/2018 10:36 AM, Colleen Murphy wrote: > > 1) All trademark-related tests should go in the tempest repo, in > > accordance > > > > with the original resolution. This would mean that even projects that > > have > >

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

- Original Message - > On 12/14/2017 9:38 AM, Luigi Toscano wrote: > > And the QE in me says that there are enough moving parts around for the > > integration testing (because CD yes, but the resources are limited) that a > > longer cycle with a longer time betwe

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

- Original Message - > On Dec 13, 2017, at 12:13 PM, Tim Bell wrote: > > > There is a risk that deployment to production is delayed, and therefore > > feedback is delayed and the wait for the ‘initial bug fixes before we > > deploy to prod’ gets longer. > > There is

Re: [openstack-dev] [sahara] [api] [sdks] [keystone] Sahara APIv2: service discovery

On Friday, 1 December 2017 01:34:36 CET Monty Taylor wrote: > First and most importantly you need to update python-saharaclient to > make sure it can handle it an unversioned endpoint in the catalog (by > doing discovery) - and that if it finds an unversioned endpoint in the > catalog it knows to

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

On Saturday, 7 October 2017 12:30:54 CEST Thomas Goirand wrote: > On 10/03/2017 03:07 PM, Luigi Toscano wrote: > >> Why not? Simply because installing config files in /usr/etc is silly. > >> The question would rather be: why not accepting the PBR patch... > > > &g

Re: [openstack-dev] [sahara] Meeting time

On Wednesday, 4 October 2017 19:23:13 CEST Telles Nobrega wrote: > Hi saharans and meeting time organizers, > > during the Denver PTG the sahara team agreed that the best meeting time for > the whole team is on Thursday at 14:00UTC. > > Currently we work with a changing meeting time, one week it

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

On Tuesday, 3 October 2017 14:31:05 CEST Thomas Goirand wrote: > On 10/02/2017 02:04 PM, Luigi Toscano wrote: > > Why not? Even if it does not fix the issue for proper installations, > > - it does not provent people from copying the files somewhere else (it > > happened in

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

On Monday, 2 October 2017 13:28:17 CEST Thomas Goirand wrote: > On 09/28/2017 04:50 PM, Jesse Pretorius wrote: > > There’s some history around this discussion [1], but times have changed > > and the purpose of the patches I’m submitting is slightly different [2] > > as far as I can see – it’s a

Re: [openstack-dev] [neutron] [tests] [tempest] Neutron dvr tempest test problem

On Thursday, 24 August 2017 12:51:05 CEST Ning Yao wrote: > Hi, all > > I encounter a problem about neutron tempest test. I run the tempest > neutron plugin test against my self-build OpenStack, and I find that > tempest will run the dvr test and report NotImplementedERROR. I dig > into the test

Re: [openstack-dev] [docs] [training-guides] Moving from Hieroglyph for rendering slides

On Thursday, 3 August 2017 18:18:31 CEST Pančur, Matjaž wrote: > Hi all, > > Andreas filed a bug report [1] that can impact what will we use to render > slides for Upstream University and other training related slide material in > the future. We’ve already had many discussions at Training guides

[openstack-dev] [sahara][keystone][oslo.config] Access to keystone_authtoken config options (required for Sahara trust)

Hi, I was trying to deploy Sahara/Pike using TripleO and the cluster creation does not work, while it works on Sahara gates. Cluster operation uses trust (see http://specs.openstack.org/openstack/sahara-specs/specs/liberty/cluster-creation-with-trust.html) The difference between the two

Re: [OpenStack-Infra] Space for Sahara artifacts (disk images)

On Friday, 26 May 2017 15:27:02 CEST Jeremy Stanley wrote: > On 2017-04-28 14:39:51 +0200 (+0200), Luigi Toscano wrote: > > The Sahara project has been providing pre-built images containing > > the Hadoop/ Spark/$bigdata frameworks since the beginning of the > > proje

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On Monday, 15 May 2017 21:12:16 CEST Doug Hellmann wrote: > Excerpts from Michał Jastrzębski's message of 2017-05-15 10:52:12 -0700: > > > On 15 May 2017 at 10:34, Doug Hellmann wrote: > > > I'm raising the issue here to get some more input into how to > > > proceed. Do

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thursday, 4 May 2017 20:11:14 CEST Emilien Macchi wrote: > On Thu, May 4, 2017 at 9:41 AM, Dan Prince wrote: > > I like the idea of getting pingtest out of tripleo.sh as more of a > > stand alone tool. I would support an effort that re-implemented it... > > and using

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thursday, 4 May 2017 15:41:04 CEST Dan Prince wrote: > On Thu, 2017-05-04 at 03:11 -0400, Luigi Toscano wrote: > > - Original Message - > > > > > > > > Running a subset of Tempest tests isn't the same thing as designing > > > (and owning) y

Re: [openstack-dev] [tripleo] pingtest vs tempest

- Original Message - > On Wed, 2017-05-03 at 17:53 -0400, Emilien Macchi wrote: > > (cross-posting) > > > Instead of running the Pingtest, we would execute a Tempest Scenario > > that boot an instance from volume (like Pingstest is already doing) > > and see how it goes (in term of

Re: [openstack-dev] [qa][heat][murano][daisycloud] Removing Heat support from Tempest

- Original Message - > > > On Tue, May 2, 2017 at 5:27 AM, MONTEIRO, FELIPE C < fm5...@att.com > wrote: > > >> Murano currently uses the Tempest orchestration client for its scenario >> Tempest tests [0], which are not turned on by default in the Murano Tempest >> gate due to resource

[OpenStack-Infra] Space for Sahara artifacts (disk images)

Hi, The Sahara project has been providing pre-built images containing the Hadoop/ Spark/$bigdata frameworks since the beginning of the project, so that users can be immediately productive. The generated qcow2 images have been living so far here: http://sahara-files.mirantis.com/images/upstream/

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Monday, 17 April 2017 18:28:24 CEST Ben Nemec wrote: > On 04/17/2017 10:51 AM, Emilien Macchi wrote: > > We haven't got much feedback from TripleO core reviewers, who are > > usually more involved on this topic. I'll give a chance to let them > > talk because we take some actions based on the

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thursday, 6 April 2017 13:29:32 CEST Justin Kilpatrick wrote: > Maybe I'm getting a little off topic with this question, but why was > Tempest removed last time? > > I'm not well versed in the history of this discussion, but from what I > understand Tempest in the gate has > been an off and on

Re: [openstack-dev] [Sahara][infra] Jenkins based 3rd party CIs

On Monday, 6 March 2017 20:05:18 CET James E. Blair wrote: > Telles Nobrega writes: > > Hello, > > > > we from Sahara use the compatibility layer with Zuulv2.5 and we are > > wondering if with the change to Zuulv3 this compatibility layer will still > > be maintained. > > If

Re: [openstack-dev] [QA]Refactoring Scenarios manager.py

On Wednesday, 1 March 2017 13:35:26 CET Jordan Pittier wrote: > On Wed, Mar 1, 2017 at 3:57 AM, Ghanshyam Mann > > > 2. Start refactoring the scenario framework by adding more and more helper > > function under /common or lib. > > Starting a "framework" (each time I see

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

- Original Message - > Excerpts from Shamail Tahir's message of 2017-02-27 00:44:44 -0500: > > Hi Clint, > > > > On Mon, Feb 27, 2017 at 12:25 AM, Clint Byrum wrote: > > > > > Excerpts from Matt Riedemann's message of 2017-02-26 19:48:50 -0600: > > > > On 2/26/2017

Re: [openstack-dev] [Sahara][QA] Tests broken after a devstack change

On Tuesday, 21 February 2017 11:18:12 CET Sean Dague wrote: > On 02/21/2017 10:45 AM, Luigi Toscano wrote: > > Hi team (mostly at the PTG), > > > > you probably noticed that the jobs has been failing since February 17th. > > The reason can be traced back to this change

[openstack-dev] [Sahara][QA] Tests broken after a devstack change

Hi team (mostly at the PTG), you probably noticed that the jobs has been failing since February 17th. The reason can be traced back to this change in devstack: https://review.openstack.org/#/c/433272/ I tried to revert it and rerun a job after setting the revert and dependency, and indeed

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

On Friday, 2 December 2016 14:42:31 CET Matt Riedemann wrote: > But like we recently talked about the stable team meetings, we don't > really need to be in a separate -alt room for those when we have the > channel and anyone that cares about stable enough to be in the meeting > is already in that

Re: [openstack-dev] [Rally][all] Gitter as an alternative way for communication

On Thursday, 24 November 2016 16:20:32 CET Andrey Kurilin wrote: > Hi folks! > > I'm happy to announce our new chats at gitter.im : > > - https://gitter.im/rally-dev/Lobby # main chat for regular > communication > - https://gitter.im/rally-dev/statuses # chat for gerrit notifications > >

[openstack-dev] [sahara][qa] Unblocking Sahara gate

Hi all, the removal of the Sahara tests from Tempest [1] broke the tests now in sahara-tests, and basically I underestimated the fall-out of the removal. Apart from a minor issue due to the wrong exception [2], the key issue comes from the option groups in tempest.conf, which are defined as

Re: [openstack-dev] [ironic][docs] What is the policy for backporting docs changes to stable branches?

On Wednesday, 5 October 2016 15:31:50 CEST Pavlo Shchelokovskyy wrote: > Hi all, > > lately I realized that docs for two of the features I was working on during > Newton cycle are absent from Ironic's new install guide [0]. This is my > fault, and I am sorry for missing that out. Currently I am

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

On Friday, 9 September 2016 14:12:51 CEST Matt Riedemann wrote: > On 9/9/2016 1:58 PM, Ben Swartzlander wrote: > > On 09/08/2016 08:37 PM, Matt Riedemann wrote: > >> On 9/8/2016 7:05 PM, Ravi, Goutham wrote: > >>> Hi, > >>> > >>> > >>> > >>> I was looking for some clarity around backports of

[OpenStack-Infra] Importing code with history (sahara-tests)

Hi, tl;dr this is request for help with a procedure which should take 10 minutes to a member of openstack-infra-core. Long version: I'm one of the upstream maintainers of sahara-core and I'd like to import some code from two repository into another but keeping the history. (from sahara and from

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wednesday, 10 August 2016 12:00:41 CEST Ben Swartzlander wrote: > On 08/10/2016 11:33 AM, Luigi Toscano wrote: > > On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote: > >> Luigi Toscano <ltosc...@redhat.com> wrote: > >>> On Wednesday, 10 August

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote: > Luigi Toscano <ltosc...@redhat.com> wrote: > > On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: > >> On 08/10/2016 04:33 AM, Duncan Thomas wrote: > >>> So I tried to get into

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: > On 08/10/2016 04:33 AM, Duncan Thomas wrote: > > So I tried to get into helping with the cinder stable tree for a while, > > and while I wasn't very successful (lack of time and an inability to > > convince my employer it should

Re: [openstack-dev] [sahara][heat][infra] breakage of Sahara gate and images from openstack.org

On Monday, 1 August 2016 10:56:21 CEST Zane Bitter wrote: > On 29/07/16 13:12, Luigi Toscano wrote: > > Hi all, > > the Sahara jobs on the gate run the scenario tests (from sahara-tests) > > using the fake plugin, so no real Hadoop/Spark/BigData operations are > > per

[openstack-dev] [sahara][heat][infra] breakage of Sahara gate and images from openstack.org

Hi all, the Sahara jobs on the gate run the scenario tests (from sahara-tests) using the fake plugin, so no real Hadoop/Spark/BigData operations are performed, but other the other expected operations are executed on the image. In order to do this we used for long time this image:

Re: [openstack-dev] [all][tc] Equal Chances for all projects (was Plugins for all)

On Tuesday, 26 July 2016 13:23:05 CEST Hayes, Graham wrote: > On 26/07/2016 14:18, Doug Hellmann wrote: > >>> And just to satisfy my own curiosity, how does someone looking at the > >>> internals of tempest know what's on the stable API and what's not > >>> considered stable? Are the parts of the

Re: [openstack-dev] [all][tc] Equal Chances for all projects (was Plugins for all)

On Tuesday, 26 July 2016 08:34:27 CEST Doug Hellmann wrote: > Excerpts from Andrea Frittoli's message of 2016-07-26 10:24:07 +: > > > > What still requires work in Tempest is the stable interface. Because > > plugins are not in the Tempest tree, the QA team recommend that they use > > only

Re: [openstack-dev] [tc][all] Plugins for all

On Friday, 15 July 2016 17:05:41 CEST Hayes, Graham wrote: > On 15/07/2016 17:52, Luigi Toscano wrote: > > On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: > >> On 15/07/2016 17:10, Andrew Laski wrote: > >>>> Tempest plugins are another example. Approxim

Re: [openstack-dev] [tc][all] Plugins for all

On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: > On 15/07/2016 17:10, Andrew Laski wrote: > >> Tempest plugins are another example. Approximately 30 of the 36 > >> current plugins are using resources that are not supposed to be > >> used, and are an unstable interface. Projects in

Re: [openstack-dev] [release][sahara] sahara-tests 0.1.0 release (newton)

On Wednesday 13 of April 2016 09:42:25 dava...@gmail.com wrote: > We are gleeful to announce the release of: > > sahara-tests 0.1.0: Sahara tests > > This is the first release of sahara-tests. This release is part of the > newton release series. > > For more details, please see below. Small

Re: [openstack-dev] [Sahara][QA] Notes about the move of the Sahara Tempest API test to sahara-tests

On Sunday 20 of March 2016 21:07:06 Luigi Toscano wrote: > Hi, Small update on the plan: > > as discussed in the last (two) Sahara meetings, I'm working on moving the > Tempest API tests from the Tempest repository to the new sahara-tests > repository, which contains only (non-te

Re: [openstack-dev] [trove] OpenStack Trove meeting minutes (2016-03-23)

- Original Message - > On Wed, Mar 23, 2016 at 07:52:10PM +, Amrith Kumar wrote: > > The meeting bot died during the meeting and therefore the logs on eavesdrop > > are useless. So I've had to get "Old-Fashioned-Logs(tm)". > > > > Action Items: > > > > #action [all] If you have a

Re: [openstack-dev] [Sahara][QA] Notes about the move of the Sahara Tempest API test to sahara-tests

On Monday 21 of March 2016 10:50:30 Evgeny Sikachev wrote: > Hi, Luigi! > > Thanks for this short spec :) > Changes looking good for me, and I think Sahara-team can help with pushing > this changes to sahara-tests repo. > > But I have a question: why we need to use detached branch for it? A

[openstack-dev] [Sahara][QA] Notes about the move of the Sahara Tempest API test to sahara-tests

Hi, as discussed in the last (two) Sahara meetings, I'm working on moving the Tempest API tests from the Tempest repository to the new sahara-tests repository, which contains only (non-tempest) scenario tests and it's branchless as well. The move is a natural consequence of the Tempest focus

Re: [openstack-dev] [Openstack-stable-maint][stable/liberty][trove] stable/liberty changes in Trove that are ready for merge

- Original Message - > On 03/19/2016 01:43 AM, Tony Breeds wrote: > > On Sun, Mar 13, 2016 at 12:15:23PM +, Amrith Kumar wrote: > >> Hi, > >> > >> Sorry for the blast mail, this is targeted at the stable-maint team. The > >> following five changes are now ready to merge. Two of them

Re: [openstack-dev] [cinder][all] Integration python-*client tests on gates

On Wednesday 02 of March 2016 12:24:57 Ivan Kolodyazhny wrote: > Sean, > > I do understand why we have tempest for python-cinderclient now. > > But my point is: tempest runs more than 200 tests per each cinderclient > change request which takes a lot of time. Why can't we just introduce few >

Re: [openstack-dev] [sahara] update methods

On Wednesday 05 of August 2015 11:14:13 michael mccune wrote: hey all, the recent discussions[1] on updating resources through the rest api has got me thinking that it might be worthwhile to convert the few methods we have implemented to use PATCH instead of PUT. we are starting to create

[openstack-dev] OSPd, post-installation changes/new components

Hi, Are there any suggested steps on how to execute post-deployment (OSPd) tuning of components? I see two possible scenarios, but maybe they are the same: a) configuration changes to a component which is managed by OSPd (cinder, nova, etc); b) installation of additional components (Sahara,

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On Tuesday 14 of July 2015 10:33:18 Ihar Hrachyshka wrote: On 07/14/2015 01:46 AM, Perry, Sean wrote: -Original Message- From: Doug Hellmann I don't *want* to keep 2.6 support around, and I do understand that the requirements work will be made easier. I'm just trying to