Managing a Server
Server management starts from the sever dashboard.
To get there:
- Select the Infrastructure tab from the main, left-hand navigation.
- Click into Servers from the infrastructure sub-menu.
- Select a server from the first column.
There are three menu items available from the horizontal navigation:
Server Configure
The server configuration page allows users to create file systems directly on the host that can be mounted into containers.
The reconfigure server button will not restart the server or cause interference with running containers.
Allow SFTP
By default SFTP connections will not be available on a newly deployed server.
To enable SFTP connections on the server select the checkbox to enable, and click the Reconfigure Server button.
Custom Base Volume Size
A base volume is how much space should be set aside for images on this server. If a user wishes to increase this amount they can using this form.
Increase Only
The custom base volume setting can only be increased, as a decrease could result in the corruption of the images stored in that volume.
Shared Mounts
The shared mounts option is meant for users that wish to mount a file system that is remote to the host it will be mounted on.
The first step in creating a shared mount is to enter an identifier and press the + button.
- Type - The filesystem type.
- Options - Filesystem mount options.
- Source - Where is the source of the data?
example for an NFS mount through EFS on AWS.
- type -
nfs4 - options -
nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,addr=ip address - source -
:/
Shared Directories
The shared directories option is a much simpler form. Shared directories only require an identifier and each entry represents a directory on the host that can be consumed by any container.
Server Console
Users that want direct access to sever level logging can use the server console page to get view the latest 128KB of logs for any given server.
Settings
Manage the settings of individual servers. Server settings control the type of instances that can be deployed to each server as well as resource allocation limits.
Basics
In the basics section of server settings users can find more information about the server Id and hostname.
Update Server
Tags
Server tags are a way to give instances more information for deployment. Cycle will automatically generate a few relevant tags.
Click into the Tags field and start typing the tag to add. When ready, press enter. To remove a tag, click the [x] next to it.
Allow Pool
If this checkbox is selected, this server will accept instances that have no tags specified.
Allow Services
When an environment is created, the service containers that come with that environment are automatically created and placed on servers. If this box is selected, the server will accept service containers. If it is unchecked, no service containers will be deployed to this server.
Advanced Updates
Allow Overcommit
To allow for the server to over-commit its CPU resources, check the box and enter a multiple. The multiple is how many times over-committed the CPU can be.
Controls
Controls is split into two sections:
- General - where the compute service can be restarted.
- Advanced - where the server or compute spawner can be restarted.
Restart Compute
Restarting compute will simply restart the compute process running on the node. This restart will not interact with networks or containers running on the node. Minimal to zero downtime impact.
Restart Compute Spawner
Restarting compute spawner will all containers on the node to restart and will rebuild all networks from 0 to 100%. This restart will cause downtime for all container instances on the node.
Restart Server
Restarting the server will issue a restart for the given server to the service provider. All containers on the server will be offline for a few minutes, or until the server comes back online.
Evacuate Server
Users that wish to move all workloads off of a server and onto another can use the evacuate server form to select a server target to migrate the server instances to.
Minimum 2 Servers
This functionality will not work if the cluster has only one server in it.
Deleting a Server
Use the delete from to delete the server.
The "Force Delete Server" checkbox is to be used only when a normal delete action cannot be done and the user needs to remove the server forcibly from Cycle.