Task #1992

Project WP #654: WP6 - Supporting Blue Economy: VREs Development [Months: 1-30]

Project Task #656: T6.2 Strategic Investment analysis and Scientific Planning/Alerting VRE [Months: 1-30]

Project Activity #1633: Blue Economy VRE#2 Software Implementation, Integration and Deployment (Stage 2)

Task #6101: Geospatial Analytics & Alerting Platform Implementation (Stage 2)

Logical Layer Broker & Manager development

Added by Gerasimos Farantatos over 3 years ago. Updated over 2 years ago.

Status:ClosedStart date:Jan 18, 2016
Priority:NormalDue date:Dec 31, 2016
Assignee:Nikolas Laskaris% Done:


Duration: 250


In the context of the platform, a logical layer is simply a uniquely identifiable set of physical layer replicas. The operations upon logical layers are performed by a pair of components, namely the Logical Layer Broker and the Logical Layer Manager.

The Logical Layer Broker accepts a layer unique identifier and locates and returns the corresponding physical layer. Since there are in general more than one physical layer replicas, the broker will be able to perform load balancing according to a configurable policy.

The Logical Layer Manager is tasked with update operations upon logical layers, namely delete and insert. Its main task is to maintain the number of replicas at the configured levels and to keep inconsistencies to a minimum.

In order to access and manage the layer replicas, both components access a common logical layer catalog which retains the location of each replica and is updated when specific events occur in the cluster, e.g. a node went down, a new logical layer is created or a logical layer is deleted.


Task #1993: Logical Layer Broker developmentClosedNikolas Laskaris

Task #1994: Logical Layer Manager DevelopmentClosedNikolas Laskaris


#1 Updated by George Kakaletris almost 3 years ago

  • Due date set to Sep 30, 2016

due to changes in a related task

#2 Updated by George Kakaletris almost 3 years ago

  • Assignee changed from Gerasimos Farantatos to Nikolas Laskaris

#3 Updated by George Kakaletris almost 3 years ago

  • Due date changed from Sep 30, 2016 to Dec 31, 2016

due to changes in a related task

#4 Updated by Dimitris Katris over 2 years ago

  • Parent task changed from #1991 to #6101

#5 Updated by Nikolas Laskaris over 2 years ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF