This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cephlonaccess [2025/05/08 11:46] akraitman [Requesting Access] |
cephlonaccess [2025/11/16 14:55] (current) akraitman [Cephlon] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Cephlon ====== | ====== Cephlon ====== | ||
| + | |||
| + | **__For now this tool can only be used in the downstream tucson lab__** (We are working in making it available in the upstream lab) | ||
| + | |||
| + | |||
| ===== Requesting Access ===== | ===== Requesting Access ===== | ||
| - | To request access to cephlon, | + | Requesting access to cephlon: |
| - | - Request for a user and password for the Snipe-IT tool **. | + | - Request a new snipe-it user and password**. **write down your desired username, e-mail address and public ssh key** |
| - | - [[https://tracker.ceph.com/projects/internal_lab/issues/new|File a ticket]]. *** | + | - [[https://tracker.ceph.com/projects/internal_lab/issues/new|File a ticket]]. ** |
| + | - After receiving your Snipe-IT user and password login to the Snipe-IT tool[[http://ceph25.ceph.tuc.ibm.com/|Snipe-IT]]. | ||
| + | - Go to manage API keys | ||
| + | - Click on "Create new" | ||
| + | - Choose a name of your choice, click on "Create new" and copy your API key to a safe place | ||
| + | |||
| + | {{ :snipe-it1.png |}} | ||
| + | |||
| + | {{:snipe-it2.png|}} | ||
| + | |||
| + | - Clone the [[https://github.ibm.com/ceph/Cephlon/tree/main|cephlon]] repo to your workstation. | ||
| + | - '' cd cephlon'' | ||
| + | - '' docker build -t cephlon .'' | ||
| + | - In the same directory, create a ''.config'' file or ''cp configs/.config.template .config'' and replace ''<your snipe-it api token>'' with your API token. | ||
| + | |||
| + | <code> | ||
| + | |||
| + | [api] | ||
| + | url = http://ceph25.ceph.tuc.ibm.com/api/v1/hardware | ||
| + | access_token = <your snipe-it api token> | ||
| + | |||
| + | </code> | ||
| + | |||
| + | Test that everything is configured correctly by running ''./cephlon status'' | ||
| + | |||
| + | **For more information on how to use cephlon you can checkout the readme file in the cephlon repo** | ||