feat: add rtx5060ti gpu and ssh docs update

rekpero · web-flow · commit 93c52482d884 · 2025-05-19T14:50:03.000+04:00
Merge pull request #8 from spheronFdn/rekpero/5060-add
diff --git a/content/fizz/reward-details.mdx b/content/fizz/reward-details.mdx
@@ -50,12 +50,13 @@ Fizz Node can earn points based on the GPU resources they contribute to the netw
 | NVIDIA Titan RTX         | titanrtx        | Low 2    |    0.75     | 500 |   $0.132   |    $95.05  |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA RTX 3090          | rtx3090         | Low 2    |    0.75     | 500 |   $0.126   |    $90.65  |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA RTX 3090 Ti       | rtx3090ti       | Low 2    |    0.75     | 500 |   $0.148   |    $106.56 |  $0.75   |    $0.1     |      $0.01       |
-| NVIDIA RTX 4090          | rtx4090         | Medium 1 |    1        | 500 |   $0.175   |    $126.00 |  $0.75   |    $0.1     |      $0.01       |
+| NVIDIA RTX 5060 Ti       | rtx5060ti       | Medium 1 |    0.75     | 500 |   $0.140   |    $100.80 |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA RTX 4000 Ada      | rtx4000-ada     | Medium 1 |    1        | 500 |   $0.140   |    $100.80 |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA RTX 4000 SFF Ada  | rtx4000-sff-ada | Medium 1 |    1        | 500 |   $0.145   |    $104.40 |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA RTX A5000         | rtxa5000        | Medium 1 |    1        | 500 |   $0.088   |    $63.00  |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA Tesla V100        | v100            | Medium 1 |    1        | 500 |   $0.088   |    $63.00  |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA Tesla V100S       | v100s           | Medium 1 |    1        | 500 |   $0.092   |    $66.24  |  $0.75   |    $0.1     |      $0.01       |
+| NVIDIA RTX 4090          | rtx4090         | Medium 1 |    1        | 500 |   $0.175   |    $126.00 |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA L4                | l4              | Medium 1 |    1        | 500 |   $0.098   |    $71.40  |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA A10               | a10             | Medium 1 |    1        | 500 |   $0.091   |    $65.45  |  $0.75   |    $0.1     |      $0.01       |
 | NVIDIA A10G              | a10g            | Medium 1 |    1        | 500 |   $0.123   |    $88.20  |  $0.75   |    $0.1     |      $0.01       |
diff --git a/content/rent-gpu/deploy-container/_meta.ts b/content/rent-gpu/deploy-container/_meta.ts
@@ -1,6 +1,7 @@
 import { MetaRecord } from "nextra";
 
 const META: MetaRecord = {
+  "ssh-access": "Generate SSH Keys",
   "with-console": "Deploy with Console",
   "with-playground": "Deploy with Playground",
   "with-cli": "Deploy with CLI",
diff --git a/content/rent-gpu/deploy-container/ssh-access.mdx b/content/rent-gpu/deploy-container/ssh-access.mdx
@@ -0,0 +1,61 @@
+import { Callout } from "nextra/components";
+import { Steps } from 'nextra/components'
+
+# Generate SSH Keys
+
+# Overview
+SSH (Secure Shell) keys provide secure authentication for accessing your rented GPU instances on Spheron. This guide explains how to generate and set up SSH keys.
+
+## What are SSH Keys?
+SSH keys use public-key cryptography to authenticate connections:
+
+- **Public Key**: Uploaded to Spheron and installed on the GPU server
+- **Private Key**: Kept securely on your local machine
+- **Key Pair**: The public and private keys work together to establish secure connections
+
+## Prerequisites
+- Local machine with terminal access 
+- Spheron account with some credits
+
+This guide will walk you through generating a new SSH key pair and configuring it for use with your Spheron GPU deployments.
+
+<Steps>
+### Open a Terminal
+On your computer, open a terminal window.
+
+### Run the SSH Key Generation Command
+Type the following command and press Enter:
+
+```sh
+ssh-keygen
+```
+
+### Choose the Save Location
+Press Enter to accept the default location (usually `~/.ssh/id_rsa`).
+
+### Set a Passphrase (Optional)
+You will be prompted to enter a passphrase to secure your key:
+  1. To skip, just press Enter twice (once to skip, once to confirm an empty passphrase).
+  2. To add extra security, enter a passphrase. (You will need to enter this passphrase whenever you use your SSH key.)
+
+### Key Generation Complete
+1. Once the key is generated, you will see output showing where your private and public keys have been saved.
+2. Your public key file is usually named `id_rsa.pub` and is located in the `~/.ssh/` directory.
+
+### Upload Your Public Key to Spheron Console
+1. Go to **User Settings > SSH Settings** in your Spheron console.
+2. Upload the contents of your `id_rsa.pub` file.
+
+### Or Use CLI to setup SSH Key
+Use the following command to setup your SSH key:
+
+```sh
+sphnctl deployment ssh set-key ~/.ssh/id_rsa.pub
+```
+
+This will allow you secure, remote access to your rented GPU.
+</Steps>
+
+<Callout type="info">
+  If you already have a public key, you may use it and do not need to generate a new one.
+</Callout>
diff --git a/content/rent-gpu/deploy-container/with-cli.mdx b/content/rent-gpu/deploy-container/with-cli.mdx
@@ -89,7 +89,7 @@ sphnctl wallet balance --token uSPON
 **Note:** You can withdraw tokens from your unlocked balance at any time. However, if the tokens are in a locked state, you will not be able to withdraw them until you close your deployment. Upon closing, the locked tokens will be returned to the unlocked state after deducting provider charges and protocol fees.
 </Callout>
 
-### Set the C Base Mainnet RPC WSS URL
+### Set the Custom Base Mainnet RPC WSS URL
 
 To ensure reliable Base Mainnet deployments, you should supply your own dedicated base mainnet RPC endpoint. Public base mainnet RPCs are rate-limited and can lead to failed or stalled deployments under load.
 
diff --git a/content/rent-gpu/deploy-container/with-console.mdx b/content/rent-gpu/deploy-container/with-console.mdx
@@ -27,6 +27,36 @@ This guide will walk you through the steps to deploy and access your application
 3. Browse available GPUs or use the search function to find specific models
 4. Review pricing and specifications before selection
 
+### Deploy Template with SSH Access
+This section will guide you through the process of deploying a template with SSH access.
+<Steps>
+### Generate SSH Key Pair
+Generate an SSH key pair on your local machine, Follow the steps in [Generate SSH Keys](/rent-gpu/deploy-container/ssh-access)
+
+### Upload Your Public Key to Spheron Console
+Go to **User Settings > SSH Settings** in your Spheron console.
+
+Upload the contents of your `id_rsa.pub` file.
+
+### Deploy SSH Enabled Template
+Select the **Pytorch** template with SSH enabled and configure your deployment settings:
+
+- Adjust GPU count based on your needs
+- Choose your deployment duration
+
+### Enable SSH for Your Deployment
+Once the deployment service is active, go to SSH tab and connect to your rented GPU. It will take few minutes to activate.
+
+### Take the command from SSH tab and run it on your local machine
+
+```sh
+ssh -i <path-to-private-key> -p <port> root@<deployment-url>
+```
+</Steps>
+
+### Deploy Template with No SSH Access  
+This section will guide you through the process of deploying a template with no SSH access.
+<Steps>
 ### Configure Your Deployment
 1. Select the **Jupyter with PyTorch 2.4.1** template
    - Pre-configured with CUDA support
@@ -58,6 +88,7 @@ This guide will walk you through the steps to deploy and access your application
 - You can install additional packages as needed
 - You can also access the deployment shell to run any command you want and deployment logs to check the status of your deployment
 </Steps>
+</Steps>
 
 
 ## Verification
@@ -78,5 +109,4 @@ nvidia-smi
 - Monitor your memory usage carefully - if your notebook uses more memory than available (Out Of Memory/OOM), the server will automatically terminate and restart your notebook session, causing you to lose any unsaved work. You can check memory usage by running `nvidia-smi` in a notebook cell.
 - Your deployment environment is dedicated to you and not shared with other users, ensuring optimal performance for your workloads.
 
-
-Congratulations! Your app is now deployed and accessible. If you encounter any issues, reach out to [Spheron Discord Support](https://sphn.wiki/discord).
+Congratulations! You have successfully deployed your rented GPU and can now access it via SSH. If you encounter any issues, reach out to [Spheron Discord Support](https://sphn.wiki/discord).
diff --git a/content/rent-gpu/fizz-vs-provider.mdx b/content/rent-gpu/fizz-vs-provider.mdx
@@ -113,12 +113,11 @@ profiles:
           size: 1Gi
 ```
 
-- Limited resource availability - max 32 units of CPU, 128Gi of memory and 2000Gi of storage, and only 1 GPU in a Fizz node
+- Limited resource availability - max 32 units of CPU, 128Gi of memory and 2000Gi of storage
 - Variable performance - Can have downtime if fizz node is stopped by the user
-- Limited scaling options - Updating resource in runtime is not supported
+- Updating resource in runtime is supported
 - Shared Memory (SHM) is not supported
-- You can't change count to multiple containers in a single deployment
-- Can't deploy multiple GPUs for a single deployment
+- You can change count to multiple containers in a single deployment
 
 ### 3. Logging and Monitoring
 
@@ -145,23 +144,23 @@ sphnctl deployment logs --lid 123 --startup
 sphnctl deployment logs --lid 123
 ```
 
-- Basic logging capabilities
-- Startup logs available - to check what's happening during the startup of your application
-- Limited filtering options
+- Real-time log streaming - you can follow the logs as they are generated
+- Service-specific logging
 - Detailed event tracking - you can see all the events happening in your deployment
 
 ### 4. Deployment Updates
 
 #### Provider Mode
-- Dynamic resource scaling
-- Live environment updates
-- Container image updates
-- Zero-downtime updates
-- Secure and more reliable
+- Dynamic resource scaling - you can update the resource in runtime
+- Live environment updates - you can update the environment variables in runtime
+- Container image updates - you can update the container image in runtime
+- Zero-downtime updates - you can update the container image in runtime without downtime
+- Secure and more reliable - you can update the container image in runtime without downtime
 
 #### Fizz Mode
-- Can't update resource in runtime
-- May require redeployment to update deployment resource specification
+- Dynamic resource scaling - you can update the resource in runtime
+- Live environment updates - you can update the environment variables in runtime
+- Container image updates - you can update the container image in runtime
 
 ## Best Practices
 
diff --git a/content/rent-gpu/icl.mdx b/content/rent-gpu/icl.mdx
@@ -680,7 +680,7 @@ This is particularly useful when you need to:
 The region must match one of Spheron's [supported region codes](/rent-gpu/supports#supported-regions). If not specified, your application can be deployed in any available region.
 </Callout>
 
-#### 2. Exclude Region
+#### 2. Region Exclusion
 Use the `exclude_region` attribute to specify which geographic regions your application should not be deployed in:
 
 ```yaml
@@ -723,10 +723,36 @@ This is helpful when you:
 - Want to distribute your workload across multiple preferred providers
 
 <Callout type="info">
-This works in both `provider` and `fizz` modes. In `fizz` mode, it will select fizz nodes that are connected to your chosen provider(s).
+This works in both `provider` and `fizz` modes. In `fizz` mode, it will select fizz nodes that are connected to your chosen gateway(s).
 </Callout>
 
-#### 3. Fizz Node Selection
+#### 4. Provider Exclusion
+
+You can exclude a provider from your deployment using the `exclude_provider` attribute:
+
+```yaml
+attributes:
+  provider_exclude: "0x1234...5678"  # Replace with actual provider address
+```
+
+You can also exclude multiple providers as a semicolon-separated list:
+
+```yaml
+attributes:
+  provider_exclude: "0x1234...5678;0xabcd...1234;0xefgh...5678"  # Multiple provider addresses
+```
+
+This is useful when you:
+- Want to exclude a specific provider from deployment
+- Need to ensure your application does not run on a specific provider
+- Are testing provider-specific functionality
+- Have compliance requirements that prohibit deployment on certain providers
+
+<Callout type="info">
+This works in both `provider` and `fizz` modes. In `fizz` mode, it will exclude fizz nodes that are connected to the specified gateway(s).
+</Callout>
+
+#### 5. Fizz Node Selection
 For deployments using `fizz` mode, you can target a specific fizz node:
 
 ```yaml
@@ -747,7 +773,29 @@ This is useful when you:
 - Are testing node-specific functionality
 - Want to distribute your workload across multiple preferred fizz nodes
 
-#### 4. Bandwidth Selection
+#### 6. Fizz Node Exclusion
+
+You can exclude a fizz node from your deployment using the `exclude_fizz` attribute:
+
+```yaml
+attributes:
+  fizz_exclude: "0x1234...5678"  # Replace with actual fizz node address
+```
+
+You can also exclude multiple fizz nodes as a semicolon-separated list:
+
+```yaml
+attributes:
+  fizz_exclude: "0x1234...5678;0xabcd...1234;0xefgh...5678"  # Multiple fizz node addresses
+```
+
+This is useful when you:
+- Want to exclude a specific fizz node from deployment
+- Need to ensure your application does not run on a specific fizz node
+- Are testing fizz node-specific functionality
+- Have compliance requirements that prohibit deployment on certain fizz nodes
+
+#### 7. Bandwidth Selection
 <Callout type="info">
   **Note:** This is only applicable for fizz mode deployments.
 </Callout>
@@ -773,7 +821,9 @@ profiles:
       attributes:
         region: us-east                              # Geographic region
         desired_provider: "0x1234...5678"            # Specific provider
+        provider_exclude: "0x1234...5678"            # Exclude specific provider
         desired_fizz: "0xabcd...ef12"                # Specific fizz node
+        fizz_exclude: "0xabcd...ef12"                # Exclude specific fizz node
         bandwidth: 100mbps                            # Minimum bandwidth
       pricing:
         web:
