> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Management

> Create administrator accounts and scale compute and API workers for your deployed cloud

Management handles post-deployment administration tasks. After your cloud is deployed, you need administrator accounts for accessing the Dashboard and APIs, and you may need to scale compute or API workers to match demand. The Management tool provides two tabs for these operations.

<Note>
  **Prerequisites**

  * Cloud deployment completed via [Operations](/deployment/operations) (Deploy + Post-Deploy)
  * Access to XDeploy on the deployment node
</Note>

***

## Management Tabs

<Tabs>
  <Tab title="User Management" icon="users">
    Create administrator accounts for accessing the Xloud Dashboard and APIs. Each user account receives admin and heat\_stack\_owner roles, granting full control over the cloud environment.

    ***

    ### Create Administrator Account

    | Field                | Required | Description                                                                                                               |
    | -------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------- |
    | **Username**         | Yes      | Unique login identifier. Must be 3-32 characters, alphanumeric only. The username `admin` is reserved and cannot be used. |
    | **Password**         | Yes      | Account password. Minimum 12 characters with at least one uppercase letter, one number, and one special character.        |
    | **Confirm Password** | Yes      | Re-enter the password to confirm accuracy                                                                                 |
    | **Email**            | No       | Optional email address associated with the account                                                                        |

    Click **Create Administrator Account** to provision the user.

    <Warning>
      Usernames cannot be changed after creation. Choose usernames carefully following your organization's naming conventions. The reserved username `admin` cannot be used --- it is reserved for the built-in system administrator account created during deployment.
    </Warning>

    <Info>
      Every account created through this interface receives the **admin** and **heat\_stack\_owner** roles automatically. These roles grant full access to all projects, users, and orchestration capabilities. For restricted user accounts with limited roles, use the [Xloud Dashboard](/services/dashboard/user-guide) identity management panel after deployment.
    </Info>
  </Tab>

  <Tab title="Scaling" icon="trending-up">
    Scale compute workers and API workers to match your cluster's workload demands. Scaling adjusts the number of service processes running across your deployment.

    ***

    ### Compute Workers

    Compute workers handle virtual machine lifecycle operations --- launching, stopping, migrating, and monitoring instances. Increase compute workers to handle higher instance concurrency.

    | Setting                  | Description                                         |
    | ------------------------ | --------------------------------------------------- |
    | **Compute Worker Count** | Number of compute worker processes per compute node |

    ***

    ### API Workers

    API workers handle incoming requests to the cloud APIs. Increase API workers to handle higher request throughput from the Dashboard, CLI, and automation tools.

    | Setting              | Description                                        |
    | -------------------- | -------------------------------------------------- |
    | **API Worker Count** | Number of API worker processes per controller node |

    <Tip>
      A general guideline is one API worker per CPU core on the controller node. Over-provisioning API workers beyond available CPU cores can increase latency due to context switching overhead.
    </Tip>

    <Warning>
      Changing worker counts requires a service restart. Plan scaling operations during maintenance windows to avoid brief API interruptions.
    </Warning>
  </Tab>
</Tabs>

***

## Validation

After creating accounts and adjusting scaling settings, verify the configuration is correct.

<Steps titleSize="h3">
  <Step title="Test User Login" icon="circle-check">
    Log in to the **Xloud Dashboard** (`https://connect.<your-domain>`) using a newly created administrator account. Verify that the user has full administrative access and can view all projects.
  </Step>

  <Step title="Verify Account Roles" icon="shield-check">
    Confirm that the created account has the expected roles:

    ```bash title="Check role assignments" theme={null}
    source openrc.sh
    openstack role assignment list --user <username> --names
    ```

    The output should show both **admin** and **heat\_stack\_owner** roles assigned to the user.
  </Step>

  <Step title="Verify Worker Scaling" icon="activity">
    After adjusting worker counts, confirm the new worker processes are running:

    ```bash title="Check API worker count" theme={null}
    docker exec nova_api ps aux | grep nova-api | wc -l
    ```

    The count should match the configured API worker setting.

    <Check>Administrator accounts created and worker scaling verified.</Check>
  </Step>
</Steps>

***

## Best Practices

<CardGroup cols={2}>
  <Card title="Individual Accounts" icon="users" color="#197560">
    Create separate administrator accounts for each person who needs access. Never share credentials. Individual accounts provide accountability through audit logs and allow targeted access revocation.
  </Card>

  <Card title="Strong Passwords" icon="lock" color="#197560">
    Use passwords that exceed the minimum requirements. Combine uppercase, lowercase, numbers, and special characters. Consider using a password manager to generate and store credentials securely.
  </Card>

  <Card title="Scale Gradually" icon="trending-up" color="#197560">
    When scaling workers, increase in small increments and monitor resource utilization after each change. Doubling worker counts without verifying CPU and memory headroom can degrade performance.
  </Card>

  <Card title="Maintenance Windows" icon="clock" color="#197560">
    Schedule worker scaling during planned maintenance windows. Worker count changes require service restarts, which cause brief interruptions to API availability.
  </Card>
</CardGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="User cannot log in to the Dashboard" icon="alert-triangle">
    **Cause**: Incorrect credentials, disabled account, or the user is not assigned to any project.

    **Resolution**: Verify the username and password in the Management tool. Ensure the user account is enabled and assigned to at least one project with a valid role. Reset the password if necessary.
  </Accordion>

  <Accordion title="Account creation fails with username validation error" icon="alert-triangle">
    **Cause**: The username does not meet the requirements (3-32 characters, alphanumeric only) or uses the reserved name `admin`.

    **Resolution**: Choose a different username that meets the character requirements and is not reserved.
  </Accordion>

  <Accordion title="API becomes unresponsive after scaling workers" icon="alert-triangle">
    **Cause**: Worker count exceeds available CPU cores, causing excessive context switching and memory pressure.

    **Resolution**: Reduce the worker count to match the number of available CPU cores. Monitor memory usage to ensure the node has sufficient RAM for all worker processes.
  </Accordion>
</AccordionGroup>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Cloud Fleet" icon="globe" href="/deployment/cloud-fleet" color="#197560">
    View the interactive topology map of your deployed infrastructure and service status
  </Card>

  <Card title="Dashboard User Guide" icon="monitor" href="/services/dashboard/user-guide" color="#197560">
    Learn to manage instances, volumes, networks, and images through the Xloud Dashboard
  </Card>
</CardGroup>