jan/agentbox
1
0
Fork 0
Code Issues 10 Pull requests Projects Releases Packages Wiki Activity Actions

Spike: headless Autodesk Maya (mayapy) in a project template #8

New issue
Open
opened 2026-10-01 09:20:28 +00:00 by jan · 0 comments
jan commented 2026-10-01 09:20:28 +00:00
Owner
Copy link

Motivation

The work project is a Maya pipeline. Without Maya in the VM the agent can only
test pure-Python logic; everything that touches scenes has to be checked by
hand on the host. Running mayapy headless in the VM would close that gap.

Running mayapy on the host on the agent's behalf is not an option: that
executes agent-written code outside the sandbox.

Questions to answer

  • Licensing. How does Maya get a license inside a default-deny VM?
    Network license server (one host:port rule), or named-user login (a
    token inside the VM that the agent can read)? Are VM installs covered by
    the license terms? Ask whoever manages the licenses.
  • Distro. Autodesk supports RHEL/Rocky. Does mayapy run on the
    template's base image with extra libraries, or does the project template
    need a different base?
  • Version. Match the host's Maya version and its bundled Python
    exactly.
  • Size. The install is several GB: install from a host path at build
    time (#5 (Project templates on top of the agent template)), not from the network.
  • Plugins. Which plugins the project loads exist for Linux; renderer
    plugins can be absent (nodes load as unknown).
  • Project code. Vendored Windows-only binaries (e.g. a numpy wheel,
    PySide) and .bat launchers need Linux counterparts in the VM.

Done when

A written answer to each question, and either a working
mayapy -c "import maya.standalone; maya.standalone.initialize()" in a
project-template sandbox, or a clear reason why not.

## Motivation The work project is a Maya pipeline. Without Maya in the VM the agent can only test pure-Python logic; everything that touches scenes has to be checked by hand on the host. Running `mayapy` headless in the VM would close that gap. Running `mayapy` on the **host** on the agent's behalf is not an option: that executes agent-written code outside the sandbox. ## Questions to answer - [ ] **Licensing.** How does Maya get a license inside a default-deny VM? Network license server (one `host:port` rule), or named-user login (a token inside the VM that the agent can read)? Are VM installs covered by the license terms? Ask whoever manages the licenses. - [ ] **Distro.** Autodesk supports RHEL/Rocky. Does `mayapy` run on the template's base image with extra libraries, or does the project template need a different base? - [ ] **Version.** Match the host's Maya version and its bundled Python exactly. - [ ] **Size.** The install is several GB: install from a host path at build time (#5 (Project templates on top of the agent template)), not from the network. - [ ] **Plugins.** Which plugins the project loads exist for Linux; renderer plugins can be absent (nodes load as unknown). - [ ] **Project code.** Vendored Windows-only binaries (e.g. a numpy wheel, PySide) and `.bat` launchers need Linux counterparts in the VM. ## Done when A written answer to each question, and either a working `mayapy -c "import maya.standalone; maya.standalone.initialize()"` in a project-template sandbox, or a clear reason why not.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.2.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jan/agentbox#8
No description provided.