• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
3 4 Use Case Heart Beacon

3 4 Use Case Heart Beacon



National Institute for Standards and Technology NIST Cloud Computing Use case in Wiki

National Institute for Standards and Technology NIST Cloud Computing Use case in Wiki



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    3 4 Use Case Heart Beacon 3 4 Use Case Heart Beacon Document Transcript

    • 3.4 Copy Data Objects Into A Cloud Actors: cloud-subscriber, cloud-provider,transport-agent.Goals: Cloud-subscriber initiates a copy of data objects from cloud-subscribers system toa cloud-providers system. Optionally, protect transferred objects from disclosure.[OPTION: Set Heartbeat data collection interval.][OPTION: Assign cloud-subscriber ORD ID]Assumptions: Assumes the Use Case "Open an Account" for cloud-subscriber on cloud-providers system. The cloud-subscriber has modify access to a named data objectcontainer on the cloud-providers system.Success Scenario 1 (cloud-subscriber-to-network copy, IaaS, PaaS, SaaS): The cloud-subscriber determines a local file for copying to the cloud-providers system. The cloud-subscriber issues a command to the cloud-providers system to copy the object to acontainer on the cloud-providers system. The command may perform both the objectcreation and the data transfer, or the data transfer may be performed with subsequentcommands. The command specifies the location of the local file, the data encoding of thelocal file, and the name of the new object within the container. If the cloud-subscriberrequests protection from disclosure, cryptography is used to protect the objects in transit.The command returns the success status of the operation from the cloud-providerssystem to the cloud-subscriber. The cloud-provider charges the cloud-subscriber for thetransfer according to the terms of the SLA, and begins accruing storage charges.Failure Conditions 1: (1) partial writes and concurrent accesses; (2) size limitations, i.e.,the local file will not fit into the container; (3) network fails repeatedly during transfer;(4) security breaches resulting in stolen data are discovered by cloud-provider; (5) dataloss during transfer; (6) data errors during transfer; (7) cloud-providers system fails tonotify the cloud-subscriber the successful data object transfer to container.Failure Handling 1: For (1), (3), (5), (6), cloud-subscriber retries request; For (4) cloud-provider sends a notice of unauthorized disclosure to the cloud-subscriber; For (2), cloud-subscriber contacts cloud-provider for larger container; For (7), See Use Case "CloseAccount" on failure handling related to notifications from cloud-provider to cloud-subscriber.Additional Assumptions: Data in transit is protected by one of two methods: 1) the cloud-subscriber encrypts data prior to copying it onto the disk drive and also informs thecloud-provider of the decryption key via a secure connection and the cloud-provider thendecrypts the data before copying it into a new object, 2) the cloud-subscriber encrypts thedata prior to copying it onto the disk drive and then, later, performs the decryption usingprocessing resources of the cloud. The cloud-provider will provide disk drives to cloud-subscriber or will accept cloud-subscriber-provided disk drives.
    • Success Scenario 2 (cloud-subscriber-to-transport-agent copy, IaaS, PaaS, SaaS): Thecloud-subscriber prepares a local file for copying to the cloud-providers system. Thecloud-subscriber accesses the cloud-providers documentation and determines thecharacteristics of disk drives that the cloud-provider accepts for data import. The cloud-subscriber uses a cloud-provider-compatible disk and connects the disk drive to thecloud-subscribers computer system and performs a local copy of the local file onto thedisk drive, along with a manifest specifying the encoding of the file, the container inwhich the file should be placed at the cloud-provider, access control metadata about thefile, and the files intended name. The cloud-subscriber uses a transport-agent to deliverthe disk drive to the cloud-provider. On receipt of the disk drive, the cloud-providerconnects the disk drive to the cloud-providers system and performs a local copy of thedata into the container specified by the cloud-subscriber, and either retains or returns thedisk drive according how the drive was provisioned. If the drive is to be re-used by thecloud-provider, the cloud-provider erases all cloud-subscriber data on the disk using asuitable mechanism (see Use Case: "Erase Data Objects In a Cloud"), sends an attestationto the cloud-subscriber that the erase operations have been performed, and charges thecloud-subscriber if they requested special erase operations.Failure Conditions 2: (1) cloud-subscriber sends inappropriate disk that fails to satisfy therequirements of the cloud-provider; (2) data object is in format not supported by cloud-provider; (3) transport-agent loses diskFailure Handling 2: For (1) cloud-provider returns disk to cloud-subscriber; For (2)cloud-provider returns disk to cloud-subscriber and sends message to cloud-subscriberrequesting data is resent in proper file encoding format; (3) transport-agent notifies cloud-subscriber of loss.Credit: This scenario is inspired by the Amazon S3 system.[COMMENT: Heart Beacon: The TCP/IP sub-protocol’s heartbeat function acts as a minipublish-subscribe mechanism that is set to gather state meta data from cloud-subscriber-user at pre-defined intervals by cloud-subscriber-administrator. State meta data istemporarily transferred to files, queues, folders, caches and other temporary data storagesawaiting pick up by transport-agent to the cloud-management-broker that aggregatescloud-subscriber-user state management data into heartbeat state management snapshots(REST Representational State Transfer compliant) for onward replication (copy) to othercloud-subscriber-administrators to effect inter and intra cloud infrastructure changesaccommodating group adhoc spontaneous integration and cloud-subscriber-GROUP(described by Organization Identification ORG ID) affiliation / de-affiliation based oncurrent mission, operation, scenario goal.]
    • USE CASE 3-4: Copy Data Objects Into a Cloud (Heartbeat synchronized)POINT OF CONTACT:Steven J. McGee |SAW Concepts LLC|Simple Wins Concept LLCCEO / Scribe for The Heart_Beacon|PO Box 28 Oceanport NJ| 07757-1354|VOIP: 732.637.4096|Cell:732.768.5440|Web: http://sawconcepts.com|Secure E-Form: https://forms.hush.com/ceo_heartbeaconE:mail: ceo_heartbeacon@hushmail.comhttp://www.slideshare.net/HeartBeaconhttp://www.linkedin.com/in/sawconceptshttp://twitter.com/Heart_Beacon