Skip to content Skip to navigation

JIRA Issue

[#XCI-435] Identify a reliability wrapper for OpenStack instance creation requests

[XCI-435] Identify a reliability wrapper for OpenStack instance creation requests Created: 08/22/2018  Updated: 08/22/2018

Status: Proposed
Project: XSEDE Cyberinfrastructure Integration
Component/s: None
Fix Version/s: None

Type: XCI Documentation Priority: Major
Reporter: Lee Liming Assignee: Unassigned
Resolution: Unresolved Votes: 0

XSEDE Priority: -
Public activity link: https://software.xsede.org/display/xci-435
Devel Repository: https://software.xsede.org/svn/xci/activities/xci-435/trunk/
Use Cases:
IAAS-9: Reliably acquire and manage hosted computer systems and/or storage volumes
Effort and Costs:
Staff Name (Lastname, Firstname) Effort (person weeks) Roles or Contributions Status
<Activity Lead Name – Last, First> 6 six weeks of effort to lead and implement the activity (required) none
<User Doc Drafter – Last, First> 0.2 one day of effort to draft user documentation (required ) none
TBD (tester) 1 one week of effort to test the software none
... ... .. none
Deliverables:
Due by Activity Deliverable
DSR Design document*
TRR Implemented Software Capability
TRR Other type of deliverable
TRR Deployment plan*
TRR Test plan*
TRR User documentation*
TRR (post) TRR Baseline* (Shava)
Deployment Deployment Baseline* (Shava)
Deployment Test Report* (Shava)
  • Click on "Deliverables" tab for URL.
Lead Tester: Shava Smallen

 Description   

Use case IAAS-9 requires an API that automatically recovers from common exceptions. The desired API, "automatically resolves common issues and only returns control to the calling application when the request succeeds or cannot reasonably be satisfied without human intervention."

We are currently not aware of a convenience wrapper for OpenStack Nova that provides this level of fault recovery. People who currently use the Openstack Nova API with XSEDE cloud resources (JetStream, Bridges, and Comet) are working around this by coding their own fault recovery in their applications, as described in IAAS-08.

XSEDE should not develop a convenience wrapper, but if one exists and we are made aware of it, we should document it, support it, and recommend it to XSEDE users.