Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Fix some small typos.

Browse source
This commit is contained in:
Bussi Andrea 2022-02-19 00:33:28 +01:00
parent 254dd5f50d
commit d9066bb553
5 changed files with 25 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

22
modules/sysadmin_guide/pages/accountdeletion.adoc
View file

@ -173,7 +173,7 @@ username/groupname rather than UID/GID.
[WARNING]
.Warning
====
Needs more eyes This list may not be complete.
Needs more eyes. This list may not be complete.
====
* Check the databases for koji, pkgdb, and bodhi for occurrences of
@ -200,7 +200,7 @@ themselves b/c they're getting a new home directory).
[WARNING]
.Warning
====
Needs more eyes This list may not be complete.
Needs more eyes. This list may not be complete.
====
* grep through ansible for occurrences of the group name.
* Check for group-members,group-admins,group-sponsors@fedoraproject.org
@ -223,7 +223,7 @@ reused.
.Note
====
Recommended to rename instead When not strictly necessary to purge all
traces of an account, it's highlyrecommended to rename the user or group
traces of an account, it's highly recommended to rename the user or group
to something like DELETED_oldusername instead of deleting. This avoids
the problems and additional checking that we have to do below.
====
@ -232,8 +232,10 @@ the problems and additional checking that we have to do below.
[WARNING]
.Warning
====
Needs more eyes This list may be incomplete. Needs more people to look
at this and find places that may need to be updated
Needs more eyes.
This list may be incomplete. Needs more people to look
at this and find places that may need to be updated.
====
* Check everything for the #Rename Accounts case.
* Figure out what boxes a user may have had access to in the past. This
@ -257,7 +259,7 @@ Any files owned by that uid must be reassigned to another user or::
.Warning
====
What to do about backups? Backups pose a special problem as they may
contain the uid that's being removed. Need to decide how to handle this
contain the uid that's being removed. Need to decide how to handle this.
====
* Add other places to check here
@ -266,8 +268,10 @@ contain the uid that's being removed. Need to decide how to handle this
[WARNING]
.Warning
====
Needs more eyes This list may be incomplete. Needs more people to look
at this and find places that may need to be updated
Needs more eyes.
This list may be incomplete. Needs more people to look
at this and find places that may need to be updated.
====
* Check everything for the #Rename Groups case.
* Figure out what boxes may have had files owned by that group. This
@ -289,6 +293,6 @@ removed.
.Warning
====
What to do about backups? Backups pose a special problem as they may
contain the gid that's being removed. Need to decide how to handle this
contain the gid that's being removed. Need to decide how to handle this.
====
* Add other places to check here

2
modules/sysadmin_guide/pages/database.adoc
View file

@ -161,7 +161,7 @@ from pg_database order by xids_remaining;
== Restart Procedure
If the database server needs to be restarted it should come back on it's
If the database server needs to be restarted it should come back on its
own. Otherwise each service on it can be restarted:
....

8
modules/sysadmin_guide/pages/orientation.adoc
View file

@ -56,7 +56,7 @@ make sure you ask yourself what is important to you and make sure to
provide data, we like that. We generally communicate on libera.chat
in #fedora-admin. We have our weekly meetings on IRC and its the
quickest way to get in touch with everyone. Secondary to that we use the
mailing list. After that its our ticketing system and
mailing list. After that it's our ticketing system and
talk.fedoraproject.org.
_Welcome to the team!_
@ -110,8 +110,8 @@ https://pagure.io/fedora-infrastructure/issues
When you find a ticket that interests you contact your sponsor or the
ticket owner and offer help. While you're getting used to the way things
work, don't be offput by someone saying no or you can't work on that. It
happens, sometimes its a security thing, sometimes its a "I'm half way
through it and I'm not happy with where it is thing." Just move on to
happens, sometimes it's a security thing, sometimes it's a "I'm half way
through it and I'm not happy with where it is" thing. Just move on to
the next ticket and go from there.
Also don't be surprised if some of the work involved includes testing on
@ -121,7 +121,7 @@ no access at all. Doing this kind of work is a sure fire way to get in
to more groups and get more involved. Don't be afraid to take on tasks
you don't already know how to do. But don't take on something you know
you won't be able to do. Ask for help when you need it and keep in
contact with your sponsor so you know
contact with your sponsor.
== Ansible

2
modules/sysadmin_guide/pages/outage.adoc
View file

@ -168,7 +168,7 @@ be pushed to show the services are restored.
[IMPORTANT]
====
Additionally update any SOP's that may have changed in the course of the outage
Additionally update any SOP's that may have changed in the course of the outage.
====
=== Unplanned Outage

12
modules/sysadmin_guide/pages/status-fedora.adoc
View file

@ -81,10 +81,10 @@ and relocate the swarm.
....
+
____
* Note that OutageFinish is optional, but should really only be ommited
* Note that OutageFinish is optional, but should really only be omitted
if the projected / or actual outage time is unknown.
* When providing dated, keep the timezone offset at +0000 / UTC
datetimes
* When providing a date, keep the timezone offset at +0000 / UTC
datetimes.
____
=== Moving an outage
@ -129,7 +129,7 @@ moving outages)
=== Publishing theme changes
If your changes involve changes to the theme, run the following command
to upload everything content and theme changes to the live server:
to upload everything (content and theme changes) to the live server:
....
make upload-theme
@ -153,8 +153,8 @@ In a different terminal upload requested file to AWS S3 bucket:
echo SOME_VALUE >myfile
aws --profile statusfpo s3 cp myfile s3://status.fedoraproject.org/.well-known/acme-challenge/SOME_FILE
....
. Verify that uploaded file is available under the rigt URL. If previous
certificate already expired you may need to run curl with -k option:
. Verify that uploaded file is available under the right URL. If the previous
certificate is already expired, you may need to run curl with -k option:
+
....
curl -kL http://www.fedorastatus.org/.well-known/acme-challenge/SOME_FILE