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 "EclipseLink/Cloud"
m (→Scope) |
m (→Hardware) |
||
| Line 17: | Line 17: | ||
==Software== | ==Software== | ||
==Hardware== | ==Hardware== | ||
| + | ===4 Machines=== | ||
| + | *Our cluster similations will run on an existing set of 4 machines of varying capability that run on a private subnet accessible from the dual networked PC1 via remote desktop | ||
| + | ====PC1:xps435: Windows 7 64-bit 8 core Intel i7-920==== | ||
| + | *192.168.0.194 | ||
| + | ====PC2:mfobrien-pc2: Windows XP 32-bit 2 core Intel E8400==== | ||
| + | *192.168.0.191 | ||
| + | ====PC3:beowulf5: Windows XP 32-bit 2 core Intel P630==== | ||
| + | *192.168.0.165 | ||
| + | ====PC4:beowulf6: Windows XP 32-bit 2 core Intel P630==== | ||
| + | *192.168.0.166 | ||
| + | |||
==References== | ==References== | ||
*[http://csrc.nist.gov/groups/SNS/cloud-computing/ NIST definition of Cloud Computing] | *[http://csrc.nist.gov/groups/SNS/cloud-computing/ NIST definition of Cloud Computing] | ||
Revision as of 11:32, 27 October 2010
Contents
Cloud Enabled EclipseLink : CEE
DISCLAIMER: This page reflects investigation into how EclipseLink technology can used as part of - or benefit from integration with other projects. It does NOT imply any formal certification from EclipseLink on these technologies or make any assumptions on the direction of the API. This page is purely experimental speculation.
Scope
- This page started 20101020 details thoughts, initiatives or projects surrounding performance optimization through use of Cloud Computing hardware running EclipseLink as a layer of their software stack.
- Multitenancy may enter into the discussion here - where everything is shared (OS, software stack, application and database) except that data is kept separate between different customers. The complexity in this case moves to the developer in the form of separate data models.
- Virtualization may be discussed here - where everything is logically separated into virtual machines. A valid use case is one where virtualization is used as a means to offer multiple release versions of a multitenancy application.
Analysis
- The move from a single server hosting single customer applications to a cloud server hosting multiple applications with some or all of these running as multitenant applications will involve a lot of design decisions because of the increased complexity of simultanously dealing with concurrent customers, applications and hardware.
- In some ways we are already dealing with most of these issues separately.
- Hardware concurrency is dealt with in clusters and grid systems
- Software concurrency is experienced in multithreaded synchronization to resources such as memory and persistent storage on the system or network
- Customer concurrency is an issue in multitenant systems where the data model and its use is the only non-shared resource
- In some ways we are already dealing with most of these issues separately.
Recommendations
Software
Hardware
4 Machines
- Our cluster similations will run on an existing set of 4 machines of varying capability that run on a private subnet accessible from the dual networked PC1 via remote desktop
PC1:xps435: Windows 7 64-bit 8 core Intel i7-920
- 192.168.0.194
PC2:mfobrien-pc2: Windows XP 32-bit 2 core Intel E8400
- 192.168.0.191
PC3:beowulf5: Windows XP 32-bit 2 core Intel P630
- 192.168.0.165
PC4:beowulf6: Windows XP 32-bit 2 core Intel P630
- 192.168.0.166