Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties


Project TitleSLA Self-Assessment with Hyperledger Fabric
Status

Blue
Status
colour
titlePending TSC Reviewrecommended for approval

Difficulty

 

Status
colourYellow
titleMedium


Description 

Why Service Level Agreements (SLAs)?

Service Level Agreements or SLAs define the way that providers, e.g. Public Cloud Infrastructure As A Service providers, are offering their services to their clientele. An SLA is defined in a form of a contract with specific metric values that must be met by the provider or else an SLA Violation of its contractual terms occurs. Although it is straightforward to compute SLA metric values when needed, there is no holistic system that fairly calculates the respective metrics under a well-defined or pre-agreed mechanism; each provider defines their own methods of metrics computation without transparency to their clientele. The objective of this project is to address the existing gray areas of the SLA monitoring process by bringing (i.) transparency to the SLA monitoring for both the client and the provider and (ii.) privacy to the SLA computations through the result framework.

...

The overall project plan is divided into three phases while the mentee is properly guided by their mentor in each phase. In the first phase, the development of the Fabric chaincodes for the SLA operations and their integration points occurs in the context of an entire decentralized architecture. In the second phase, building on the required interactions with on- and off-chain data is addressed with details as understood and designed on the previous phase. Finally, the holistic approach is developed in the third phase, where permissioned ecosystem is formed end-to-end and its related documentation is produced.

Additional Information

Learning Objectives

The selected Mentee will benefit from the following learning objectives:

  1. Good exposure to the significance of the natural coupling between open source capabilities and immediate industry needs
  2. Clarifying the demand for SLAs to be established and maintained in a decentralized way
  3. Enhance the knowledge related to trusted computation importance in blockchain environments
  4. Deeper understanding of Hyperledger Fabric concepts
  5. Hands-on experience with open source software development, particularly:
    1. Hyperledger Fabric network
    2. Fabric Private Chaincode
    3. Systems integration and interoperability
    4. Managing on- and off-chain data

Expected Outcome

The expected outcomes of the project would include:

...