Change #1224817 had a related patch set uploaded (by Eevans; author: Eevans):

[operations/deployment-charts@master] WIP hoard chart

https://gerrit.wikimedia.org/r/1224817

Bikeshedding of service names welcome!

:)

Do you prefer Artifact over Entity? Entity seems like a more common term for this concept to me, whatcha think? In DPE at least, artifacts usually mean something more like a static file

Also, why 'linked'? I'd guess maybe because a record stored in the cache is 'linked' by a stable foreign key to the source system? I worry that 'linked' may be a overloaded term here, especially if we ever store page links ;) What did you intend 'linked' to mean?

entity-cache maybe?

In T414112#11506054, @Ottomata wrote:

[ ... ]
Do you prefer Artifact over Entity? Entity seems like a more common term for this concept to me, whatcha think?

Both are a little too generic for my taste, but I think the entity here is the MediaWiki article. It is a particular and discrete unit that can be considered apart from its properties...

What is being stored here is more ...object produced or shaped by craft, especially a tool...or ornament of archaeological or historical interest, or something viewed as a product...rather than an inherent element. So artifacts associated with entities.

In DPE at least, artifacts usually mean something more like a static file

I don't think that's too far off. For example, from the perspective of this system, the data is opaque (as it is for a system storing files), even if it's somehow structured according to the thing that produced it.

Also, why 'linked'? I'd guess maybe because a record stored in the cache is 'linked' by a stable foreign key to the source system? I worry that 'linked' may be a overloaded term here, especially if we ever store page links ;) What did you intend 'linked' to mean?

Yes, linked as in "connected". Each is linked to a particular revision of a MediaWiki article.

I think as important as having the capability itself, is having a system (and it's corresponding documentation, nomenclature, etc) that encapsulates a well-defined problem. We should be able to clearly and easily define exactly what this is for (and perhaps even more importantly, what it isn't for).

entity-cache maybe?

This feels less specific, where I would prefer something more specific. The less ambiguous the better!

Oh, entity vs artifact interesting. Indeed! We would not be storing the entity, but data directly associated with / about the entity. A MW example: pagelinks is derived data, but we would not say that a pagelink is a core MW entity. It is derived data about a MW entity: the page. Is it a new derived entity? Meh, I suppose you could call it that, but that is not helpful. Okay I'm convinced entity is not a good name for this then.

Another term for what this is sort of doing: materialized view storage. Or, it can be used as a materialized view, but it also has cache like abilities: fetching the requested value on cache miss. materialized-artifacts? Meh.

Yes, linked as in "connected".

Hm, what about using the term 'foreign' as in foreign key somehow. foreign-artifacts? Too weird? :) associated-artifacts ?

Maybe linked-artifacts is just fine :D

In T414112#11519172, @Ottomata wrote:

[ ... ]

Hm, what about using the term 'foreign' as in foreign key somehow. foreign-artifacts? Too weird? :) associated-artifacts ?

Maybe linked-artifacts is just fine :D

I'm not a huge fan of linked-artifacts, but I've vacillated on this quite a bit, with a trajectory that looked a lot like the above. :)

Change #1227851 had a related patch set uploaded (by Federico Ceratto; author: Federico Ceratto):

[operations/puppet@production] service, trafficserver: Prepare "linked-artifacts" k8s pod

https://gerrit.wikimedia.org/r/1227851

We (Serviceops) are at capacity this quarter, but we'll keep an eye on this, please tag us if we can help with design questions or issues during deployment.

jelto opened https://gitlab.wikimedia.org/repos/releng/gitlab-trusted-runner/-/merge_requests/142

add repos/sre/hoarde to trusted runners

jelto merged https://gitlab.wikimedia.org/repos/releng/gitlab-trusted-runner/-/merge_requests/142

add repos/sre/hoarde to trusted runners

Change #1237258 had a related patch set uploaded (by Jelto; author: Jelto):

[operations/puppet@production] deployment_server: add linked-artifacts kubeconfig files

https://gerrit.wikimedia.org/r/1237258