<div> </div> <div> <b>Day & Date :</b> Friday, 27<sup>th</sup> May 2016 </div> <div> <b>Time :</b> 2:00 PM - 3:00 PM (SGT) </div> <div> <b>Event :</b> vROps Webinar 2016 </div> <div> <b>Topic :</b> Part 5 : Design & Deployment Considerations </div> <div> <b>Speakers :</b> <b><a href="https://twitter.com/simoneady">Simon Eady</a> / <a href="https://twitter.com/Sunny_Dua">Sunny Dua</a></b> </div> <div> </div> <div> <b>WebEx Link</b> <b>:</b> <b><a href="https://vmware.webex.com/vmware/j.php?MTID=mc001f97ebb5214ce2ecd86eb41d8e1a1">Join WebEx meeting </a></b> </div> <p> <b>NOTE</b> - Don't forget to mark your calendars by saving the calendar invite!! Feel free to forward the invite to anyone who might be interested. It's open to all!! </p>
#VROPS WEBINAR 2016 – ANNOUNCING PART 5 : DESIGN & DEPLOYMENT CONSIDERATIONS
Time to announce the next part of the year long webinar series on vRealize Operations Manager. This time around, Sunny and I thought about discussing Architecture of vROps. To some, it might sound strange as for smaller deployments you might not have to worry about Sizing and Architecture much since it is pretty simple to install and configure a small or a medium node for a small shop. However as your monitoring needs grow and you start adding solutions for monitoring data sources beyond vSphere, you would need to think about scaling up or scaling out. As your monitoring environment weaves into your incident ticketing system, you would start to see the need to HA of vROps and as you have a DR strategy for your workloads, you will start thinking about DR for your operations tools as well.