hello world: converged computing terms

.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

.github/LICENSE-BOOTSTRAP.md

@@ -0,0 +1,7 @@
+Copyright 2017 - Present Stuart Yamartino (@StuYam)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

.gitignore

@@ -0,0 +1,3 @@
+/_site
+/.sass-cache
+.DS_Store

404.html

@@ -0,0 +1,24 @@
+---
+layout: default
+---
+
+<style type="text/css" media="screen">
+  .container {
+    margin: 10px auto;
+    max-width: 600px;
+    text-align: center;
+  }
+  h1 {
+    margin: 30px 0;
+    font-size: 4em;
+    line-height: 1;
+    letter-spacing: -1px;
+  }
+</style>
+
+<div class="container">
+  <h1>404</h1>
+
+  <p><strong>Page not found :(</strong></p>
+  <p>The requested page could not be found.</p>
+</div>

CNAME

@@ -0,0 +1 @@
+converged-computing.org

Gemfile

@@ -0,0 +1,21 @@
+source "https://rubygems.org"
+
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+#     bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+# gem 'jekyll', '>= 3.6.3'
+
+# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
+# uncomment the line below. To upgrade, run `bundle update github-pages`.
+gem "github-pages", group: :jekyll_plugins
+gem "webrick"
+
+# If you have any plugins, put them here!
+group :jekyll_plugins do
+  gem 'jekyll-feed', '~> 0.6'
+end

README.md

@@ -4,17 +4,13 @@
 
 > A Best-of-Both-Worlds of HPC and Cloud
 
-This is a [CiSE Special Issue Proposal](https://www.authorea.com/users/34995/articles/430859-cise-guest-editors-guide) and 
-the repository where we will write and document our whitepaper to introduce it. 
-
-## Important Dates
-
-- Anticipated for 2023-2023
+This is the Converged Computing working space. It includes definitions, projects, and eventually will also include a [CiSE Special Issue](https://www.authorea.com/users/34995/articles/430859-cise-guest-editors-guide) on converged computing. 
 
 ## Overview
 
-Major trends have brought the cloud and high performance computing (HPC) communities closer together: the maturation of cloud technologies has shifted focus toward running workloads efficiently, and composite scientific workflows and resource heterogeneity and dynamism have revealed the limitations of traditional HPC resource and workflow management. It has become clear that the initially disparate communities have much to benefit in working together. This special issue aims to bridge the gap between HPC and cloud to discuss work in converged computing – the collaborative space between these traditionally separate communities – to develop novel technologies and applications. These hybrid technologies might span the gamut from automation, workflows, containerization, to software development and deployment and testing. This is a timely topic as collaborative work is happening to a greater degree that combines approaches from high performance computing with cloud-native computing.
+> Special Issue Anticipated for mid 2024
 
+Major trends have brought the cloud and high performance computing (HPC) communities closer together: the maturation of cloud technologies has shifted focus toward running workloads efficiently, and composite scientific workflows and resource heterogeneity and dynamism have revealed the limitations of traditional HPC resource and workflow management. It has become clear that the initially disparate communities have much to benefit in working together. This special issue aims to bridge the gap between HPC and cloud to discuss work in converged computing – the collaborative space between these traditionally separate communities – to develop novel technologies and applications. These hybrid technologies might span the gamut from automation, workflows, containerization, to software development and deployment and testing. This is a timely topic as collaborative work is happening to a greater degree that combines approaches from high performance computing with cloud-native computing.
 
 ## Guest Editors
 
@@ -24,3 +20,7 @@ Major trends have brought the cloud and high performance computing (HPC) communi
  - Jakob Luettgau, University of Tennessee Knoxville
  - Evan Bollig, Amazon Web Services
  - Bill Magro, Google
+
+## Thank you
+
+This site is based on [this template](https://bootstrapemail.com/) that is covered under the MIT license. The license is included [here](.github/LICENSE-BOOTSTRAP.md).

_config.yml

@@ -0,0 +1,53 @@
+# Welcome to Jekyll!
+#
+# This config file is meant for settings that affect your whole blog, values
+# which you are expected to set up once and rarely edit after that. If you find
+# yourself editing this file very often, consider using Jekyll's data files
+# feature for the data you need to update frequently.
+#
+# For technical reasons, this file is *NOT* reloaded automatically when you use
+# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
+
+# Site settings
+# These are used to personalize your new site. If you look in the HTML files,
+# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
+# You can create any custom variable you would like, and they will be accessible
+# in the templates via {{ site.myvariable }}.
+title: Converged Computing
+email: [email protected]
+description: >- # this means to ignore newlines until "baseurl:"
+ The best of both worlds for cloud and HPC
+baseurl: "" # the subpath of your site, e.g. /blog
+url: "https://converged-computing.org" # the base hostname & protocol for your site, e.g. http://example.com
+permalink: /docs/:title
+
+# Build settings
+markdown: kramdown
+plugins:
+  - jekyll-feed
+kramdown:
+  auto_id_prefix: 'doc-'
+
+# Collections
+collections:
+  docs:
+    output: true
+    permalink: /:collection/:title/
+
+# Defaults
+defaults:
+  -
+    scope:
+      path: ""
+      type: "docs"
+    values:
+      layout: "docs"
+
+
+# Exclude from processing.
+# The following items will not be processed, by default. Create a custom list
+# to override the default setting.
+exclude:
+   - Gemfile
+   - Gemfile.lock
+   - vendor

_data/border_radiuses.csv

@@ -0,0 +1,10 @@
+name,radius
+,4
+-none,0
+-sm,2
+-md,6
+-lg,8
+-xl,12
+-2xl,16
+-3xl,24
+-full,9999

_data/border_widths.csv

@@ -0,0 +1,7 @@
+name,width
+,1
+-2,2
+-3,3
+-4,4
+-5,5
+-0,0

_data/displays.json

@@ -0,0 +1 @@
+['inline','inline-block','block','table','none']

_data/font_sizes.csv

@@ -0,0 +1,12 @@
+name,size
+xs,12
+sm,14
+base,16
+lg,18
+xl,20
+2xl,24
+3xl,30
+4xl,36
+5xl,48
+6xl,64
+7xl,80

_data/font_weights.json

@@ -0,0 +1 @@
+[100, 200, 300, 400, 500, 600, 700, 800, 900]

_data/grid_cols.csv

@@ -0,0 +1,13 @@
+name,width
+1,8.333333%
+2,16.666667%
+3,25%
+4,33.333333%
+5,41.666667%
+6,50%
+7,58.333333%
+8,66.666667%
+9,75%
+10,83.333333%
+11,91.666667%
+12,100%

_data/line_heights.csv

@@ -0,0 +1,5 @@
+name,size
+1,1
+sm,1.25
+base,1.5
+lg,2

_data/palette_colors.csv

@@ -0,0 +1,103 @@
+name,color
+black,#000000
+white,#ffffff
+transparent,transparent
+gray-100,#f8f9fa
+gray-200,#e9ecef
+gray-300,#dee2e6
+gray-400,#ced4da
+gray-500,#adb5bd
+gray-600,#6c757d
+gray-700,#495057
+gray-800,#343a40
+gray-900,#212529
+blue-100,#cfe2ff
+blue-200,#9ec5fe
+blue-300,#6ea8fe
+blue-400,#3d8bfd
+blue-500,#0d6efd
+blue-600,#0a58ca
+blue-700,#084298
+blue-800,#052c65
+blue-900,#031633
+indigo-100,#e0cffc
+indigo-200,#c29ffa
+indigo-300,#a370f7
+indigo-400,#8540f5
+indigo-500,#6610f2
+indigo-600,#520dc2
+indigo-700,#3d0a91
+indigo-800,#290661
+indigo-900,#140330
+purple-100,#e2d9f3
+purple-200,#c5b3e6
+purple-300,#a98eda
+purple-400,#8c68cd
+purple-500,#6f42c1
+purple-600,#59359a
+purple-700,#432874
+purple-800,#2c1a4d
+purple-900,#160d27
+pink-100,#f7d6e6
+pink-200,#efadce
+pink-300,#e685b5
+pink-400,#de5c9d
+pink-500,#d63384
+pink-600,#ab296a
+pink-700,#801f4f
+pink-800,#561435
+pink-900,#2b0a1a
+red-100,#f8d7da
+red-200,#f1aeb5
+red-300,#ea868f
+red-400,#e35d6a
+red-500,#dc3545
+red-600,#b02a37
+red-700,#842029
+red-800,#58151c
+red-900,#2c0b0e
+orange-100,#ffe5d0
+orange-200,#fecba1
+orange-300,#feb272
+orange-400,#fd9843
+orange-500,#fd7e14
+orange-600,#ca6510
+orange-700,#984c0c
+orange-800,#653208
+orange-900,#331904
+yellow-100,#fff3cd
+yellow-200,#ffe69c
+yellow-300,#ffda6a
+yellow-400,#ffcd39
+yellow-500,#ffc107
+yellow-600,#cc9a06
+yellow-700,#997404
+yellow-800,#664d03
+yellow-900,#332701
+green-100,#d1e7dd
+green-200,#a3cfbb
+green-300,#75b798
+green-400,#479f76
+green-500,#198754
+green-600,#146c43
+green-700,#0f5132
+green-800,#0a3622
+green-900,#051b11
+teal-100,#d2f4ea
+teal-200,#a6e9d5
+teal-300,#79dfc1
+teal-400,#4dd4ac
+teal-500,#20c997
+teal-600,#1aa179
+teal-700,#13795b
+teal-800,#0d503c
+teal-900,#06281e
+cyan-100,#cff4fc
+cyan-200,#9eeaf9
+cyan-300,#6edff6
+cyan-400,#3dd5f3
+cyan-500,#0dcaf0
+cyan-600,#0aa2c0
+cyan-700,#087990
+cyan-800,#055160
+cyan-900,#032830

_data/sizings.json

@@ -0,0 +1 @@
+[0,1,2,3,4,5,6,7,8,9,10,12,16,20,24,32,40,48,56,64,80,96,112,128,144,150]

_data/spacings.json

@@ -0,0 +1 @@
+[0,1,2,3,4,5,6,7,8,9,10,12,16,20,24,32,40]

_data/terms.yaml

@@ -0,0 +1,24 @@
+getting-started:
+- name: Introduction
+  url: /docs/introduction
+- name: About
+  url: /about
+#  - name: Goals
+#    url: /docs/goals
+comparisons:
+- name: HPC vs HTC
+  url: /docs/hpc-vs-htc
+
+patterns:
+- name: jobs
+  url: /docs/job-patterns
+- name: workflows
+  url: /docs/workflow-patterns
+#- section: Projects
+#  items:
+#  - name: Journal Special Issue
+#    url: /docs/journal
+#  - name: Kubernetes
+#    url: /docs/kubernetes
+#  - name: HPC Schedulers
+#    url: /docs/hpc

_data/theme_colors.csv

@@ -0,0 +1,9 @@
+name,color
+primary,#0d6efd
+secondary,#6c757d
+success,#198754
+info,#0dcaf0
+warning,#ffc107
+danger,#dc3545
+light,#f8f9fa
+dark,#212529

_docs/accounting.md

@@ -0,0 +1,14 @@
+---
+layout: docs
+title:  "Accounting"
+sections:
+  - Example
+---
+
+Keeping track of resource usage time, usually on the level of a user or group. This information can be stored in a database and used for making future decisions about scheduling or priority. In terms of units of resource usage, this can vary. 
+
+## Example
+
+HPC uses core-hours (time spent doing the compute). One core-hour equals one CPU core being used for the duration of one hour of execution time. The time is measured as the jobs elapsed wall-clock time from start to finish. [[ref](https://help.itc.rwth-aachen.de/en/service/rhr4fjjutttf/article/090b27dc31484f3c833957978b039b55/), [ref](https://slurm.schedmd.com/accounting.html)]. Cloud does not have the same need for multi-tenancy as HPC, and so accounting to track resource usage is typically associated with cost. Cloud accounts for resources to bill projects, and charges based on data usage or instance cost.
+
+In Flux, accounting is separate from scheduling (flux-sched) as a design choice to make them swappable (e.g., install a different scheduler) however in many HPC managers they are built together, meaning accounting is part of the scheduler.

_docs/allocation.md

@@ -0,0 +1,12 @@
+---
+layout: docs
+title:  "Allocation"
+#sections:
+#  - Example
+---
+
+The actual set of physical resources that an application is running on. There are two types of allocations: shared and exclusive.
+
+ - *Exclusive allocation*: jobs have dedicated physical resources (e.g., nodes, cores, memory). Multiple users cannot share a physical resource, and resources are not shared between jobs. This setup is common in HPC.
+ - *Shared allocation*: jobs share underlying physical resources (e.g., nodes, cores, memory). Multiple users can run on the same physical resources. This setup is common in cloud.
+

_docs/application-programming-interface.md

@@ -0,0 +1,8 @@
+---
+layout: docs
+title:  "Application Programming Interface"
+#sections:
+#  - Example
+---
+
+Programmatic interface for interacting with components. In Kubernetes this might be the kube-apiserver, and in Flux it could be a socket (connected via flux proxy) or the flux restful API.