[Cluster-devel] Moving projects away from fedorahosted.org

[Cluster-devel] Moving projects away from fedorahosted.org

[Andrew Price]

Hi all,

Re: https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/

We'll need to find a new host for the cluster projects that haven't 
migrated away from fedorahosted.org yet.

The recommended successor to fedorahosted.org is pagure.io which is a 
Fedora project, open source, uses the same user account system, allows 
git hooks to be set up, and has the added advantage that we have a 
direct line to the admins and developers.

I've investigated whether pagure.io has the features required to support 
our workflows (group push access) and I've had confirmation that it does 
from #fedora-admin. I've also tried out the test instance of Pagure 
<https://stg.pagure.io/> and it looks like it has everything we need.

We have until Feb 28 to do this so there is time to discuss the 
migration if discussion is needed. Unless we find some good reasons to 
go elsewhere I'll aim to migrate the gfs2-related git repositories to 
Pagure by the end of January.

I gather that the non-gfs2-related projects have mostly been moved to 
github already, under the clusterlabs umbrella, but if there are any 
remaining on fedorahosted I will leave their fates to their respective 
owners, although I'd be happy to help get things migrated if needed.

Cheers,
Andy

[Cluster-devel] Moving gfs2-utils away from fedorahosted.org

[Andrew Price]

On 19/09/16 17:48, Andrew Price wrote:
> Hi all,
>
> Re: https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/
>
> We'll need to find a new host for the cluster projects that haven't
> migrated away from fedorahosted.org yet.
>
> The recommended successor to fedorahosted.org is pagure.io which is a
> Fedora project, open source, uses the same user account system, allows
> git hooks to be set up, and has the added advantage that we have a
> direct line to the admins and developers.
>
> I've investigated whether pagure.io has the features required to support
> our workflows (group push access) and I've had confirmation that it does
> from #fedora-admin. I've also tried out the test instance of Pagure
> <https://stg.pagure.io/> and it looks like it has everything we need.
>
> We have until Feb 28 to do this so there is time to discuss the
> migration if discussion is needed. Unless we find some good reasons to
> go elsewhere I'll aim to migrate the gfs2-related git repositories to
> Pagure by the end of January.

Progress on this:

- A new repository has been created at <https://pagure.io/gfs2-utils> 
and everything in the gfs2-utils Fedora Hosted repository has been 
pushed to it. This will be kept mirrored until the switch over.

- A gfs2-utils maintainers group 
<https://pagure.io/group/gfs2-utils-maint> has been set up and given 
push access to the repository.

- Filed a ticket <https://pagure.io/fedora-infrastructure/issue/5696> to 
get the release tarballs etc. migrated over (and hopefully a URL 
redirect set up).

- Disabled the issue tracker and pull request features for the project 
as we currently have no plans to move away from Bugzilla and email.


Left to do:

- Switch over. I think Feb 3 would be a good date for this as it gives 
us plenty of time to work out any issues, though I don't foresee any.

- Migrate over the current push access list. Pagure uses the Fedora 
accounts system like Fedora Hosted does so this should be simple.

- Set up commit notifications to the appropriate mailing list.

- Update URLs etc. in the git repository itself.

If there's anything I might have missed, do let me know.

Cheers,
Andy

[Cluster-devel] Moving gfs2-utils away from fedorahosted.org

[Jan Pokorný]

[adding developers list at clusterlabs to CC]

On 16/01/17 18:45 +0000, Andrew Price wrote:
> On 19/09/16 17:48, Andrew Price wrote:
>> Re: https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/
>> 
>> We'll need to find a new host for the cluster projects that haven't
>> migrated away from fedorahosted.org yet.
>> 
>> The recommended successor to fedorahosted.org is pagure.io which is a
>> Fedora project, open source, uses the same user account system, allows
>> git hooks to be set up, and has the added advantage that we have a
>> direct line to the admins and developers.
>> 
>> [...]
> 
> Progress on this:
> 
> - A new repository has been created at <https://pagure.io/gfs2-utils> and
> everything in the gfs2-utils Fedora Hosted repository has been pushed to it.
> This will be kept mirrored until the switch over.
> 
> - A gfs2-utils maintainers group <https://pagure.io/group/gfs2-utils-maint>
> has been set up and given push access to the repository.
> 
> - Filed a ticket <https://pagure.io/fedora-infrastructure/issue/5696> to get
> the release tarballs etc. migrated over (and hopefully a URL redirect set
> up).
> 
> - Disabled the issue tracker and pull request features for the project as we
> currently have no plans to move away from Bugzilla and email.

Thanks for setting an example on this matter, Andy.

Tangentially touching is a question of "cluster" project at
fedorahosted location incl. still occasionally evolving or at least
valuable material, perhaps subject of future changes -- git tree
itself and the wiki.

For the former, there are still active branches:
- RHEL6 (head currently featuring Andy's recent commit):
  https://git.fedorahosted.org/cgit/cluster.git/commit/?h=RHEL6
- STABLE32 (Chrissie's commit from around the same time as above)
  https://git.fedorahosted.org/cgit/cluster.git/commit/?h=STABLE32

For the latter, there are some pretty authoritative documents, such
as definition of the API that fence agents should provide:
https://fedorahosted.org/cluster/wiki/FenceAgentAPI

So I think we should arrange for a move to pagure.io for this cluster
project as well if possible, if only to retain the ability to change
something should there be a need.

I can pursuit this if there are no complaints.  Just let me know
(off-list) who aspires to cluster-maint group (to be created)
membership.

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20170117/8ac28048/attachment.sig>

[Cluster-devel] Moving gfs2-utils away from fedorahosted.org

[Andrew Price]

On 17/01/17 19:58, Jan Pokorn? wrote:
> So I think we should arrange for a move to pagure.io for this cluster
> project as well if possible, if only to retain the ability to change
> something should there be a need.

Good plan.

> I can pursuit this if there are no complaints.  Just let me know
> (off-list) who aspires to cluster-maint group (to be created)
> membership.

Could you give the gfs2-utils-maint group push access to the cluster 
project once it's been set up? (It is possible to add many groups to a 
project.) I think that would be the most logical way to do it.

Cheers,
Andy

[Cluster-devel] Moving cluster project (Was: Moving gfs2-utils away from fedorahosted.org)

[Jan Pokorný]

On 17/01/17 21:14 +0000, Andrew Price wrote:
> On 17/01/17 19:58, Jan Pokorn? wrote:
>> So I think we should arrange for a move to pagure.io for this cluster
>> project as well if possible, if only to retain the ability to change
>> something should there be a need.
> 
> Good plan.
> 
>> I can pursuit this if there are no complaints.  Just let me know
>> (off-list) who aspires to cluster-maint group (to be created)
>> membership.
> 
> Could you give the gfs2-utils-maint group push access to the cluster project
> once it's been set up? (It is possible to add many groups to a project.) I
> think that would be the most logical way to do it.

Sure and thanks for a cumulative access assignment tip.

I'll proceed on Friday or early next week, then.

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20170117/6c8f8ada/attachment.sig>

[Cluster-devel] Moving cluster project (Was: Moving gfs2-utils away from fedorahosted.org)

[Jan Pokorný]

On 17/01/17 22:27 +0100, Jan Pokorn? wrote:
> On 17/01/17 21:14 +0000, Andrew Price wrote:
>> On 17/01/17 19:58, Jan Pokorn? wrote:
>>> So I think we should arrange for a move to pagure.io for this cluster
>>> project as well if possible, if only to retain the ability to change
>>> something should there be a need.
>> 
>> Good plan.
>> 
>>> I can pursuit this if there are no complaints.  Just let me know
>>> (off-list) who aspires to cluster-maint group (to be created)
>>> membership.
>> 
>> Could you give the gfs2-utils-maint group push access to the cluster project
>> once it's been set up? (It is possible to add many groups to a project.) I
>> think that would be the most logical way to do it.
> 
> Sure and thanks for a cumulative access assignment tip.
> 
> I'll proceed on Friday or early next week, then.

Well, scheduler of mine didn't get to it until now, so sorry
to anyone starting to worry.

So what's been done:

- git repo moved over to https://pagure.io/linux-cluster/cluster
  + granted commit rights for gfs2-utils-maint group
    (and will add some more folks to linux-cluster group,
    feel free to bug me off-list about that)
  + mass-committed an explanation change to every branch at
    the discontinued fedorahosted.org (fh.o) provider I could,
    as some are already frozen
    (https://git.fedorahosted.org/cgit/cluster.git/)
  . I've decided to use a namespace (because there are possibly
    more projects to be migrated under that label), and have
    stuck with linux-cluster referring to the mailing list of
    the same name that once actively served to discuss the
    cluster stack in question (and is quite abandoned nowadays)

- quickly added backup location links at
  https://fedorahosted.org/cluster/ and
  https://fedorahosted.org/cluster/wiki/FenceAgentAPI, i.e.,
  the pages that seem most important to me, to allow for
  smooth "forward compatibility"; the links currently refer
  to vain stubs at ClusterLabs wiki, but that can be solved
  later on -- I am still unsure if trac wikis at fh.o will
  be served in the next phase or shut down right away and
  apparently this measure will help only in the former case

What to do:
- move releases over to pagure.io as well:
  https://fedorahosted.org/releases/c/l/cluster/
- possibly migrate some original wiki content to proper
  "doc pages" exposed directly through pagure.io
- resolve the question of the linked wiki stubs and
  cross-linking as such

Any comments?  Ideas?

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20170228/aeb83f1b/attachment.sig>

[Cluster-devel] Pagure.io as legacy codebases/distribution files/documentation hosting (Was: Moving cluster project)

[Jan Pokorný]

On 28/02/17 03:18 +0100, Jan Pokorn? wrote:
> On 17/01/17 22:27 +0100, Jan Pokorn? wrote:
>> On 17/01/17 21:14 +0000, Andrew Price wrote:
>>> On 17/01/17 19:58, Jan Pokorn? wrote:
>>>> So I think we should arrange for a move to pagure.io for this cluster
>>>> project as well if possible, if only to retain the ability to change
>>>> something should there be a need.
>>> 
>>> Good plan.
>>> 
>>>> I can pursuit this if there are no complaints.  Just let me know
>>>> (off-list) who aspires to cluster-maint group (to be created)
>>>> membership.
>>> 
>>> Could you give the gfs2-utils-maint group push access to the cluster project
>>> once it's been set up? (It is possible to add many groups to a project.) I
>>> think that would be the most logical way to do it.
>> 
>> Sure and thanks for a cumulative access assignment tip.
>> 
>> I'll proceed on Friday or early next week, then.
> 
> Well, scheduler of mine didn't get to it until now, so sorry
> to anyone starting to worry.
> 
> So what's been done:
> 
> - git repo moved over to https://pagure.io/linux-cluster/cluster
>   + granted commit rights for gfs2-utils-maint group
>     (and will add some more folks to linux-cluster group,
>     feel free to bug me off-list about that)
>   + mass-committed an explanation change to every branch at
>     the discontinued fedorahosted.org (fh.o) provider I could,
>     as some are already frozen
>     (https://git.fedorahosted.org/cgit/cluster.git/)
>   . I've decided to use a namespace (because there are possibly
>     more projects to be migrated under that label),

Actually, there are quite a few legacy project copied over, some
merely for plain archival bits-preserving:
https://pagure.io/group/linux-cluster
[did I miss anything?  AFAIK, gfs-utils and dlm components migrated
on their own, and corosync is on GitHub for years]

Actually also some components otherwise found under ClusterLabs label
(note that *-agents are common to both worlds) are affected, and for
that I created a separate ClusterLabs group on pagure.io:
https://pagure.io/group/ClusterLabs

The respective projects there are just envelopes that I used for
uploading distribution files and/or documentation that were so
far served by fedorahosted.org [*], not used for active code
hosting (at this time, anyway).

[*] locations like:
    https://fedorahosted.org/releases/q/u/quarterback/
    https://fedorahosted.org/releases/f/e/fence-agents/

>     and have stuck with linux-cluster referring to the mailing list
>     of the same name that once actively served to discuss the
>     cluster stack in question (and is quite abandoned nowadays)
> 
> - quickly added backup location links at
>   https://fedorahosted.org/cluster/ and
>   https://fedorahosted.org/cluster/wiki/FenceAgentAPI,

I've converted the latter to Markdown and exposed at
https://docs.pagure.org/ClusterLabs.fence-agents/FenceAgentAPI.md
The maintenance or just source access should be as simple as
cloning from ssh://git at pagure.io/docs/ClusterLabs/fence-agents.git
or https://pagure.io/docs/ClusterLabs/fence-agents.git, respectively.

>   i.e., the pages that seem most important to me, to allow for
>   smooth "forward compatibility"; the links currently refer to vain
>   stubs at ClusterLabs wiki, but that can be solved later on -- I am
>   still unsure if trac wikis at fh.o will be served in the next
>   phase or shut down right away and apparently this measure will
>   help only in the former case
> 
> What to do:
> - move releases over to pagure.io as well:
>   https://fedorahosted.org/releases/c/l/cluster/

Done for cluster:
http://releases.pagure.org/linux-cluster/cluster/

Tarballs for split components from here will eventually be uploaded
to respective release directories for the particular projects, e.g.,
http://releases.pagure.org/ClusterLabs/fence-agents/, it's a WIP.

> - possibly migrate some original wiki content to proper
>   "doc pages" exposed directly through pagure.io

So far I am just collecting the cluster wiki texts for possible
later ressurecting.

> - resolve the question of the linked wiki stubs and
>   cross-linking as such
> 
> Any comments?  Ideas?

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20170228/1aa53423/attachment.sig>