Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

Add Flexible Topologies tables and modify deliveryservice table #4564

@zrhoffman

Description

@zrhoffman

I'm submitting a ...

  • new feature / enhancement request

Description

Traffic Control components affected ...

  • Traffic Ops DB

Acceptance Criteria

  • topology table adheres to this schema:

    column type modifiers
    name text not null, PK
    description text
    last_updated timestamptz default now()
  • topology_cachegroup table adheres to this schema:

    column type modifiers
    id int not null, PK
    topology text not null, FK: references topology(name)
    cachegroup text not null, FK: references cachegroup(short_name)
    last_updated timestamptz default now()
  • topology_cachegroup_parents table adheres to this schema:

    column type modifiers
    child int not null, FK: references topology_cachegroup(id)
    parent int not null, FK: references topology_cachegroup(id)
    rank int not null
    last_updated timestamptz default now()
  • After running migrations, deliveryservice table has a topology column that can be described as:

    column type modifiers
    topology text FK: references topology(name)

The line

See the Flexible Topologies PR for specifics: #4537

Metadata

Metadata

Assignees

No one assigned

    Labels

    databaserelating to setup/installation/structure of the Traffic Ops databasenew featureA new feature, capability or behavior

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions