Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/markitobonito/cloud_repositorio/llms.txt

Use this file to discover all available pages before exploring further.

A slice is the top-level resource you manage in Cloud Repositorio. You create it first, build its topology by adding VMs and creating links between them, then deploy everything to the cluster in a single operation. All resources within a slice share an isolated VLAN pool and are owned by a single user.

​
Slice lifecycle

1

Create a slice

Select 2. Create Slice from the main menu and enter a name for your slice.The orchestrator assigns a unique slice_id and a VLAN pool based on the formula:
vlan_pool_start = 100 + (slice_id % 100) * 20
vlan_pool_end   = vlan_pool_start + 19
For example, a slice with ID 1000 receives the pool 100–119 (20 VLANs).The slice is stored in the database with status design and the slice_id is returned:
Slice created! ID: 1000
2

Add VMs

Select 3. Add VM to Slice and repeat for each VM you want in the slice. Provide the slice ID, a VM name, a flavor, the number of data interfaces, and whether to enable internet access.Each VM is registered with a worker assignment (assigned round-robin across 10.0.10.1, 10.0.10.2, 10.0.10.3 by default) and a QCOW2 backing image path on that worker. VMs remain in design status.See Add, configure, and remove VMs for full details.
3

Create links

Select 4. Create Link between VMs to connect data interfaces between VMs. Each link consumes one VLAN from the slice’s pool.You can create up to 20 links per slice (limited by the 20-VLAN pool). Interfaces involved in a link are updated with the assigned vlan_id and a link_id.
4

Review topology

Select 5. View my Slices to inspect the current topology before deploying.Output format:
======================================================================
Slice 1000 [design]: 2 VMs, 1 Links, VLAN pool: 100-119
  └─ VM 1001: web (VNC: 5901, Worker: 10.0.10.1, Disk: 1GB)
      eth0: MAC 52:54:00:03:e9:00, VLAN: 400, unconnected
      eth1: MAC 52:54:00:03:e9:01, VLAN: 100, Link: 1
  └─ VM 1002: db (VNC: 5902, Worker: 10.0.10.2, Disk: 2.2GB)
      eth0: MAC 52:54:00:03:ea:00, unconnected
      eth1: MAC 52:54:00:03:ea:01, VLAN: 100, Link: 1
  Link 1: VM1001.eth1 <-> VM1002.eth1 (VLAN 100)
======================================================================
Each VM line shows its ID, name, VNC port, assigned worker, and disk size. Each interface line shows its MAC, VLAN assignment (if any), and link connection status.
5

Deploy the slice

Select 6. Deploy Slice and enter the slice ID. The orchestrator performs these steps in order:
  1. If any VM has internet enabled, configures VLAN 400 (10.60.7.0/24, gateway 10.60.7.1, DHCP) on the network node.
  2. For each link, configures a VLAN with a /24 subnet and gateway derived from the VLAN ID (e.g., VLAN 101 → 192.168.101.0/24, gateway 192.168.101.1) with DHCP enabled.
  3. Launches all VMs via QEMU on their assigned workers. Each running VM receives a PID.
On success the slice status changes to running:
Slice deployed successfully
6

Delete the slice

Select 7. Delete Slice and enter the slice ID.If the slice is running, the orchestrator first stops all QEMU processes on the workers and removes the OVS VLAN configuration for each link. Regardless of status, QCOW2 images for all VMs are deleted from the workers, the slice is removed from the database, and the user’s used_vms count is decremented.
Deleting a running slice kills all QEMU processes on workers and permanently removes QCOW2 images. Any unsaved VM state is lost and cannot be recovered.

​
Slice status reference

StatusMeaning
designSlice created; VMs and links registered but no QEMU processes running
runningSlice fully deployed; all VMs started and VLANs configured on the network node
The CLI tracks a current_slice context (ID and owner) for the most recently created slice. This is used by the SIGINT handler to clean up the in-progress slice if the orchestrator process is interrupted during design. Only one slice occupies this context at a time; creating a new slice replaces the previous entry.

Build docs developers (and LLMs) love

Get started for freeTalk to us