announce January 2017

announce@lists.fedoraproject.org

1 participants
2 discussions

Planned outage: Server Reboots / Firmware updates - 2017-01-25 21:00 UTC
by Kevin Fenzi 23 Jan '17

23 Jan '17

Planned Outage: Server reboots / Firmware updates - 2017-01-25 21:00 UTC There will be an outage starting at 2017-01-25 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2017-01-25 21:00 UTC' Reason for outage: We will be rebooting servers into the latest kernel and updated package sets, as well and performing some firmware updates on selected servers. No one service should be down very long, but all services may go up and down in the outage window as various servers are rebooted. Affected Services: All services may be up or down during the outage window, with the exception of cloud services (anything with .cloud.fedoraproject.org or fedorainfracloud.org in the name) Contact Information: Ticket Link: https://pagure.io/fedora-infrastructure/issue/5715 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above.

1 0

Fedorahosted.org sunset reminder: 2017-02-28
by Kevin Fenzi 12 Jan '17

12 Jan '17

(This is a resend reminder, with some additional faq information) Greetings. Fedora Infrastructure currently maintains two sites for general open source code hosting: fedorahosted.org and pagure.io. Fedorahosted.org was established in late 2007 using Trac for issues and wiki pages, Fedora Account System groups for access control and source uploads, and offering a variety of Source Control Management tools (git, svn, hg, bzr). With the rise of new workflows and source repositories fedorahosted.org has ceased to grow, adding just one new project this year and a handful the year before. Pagure.io was established in 2015, and is a modern Flask/Python based application. It is under rapid development and supports git repos for source code, docs, and tickets. The pull request model is used for changes along with many options for projects. Access control is standalone. New projects are self service and added all the time. Given the lack of growth and continued maintenance burden, Fedora Infrastructure would like to retire fedorahosted.org and encourage all its active projects to move to pagure.io (or whatever other place they feel best meets their needs). We have tenatively scheduled this retirement for February 28th, 2017. The Infrastructure team has already contacted owners of the top ten projects on Fedora Hosted for input on their needs. If your project has special needs, please contact the Infrastructure team (details below) to discuss options. After the sunset date, we will continue to provide raw data from public projects previously hosted at fedorahosted.org, but the service itself will be closed. We hope to provide this data for download for a few years, but won't provide it forever. A quick FAQ: Question: pagure.io has some issues/problems that prevent me from moving my project there. What can I do? Answer: Please file these issues against pagure: https://pagure.io/pagure/issues/ and we will try and address them as best we can. Note that not every feature request can be accommodated but the team will consider all requests. Question: How can I migrate my data from fedorahosted to pagure.io? Answer: You can use the https://pagure.io/pagure-importer tool to migrate trac data to pagure.io issues. Git repositories should be easily migrated with a push to the new pagure.io repo. Releases can be uploaded to pagure.io. There is also available a copr repo with the latest version of the importer tool: https://copr.fedorainfracloud.org/coprs/cverna/pagure-importer/ Question: I want to test things out, but not migrate yet, how can I do that? Answer: We have a https://stg.pagure.io/ test instance you are welcome to create projects on and test importing data. Note that from time to time we clear out this instance, so do not use it for any long term use. Question: What happens if I ignore this/don't get around to migrating my project by the 2017-02-28 deadline? Answer: We hope to provide the raw data from projects for download for a while, so you should be able to download a tar.xz of your old git repo and trac files, but it will be up to you to extract what you need from them, and we won't host them forever. The data sunset period would be at least several additional months. Question: Does pagure.io support hg, bzr, svn or cvs? Answer: no. Question: I have a mailing list at lists.fedorahosted.org, what happens to that? Answer: We have no plans to retire lists.fedorahosted.org at this time. All lists and archives will keep functioning. We hope soon to have a lists.pagure.io domain available and projects that wish to migrate can do so if they choose. Question: I have more questions, where can I get more answers? Answer: Feel free to ask on the infrastructure(a)lists.fedoraproject.org list or #fedora-admin on IRC Thanks, kevin

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

announce January 2017