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"
m (→Ideas) |
|||
| Line 5: | Line 5: | ||
* It should allow us to deploy OSGi bundles (that's our future goal) | * It should allow us to deploy OSGi bundles (that's our future goal) | ||
* Information Service (fetchService) should provide all the necessary and available info from AWS | * Information Service (fetchService) should provide all the necessary and available info from AWS | ||
| + | |||
| + | === 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 == | == Open Issues == | ||
Revision as of 09:58, 7 April 2008
Ideas
- We create another AMI (Amazon Machine Image) that contains
- Java and e.g. a tomcat
- It should allow us to deploy OSGi bundles (that's our future goal)
- Information Service (fetchService) should provide all the necessary and available info from AWS
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)