Provide an interface for dynamically configuring CloudI.

Supported request formats:

• JSON-RPC
• JSON
• Erlang term data
• native Erlang function calls (cloudi_service_api module) within the same Erlang VM

CloudI allows you to call dynamic configuration functions from any CloudI process (assuming it is not blocked by an ACL). The default configuration initializes the CloudI service responsible for dynamic configuration which subscribes to service names based on the functions defined in the cloudi_service_api module:

• "/cloudi/api/rpc.json"
• "/cloudi/api/rpc/?.json" (see below)
  • "/cloudi/api/rpc/acl_add.json"
  • "/cloudi/api/rpc/acl_remove.json"
  • "/cloudi/api/rpc/acl.json"
  • "/cloudi/api/rpc/service_subscriptions.json"
  • "/cloudi/api/rpc/services_add.json"
  • "/cloudi/api/rpc/services_remove.json"
  • "/cloudi/api/rpc/services_restart.json"
  • "/cloudi/api/rpc/services_suspend.json"
  • "/cloudi/api/rpc/services_resume.json"
  • "/cloudi/api/rpc/services_search.json"
  • "/cloudi/api/rpc/services_status.json"
  • "/cloudi/api/rpc/services_update.json"
  • "/cloudi/api/rpc/services.json"
  • "/cloudi/api/rpc/nodes_set.json"
  • "/cloudi/api/rpc/nodes_get.json"
  • "/cloudi/api/rpc/nodes_add.json"
  • "/cloudi/api/rpc/nodes_remove.json"
  • "/cloudi/api/rpc/nodes_alive.json"
  • "/cloudi/api/rpc/nodes_dead.json"
  • "/cloudi/api/rpc/nodes_status.json"
  • "/cloudi/api/rpc/nodes.json"
  • "/cloudi/api/rpc/logging_set.json"
  • "/cloudi/api/rpc/logging_file_set.json"
  • "/cloudi/api/rpc/logging_level_set.json"
  • "/cloudi/api/rpc/logging_stdout_set.json"
  • "/cloudi/api/rpc/logging_syslog_set.json"
  • "/cloudi/api/rpc/logging_formatters_set"
  • "/cloudi/api/rpc/logging_redirect_set.json"
  • "/cloudi/api/rpc/logging_status.json"
  • "/cloudi/api/rpc/logging_status_reset.json"
  • "/cloudi/api/rpc/logging.json"
  • "/cloudi/api/rpc/code_path_add.json"
  • "/cloudi/api/rpc/code_path_remove.json"
  • "/cloudi/api/rpc/code_path.json"
  • "/cloudi/api/rpc/code_status.json"
• "/cloudi/api/rpc/?.erl" (same as above with Erlang term data)

The default configuration expects HTTP requests to port 6464 with the proper service path and format (listed above) to call the CloudI service interface.

The CloudI dashboard provides a web UI with all the CloudI Service API functionality available to the user visually. The installed configuration provides the web UI on port 6464 (i.e., http://localhost:6464/cloudi/).

CloudI Service API integration example:

• Python (JSON-RPC over HTTP)

CloudI Service API usage examples:

• Python (Turn logging off)
• Python (Turn logging on)
• Python (Add to the Erlang code search path)
• Python (Add/Remove nodes, Add/Remove ACL entries, Start/Stop services)

Please see the CloudI Service API documentation for more details.