Demo presets provide pre-configured data sets for demonstrations, testing, and development. Each preset contains users, organizations, projects, offerings, resources, and usage data.
| Preset | Description |
|---|---|
minimal_quickstart |
Basic setup for quick demos and testing |
government_cloud |
GDPR-compliant cloud services for public sector |
research_institution |
HPC and research computing environment |
hpc_ai_platform |
GPU clusters and AI/ML workloads |
waldur demo_presets list
waldur demo_presets list --quiet # Names onlywaldur demo_presets info minimal_quickstart# Load with confirmation prompt
waldur demo_presets load minimal_quickstart
# Skip confirmation
waldur demo_presets load minimal_quickstart --yes
# Preview without applying changes
waldur demo_presets load minimal_quickstart --dry-run
# Keep existing data (no cleanup)
waldur demo_presets load minimal_quickstart --no-cleanup
# Skip user import
waldur demo_presets load minimal_quickstart --skip-usersAfter loading, the command displays user credentials:
============================================================
Demo User Credentials
============================================================
staff: demo [staff]
support: demo [support]
owner: demo
manager: demo
member: demo
============================================================
waldur demo_presets export my_preset --title "My Custom Setup"GET /api/marketplace-demo-presets/list/
Authorization: Token <staff_token>GET /api/marketplace-demo-presets/info/{name}/
Authorization: Token <staff_token>POST /api/marketplace-demo-presets/load/{name}/
Authorization: Token <staff_token>
Content-Type: application/json
{
"dry_run": false,
"cleanup_first": true,
"skip_users": false,
"skip_roles": false
}Response includes user credentials:
{
"success": true,
"message": "Preset 'minimal_quickstart' loaded successfully",
"output": "...",
"users": [
{"username": "staff", "password": "demo", "is_staff": true, "is_support": false},
{"username": "owner", "password": "demo", "is_staff": false, "is_support": false}
]
}Each preset JSON file includes:
_metadata- Title, description, version, scenariosusers- User accounts with passwordscustomers- Organizationsprojects- Projects within organizationsofferings- Service offerings with componentsplans- Pricing plansresources- Provisioned resourcescomponent_usages- Usage data per billing periodcomponent_user_usages- Per-user usage breakdownuser_roles- Role assignmentsconstance_settings- Site configuration
- Export current state or copy an existing preset
- Place JSON file in
src/waldur_mastermind/marketplace/demo_presets/presets/ - Add
_metadatasection with title, description, version - Ensure all UUIDs are unique 32-character hex strings
UUIDs must be exactly 32 hexadecimal characters (0-9, a-f):
"uuid": "00000000000000000000000000000001"Include plaintext passwords in the users array:
{
"username": "demo_user",
"password": "demo",
"email": "demo@example.com"
}Presets are stored in:
src/waldur_mastermind/marketplace/demo_presets/presets/