openflighthpc/flight-cloud-client

flight-cloud-client's Issues

Update the `API` library to match the new end points

Make the appropriate changes to match:
openflighthpc/flight-cloud#243
openflighthpc/flight-cloud#249

This might be useful for a reference on Faraday:
https://github.com/alces-software/flight_cache/blob/9ed135a08a170acf744a26d382e731bcce234901/lib/flight_cache/client.rb#L67

Add the listing and modify commands

The following commands need to be added to the CLI:

cloud list  # => Return a new line separated list of nodes (+ domain)
cloud list --group # => filter the above list by group
cloud list-groups # => Return all the available groups (space separated)

It also needs a modify command that implements the following CLI:

> flight modify
  NAME:

    modify
	
  SYNOPSIS:
  
    modify NODE_IDENTIFIER [OPTIONS]
	
  DESCRIPTION:

    Tool for modifying basic node configuration.
	
	If no OPTIONS are provided then an interactive prompt will appear for each possible option.
	
  OPTIONS: 
  
   	-g, --group
        Switch NODE_IDENTIFIER to be GROUP_IDENTIFIER, this will modify all nodes in the group at once
	
	--instance-type TYPE
		Modify the instance type of the node

> flight modify node01 --instance-type=c5.large
Changing instance type of node01 to c5.large

Output power commands in a pretty format

ATM the CLI dumps the raw JSON response to standard out. Instead it should be more like:

> flight power node01 off
node01: Powering off

> flight power -g nodes status
node01: off
node02: on
node03: on

There should be no translation of the state returned from the server. Therefore if the server returns "pending" then it should print node01: pending

Support multiple clusters

Between here and the cloud server, allow for multiple clusters to be managed.

Perhaps something like a cluster flag that's configured for the client, sent to server, and validated on server end?

Security-wise, this could be vulnerable but see #11 for initial thoughts on that.

Improve security

Some form of authentication/key that the client needs to be able to successfully send requests to the server. Perhaps the key is on a per-cluster basis on the server.