Bug 245123 - Properties view related issues for AWS resources
Summary: Properties view related issues for AWS resources
Status: ASSIGNED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Geclipse (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Moritz Post CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-25 10:38 EDT by Ariel Garcia CLA
Modified: 2014-01-09 16:01 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ariel Garcia CLA 2008-08-25 10:38:16 EDT
Again several issues which don't deserve separate bugs:

* the properties view for AMI/AKI/ARI images is missing the architecture info, and eventually type (kernel, machine, ramdisk)

* in the properties for a running instance, the fields "kernel ID" (Ramdisk ID also) and "Key Name" remain empty.

* elastic IPs associated to a running instance are missing from the properties

* the properties page could be organized a bit, currently everything falls under the "General" category. The "Reason" field should be renamed or be moved _after_ "Status" (currently i can have "Reason: user initiated", and then "Status: terminated")

* using "Copy" on one property (for instance DNS name) copies also the property name together with the value, so i get "DNS NameMY_AWS_HOST_NAME" all glued together.
Comment 1 Ariel Garcia CLA 2008-08-25 11:01:35 EDT
Add'l issue/question:

* If somebody starts an instance giving me permissions to access it, where can i see that, resp. distinguish that instance from another one that I start? Should there be some related info in the properties page or somehwere else?
Comment 2 Moritz Post CLA 2008-09-05 12:00:37 EDT
(In reply to comment #0)
> Again several issues which don't deserve separate bugs:
> 
> * the properties view for AMI/AKI/ARI images is missing the architecture info,
> and eventually type (kernel, machine, ramdisk)

That is correct. These information are not provided by EC2.

> * in the properties for a running instance, the fields "kernel ID" (Ramdisk ID
> also) and "Key Name" remain empty.

I think these information are not provided by EC2 as well. Will look into it.
 
> * elastic IPs associated to a running instance are missing from the properties

refreshing the computing node by contracting/expanding it will refresh the running instance and with it the ip. This is related to the programmatic refresh of a category, bug 239012.

> * the properties page could be organized a bit, currently everything falls under
> the "General" category. The "Reason" field should be renamed or be moved _after_
> "Status" (currently i can have "Reason: user initiated", and then "Status:
> terminated")

Yes. multiple categories are applicable here.
 
> * using "Copy" on one property (for instance DNS name) copies also the property
> name together with the value, so i get "DNS NameMY_AWS_HOST_NAME" all glued
> together.

That is something originating from the properties view imo. If their is a way to overcome this behaivour i would love to know about it.