Re: [openstack-dev] [all]-ish : Updates required for readthedocs publishers

What is the process once webhook_id is added to project's zuul.yaml? Should I propose a change into project-config/zuul.d/projects.yaml or it will be done automatically? BTW (not completely related to this topic, but since I'm touching zuul.yaml anyway) - what are the best practices for non-offici

[openstack-dev] [DriverLog] DriverLog future

Hi! For those who do not know, DriverLog is a community registry of 3rd-party drivers for OpenStack hosted together with Stackalytics [1]. The project started 4 years ago and by now contains information about 220 drivers. The data from DriverLog is also consumed by official Marketplace [2]. Here

Re: [openstack-dev] Pike release update on driverlog/etc/default_data.json

Hi Sumit, It's just been done in https://review.openstack.org/#/c/500670/3 ("Update Dell EMC drivers info"). Best regards, Ilya 2017-09-06 10:43 GMT+02:00 Shatwara, Sumit : > Hi Team, > > > > When will the details related to Pike release be added in “releases” > section of etc/default_data.json

Re: [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing

rsion_2/plan.html#reliability-testing-version-2 * example of report: https://docs.openstack.org/performance-docs/latest/test_results/reliability/version_2/reports/neutron/create_and_list_networks_with_kill_mysql_service_on_one_node/index.html Best regards, Ilya Shakhat ___

Re: [openstack-dev] [oslo][performance] Proposing tail-based sampling in OSProfiler

tps://www.elastic.co/guide/en/logstash/current/plugins-inputs-udp.html [2] https://www.elastic.co/guide/en/beats/libbeat/current/beats-reference.html Best regards, Ilya Shakhat 2017-08-04 4:04 GMT+02:00 vin...@vn.fujitsu.com : > Hi Rajul, > > > > For the `agent idea`, I think it is very goo

Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman proposal for message bus analysis

Hi Ken, Please check scenarios and reports that exist in Performance Docs. In particular you may be interested in: * O.M.Simulator - https://github.com/openstack/oslo.messaging/blob/master/tools/simulator.py * MQ performance scenario - https://docs.openstack.org/developer/performance-docs/test_

Re: [openstack-dev] [Shaker] Shaker Image Builder fails in Ocata due to OS::Glance::Image deprecation

ce v1 is not available. The behavior can also be enforced by --image-builder-mode parameter. Thanks, Ilya 2017-02-03 13:16 GMT+04:00 Ilya Shakhat : > Starting Ocata, looks like only glance v2 is enabled by default. This >> breaks the shaker image builder template since we make use o

Re: [openstack-dev] [karbor][stackalytics] Karbor Missing Commits in Stackalytics

Sure, I'll take a look at this. --Ilya 2017-02-09 13:47 GMT+04:00 Zhenguo Niu : > After the rename of Nimble to Mogan, all git-related stats are lost as > well. > > http://stackalytics.com/?metric=commits&project_type=opensta > ck-others&module=mogan > > Ilya, Can you please assist with rectifyi

Re: [openstack-dev] [Shaker] Shaker Image Builder fails in Ocata due to OS::Glance::Image deprecation

> > Starting Ocata, looks like only glance v2 is enabled by default. This > breaks the shaker image builder template since we make use of the resource > type OS::Glance::Image and creating images from url links is not > supported in v2. How do we want deal with this? Maybe have the user pass in > t

Re: [openstack-dev] [Performance][Shaker]

Hi Sai, In UDP testing PPS represents packets sent by iperf client to server. Loss is the percentage of packets that were not received by server (more specifically the server tracks packets and sums gaps between of them, https://github.com/esnet/iperf/blob/3.0.7/src/iperf_udp.c#L64). While report

Re: [openstack-dev] [Performance][shaker] Triangular topology

realized that I missed a proper subjet to the thread :(. > If this thread continue it's maybe better to change that. > > - Mail original - > > De: "Ilya Shakhat" > > À: "OpenStack Development Mailing List (not for usage questions)" < > op

Re: [openstack-dev] [stackalytics][neutron] some big tent projects included into 'Neutron Official'

Hi Ihar, This sounds like a bug - the contents of official group should be in sync with the governance repo. I'll take a look what went wrong with it. Thanks, Ilya 2016-11-26 2:28 GMT+03:00 Ihar Hrachyshka : > Hi all, > > I am looking at http://stackalytics.com/?project_type=openstack&module= >

Re: [openstack-dev] [Performance][shaker]

Hi Matt, Out of the box Shaker doesn't support such topology. It shouldn't be hard to implement though. Let me check what needs to be done. Thanks, Ilya 2016-11-24 13:49 GMT+03:00 Matthieu Simonin : > Hello, > > I'm looking to shaker capabilities and I'm wondering if this kind > of accomodation

[openstack-dev] [QA][os-faults] OpenStack destructive and reliability testing announcement

Hello, A while ago we've introduced a new library called os-faults [1]. The main purpose of the library is to provide a unified API to perform different destructive actions in OpenStack cloud. The library can do service-related operations (e.g. kill particular service) and node-related (e.g. switc

Re: [openstack-dev] [stackalytics]

Roman, There are certainly exist a bug in stackalytics [1]. Current contribution > to different openstack/* projects was counted for deb-* . Now all affected > commit records on stackalytics are removed from deb-* projects, but they > should be moved to proper non-deb projects. Is there any one

Re: [openstack-dev] [stackalytics] [deb] [packaging] OpenStack contribution stats skewed by deb-* projects

2016-09-21 14:37 GMT+03:00 Thierry Carrez : > Ilya Shakhat wrote: > > Hi, > > > > tldr; Commits stats are significantly skewed by deb-* projects > > (http://stackalytics.com/?metric=commits&module=packaging-deb-group) > > > > By default Stackalytics pro

[openstack-dev] [stackalytics] [deb] [packaging] OpenStack contribution stats skewed by deb-* projects

Hi, tldr; Commits stats are significantly skewed by deb-* projects ( http://stackalytics.com/?metric=commits&module=packaging-deb-group) By default Stackalytics processes commits from project's master branch. For some "old core" projects there is configuration to process stable branches as well.

Re: [openstack-dev] Cloud Reliability and Resilience for OpenStack (Fault Injection, Chaos Engineering, and Google SRE)

Hi Jorge, Reliability testing automation is the thing that OpenStack Performance team [1] is working right now. The whole solution will consist of: * Fault injection library os-failures [2] that provides an API to do different kind of faults on different OpenStack clouds. The lib is currently und

Re: [openstack-dev] [stackalytics] Proposal for some code/feature changes

Hi Nikhil, 2016-04-12 5:59 GMT+03:00 Nikhil Komawar : > Hello, > > I was hoping to make some changes to the stackalytics dashboard > specifically of this type [1] following my requested suggestions here > [2]; possibly add a few extra columns for +0s and just Bot +1s. I think > having this info g

Re: [openstack-dev] [i18n][stackalytics] Translations metrics

2016-02-25 13:42 GMT+03:00 Ying Chun Guo : > Is it possible to link two IDs with email ? > > The link is possible by adding user profile into Stackalytics default_data.json. The patch needs to be similar to https://review.openstack.org/#/c/284638/1/etc/default_data.json. Basically it lists all use

Re: [openstack-dev] [i18n][stackalytics] Translations metrics

Hi Shu, Thanks for bringing attention to this. The reason is that Stackalytics tries to match Zanata id with LP id, and expects both to be the same. But if they are different (or point to different people) then a static profile should help. I will add the one for you soon. Best regards, Ilya

Re: [openstack-dev] [infra][stackalytics] some projects not visible in stackalytics now

renamed soon: https://review.openstack.org/#/c/265741/ Thanks, Ilya Shakhat > -- > Thierry Carrez (ttx) > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: ope

Re: [openstack-dev] [OpenStack-Infra] [infra][stackalytics] some projects not visible in stackalytics now

Hi everyone! It appears that Stackalytics host is banned by review.openstack.org. It gets "Received disconnect from 2001:4800:7818:102:be76:4eff:fe05:9b12: 7: Too many concurrent connections" while attempting to execute "gerrit" command. As consequence Stackalytics fails to retrieve list of projec

Re: [openstack-dev] [all] how to add/list drivers @ https://www.openstack.org/marketplace/drivers/

Community-maintained list of drivers exists within the project DriverLog. The UI is available at http://stackalytics.com/report/driverlog , it has all options to filter the data. Thanks, Ilya 2015-11-25 11:48 GMT+03:00 Mohan Kumar : > Hi Team, > > In the following link, i can see only some ven

Re: [openstack-dev] [stackalytics] [metrics] Review metrics: average numbers

Hi Mike, > Do I understand right, that average numbers > > here are calculated out of open reviews, not total number of reviews? Average numbers are calculated for reviews within the group. But I'd expect them to be "time since the last vote", not "time when patch proposed" as they do now. > Th

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

2015-11-11 16:38 GMT+03:00 Thierry Carrez : > > date_fix_committed is probably not set if we directly switch the bug to > "Fix released", and that is what we plan to do now with Launchpad bugs. > > We might therefore need a backward-compatible patch to Stackalytics so > that it uses (date_fix_comm

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

Doug, You are right, there should not be any changes in the stats. Bugs are mapped to release only by date, target milestone is not taken into account. For resolved bugs metric Stackalytics uses 'date_fix_commited' field, for filed bugs metric - 'date_created'. Thanks, Ilya 2015-11-10 0:53 GMT+0

[openstack-dev] Stackalytics 0.9: new features and improvements

Hi all, During the last month we've made a number of changes and improvements in Stackalytics that deserve version tag and special announcement. The most important feature is tracking history of official projects list - highly demanded after shift to 'big tent' model. The full list of changes bel

Re: [openstack-dev] [stackalytics] Broken stats after project rename

Hi Jesse, Thanks for letting know. Stackalytics team will fix the issue during the day. --Ilya 2015-09-30 12:19 GMT+03:00 Jesse Pretorius : > Hi everyone, > > After the rename of os-ansible-deployment to openstack-ansible it appears > that all git-related stats (eg: commits) prior to the rename

Re: [openstack-dev] [Stackalytics] Complementary projects

Some reasons of having complementary projects in Stackalytics: * to compare efforts in other communities with OpenStack - just to feed curiosity on what is larger OpenStack or Kubernetes? * to light interest to contribute to projects that OpenStack depends on, like OVS and Ansible. * to keep an

[openstack-dev] [Neutron] Data-plane performance testing with Shaker

Hi all! Let me introduce you Shaker - a tool for data-plane performance testing in OpenStack. The motivation behind it is to have a simple way for measuring networking bandwidth between instances. Shaker key features are: 1. *User-defined topology*. The topology is specified as Heat template, so

Re: [openstack-dev] [Fuel] Logstash and grok patterns

Hi, Here are some suggestions from my experience: 1. Input patterns could be simplified by * matches, e.g.: file { path => [ "/var/log/remote/*.domain.tld/neutron*" ] exclude => "*.gz" } 2. Logs could be parsed by the following pattern: grok { patterns_dir => "patterns" match

Re: [openstack-dev] EOL and Stable Contributions (was Juno is flubber at the gate)

> > > Secondly, it's difficult to get stack-analytics credit for back > > ports, as the preferred method is to cherry pick the code, and > > that keeps the original author's name. I've personally gotten a > > few commits into stable, but have nothing to show for it in > > stack-analytics (if I'm do

[openstack-dev] [Rally] Load testing of dependent resources

Ralliers, I'd like to share with you an idea on how to test dependent resources. Let's consider the following example: there is a network and ports belonging to it and we would like to test port creation process. Currently I see 2 options of writing scenario: a) The scenario creates network and

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

2014-06-30 19:17 GMT+04:00 Kurt Taylor : > Dan Smith wrote on 06/27/2014 12:33:48 PM: > > If it really does show up right in Gerrit as if it were integrated, > > then that would be fine with me. I think the biggest problem we have > > right now is that a lot of the CI systems are very inconsisten

[openstack-dev] [neutron] [third-party] Neutron 3rd Party CI status dashboard

Hi! During last couple weeks there is an increasing demand on tracking 3rd-party CI statuses. We at Stackalytics decided to be in trend and (with some inspiration from Salvatore's proposal) implemented report that shows summary on external CI status. The initial version is available for Neutron -

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

Let me explain how Stackalytics grouping works. Most of groups are created from the official programs .yaml. Every program turns into item in the module list (colored in violet), for example 'Nova Compute' is a group containing 'nova', 'python-novaclient' and 'nova-specs'. E

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

> > > However, it would be great if we could start devising a solution for > having > > "health" reports from the various CI systems. > > This report should report the following kind of information: > > - timestamp of last run > > - timestamp of last vote (a system might start job which then get ab

Re: [openstack-dev] [DriverLog] What to fix and when

Anita, I put the meeting on my schedule. Jay, can you be a back-up person? Thanks, Ilya 2014-06-10 22:18 GMT+04:00 Anita Kuno : > On 06/10/2014 01:58 PM, Jay Pipes wrote: > > Stackers, > > > > OK, we are fully aware that there are problems with the early DriverLog > > data that is shown in the

Re: [openstack-dev] [neutron] [driverlog] Tail-f CI and it's lack of running and it's DriverLog status

Hi! Tail-f driver seems to be configured correctly. DriverLog will poll Gerrit in the next 4 hours and update driver details screen. Regarding green mark on summary screen - it is shown for those drivers that have configured CI and CI ran at least once. But it doesn't take into account when the l

Re: [openstack-dev] [DriverLog][nova][neutron][cinder] Call for vendor participation please

Hi Akihiro, Please see my comments inline. 2014-05-07 10:35 GMT+04:00 Akihiro Motoki : > Hi, > > Thanks for the effort. > While I am looking the website and the driver database, > I have a couple of questions and suggestions. > > - Is it better to include "trunk" (= Juno) in "releases" in each d

[openstack-dev] [Fuel] Rabbit in HA mode for Glance

Hi, Recently Glance switched to oslo.messaging library and as benefit got support of HA for Rabbit queues (parameter 'rabbit_ha_queues'). There are similar parameters in other projects (Nova, Heat, Ceilometer) and they are configured in corresponding manifest files. Are there plans to add the same

Re: [openstack-dev] [savanna] Nominate Andrew Lazarew for savanna-core

2014-02-21 16:46 GMT+04:00 Matthew Farrellee : > > fyi, some of those links don't work, but these do, > > http://stackalytics.com/report/contribution/savanna-group/30 > http://stackalytics.com/report/contribution/savanna-group/90 > http://stackalytics.com/report/contribution/savanna-group/180 Ye

[openstack-dev] [WSME] Can't install WSME 0.6 due to ipaddr library

Hi Doug, I'm trying to install WSME 0.6, but today it fails due to inability to install ipaddr dependency. Pip output: Downloading/unpacking ipaddr (from WSME) You are installing a potentially insecure and unverifiable file. Future versions of pip will default to disallowing insecure files. H

Re: [openstack-dev] Reviewing reviewers

And it is worth mentioning activity report in Stackalytics, the link to it is located in contribution summary block on user's statistics screen. The report looks like http://stackalytics.com/report/users/zaneb and contains all reviews, posted patches, commits, emails and blueprints. Thanks, Ilya

[openstack-dev] Stackalytics 0.4 released!

Hello everyone! Stackalytics team is happy to announce the release of version 0.4. This release is completely dedicated to different types of reports. We added highly demanded top reviewers chart acknowledged as an essential tool for finding most active reviewers (ex. http://stackalytics.com/repor

Re: [openstack-dev] [infra] How to determine patch set load for a given project

Matt, As an option you may estimate the load using Stackalytics data on number of commits - http://stackalytics.com/?release=icehouse&metric=commits&project_type=all&module=sqlalchemy-migrateNumber of commits is certainly less than number of patches, but for project sqlalchemy-migrate the multipli

Re: [openstack-dev] [stackalytics] Official Programs tag?

Sean, Currently the grouping is two-layer: the higher is to split between openstack-hosted and stackforge-hosted projects, the lower is to split core, incubation, docs, etc. The grouping may be not so accurate since it needs to comply with the latest changes in integrated / incubated projects (bug

[openstack-dev] [stackalytics] team meeting minutes October 21

alytics.2013-10-21-15.01.txt Log: http://eavesdrop.openstack.org/meetings/stackalytics/2013/stackalytics.2013-10-21-15.01.log.html Sincerely yours, Ilya Shakhat ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.o

[openstack-dev] [Stackalytics] 0.3 release

Hello everyone! Together with Havana we are glad to present a new version of Stackalytics - 0.3. In this release the service is extended by email and blueprint processing. Blueprints are metered by popularity - the number of times they are mentioned in either emails o

Re: [openstack-dev] OpenStack Heat - Email deleted by mistake

Maty, You can always check list archive at http://lists.openstack.org/pipermail/openstack-dev/2013-September/ Ilya. 2013/9/17 GROSZ, Maty (Maty) > All, > > ** ** > > Earlier this morning (Middle east time) we received an email regarding a > Heat document that is kept within Google by ope

Re: [openstack-dev] [Tuskar] Weekly IRC meetings

Oleg, Savanna meeting is on Thursdays at 18:00 UTC ( https://wiki.openstack.org/wiki/Meetings#Savanna_.28Hadoop.29_meeting) Ilya. 2013/9/5 Oleg Gelbukh > Tomas, > > Thanks for very interesting project and this meeting as opportunity to > follow its progress! > > Just to clarify, it looks like

[openstack-dev] [Stackalytics] 0.2 release

Hello everyone! We are excited to present the new release of Stackalytics- 0.2. One of major features of this release is review processing. It gives data on who reviews most, distribution of reviews by engineers or by modules, what is the ratio of positive to negative

Re: [openstack-dev] [OpenStack][python-quantumclient] unit test question

in_state_up': True}} Ilya. 2013/6/27 Kuang-Ching Wang > Ilya, thanks for catching this - I took care of the plural, though the > POST error earlier still persists. > > Any idea why the expected call breaks into two sections - the call itself > and the body separated? > > K

Re: [openstack-dev] [OpenStack][python-quantumclient] unit test question

Hi KC, There's one more place in code that relies on rule of making plurals, it adds letter 's' producing 'policys' instead of 'policies'. The code is in quantum/v2_0/__init__.py line # 511. Thanks, Ilya 2013/6/26 Kuang-Ching Wang > Hi Eugene, > > thanks for looking into this. I just pushed m

[openstack-dev] Misspelled pbr parameter in quantum setup.cfg

Hi Monty, I've noticed that pbr section of Quantum's setup.cfg contains misspelled parameter: *[pbr]* *single-version-externally-mananged = true* (extra 'n' in word managed) Should this parameter be fixed or removed completely? Ilya ___ OpenStack-dev ma