Re: [stackalytics] Reported numbers seem inaccurate
Hello All, I first want to thank each and everyone of you for reaching out and sharing the inaccuracies you all have found within Stackalytics, this has helped us tremendously with the efforts to correct these flaws. I am writing this email to directly address each individual that has reached out and shared their concerns with our Stackalytics data. Mark Goddard Michael Johnson Julia Kreger Collen Murphy Clark Boylan Sean Mooney Thierry Carrez Jermey Stanley Arkady Kanvesky (Hopefully, I did not miss anyone) I want to insure everyone that the team is working hard to fix the inaccuracies in some of our data. We are still very much involved in OpenStack and we do read each and every message regarding Stackalytics. As Boris and Sergey mentioned, we found that this occurred due to an outdated production environment. We are currently in the progress of migrating to a new environment, and the data should be corrected. The team and I are sorry for these discrepancies and appreciate you all for bringing this to our attention. Thank you all, for providing links and examples of the inaccuracies. This has helped our efforts greatly in correcting the current issues. It would be great if the community can continue reviewing Stackalytics data and help us provide a better service to all. Once again, we are all very sorry for this and will continue to fix these issues. Cheers, Edward
On Apr 16, 2019, at 4:05 PM, Edward Ionel <eionel@mirantis.com> wrote:
On Tue, Apr 16, 2019 at 2:56 PM Boris Renski <brenski@mirantis.com> wrote: Folks - more specifically, we plan to roll out an update by tomorrow mid-day PT which should fix all the numbers + add aggregate details on Airship project contributions.
Would really appreciate the help of the community to poke around tomorrow afternoon and see if there are still discrepancies.
Sorry about this and thank you for catching it and brining it to our attention.
-Boris
On Tue, Apr 16, 2019 at 1:33 PM Sergey Nikitin <snikitin@mirantis.com> wrote: Hello everyone, As you mentioned there are some inaccuracies in stats on stackalytics.com. It happened because of outdated Prod env. At this moment we are in a process of migration to the new env. All data on this env is fresh and accurate. So the problem will be solved soon.
-- Best Regards, Sergey Nikitin
-- Edward Ionel Marketing Operations Manager Mirantis, Inc. 900 E Hamilton Ave, Suite 650 Campbell, CA 95008 Eionel@mirantis.com www.mirantis.com
Hello everyone, Yesterday we've finished stackalytics migration. Thank you for patience and for notifications about the problem. Now all stats must be accurate. We are working hard to keep stackalytics.com a trusted storage of OpenStack statistics. So if you will find some problems with data again, please tell as and we will fix it ASAP. Sergey On Wed, Apr 17, 2019 at 7:37 AM Edward Ionel <eionel@mirantis.com> wrote:
Hello All,
I first want to thank each and everyone of you for reaching out and sharing the inaccuracies you all have found within Stackalytics, this has helped us tremendously with the efforts to correct these flaws.
I am writing this email to directly address each individual that has reached out and shared their concerns with our Stackalytics data.
Mark Goddard
Michael Johnson
Julia Kreger
Collen Murphy
Clark Boylan
Sean Mooney
Thierry Carrez
Jermey Stanley
Arkady Kanvesky
(Hopefully, I did not miss anyone)
I want to insure everyone that the team is working hard to fix the inaccuracies in some of our data. We are still very much involved in OpenStack and we do read each and every message regarding Stackalytics.
As Boris and Sergey mentioned, we found that this occurred due to an outdated production environment. We are currently in the progress of migrating to a new environment, and the data should be corrected.
The team and I are sorry for these discrepancies and appreciate you all for bringing this to our attention.
Thank you all, for providing links and examples of the inaccuracies. This has helped our efforts greatly in correcting the current issues. It would be great if the community can continue reviewing Stackalytics data and help us provide a better service to all.
Once again, we are all very sorry for this and will continue to fix these issues.
Cheers,
Edward
On Apr 16, 2019, at 4:05 PM, Edward Ionel <eionel@mirantis.com> wrote:
On Tue, Apr 16, 2019 at 2:56 PM Boris Renski <brenski@mirantis.com> wrote:
Folks - more specifically, we plan to roll out an update by tomorrow mid-day PT which should fix all the numbers + add aggregate details on Airship project contributions.
Would really appreciate the help of the community to poke around tomorrow afternoon and see if there are still discrepancies.
Sorry about this and thank you for catching it and brining it to our attention.
-Boris
On Tue, Apr 16, 2019 at 1:33 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Hello everyone, As you mentioned there are some inaccuracies in stats on stackalytics.com. It happened because of outdated Prod env. At this moment we are in a process of migration to the new env. All data on this env is fresh and accurate. So the problem will be solved soon.
-- Best Regards, Sergey Nikitin
--
Edward Ionel
Marketing Operations Manager
Mirantis, Inc.
900 E Hamilton Ave, Suite 650
Campbell, CA 95008
Eionel@mirantis.com
www.mirantis.com
-- Best Regards, Sergey Nikitin
Hi there, Recently we found we lost a person's data from our company at the stackalytics website. You can check the merged patch from [0], but there no date from the stackalytics website. stackalytics info as below: Company: ZTE Corporation Launchpad: 578043796-b Gerrit: gengchc2 Look forward to hearing from you! [0]: https://review.opendev.org/#/q/owner:gengchc2,n,z On Fri, Apr 19, 2019 at 12:16 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Hello everyone,
Yesterday we've finished stackalytics migration. Thank you for patience and for notifications about the problem. Now all stats must be accurate.
We are working hard to keep stackalytics.com a trusted storage of OpenStack statistics. So if you will find some problems with data again, please tell as and we will fix it ASAP.
Sergey
On Wed, Apr 17, 2019 at 7:37 AM Edward Ionel <eionel@mirantis.com> wrote:
Hello All,
I first want to thank each and everyone of you for reaching out and sharing the inaccuracies you all have found within Stackalytics, this has helped us tremendously with the efforts to correct these flaws.
I am writing this email to directly address each individual that has reached out and shared their concerns with our Stackalytics data.
Mark Goddard
Michael Johnson
Julia Kreger
Collen Murphy
Clark Boylan
Sean Mooney
Thierry Carrez
Jermey Stanley
Arkady Kanvesky
(Hopefully, I did not miss anyone)
I want to insure everyone that the team is working hard to fix the inaccuracies in some of our data. We are still very much involved in OpenStack and we do read each and every message regarding Stackalytics.
As Boris and Sergey mentioned, we found that this occurred due to an outdated production environment. We are currently in the progress of migrating to a new environment, and the data should be corrected.
The team and I are sorry for these discrepancies and appreciate you all for bringing this to our attention.
Thank you all, for providing links and examples of the inaccuracies. This has helped our efforts greatly in correcting the current issues. It would be great if the community can continue reviewing Stackalytics data and help us provide a better service to all.
Once again, we are all very sorry for this and will continue to fix these issues.
Cheers,
Edward
On Apr 16, 2019, at 4:05 PM, Edward Ionel <eionel@mirantis.com> wrote:
On Tue, Apr 16, 2019 at 2:56 PM Boris Renski <brenski@mirantis.com> wrote:
Folks - more specifically, we plan to roll out an update by tomorrow mid-day PT which should fix all the numbers + add aggregate details on Airship project contributions.
Would really appreciate the help of the community to poke around tomorrow afternoon and see if there are still discrepancies.
Sorry about this and thank you for catching it and brining it to our attention.
-Boris
On Tue, Apr 16, 2019 at 1:33 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Hello everyone, As you mentioned there are some inaccuracies in stats on stackalytics.com. It happened because of outdated Prod env. At this moment we are in a process of migration to the new env. All data on this env is fresh and accurate. So the problem will be solved soon.
-- Best Regards, Sergey Nikitin
--
Edward Ionel
Marketing Operations Manager
Mirantis, Inc.
900 E Hamilton Ave, Suite 650
Campbell, CA 95008
Eionel@mirantis.com
www.mirantis.com
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
Thank you for information! I will take a look On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi there,
Recently we found we lost a person's data from our company at the stackalytics website. You can check the merged patch from [0], but there no date from the stackalytics website.
stackalytics info as below: Company: ZTE Corporation Launchpad: 578043796-b Gerrit: gengchc2
Look forward to hearing from you!
[0]: https://review.opendev.org/#/q/owner:gengchc2,n,z
On Fri, Apr 19, 2019 at 12:16 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Hello everyone,
Yesterday we've finished stackalytics migration. Thank you for patience and for notifications about the problem. Now all stats must be accurate.
We are working hard to keep stackalytics.com a trusted storage of OpenStack statistics. So if you will find some problems with data again, please tell as and we will fix it ASAP.
Sergey
On Wed, Apr 17, 2019 at 7:37 AM Edward Ionel <eionel@mirantis.com> wrote:
Hello All,
I first want to thank each and everyone of you for reaching out and sharing the inaccuracies you all have found within Stackalytics, this has helped us tremendously with the efforts to correct these flaws.
I am writing this email to directly address each individual that has reached out and shared their concerns with our Stackalytics data.
Mark Goddard
Michael Johnson
Julia Kreger
Collen Murphy
Clark Boylan
Sean Mooney
Thierry Carrez
Jermey Stanley
Arkady Kanvesky
(Hopefully, I did not miss anyone)
I want to insure everyone that the team is working hard to fix the inaccuracies in some of our data. We are still very much involved in OpenStack and we do read each and every message regarding Stackalytics.
As Boris and Sergey mentioned, we found that this occurred due to an outdated production environment. We are currently in the progress of migrating to a new environment, and the data should be corrected.
The team and I are sorry for these discrepancies and appreciate you all for bringing this to our attention.
Thank you all, for providing links and examples of the inaccuracies. This has helped our efforts greatly in correcting the current issues. It would be great if the community can continue reviewing Stackalytics data and help us provide a better service to all.
Once again, we are all very sorry for this and will continue to fix these issues.
Cheers,
Edward
On Apr 16, 2019, at 4:05 PM, Edward Ionel <eionel@mirantis.com> wrote:
On Tue, Apr 16, 2019 at 2:56 PM Boris Renski <brenski@mirantis.com> wrote:
Folks - more specifically, we plan to roll out an update by tomorrow mid-day PT which should fix all the numbers + add aggregate details on Airship project contributions.
Would really appreciate the help of the community to poke around tomorrow afternoon and see if there are still discrepancies.
Sorry about this and thank you for catching it and brining it to our attention.
-Boris
On Tue, Apr 16, 2019 at 1:33 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Hello everyone, As you mentioned there are some inaccuracies in stats on stackalytics.com. It happened because of outdated Prod env. At this moment we are in a process of migration to the new env. All data on this env is fresh and accurate. So the problem will be solved soon.
-- Best Regards, Sergey Nikitin
--
Edward Ionel
Marketing Operations Manager
Mirantis, Inc.
900 E Hamilton Ave, Suite 650
Campbell, CA 95008
Eionel@mirantis.com
www.mirantis.com
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
Hi Sergey, Do we have any process about my colleague's data loss problem? Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道：
Thank you for information! I will take a look
On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi there,
Recently we found we lost a person's data from our company at the stackalytics website. You can check the merged patch from [0], but there no date from the stackalytics website.
stackalytics info as below: Company: ZTE Corporation Launchpad: 578043796-b Gerrit: gengchc2
Look forward to hearing from you!
Best Regards, Rong Zhu
--
Thanks, Rong Zhu
Hello Rong, Sorry for long response. I was on a trip during last 5 days. What I have found: Lets take a look on this patch [1]. It must be a contribution of gengchc2, but for some reasons it was matched to Yuval Brik [2] I'm still trying to find a root cause of it, but anyway on this week we are planing to rebuild our database to increase RAM. I checked statistics of gengchc2 on clean database and it's complete correct. So your problem will be solved in several days. It will take so long time because full rebuild of DB takes 48 hours, but we need to test our migration process first to keep zero down time. I'll share a results with you here when the process will be finished. Thank you for your patience. Sergey [1] https://review.opendev.org/#/c/627762/ [2] https://www.stackalytics.com/?user_id=jhamhader&project_type=all&release=all&metric=commits&company=&module=freezer-api On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Do we have any process about my colleague's data loss problem?
Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道：
Thank you for information! I will take a look
On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi there,
Recently we found we lost a person's data from our company at the stackalytics website. You can check the merged patch from [0], but there no date from the stackalytics website.
stackalytics info as below: Company: ZTE Corporation Launchpad: 578043796-b Gerrit: gengchc2
Look forward to hearing from you!
Best Regards, Rong Zhu
--
Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
Hi Sergey, What is the process about rebuild the database? Thanks, Rong Zhu Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道：
Hello Rong,
Sorry for long response. I was on a trip during last 5 days.
What I have found: Lets take a look on this patch [1]. It must be a contribution of gengchc2, but for some reasons it was matched to Yuval Brik [2] I'm still trying to find a root cause of it, but anyway on this week we are planing to rebuild our database to increase RAM. I checked statistics of gengchc2 on clean database and it's complete correct. So your problem will be solved in several days. It will take so long time because full rebuild of DB takes 48 hours, but we need to test our migration process first to keep zero down time. I'll share a results with you here when the process will be finished. Thank you for your patience.
Sergey
[1] https://review.opendev.org/#/c/627762/ [2] https://www.stackalytics.com/?user_id=jhamhader&project_type=all&release=all&metric=commits&company=&module=freezer-api
On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Do we have any process about my colleague's data loss problem?
Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道：
Thank you for information! I will take a look
On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi there,
Recently we found we lost a person's data from our company at the stackalytics website. You can check the merged patch from [0], but there no date from the stackalytics website.
stackalytics info as below: Company: ZTE Corporation Launchpad: 578043796-b Gerrit: gengchc2
Look forward to hearing from you!
Best Regards, Rong Zhu
--
Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
Testing of migration process shown us that we have to rebuild database "on live". Unfortunately it means that during rebuild data will be incomplete. I talked with the colleague who did it previously and he told me that it's normal procedure. I got these results on Monday and at this moment I'm waiting for weekend. It's better to rebuild database in Saturday and Sunday to do now affect much number of users. So by the end of this week everything will be completed. Thank you for patient. On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
What is the process about rebuild the database?
Thanks, Rong Zhu
Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道：
Hello Rong,
Sorry for long response. I was on a trip during last 5 days.
What I have found: Lets take a look on this patch [1]. It must be a contribution of gengchc2, but for some reasons it was matched to Yuval Brik [2] I'm still trying to find a root cause of it, but anyway on this week we are planing to rebuild our database to increase RAM. I checked statistics of gengchc2 on clean database and it's complete correct. So your problem will be solved in several days. It will take so long time because full rebuild of DB takes 48 hours, but we need to test our migration process first to keep zero down time. I'll share a results with you here when the process will be finished. Thank you for your patience.
Sergey
[1] https://review.opendev.org/#/c/627762/ [2] https://www.stackalytics.com/?user_id=jhamhader&project_type=all&release=all&metric=commits&company=&module=freezer-api
On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Do we have any process about my colleague's data loss problem?
Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道：
Thank you for information! I will take a look
On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi there,
Recently we found we lost a person's data from our company at the stackalytics website. You can check the merged patch from [0], but there no date from the stackalytics website.
stackalytics info as below: Company: ZTE Corporation Launchpad: 578043796-b Gerrit: gengchc2
Look forward to hearing from you!
Best Regards, Rong Zhu
--
Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
Hi, Rong, Database was rebuild and now stats o gengchc2 [1] is correct [2]. [1] https://www.stackalytics.com/?release=all&metric=commits&project_type=all&user_id=578043796-b [2] https://review.opendev.org/#/q/owner:gengchc2,n,z Sorry for delay, Sergey On Fri, May 17, 2019 at 6:20 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Testing of migration process shown us that we have to rebuild database "on live". Unfortunately it means that during rebuild data will be incomplete. I talked with the colleague who did it previously and he told me that it's normal procedure. I got these results on Monday and at this moment I'm waiting for weekend. It's better to rebuild database in Saturday and Sunday to do now affect much number of users. So by the end of this week everything will be completed. Thank you for patient.
On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
What is the process about rebuild the database?
Thanks, Rong Zhu
Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道：
Hello Rong,
Sorry for long response. I was on a trip during last 5 days.
What I have found: Lets take a look on this patch [1]. It must be a contribution of gengchc2, but for some reasons it was matched to Yuval Brik [2] I'm still trying to find a root cause of it, but anyway on this week we are planing to rebuild our database to increase RAM. I checked statistics of gengchc2 on clean database and it's complete correct. So your problem will be solved in several days. It will take so long time because full rebuild of DB takes 48 hours, but we need to test our migration process first to keep zero down time. I'll share a results with you here when the process will be finished. Thank you for your patience.
Sergey
[1] https://review.opendev.org/#/c/627762/ [2] https://www.stackalytics.com/?user_id=jhamhader&project_type=all&release=all&metric=commits&company=&module=freezer-api
On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Do we have any process about my colleague's data loss problem?
Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道：
Thank you for information! I will take a look
On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi there,
Recently we found we lost a person's data from our company at the stackalytics website. You can check the merged patch from [0], but there no date from the stackalytics website.
stackalytics info as below: Company: ZTE Corporation Launchpad: 578043796-b Gerrit: gengchc2
Look forward to hearing from you!
Best Regards, Rong Zhu
--
Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
Hi Sergey, Thanks for your help. Now the numbers are correctly. Sergey Nikitin <snikitin@mirantis.com>于2019年5月19日 周日21:12写道：
Hi, Rong,
Database was rebuild and now stats o gengchc2 [1] is correct [2].
[1] https://www.stackalytics.com/?release=all&metric=commits&project_type=all&user_id=578043796-b [2] https://review.opendev.org/#/q/owner:gengchc2,n,z
Sorry for delay, Sergey
On Fri, May 17, 2019 at 6:20 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Testing of migration process shown us that we have to rebuild database "on live". Unfortunately it means that during rebuild data will be incomplete. I talked with the colleague who did it previously and he told me that it's normal procedure. I got these results on Monday and at this moment I'm waiting for weekend. It's better to rebuild database in Saturday and Sunday to do now affect much number of users. So by the end of this week everything will be completed. Thank you for patient.
On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
What is the process about rebuild the database?
Thanks, Rong Zhu
Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道：
Hello Rong,
Sorry for long response. I was on a trip during last 5 days.
What I have found: Lets take a look on this patch [1]. It must be a contribution of gengchc2, but for some reasons it was matched to Yuval Brik [2] I'm still trying to find a root cause of it, but anyway on this week we are planing to rebuild our database to increase RAM. I checked statistics of gengchc2 on clean database and it's complete correct. So your problem will be solved in several days. It will take so long time because full rebuild of DB takes 48 hours, but we need to test our migration process first to keep zero down time. I'll share a results with you here when the process will be finished. Thank you for your patience.
Sergey
[1] https://review.opendev.org/#/c/627762/ [2] https://www.stackalytics.com/?user_id=jhamhader&project_type=all&release=all&metric=commits&company=&module=freezer-api
On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Do we have any process about my colleague's data loss problem?
Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道：
Thank you for information! I will take a look
On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> wrote:
> Hi there, > > Recently we found we lost a person's data from our company at the > stackalytics website. > You can check the merged patch from [0], but there no date from > the stackalytics website. > > stackalytics info as below: > Company: ZTE Corporation > Launchpad: 578043796-b > Gerrit: gengchc2 > > Look forward to hearing from you! >
Best Regards, Rong Zhu
> --
Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
There are still issues. For example nova is not showing any commits since April: https://www.stackalytics.com/?metric=commits&release=train&project_type=all&module=nova Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Thanks for your help. Now the numbers are correctly.
Sergey Nikitin <snikitin@mirantis.com>于2019年5月19日 周日21:12写道：
Hi, Rong,
Database was rebuild and now stats o gengchc2 [1] is correct [2].
[1] https://www.stackalytics.com/?release=all&metric=commits&project_type=all&user_id=578043796-b [2] https://review.opendev.org/#/q/owner:gengchc2,n,z
Sorry for delay, Sergey
On Fri, May 17, 2019 at 6:20 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Testing of migration process shown us that we have to rebuild database "on live". Unfortunately it means that during rebuild data will be incomplete. I talked with the colleague who did it previously and he told me that it's normal procedure. I got these results on Monday and at this moment I'm waiting for weekend. It's better to rebuild database in Saturday and Sunday to do now affect much number of users. So by the end of this week everything will be completed. Thank you for patient.
On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
What is the process about rebuild the database?
Thanks, Rong Zhu
Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道：
Hello Rong,
Sorry for long response. I was on a trip during last 5 days.
What I have found: Lets take a look on this patch [1]. It must be a contribution of gengchc2, but for some reasons it was matched to Yuval Brik [2] I'm still trying to find a root cause of it, but anyway on this week we are planing to rebuild our database to increase RAM. I checked statistics of gengchc2 on clean database and it's complete correct. So your problem will be solved in several days. It will take so long time because full rebuild of DB takes 48 hours, but we need to test our migration process first to keep zero down time. I'll share a results with you here when the process will be finished. Thank you for your patience.
Sergey
[1] https://review.opendev.org/#/c/627762/ [2] https://www.stackalytics.com/?user_id=jhamhader&project_type=all&release=all&metric=commits&company=&module=freezer-api
On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Do we have any process about my colleague's data loss problem?
Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道：
> Thank you for information! I will take a look > > On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> > wrote: > >> Hi there, >> >> Recently we found we lost a person's data from our company at the >> stackalytics website. >> You can check the merged patch from [0], but there no date from >> the stackalytics website. >> >> stackalytics info as below: >> Company: ZTE Corporation >> Launchpad: 578043796-b >> Gerrit: gengchc2 >> >> Look forward to hearing from you! >> > Best Regards, Rong Zhu
> >> -- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
Thank you for message! yes, I guess new train release wasn't added into repos (just on drop down). I'll fix it now. On Thu, May 23, 2019 at 1:39 AM Adam Spiers <aspiers@suse.com> wrote:
There are still issues. For example nova is not showing any commits since April:
https://www.stackalytics.com/?metric=commits&release=train&project_type=all&module=nova
Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Thanks for your help. Now the numbers are correctly.
Sergey Nikitin <snikitin@mirantis.com>于2019年5月19日 周日21:12写道：
Hi, Rong,
Database was rebuild and now stats o gengchc2 [1] is correct [2].
[1]
https://www.stackalytics.com/?release=all&metric=commits&project_type=all&user_id=578043796-b
[2] https://review.opendev.org/#/q/owner:gengchc2,n,z
Sorry for delay, Sergey
On Fri, May 17, 2019 at 6:20 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Testing of migration process shown us that we have to rebuild database "on live". Unfortunately it means that during rebuild data will be incomplete. I talked with the colleague who did it previously and he told me that it's normal procedure. I got these results on Monday and at this moment I'm waiting for weekend. It's better to rebuild database in Saturday and Sunday to do now affect much number of users. So by the end of this week everything will be completed. Thank you for patient.
On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
What is the process about rebuild the database?
Thanks, Rong Zhu
Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道：
Hello Rong,
Sorry for long response. I was on a trip during last 5 days.
What I have found: Lets take a look on this patch [1]. It must be a contribution of gengchc2, but for some reasons it was matched to Yuval Brik [2] I'm still trying to find a root cause of it, but anyway on this week we are planing to rebuild our database to increase RAM. I checked statistics of gengchc2 on clean database and it's complete correct. So your problem will be solved in several days. It will take so long time because full rebuild of DB takes 48 hours, but we need to test our migration process first to keep zero down time. I'll share a results with you here when the process will be finished. Thank you for your patience.
Sergey
On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com>
wrote:
> Hi Sergey, > > Do we have any process about my colleague's data loss problem? > > Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道： > >> Thank you for information! I will take a look >> >> On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> >> wrote: >> >>> Hi there, >>> >>> Recently we found we lost a person's data from our company at the >>> stackalytics website. >>> You can check the merged patch from [0], but there no date from >>> the stackalytics website. >>> >>> stackalytics info as below: >>> Company: ZTE Corporation >>> Launchpad: 578043796-b >>> Gerrit: gengchc2 >>> >>> Look forward to hearing from you! >>> >> > Best Regards, > Rong Zhu > >> >>> -- > Thanks, > Rong Zhu >
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
Thanks for looking at this. Maybe I'm just being too impatient and the data is still synchronising, but now I only see 4 commits to nova in May, and there have definitely been a *lot* more than that :-) https://opendev.org/openstack/nova/commits/branch/master Sergey Nikitin <snikitin@mirantis.com> wrote:
Thank you for message! yes, I guess new train release wasn't added into repos (just on drop down). I'll fix it now.
On Thu, May 23, 2019 at 1:39 AM Adam Spiers <aspiers@suse.com> wrote:
There are still issues. For example nova is not showing any commits since April:
https://www.stackalytics.com/?metric=commits&release=train&project_type=all&module=nova
Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Thanks for your help. Now the numbers are correctly.
Sergey Nikitin <snikitin@mirantis.com>于2019年5月19日 周日21:12写道：
Hi, Rong,
Database was rebuild and now stats o gengchc2 [1] is correct [2].
[1]
https://www.stackalytics.com/?release=all&metric=commits&project_type=all&user_id=578043796-b
[2] https://review.opendev.org/#/q/owner:gengchc2,n,z
Sorry for delay, Sergey
On Fri, May 17, 2019 at 6:20 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Testing of migration process shown us that we have to rebuild database "on live". Unfortunately it means that during rebuild data will be incomplete. I talked with the colleague who did it previously and he told me that it's normal procedure. I got these results on Monday and at this moment I'm waiting for weekend. It's better to rebuild database in Saturday and Sunday to do now affect much number of users. So by the end of this week everything will be completed. Thank you for patient.
On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
What is the process about rebuild the database?
Thanks, Rong Zhu
Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道：
> Hello Rong, > > Sorry for long response. I was on a trip during last 5 days. > > What I have found: > Lets take a look on this patch [1]. It must be a contribution of > gengchc2, but for some reasons it was matched to Yuval Brik [2] > I'm still trying to find a root cause of it, but anyway on this week we > are planing to rebuild our database to increase RAM. I checked statistics > of gengchc2 on clean database and it's complete correct. > So your problem will be solved in several days. It will take so long > time because full rebuild of DB takes 48 hours, but we need to test our > migration process first to keep zero down time. > I'll share a results with you here when the process will be finished. > Thank you for your patience. > > Sergey > > [1] https://review.opendev.org/#/c/627762/ > [2] > https://www.stackalytics.com/?user_id=jhamhader&project_type=all&release=all&metric=commits&company=&module=freezer-api > > > On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote: > >> Hi Sergey, >> >> Do we have any process about my colleague's data loss problem? >> >> Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道： >> >>> Thank you for information! I will take a look >>> >>> On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu <aaronzhu1121@gmail.com> >>> wrote: >>> >>>> Hi there, >>>> >>>> Recently we found we lost a person's data from our company at the >>>> stackalytics website. >>>> You can check the merged patch from [0], but there no date from >>>> the stackalytics website. >>>> >>>> stackalytics info as below: >>>> Company: ZTE Corporation >>>> Launchpad: 578043796-b >>>> Gerrit: gengchc2 >>>> >>>> Look forward to hearing from you! >>>> >>> >> Best Regards, >> Rong Zhu >> >>> >>>> -- >> Thanks, >> Rong Zhu >> > > > -- > Best Regards, > Sergey Nikitin > -- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
Hi, Yes, data synchronization takes up to 24 hours. So we have to wait. I'll inform you when the process will be finished. On Fri, May 24, 2019 at 1:53 AM Adam Spiers <aspiers@suse.com> wrote:
Thanks for looking at this. Maybe I'm just being too impatient and the data is still synchronising, but now I only see 4 commits to nova in May, and there have definitely been a *lot* more than that :-)
https://opendev.org/openstack/nova/commits/branch/master
Thank you for message! yes, I guess new train release wasn't added into repos (just on drop down). I'll fix it now.
On Thu, May 23, 2019 at 1:39 AM Adam Spiers <aspiers@suse.com> wrote:
There are still issues. For example nova is not showing any commits since April:
https://www.stackalytics.com/?metric=commits&release=train&project_type=all&module=nova
Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Thanks for your help. Now the numbers are correctly.
Sergey Nikitin <snikitin@mirantis.com>于2019年5月19日 周日21:12写道：
Hi, Rong,
Database was rebuild and now stats o gengchc2 [1] is correct [2].
[1]
https://www.stackalytics.com/?release=all&metric=commits&project_type=all&user_id=578043796-b
[2] https://review.opendev.org/#/q/owner:gengchc2,n,z
Sorry for delay, Sergey
On Fri, May 17, 2019 at 6:20 PM Sergey Nikitin < snikitin@mirantis.com> wrote:
Testing of migration process shown us that we have to rebuild database "on live". Unfortunately it means that during rebuild data will be incomplete. I talked with the colleague who did it previously and he told me that it's normal procedure. I got these results on Monday and at this moment I'm waiting for weekend. It's better to rebuild database in Saturday and Sunday to do now affect much number of users. So by the end of this week everything will be completed. Thank you for patient.
On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote:
> Hi Sergey, > > What is the process about rebuild the database? > > Thanks, > Rong Zhu > > Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道： > >> Hello Rong, >> >> Sorry for long response. I was on a trip during last 5 days. >> >> What I have found: >> Lets take a look on this patch [1]. It must be a contribution of >> gengchc2, but for some reasons it was matched to Yuval Brik [2] >> I'm still trying to find a root cause of it, but anyway on this week we >> are planing to rebuild our database to increase RAM. I checked statistics >> of gengchc2 on clean database and it's complete correct. >> So your problem will be solved in several days. It will take so long >> time because full rebuild of DB takes 48 hours, but we need to test our >> migration process first to keep zero down time. >> I'll share a results with you here when the process will be finished. >> Thank you for your patience. >> >> Sergey >> >> [1] https://review.opendev.org/#/c/627762/ >> [2] >>
>> >> >> On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote: >> >>> Hi Sergey, >>> >>> Do we have any process about my colleague's data loss problem? >>> >>> Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道： >>> >>>> Thank you for information! I will take a look >>>> >>>> On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu < aaronzhu1121@gmail.com> >>>> wrote: >>>> >>>>> Hi there, >>>>> >>>>> Recently we found we lost a person's data from our company at
Sergey Nikitin <snikitin@mirantis.com> wrote: the
>>>>> stackalytics website. >>>>> You can check the merged patch from [0], but there no date from >>>>> the stackalytics website. >>>>> >>>>> stackalytics info as below: >>>>> Company: ZTE Corporation >>>>> Launchpad: 578043796-b >>>>> Gerrit: gengchc2 >>>>> >>>>> Look forward to hearing from you! >>>>> >>>> >>> Best Regards, >>> Rong Zhu >>> >>>> >>>>> -- >>> Thanks, >>> Rong Zhu >>> >> >> >> -- >> Best Regards, >> Sergey Nikitin >> > -- > Thanks, > Rong Zhu >
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
Hi, Looks like data finally was processed! [1] Thank your for your notification! If you will find some other problems please let me know. Sergey [1] https://www.stackalytics.com/?metric=commits&release=train&project_type=all&module=nova On Fri, May 24, 2019 at 4:16 PM Sergey Nikitin <snikitin@mirantis.com> wrote:
Hi, Yes, data synchronization takes up to 24 hours. So we have to wait. I'll inform you when the process will be finished.
On Fri, May 24, 2019 at 1:53 AM Adam Spiers <aspiers@suse.com> wrote:
Thanks for looking at this. Maybe I'm just being too impatient and the data is still synchronising, but now I only see 4 commits to nova in May, and there have definitely been a *lot* more than that :-)
https://opendev.org/openstack/nova/commits/branch/master
Thank you for message! yes, I guess new train release wasn't added into repos (just on drop down). I'll fix it now.
On Thu, May 23, 2019 at 1:39 AM Adam Spiers <aspiers@suse.com> wrote:
There are still issues. For example nova is not showing any commits since April:
https://www.stackalytics.com/?metric=commits&release=train&project_type=all&module=nova
Rong Zhu <aaronzhu1121@gmail.com> wrote:
Hi Sergey,
Thanks for your help. Now the numbers are correctly.
Sergey Nikitin <snikitin@mirantis.com>于2019年5月19日 周日21:12写道：
Hi, Rong,
Database was rebuild and now stats o gengchc2 [1] is correct [2].
[1]
https://www.stackalytics.com/?release=all&metric=commits&project_type=all&user_id=578043796-b
[2] https://review.opendev.org/#/q/owner:gengchc2,n,z
Sorry for delay, Sergey
On Fri, May 17, 2019 at 6:20 PM Sergey Nikitin < snikitin@mirantis.com> wrote:
> Testing of migration process shown us that we have to rebuild database > "on live". > Unfortunately it means that during rebuild data will be incomplete. I > talked with the colleague who did it previously and he told me that it's > normal procedure. > I got these results on Monday and at this moment I'm waiting for weekend. > It's better to rebuild database in Saturday and Sunday to do now affect > much number of users. > So by the end of this week everything will be completed. Thank you for > patient. > > On Fri, May 17, 2019 at 6:15 AM Rong Zhu <aaronzhu1121@gmail.com> wrote: > >> Hi Sergey, >> >> What is the process about rebuild the database? >> >> Thanks, >> Rong Zhu >> >> Sergey Nikitin <snikitin@mirantis.com>于2019年5月7日 周二00:59写道： >> >>> Hello Rong, >>> >>> Sorry for long response. I was on a trip during last 5 days. >>> >>> What I have found: >>> Lets take a look on this patch [1]. It must be a contribution of >>> gengchc2, but for some reasons it was matched to Yuval Brik [2] >>> I'm still trying to find a root cause of it, but anyway on this week we >>> are planing to rebuild our database to increase RAM. I checked statistics >>> of gengchc2 on clean database and it's complete correct. >>> So your problem will be solved in several days. It will take so long >>> time because full rebuild of DB takes 48 hours, but we need to test our >>> migration process first to keep zero down time. >>> I'll share a results with you here when the process will be finished. >>> Thank you for your patience. >>> >>> Sergey >>> >>> [1] https://review.opendev.org/#/c/627762/ >>> [2] >>>
>>> >>> >>> On Mon, May 6, 2019 at 6:30 AM Rong Zhu <aaronzhu1121@gmail.com> wrote: >>> >>>> Hi Sergey, >>>> >>>> Do we have any process about my colleague's data loss problem? >>>> >>>> Sergey Nikitin <snikitin@mirantis.com>于2019年4月29日 周一19:57写道： >>>> >>>>> Thank you for information! I will take a look >>>>> >>>>> On Mon, Apr 29, 2019 at 3:47 PM Rong Zhu < aaronzhu1121@gmail.com> >>>>> wrote: >>>>> >>>>>> Hi there, >>>>>> >>>>>> Recently we found we lost a person's data from our company at
Sergey Nikitin <snikitin@mirantis.com> wrote: the
>>>>>> stackalytics website. >>>>>> You can check the merged patch from [0], but there no date from >>>>>> the stackalytics website. >>>>>> >>>>>> stackalytics info as below: >>>>>> Company: ZTE Corporation >>>>>> Launchpad: 578043796-b >>>>>> Gerrit: gengchc2 >>>>>> >>>>>> Look forward to hearing from you! >>>>>> >>>>> >>>> Best Regards, >>>> Rong Zhu >>>> >>>>> >>>>>> -- >>>> Thanks, >>>> Rong Zhu >>>> >>> >>> >>> -- >>> Best Regards, >>> Sergey Nikitin >>> >> -- >> Thanks, >> Rong Zhu >> > > > -- > Best Regards, > Sergey Nikitin >
-- Best Regards, Sergey Nikitin
-- Thanks, Rong Zhu
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
-- Best Regards, Sergey Nikitin
participants (4)
-
Adam Spiers
-
Edward Ionel
-
Rong Zhu
-
Sergey Nikitin