lots of fixes and add ons
This commit is contained in:
Binary file not shown.
Before Width: | Height: | Size: 396 KiB |
Binary file not shown.
Before Width: | Height: | Size: 279 KiB |
BIN
collections/tech/smartcontract_it/img/smartcontract_iac2.png
Normal file
BIN
collections/tech/smartcontract_it/img/smartcontract_iac2.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 341 KiB |
BIN
collections/tech/smartcontract_it/img/smartcontractit_2.png
Normal file
BIN
collections/tech/smartcontract_it/img/smartcontractit_2.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 444 KiB |
BIN
collections/tech/smartcontract_it/img/smrt_contract_it2.png
Normal file
BIN
collections/tech/smartcontract_it/img/smrt_contract_it2.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 261 KiB |
@@ -6,5 +6,6 @@ IAC = DevOps is a process framework that ensures collaboration between Developme
|
||||
|
||||
In simple terms, DevOps can be defined as an alignment between development and IT operations with better communication and collaboration.
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
|
@@ -1,5 +1,5 @@
|
||||
|
||||
### Smart Contract IT Flow
|
||||
### Smart Contract IT Flow (ZOS3)
|
||||
|
||||
|
||||
The TFChain Blockchain will keep a record of all Entities, Twins, Nodes and Farmers in the TF-Grid network. This makes it easy to integrate the Smart Contract on TFChain as well since we can read from that storage in runtime.
|
||||
|
@@ -32,15 +32,6 @@ If `public_ips` is specified, the contract will reserve the number of public ips
|
||||
|
||||
This contract is registered on the blockchain.
|
||||
|
||||
#### Reliable Message Bus
|
||||
|
||||
The user sends the contractID and workload through the RMB to the destination Node.
|
||||
|
||||
RMB is our Reliable Message Bus, workload definitions don't get registerd on the TFChain but directly send peer2peer, this is more secure and private, the smart contract still controls the overall process.
|
||||
|
||||
The Node reads from the [RMB](https://github.com/threefoldtech/rmb) and sees a deploy command, it reads the contractID and workload definition from the payload.
|
||||
It decodes the workload and reads the contract from chain using the contract ID, the Node will check if the user that created the contract and the deployment hash on the contract is the same as what the Node receives over RMB. If all things check out, the Node deploys the workload.
|
||||
|
||||
#### consumption reports
|
||||
|
||||
The Node periodically sends consumption reports back to the chain for each deployed contract. The chain will compute how much is being used and will charte the user in TFT.
|
||||
|
@@ -1,14 +1,15 @@
|
||||
## Smart Contract for IT
|
||||
|
||||
Ability for developers to launch IT workloads (applications) on the ThreeFold Grid using our TFGrid primitives secured by blockchain concepts.
|
||||

|
||||
|
||||
Ability for developers to launch IT workloads (applications) on a Decentralized Cloud e.g the ThreeFold Grid is using these deployment primitives secured by blockchain concepts.
|
||||
|
||||

|
||||

|
||||
|
||||
Following benefits
|
||||
|
||||
- IT workloads can be deployed 100% deterministic, this means all specific properties of the workloads like necessary files, network bridges, processes, ... are all known at build time, this leads to good security and predictability.
|
||||
- Consensus can be required for deploying a workload on the ThreeFold grid.
|
||||
- Consensus can be required for deploying a workload.
|
||||
- Auditing and full transparancy on what has been deployed by who at what time.
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user