ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Deepshikha Khandelwal
Hi folks,

We have initiated the migration process today. All the patch owners are requested to move their existing patches from Gerrit[1] to Github[2].

The changes we brought in with this migration:

- The 'devel' branch[3] is the new default branch on GitHub to get away from master/slave language.

- This 'devel' branch is the result of the merge of the current branch and the historic repository, thus requiring a new clone. It helps in getting the complete idea of tracing any changes properly to its origin to understand the intentions behind the code.

- We have switched the glusterfs repo on gerrit to readonly state. So you will not be able to merge the patches on Gerrit from now onwards. Though we are not deprecating gerrit right now, we will work with the remaining users/projects to move to github as well.

- Changes in the development workflow:
    - All the required smoke tests would be auto-triggered on submitting a PR.
    - Developers can retrigger the smoke tests using "/recheck smoke" as comment.
    - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"

For more information you can go through the contribution guidelines listed in CONTRIBUTING.md[5]

[1] https://review.gluster.org/#/q/status:open+project:glusterfs
[2] https://github.com/gluster/glusterfs
[3] https://github.com/gluster/glusterfs/tree/devel
[4] https://github.com/orgs/gluster/teams/gluster-maintainers
[5] https://github.com/gluster/glusterfs/blob/master/CONTRIBUTING.md

Please reach out to us if you have any queries.

Thanks,
Gluster-infra team

_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Amar Tumballi-3
Thanks for getting this done, Deepshika and Michael, and Infra team members.

Thanks everyone for valuable feedback during this process!

I personally hope this change will help glusterfs project to attract more developers, and we can engage more closely with our developers!

Note that this would result in weeks of confusions, questions, and bugs in workflow! We are trying to tune the workflow accordingly! Please try it out, and give feedback! Once we start using we may figure out new things, so jump in, and give it a try!

In case of any issues, raise a github issue,  or find some of us on gluster.slack.com

Regards,
Amar



On Wed, Oct 7, 2020 at 3:16 PM Deepshikha Khandelwal <[hidden email]> wrote:
Hi folks,

We have initiated the migration process today. All the patch owners are requested to move their existing patches from Gerrit[1] to Github[2].

The changes we brought in with this migration:

- The 'devel' branch[3] is the new default branch on GitHub to get away from master/slave language.

- This 'devel' branch is the result of the merge of the current branch and the historic repository, thus requiring a new clone. It helps in getting the complete idea of tracing any changes properly to its origin to understand the intentions behind the code.

- We have switched the glusterfs repo on gerrit to readonly state. So you will not be able to merge the patches on Gerrit from now onwards. Though we are not deprecating gerrit right now, we will work with the remaining users/projects to move to github as well.

- Changes in the development workflow:
    - All the required smoke tests would be auto-triggered on submitting a PR.
    - Developers can retrigger the smoke tests using "/recheck smoke" as comment.
    - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"

For more information you can go through the contribution guidelines listed in CONTRIBUTING.md[5]

[1] https://review.gluster.org/#/q/status:open+project:glusterfs
[2] https://github.com/gluster/glusterfs
[3] https://github.com/gluster/glusterfs/tree/devel
[4] https://github.com/orgs/gluster/teams/gluster-maintainers
[5] https://github.com/gluster/glusterfs/blob/master/CONTRIBUTING.md

Please reach out to us if you have any queries.

Thanks,
Gluster-infra team


--
--
Container Storage made easy!


_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Question about disperse volumes

Federico Strati
In reply to this post by Deepshikha Khandelwal
Hello,

from the point of performance we observe a very strong reduction in
throuhgput

when we enable EC (erasure coding) with disperse volumes.

Is that possible that there is a sequential process of distribution of
fragments among clients?

What is in effect the role of the events manager inside gluster ?

Thanks in advance

Kind regards

Federico Strati

_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-infra] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Kaleb Keithley
In reply to this post by Deepshikha Khandelwal


On Wed, Oct 7, 2020 at 5:46 AM Deepshikha Khandelwal <[hidden email]> wrote:

    - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"

[4] https://github.com/orgs/gluster/teams/gluster-maintainers

There are a lot of people in that group that haven't been involved with Gluster for a long time.

Maybe some of them should be "retired."

--

Kaleb 

_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-infra] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Sunil Kumar Heggodu Gopala Acharya

Regards,

Sunil kumar Acharya




On Wed, Oct 7, 2020 at 4:54 PM Kaleb Keithley <[hidden email]> wrote:


On Wed, Oct 7, 2020 at 5:46 AM Deepshikha Khandelwal <[hidden email]> wrote:

    - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"

[4] https://github.com/orgs/gluster/teams/gluster-maintainers

There are a lot of people in that group that haven't been involved with Gluster for a long time.
Also there are new contributors, time to update!

Maybe some of them should be "retired."

--

Kaleb 
_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel


_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-Maintainers] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Aravinda VK-2
In reply to this post by Deepshikha Khandelwal
This is awesome. Thanks to infra team for the great effort.

Aravinda Vishwanathapura

On 07-Oct-2020, at 3:16 PM, Deepshikha Khandelwal <[hidden email]> wrote:

Hi folks,

We have initiated the migration process today. All the patch owners are requested to move their existing patches from Gerrit[1] to Github[2].

The changes we brought in with this migration:

- The 'devel' branch[3] is the new default branch on GitHub to get away from master/slave language.

- This 'devel' branch is the result of the merge of the current branch and the historic repository, thus requiring a new clone. It helps in getting the complete idea of tracing any changes properly to its origin to understand the intentions behind the code.

- We have switched the glusterfs repo on gerrit to readonly state. So you will not be able to merge the patches on Gerrit from now onwards. Though we are not deprecating gerrit right now, we will work with the remaining users/projects to move to github as well.

- Changes in the development workflow:
    - All the required smoke tests would be auto-triggered on submitting a PR.
    - Developers can retrigger the smoke tests using "/recheck smoke" as comment.
    - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"

For more information you can go through the contribution guidelines listed in CONTRIBUTING.md[5]

[1] https://review.gluster.org/#/q/status:open+project:glusterfs
[2] https://github.com/gluster/glusterfs
[3] https://github.com/gluster/glusterfs/tree/devel
[4] https://github.com/orgs/gluster/teams/gluster-maintainers
[5] https://github.com/gluster/glusterfs/blob/master/CONTRIBUTING.md

Please reach out to us if you have any queries.

Thanks,
Gluster-infra team
_______________________________________________
maintainers mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/maintainers






_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-infra] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Kaleb Keithley
In reply to this post by Sunil Kumar Heggodu Gopala Acharya
On Wed, Oct 7, 2020 at 7:33 AM Sunil Kumar Heggodu Gopala Acharya <[hidden email]> wrote:

Regards,

Sunil kumar Acharya




On Wed, Oct 7, 2020 at 4:54 PM Kaleb Keithley <[hidden email]> wrote:


On Wed, Oct 7, 2020 at 5:46 AM Deepshikha Khandelwal <[hidden email]> wrote:

    - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"

[4] https://github.com/orgs/gluster/teams/gluster-maintainers

There are a lot of people in that group that haven't been involved with Gluster for a long time.
Also there are new contributors, time to update! 

Who is going to do this? I don't have the necessary privs.

(I also note that Jeff Darcy has been removed. Perhaps he removed himself?)

--

Kaleb
 

_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-infra] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Kaleb Keithley


On Thu, Oct 8, 2020 at 8:10 AM Kaleb Keithley <[hidden email]> wrote:
On Wed, Oct 7, 2020 at 7:33 AM Sunil Kumar Heggodu Gopala Acharya <[hidden email]> wrote:

Regards,

Sunil kumar Acharya




On Wed, Oct 7, 2020 at 4:54 PM Kaleb Keithley <[hidden email]> wrote:


On Wed, Oct 7, 2020 at 5:46 AM Deepshikha Khandelwal <[hidden email]> wrote:

    - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"

[4] https://github.com/orgs/gluster/teams/gluster-maintainers

There are a lot of people in that group that haven't been involved with Gluster for a long time.
Also there are new contributors, time to update! 

Who is going to do this? I don't have the necessary privs.

Anyone? 

--

Kaleb 

_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-Maintainers] [Gluster-infra] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Sankarshan Mukhopadhyay
It is perhaps on Amar to send the PR with the changes - but that would
kind of make the approval/merge process a bit muddled? How about a PR
being sent for review and then merged in?

On Mon, 12 Oct 2020 at 19:22, Kaleb Keithley <[hidden email]> wrote:

>
>
>
> On Thu, Oct 8, 2020 at 8:10 AM Kaleb Keithley <[hidden email]> wrote:
>>
>> On Wed, Oct 7, 2020 at 7:33 AM Sunil Kumar Heggodu Gopala Acharya <[hidden email]> wrote:
>>>
>>>
>>> Regards,
>>>
>>> Sunil kumar Acharya
>>>
>>>
>>>
>>>
>>> On Wed, Oct 7, 2020 at 4:54 PM Kaleb Keithley <[hidden email]> wrote:
>>>>
>>>>
>>>>
>>>> On Wed, Oct 7, 2020 at 5:46 AM Deepshikha Khandelwal <[hidden email]> wrote:
>>>>>
>>>>>
>>>>>     - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"
>>>>>
>>>>> [4] https://github.com/orgs/gluster/teams/gluster-maintainers
>>>>
>>>>
>>>> There are a lot of people in that group that haven't been involved with Gluster for a long time.
>>>
>>> Also there are new contributors, time to update!
>>
>>
>> Who is going to do this? I don't have the necessary privs.
>
>
> Anyone?
>
> --
>
> Kaleb
> _______________________________________________
> maintainers mailing list
> [hidden email]
> https://lists.gluster.org/mailman/listinfo/maintainers



--
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-infra] [Gluster-Maintainers] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

Amar Tumballi-3


On Mon, 12 Oct, 2020, 8:08 pm sankarshan, <[hidden email]> wrote:
It is perhaps on Amar to send the PR with the changes - but that would
kind of make the approval/merge process a bit muddled? How about a PR
being sent for review and then merged in?

On Mon, 12 Oct 2020 at 19:22, Kaleb Keithley <[hidden email]> wrote:
>
>
>
> On Thu, Oct 8, 2020 at 8:10 AM Kaleb Keithley <[hidden email]> wrote:
>>
>> On Wed, Oct 7, 2020 at 7:33 AM Sunil Kumar Heggodu Gopala Acharya <[hidden email]> wrote:
>>>
>>>
>>> Regards,
>>>
>>> Sunil kumar Acharya
>>>
>>>
>>>
>>>
>>> On Wed, Oct 7, 2020 at 4:54 PM Kaleb Keithley <[hidden email]> wrote:
>>>>
>>>>
>>>>
>>>> On Wed, Oct 7, 2020 at 5:46 AM Deepshikha Khandelwal <[hidden email]> wrote:
>>>>>
>>>>>
>>>>>     - The "regression" tests would be triggered by a comment "/run regression" from anyone in the gluster-maintainers[4] github group. To run full regression, maintainers need to comment "/run full regression"
>>>>>
>>>>> [4] https://github.com/orgs/gluster/teams/gluster-maintainers
>>>>
>>>>
>>>> There are a lot of people in that group that haven't been involved with Gluster for a long time.
>>>
>>> Also there are new contributors, time to update!
>>
>>
>> Who is going to do this? I don't have the necessary privs.
>
>
> Anyone?

I will volunteer to do it to match with content with Maintainers file. IMO, we should also fix non existing emails from maintainers file.

Will take a look sometime tomorrow!

Regards
Amar
 
>
> --
>
> Kaleb
> _______________________________________________
> maintainers mailing list
> [hidden email]
> https://lists.gluster.org/mailman/listinfo/maintainers



--
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
_______________________________________________
Gluster-infra mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-infra

_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel