'euca-describe-availability-zones verbose' should show vm types for non-admin users

Bug #537464 reported by Andrew Glen-Young
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running 'euca-describe-availability-zones verbose' as a non-admin user shows the availability zone status _only_ and does not show what vm instances are available.

I don't think that displaying the available vm types should be limited to the admin user only. I cannot think of a valid reason for this restriction (however I am happy to be proven wrong).

The 'getDescriptionEntry' function in clc/modules/cluster-manager/src/main/java/edu/ucsb/eucalyptus/cloud/cluster/ClusterEndpoint.java seems to be the culprit.

----

Running the command as an admin user:

$ euca-describe-availability-zones verbose
AVAILABILITYZONE mycloud 127.0.0.1
AVAILABILITYZONE |- vm types free / max cpu ram disk
AVAILABILITYZONE |- m1.small 0031 / 0032 1 128 2
AVAILABILITYZONE |- c1.medium 0031 / 0032 1 256 5
AVAILABILITYZONE |- m1.large 0015 / 0016 2 512 10
AVAILABILITYZONE |- m1.xlarge 0015 / 0016 2 1024 20
AVAILABILITYZONE |- c1.xlarge 0007 / 0008 4 2048 20

Running the command as a non-admin user:

$ euca-describe-availability-zones verbose
AVAILABILITYZONE mycloud 127.0.0.1

Revision history for this message
chris grzegorczyk (chris-grze) wrote :

As the author of the "culprit" I can tell you this is not a bug and is indeed the intended behaviour.

cheers.

Revision history for this message
Thierry Carrez (ttx) wrote :

Expected behavior.

Changed in eucalyptus (Ubuntu):
status: New → Invalid
Revision history for this message
Andrew Glen-Young (aglenyoung) wrote :

@chris, could you please explain the rationale behind this behavior? Since this information is often needed by developers and users when they want to create or run images on EUC - I am curious as to why this command is limited to the admin user only?

Revision history for this message
Thierry Carrez (ttx) wrote :

I think the rationale is EC2 behavior compatibility.

Revision history for this message
chris grzegorczyk (chris-grze) wrote :

@Andrew What Thierry says is correct. More specifically, we need to provide extra information for admins, but for many tools the normal user's view needs to be the same as that presented by EC2 or many tools do not work correctly.

Revision history for this message
Andrew Glen-Young (aglenyoung) wrote :

@chris, @Thierry Thanks, this makes sense to me now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.