stork merge requestshttps://gitlab.isc.org/isc-projects/stork/-/merge_requests2021-12-06T20:05:07Zhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/372Resolve "Document alerting using Prometheus"2021-12-06T20:05:07ZTomek MrugalskiResolve "Document alerting using Prometheus"Closes #600Closes #6001.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/371Resolve "More explanatory comments in /etc/stork/agent.env"2021-12-03T21:21:42ZSlawek FigielResolve "More explanatory comments in /etc/stork/agent.env"Closes #632Closes #6321.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/370Resolve "Password not parsed correctly by stork-tool"2021-12-02T13:02:16ZSlawek FigielResolve "Password not parsed correctly by stork-tool"Closes #628Closes #6281.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/369[#606] Upgraded npm and angular to 132021-12-02T15:25:54ZMarcin Siodelski[#606] Upgraded npm and angular to 13Closes #606Closes #6061.0Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/368Resolve "STORK_SERVER_URL - unknown environment variable in doc"2021-12-02T20:32:52ZSlawek FigielResolve "STORK_SERVER_URL - unknown environment variable in doc"Closes #621Closes #6211.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/367Resolve "Wrong port in example"2021-12-01T14:19:39ZSlawek FigielResolve "Wrong port in example"Closes #626Closes #6261.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/365Resolve "Document troubleshooting steps for when agent doesn't register prope...2021-12-02T21:35:39ZSlawek FigielResolve "Document troubleshooting steps for when agent doesn't register properly in Server"Closes #475Closes #4751.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/364Resolve "When subnet is moved into a shared network the old subnet entry is n...2021-12-02T10:54:43ZMarcin SiodelskiResolve "When subnet is moved into a shared network the old subnet entry is not removed"Closes #473Closes #4731.0Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/363Resolve "Cannot fetch machine state when using IPv6 address"2021-12-02T16:59:53ZSlawek FigielResolve "Cannot fetch machine state when using IPv6 address"Closes #447Closes #4471.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/362Draft: Resolve "problem with parsing kea config with comments"2021-12-01T12:16:11ZSlawek FigielDraft: Resolve "problem with parsing kea config with comments"Closes #264Closes #2641.0https://gitlab.isc.org/isc-projects/stork/-/merge_requests/361Resolve "Pool utilization shows inaccurate numbers"2021-12-03T19:08:27ZSlawek FigielResolve "Pool utilization shows inaccurate numbers"Closes #560Closes #5601.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/359CI deploy_demo: push core images to private registry2021-11-16T10:44:24ZAndrei Pavelandrei@isc.orgCI deploy_demo: push core images to private registryCloses #615.
The error states that it can't push to the private registry. That much I understand.
Why this has started failing recently? That I don't understand.
Limitations:
* `docker login` only supports one login at a time.
* Gitla...Closes #615.
The error states that it can't push to the private registry. That much I understand.
Why this has started failing recently? That I don't understand.
Limitations:
* `docker login` only supports one login at a time.
* Gitlab deploy tokens are not editable.
That being said, this solution is not perfect, but I welcome any more elegant suggestion. I've spent a sufficient 6 hours on this.
* [X] Modify core docker-compose.yaml to allow pushing to a custom registry. Keep the current as a default value.
* [X] Still push core images to the public registry so that they are available to the public.
* [X] Push core and premium images to the private registry.
* Because we can't push only the premium images, because it has services that `depend_on` core services.
* Because, when deploying, we also can't pull using docker-compose from a single registry for the same reason.
* Because we also can't push and pull to multiple registries because of the `docker login` limitation.
* Because we also can't have the same deploy token on both registries.
* [X] When deploying, pull from the private registry instead of the public registry, because we want premium too in the demo.1.0Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/358Resolve "New ways of triggering the config review"2021-11-22T16:25:47ZMarcin SiodelskiResolve "New ways of triggering the config review"Closes #609Closes #6091.0Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/356Resolve "update docs on how to set up rootless docker access"2021-11-09T14:45:43ZAndrei Pavelandrei@isc.orgResolve "update docs on how to set up rootless docker access"Closes #602Closes #6021.0Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/355Resolve "readthedocs build fails"2021-11-09T17:59:49ZAndrei Pavelandrei@isc.orgResolve "readthedocs build fails"Closes #608.
* [X] Add `doc/requirements.txt`. This is the only strictly required fix.
* [X] Add `.readthedocs.yaml` so that any readthedocs configuration change goes through the usual review. More on readthedocs configuration [here](ht...Closes #608.
* [X] Add `doc/requirements.txt`. This is the only strictly required fix.
* [X] Add `.readthedocs.yaml` so that any readthedocs configuration change goes through the usual review. More on readthedocs configuration [here](https://docs.readthedocs.io/en/stable/config-file/v2.html).
* [X] The newly added `fail_on_warning: true` makes the build fail because of `WARNING: unknown mimetype for _static/arch.drawio, ignoring`. I've moved `arch.drawio` out of static and added a rake task to build the PNG.
Git-tagged as `v0.22.0-fix`. Documentation is now live: https://stork.readthedocs.io/en/v0.22.0-fix/.1.0Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/353Resolve "Support for DB connection encryption"2021-11-09T13:33:40ZMarcin SiodelskiResolve "Support for DB connection encryption"Closes #403Closes #4031.0Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/347Resolve "Req 1.8 - Dump Service Configuration"2021-11-26T14:36:22ZSlawek FigielResolve "Req 1.8 - Dump Service Configuration"Closes #43Closes #431.0Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/411Resolve "Broken statistics, subnets, shared networks"2022-02-02T12:48:33ZSlawek FigielResolve "Broken statistics, subnets, shared networks"Closes #688Closes #6881.1Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/410Resolve "Fix copyright date on the login screen"2022-02-02T12:31:03ZMarcin SiodelskiResolve "Fix copyright date on the login screen"Closes #687Closes #6871.1Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/merge_requests/409Resolve "deploy_demo deploys old version of stork"2022-02-02T13:58:59ZAndrei Pavelandrei@isc.orgResolve "deploy_demo deploys old version of stork"Closes #686.
The problem was `docker-compose up` was run with default REGISTRY which you can see in `docker-compose.yaml` points to the public registry. Prior to the `docker-compose up` we are pushing the updated images to both the publ...Closes #686.
The problem was `docker-compose up` was run with default REGISTRY which you can see in `docker-compose.yaml` points to the public registry. Prior to the `docker-compose up` we are pushing the updated images to both the public registry and the private registry, and then we pull only from the private registry because we want the demo integrated with kea-premium. We never pull from the public registry. All recent invocations of `deploy_demo` were starting docker containers from images tagged with the public registry which might have been pulled manually at some point. This MR starts the right containers.1.1Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.org