Cloud Era.

Cloud System Model Overview.

César Delgado González
https://youtu.be/UQWxLlS7aJU
 CLOUD COMPUTING: ARTICULATE AND INTEGRATE IT RESOURCES

D EFINITION : C LOUD S YSTEM M ODEL

loud is a bundle of world-wide distributed data-center resources used to allocate any
logic over an automated infrastructure. There are two families of clouds according to
contents, telco cloud and cloud computing.
SYSTEM TYPE: loud computing is an operating system to deploy networks of services
across autonomous administrative domains (with inheritance and visibility challenges
due to distributed nature). Services are designed based on well-tested reusable modules,
and deployed in platforms across domains to supply tools and tracing services to human
activities for internal coordination and external cooperation of social structures.
SYSTEM MODEL: tratified organic distribution as solid foundations for development
ecosystem freely evolving into complex organic infrastructures entirely unaware of
distribution and traffic handling. Applications are boxed into a standardized packaging
(such CORBA interface), then spread across the network of domains through distribution,
deployment and access ecosystems, each one operating independently, but integrated
connecting articulation planes to provide full centralized control over delivery process.
Distributed processes and files abstractions are main delivery mechanisms: many
parameters for unique data-centers deployment logic.
SYSTEM CHALLENGES: ecurity and flexibility challenges can only be solved under an organic
approach: coherent compact units industrially produced working as a distributed
operating system for applications with all connectivity, updating and security issues
solved out of the box configured based on heavily tested profiles in high level
programming language for the infrastructure to apply during delivery process,
concentrating efforts on business logic evolution.

ANATOMY : S TRATIFIED O RGANIC A PPLICATION D ISTRIBUTION

CLOUD COMPUTING TYPE : D ISTRIBUTED S YSTEM CLOUD COMPUTING STYLE : O PERATING S YSTEM

C.D.G.
 SYSTEM MODEL: ARTICULATION AND OPERATION ALGORITHMS . 1

S YSTEM M ODEL O VERVIEW

Articulation Scheme and Operation Infrastructure: ecosystem articulation
model is about values orchestration (life cycle operations) and choreography
(handling and coordination) through exchange of meta-information, while operation
infrastructure model is the required leveraging platforms to run the articulation on
top, with all meta-contents required to integrate heterogeneous resources into
coherent specialized values leveraging platforms.
Same articulation boxes in different types for organic integration, since same
value in different aggregation levels, same articulation algorithms required allowing
automatic integration between types in Russian doll fashion.
C REATIONAL A RCHETYPE –A RTICULATION S CHEME - R OLES , C ONTROL , S IGNALING

A RCHETYPE – O PERATING S YSTEM : V ALUES A RTICULATION

Roles Responsibility and Types
Creation Model: articulate resources to spawn
process and data abstractions. Solaris Kernel
can serve as main reference
(https://www.oracle.com/technetwork/server-
storage/solaris/solaris-internals-137242.html).
Orchestration Process and data abstractions appears in three
Kernel types:
§ Service, Repository: cloud computing
distributed process abstraction.
§ Container, Blueprint: virtual container process
abstraction.
§ Process, File: computer process abstraction.

C.D.G.
 SYSTEM MODEL: ARTICULATION AND OPERATION ALGORITHMS . 2

Execution Model: three stages execution

model, same recipes for all aggregation levels:
§ Authentication and Authorization: identity
management.
Orchestration
§ Launch: encapsulated use of resources.
Value Life Cycle
§ Cooperation: choreography archetypes
applied on three ecosystem types through
middleware: run-times, overlay networks,
bus of events between services.

Management Model: algorithms to organize

Choreography
processes in trees. Node identity is key
Value Tree
outband control required from the articulation
Organization
plane to organize the structure.

Control (Outband) Responsibility

Handling Values: control information required
for the algorithms that create trees of
processes and files (PID, PPID, execution
Monitoring
information).
§ Algorithms: Tree Management.
§ Organic Integration: Solaris Dtrace
Updating Values: data distribution to update
operation infrastructures of each level (services
integration structures, hypervisors, software
Update packaging):
§ Algorithms: Contract, Execute
§ No Organic Integration: operational tissue
within stratum.
Signalling (Inband) Responsibility
Credential: Vector of parameters that
univocally identifies a role within a system,
core value of authentication.
Credential
§ Algorithms: Authentication, Authorization
§ Organic Integration: Synchronize Solaris
credential system.

Command: Vector of parameters that

univocally identifies operations across the
Command system, core value of authorization.
§ Algorithms: Contract, Execute
§ Organic Integration: SSH Shell

Signal: internal coordination across operation

infrastructures (bus, overlay, memory i/o).
§ Algorithms: Read, Write
Signal
§ No Organic Integration: operational tissue
within stratum.

C.D.G.
 SYSTEM MODEL: ARTICULATION AND OPERATION ALGORITHMS . 3

Cloud Type SW Creation SW Ecosystem

Continuos Delivery & Federation of Logical Domains
Continuos Integration Run-Time

Articulation:
SW Creation
Needs
Process: Service File: Repository Signal: Bus of Events

Operation:
HW
Infrastructure
Element: Interface Connectivity: Real Time

Data-Center SW Creation SW Ecosystem

Type Microservices Architectures Run- Desktop of Cluster Applications
Times

Articulation:
SW Creation
Needs
Process: Container File: Blueprint Signal: Overlay

Operation:
HW
Infrastructure
Element: Virtualized Device Connectivity:
Software Defined Network

Computer SW Creation
Computing Languages Run-Times SW Ecosystem
Type Desktop of Monolithic Applications

Articulation:
SW Creation
Needs
Process: Process File: File Signal: Memory

Operation:
HW
Infrastructure
Element: Device Connectivity: Buses

C.D.G.
 SYSTEM MODEL: ARTICULATION AND OPERATION ALGORITHMS . 4

T YPE – S ERVICES O PERATION S TRATUM – L AYERS , I NTERFACES , P ROTOCOLS

Layer 1 – Domains Integration: start connectivity infrastructure between domains

(RTP switching and datagram networks as federation of session headers providing
distributed data session handling with value added services capabilities, enhanced traffic
engineering capabilities and user experience over centralized data session handling at
application level).
Layer 2 – Domains Articulation: start outband control (monitoring, update) and
inband coordination platforms (commands, credentials, signals) between domains that
allow system articulation.
T YPE - D ISTRIBUTED S YSTEM : L EVERAGING R OLES I NTEGRATION
Value Type
Service: distributed process across domains.
§ Contract (API): Accounting, Software Development Cycle, Big
Data, Artificial Intelligence…
Process § Inheritance Style: Autonomous Systems
§ Visibility Style: Hierarchical Tree.
§ Shape (implementation technologies): Jekins (software
releasing), Horton Works (big data), SAP(accounting), etc.
Repository: distributed file system across domains.
§ Contract (API): Version Control, Database, Cache, etc
§ Inheritance Style: Autonomous Systems.
File
§ Visibility Style: Hierarchical Tree.
§ Shape (technologies): Github, ClearCase –software versioning-,
MySQL, etc.
C.D.G.
 SYSTEM MODEL: ARTICULATION AND OPERATION ALGORITHMS . 5

Control Outband Type

Service Labeling: services handling in

Monitoring tree structures (SID, PSID, execution
information)

Service integration structures:

Update
interfaces, middleware, contracts.

Signalling Inband Type

Home-Visitor: distribution of credential

Credential
across the tree of administrative domains.

§ Service Contract: public declaration

of responsibilities.
Command
§ Service Remote Command:
execution of instructions.

Event: signaling between services to

Signal coordinate operations across distributed
domains.

Operation Interface
Connectivity Box: uniforms for values integration into leverage
Leverage platforms (such Corba interfaces to integrate applications into
the distribution system).

Encapsulated Bean: uniforms for signalling elements

Coordinate
(credential, command, signal) to exchange.

Adapter Relationship: {Service -> Data-Center} Types

Credential Aggregation: service level credential should be
Credential
mapped into a bundle of data-center credentials that allows
Synchro.
deploying successfully services according to security standards.
DevOps: operation service level instruction should be compiled
from logical administrative domain into a set of data-center
Command
specific operations (service, microservices and containerization)
Compiler
and SDN network policies, solving security in design, deployment
and access levels automatically.

C.D.G.
 SYSTEM MODEL: ARTICULATION AND OPERATION ALGORITHMS . 6

T YPE - L AYERS : C ONTENT L EVERAGING P LATFORMS

Administrative Domain Tree: tree of autonomous systems,
each one organized in zones.
§ Protocol: Content Based Routing
§ Inheritance Style: Autonomous Systems
§ Visibility Style: Tree of Administrative Zones.

PRODUCTION Signalling Distribution Lines: operation infrastructure for

Domains archetypical execution model (PADRES Project:
http://www.msrg.org/projects/padres/vision.php).
Art. Platform Inheritance Style Visibility Style
Event Bus § Publish/Subscribe
§ Request/Reply
§ Point to Point
§ Orchestration
Command Federation § Area Aggregation
Credential Tree § Home-Visitor

Control Distribution Lines: operation infrastructure for

archetypical management model.
Art. Platform Inheritance Style Visibility Style
Update Tree § Master-Slave
Node ID Tree § Master-Slave
Domain Integration through Federations: coordinated content
DISTRIBUTION delivery.
Integration § Protocol: RTP Circuits, Datagram
§ Inheritance Style: Federated Areas
§ Visibility Style: Core of Session Headers (separation between
traffic and control headers to dynamically scale upon demand,
adding distributed data sessions handling over services
headers, superior to any centralized sessions at application
level approach).
T YPE - L AYERS : C ONTENT A RTICULATION P LATFORMS
Central Monitorization and Control:
CONTROL § Value Control: implementing creational archetype.
Creational Value Inheritance Style Visibility Style
Archetype Service Hierarchical Tree § Area aggregation
Repository Hierarchical Tree § Area aggregation

§ Leverage Control: operation infrastructure monitor.

Platform Inheritance Style Visibility Style
Domain Hierarchical Tree § Area aggregation
Integration Federation § Area aggregation
INTERFACE
Organic integration Encapsulation and Organic Integration: ecosystem
encapsulation to organically control and integrate as autonomous
role.
Platform Inheritance Style Visibility Style
Public Federation § Area aggregation
Private Hierarchical Tree § Area aggregation

C.D.G.
INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 7

C.D.G.
 INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 8

STRATEGIES: INFRASTRUCTURE DESIGN MODEL

STANDARDS: INFRASTRUCTURE MANUFACTURE MODEL

C.D.G.
 INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 9

MANUFACTURE MODEL:
ALGORITHM TO ORGANIZE STANDARDS
ach shape of the system is a combination of strategies to balance design options
implemented through different bundles of standards from the integration framework.
Below the recursive algorithm to organize standards of the integration framework:

Content to Operate: build stable secure

components capable to fulfill its role in his context as
a composition of basic elements. Each element is the
implementation of integration and design patterns in
DESIGN
many different ways.
Meta-Content to Articulate: integrate and
encapsulate all inner design into a coherent whole,
providing external control and internal coordination
CONTROL services.

C.D.G.
 INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 10

VALUES OPERATION
O RCHESTRATION : V ALUE L IFE C YCLE

Ø Cloud Identity: Public Domain

Public
Ø Cloud Integration: Public API, Credential Adapter
Ø Stratum Identity: Domain and Zones Schemes Creation
ORGANIC Private
Ø Stratum Integration: Services Shell, Credential Cache.
INTEGRATION
Creation, Ø Service Creation & ID Ø Repository Creation & ID
Execution, Ø Credential System Ø Credential System
Handling Ø Middleware Mailboxes
Creation & ID
Ø RTP Circuits Creation & ID Ø CDN Domain Creation & ID
CREATIONAL Leverage Ø SIP Domain Creation & ID Ø Load Balancers Features
ARCHETYPE Infrastructure Ø SIP Session Features Provisioning
Provisioning

Service Repository
VALUES

Ø Data-Center Identity: Data-Center IP

Public
Ø Data-Center Integration: Public API, Credential Adapter
Ø Stratum Identity: IP Schemes Creation
ORGANIC Private
Ø Stratum Integration: Data-Center Shell, Credential Cache
INTEGRATION
Creation, Ø Container Creation & ID Ø Blueprint Creation & ID
Execution, Ø Credential System Ø Credential System
Handling
Ø Software Defined Nodes Ø Software Defined Nodes
CREATIONAL Leverage
(Hypervisors, etc.) (Storage, etc.)
ARCHETYPEE Infrastructure
Ø Software Defined Network Ø Software Defined Network

Container Blueprint
VALUE
C.D.G.
 INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 11

Ø Cloud Identity: Public Domain Registry (DNS)

Public
Ø Cloud Integration: Dtrace Adapter, Updating Adapter
Ø Stratum Identity: Domain and Zones Handling & Monitor
ORGANIC Private
Ø Stratum Integration: Dtrace Monitoring, Updating Repo.
INTEGRATION
Creation, Ø Services Monitoring Ø Repositories Monitoring
Execution, Ø Services Cooperation Ø Repositories Distribution
Handling Schemes Appliance Schemes Appliance
Ø RTP Circuits Traffic Ø Datagram Traffic
CREATIONAL
Leverage Ø Middleware Traffic Ø Contracts Traffic
ARCHETYPE Infrastructure Ø SIP Domain Handling and Ø CDN Domain Handling and
Monitoring Monitoring

Service Repository
VALUES
Public Ø Data-Center Identity: Public Domain Registry (DNS)
Ø Data-Center Integration: Dtrace Adapter, Update Adapter

Ø Stratum Identity: Geographical Zones Handling & Monitor

ORGANIC Private
Ø Stratum Integration: Dtrace Monitoring, Updating Cache
INTEGRATION
Ø Container Monitor Ø Blueprint Storage Handling &
Creation,
Ø Container Cooperation Monitor
Execution,
Schemes Appliance and Ø Blueprint Distribution
Handling
Monitor (Cloud Patterns) Schemes Appliance & Monitor

CREATIONAL Leverage Ø Hypervisors Handle & Ø Cache Traffic Monitor

ARCHETYPE Infrastructure Monitor Ø Command Traffic
Ø Overlay Traffic

Container Blueprint
VALUE
C HOREOGRAPHY : V ALUES H ANDLING & C OORDINATION
VALUES ARTICULATION
C.D.G.
 INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 12

LEVERAGE ARTICULATION
DISTRIBUTED ROLES CONTROL

Process File
CONTENT
Administrative Ø Service Credential Ø Repository Credential
Domains Platform Ø Service Contracts Ø Repository Contracts
Ø Middleware Ø Repository Connectivity
Ø Service Monitor Ø Repository Monitor

OPERATION
Federated Delivery SIP Domains CDN Management
Platform Management Network Network

Node Network
DATA-CENTER
Virtualization Ø Container and Ø Overlay Management
Platform Hypervisors Control Network
Network Ø Security Policies
Federated Ø Data-Center Ø Underlay Management
Autonomous Management Network Network
Systems Platform Ø Security Policies
OPERATION
Control

C.D.G.
 INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 13

Process File
CONTENT
Administrative Ø Service Deployment Ø Distributed Repositories
Domains Platform Deployment
Federated Delivery Ø SIP Domains and Ø Content Delivery
OPERATION
Platform RTP Deployment Network Deployment

Node Network
DATA-CENTER
Virtualization Ø Hypervisors and Overlay Deployment
Platform Container Ø Container Connectivity
Deployment Ø Network Virtualized
Devices
Federated Ø Data-Center Underlay Network
OPERATION Autonomous Deployment Ø IP Standards
Systems Platform Ø Optical Standards

DISTRIBUTED ROLES DESIGN - RECURSIVITY ENTRY

LEVERAGE OPERATION
C.D.G.
 INTEGRATION FRAMEWORK: IMPLEMENTATION STANDARDS . 14

ORCHESTRATION
1. Bernhard Neumair, Integrated Management of Networked Systems
Sebastian Abeck, https://www.amazon.es/Integrated-Management-
Heinz-Gerd Hegering Networked-Systems-Architectures/dp/1558605711
2. Dimitri Stiliadis Nuage Networks Policies System:
https://youtu.be/hcZHkYhE1_M?t=1955
3. Dimitri Stiliadis Overlay and Underlay Design:
http://www.nuagenetworks.net/blog/network-
virtualization-overlay-and-underlay-design/
4. Red Hat Overlord Services Monitorization:
https://www.projectoverlord.io/
5. Diogo R. Ferreira Enterprise Systems Integration: A Process-Oriented
Approach:
https://www.amazon.es/Enterprise-Systems-
Integration-Process-Oriented-
Approach/dp/3642407951

CHOREOGRAPHY
ROLES CONTROL
6. Hans-Arno Jacobsen PADRES, Publish/Subscribe Applied to Distributed
Resource Scheduling
http://www.msrg.org/projects/padres/vision.php
7. Russell Bryant OpenStack Operation Standards:
http://shop.oreilly.com/product/0636920032625.do
8. Common Architecture Integration Strategies in a single Delivery Layer:
for Real Time Services https://www.business.att.com/content/whitepaper/
(CARTS, AT&T) w_ATT_CARTS.pdf
9. Thomas Erl Services Messaging (Apache Kafka, Rabbit MQ,
Apache ActiveMQ, etc.):
http://serviceorientation.com/whatissoa/about_web
_services
10. Thomas Erl Services, micro-services and containerization:
https://www.arcitura.com/books/
11. SIP Sense SIP Network components:
https://youtu.be/uTU6-gDQL_E?t=458
12. Nir Simionovich voIP Control Headers:
https://youtu.be/Sk3nuKMB7o8?t=308
13. Nir Simionovich Federated voIP: https://youtu.be/0pqhRHQ-uQ0
14. Nir Simionovich The Challenge of Augmented RTP, Monitorization
Tools: https://youtu.be/mT0jhn75x4c?t=1074
15. Gregor Hohpe Enterprise Integration Patterns,
https://www.enterpriseintegrationpatterns.com/
16. Sun Microsystems Constellation System (CLUMEQ example):
https://youtu.be/1qyCH2G8epo

ROLES DEPLOYMENT

C.D.G.