empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] [Updated] (EMPIREDB-234) Update release guide for people.apache.org going out of service
Date Wed, 25 May 2016 21:59:12 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Francis De Brabandere updated EMPIREDB-234:
-------------------------------------------
    Description: 
Need to update release guide

people.apache.org web space is moving to home.apache.org
Hi folks,
as the subject says, people.apache.org is being decommissioned soon, and
personal web space is being moved to a new home, aptly named
home.apache.org ( https://home.apache.org/ )

IMPORTANT:
If you have things on people.apache.org that you would like to retain,
please make a copy of it and move it to home.apache.org. (note, you will
have to make a folder called 'public_html' there, for items to show up
under https://home.apache.org/~yourID/ ).

We will _NOT_ be moving your data for you. There is simply too much old
junk data on minotaur (the current people.apache.org machine) for it to
make sense to rsync it across, so we have made the decision that moving
data is up to each individual committer.

The new host, home.apache.org, will ONLY be for web space, you will not
have shell access to the machine (but you can copy data to it using SFTP
and your SSH key). Access to modify LDAP records (for project chairs)
will be moved to a separate host when the time comes.

There will be a 3 month grace period to move your data across. After
this time span (March 1st, 2016), minotaur will no longer serve up
personal web space, and visits to people.apache.org will be redirected
to home.apache.org.

With regards,
Daniel on behalf of the Apache Infrastructure Team.

PS: All replies to this should go to infrastructure@apache.org


AND

There is a staging area on the dist server for just this purpose:
https://dist.apache.org/repos/dist/dev/<project>
Upload the RC to that instead.

This is much better than the home directory on people because there is
no need to copy the files again when the vote succeeds.
Instead you can use svn/svnmucc to move the files to the dist release
directory (same repo, so files don't travel across the network).
Also there can be proper traceability of the RC artifacts; just
include the revision number of the dev tree in the vote e-mail.


=====second mail=====
Dear Apache Committer,

An infrastructure volunteer has stepped forward to automate the
migration of public_html content from minotaur.apache.org (the old
people.a.o) to home.apache.org (the new people.a.o). This e-mail is to
let you know how the migration was undertaken so you can understand the
results and take any further action if necessary.

Data was copied from /home/*/public_html on minotaur.a.o to a temporary
location on home.a.o. Note that only publicly readable content was
copied. Anything that would not have been served by httpd was not copied.

There was approximately 500GB of content. That was rather more than the
infrastructure team expected. A quick review of the largest files
identified that much of this volume was due to files being hosted in
committer's public_html directories that should be located elsewhere
(e.g. RCs, nightly builds, etc.). The personal web space section [1] of
the new committers guide has been updated to provide additional guidance
on what is, and is not, acceptable use.

After the first copy to the temporary location had completed, a second
copy was created for the filtering process. Using a second copy for the
filtering means that any files filtered in error can be restored from
the first copy should the need arise. The first copy of all the content
will be removed after a month or so.

The infra team then filtered the second copy (primarily based on file
size) and removed the inappropriate content. The removed content was
primarily releases, RCs, snapshots, copies of web sites, installers and
Maven repos.

After the review, the remaining content was copied to the individual
public_html directories if, and only if, that directory either did not
exist or was currently completely empty. In the end, around 110GB of
data was added to new public_html directories.

Users who have already created their public_html content on home.a.o but
would like access to a copy of their data from minotaur.a.o should
contact the infrastructure team.

Generally the infrastructure team expects individual public_html
directories to be of the order of a few hundred MB. This is not a hard
limit and will not be enforced as such. However, committers using in
excess of this may be required to justify why the additional storage is
required.

Please direct any questions to infrastructure@apache.org (Reply-To set)

Mark
on behalf of the ASF Infrastructure Team


[1] https://reference.apache.org/committer/newaccount#personal-web-space



  was:
Need to update release guide

people.apache.org web space is moving to home.apache.org
Hi folks,
as the subject says, people.apache.org is being decommissioned soon, and
personal web space is being moved to a new home, aptly named
home.apache.org ( https://home.apache.org/ )

IMPORTANT:
If you have things on people.apache.org that you would like to retain,
please make a copy of it and move it to home.apache.org. (note, you will
have to make a folder called 'public_html' there, for items to show up
under https://home.apache.org/~yourID/ ).

We will _NOT_ be moving your data for you. There is simply too much old
junk data on minotaur (the current people.apache.org machine) for it to
make sense to rsync it across, so we have made the decision that moving
data is up to each individual committer.

The new host, home.apache.org, will ONLY be for web space, you will not
have shell access to the machine (but you can copy data to it using SFTP
and your SSH key). Access to modify LDAP records (for project chairs)
will be moved to a separate host when the time comes.

There will be a 3 month grace period to move your data across. After
this time span (March 1st, 2016), minotaur will no longer serve up
personal web space, and visits to people.apache.org will be redirected
to home.apache.org.

With regards,
Daniel on behalf of the Apache Infrastructure Team.

PS: All replies to this should go to infrastructure@apache.org


AND

There is a staging area on the dist server for just this purpose:
https://dist.apache.org/repos/dist/dev/<project>
Upload the RC to that instead.

This is much better than the home directory on people because there is
no need to copy the files again when the vote succeeds.
Instead you can use svn/svnmucc to move the files to the dist release
directory (same repo, so files don't travel across the network).
Also there can be proper traceability of the RC artifacts; just
include the revision number of the dev tree in the vote e-mail.


> Update release guide for people.apache.org going out of service
> ---------------------------------------------------------------
>
>                 Key: EMPIREDB-234
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-234
>             Project: Empire-DB
>          Issue Type: Task
>            Reporter: Francis De Brabandere
>            Assignee: Francis De Brabandere
>            Priority: Minor
>
> Need to update release guide
> people.apache.org web space is moving to home.apache.org
> Hi folks,
> as the subject says, people.apache.org is being decommissioned soon, and
> personal web space is being moved to a new home, aptly named
> home.apache.org ( https://home.apache.org/ )
> IMPORTANT:
> If you have things on people.apache.org that you would like to retain,
> please make a copy of it and move it to home.apache.org. (note, you will
> have to make a folder called 'public_html' there, for items to show up
> under https://home.apache.org/~yourID/ ).
> We will _NOT_ be moving your data for you. There is simply too much old
> junk data on minotaur (the current people.apache.org machine) for it to
> make sense to rsync it across, so we have made the decision that moving
> data is up to each individual committer.
> The new host, home.apache.org, will ONLY be for web space, you will not
> have shell access to the machine (but you can copy data to it using SFTP
> and your SSH key). Access to modify LDAP records (for project chairs)
> will be moved to a separate host when the time comes.
> There will be a 3 month grace period to move your data across. After
> this time span (March 1st, 2016), minotaur will no longer serve up
> personal web space, and visits to people.apache.org will be redirected
> to home.apache.org.
> With regards,
> Daniel on behalf of the Apache Infrastructure Team.
> PS: All replies to this should go to infrastructure@apache.org
> AND
> There is a staging area on the dist server for just this purpose:
> https://dist.apache.org/repos/dist/dev/<project>
> Upload the RC to that instead.
> This is much better than the home directory on people because there is
> no need to copy the files again when the vote succeeds.
> Instead you can use svn/svnmucc to move the files to the dist release
> directory (same repo, so files don't travel across the network).
> Also there can be proper traceability of the RC artifacts; just
> include the revision number of the dev tree in the vote e-mail.
> =====second mail=====
> Dear Apache Committer,
> An infrastructure volunteer has stepped forward to automate the
> migration of public_html content from minotaur.apache.org (the old
> people.a.o) to home.apache.org (the new people.a.o). This e-mail is to
> let you know how the migration was undertaken so you can understand the
> results and take any further action if necessary.
> Data was copied from /home/*/public_html on minotaur.a.o to a temporary
> location on home.a.o. Note that only publicly readable content was
> copied. Anything that would not have been served by httpd was not copied.
> There was approximately 500GB of content. That was rather more than the
> infrastructure team expected. A quick review of the largest files
> identified that much of this volume was due to files being hosted in
> committer's public_html directories that should be located elsewhere
> (e.g. RCs, nightly builds, etc.). The personal web space section [1] of
> the new committers guide has been updated to provide additional guidance
> on what is, and is not, acceptable use.
> After the first copy to the temporary location had completed, a second
> copy was created for the filtering process. Using a second copy for the
> filtering means that any files filtered in error can be restored from
> the first copy should the need arise. The first copy of all the content
> will be removed after a month or so.
> The infra team then filtered the second copy (primarily based on file
> size) and removed the inappropriate content. The removed content was
> primarily releases, RCs, snapshots, copies of web sites, installers and
> Maven repos.
> After the review, the remaining content was copied to the individual
> public_html directories if, and only if, that directory either did not
> exist or was currently completely empty. In the end, around 110GB of
> data was added to new public_html directories.
> Users who have already created their public_html content on home.a.o but
> would like access to a copy of their data from minotaur.a.o should
> contact the infrastructure team.
> Generally the infrastructure team expects individual public_html
> directories to be of the order of a few hundred MB. This is not a hard
> limit and will not be enforced as such. However, committers using in
> excess of this may be required to justify why the additional storage is
> required.
> Please direct any questions to infrastructure@apache.org (Reply-To set)
> Mark
> on behalf of the ASF Infrastructure Team
> [1] https://reference.apache.org/committer/newaccount#personal-web-space



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message