agentleFS
QubinodeQubinode/qubinode_navigator/.cursor/rules/vm-operations.mdc

qubinode_navigator / rules

Cursor rule1 starsChanged 10 months agoMITView on GitHub

Located in airflow/plugins/qubinode/operators.py: Before creating VMs, verify: 1. Sufficient memory: free -h 2. Disk space: df -h /var/lib/libvirt 3. Libvirt running: systemctl is-active libvirtd 4. Network available: virsh net-list For DAGs that need to run commands on the host:

The file

We split this vm-operations.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before creating VMs, verify:

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
vm-operations.mdc
---
globs: ["**/*vm*", "**/*kcli*", "**/infrastructure/**"]
alwaysApply: false
---

# VM Operations Guide

## kcli Commands

```bash
# List VMs
kcli list vm

# Get VM info
kcli info vm <vm-name>

# Create VM
kcli create vm <name> -i <image> -P memory=<MB> -P cpus=<N> -P disks=['{"size": <GB>}']

# Delete VM
kcli delete vm <name> -y

# List available images
kcli list images

# List networks
kcli list network
```

## Custom Operators

Located in `airflow/plugins/qubinode/operators.py`:

```python
from qubinode.operators import KcliVMCreateOperator, KcliVMDeleteOperator, KcliVMListOperator

# Create VM
create_task = KcliVMCreateOperator(
    task_id='create_vm',
    vm_name='my-vm',
    image='centos-stream-10',
    memory=4096,
    cpus=2,
    disk_size='20G',
)

# Delete VM
delete_task = KcliVMDeleteOperator(
    task_id='delete_vm',
    vm_name='my-vm',
    force=True,
)

# List VMs
list_task = KcliVMListOperator(
    task_id='list_vms',
)
```

## Preflight Checks

Before creating VMs, verify:
1. Sufficient memory: `free -h`
2. Disk space: `df -h /var/lib/libvirt`
3. Libvirt running: `systemctl is-active libvirtd`
4. Network available: `virsh net-list`

## SSH Execution Pattern (ADR-0046)

For DAGs that need to run commands on the host:

```python
bash_command="""
ssh -o StrictHostKeyChecking=no root@localhost \
    "cd /opt/kcli-pipelines && ./deploy.sh"
"""
```

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.