Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1256

Provide amount of resources needed by Network Observability

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 241, NetObserv - Sprint 242, NetObserv - Sprint 243, NetObserv - Sprint 244, NetObserv - Sprint 245, NetObserv - Sprint 246, NetObserv - Sprint 247, NetObserv - Sprint 248, NetObserv - Sprint 249, NetObserv - Sprint 250

      The most common questions asked are:

      • How much resources do I need to enable Network Observability?
      • Given the size of my cluster, do I have enough resources to enable Network Observability?

      This Jira issue is to test and come up with answers to these questions.  The CPU resource is the most critical and tied to memory since selecting the number of CPUs for a node also determines the amount of memory (although there are varying options).

      The tasks are:

      1. Determine the peak CPU usage.  Then see what percentage of peak usage is needed by Network Observability.  For example, if you have 40 nodes with 16 vCPUs per node and peak usage is 80%, that is 512 vCPUs.  If Network Observability needs max 50 vCPUs, then that is slightly less than 10% of peak CPU.

      2. Do similar analysis for memory.

      3. Note how much storage is used on a daily basis.

      4. Test with different testbeds.  See NETOBSERV-224, NETOBSERV-483, and NETOBESRV-484.

            stlee@redhat.com Steven Lee
            stlee@redhat.com Steven Lee
            Nathan Weinberg Nathan Weinberg
            Sara Thomas Sara Thomas
            0 Vote for this issue
            5 Start watching this issue