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

[Moritz Post <mpost@xxxxxxxxxxxxxx>]

Hi
Yeah i agree that it is a little hard to really grasp what i am talking about. To further describe the functioanllity i have attatched a couple of screenshots demonstrating this functionality inside the Cloud Studio (http://www.service-cloud.com/) application. This Eclipse based application is also allowing to interact with the EC2/S3 services.

=== 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).

 

=== 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.



=== 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).



I hope these screenshots helped to describe the functionality we need should include in the gEclipse EC2 implementation. I don't think the way the cloud studio is handling things is the best possible solution but it does do the job. Are there any analogies in geclipse?

greets
Moritz

Just to give some initial comments to start a discussion here …

> - Keypair Management (allows login into a EC2 instance without password)
>    Keypairs are created (registered) and deleted and by creating produce a pk file

 

I suspect with keypair management you mean the remote management of registered keypairs for your EC2 instances, right? It would be nice to have a more detailed description here about what you mean. Nevertheless I think we can manage this with context menu entries for the instances in combination with enhanced functionality of the auth token view, so I currently do not see any need for yet another view.

> - Security Management (think firewall)
>    Security groups are created/deleted and rules are added to this group (open port 80 for ip 1.2.3.4)

 

Also here I am not completely sure about you are talking, more details please, we are not experts for EC2. Nevertheless I know that Ganymede itself will be shipped with new functionality concerning security management. I do not know if your use case may fit in there, but it may be worth to have a look at this.

> - Elastic IPs (attached IP address which survives an instance restart)
>    fixed ips are added to running instances

 

Where do these IPs come from? How are they attached to the instance? Isn’t something like a context menu enough here? Maybe also an extended launch configuration with another tab “Elastic IPs” would be useful here?

 

Cheers, Mathias

_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev