Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Cloud"

m (Cloud Enabled EclipseLink : CEE)
m
 
(12 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
=Cloud Enabled EclipseLink : CEE=
 
=Cloud Enabled EclipseLink : CEE=
 
<div style="border: 3px red solid;" align="center" ><font color="red">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.</font></div>  
 
<div style="border: 3px red solid;" align="center" ><font color="red">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.</font></div>  
 +
<!--
 
==Scope==
 
==Scope==
*This page details thoughts, initiatives or projects surrounding performance optimization through use of Cloud Computing hardware running EclipseLink as a layer of their software stack.
+
*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.
 
*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.
 
*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.
Line 16: 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]
Line 25: Line 38:
 
*[http://www.infoworld.com/d/cloud-computing?source=footer Cloud Computing Channel - InfoWorld]
 
*[http://www.infoworld.com/d/cloud-computing?source=footer Cloud Computing Channel - InfoWorld]
 
*[http://en.wikipedia.org/wiki/Acadia_(technical_partnership) VBlock Virtualization initiative]
 
*[http://en.wikipedia.org/wiki/Acadia_(technical_partnership) VBlock Virtualization initiative]
 +
*[http://en.wikipedia.org/wiki/Jazelle Jazelle] enables [http://en.wikipedia.org/wiki/ARM9E ARM 9E] chips to run Java bytecode in hardware (this not a Parallax Propeller running assembly language) - mostly for J2ME not JEE.

Latest revision as of 22:50, 13 November 2011

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.

References

Back to the top