[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [geclipse-dev] Supporting AWS infrastructure in g-Eclipse
|
Hi all
ACL's are important, but perhaps we invest at this moment of time a little
bit more effort in the hardening of the current implementation, especially
with the GRIA support. If that is done, I want to see the ACL stuff getting
integrated too!
But not all issues with GRIA key stores, etc are solved up to now! That is
much more urgent for the Reading meeting!
Harald
==========================================
Dr. Harald Kornmayer
Senior researcher
NEC Laboratories Europe
IT Division
Rathausallee 10
D-53757 Sankt Augustin
Germany
Phone: +49 2241 92 52 57
Fax: +49 2241 92 52 99
Email: harald.kornmayer@xxxxxxxxxxxx
NEC Europe Ltd., Registered Office: NEC House,
1 Victoria Road, London W3 6bL,
Registered in England 2832014
==========================================
>>-----Original Message-----
>>From: geclipse-dev-bounces@xxxxxxxxxxx
>>[mailto:geclipse-dev-bounces@xxxxxxxxxxx] On Behalf Of
>>Stuempert, Mathias IWR
>>Sent: Thursday, June 19, 2008 9:59 AM
>>To: Developer mailing list
>>Subject: AW: [geclipse-dev] Supporting AWS infrastructure in g-Eclipse
>>
>>Hi 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
>>
>>
