In these examples, ``wordpress`` and ``kvm`` are aliases for the full URL, and are defined in :file:`slapos-client.cfg`.
..
XXX Change in slaplib: allow to fetch instance params without changing anything. i.e we should do "slapos request myalreadyrequestedinstance" to fetch connection parameters without erasing previously defined instance parameters.
XXX Change in slaplib: allow to fetch instance params without changing anything.
i.e we should do "slapos request myalreadyrequestedinstance" to fetch connection parameters
without erasing previously defined instance parameters.
..
...
...
@@ -79,7 +89,8 @@ supply
.. program-output:: python slapos help supply
Ask installation of a software on a specific node or group of nodes. Nodes will then be ready to accept instances of specified software.
Ask installation of a software on a specific node or group of nodes.
Nodes will then be ready to accept instances of specified software.
Examples
...
...
@@ -87,6 +98,7 @@ Examples
$ slapos supply wordpress COMP-12345
In this example, ``wordpress`` is an alias for the full URL, and is defined in :file:`slapos-client.cfg`.
remove
~~~~~~
...
...
@@ -104,6 +116,7 @@ Examples
$ slapos supply wordpress COMP-12345
In this example, ``wordpress`` is an alias for the full URL, and is defined in :file:`slapos-client.cfg`.
Like "slapos suppply", but on-demand. Software will be (re)installed only when at least one instance of this software is requested. When no instance of this software is deployed on the node, it will be uninstalled.
Like "slapos suppply", but on-demand. Software will be (re)installed only when at least one instance
of this software is requested. When no instance of this software is deployed on the node, it will be uninstalled.
console
...
...
@@ -161,13 +175,16 @@ node register
If login is not provided, asks for user's SlapOS Master account then password.
Node will register itself, if not already done, to the SlapOS Master defined in configuration file, and will generate SlapOS configuration file.
Node will register itself, if not already done, to the SlapOS Master defined in
configuration file, and will generate SlapOS configuration file.
..
XXX-Cedric should be like this: If desired node name is already taken, will raise an error.
XXX-Cedric: --master-url-web url will disappear in REST API. Currently, "register" uses SlapOS master web URL to register computer, so it needs the web URL (like http://www.slapos.org)
XXX-Cedric: --master-url-web url will disappear in REST API. Currently, "register" uses
SlapOS master web URL to register computer, so it needs the web URL (like http://www.slapos.org)
If Node is already registered (slapos.cfg and certificate already present), issues a warning, backups original configuration and creates new one.
If Node is already registered (:file:`slapos.cfg` and certificate already present), issues a warning,
backups the original configuration and creates a new one.
..
XXX-Cedric should check for IPv6 in selected interface
...
...
@@ -184,18 +201,19 @@ Examples
$ slapos node register mycomputer
* Register computer named "mycomputer" to SlapOS Master using br0 as primary interface, tap0 as IPv6 interface and different local ipv4 subnet::
* Register computer named "mycomputer" to SlapOS Master using br0 as primary interface,
tap0 as IPv6 interface and different local ipv4 subnet::
* Register computer named "mycomputer" to another SlapOS master accessible via https://www.myownslaposmaster.com, and SLAP webservice accessible via https://slap.myownslaposmaster.com (Note that this address should be the "slap" webservice URL, not web URL)::
* Register computer named "mycomputer" to another SlapOS master accessible via https://www.myownslaposmaster.com,
and SLAP webservice accessible via https://slap.myownslaposmaster.com (note that this address should be the