AYS Parent/Child Relationship

A service can be a parent for other services.

It's just a way of organizing your services and grouping them.

Child services are created in a subdirectory of its parent.

Example

Example of parent in schema.hrd:

node = type:str parent:node auto

• This means that the service has a parent of role node and that it should auto create its parent if it doesn't already exist.
• The auto tag is optional and means that we will look if there is a parent if right type if yes will use that one
• The optional tag is optional and means that the parent relationship is not required

Example deployed:

Considering the following blueprint:

datacenter__eu:
    location: 'Europe'
    description: 'Main datacenter in Europe'

datacenter__us:
    location: 'USA'
    description: 'Main datacenter in USA'


rack__storage1:
    datacenter: 'eu'
    location: 'room1'
    description: 'rack for storage node'

rack__storage2:
    datacenter: 'eu'
    location: 'room1'
    description: 'rack for storage node'

rack__cpu1:
    datacenter: 'us'
    location: 'east building'
    description: 'rack for cpu node'

rack__storage4:
    datacenter: 'us'
    location: 'west buuilding'
    description: 'rack for cpu node'

In this example the rack service use the datacenter service as parent.
After execution of the command ays blueprint, the service tree will look like that:

$ tree services/
services/
├── datacenter!eu
│   ├── instance.hrd
│   ├── rack!storage1
│   │   ├── instance.hrd
│   │   └── state.yaml
│   ├── rack!storage2
│   │   ├── instance.hrd
│   │   └── state.yaml
│   └── state.yaml
└── datacenter!us
    ├── instance.hrd
    ├── rack!cpu1
    │   ├── instance.hrd
    │   └── state.yaml
    ├── rack!storage4
    │   ├── instance.hrd
    │   └── state.yaml
    └── state.yaml

6 directories, 12 files