Demo Data from EDBT 2026 / reviewers in the wild / expert
Richard E. Harper
dblp:51/2133 · also Rick Harper 0001
· DBLP profile ↗
9ranked-venue papers
0as first author
0since 2021 · last 2020
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Applied, interdisciplinary, general and emerging computing · 4Systems, architecture and hardware · 2Security and privacy · 2
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Embedded and real-time systems · 100% |
Topics — the 1 heaviest of 1, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Embedded and real-time systems › real-time embedded systems
safety-critical real-time systems |
0.0 | 1 | 1994 | Architectural principles for safety-critical real-time applications · Proc. IEEE 1994 |
Methods — techniques the papers use, named apart from their topics
formal verification · 0.0fault tolerance · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2020 | Scheduling Physical Machine Maintenance on Qualified Clouds: What if Migration is not Allowed?abstractIncreasingly, cloud systems host IT services for critical domains such as public health and electric power. Such cloud systems need to be qualified and validated in accordance with compliance policies or government regulations. Configurations of such qualified cloud systems, including VM placement and software deployment, are limited to a small set of configurations which passed the qualification and validation process. So, on practical qualified cloud systems, on-demand VM migration or replication is not allowed. We address the problem of optimally scheduling physical machine maintenance on qualified cloud systems where VM placement cannot change dynamically. Particularly, we try to minimize the number of maintenance waves, and hence, minimize the qualified cloud systems' exposure to loss of high availability. Moreover, we study how the initial placement of service component replicas can help optimize the maintenance schedule while minimize the hardware cost, which is much higher on qualified cloud systems than regular ones. Evaluations in simulations and our real-world qualified cloud system demonstrate the effectiveness of our algorithms and justify our algorithm selection in the real qualified system. In particular, our approach eliminated impacts on service workload and availability during maintenance, while simultaneously largely reduced maintenance time. Long Wang 0003, HariGovind V. Ramasamy, Richard E. Harper |
CLOUD | 3 |
| 2017 | Business Resiliency Framework for Enterprise Workloads in the Cloud
Valentina Salapura, Ruchi Mahindru, Richard E. Harper |
CLOSER | 3 |
| 2016 | Disaster Recovery for Cloud-Hosted Enterprise ApplicationsabstractWe describe disaster protection and recovery of cloud-hosted enterprise applications both at the cloud infrastructure level and at the application level. We explore scenarios which favor one option over the other, and scenarios where a combination of both are required for effective and end-to-end protection. Through case studies grounded in the experience of implementing disaster recovery for IBM's Cloud Managed Services (CMS) platform, we highlight the complexities of protecting enterprise applications on the cloud. For recovery planning and execution, we present a scheduling algorithm that recovers machines hosted on cloud by taking into account application-level logical dependencies and the business criticalities of the applications. Long Wang 0003, Richard E. Harper, Ruchi Mahindru, HariGovind V. Ramasamy |
CLOUD | 2 |
| 2015 | Remote Restart for a High Performance Virtual Machine Recovery in a CloudabstractIn this paper, we present a scalable parallel virtual machine planning and fail over method that enables high availability at a VM level in a data center. The solution is implemented and used in IBM's CMS enterprise private cloud as a high availability feature for efficient fail over in large data centers with a large number of servers, VMs, and a large number of disks. The introduced restart system enables dynamic and at-fail over-time planning and execution, and keeps the recovery time within limits of service level agreement (SLA) allowed time budget. The initial serial fail over time is reduced by a factor of up to 11 for parallel implementation, and by a factor of up to 44 for parallel fail over - parallel storage mapping implementation. As part of our future work, we plan to explore the applicability of this planning and fail over solution for Disaster Recovery. Valentina Salapura, Richard E. Harper |
CLOUD | 2 |
| 2015 | High Performance Virtual Machine Recovery in the Cloud
Valentina Salapura, Richard E. Harper |
CLOSER | 2 |
| 2015 | Experiences with Building Disaster Recovery for Enterprise-Class CloudsabstractThe ability to recover from disasters is an important requirement for many enterprises. With enterprise-class workloads increasingly hosted on the cloud, cloud customers have come to expect disaster recovery (DR) as a necessary feature from cloud platforms. This paper identifies key challenges in providing DR as a service on enterprise cloud platforms, and portrays DR solutions for a managed cloud platform. In particular, we present the reference architecture for DR solutions, and describe our practical experiences in providing a portfolio of DR solutions for the cloud platform. The solutions cover diverse target recovery sites, such as an equivalent cloud site, a dedicated recovery site, and a customer-owned site. From the experiences, we provide insights into and lessons on implementing DR for enterprise-class clouds. Long Wang 0003, HariGovind V. Ramasamy, Richard E. Harper, Mahesh Viswanathan 0002, Edmond Plattier |
DSN | 3 |
| 2008 | A Case for High Availability in a Virtualized Environment (HAVEN)abstractThe cost and operational complexity of traditional High Availability solutions has limited their widespread adoption. Virtualization allows availability properties to be associated with the system architecture, rather than depending on the intrinsic reliability of components. This paper introduces an extensible grammar that classifies the states and transitions of virtual machine images. From this grammar, rules for recovery and High Availability can be created which define how virtualization allows for simplified fault tolerance, making HAVENs accessible to the mainstream user. Erin Farr, Richard E. Harper, Lisa Spainhower, Jimi Xenidis |
ARES | 2 |
| 2001 | Performance and dependability techniques and tools
Boudewijn R. Haverkort, Richard E. Harper |
Perform. Evaluation | 2 |
| 1994 | Architectural principles for safety-critical real-time applicationsabstractThis paper addresses the general area of computer architectures for safety-critical real time applications. The maximum acceptable probability of failure for these applications ranges from about 10/sup /spl minus/4/ to 10/sup /spl minus/10/ per hour depending on whether it is a military or civil application. Typical examples include commercial and military aircraft fly-by-wire, full authority engine control, satellite and launch vehicle control, ground transport vehicles, etc. Realtime response requirements for these applications are also very demanding, with correct control inputs required every 10 to 100 ms, depending on the application. These dual goals of ultrahigh reliability and real-time response necessitate computer systems that are quite different from other dependable systems in their architecture, design and development methodology, validation and verification, and operational philosophy. This paper highlights these differences by describing each of these aspects of safety-critical systems. Architectural principles and techniques to address these unique requirements are described.> Jaynarayan H. Lala, Richard E. Harper |
Proc. IEEE | 2 |