Zenoss as a Service: How to Get There
Download as PPTX, PDF0 likes318 views
This document outlines the steps for migrating to Zenoss as a Service (ZaaS) for both version 4 and version 5 on-premises customers, emphasizing the complimentary migration assessment process. It details requirements, restrictions, and the deployment process while providing a comparison of migration strategies for the two versions. Additionally, it highlights the backup and restore features that facilitate a smoother transition for users moving from version 5.x.
Zenoss as a Service: How to Get There
- 1. Zenoss as a Service: How to Get There Jacob Keith – Staff Deployment Architect Nick Turner – Director, IT Operations
- 2. First steps toward migrating to Zenoss as a Service (ZaaS) • All migrations are eligible for a complimentary migration assessment which consists the following: @Zenoss © 2017 All Rights Reserved CONFIDENTIAL 2 • Migration to Zenoss as a Service is offered for both version 4 and version 5 on-premises customers, and our Sales and Services teams will gladly help you on your way. 1 Connect with Your Sales Rep to Kickstart the Assessment Once you let us know you are interested in learning what it takes to make the switch, your sales representative will help you on your journey. 2 Help us Gather Information about Your Implementation Complete a simple questionnaire and run 3 secure scripts from Zenoss on your system and send the output back to us. 3 Get Zenoss’ Expert Opinion on What It’ll Take to Migrate Our Professional Services team will analyze the results and propose the best course of action, recommended architecture, and number of service hours required to smoothly transition your monitoring to ZaaS. 4 Decide to Move Forward with Your Transition to ZaaS With all of the info at your fingertips, feel confident in your decision to migrate to ZaaS.
- 3. Assessing if ZaaS is right for you… Restrictions • No Access to Control Center • No Access to Command-Line • No Access to DMD • Cannot install ZenPacks • Cannot manage users directly in UI • Remote Collection / Polling frequency @Zenoss © 2016 All Rights Reserved CONFIDENTIAL 3 Alternatives • Reduced Administration • Leveraging the API • Professional Services
- 4. ZaaS Deployment Process @Zenoss © 2017 All Rights Reserved CONFIDENTIAL 4 • Ticket Opened for Ops Team • Customer Name – “name.saas.zenoss.com” • Requested ZenPacks • # of MR, # of collectors, # of pools/locations • Start the scripted process – currently utilizing a mixture of AMIs, AWSCLI, Bash, and Ruby – In the process of migrating to SALT • Less than a business day to deploy • Collector deployment – Wiki • VMware, HyperV, AWS/GovCloud, Azure • 4vCPU, 16GB of RAM, 75GB / 110GB disk • Ports 443, 8055, 1194 • oVPN tunnels from the appliances to Master • Initial users set up, additional users can be done via ticket, API, or LDAP integration
- 5. Your environment is ready. Now what are we migrating? @Zenoss © 2017 All Rights Reserved CONFIDENTIAL 5 • Both version 4.x and 5.x On-Premises installations are eligible for migration to ZaaS 5.x instances. These migration paths will share common overall workflow, but will differ in some of the methods for migrating. • Migration Strategy: 1. A Dedicated environment deployed in AWS by our ZaaS Operations team. 2. Zenoss Professional Services will work with you to deploy collectors across your environment. 3. A change freeze should be implemented for your current Zenoss software deployment. 4. Configurations will be migrated from on-premise install to new ZaaS environment. 5. Parallel run for up to a 2 week period to validate functionality. 6. When ready, Your ZaaS instance becomes your official monitoring system of record and you are able to decommission your on-premises deployment at any time following the cutover.
- 6. Migration process overview (applies to 4.x* and 5.x) @Zenoss © 2017 All Rights Reserved CONFIDENTIAL 6
- 7. Migrating to ZaaS from Zenoss version 5.x? We’ve got your Back(up) @Zenoss © 2017 All Rights Reserved CONFIDENTIAL 7 • Thanks to the backup & restore features built into our Control Center software, customers moving from 5.x on-premises to 5.x ZaaS have the option of simply uploading a single backup tgz file. • Restoring this file allows for the migration of the complete set of Docker Images, ZenPacks, configuration settings, device inventory, event history, and performance data (optional). • If the versions match, after some minor configuration by our ZaaS operations team the environment is ready to go. • For older 5.x versions, a product upgrade will be performed as well prior to being made available.
- 8. Migrating to ZaaS from Zenoss version 4.x On-Premises @Zenoss © 2017 All Rights Reserved CONFIDENTIAL 8 • Migrating from 4.x requires a few extra steps compared to 5.x, and does not cover historical event or performance data. • Device Inventory is migrated via the Zenbatchdump & Zenbatchload utilities – Exporting an editable text file containing configuration elements such as: Device Name, IP Address, Device Class, Groups, Systems, Locations, Collector Association, and the content of cProperties & zProperties • ZaaS Operations team handles the installation of required Zenoss Enterprise & Open- Source ZenPacks • ZenPacks may also be provided containing Monitoring Templates, Thresholds/Graph Definitions, Event Classes/Mappings, Transforms, MIBs, Reports. • Impact Services may be migrated from matching Impact versions through the Export/Import feature
- 9. © 2017 All Rights Reserved CONFIDENTIAL 9 Welcome to ZaaS! @Zenoss
- 10. © 2017 All Rights Reserved CONFIDENTIAL 10 Questions @Zenoss