Bug 806836

Summary: [REST API] should inform client about application quota
Product: OKD Reporter: Andre Dietisheim <adietish>
Component: MasterAssignee: Krishna Raman <kraman>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.xCC: adietish, lnader, mfisher, mpatel, qgong, xcoulon
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-17 21:30:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andre Dietisheim 2012-03-26 10:36:50 UTC
User quotas limit the number of applications a user may create on the PaaS. It would be by far better to offer this validation upfront to the user (in the tooling). Since there are already different kind of users the PaaS should allow us to know about these quotas.

Comment 1 JBoss JIRA Server 2012-03-26 10:38:44 UTC
Andre Dietisheim <adietish> made a comment on jira JBIDE-10263

That means that the REST service should allow us to know about the quota. I filed an appropriate issue in the OpenShift bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=806836

Comment 2 JBoss JIRA Server 2012-03-26 11:44:16 UTC
Max Rydahl Andersen <max.andersen> made a comment on jira JBIDE-10263

agreed there should be a way to know how many slots is available but until that is available we can do a warning if user have 5 already filled.

Comment 3 JBoss JIRA Server 2012-04-10 09:11:46 UTC
Stefan Bunciak <sbunciak> made a comment on jira JBIDE-10263

There are max 3 applications (gears) available on OpenShift

Comment 4 JBoss JIRA Server 2012-04-10 09:20:35 UTC
Max Rydahl Andersen <max.andersen> made a comment on jira JBIDE-10263

Stefan, not true ;)

You have 3 applications available by default on OpenShift - but you can have more (i.e. I got 50)

Comment 5 JBoss JIRA Server 2012-04-24 13:27:05 UTC
Max Rydahl Andersen <max.andersen> made a comment on jira JBIDE-10263

For Beta3: We should raise the importance of having "max gear" info in openshift rest API. 

Then move to 3.3.x.

Comment 6 JBoss JIRA Server 2012-04-24 16:13:53 UTC
Max Rydahl Andersen <max.andersen> made a comment on jira JBIDE-10263

For Beta3: We should raise the importance of having "max gear" info in openshift rest API. 
With scaling this is no longer just create_apps >= max_gears, its created_apps * scale-size(?) >= max_gears.

Is there API to calculate this ?

For 3.3.0 we rely on error message to be informative enough, so raise on openshift lists and then move to 3.3.x.

Comment 7 JBoss JIRA Server 2012-04-30 11:24:25 UTC
Andre Dietisheim <adietish> made a comment on jira JBIDE-10263

error reporting is informative about the cause:

!error-application-quota-reached.png!

The wording could be improved though.

I move the issue to 3.3.x

Comment 8 Lili Nader 2012-08-15 20:21:55 UTC
A GET request on /user will get you max_gears and consumed_gears.

Comment 9 Rony Gong 🔥 2012-08-16 02:04:20 UTC
Verified on devenv_1995, could get user's max_gear

      <link>
          <optional-params/>
          <method>POST</method>
          <href>https://ec2-174-129-130-66.compute-1.amazonaws.com/broker/rest/user/keys</href>
          <required-params>
            <param>
              <description>Name of the key</description>
              <valid-options/>
              <name>name</name>
              <invalid-options/>
              <type>string</type>
            </param>
            <param>
              <description>Type of Key</description>
              <valid-options>
                <valid-option>ssh-rsa</valid-option>
                <valid-option>ssh-dss</valid-option>
              </valid-options>
              <name>type</name>
              <invalid-options/>
              <type>string</type>
            </param>
            <param>
              <description>The key portion of an rsa key (excluding ssh-rsa and comment)</description>
              <valid-options/>
              <name>content</name>
              <invalid-options/>
              <type>string</type>
            </param>
          </required-params>
          <rel>Add new SSH key</rel>
        </link>
      </links>
      <login>qgong</login>
      <max-gears>10</max-gears>
    </user>
  </data>
  <status>ok</status>
  <messages/>
  <type>user</type>