2015
DOI: 10.1016/j.future.2014.10.001
|View full text |Cite
|
Sign up to set email alerts
|

Exposing HPC and sequential applications as services through the development and deployment of a SaaS cloud

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
14
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
5
1
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 18 publications
(14 citation statements)
references
References 19 publications
0
14
0
Order By: Relevance
“…Building a multinode HPC cluster environment on the clouds used to be difficult, prompting developments of “HPC‐as‐a‐Service” (Baun et al, 2011; Church et al, 2015; Huang, 2014; Section 2.3 of Netto et al, 2017; Wong & Goscinski, 2013), where scientists can access a preconfigured HPC environment, often through a graphical web portal (Calegari et al, 2019), with no need to understand the underlying infrastructure. However, such black‐box service has several drawbacks for research computing: (1) The available software libraries and applications are determined by the HPC service provider and are not easy to extend to custom research code and (2) continuous maintenance by the service provider is required to keep software and hardware up to date.…”
Section: Hpc Workflow On the Aws Cloudmentioning
confidence: 99%
“…Building a multinode HPC cluster environment on the clouds used to be difficult, prompting developments of “HPC‐as‐a‐Service” (Baun et al, 2011; Church et al, 2015; Huang, 2014; Section 2.3 of Netto et al, 2017; Wong & Goscinski, 2013), where scientists can access a preconfigured HPC environment, often through a graphical web portal (Calegari et al, 2019), with no need to understand the underlying infrastructure. However, such black‐box service has several drawbacks for research computing: (1) The available software libraries and applications are determined by the HPC service provider and are not easy to extend to custom research code and (2) continuous maintenance by the service provider is required to keep software and hardware up to date.…”
Section: Hpc Workflow On the Aws Cloudmentioning
confidence: 99%
“…Building a multi-node HPC cluster environment on the clouds used to be difficult, prompting developments of "HPC-as-a-Service" (Baun et al, 2011;Wong and Goscinski, 2013;Huang, 2014;Church et al, 2015;Section 2.3 of Netto et al, 2017), where scientists can access a preconfigured HPC environment, often through a graphical web portal (Calegari et al, 2019), with no need to understand the underlying infrastructure. However, such black-box service has several drawbacks for research computing: (1) the available software libraries and applications are determined by the HPC service provider, and are not easy to extend to custom research code; (2) continuous maintenance by the service provider is required to keep software and hardware up-todate.…”
Section: Multi-node Workflowmentioning
confidence: 99%
“…Having this motivation, they started to develop a framework to translate HPC applications into services. Over the years, the same group [31] presented novel use cases of their framework in the area of genomics. Church and Goscinki [33] also presented a survey on technologies available to help researchers working with mammalian genomics run their experiments.…”
Section: Execution Steeringmentioning
confidence: 99%
“…Management [18,31,33,115,117] Related to proper mapping of multiple activities, possibly including dependencies. Frameworks that have knowledge of cloud pricing models can reduce time and costs for deploying and exposing HPC applications in the cloud.…”
Section: Workflowmentioning
confidence: 99%