Re: AW: AW: [geclipse-dev] Supporting AWS infrastructure in g-Eclipse

[Moritz Post <mpost@xxxxxxxxxxxxxx>]

Hi Mathias

Thanks for the details, let’s go through them …

 

=== Security Groups ===

The actions of the view allow to add/remove security groups, which are than shown in the list to the top of the view. Each security group can than be selected to add and remove entries in its permission list (context menu).

 

 

Are these security groups specific for an AMI or a running instance? In any case, how about a properties page within the properties dialog? Of course a view could do it as well … but you know we already have a lot of views.

These security groups are completely decoupled from an AMI or a running instance. They are attached when launching an AMI but their management is independent.

I think, due to the new category based VO subfolder layout, we could also create a folder structure like this:

AWS VO
 \-- Instances
 \-- Images
 \-- Security Groups
      \-- my security group
      \-- another security group
 \-- Storage

To add a security group you would rightclick on "Security Group" and choose "Add Security Group". Is it possible to attach actions to a Category? On a particular security group you could than add an action to display the properties in some kind of dialog to edit the rules in a table form similar to the one in the screenshot. Also you could display the details of the security group in the properties dialog.

=== Keypairs ===

You add/remove keypairs via the views actions.To add a keypair you choose a name for the keypair and a local file to save the generated private key to. This keypair is also the one you specify in the launch dialog if you want to login without a password.

 

This is clearly an authentication token, right?! So we should implement it as such.

It seams like it, but it is not really used as such. When you create one you are given a pk file. You specify the name of the keypair in the launch dialog and when the instance is running,  you insert the ok file in the SSH2 preferences to login to an EC2 instance. so you don't make use of it in the context of geclipse.

Also... It could be an authentication token but that would mean, that you would need to create an authentication token (AWSToken) to create a keypair token. You would need to fetch the keypair name.

This scenario feels kind of awkward since you would create a token but not use it for authentication.

A possibility would be to make an entry at the AWS VO subfolder.

 

=== Elastiv IPs ===

In this view you can allocate an address. Allocating means to request a fixed ip from the EC2 infrastructure. This address can than be attached to a running EC2 instance. When the EC2 instance is terminated the ip gets disassociated from the EC2 instance but stays in the pool of assigned IPs (causing costs).

Also here I tend to use a properties page. Nevertheless as you mentioned the pool of assigned IPs I would rather see the IP as a grid resource. Maybe it would be possible to have a resource category holding these IPs?

Grid resource as in grid element? I could image to add them their. When you have one of these ips assigned to you, you could rightclick on a running instance and choose "Assign Elastic IP" -> list of ips -> "1.2.3.4"

greets Moritz