add info for projects and quotas

Signed-off-by: Gabin L <gabin.lanore@gmail.com>

Author: msterhuj

docs/cloud/cert.md

@@ -1,2 +1,3 @@
 # Install Certificates
 
+You can download the Public ROOT CA of the laboinfra at [Laboinfra_Root_CA_2024.pem](https://docs.laboinfra.net/assets/Laboinfra_Root_CA_2024.pem)

docs/cloud/cli.md

@@ -2,4 +2,4 @@
 
 TODO
 
-If you need to get help use the `--help` or contact us
+If you need to get help use `labctl --help` or contact us with a discord ticket

docs/cloud/getting-started.md

@@ -82,4 +82,4 @@ For the domain, use `esgi` and for the username, use the username you use to log
 
 ## Next steps
 
-For more information about how to use labctl, check the [CLI documentation](cli.md).
+You will need to give quota to the project you created to be able to create resources. You can check the [Projects and Quotas](projects_quotas.md) documentation for more information.

docs/cloud/projects_quotas.md

@@ -0,0 +1,100 @@
+# Manage projects and quotas
+
+## Introduction
+
+On Laboinfra, you get a quota assigned by an admin. This quota includes resources like RAM, CPU, and storage, and it’s yours to distribute across different projects as needed.
+
+Using the API or the labctl CLI, you can:
+
+- Create new projects,
+- Add members to your projects,
+- Allocate your quota however you want between your projects.
+
+This gives you full control over how you use your resources, making it easy to collaborate and work on multiple school projects efficiently.
+
+## Projects
+
+### Create a new project
+
+```bash
+labctl project create PROJECT_NAME
+```
+
+!!! info
+    Project names are suffixed with a unique identifier to ensure they are unique across the platform.
+
+### List your projects
+
+```bash
+labctl project list
+```
+
+### Add a member to a project
+
+```bash
+labctl project add-user PROJECT_NAME MEMBER_NAME
+```
+
+### Remove a member from a project
+
+```bash
+labctl project del-user PROJECT_NAME MEMBER_NAME
+```
+
+!!! info
+    Before removing a member from a project, make sure your project have enough resources quota to accommodate
+
+### Delete a project
+
+```bash
+labctl project delete PROJECT_NAME
+```
+
+??? warning
+    In order to delete a project, you must first delete all the resources associated with it (VMs, disks, etc.) and remove all quotas allocated to it.
+
+## Quotas
+
+Type of quotas:
+
+| Type  | Description |
+|-------|-------------|
+| `cpu` | CPU cores   |
+| `mem` | RAM in GB   |
+| `sto` | Disk in GB  |
+
+### Display your quota
+
+With the me command you get global information about your account, including your quota.
+
+```bash
+labctl me
+```
+
+### Allocate quota to a project
+
+```bash
+labctl quota set PROJECT_NAME TYPE VALUE
+```
+
+### Display quota for a project
+
+With this command you can see how much quota is allocated to a project and who share the quota to the project.
+
+```bash
+labctl quota show-project PROJECT_NAME
+```
+
+### Remove quota from a project
+
+If you just want to decrease the quota allocated to a project, you can use the same command as allocating quota, but with the new value you want to set.
+
+```bash
+labctl quota set PROJECT_NAME TYPE VALUE
+```
+
+If you want to remove all the quota allocated to a project, you can use the following command:
+
+```bash
+labctl quota unset PROJECT_NAME TYPE
+```

docs/cloud/tos.md

@@ -14,15 +14,15 @@ Access is restricted to ESGI students and teachers. Each user must use their own
 
 ## 4. Best Practices and Restrictions
 
-### What You Can Do:
+### What You Can Do
 
 - Deploy virtual machines and use resources for educational purposes.
 - Test applications, develop projects, and experiment with cloud technologies.
 - Use the cloud for academic projects and research.
 - Respect the quotas allocated to your account.
 - Secure your access and data.
 
-### What Is Prohibited:
+### What Is Prohibited
 
 - Hosting publicly accessible services without authorization.
 - Engaging in illegal activities (hacking, DDoS, cryptomining, etc.).
@@ -36,6 +36,7 @@ Access is restricted to ESGI students and teachers. Each user must use their own
 
 - Each user is responsible for actions performed with their account.
 - Any suspicious or non-compliant activity may be reported and investigated.
+- Monitoring and Intervention: The Infrastructure Lab team reserves the right to access any hosted resources if suspicious activity is detected that could compromise the security, stability, or integrity of the services. This includes, but is not limited to, unauthorized access attempts, abuse of resources, or any actions that violate the platform’s acceptable use policies. Any attempt to obstruct an investigation or restrict administrator access will result in an immediate account suspension and an official report to the ESGI administration.
 - If a user performs unauthorized actions or endangers the infrastructure, the incident will be immediately reported to the ESGI administration. The user may be required to explain their actions at a disciplinary committee.
 - VM updates and security are the user’s responsibility.
 - In case of issues, contact the team via the #ticket-help channel on Discord.

mkdocs.yml

@@ -21,6 +21,7 @@ nav:
   - Cloud:
     - Getting started: cloud/getting-started.md
     - Install certificate: cloud/cert.md
+    - Manage projects and quotas: cloud/projects_quotas.md
     - CLI reference: cloud/cli.md
     - Terms of service: cloud/tos.md
   - Game:
@@ -38,6 +39,8 @@ markdown_extensions:
   - pymdownx.inlinehilite
   - pymdownx.snippets
   - pymdownx.superfences
+  - admonition
+  - pymdownx.details
   - attr_list
   - pymdownx.emoji:
       emoji_index: !!python/name:material.extensions.emoji.twemoji