Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695027 - cluster-capacity command is part of the command hypercc now
Summary: cluster-capacity command is part of the command hypercc now
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-02 10:33 UTC by Oscar Casal Sanchez
Modified: 2019-04-03 07:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Oscar Casal Sanchez 2019-04-02 10:33:07 UTC
Document URL:
#############
https://docs.openshift.com/container-platform/3.11/admin_guide/cluster_capacity.html 

Section Number and Name:
########################
Running Cluster Capacity Analysis on the Command Line 

Describe the issue:
################### 

As a user, I can read the next command:

$ cluster-capacity --kubeconfig <path-to-kubeconfig> \
    --podspec <path-to-pod-spec>

or 

$ cluster-capacity --kubeconfig <path-to-kubeconfig> \
    --podspec <path-to-pod-spec> --verbose

The cluster-capacity command doesn't exist anymore. Red Hat with RHEL provides with the package openshift-enterprise-cluster-capacity.x86_64 the binary hypercc what's a binary that can run any capacity commands: cluster-capacity or genpod.

Then, to use the cluster-capacity command should be something like this:

$ hypercc cluster-capacity --kubeconfig <path-to-kubeconfig> \
    --podspec <path-to-pod-spec>

or 

$ hypercc cluster-capacity --kubeconfig <path-to-kubeconfig> \
    --podspec <path-to-pod-spec> --verbose


Note You need to log in before you can comment on or make changes to this bug.