New levels of flexibility and control in Orca v3.4
Zero Downtime in application release automation
Better issue visibility
Shorten time to detect and correct drift
User Scripts Library provides more flexibility
While we at Orca pride ourselves in providing out of the box (scripting-free) integrations to important middleware, databases, operating systems, ITSMs and more, we also know that our users often rely on their own custom scripts library as well.
So we are happy to announce that users can now add their own scripts directly to the console for Orca to manage. These scripts can be in any interpreted language. This helps users to:
- Customize deployment workflows
Users have several choices: 1) reuse saved workflows 2) build on their existing workflows 3) they can add their scripts as part of a workflow. And during deployment Orca ships the script out and executes it.
- GET configuration data
Another powerful way to manage your environment. Use your own command or script to gather configuration data from disparate systems.
Issues tab gives better issue visibility, faster time to detect/ correct
The issues tab in the ecosystem section of the console gives a quick glance at all the issues on a node, whether it’s compliance violations, drift, or server difference issues. Unless users prefer to, there is no need to drill down into the config data to see the problem. Just glance at the issues tab!
Issues Tab: Shows what’s wrong right away
Issues Tab: No Guesswork
Pool Controllers with F5 interface for Zero Downtime in application release
With Orca users can define pools of servers. During deployment, Orca will deploy to each pool in a ‘rolling’ fashion for zero downtime. Here’s how it works. During deployment, Orca will use its out of the box interface to talk to F5 and actually remove the servers in the pool from the load balancer, deploy to them, put them back in the load balancer, and then move on to the next pool.
Using Orca, you configure this behavior once for any application environment, and all deployments and configuration changes will adhere to it. Orca does this out of the box, saving time and effort doing customization work.
Compliance rules for even tighter control
Orca has added new functionality for even tighter control and easier adherence to compliance rules.
- “Child path must exist”. A good example is making sure that a user exists. If that user doesn’t exist, Orca flags it as a compliance violation.
- For our existing compliance rules, you now have the option to ignore white space and case.
- For the “validate value” compliance rule, you can now perform a more comprehensive validation using a regular expression.