Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "G-Eclipse-Amazon-Integration"
(→Ideas) |
|||
| Line 1: | Line 1: | ||
| − | == | + | == Basic == |
| − | * | + | Here we want to discuss how an integration of Amazon Web Services (AWS) into the g-Eclipse framework can be realized. |
| − | ** Java and e.g. a tomcat | + | First we want to integrate the services S3 and EC2 from AWS. At the very beginning g-Eclipse started as a tool for Grid infrastructures, but as the differences between Grid and Cloud computing are not that big, the g-Eclipse model seems to be able to "host" the integration for AWS too. |
| − | * | + | |
| − | + | == Goals == | |
| + | |||
| + | * The tool should be able to manage the lifecycle of EC2 instances | ||
| + | * The tool should enable the ssh login into running instance | ||
| + | * The tool should be able to configure existing instance from the g-Eclipse framework. | ||
| + | * The tool should provide information of all running instances from one user to enable a efficient control of the resources. | ||
| + | |||
| + | * In the future, we want to provide a dedicated AMI (Amazon Machine Image), which | ||
| + | ** contains Java and a dedicated service e.g. a tomcat server or a OSGi kernel | ||
| + | * In the future we want to access dedicated AMI instances to enable the remote deployment of OSGi bundles | ||
=== EC2 Specific Ideas === | === EC2 Specific Ideas === | ||
Revision as of 07:25, 16 April 2008
Basic
Here we want to discuss how an integration of Amazon Web Services (AWS) into the g-Eclipse framework can be realized. First we want to integrate the services S3 and EC2 from AWS. At the very beginning g-Eclipse started as a tool for Grid infrastructures, but as the differences between Grid and Cloud computing are not that big, the g-Eclipse model seems to be able to "host" the integration for AWS too.
Goals
- The tool should be able to manage the lifecycle of EC2 instances
- The tool should enable the ssh login into running instance
- The tool should be able to configure existing instance from the g-Eclipse framework.
- The tool should provide information of all running instances from one user to enable a efficient control of the resources.
- In the future, we want to provide a dedicated AMI (Amazon Machine Image), which
- contains Java and a dedicated service e.g. a tomcat server or a OSGi kernel
- In the future we want to access dedicated AMI instances to enable the remote deployment of OSGi bundles
EC2 Specific Ideas
- The List of available system-images == Entry in the Service category
- Running instances of an image == Entry in the Computing Elements
- Bundles to deploy on a running image == Jobs
With a running image up and running the following interfacing technologies provide a good entry into the amazon virtual server:
- Using a created keypair for each instantiation of an image, a direct login (rightclick on instance in CE list) via ssh should be made possible. Because of the used new cert no additional login is required and the user is directly faced with the blinking shell in the console view.
- Similiary to the above, the user should be able to browse the new host system by selecting the node and opening it in the connection view via scp or sftp etc.
Open Issues
- Is there something like a group in S3/EC2? This could be used like a VO to browse the resources of a user/member.
- Deployment: Launch configuration or is there a concept like deployment e.g. in Webtools?
- Currently the S3 authentication implementation != x.509
- Is it possible (how?) to get the information about other S3 buckets that belong to a certain group?
- X.509 libraries, clarify IP issues, bouncycastle
- Management of running AMI instances
- Should work with proxies requiring authentication (cockpit application works fine, but AWS in g-Eclipse still has issues)
Dictionary
- S3/EC2 UIDs == (in a first approach) VO (Virtual Organization)
- S3 Storage == SE (Storage Element)
- AMI (Amazon Machine Image) == CE (Compute Element)
- Installing, starting bundles in a running AMI == Application Deployment
Important Interfaces
- IGridElement
- IGridElementCreator
- IVirtualOrganization (AbstractVirtualOrganization)
- IGridInfoService
- IAuthenticationTokenDescription, IAuthenticationToken (e.g. the Globus (x.509) implementation)