Yes, you heard it right, in 2 Days!
OpsMx did it for many enterprises and can do it for you as well. But, the first question is why move at all in the first place?
Open Source Spinnaker and Armory Spinnaker are Continuous Delivery software solutions designed for multi-cloud deployments. However the need to move from Open Source Spinnaker and Armory Spinnaker is primarily driven by the following:
Need for Better Security and Compliance
OpsMx Spinnaker is distributed with UBI8 images that are better suited for use in RHEL containerized environments, unlike simple Ubuntu images. That makes OpsMx enterprise-ready, especially for large enterprises.
OpsMx Spinnaker images are CVE fixed and are ahead of the security vulnerability fixes curve as opposed to any other Spinnaker images.
OpsMx Spinnaker images are FedRamp compliant as well.
Need for Better Scalability
OpsMx Spinnaker is fine-tuned to offer optimal performance for large-scale enterprises. We are currently working with enterprises with distributed engineering teams. They are about centrally managing and scaling their operations while having security and compliance controls in place. OpsMx Spinnaker is perfectly suited for them to increase the volume and velocity of release/deployments without breaking anything.
Need for More Flexibility
OpsMx Spinnaker is designed to handle complex scenarios for both workflow and deployments and is a good fit for enterprises with ever-changing operations/business scenarios. Our out-of-the-box configuration approach driven by an intuitive UI makes it extremely easy for the users to adapt to new situations.
Need for Speed and Audit Controls
Security and Compliance usually breaks with speed. OpsMx Spinnaker, with its AI/ML engine and data-driven approach, ensures those checks are an integral part of your pipelines instead of an afterthought.
Need for Better, No-excuses Enterprise Support
OpsMx is a leading contributor to Spinnaker and Argo, which shows our commitment to the open-source community. We have the experience of managing large-scale enterprise transformation projects around DevOps and DevSecOps and have the requisite expertise to take any enterprise from one level to the next level on the maturity curve. Our support keeps our customers coming back to us.
Easy Steps to Move from Armory Spinnaker to OpsMx Spinnaker
There are three key elements that enable a successful migration of the entire Continuous Delivery infrastructure and process from Armory Spinnaker to OpsMx Spinnaker. By the way, this is not just a theory but has been practically achieved with several customers in the last few months.
These three elements complete a successful migration from Armory Spinnaker to OpsMx Spinnaker:
- Data Migration
- Integration, Custom Stages and Policy Configuration
- User Migration
Let me explain these in detail.
Data Migration
This involves migration of following:
- Metadata migration
- Pipeline execution data migration
Both metadata and pipeline execution data are natively stored in a Redis data store.
The first step is to make this database point to OpsMx Spinnaker. Ideally, we recommend splitting the DB into two components: the core metadata and the cloud driver data for enhanced performance for large enterprises.
This entire data migration takes about 20 minutes, including the testing.
Integration Migration and Custom Stages Migration (including approvals)
Using the OpsMx integration UI, you need to configure the integration points. This ensures compatibility. The integration points may include and are not restricted to your core or image repository, governance, Continuous Integration (CI), build, observability, scanning, secrets manager, and target destinations. These integrations and their configuration is all supported via an intuitive UI.
Similarly, the policy and other custom stages must be reconfigured to ensure compatibility. We did this exercise with one of the world’s largest financial services companies and did this in about a few hours.
Once done, you’ll have the historical data showing up on the OpsMx Spinnaker dashboard. The new execution will show up once OpsMx Spinnaker and your pipelines are ready for execution.
User and Access Control Migration
OpsMx Spinnaker enables role-based access control (RBAC) by allowing you to seamlessly integrate (out of the box) to your existing active directory. It further allows you to enforce guardrails to secure your pipelines and the process. You can reuse your existing single sign-on mechanism.
This may take a few hours in case you want to up the level of existing security.
You need to test by having a few users login and access the dashboard and pipelines.
You are now ready to execute your first production-ready pipeline. With OpsMx Spinnaker, you get several added advantages that you may have been missing in Armory Spinnaker.
Our existing customers who have adopted OpsMx Spinnaker as their enterprise strategy are leveraging AI/ML-based data-driven automation for approvals, verifications, security controls, compliance automation and release or deployment firewall. There is a significant ROI associated with an insignificant drift in the cost.
Contact us if you would like to talk to a Top Spinnaker Expert or would like to see a working demo.
0 Comments