Closed pawiecz closed 2 months ago
I would vote for localinstall, local is too generic.
I agree just "local" might seem too generic without any context. Although I do believe it should be fine in the context of -deploy
repo, let's drop it in favor of another one.
Currently we've got two subdirectories for deploying KernelCI onto Kubernetes clusters ("k8s" and "kubernetes" just for Azure).
@nuclearcat do you think that it would make sense to store kci-easy
in a "docker-compose" directory to reflect base tech required for this deployment type? Then we could still reuse "localinstall" for running KernelCI system components without any middleware (just as system services).
I created #150 to import your code here (with some adjustments not merged in the source repo yet) under "localinstall" but will happily git mv
it and amend that PR if we agree on other naming scheme.
Resolved by #150 (I forgot to add Fixes:
tag to autoclose this task)
kci-easy
is a tool created to simplify deployment of a local KernelCI system instance.It could be leveraged as a development/evaluation environment for the new system.
Potential names for its subdirectory within
-deploy
repo were suggested on IRC: