- All Superinterfaces:
org.gcube.informationsystem.base.reference.Element, org.gcube.informationsystem.model.reference.entities.Entity, org.gcube.informationsystem.base.reference.entities.EntityElement, org.gcube.informationsystem.model.reference.ERElement, GCubeResource, org.gcube.informationsystem.base.reference.IdentifiableElement, org.gcube.informationsystem.model.reference.ModelElement, org.gcube.informationsystem.model.reference.entities.Resource, Serializable, Service
- All Known Implementing Classes:
HostingNodeImpl
@ResourceSchema(facets={@ResourceSchemaEntry(relation=IsIdentifiedBy.class,facet=NetworkingFacet.class,min=1,max=1,description="The Network ID characterising the Hosting Node."),,,,,,,})
@TypeMetadata(name="HostingNode",
description="HostingNode represents a container capable of managing the lifecycle of an electronic service, i.e., being capable of hosting and operating an [EService](type:EService). Examples are docker, tomcat. A container is a service which is conceived to enable any services respecting the container rules to be operative. The container does not typically provide any functionality rather than allowing the hosted service to operate. The HostingNode characterisation in terms of facets reflects the one presented for [VirtualMachine](type:VirtualMachine). In particular, facets representing memory, CPU and networking interface are used to describe the HostingNode when the [VirtualMachine](type:VirtualMachine) enabling the HostingNode is not represented. Federated systems can provide virtual machines as resources or containers as resources. In some cases, the description of a container includes (virtual) hardware information. It is important to highlight that HostingNode is not a subclass of [VirtualMachine](type:VirtualMachine).",
version="1.0.0")
@Change(version="1.0.0",
description="First Version")
public interface HostingNode
extends Service
HostingNode represents a container capable of managing the lifecycle of an
electronic service, i.e.,
being capable of hosting and operating an
EService. Examples are
docker, tomcat. A container
is a service which is conceived to enable any services respecting the
container rules to be
operative; it does not typically provide any functionality other than
allowing the hosted service to
operate.
The HostingNode characterisation in terms of facets reflects the one
presented for
VirtualMachine. In particular, facets representing memory, CPU and
networking interface are
used to describe the HostingNode when the
VirtualMachine enabling it
is not represented.
Federated systems can provide virtual machines as resources or containers as
resources, and in some
cases the description of a container includes (virtual) hardware information.
It is important to highlight that HostingNode is not a subclass of
VirtualMachine.
- Author:
- Luca Frosini (ISTI - CNR)