diff --git a/preview-osg-school-page/LICENSE b/preview-osg-school-page/LICENSE
new file mode 100644
index 000000000..8dada3eda
--- /dev/null
+++ b/preview-osg-school-page/LICENSE
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "{}"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright {yyyy} {name of copyright owner}
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/preview-osg-school-page/OfficeHoursSignin.html b/preview-osg-school-page/OfficeHoursSignin.html
new file mode 100644
index 000000000..c7cdcbebe
--- /dev/null
+++ b/preview-osg-school-page/OfficeHoursSignin.html
@@ -0,0 +1,14 @@
+
+
+
diff --git a/preview-osg-school-page/README.md b/preview-osg-school-page/README.md
new file mode 100644
index 000000000..1f40f4f4c
--- /dev/null
+++ b/preview-osg-school-page/README.md
@@ -0,0 +1,96 @@
+## Welcome to the OSG
+
+- [How to add to this Website](#deployment)
+- [Using Github for Development](#using-github-for-development)
+- [Pushing Changes to Production](#pushing-changes-to-production)
+
+This repository contains the source code of the OSG website; it is not the public facing site.
+
+The real webpage for the OSG is .
+
+# Deployment
+
+To have your changes merged into master you must create a PR and get one review. If you don't have anyone in mind you can request _@CannonLock_ and he will review it the next morning.
+
+### What We Do
+
+The OSG facilitates access to distributed high throughput computing for research in the US.
+The resources accessible through the OSG are contributed by the community, organized by the OSG, and governed by the OSG consortium.
+In the last 12 months, we have provided more than 1.2 billion CPU hours to researchers across a wide variety of projects.
+
+To see the breadth of the OSG impact, [explore our accounting portal](https://gracc.opensciencegrid.org).
+
+### Submit Locally, Run Globally
+
+Researchers can submit batch jobs from their home institution - or OSG-provided submit points - in order to access their local resources and expand
+elastically out to the OSG, leverage the distributed nature of our consortium.
+
+### Sharing Is Key
+
+*Sharing is a core principle of the OSG.* Over 100 million CPU hours delivered on the OSG in the past year were opportunistic: they would have remained on but idle
+if it wasn't for the OSG. Sharing allows individual researchers to access larger computing resources and large organizations to keep their utilization high.
+
+### Resource Providers
+
+The OSG consists of computing and storage elements at over 100 individual sites spanning the United States.
+These sites, primarily at universities and national labs, range in size from a few hundred to tens of thousands of CPU cores.
+
+### The OSG Software Stack
+
+The OSG provides an integrated software stack to enable high throughput computing; [visit our technical documents website for information](docs/).
+
+### Find Us!
+
+Are you a user wanting more computing resources?
+
+Are you a resource provider wanting to join our collaboration?
+
+If so, find us at the [support desk](https://support.opensciencegrid.org).
+
+## Internal Documentation
+
+### Using Github for Development
+
+1. Create a Branch from master with 'preview-' at the start of the branch name
+ - For instance 'preview-helloworld'
+2. Push this branch to the repo at https://github.com/path-cc/path-cc.github.io.git
+ - If you created the branch on github it is already there!
+4. Populate the changes that you want to see
+5. Preview the changes that you have made at https://path-cc.io/web-preview//
+ - For this instance https://path-cc.io/web-preview/preview-helloworld/
+6. When you are happy with the changes create a PR into master
+
+### Using Local Computer for Developement
+
+To make changes to the website clone the files and run the below line to run the container.
+
+```shell
+docker run -it -p 8002:8000 -v $PWD:/app -w /app ruby:2.7 /bin/bash
+```
+
+In the container run the below line to build the website.
+
+```shell
+gem install bundler:2.2.30
+bundle install
+bundle exec jekyll serve --watch --config _config.yml -H 0.0.0.0 -P 8000
+```
+After the build is complete the website will be available at [http://0.0.0.0:8000/](http://0.0.0.0:8000/)
+
+### Pushing Changes to Production
+
+The production websites (https://opensciencegrid.org/, https://osg-htc.org) are built automatically by GitHub Pages from the **master** branch.
+
+To make changes to the website, use the following workflow:
+
+1. Submit a pull request with website updates to the `master` branch (the default) and request a review.
+ - Any reviews with visual changes can be handled more quickly if you provide a [preview instance](#using-github-for-development)
+1. Upon approval you can view the changes at https://opensciencegrid.org/ and https://osg-htc.org
+
+### Adding To the Team Page
+
+The [team page](https://opensciencegrid.org/about/team) provides an overview of those working on the OSG. It's important to keep this updated to reflect the evolving nature of the OSG. To add yourself to this page, [create a pull request](https://help.github.com/articles/about-pull-requests/) (using the standard GitHub workflow) with the following:
+
+* A short config file about yourself, [following this example](https://github.com/opensciencegrid/opensciencegrid.github.io/blob/master/_data/people/bbockelm.yml). Make sure to include your *name*, *shortname* (typically either your GitHub ID as in `bbockelm` or *Firstname-Lastname* as in `Brian-Bockelman`), *institution*, *website*, and *photo*. If you are an area coordinator or have some other named role, you can fill in *title*.
+* Upload a headshot of yourself into the `assets/images/team` directory. Name it in the form `assets/images/team/Firstname-Lastname.jpg`; in this case, the corresponding value of the *photo* tag in your config file will be `/assets/images/team/Firstname-Lastname.jpg`.
+* If you are a member of the executive team, then add your shortname tag to the [organization file](https://github.com/opensciencegrid/opensciencegrid.github.io/blob/master/_data/orgs/exec-team.yml), `_data/orgs/exec-team.yml`.
diff --git a/preview-osg-school-page/about/computation-ideal-for-OSPool/index.html b/preview-osg-school-page/about/computation-ideal-for-OSPool/index.html
new file mode 100644
index 000000000..770a35482
--- /dev/null
+++ b/preview-osg-school-page/about/computation-ideal-for-OSPool/index.html
@@ -0,0 +1,17 @@
+
+
+
+
+
+ The OSG Consortium is a national and worldwide hub for research on distributed computing.
+ Below are some employment opportunities related to this work.
+
+
+
OSG Project Positions
+
The following positions are with projects that contribute directly to the OSG program of work.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Student Fellow
+
+
+
+
Institution
+
Morgridge Institute for Research & University of Wisconsin–Madison
+
+
+
+
+
Summary
+
Horizontal scaling of HTTP caches: learn how to automate load-balancing with Kubernetes.
+
+
The OSG offers an integrated software stack and infrastructure used by the High-Energy Physics
+community to meet their computational needs. Frontier Squid is part of this software stack and
+acts as an HTTP proxy, caching requests to improve network usage. We seek a fellow to turn our
+existing single cache Kubernetes deployment into one that can scale horizontally using the same
+underlying storage for its cache.
OSG is a consortium dedicated to the advancement of open science via the
+practice of distributed High Throughput Computing, and the advancement of
+its state of the art.
+
+
The OSG Consortium builds and operates a set of pools of shared computing and
+data capacity for distributed high-throughput computing (dHTC). Each pool is
+organized and operated to serve a particular research community (e.g. a campus,
+multi-institutional collaboration, etc.), using technologies and
+services provided by the core OSG Team. One of these pools, known as the
+Open Science Pool is operated for all of US-associated
+open science. The Consortium, thus, represents the totality of all researchers,
+resources, individuals and institutions that benefit from or contribute to any
+of the OSG Fabric of Services (further below).
+
+
The OSG Council governs the consortium ensuring that the OSG benefits
+the scientific mission of its stakeholders: the research communities, organizations
+that provide resources and services for them, including funding resources.
+
+
The Executive Team manages the core OSG Team, with
+team members from various institutions organized into Areas that provide core OSG
+technologies and services required to operate pools in support of research communities.
+As of January 2022, the OSG Team is funded primarily via the PATh (NSF #2030508),
+IRIS-HEP (NSF #1836650) projects, and in kind contributions from multiple entities,
+including DOE national laboratories.
+
+
Distributed High Throughput Computing
+
+
High-throughput computing (HTC) is the execution of computational work in the form
+of numerous, self-contained tasks to optimize their overall completion across
+available computing resources. Specialized by the OSG, distributed high-throughput
+computing (dHTC) involves the operation of HTC-optimized infrastructure across
+many independent, collaborating administrative domains.
+
+
The OSG Fabric of Services
+
+
The OSG provides various open-source software, other technologies, and services
+for researchers and research organizations to support their dHTC compute requirements.
+Our software and technologies allow research organizations to build dHTC systems
+at-scale from shared computing and data resources, and to make these resources
+available to researchers within virtual clusters (what the OSG calls “pools”).
+
+
Some pools or participating organizations provide application-specific interfaces
+or datasets, such that end-users may not even be aware of integration with
+OSG and its services/technologies. Many OSG technologies and services are
+based upon or directly leverage the HTCondor Software Suite (HTCSS), in addition
+to other open-source tools that enable shared computing and data capabilities.
+These can be deployed by a research organization to create their own dHTC pool
+across participating compute and data components, making their federated capacity
+available to the researchers they serve.
+
+
OSG Technologies and Services
+
+
The OSG’s Global Research Accounting (GRACC) system provides metrics of capacity
+contributions and usage across reporting OSG pools, including specific metrics
+for participating institutions and research projects, some of which represent
+hundreds or thousands of individual users.
+
+
The Open Science Pool (OSPool) provides dHTC capacity for research projects
+associated with a US-based academic, government, or non-profit organization,
+and with funding from the National Science Foundation through the PATh project
+(NSF #2030508). Applicable researchers can obtain access to OSPool resources
+via an access point operated by their institution or collaboration, or via the
+OSG Portal.
\ No newline at end of file
diff --git a/preview-osg-school-page/about/organization/index.html b/preview-osg-school-page/about/organization/index.html
new file mode 100644
index 000000000..b215519b6
--- /dev/null
+++ b/preview-osg-school-page/about/organization/index.html
@@ -0,0 +1,318 @@
+
+
+
+
+
+
+
+
+
+Members of the OSG Consortium | OSG
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Members of the OSG Consortium
+
+
We consider the consortium to be the totality of all researchers, resources, individuals and institutions that benefit from or contribute to any of the OSG fabric of services.
+
+
Pools in the OSG
+
+
Each of the more than 20 OSG pools (previously “virtual organizations” or “VOs”)
+consists of computing and data capacity operated via OSG and HTCSS technologies
+and services, as well as any additional resources and services provided by/for
+the pool’s relevant research community.
The OSG Team operates the Open Science Pool (OSPool) for use by research projects
+associated with a US-based academic, government, or non-profit organization,
+and with funding from the National Science Foundation through the NSF PATh
+project (NSF #2030508). Applicable researchers can obtain access to OSPool
+resources via an associated access point operated by their institution or
+collaboration, or via the OSG Portal. Institutions can contribute
+capacity to the OSPool (and other pools) by becoming an OSG Site.
+
+
Other pools within the OSG are operated by/for the research communities they
+serve, often with their own (private) access points, documentation, policies,
+etc., separate from those pertaining to using and contributing to the OSPool.
+Some pool communities or participating organizations provide application-specific
+interfaces or datasets, such that end-users may not even be aware of integration
+with OSG and its services/technologies. Some pools share capacity with one another,
+and organizations can contribute resources to more than one pool. If you’re interested
+in supporting the Open Science Pool, specific projects, or any pool/research
+community, contact us at support@osg-htc.org.
+
+
Research Projects with Accounted Usage Across OSG Pools
+ Our mental model for an OSDF Origin is that of a filesystem, possibly composed of
+ many servers, that is mounted on a host managed via Kubernetes. Both the filesystem
+ and that host is the responsibility of the owner institution. The
+ PATh team has access
+ to that host to instantiate the origin services by deploying a container.
+
+
+ The institution owning the hardware on which the filesystem is implemented is
+ responsible for communicating with PATh via the PATh ticketing system what parts
+ of the filesystem they want to export into the OSDF, and who should have read/write
+ access to it. The owner can change this unilaterally any time, but we request
+ notification ideally a few days prior, if possible.
+
+
+ The PATh services team is responsible for operating the origin service as requested.
+ This includes communicating the absolute path the owners exported filesystems show
+ up in the OSG runtime environment to the institution owning the exported filesystem.
+
+
+ Figure 1 below depicts this architectural arrangement.
+ PATh is responsible for services in red. This figure shows an arrangement where
+ the actual exported filesystem sits behind an institutional firewall, while the
+ Kubernetes host is dual homed, straddling this firewall.
+
+
+ We suggest that the institution owning the filesystem and the Kubernetes host work
+ with the
+ National Research Platform (NRP)
+ project to operate the Kubernetes host. This
+ is by far the least effort way forward for the institution. We are happy to introduce
+ you.
+
+
+ If the institution insists to deploy and operate the origin themselves, we can provide
+ appropriate RPMs. However, we strongly suggest to leave operations of this service to
+ the experts in the PATh operations team.
+
This page lists publications and presentations to which OSG staff contributed
+and that acknowledged the NSF “OSG: Next 5 Years” award (MPS-1148698).
+Also, OSG staff contributed to some of the publications and presentations listed on the
+IRIS-HEP project website.
+
+
Publications
+
+
2020
+
+
+
+
Babik, M., McKee, S., Andrade, P., Bockelman, B. P., Gardner, R., Fajardo Hernandez, E. M.,
+Martelli, E., Vukotic, I., Weitzel, D., & Zvada, M.
+(2020).
+WLCG networks: Update on monitoring and analytics.
+EPJ Web of Conferences, 245, 07053.
+https://doi.org/10.1051/epjconf/202024507053
+
+
+
Bockelman, B., Livny, M., Lin, B., & Prelz, F.
+(2020).
+Principles, technologies, and time: The translational journey of the HTCondor-CE.
+Journal of Computational Science, 101213.
+https://doi.org/10.1016/j.jocs.2020.101213
+
+
+
Dost, J., Mascheroni, M., Bockelman, B., Bryant, L., Cartwright, T., Fajardo, E., Gardner, R.,
+Letts, J., Lin, B., Selmeci, M., Sfiligoi, I., Stephen, J., Weitzel, D., Würthwein, F., & Zhu, H.
+(2020).
+A lightweight door into non-grid sites.
+EPJ Web of Conferences, 245, 07005.
+https://doi.org/10.1051/epjconf/202024507005
+
+
+
Fajardo, E., Weitzel, D., Rynge, M., Zvada, M., Hicks, J., Selmeci, M., … & Sfiligoi, I.,
+“Creating a content delivery network for general science on the internet backbone using XCaches,”
+EPJ Web of Conferences 245, 04041 (2020).
+https://doi.org/10.1051/epjconf/202024504041
+
+
+
E. Fajardo et al,
+“Moving the California distributed CMS XCache from bare metal into containers using Kubernetes,”
+EPJ Web of Conferences 245, 04042 (2020).
+https://doi.org/10.1051/epjconf/202024504042
+
+
+
I. Sfiligoi, J. Graham and F. Wuerthwein,
+“Characterizing network paths in and out of the clouds”,
+EPJ Web of Conferences 245, 07059 (2020).
+https://doi.org/10.1051/epjconf/202024507059
+
+
+
I. Sfiligoi, F. Würthwein, B. Riedel and D. Schultz,
+“Running a Pre-exascale, Geographically Distributed, Multi-cloud Scientific Simulation,”
+In: High Performance Computing. ISC High Performance 2020. Lecture Notes in Computer Science, vol 12151. Springer, Cham. (2020).
+https://doi.org/10.1007/978-3-030-50743-5_2
+
+
+
I. Sfiligoi et al,
+“Demonstrating a Pre-Exascale, Cost-Effective Multi-Cloud Environment for Scientific Computing: Producing a fp32 ExaFLOP hour worth of IceCube simulation data in a single workday,”
+PEARC ‘20: Practice and Experience in Advanced Research Computing, July 2020, Pages 85–90.
+https://doi.org/10.1145/3311790.3396625
+
+
+
I. Sfiligoi, D. Schultz, F. Würthwein and B. Riedel,
+“Pushing the Cloud Limits in Support of IceCube Science,”
+in IEEE Internet Computing, vol. 25, no. 1, pp. 71-75, 1 Jan.-Feb. 2021.
+https://doi.org/10.1109/MIC.2020.3045209
+
+
+
I. Sfiligoi,
+“Demonstrating 100 Gbps in and out of the public Clouds,”
+PEARC ‘20: Practice and Experience in Advanced Research Computing, July 2020, Pages 495–499.
+https://doi.org/10.1145/3311790.3399612
+
+
+
Zhang, Z., Bockelman, B., Weitzel, D., & Swanson, D.
+“Exploring erasure coding techniques for high availability of intermediate data.”
+In 2020 20th IEEE/ACM International Symposium on Cluster, Cloud and Internet Computing (CCGRID) (pp. 865-872). IEEE.
+https://doi.org/10.1109/CCGrid49817.2020.00012
+
+
+
Zhang, Z., Bockelman, B., Weitzel, D., Zhang, X., Vakilzadian, H., & Swanson, D.
+“Trua: Efficient task replication for flexible user-defined availability in scientific grids.”
+In 2020 20th IEEE/ACM International Symposium on Cluster, Cloud and Internet Computing (CCGRID) (pp. 360-369). IEEE.
+https://doi.org/10.1109/CCGrid49817.2020.00-57
+
+
+
+
2019
+
+
+
+
Babik, M., McKee, S., Bockelman, B. P., Hernandez, E. M. F., Martelli, E., Vukotic, I., … & Zvada, M.
+“Improving WLCG Networks Through Monitoring and Analytics,”
+EPJ Web of Conferences (Vol. 214, p. 08006).
+https://doi.org/10.1051/epjconf/201921408006
+
+
+
Bockelman, B., Hanushevsky, A., Keeble, O., Lassnig, M., Millar, P., Weitzel, D., & Yang, W.
+“Bootstrapping a new LHC data transfer ecosystem.”
+In EPJ Web of Conferences (Vol. 214, p. 04045). EDP Sciences
+https://doi.org/10.1051/epjconf/201921404045
+
+
+
Weitzel, D., Zvada, M., Vukotic, I., Gardner, R., Bockelman, B., Rynge, M., … & Selmeci, M.
+“StashCache: a distributed caching federation for the open science grid.”
+In Proceedings of the Practice and Experience in Advanced Research Computing on Rise of the Machines (learning) (pp. 1-7).
+https://doi.org/10.1145/3332186.3332212
+
+
+
+
2018
+
+
+
Zhang, Z., Bockelman, B., Weitzel, D., & Swanson, D.
+“Discovering job preemptions in the open science grid.”
+In Proceedings of the Practice and Experience on Advanced Research Computing (pp. 1-8).
+https://doi.org/10.1145/3219104.3229282
+
+
+
2017
+
+
+
+
Weitzel, D., & Bockelman, B.
+“Contributing opportunistic resources to the grid with HTCondor-CE-Bosco.”
+In Journal of Physics: Conference Series (Vol. 898, No. 9, p. 092026). IOP Publishing.
+https://doi.org/10.1088/1742-6596/898/9/092026
+
+
+
Weitzel, D., Bockelman, B., Dykstra, D., Blomer, J., & Meusel, R.
+“Accessing Data Federations with CVMFS.”
+In Journal of Physics: Conference Series (Vol. 898, No. 6, p. 062044). IOP Publishing.
+https://doi.org/10.1088/1742-6596/898/6/062044
+
+
+
Weitzel, D., Bockelman, B., Brown, D. A., Couvares, P., Würthwein, F., & Hernandez, E. F.
+“Data Access for LIGO on the OSG.”
+In Proceedings of the Practice and Experience in Advanced Research Computing 2017 on Sustainability, Success and Impact (pp. 1-6).
+https://doi.org/10.1145/3093338.3093363
He, C., Weitzel, D., Swanson, D., & Lu, Y.
+Hog: Distributed hadoop mapreduce on the grid.
+In 2012 SC Companion: High Performance Computing, Networking Storage and Analysis (pp. 1276-1283). IEEE.
+https://doi.org/10.1109/SC.Companion.2012.154
Lin, B., Hicks, J., Zvada, M., Weitzel, D., Selmeci, M., & Paschos, P. (2019, November 5).
+Creating a content delivery network for general science on the backbone of the Internet using XCache(s) [Presentation].
+24th International Conference on Computing in High Energy & Nuclear Physics, Adelaide, Australia.
+https://indico.cern.ch/event/773049/contributions/3474435/
+
+
+
McKee, S., Bockelman, B., Gardner, R., Vukotic, I., Babik, M., Weitzel, D., Zvada, M., & Fajardo Hernandez, E. (2019, November 4).
+WLCG networks: Update on monitoring and analytics [Presentation].
+24th International Conference on Computing in High Energy & Nuclear Physics, Adelaide, Australia.
+https://indico.cern.ch/event/773049/contributions/3473823/
Papers, presentations, and other publications that feature research that benefited from the Open Science Pool (OSPool) and Open Science Data Federation (OSDF) resources, services and/or staff expertise should cite the following articles and DOIs:
+
+
+
+
+
Pordes, R., Petravick, D., Kramer, B., Olson, D., Livny, M., Roy, A., Avery, P., Blackburn, K., Wenaus, T., Würthwein, F., Foster, I., Gardner, R., Wilde, M., Blatecky, A., McGee, J., & Quick, R. (2007). The open science grid. J. Phys. Conf. Ser., 78, 012057. https://doi.org/10.1088/1742-6596/78/1/012057
+
+
+
Sfiligoi, I., Bradley, D. C., Holzman, B., Mhashilkar, P., Padhi, S., & Wurthwein, F. (2009). The pilot way to grid resources using glideinWMS. 2009 WRI World Congress on Computer Science and Information Engineering, 2, 428–432. https://doi.org/10.1109/CSIE.2009.950
OSG. (2015). Open Science Data Federation. OSG. https://doi.org/10.21231/0KVZ-VE57
+
+
+
+
+
and include in the text the following acknowledgement:
+
+
+
This research was done using services provided by the OSG Consortium [1,2,3,4], which is supported by the National Science Foundation awards #2030508 and #1836650.
` all receive top and bottom margins. We nuke the top\n// margin for easier control within type scales as it avoids margin collapsing.\n\n%heading {\n margin-top: 0; // 1\n margin-bottom: $headings-margin-bottom;\n font-family: $headings-font-family;\n font-style: $headings-font-style;\n font-weight: $headings-font-weight;\n line-height: $headings-line-height;\n color: $headings-color;\n}\n\nh1 {\n @extend %heading;\n @include font-size($h1-font-size);\n}\n\nh2 {\n @extend %heading;\n @include font-size($h2-font-size);\n}\n\nh3 {\n @extend %heading;\n @include font-size($h3-font-size);\n}\n\nh4 {\n @extend %heading;\n @include font-size($h4-font-size);\n}\n\nh5 {\n @extend %heading;\n @include font-size($h5-font-size);\n}\n\nh6 {\n @extend %heading;\n @include font-size($h6-font-size);\n}\n\n\n// Reset margins on paragraphs\n//\n// Similarly, the top margin on `
`s get reset. However, we also reset the\n// bottom margin to use `rem` units instead of `em`.\n\np {\n margin-top: 0;\n margin-bottom: $paragraph-margin-bottom;\n}\n\n\n// Abbreviations\n//\n// 1. Duplicate behavior to the data-bs-* attribute for our tooltip plugin\n// 2. Add the correct text decoration in Chrome, Edge, Opera, and Safari.\n// 3. Add explicit cursor to indicate changed behavior.\n// 4. Prevent the text-decoration to be skipped.\n\nabbr[title],\nabbr[data-bs-original-title] { // 1\n text-decoration: underline dotted; // 2\n cursor: help; // 3\n text-decoration-skip-ink: none; // 4\n}\n\n\n// Address\n\naddress {\n margin-bottom: 1rem;\n font-style: normal;\n line-height: inherit;\n}\n\n\n// Lists\n\nol,\nul {\n padding-left: 2rem;\n}\n\nol,\nul,\ndl {\n margin-top: 0;\n margin-bottom: 1rem;\n}\n\nol ol,\nul ul,\nol ul,\nul ol {\n margin-bottom: 0;\n}\n\ndt {\n font-weight: $dt-font-weight;\n}\n\n// 1. Undo browser default\n\ndd {\n margin-bottom: .5rem;\n margin-left: 0; // 1\n}\n\n\n// Blockquote\n\nblockquote {\n margin: 0 0 1rem;\n}\n\n\n// Strong\n//\n// Add the correct font weight in Chrome, Edge, and Safari\n\nb,\nstrong {\n font-weight: $font-weight-bolder;\n}\n\n\n// Small\n//\n// Add the correct font size in all browsers\n\nsmall {\n @include font-size($small-font-size);\n}\n\n\n// Mark\n\nmark {\n padding: $mark-padding;\n background-color: $mark-bg;\n}\n\n\n// Sub and Sup\n//\n// Prevent `sub` and `sup` elements from affecting the line height in\n// all browsers.\n\nsub,\nsup {\n position: relative;\n @include font-size($sub-sup-font-size);\n line-height: 0;\n vertical-align: baseline;\n}\n\nsub { bottom: -.25em; }\nsup { top: -.5em; }\n\n\n// Links\n\na {\n color: $link-color;\n text-decoration: $link-decoration;\n\n &:hover {\n color: $link-hover-color;\n text-decoration: $link-hover-decoration;\n }\n}\n\n// And undo these styles for placeholder links/named anchors (without href).\n// It would be more straightforward to just use a[href] in previous block, but that\n// causes specificity issues in many other styles that are too complex to fix.\n// See https://github.com/twbs/bootstrap/issues/19402\n\na:not([href]):not([class]) {\n &,\n &:hover {\n color: inherit;\n text-decoration: none;\n }\n}\n\n\n// Code\n\npre,\ncode,\nkbd,\nsamp {\n font-family: $font-family-code;\n @include font-size(1em); // Correct the odd `em` font sizing in all browsers.\n direction: ltr #{\"/* rtl:ignore */\"};\n unicode-bidi: bidi-override;\n}\n\n// 1. Remove browser default top margin\n// 2. Reset browser default of `1em` to use `rem`s\n// 3. Don't allow content to break outside\n\npre {\n display: block;\n margin-top: 0; // 1\n margin-bottom: 1rem; // 2\n overflow: auto; // 3\n @include font-size($code-font-size);\n color: $pre-color;\n\n // Account for some code outputs that place code tags in pre tags\n code {\n @include font-size(inherit);\n color: inherit;\n word-break: normal;\n }\n}\n\ncode {\n @include font-size($code-font-size);\n color: $code-color;\n word-wrap: break-word;\n\n // Streamline the style when inside anchors to avoid broken underline and more\n a > & {\n color: inherit;\n }\n}\n\nkbd {\n padding: $kbd-padding-y $kbd-padding-x;\n @include font-size($kbd-font-size);\n color: $kbd-color;\n background-color: $kbd-bg;\n @include border-radius($border-radius-sm);\n\n kbd {\n padding: 0;\n @include font-size(1em);\n font-weight: $nested-kbd-font-weight;\n }\n}\n\n\n// Figures\n//\n// Apply a consistent margin strategy (matches our type styles).\n\nfigure {\n margin: 0 0 1rem;\n}\n\n\n// Images and content\n\nimg,\nsvg {\n vertical-align: middle;\n}\n\n\n// Tables\n//\n// Prevent double borders\n\ntable {\n caption-side: bottom;\n border-collapse: collapse;\n}\n\ncaption {\n padding-top: $table-cell-padding-y;\n padding-bottom: $table-cell-padding-y;\n color: $table-caption-color;\n text-align: left;\n}\n\n// 1. Removes font-weight bold by inheriting\n// 2. Matches default `
` alignment by inheriting `text-align`.\n// 3. Fix alignment for Safari\n\nth {\n font-weight: $table-th-font-weight; // 1\n text-align: inherit; // 2\n text-align: -webkit-match-parent; // 3\n}\n\nthead,\ntbody,\ntfoot,\ntr,\ntd,\nth {\n border-color: inherit;\n border-style: solid;\n border-width: 0;\n}\n\n\n// Forms\n//\n// 1. Allow labels to use `margin` for spacing.\n\nlabel {\n display: inline-block; // 1\n}\n\n// Remove the default `border-radius` that macOS Chrome adds.\n// See https://github.com/twbs/bootstrap/issues/24093\n\nbutton {\n // stylelint-disable-next-line property-disallowed-list\n border-radius: 0;\n}\n\n// Explicitly remove focus outline in Chromium when it shouldn't be\n// visible (e.g. as result of mouse click or touch tap). It already\n// should be doing this automatically, but seems to currently be\n// confused and applies its very visible two-tone outline anyway.\n\nbutton:focus:not(:focus-visible) {\n outline: 0;\n}\n\n// 1. Remove the margin in Firefox and Safari\n\ninput,\nbutton,\nselect,\noptgroup,\ntextarea {\n margin: 0; // 1\n font-family: inherit;\n @include font-size(inherit);\n line-height: inherit;\n}\n\n// Remove the inheritance of text transform in Firefox\nbutton,\nselect {\n text-transform: none;\n}\n// Set the cursor for non-`