Ibiblio downtime/outage 2018-07-11 (affects torrents/people)
Created seconds ago by smooge
Modified just now
There will be an outage starting at 2018-07-10 14:00UTC, which will
last approximately 6 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2018-07-10 14:00UTC'
Reason for outage:
The racks the servers are in are getting decommissioned and the
servers need to be moved to across the network.
Affected Services:
Any service housed in ibiblio including torrent and fedorapeople.org
Contact Information:
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/7085
Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
--
Stephen J Smoogen.
Dear all,
You are kindly invited to the meeting:
Infra Office Hours on 2018-07-10 from 18:00:00 to 19:00:00 UTC
At fedora-admin(a)irc.freenode.net
The meeting will be about:
Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features.
Source: https://apps.fedoraproject.org/calendar/meeting/9255/
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-07-05 at 14:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2018-07-05)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info bowlofeggs is on PTO
#info abompard is on PTO
#info pingou is on half-time PTO
#info tflink is going on extended PTO
#info major Ibiblio outage 2018-07-10
#info FLOCK in Dresden is 2018-08-08
#info visit to PHX2 will be happenening 2018-08-15->2018-08-18
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic Oncall
#info Summary of last week?
#info Kevin is on call from 2018-07-06->2018-07-12
#info Relrod is on call from 2018-07-13->2018-07-19
#info Smooge is on call from 2018-07-20->2018-07-26
#info Kevin? is on call from 2018-07-27->2018-08-01
#info Smooge is on call from during FLOCK
#topic Flock Talks People want to see
#topic pkgdb retirement - kevin
#info many items found last meeting. any resolutions?
#topic bugzilla5 in September - aikidouke
#info https://pagure.io/fedora-infrastructure/issue/7028
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
#topic letsencrypt by your host relrod
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
improvement,
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#info
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
This patch (available in email attachment) is to create new ostree
commit when there is no content changes since last commit during
updates compose run. By passing force_new_commit as True, pungi
runs rpm-ostree command with option --force-nocache .
More details are in releng ticket - https://pagure.io/releng/issue/7585
Thanks,
Sinny
On 28 June 2018 at 16:57, Stephen John Smoogen <smooge(a)gmail.com> wrote:
> There will be an outage starting at 2018-07-02 21:00UTC, 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 '2018-07-02 21:00UTC'
>
This outage is complete.
--
Stephen J Smoogen.
Dear all,
You are kindly invited to the meeting:
Infra Office Hours on 2018-07-03 from 18:00:00 to 19:00:00 UTC
At fedora-admin(a)irc.freenode.net
The meeting will be about:
Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features.
Source: https://apps.fedoraproject.org/calendar/meeting/9255/
Good Morning Everyone,
So yesterday we held a meeting on #fedora-apps about the future of PDC in Fedora.
We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora
Here is the gist of it:
What do we currently store in PDC:
* modules data - the list of what modules have been built, what rpms are in them,
and which ones are active or not.
* Stream branches, branch ownership, retirement dates (EOL/SLE)
* release/life-circle tracking
* product and product versions (fedpkg gets active Fedora and EPEL releases
from product versions endpont)
* critpath boolean on packages (bodhi uses this)
* metadata from composes (RPMS/images)
* "dependency" data about which rpms depend on which other rpms and which
containers include other rpms. This is not used by anything and can be
de-prioritized, dropped. (It was originally going to be used in Freshmaker.)
Endpoints:
* release-component-relationships
* release-components
* List of all packages: fedora-packages uses this list to know what to index.
It sets up the "for loop" from which fedora-packages pulls data from all our
other systems.
Endpoints:
* global-components
After some discussion the decision we reached was:
* The "dependency" data in its current form can be dropped. It's something we'll
need in the future but the data structure will most likely need to be
adjusted so let's just drop the existing data and worry about this later.
* The critpath boolean can just be imported into bodhi itself, especially
considering that bodhi is the only tool using this flag.
* The modules data is entirely going to move into MBS
Everything else (ie: composes metadata, release/life-circle tracking,
package/branches information) will need to find a new home.
This new home will be a new django app using the Django Rest Framework (DRF) in
which we will import the PDC apps as needed (potentially adjusting them where
desired).
- kellin has agreed to be the project leader for this work but needs a team to
do the actual work.
- pingou has agreed to look for said team
If you have any worries, questions or suggestions or if you want to join the
effort, please let us know :)
Finally some links:
Minutes: https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.201…
Minutes (text): https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.201…
Log: https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.201…
Have a nice day,
Pierre