cephlonaccess
Differences
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 13:10] 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 ===== | ||
| Requesting access to cephlon: | Requesting access to cephlon: | ||
| - | - Request a new user and password for accessing 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 You recived your Snipe-IT user and password login to Snipe-IT [[http://ceph-vm-14.tuc.stglabs.ibm.com:100/|Snipe-IT]]. | + | - 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 | - Go to manage API keys | ||
| - | - Click "Create new" | + | - Click on "Create new" |
| - | - Choose a name, click on "Create new" and keep your api key somewhere safe | + | - Choose a name of your choice, click on "Create new" and copy your API key to a safe place |
| {{ :snipe-it1.png |}} | {{ :snipe-it1.png |}} | ||
| Line 13: | Line 17: | ||
| {{:snipe-it2.png|}} | {{:snipe-it2.png|}} | ||
| - | - Clone the cephlon repo to your latop | + | - Clone the [[https://github.ibm.com/ceph/Cephlon/tree/main|cephlon]] repo to your workstation. |
| - | - Run the ./bootstrap script | + | - '' cd cephlon'' |
| - | - Create the .config file or rename the .config.template to .config, then place your snipe-it api key in the .config file along with the snipe-it url(you can find it in your tracker ticket) | + | - '' 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> | <code> | ||
| [api] | [api] | ||
| - | url = XXXXXXXXXXXXX | + | url = http://ceph25.ceph.tuc.ibm.com/api/v1/hardware |
| - | access_token = XXXXXXXXXXXXXXXX | + | access_token = <your snipe-it api token> |
| </code> | </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** | ||
cephlonaccess.1746709851.txt.gz · Last modified: 2025/05/08 13:10 by akraitman
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
