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

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.

Stefan Bunciak <sbunciak> made a comment on jira JBIDE-10263

There are max 3 applications (gears) available on OpenShift

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)

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.

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.

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

A GET request on /user will get you max_gears and consumed_gears.

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>