<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>jcossota_san Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>jcossota_san Tracker</description>
    <pubDate>Wed, 15 Nov 2023 08:06:37 GMT</pubDate>
    <dc:date>2023-11-15T08:06:37Z</dc:date>
    <item>
      <title>Re: Multi-site architecture for vRA 8.1?</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/Multi-site-architecture-for-vRA-8-1/m-p/2303920#M18458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks everyone for the input - will chew on this for a bit and figure out best course of action until a best practice is published officially for the intertwining products.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Aug 2020 15:05:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/Multi-site-architecture-for-vRA-8-1/m-p/2303920#M18458</guid>
      <dc:creator>jcossota_san</dc:creator>
      <dc:date>2020-08-31T15:05:29Z</dc:date>
    </item>
    <item>
      <title>Multi-site architecture for vRA 8.1?</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/Multi-site-architecture-for-vRA-8-1/m-p/2303916#M18454</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Author : &lt;A href="https://communities.vmware.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;URL : &lt;A href="http:////docs.vmware.com/en/vRealize-Automation/8.1/reference-architecture/GUID-B6422967-D0EF-47C1-8D74-D1C1D71FC98C.html"&gt;http:////docs.vmware.com/en/vRealize-Automation/8.1/reference-architecture/GUID-B6422967-D0EF-47C1-8D74-D1C1D71FC98C.html&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Topic Name : Deployment and Configuration Recommendations&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Publication Name : vRealize Automation 8.1 Reference Architecture Guide&lt;/P&gt;&lt;P&gt;Product/Version : vRealize Automation/8.1&lt;/P&gt;&lt;P&gt;Question :&lt;/P&gt;&lt;P&gt;Looking at the documentation I do not see any reference for multi-site deployment architecture best practices.&amp;nbsp; Is it feasible to have a large deployment facilitate a linked site in another geographical region?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2020 18:32:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/Multi-site-architecture-for-vRA-8-1/m-p/2303916#M18454</guid>
      <dc:creator>jcossota_san</dc:creator>
      <dc:date>2020-08-05T18:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Visio Diagrams for VMware Validated Design for SDDC 4.3</title>
      <link>https://communities.vmware.com/t5/Documents/Visio-Diagrams-for-VMware-Validated-Design-for-SDDC-4-3/m-p/2784267#M24</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just wanted to extend my gratitude for you publishing this - comes just in time when I have to crank out some internal documentation supporting our VVD deployment!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Aug 2018 03:09:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Documents/Visio-Diagrams-for-VMware-Validated-Design-for-SDDC-4-3/m-p/2784267#M24</guid>
      <dc:creator>jcossota_san</dc:creator>
      <dc:date>2018-08-30T03:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: New Contest: Share Your vROps 6.6 Upgrade Story</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/New-Contest-Share-Your-vROps-6-6-Upgrade-Story/m-p/1396399#M8013</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Being fairly new to the VMware space (approx. 3 years or so), I cut my teeth on an inherited 5.x deployment in our multi-site 1000+ VM environment.&amp;nbsp; Being responsible for overall health, forensics, and capacity management for our entire virtual stack – a deep dive was imperative. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We all know that vRealize Operations is a beast – not just the learning curve required to understand what it presents, or how to apply metrics and data to business decisions, but the tall order of its purpose: ingest asonishing amounts of data across numerous layers and transform them into consumable entities for both ends of the complexity spectrum, from subject matter experts to senior leadership seeking a simple 35,000 ft. view.&amp;nbsp; Blogs like &lt;A href="https://blogs.vmware.com/management"&gt;this one&lt;/A&gt;, &lt;A href="http://frankdenneman.nl/"&gt;frankdenneman&lt;/A&gt;, &lt;A href="http://www.virtuallyghetto.com/"&gt;virtuallyghetto&lt;/A&gt;, and &lt;A href="http://virtual-red-dot.info/"&gt;virtual-red-dot&lt;/A&gt; have proven priceless in an attempt to peel the onion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not going to lie, the sole reason for our 6.6 upgrade was the UI.&amp;nbsp; Former positions at previous companies I delved in web development and overall I have a high desire and attraction to clean interfaces, especially if it’s an interface my eyeballs are glued to on a daily basis.&amp;nbsp; With the clarity theme being the magnet it is, and honestly without much additional motivation I snapped the existing 6.5 appliances (primary and remote collectors) and took the leap.&amp;nbsp; Upgrades went without a hitch.&amp;nbsp; Beautiful.&amp;nbsp; Data still in tact on the other end and without errors?&amp;nbsp; Even better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had already learned to &lt;STRONG&gt;not&lt;/STRONG&gt; modify existing alert definitions or apply customizations to out-of-the-box objects as upgrades will reset them, so I knew my views and dashboards I implemented from Iwan Rahabok’s &lt;A href="http://virtual-red-dot.info/operationalize-your-world/"&gt;virtual-red-dot&lt;/A&gt; were going to be fine.&amp;nbsp; Actually, the new dashboards out-of-the-box with 6.6 proved to be as useful and provide some similar insight.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I’ve kicked up some questions through our TAM channel and hope they make their way to feature requests – a lot of them dealing with capacity and projects.&amp;nbsp; Here’s hoping that now with the UI getting the well-deserved TLC it needed, capacity management and planning specifically is next on the hit list for some love; being able to manage project scenario implementation dates in bulk, or manage through API, or even change project capacity containers to view different consumption models (i.e. demand, consumption, and allocation).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Integration with vRealize Log Insight and vRealize Business is a huge plus… at this moment I’m being tasked with carving up data for senior leadership to display the sorts of data these two integrated products provide, as well as a combination of the new out-of-the-box dashboards and management packs from &lt;A href="https://bluemedora.com/platforms/true-visibility-suite-for-vmware/"&gt;Blue Medora&lt;/A&gt; we are currently testing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And last but not least, the hardening report capabilities provided our Information Security team with the required insight needed to ensure compliance based on the controls approved by our infrastructure team.&amp;nbsp; It's really as easy as modifying the hardening alert definitions to suit your environment, provide tailored least-privilege access to the dashboard, and set up automated distribution of the hardening report via the report scheduler.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tip of the hat to the vROps crew for an amazing update, can't wait to see what's in the pipeline!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Aug 2017 05:12:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/New-Contest-Share-Your-vROps-6-6-Upgrade-Story/m-p/1396399#M8013</guid>
      <dc:creator>jcossota_san</dc:creator>
      <dc:date>2017-08-01T05:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: vROps 6.6 - Total Capacity value in Capacity Remaining WRONG (Projects also busted?)</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-6-6-Total-Capacity-value-in-Capacity-Remaining-WRONG/m-p/2730937#M17488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Turns out the Total Capacity metric under the Capacity Remaining tab is an average.&amp;nbsp; Some clusters experienced events where hosts were either disconnected or unavailable, and this affected the Total Capacity metric.&amp;nbsp; Capacity under the Workload tab represents the real-time value.&amp;nbsp; Not ideal when you are performing capacity planning using current data, but there's a way to even it back out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VMware suggested that I modify the policy for the Cluster Compute Resource adapter by changing the Capacity Calculation setting from Current to &lt;STRONG&gt;Trend&lt;/STRONG&gt;.&amp;nbsp; This balanced my Total Capacity metric back out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="vrops-policy.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/73894i020D31906FB415C6/image-size/large?v=v2&amp;amp;px=999" role="button" title="vrops-policy.jpg" alt="vrops-policy.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jul 2017 04:07:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-6-6-Total-Capacity-value-in-Capacity-Remaining-WRONG/m-p/2730937#M17488</guid>
      <dc:creator>jcossota_san</dc:creator>
      <dc:date>2017-07-12T04:07:10Z</dc:date>
    </item>
    <item>
      <title>vROps 6.6 - Total Capacity value in Capacity Remaining WRONG (Projects also busted?)</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-6-6-Total-Capacity-value-in-Capacity-Remaining-WRONG/m-p/2730936#M17487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When I select Cluster &amp;gt; Analysis &amp;gt; Capacity Remaining the Total Capacity value is incorrect for both CPU and Memory.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under Workload the Capacity value is accurate.&amp;nbsp; For instance:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="vrops_workload_tc.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/73764i7C8207DEED881A9D/image-size/large?v=v2&amp;amp;px=999" role="button" title="vrops_workload_tc.jpg" alt="vrops_workload_tc.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is incorrect, which skews calculations (of course I'm under tight deadline for compute procurement):&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="vrops_capremain_tc.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/73765iEBC88D39EF1DE3B5/image-size/large?v=v2&amp;amp;px=999" role="button" title="vrops_capremain_tc.jpg" alt="vrops_capremain_tc.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Additionally, the Projects page doesn't seem to be correct either.&amp;nbsp; It shows the most constrained resource for the above selected cluster is CPU at 96% demand!&amp;nbsp; As you can see above Memory is the most constrained resource.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an SR open just wanting to see if I'm looking at something wrong, my policy is busted, or if anyone else has come across this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jul 2017 20:07:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-6-6-Total-Capacity-value-in-Capacity-Remaining-WRONG/m-p/2730936#M17487</guid>
      <dc:creator>jcossota_san</dc:creator>
      <dc:date>2017-07-06T20:07:58Z</dc:date>
    </item>
  </channel>
</rss>

