-
Notifications
You must be signed in to change notification settings - Fork 934
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show org and space quotas #2299
Show org and space quotas #2299
Conversation
ab8feab
to
a0873c7
Compare
85bc867
to
4d8d83d
Compare
* code currently assumes responses with log limits. Consider backward compatibility before shipping. Signed-off-by: Carson Long <lcarson@vmware.com>
Signed-off-by: Matthew Kocher <mkocher@vmware.com>
* will show "unlimited" for old CC API's which is technically correct Signed-off-by: Carson Long <lcarson@vmware.com>
4d8d83d
to
07a6d2e
Compare
This updates four commands:
|
Cool, this looks good in that it builds and displays org quotas with |
@pivotalgeorge the work to add the Our goal in splitting up the work like this is to make each PR more easily reviewable by y'all. Happy to take feedback (ideally in slack) to improve our current process, if you find it confusing / not ideal :). |
Signed-off-by: Rebecca Roberts <robertsre@vmware.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* org-quota and space-quota now show log volume * code currently assumes responses with log limits. Consider backward compatibility before shipping. * add log volume to space-quotas and org-quotas commands * will show "unlimited" for old CC API's which is technically correct * Fix unit tests in ccv3 Co-authored-by: Rebecca Roberts <robertsre@vmware.com> Co-authored-by: Matthew Kocher <mkocher@vmware.com> Co-authored-by: Carson Long <lcarson@vmware.com>
* org-quota and space-quota now show log volume * code currently assumes responses with log limits. Consider backward compatibility before shipping. * add log volume to space-quotas and org-quotas commands * will show "unlimited" for old CC API's which is technically correct * Fix unit tests in ccv3 Co-authored-by: Rebecca Roberts <robertsre@vmware.com> Co-authored-by: Matthew Kocher <mkocher@vmware.com> Co-authored-by: Carson Long <lcarson@vmware.com>
* org-quota and space-quota now show log volume * code currently assumes responses with log limits. Consider backward compatibility before shipping. * add log volume to space-quotas and org-quotas commands * will show "unlimited" for old CC API's which is technically correct * Fix unit tests in ccv3 Co-authored-by: Rebecca Roberts <robertsre@vmware.com> Co-authored-by: Matthew Kocher <mkocher@vmware.com> Co-authored-by: Carson Long <lcarson@vmware.com>
* org-quota and space-quota now show log volume * code currently assumes responses with log limits. Consider backward compatibility before shipping. * add log volume to space-quotas and org-quotas commands * will show "unlimited" for old CC API's which is technically correct * Fix unit tests in ccv3 Co-authored-by: Rebecca Roberts <robertsre@vmware.com> Co-authored-by: Matthew Kocher <mkocher@vmware.com> Co-authored-by: Carson Long <lcarson@vmware.com>
* Feat: create and update org quotas with log volume (#2298) * Show org and space quotas (#2299) * org-quota and space-quota now show log volume * code currently assumes responses with log limits. Consider backward compatibility before shipping. * add log volume to space-quotas and org-quotas commands * will show "unlimited" for old CC API's which is technically correct * Fix unit tests in ccv3 * Create and update space quotas (#2300) * create-space-quota accepts log volume flag * update-space-quota accepts log volume flag * Update create-space-quota flag description * Make it clear that the log volume measured is in bytes rather than log lines. * Push and scale app and run-task * Bump rack from 2.2.3 to 2.2.3.1 in /fixtures/applications/example-app * `cf push` command accepts log rate limit flag * since `cf push` uses manifests this commit also adds support for log rate limit in manifests * `cf scale` command accepts log rate limit flag * app summary displayer can now handle rendering log rate and log rate limit metrics for running instances * app summaries will show `0 of 0` if the cloud controller does not support log rate limit container metrics * `cf run-task` command accepts log rate limit flag * update help text to suggest using ='s with -1 to avoid flag parsing problem * Flag parser accepts 0B, -1B, 0T, etc for flags * this affects non-manifest based commands * Extract constants for instance stats columns * Extract constant for column count Co-authored-by: Carson Long <lcarson@vmware.com> Co-authored-by: Matthew Kocher <mkocher@vmware.com> Co-authored-by: Rebecca Roberts <robertsre@vmware.com> Co-authored-by: Benjamin Fuller <Benjamintf1@gmail.com>
* Feat: create and update org quotas with log volume (#2298) * Show org and space quotas (#2299) * org-quota and space-quota now show log volume * code currently assumes responses with log limits. Consider backward compatibility before shipping. * add log volume to space-quotas and org-quotas commands * will show "unlimited" for old CC API's which is technically correct * Fix unit tests in ccv3 * Create and update space quotas (#2300) * create-space-quota accepts log volume flag * update-space-quota accepts log volume flag * Update create-space-quota flag description * Make it clear that the log volume measured is in bytes rather than log lines. * Push and scale app and run-task * Bump rack from 2.2.3 to 2.2.3.1 in /fixtures/applications/example-app * `cf push` command accepts log rate limit flag * since `cf push` uses manifests this commit also adds support for log rate limit in manifests * `cf scale` command accepts log rate limit flag * app summary displayer can now handle rendering log rate and log rate limit metrics for running instances * app summaries will show `0 of 0` if the cloud controller does not support log rate limit container metrics * `cf run-task` command accepts log rate limit flag * update help text to suggest using ='s with -1 to avoid flag parsing problem * Flag parser accepts 0B, -1B, 0T, etc for flags * this affects non-manifest based commands * Extract constants for instance stats columns * Extract constant for column count Co-authored-by: Carson Long <lcarson@vmware.com> Co-authored-by: Matthew Kocher <mkocher@vmware.com> Co-authored-by: Rebecca Roberts <robertsre@vmware.com> Co-authored-by: Benjamin Fuller <Benjamintf1@gmail.com>
This is blocked on #2298, don't merge before then.
Adds log volume limits to quota displays.
/cc @ctlong