Usage
Aliases
fleets
Commands
Inherited flags
Examples
Subcommand reference
idyl fleet add-node
Add a node to a fleet.
Fleet membership is recorded on the node, so this sets the node’s fleet. A
node belongs to one fleet at a time, so adding a node that already belongs to
another fleet moves it.
Usage
Flags
Examples
idyl fleet assign
Assign or reassign a fleet to one subnet.
Nodes in a fleet contribute capacity to the fleet’s subnet. A fleet belongs to
zero or one subnet, so assigning again replaces the previous subnet.
Usage
Flags
Examples
idyl fleet create
Create a fleet in the current account.
The name is the fleet’s stable handle within the account and is fixed for the
life of the fleet. The 12-digit Fleet ID the platform assigns is what other
commands address the fleet by.
Usage
Flags
Examples
idyl fleet events
Show a fleet’s observed history, oldest first.
A fleet’s status says what is true now. Its events say what happened: every
launch attempted, what the cloud said when one was refused, machines replaced
because they never joined, strays terminated, teardown blocked.
Identical consecutive observations are collapsed into one row that counts up,
so a launch retried every few minutes for a day is one line whose count and
last-seen move rather than hundreds of lines.
Use —watch to keep reading. Following resumes from the position each page
ended at, so nothing is read twice and nothing is missed.
Usage
Flags
Examples
idyl fleet get
Get fleet details or list fleets
Usage
Aliases
listls
Flags
idyl fleet list-nodes
List the nodes in a fleet.
Fleet membership is recorded on each node, so this reads the account’s nodes
and selects the ones that name this fleet. The listing is read to its end
before any result is shown, and the summary line reports how many nodes were
examined.
The listing is paged by position, so a node created or removed while the scan
is reading moves rows across page boundaries. An attempt that ends holding
fewer nodes than the account’s own count, or that reaches a page carrying only
nodes it has already read, starts the scan over from the beginning. A
shortfall one attempt establishes stays in force for the rest of the command,
and a later attempt clears it by reading the nodes that were missing rather
than by reporting a smaller count. A listing that comes out that way
on all 3 attempts fails the command, and the failure names how many nodes the
last attempt read alongside the count the account gave for itself, or says the
account gave none.
The account’s count is a check on the scan rather than a guarantee of it.
Removing a node from a position the scan has already passed pulls an unread
node back into that position, and the two counts still agree, so a node can be
absent from a result that passed the check. Reading the listing again opens
that window once more rather than closing it. Running the command again reads
the listing fresh.
NODE CREATED is the date the node itself came into existence. Fleet membership
is a field on the node rather than a record of its own, so the node’s creation
date is the date this listing carries.
Usage
Aliases
ls-nodesget-nodes