1. Overview
Thank you for your interest in Koios Automation Platform. Koios Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless technical implementation. IT managers can provide guidelines on how automation is applied to individual teams. Meanwhile, automation developers retain the freedom to write tasks that use existing knowledge, without the operational overhead of conforming to complex tools and frameworks. It is a more secure and stable foundation for deploying end-to-end automation solutions, from hybrid cloud to the edge.
Koios Automation Platform allows users to define, operate, scale, and delegate automation across their organization.
1.1. Real-time Playbook Output and Exploration
Watch playbooks run in real time, seeing each host as they check in. Easily go back and explore the results for specific tasks and hosts in great detail. Search for specific plays or hosts and see just those results, or quickly zero in on errors that need to be corrected.
1.3. Role-Based Access Control and Auditing
Koios Automation Platform allows for the granting of permissions to perform a specific task (such as to view, create, or modify a file) to different teams or explicit users through role-based access control (RBAC).
Keep some projects private, while allowing some users to edit inventory and others to run playbooks against only certain systems–either in check (dry run) or live mode. You can also allow certain users to use credentials without exposing the credentials to them. Regardless of what you do, Koios Automation Platform records the history of operations and who made them–including objects edited and jobs launched.
Assign resource roles to users or teams to grant access to job templates, inventories, projects and credentials. Team members inherit the roles assigned to the team. See Role-Based Access Control for role definitions, assignments and resource scope.
Koios Automation Platform includes an ‘Auditor’ type, who can see all aspects of the systems automation, but has no permission to run or change automation, for those that need a system-level auditor. (This may also be useful for a service account that scrapes automation information from the REST API.) Refer to Role-Based Access Control for more information.
1.4. Cloud & Autoscaling Flexibility
Koios Automation Platform features a powerful provisioning callback feature that allows nodes to request configuration on demand. While optional, this is an ideal solution for a cloud auto-scaling scenario, integrating with provisioning servers like Cobbler, or when dealing with managed systems with unpredictable uptimes. Requiring no management software to be installed on remote nodes, the callback solution can be triggered via a simple call to ‘curl’ or ‘wget’, and is easily embeddable in init scripts, kickstarts, or preseeds. Access is controlled such that only machines in inventory can request configuration.
1.5. The Ideal RESTful API
The Koios Automation Platform REST API is the ideal RESTful API for a systems management application, with all resources fully discoverable, paginated, searchable, and well modeled. A styled API browser allows API exploration from the API root at http://<server name>/api/, showing off every resource and relation. Everything that can be done in the user interface can be done in the API - and more.
1.6. Backup and Restore
Koios Automation Platform is backed up and restored through the Koios operator, which captures the database, the secrets that encrypt it, and the deployment configuration. See Backup and Restore.
1.7. Ansible Galaxy Integration
When it comes to describing your automation, everyone repeats the DRY mantra–“Don’t Repeat Yourself.” Using centralized copies of Ansible roles, such as in Ansible Galaxy, allows you to bring that philosophy to your playbooks. By including an Ansible Galaxy requirements.yml file in your project directory, Koios Automation Platform automatically fetches the roles your playbook needs from Galaxy, GitHub, or your local source control. Refer to Ansible Galaxy Support for more information.
1.8. Inventory Support for OpenStack
An OpenStack inventory source discovers cloud resources for use in automation. See Inventory Sources for supported inventory sources and their configuration.
1.9. Remote Command Execution
Often times, you just need to do a simple task on a few hosts, whether it’s add a single user, update a single security vulnerability, or restart a misbehaving service. Koios Automation Platform includes remote command execution–any task that you can describe as a single Ansible play can be run on a host or group of hosts in your inventory, allowing you to get managing your systems quickly and easily. Plus, it is all backed by an RBAC engine and detailed audit logging, removing any questions regarding who has done what to what machines.
1.10. System Tracking
You can collect facts by using the fact caching feature. Refer to Fact Caching for more detail.
1.11. Integrated Notifications
Koios Automation Platform allows you to easily keep track of the status of your automation. You can configure stackable notifications for job templates, projects, or entire organizations, and configure different notifications for job start, job success, job failure, and job approval (for workflow nodes). The following notification sources are supported:
AWS SNS
Email
Grafana
IRC
Mattermost
PagerDuty
Rocket.Chat
Slack
Twilio
Webhook (post to an arbitrary webhook, for integration into other tools)
Additionally, you can customize notification messages for each of the above notification types.
1.12. Satellite Integration
Dynamic inventory sources for Red Hat Satellite 6 are supported.
1.13. Run-time Job Customization
Bringing the flexibility of the Ansible command line, you can prompt for any of the following:
inventory
credential
job tags
limits
1.14. User Interface
The layout of the user interface is organized with intuitive navigational elements. With information displayed at-a-glance, it is intuitive to find and use the automation you need. Compact and expanded viewing modes show and hide information as needed, and various built-in attributes make it easy to sort.
1.15. Execution Environments
An execution environment is a container image with Ansible and the dependencies needed by a job. Select an image for the job rather than configuring a Python virtual environment on the controller host. See Execution Environments for image selection, building a custom image and execution isolation.
1.16. Authentication
Koios Automation Platform supports LDAP, SAML, token-based authentication. The platform gateway manages login methods and OAuth 2 tokens. See Authentication and access for authentication providers, identity mapping, sessions and API tokens.
1.17. Cluster Management
Run-time management of cluster groups allows for easily configurable scaling.
1.18. Container Platform Support
Koios Automation Platform is available as a containerized pod service for Kubernetes environments that can be scaled up and down easily as needed.
1.19. Workflow Capabilities
Workflows provide these capabilities for provisioning, deployment and orchestration:
Inventory overrides for Workflows. You can override an inventory across a workflow at workflow definition time, or even at launch time. Define your application deployment workflow, and then easily re-use them in multiple environments.
Convergence nodes for Workflows. When modeling complex processes, you sometimes need to wait for multiple steps to finish before proceeding. Workflow steps can wait for any number of prior workflow steps to complete properly before proceeding.
Workflow Nesting. Re-use individual workflows as components of a larger workflow. Examples include combining provisioning and application deployment workflows into a single master workflow.
Workflow Pause and Approval. You can build workflows containing approval nodes that require user intervention. This makes it possible to pause workflows in between playbooks so that a user can give approval (or denial) for continuing on to the next step in the workflow.
1.20. Job Distribution
As automation moves enterprise-wide, the need to automate at scale grows. Koios Automation Platform offers the ability to take a fact gathering or configuration job running across thousands of machines and slice it into individual job slices that can be distributed across your Koios Automation Platform cluster for increased reliability, faster job completion, and better cluster utilization. If you need to change a parameter across 15,000 switches at scale, or gather information across your multi-thousand-node RHEL estate, job slicing distributes the work across eligible execution capacity.
1.21. FIPS validation status
Deployment of Koios Automation Platform in a FIPS-enabled environment has not been validated. This documentation does not claim FIPS certification or compliance for the platform or its execution environment images.
1.22. Limit the number of hosts per organization
Lots of large organizations have instances shared among many organizations, and do not want any one organization using all the hosts. A superuser can set an upper limit on an organization by writing max_hosts through the API, at /api/controller/v2/organizations/N/; there is no field for it in the web interface. Bulk host creation refuses to take an organization past that limit.
1.23. Inventory Plugins
Inventory sources use plugins supplied by Ansible collections in the execution environment. See Inventory Sources for source configuration and Supported Inventory Plugin Templates for plugin configuration examples.
1.24. Secret Management System
With a secret management system, external credentials are stored and supplied for use in Koios Automation Platform so you don’t have to provide them directly.