Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 2979a09

Browse files
maheroumaherou
committedJan 16, 2025·
Update use.html
1 parent 6cbd302 commit 2979a09

File tree

1 file changed

+39
-21
lines changed

1 file changed

+39
-21
lines changed
 

‎use.html

+39-21
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
<meta charset="utf-8">
1616
<meta http-equiv="X-UA-Compatible" content="IE=edge">
1717
<meta name="viewport" content="width=device-width, initial-scale=1">
18-
<title>E4S - Join</title>
18+
<title>Using E4S</title>
1919

2020
<!-- CSS -->
2121
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Josefin+Sans:300,400|Roboto:300,400,500">
@@ -61,17 +61,11 @@
6161
<div class="collapse navbar-collapse" id="top-navbar-1">
6262
<ul class="nav navbar-nav">
6363
<!--MENU START-->
64-
<li><a href="index.html">Home</a></li>
65-
<li><a href="events.html">Events</a></li>
66-
<li><a href="about.html">About</a></li>
67-
<li><a href="e4s-cl.html">E4S-CL</a></li>
68-
<li><a href="DocPortal.html">Products</a></li>
69-
<li><a href="Deployments.html">Deployments</a></li>
70-
<li><a href="policies.html">Policies</a></li>
71-
<li><a href="contact.html">Contact</a></li>
72-
<li><a href="join.html">Join</a></li>
73-
<li><a href="documentation.html">Documentation</a></li>
74-
<li><a class="btn btn-link-3" href="download.html">Download</a></li>
64+
<li><a href="index.html" style="font-size: 18px;">Home</a></li>
65+
<li><a href="use.html" style="font-size: 18px;">Using E4S</a></li>
66+
<li><a href="join.html" style="font-size: 18px;">Joining E4S</a></li>
67+
<li><a href="about.html" style="font-size: 18px;">About</a></li>
68+
<li><a href="contact.html" style="font-size: 18px;">Contact</a></li>
7569
<!--MENU END-->
7670
</ul>
7771
</div>
@@ -88,15 +82,39 @@
8882

8983
<div class="row">
9084
<div class="col-sm-12 section-description" align=left>
91-
E4S represents a growing community of HPC software products. Please <a href="contact.html">contact us</a> if you would like your product to be a part of E4S.
92-
<br><br>
93-
<b>Pre-requisite:</b> Justification for being included. The product must have some value or strong potential value to the HPC community. In other words, it must make sense for the product to belong to E4S.
94-
<br>
95-
<b>Level 0:</b> Be listed in the E4S Spack installation script and be buildable in all E4S target environments. The list of Spack recipes for E4S is <a href="https://github.com/E4S-Project/e4s/tree/master/environments">here</a>.
96-
<br>
97-
<b>Level 1:</b> Be present in the <a href="DocPortal.html">DocPortal</a>. To achieve this, we need a URL to your main repo to add to <a href="https://github.com/E4S-Project/E4S-Documenter/blob/master/data/e4s_products.yaml">this list</a>.
98-
<br>
99-
<b>Level 2:</b> Satisfy all E4S <a href="https://e4s-project.github.io/policies.html">community policies</a>. Full satisfaction is not required at this time. We are still establishing a process. Note that derived requirements from E4S member packages are not required to satisfy community policies as long as they do not destabilize E4S builds or portability.
85+
<p>The Extreme-scale Scientific Software Stack (E4S) offers multiple methods for deploying its comprehensive collection of HPC and AI software packages. Below is an overview of these deployment options:</p>
86+
<ul>
87+
<li><strong>From-Source Builds:</strong>
88+
<ul>
89+
<li>E4S utilizes <a href="https://spack.io">Spack</a>, a flexible package manager, to facilitate building software directly from source. This approach allows users to customize builds according to their specific system architectures and requirements. Detailed instructions for manual installation are available in the <a href="https://e4s-project.github.io/manual-installation.html">E4S Manual Installation Guide</a>.</li>
90+
</ul>
91+
</li>
92+
<li><strong>Spack Build Caches:</strong>
93+
<ul>
94+
<li>To expedite the installation process, E4S provides pre-built binaries through Spack build caches. These caches contain binaries for major operating systems and architectures, enabling users to install software without the need for local compilation. More information can be found on the <a href="https://e4s-project.github.io/about.html">E4S About Page</a>.</li>
95+
</ul>
96+
</li>
97+
<li><strong>Containers:</strong>
98+
<ul>
99+
<li>E4S offers containerized versions of its software stack, compatible with platforms such as Docker, Singularity, Shifter, and CharlieCloud. These containers provide a consistent and portable environment for running HPC and AI applications across diverse systems. The <a href="https://e4s-project.github.io/download.html">E4S Download Page</a> provides access to these container images.</li>
100+
</ul>
101+
</li>
102+
<li><strong>Cloud Options:</strong>
103+
<ul>
104+
<li><strong>Amazon Web Services (AWS):</strong>
105+
<ul>
106+
<li>E4S is available on AWS, allowing users to deploy the software stack on cloud-based infrastructure. This facilitates scalable and flexible computing resources for various workloads. Details about E4S on AWS can be found on the <a href="https://e4s-project.github.io">E4S Home Page</a>.</li>
107+
</ul>
108+
</li>
109+
<li><strong>Google Cloud Platform (GCP):</strong>
110+
<ul>
111+
<li>Users can also deploy E4S on GCP, leveraging Google's cloud services to run HPC and AI applications. This option provides access to high-performance virtual machines and storage solutions. Information regarding E4S on GCP is available on the <a href="https://e4s-project.github.io">E4S Home Page</a>.</li>
112+
</ul>
113+
</li>
114+
</ul>
115+
</li>
116+
</ul>
117+
<p>By offering these diverse deployment methods, E4S ensures flexibility and ease of use for researchers and developers working across various computing environments.</p>
100118
</div>
101119
</div>
102120

0 commit comments

Comments
 (0)
Please sign in to comment.