https://wiki.sepia.ceph.com/ 2026-04-06T11:15:05+0000 https://wiki.sepia.ceph.com/ https://wiki.sepia.ceph.com/lib/tpl/dokuwiki/images/favicon.ico text/html 2020-03-04T14:59:46+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:adding-new-machines&rev=1583333986&do=diff Adding New Machines This procedure should be followed when new machines is being added to the Sepia lab. Step 1: Ansible Inventory * cd /path/to/ceph-sepia-secrets * git checkout master && git pull * git checkout -b wip-new-hosts (or similar branch name) text/html 2021-03-04T20:11:27+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:adding_new_machines&rev=1614888687&do=diff Adding New Machines This procedure should be followed when new machines is being added to the Sepia lab. Step 1: Ansible Inventory * cd /path/to/ceph-sepia-secrets * git checkout master && git pull * git checkout -b wip-new-hosts (or similar branch name) text/html 2023-11-21T18:14:26+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:ceph-release-faq&rev=1700590466&do=diff Ceph Release FAQ The full release process is defined here: <https://docs.ceph.com/en/latest/dev/release-process/> The following FAQ is based on questions that arose when we previously followed the release process. See Walkthrough: Ceph Release Process for a live explanation of this document. * What if something went wrong with the ceph-tag job and a version commit PR was not created? text/html 2021-07-14T19:14:16+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:github_permissions&rev=1626290056&do=diff GitHub Permissions When a new developer joins the team/community, they will need push access to the Ceph GitHub repos. You need to be an Org Admin to do this. * Go to <https://github.com/orgs/ceph/teams/ceph/members> * * Enter the user's GitHub username * Listing All Users in All Teams text/html 2026-02-12T17:40:15+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:graceful-shutdown&rev=1770918015&do=diff Graceful Shutdown Procedure T-4h * Stop the teuthology dispatcher on soko04 systemctl stop teuthology-dispatcher@trial.service * Log in to Jenkins and Prepare for Shutdown * Begin shutting off Jenkins builders if they're not running a job text/html 2025-02-19T15:48:15+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:installing_new_arm_machines&rev=1739980095&do=diff Installing New ARM Machines This procedure should be followed when installing ARM type machines with cobbler. The reason for doing so is since cobbler doesn't support installing using uefi, we will need to create a menuentry in grub.conf with the required settings text/html 2026-03-07T01:22:13+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:lab-extras&rev=1772846533&do=diff Managing packages in lab-extras lab-extras is a repo of miscellaneous packages we want testnodes to have access to. <http://apt-mirror.front.sepia.ceph.com/lab-extras/> An example of a time we'd want to use this is when a package from CentOS 7.3 has a bugfix we want to test on CentOS 7.2. The RPM can be downloaded from the CentOS 7.2 CM (testing) repo, placed in the CentOS 7 lab-extras repo and installed. Example: text/html 2025-04-01T13:48:09+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:major-distro-release&rev=1743515289&do=diff New Major Distro Release Procedure This page will cover all the components of the Upstream testing process that need to be modified in order to start building packages for and testing new major Linux distribution versions. Steps * ceph-cm-ansible * Add the distro to text/html 2023-11-15T22:41:17+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:new-ceph-release&rev=1700088077&do=diff WIP - Procedure to Add a New Major Ceph Release This page covers all the areas and components that need to be updated to accomodate a new upstream Ceph (lettered) release. THIS IS NOT YET ALL ENCOMPASSING Steps We'll use Quincy as an example * text/html 2023-09-07T02:09:37+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:nfs-ganesha&rev=1694052577&do=diff nfs-ganesha builds and conventions NFS Ganesha CI is hosted on Openshift and it is located here: <https://jenkins-nfs-ganesha.apps.ocp.cloud.ci.centos.org>. It is also built on the sepia lab's Jenkins server, and builds are located here: <https://shaman.ceph.com/builds/nfs-ganesha/> Stable releases are located here: <https://github.com/nfs-ganesha/nfs-ganesha/releases> Version Logic Last updated 2023-08-24 text/html 2024-10-29T18:15:54+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:replace-nic&rev=1730225754&do=diff Replacing a Hardware NIC Steps * File a ticket with the labs team * Updated 29Oct2024: <https://redhat.service-now.com/help?id=sc_cat_item&sys_id=4c66fd3a1bfbc4d0ebbe43f8bc4bcb6a&appID=694b61031bd49894477e43fccd4bcbbd> * Once the Labs team replaces the NIC, log into the OS via console smithiXXX and figure out the new MAC address using ifconfig and ethtool tools. * Update the MAC address in the ansible inventory text/html 2018-04-03T21:30:12+0000 Anonymous (anonymous@undisclosed.example.com) https://wiki.sepia.ceph.com/doku.php?id=tasks:scheduled-maintenance&rev=1522791012&do=diff Planned/Scheduled Maintenance Procedures Historically, infrastructure maintenance has been on an as-needed “if it ain't broke, don't fix it” basis. Now that most Infrastructure services are highly available and the lab network/services/suite have stabilized, we're able to afford occasional downtime to perform system updates, hardware swaps,