ADA Distributed Systems Annex 2009 Filminas

Introduction
A simple ”zeitgeist” application

Social networking made easy
Distributed Ada
Implementation of the DSA
Conclusion
The Ada Distributed Systems Annex

FOSDEM 2009
Thomas Quinot
AdaCore
Brussels, 2009-02-07
The GNAT Pro Company
Thomas Quinot The Ada Distributed Systems Annex

Introduction
Distributed Ada
Conclusion
1 Introduction
2 A simple ”zeitgeist” application
3 Social networking made easy
4 Distributed Ada
5 Implementation of the DSA
6 Conclusion

Introduction
Distributed Ada
Conclusion
Outline
1 Introduction
4 Distributed Ada
6 Conclusion

Introduction
Distributed Ada
Conclusion
Motivation for distribution
Many aspects of software engineering require, or can benefit from, distributed

technology:
Load balancing
Fault tolerance
Interconnection between multiple agents
...

Introduction
Distributed Ada
Conclusion
Distribution models
A distributed application design relies on the abstractions of a distribution

model to express the interactions between application components:
Message passing
Non-structured
Remote subprogram calls
Based on natural abstraction boundaries (subprograms)
Distributed objects
Extend RPC to object-oriented design
(+ distributed shared memory)

Introduction
Distributed Ada
Conclusion
Distribution models and monolithic progamming models
Paralllel between distribution models and monolithic programming models:
GOTO Message passing

↓ ↓
Structured RPC
↓ ↓
Object-oriented Distributed objects

Introduction
Distributed Ada
Conclusion
Distributed programming
Communication APIs → BSD sockets

Cumbersome, error-prone
Specialized distribution APIs → MPI, CORBA
Intrusive, steep learning curve, freeze distribution boundaries
Distributed language → Ada DSA, Java RMI, Modula 3
Seamless integration in application, extend languages’
abstraction to support distribution.
Given a distribution model and an implementation (middleware), how to handle
interoperability with other distributed components?

Introduction
Distributed Ada
Conclusion
Distribution in Ada 95/2005
Ada has built-in features for contract-based programming

Natural extension to distribution
Comparable to Modula/3 Network Objects, Java Remote Method
Invocation.

Introduction
Distributed Ada
Conclusion
Outline
1 Introduction
4 Distributed Ada
6 Conclusion

Introduction
Distributed Ada
Conclusion
Service definition
package Z e i t g e i s t i s
type News Item i s
Author , Message : U n b o u n d e d S t r i n g ;
end News Item ;
type N e w s I t e m s i s a r r a y ( P o s i t i v e range <>)
o f News Item ;
p r o c e d u r e P o s t ( I t e m : News Item ) ;
f u n c t i o n Whats Up r e t u r n N e w s I t e m s ;
end Z e i t g e i s t ;

Introduction
Distributed Ada
Conclusion
Making it remote
We want to make calls to the service from another application

pragma R e m o t e C a l l I n t e r f a c e ;
type News Item i s
Author , Message : U n b o u n d e d S t r i n g ;
end News Item ;
o f News Item ;
f u n c t i o n Whats Up r e t u r n N e w s I t e m s ;
end Z e i t g e i s t ;

Introduction
Distributed Ada
Conclusion
Building the complete application
Once distribution pragmas have been added to identify possible distribution

boundaries, the user can:
build a monolithic application as usual
split units according to distribution boundaries ⇒ partitioning
The partitioning process is implementation defined.

Introduction
Distributed Ada
Conclusion
Partitioning configuration for a minimal application
configuration Dist App i s

pragma S t a r t e r ( None ) ;
−− U s e r s t a r t s e a c h p a r t i t i o n m a n u a l l y
S e r v e r P : P a r t i t i o n := ( Z e i t g e i s t ) ;
−− RCI p a c k a g e Z e i t g e i s t i s on p a r t i t i o n S e r v e r P
C l i e n t P : P a r t i t i o n := ( ) ;
−− P a r t i t i o n C l i e n t P h a s no RCI p a c k a g e s
f o r C l i e n t P ’ T e r m i n a t i o n use L o c a l T e r m i n a t i o n ;
−− No g l o b a l t e r m i n a t i o n
procedure Server Main i s i n ServerP ;

−− Main s u b p r o g r a m o f m a s t e r p a r t i t i o n
procedure C l i e n t M a i n ;
f o r C l i e n t P ’ Main use C l i e n t M a i n ;
−− Main s u b p r o g r a m o f s l a v e p a r t i t i o n
end D i s t A p p ; The GNAT Pro Company

Introduction
Distributed Ada
Conclusion
Outline
1 Introduction
4 Distributed Ada
6 Conclusion

Introduction
Distributed Ada
Conclusion
Components
You have a shared bulletin board — now what if you want direct messaging
between users?
package C h a t U s e r s i s
type U s e r i s a b s t r a c t tagged l i m i t e d p r i v a t e ;
type U s e r R e f i s a c c e s s a l l User ’ C l a s s ;
f u n c t i o n Name (Who : U s e r ) r e t u r n S t r i n g ;
p r o c e d u r e Say
( From : String ;
To Whom : U s e r ;
What : String );
end C h a t U s e r s ;

Introduction
Distributed Ada
Conclusion
Communicating components
OO provides flexible object interactions — now let’s extend these across

partition boundaries!
package C h a t U s e r s i s
pragma Remote Types ;
type U s e r i s a b s t r a c t tagged l i m i t e d p r i v a t e ;
type U s e r R e f i s a c c e s s a l l User ’ C l a s s ;
−− Remote A c c e s s t o C l a s s −Wide t y p e
f u n c t i o n Name (Who : U s e r ) r e t u r n S t r i n g ;
p r o c e d u r e Say
( From : String ;
To Whom : U s e r ;
What : String );
end C h a t U s e r s ;
A Remote Access to Class-Wide type may reference remote objects.

Introduction
Distributed Ada
Conclusion
Getting in touch
Each partition creates objects, and makes RACW that point to these object.
Now how do you initially obtain these pointers to remote objects?
wi th C h a t U s e r s ; use C h a t U s e r s ;
pragma R e m o t e C a l l I n t e r f a c e ;
type News Item i s
Author : User Ref ;
Message : U n b o u n d e d S t r i n g ;
end News Item ;
o f News Item ;
f u n c t i o n Whats Up r e t u r n N e w s I t e m s ; end Z e i t g e i s t ;
RCIs allow initially passing around RACW values.

Introduction
Distributed Ada
Conclusion
Outline
1 Introduction
4 Distributed Ada
6 Conclusion

Introduction
Distributed Ada
Conclusion
Unit categories and categorization pragmas
Pure
Base data types declarations (no named access types, no
indirection)
No internal state
Remote Types
Complex data types (possibly encapsulating hidden access
types), remote access types
Remote Call Interface
Remotely callable subprograms
Semantic dependency (with) constraints:
Pure ← Remote Types ← Remote Call Interface ← non-categorized

Introduction
Distributed Ada
Conclusion
Remote subprograms
Formal parameters must “support external streaming”:
no access types
no limited types
... unless stream attributes are specified.
package S t r e a m a b l e L i s t s i s
type L i s t i s p r i v a t e ;
p r o c e d u r e My Read
( S : a c c e s s Ada . S t r e a m s . R o o t S t r e a m T y p e ’ C l a s s ;
V : out L i s t ) ;
p r o c e d u r e My Write
( S : a c c e s s Ada . S t r e a m s . R o o t S t r e a m T y p e ’ C l a s s ;
V : List );
f o r L i s t ’ Read use My Read ;
f o r L i s t ’ W r i t e use My Write ;
private
...
end S t r e a m a b l e L i s t s ; The GNAT Pro Company

Introduction
Distributed Ada
Conclusion
Remote access types
Access types declared in the visible part of an RT or RCI unit.

Remote access to subprogram types may designate remote subprograms
(subprograms declared in the visible part of a remote call
interface unit).
Remote access to class-wide types may designate “suitable” tagged types
(limited private types declared in the visible part of a declared
pure or remote types unit).

Introduction
Distributed Ada
Conclusion
Behind the scene
For each remotely callable subprogram (RCI subprogram, primitive operation of

RACW type), the compiler generates:
Calling stubs (client side)
Marshall arguments, make remote call, unmarshall result;
Receiving stubs (server side)
Unmarshall arguments, make upcall to application code,
marshall result (or exception).
Generated code makes calls to supporting routines provided by the PCS.

Introduction
Distributed Ada
Conclusion
Outline
1 Introduction
4 Distributed Ada
6 Conclusion

Introduction
Distributed Ada
Conclusion
Anatomy of a DSA implementation
Code generator
Produces client and server stubs. Part of the compiler.
Partitioning tool
Assigns units to partitions and builds executables.
Partition communication subsystem (PCS)
Runtime library called by the generated code, providing the
communication services.

Introduction
Distributed Ada
Conclusion
DSA support in GNAT
DSA code generation is an integral part of the GNAT compiler.

PCS + partitioning tool (gnatdist) bundles:
GLADE (GARLIC PCS) Legacy implementation using an ad hoc,
specific protocol
PolyORB/DSA (PolyORB PCS) Based on reusable polymorphic middleware,
can use a variety of standard protocols (GIOP, SOAP...) to
allow interoperability with other distribution models such as
CORBA.
Available from http://libre.adacore.com/.

Commercial support enquiries to sales@adacore.com.

Introduction
Distributed Ada
Conclusion
PolyORB: a polymorphic, reusable middleware architecture
A generic, configurable, interoperable middleware for critical distributed

applications.
Highly decoupled, modular architecture, customizable according to
appplication and environment requirements, providing maximal
interoperability across distribution models.
Formally proven middleware kernel: the µBroker.
Application components
11111111111
00000000000
00000000000
11111111111 00000000000
11111111111
00000000000
11111111111
00000000000
11111111111
00000
11111 00000000000
11111111111
00000
11111
Applicative personalities
00000000000
11111111111
00000
11111 00000000000
11111111111
00000
11111
00000
11111 00000
11111
00000
11111 00000
11111
Neutral representation
Neutral layer
of requests and data
00000
11111 00000
11111
00000
11111 00000
11111
00000
11111
00000000000
11111111111 00000
11111
00000000000
11111111111
00000000000
11111111111 00000000000
11111111111
Protocol personalities
00000000000
11111111111 00000000000
11111111111
Remote middleware

Introduction
Distributed Ada
Conclusion
Outline
1 Introduction
4 Distributed Ada
6 Conclusion

Introduction
Distributed Ada
Conclusion
Ada DSA summary
DSA (Annex E) incorporates distribution within the language, preserving

the language’s abstraction and strong typing features.
No new API, natural extension of contract-based programming paradigm.
PolyORB/DSA allows interoperability with CORBA, SOAP systems.
GNAT implementation freely available from
http://libre.adacore.com/.
For commercial support contact sales@adacore.com.

Introduction
Distributed Ada
Conclusion
Questions?

ADA Distributed Systems Annex 2009 Filminas

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ADA Distributed Systems Annex 2009 Filminas

Uploaded by

Copyright:

Available Formats

Introduction

A simple ”zeitgeist” application

The Ada Distributed Systems Annex

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

2 A simple ”zeitgeist” application

3 Social networking made easy

5 Implementation of the DSA

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

2 A simple ”zeitgeist” application

3 Social networking made easy

5 Implementation of the DSA

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

Motivation for distribution

Many aspects of software engineering require, or can benefit from, distributed

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

A distributed application design relies on the abstractions of a distribution

(+ distributed shared memory)

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

Distribution models and monolithic progamming models

Paralllel between distribution models and monolithic programming models:

GOTO Message passing

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

Communication APIs → BSD sockets

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

Distribution in Ada 95/2005

Ada has built-in features for contract-based programming

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

2 A simple ”zeitgeist” application

3 Social networking made easy

5 Implementation of the DSA

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

We want to make calls to the service from another application

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

Building the complete application

Once distribution pragmas have been added to identify possible distribution

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

Partitioning configuration for a minimal application

configuration Dist App i s

procedure Server Main i s i n ServerP ;

Thomas Quinot The Ada Distributed Systems Annex

2 A simple ”zeitgeist” application

3 Social networking made easy

5 Implementation of the DSA

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

The GNAT Pro Company

Thomas Quinot The Ada Distributed Systems Annex

OO provides flexible object interactions — now let’s extend these across

Thomas Quinot The Ada Distributed Systems Annex

Thomas Quinot The Ada Distributed Systems Annex