stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2019-12-03T16:25:47Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/94Need to upload Stork ARM to readthedocs.io2019-12-03T16:25:47ZTomek MrugalskiNeed to upload Stork ARM to readthedocs.ioWe now have a basic Sphinx documentation for Stork. We need to upload it to readthedocs.io.
The most important info is installation manual, but other parts will become useful in the near future.We now have a basic Sphinx documentation for Stork. We need to upload it to readthedocs.io.
The most important info is installation manual, but other parts will become useful in the near future.Stork-0.2https://gitlab.isc.org/isc-projects/stork/-/issues/87Build Stork natively (also on MacOS)2019-12-02T14:28:56ZTomek MrugalskiBuild Stork natively (also on MacOS)Although we don't want to officially support MacOS (the market to run dashboards on Macs is probably non-existent), several developers and power users are interested in reviewing and testing it on MacOS.
This is mostly for developer's c...Although we don't want to officially support MacOS (the market to run dashboards on Macs is probably non-existent), several developers and power users are interested in reviewing and testing it on MacOS.
This is mostly for developer's convenience, not for end-users.
While the initial goal of this was to be able to run stork on MacOS, this eventually evolved into two things:
1. run on MacOS
2. run on the box natively (without using docker)
Stork-0.2Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/126prepare 2 containers with agent and kea configured for HA2020-01-10T05:06:07ZMichal Nowikowskiprepare 2 containers with agent and kea configured for HAStork-0.3Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/108Go format the code2020-01-13T13:35:30ZMatthijs Mekkingmatthijs@isc.orgGo format the codeWe should use `go fmt` to use consistent code style. Danger should fail if the code is not well formatted.We should use `go fmt` to use consistent code style. Danger should fail if the code is not well formatted.Stork-0.3Matthijs Mekkingmatthijs@isc.orgMatthijs Mekkingmatthijs@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/issues/102update tools to latest versions2019-12-30T17:54:52ZMichal Nowikowskiupdate tools to latest versionsStork-0.3Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/101update primeng dependency to latest 8.1.12019-12-30T17:36:04ZMichal Nowikowskiupdate primeng dependency to latest 8.1.1update other UI deps as wellupdate other UI deps as wellStork-0.3Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/152problems with defining deps in kea container2020-02-05T15:54:10ZMichal Nowikowskiproblems with defining deps in kea containerStork-0.4https://gitlab.isc.org/isc-projects/stork/-/issues/141modularize ReST swagger API definition2020-01-21T14:22:32ZMichal Nowikowskimodularize ReST swagger API definitionCurrently ReST API is defined in one big file, swagger.yaml. It will be easier to maintain the API if it is split by API groups (users, services, etc.).Currently ReST API is defined in one big file, swagger.yaml. It will be easier to maintain the API if it is split by API groups (users, services, etc.).Stork-0.4Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/114enable more checks from golangci-lint2020-01-13T13:01:29ZMichal Nowikowskienable more checks from golangci-lintStork-0.4https://gitlab.isc.org/isc-projects/stork/-/issues/189Fix docker traffic-dhcp build2020-03-06T07:45:50ZMatthijs Mekkingmatthijs@isc.orgFix docker traffic-dhcp build0.5Matthijs Mekkingmatthijs@isc.orgMatthijs Mekkingmatthijs@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/issues/224bump version to 0.62020-04-03T12:40:11ZTomek Mrugalskibump version to 0.6Need to bump up the version before 0.6 release, update changelog etc.Need to bump up the version before 0.6 release, update changelog etc.0.6https://gitlab.isc.org/isc-projects/stork/-/issues/207add deploying stork packages to cloudsmith.io2020-03-22T09:40:45ZMichal Nowikowskiadd deploying stork packages to cloudsmith.ioThere should be defined testing and public repos. There should be 2 manual GitLab CI jobs:
1) for uploading to testing repo and verifying if pkgs can be installed from that repo
2) the same but for public repoThere should be defined testing and public repos. There should be 2 manual GitLab CI jobs:
1) for uploading to testing repo and verifying if pkgs can be installed from that repo
2) the same but for public repo0.6Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/187implement building deb and rpm packages with stork2020-03-17T14:05:20ZMichal Nowikowskiimplement building deb and rpm packages with stork0.6Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/232Publish stork sources on github2020-04-15T18:00:08ZTomek MrugalskiPublish stork sources on githubStork is now approaching a phase when it can be shown to a broader audience. We need to clone/sync our repo to GH.Stork is now approaching a phase when it can be shown to a broader audience. We need to clone/sync our repo to GH.0.7https://gitlab.isc.org/isc-projects/stork/-/issues/227Sanity checks for 0.6.02022-02-02T09:51:28ZTomek MrugalskiSanity checks for 0.6.0Please test latest master and put your sanity checks in this ticket.Please test latest master and put your sanity checks in this ticket.0.7https://gitlab.isc.org/isc-projects/stork/-/issues/212lint_ui fails on files in src/assets/arm2020-05-06T09:02:55ZMarcin Siodelskilint_ui fails on files in src/assets/armI get the following errors while linting UI:
```
Checking formatting...
src/assets/arm/_static/basic.css
src/assets/arm/_static/css/badge_only.css
src/assets/arm/_static/css/theme.css
src/assets/arm/_static/doctools.js
src/assets/arm/_st...I get the following errors while linting UI:
```
Checking formatting...
src/assets/arm/_static/basic.css
src/assets/arm/_static/css/badge_only.css
src/assets/arm/_static/css/theme.css
src/assets/arm/_static/doctools.js
src/assets/arm/_static/documentation_options.js
src/assets/arm/_static/fonts/fontawesome-webfont.eot[error] No parser could be inferred for file: src/assets/arm/_static/fonts/fontawesome-webfont.eot
...
```
The commands I used:
```
$ rake build_ui
$ rake lint_ui
```
This doesn't happen if I don't build the UI prior to linting it. So this eliminates the issue:
```
$ git clean -dfx
$ rake lint_ui
```
but I want to be able to run the linter after the UI has been built. Apparently some directories need to be excluded from linting.0.7https://gitlab.isc.org/isc-projects/stork/-/issues/302Docker based demo should use Kea 1.7.82020-05-29T13:16:13ZMarcin SiodelskiDocker based demo should use Kea 1.7.8Our demo setup uses Kea 1.7.4 and Kea 1.7.3 for various agents being installed on docker containers. Kea 1.7.8 introduces new information about HA setup returned in response to the status-get command. To see this information we'd need to...Our demo setup uses Kea 1.7.4 and Kea 1.7.3 for various agents being installed on docker containers. Kea 1.7.8 introduces new information about HA setup returned in response to the status-get command. To see this information we'd need to upgrade our containers (at least ha1 and ha2) to use Kea 1.7.8.0.8https://gitlab.isc.org/isc-projects/stork/-/issues/132Go code when run in containers should be built in containers2020-05-14T14:53:52ZMichal NowikowskiGo code when run in containers should be built in containersOtherwise when code is built on e.g. macOS it is not possible to run such binaries in a container with Linux.
Such error is observed:
```
`server_1 | /bin/sh: 1: /server/stork-server: Exec format error`
```Otherwise when code is built on e.g. macOS it is not possible to run such binaries in a container with Linux.
Such error is observed:
```
`server_1 | /bin/sh: 1: /server/stork-server: Exec format error`
```0.8Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/323go-swagger build error workaround (docker/ubuntu 20.04)2020-07-09T15:26:50ZTomek Mrugalskigo-swagger build error workaround (docker/ubuntu 20.04)I've tried to build Stork demo on Ubuntu 20.04. And ended with this error:
```
rake docker_up
[...]
/repo/build-root/tools/v0.23.0/swagger_linux_amd64 generate server -s server/gen/restapi -m server/gen/models --name Stork --exclude-ma...I've tried to build Stork demo on Ubuntu 20.04. And ended with this error:
```
rake docker_up
[...]
/repo/build-root/tools/v0.23.0/swagger_linux_amd64 generate server -s server/gen/restapi -m server/gen/models --name Stork --exclude-main --spec /repo/build-root/api/swagger.yaml --template stratoscale --regenerate-configureapi
2020/06/18 19:11:51 loading contrib stratoscale
2020/06/18 19:11:51 added contributed template client/client.gotmpl from templates/contrib/stratoscale/client/client.gotmpl
2020/06/18 19:11:51 added contributed template client/facade.gotmpl from templates/contrib/stratoscale/client/facade.gotmpl
2020/06/18 19:11:51 added contributed template server/configureapi.gotmpl from templates/contrib/stratoscale/server/configureapi.gotmpl
2020/06/18 19:11:51 added contributed template server/server.gotmpl from templates/contrib/stratoscale/server/server.gotmpl
runtime: mlock of signal stack failed: 12
runtime: increase the mlock limit (ulimit -l) or
runtime: update your kernel to 5.3.15+, 5.4.2+, or 5.5+
fatal error: mlock failed
runtime stack:
runtime.throw(0xd2780f, 0xc)
/usr/local/go/src/runtime/panic.go:1112 +0x72
runtime.mlockGsignal(0xc000603e00)
/usr/local/go/src/runtime/os_linux_x86.go:72 +0x107
runtime.mpreinit(0xc000588a80)
/usr/local/go/src/runtime/os_linux.go:341 +0x78
runtime.mcommoninit(0xc000588a80)
/usr/local/go/src/runtime/proc.go:630 +0x108
runtime.allocm(0xc000061800, 0xd6dda8, 0x0)
/usr/local/go/src/runtime/proc.go:1390 +0x14e
runtime.newm(0xd6dda8, 0xc000061800)
/usr/local/go/src/runtime/proc.go:1704 +0x39
runtime.startm(0x0, 0xc000510301)
/usr/local/go/src/runtime/proc.go:1869 +0x12a
runtime.wakep(...)
/usr/local/go/src/runtime/proc.go:1953
runtime.resetspinning()
/usr/local/go/src/runtime/proc.go:2415 +0x93
runtime.schedule()
/usr/local/go/src/runtime/proc.go:2527 +0x2de
runtime.park_m(0xc000001980)
/usr/local/go/src/runtime/proc.go:2690 +0x9d
runtime.mcall(0x0)
/usr/local/go/src/runtime/asm_amd64.s:318 +0x5b
goroutine 1 [runnable]:
github.com/go-openapi/swag.WriteJSON(0xbefca0, 0xc000be60e0, 0x4, 0x10, 0x0, 0x0, 0x0)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/json.go:56 +0x1ef
github.com/go-openapi/swag.JSONMapItem.MarshalEasyJSON(0xc00089bc7c, 0x4, 0xbefca0, 0xc000be60e0, 0xc000c00620)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:125 +0x6e
github.com/go-openapi/swag.JSONMapSlice.MarshalEasyJSON(0xc000be8000, 0x6, 0x6, 0xc000c00620)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:75 +0x97
github.com/go-openapi/swag.WriteJSON(0xc48420, 0xc000be62c0, 0x3, 0x556a7c, 0x50, 0x68, 0xc000c005b0)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/json.go:59 +0x92
github.com/go-openapi/swag.JSONMapItem.MarshalEasyJSON(0xc00089bc2b, 0x3, 0xc48420, 0xc000be62c0, 0xc000c005b0)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:125 +0x6e
github.com/go-openapi/swag.JSONMapSlice.MarshalEasyJSON(0xc000be60c0, 0x1, 0x1, 0xc000c005b0)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:75 +0x97
github.com/go-openapi/swag.WriteJSON(0xc48420, 0xc000be62e0, 0x7, 0x236, 0x0, 0x0, 0x0)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/json.go:59 +0x92
github.com/go-openapi/swag.JSONMapItem.MarshalEasyJSON(0xc00089bc24, 0x7, 0xc48420, 0xc000be62e0, 0xc000bb0e00)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:125 +0x6e
github.com/go-openapi/swag.JSONMapSlice.MarshalEasyJSON(0xc0001c4780, 0x14, 0x14, 0xc000bb0e00)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:75 +0x97
github.com/go-openapi/swag.WriteJSON(0xc48420, 0xc000bec340, 0x5, 0x80, 0x0, 0x0, 0x0)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/json.go:59 +0x92
github.com/go-openapi/swag.JSONMapItem.MarshalEasyJSON(0xc00089b2b6, 0x5, 0xc48420, 0xc000bec340, 0xc000bb0c40)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:125 +0x6e
github.com/go-openapi/swag.JSONMapSlice.MarshalEasyJSON(0xc0001d4280, 0xa, 0xa, 0xc000bb0c40)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:75 +0x97
github.com/go-openapi/swag.WriteJSON(0xc48420, 0xc000bf01a0, 0xc48420, 0xc000bf01a0, 0x0, 0x0, 0x0)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/json.go:59 +0x92
github.com/go-openapi/swag.YAMLToJSON(0xc15fe0, 0xc000be1020, 0xc15fe0, 0xc000be1020, 0x0, 0x0, 0x5)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:40 +0x85
github.com/go-openapi/swag.YAMLDoc(0x7fffdebefe13, 0x21, 0xc000149d01, 0x0, 0x0, 0xc000787980, 0x4ffd00)
/go/pkg/mod/github.com/go-openapi/swag@v0.19.8/yaml.go:230 +0x60
github.com/go-openapi/loads.Spec(0x7fffdebefe13, 0x21, 0xd49261, 0xc000787a08, 0x1d)
/go/pkg/mod/github.com/go-openapi/loads@v0.19.5/spec.go:123 +0xec
github.com/go-swagger/go-swagger/generator.(*GenOpts).validateAndFlattenSpec(0xc000638fc0, 0x7fffdebefe40, 0xb, 0x0)
/go/src/github.com/go-swagger/go-swagger/generator/spec.go:22 +0x50
github.com/go-swagger/go-swagger/generator.(*GenOpts).analyzeSpec(0xc000638fc0, 0x0, 0x0, 0x7f73563f87d0, 0x0)
/go/src/github.com/go-swagger/go-swagger/generator/spec.go:88 +0x35
github.com/go-swagger/go-swagger/generator.newAppGenerator(0x7fffdebefdf7, 0x5, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc000638fc0, 0xc00001c540, ...)
/go/src/github.com/go-swagger/go-swagger/generator/support.go:61 +0x88
github.com/go-swagger/go-swagger/generator.GenerateServer(0x7fffdebefdf7, 0x5, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc000638fc0, 0xc000638fc0, ...)
/go/src/github.com/go-swagger/go-swagger/generator/support.go:36 +0x94
github.com/go-swagger/go-swagger/cmd/swagger/commands/generate.(*Server).generate(0xc00000a5a0, 0xc000638fc0, 0x0, 0x0)
/go/src/github.com/go-swagger/go-swagger/cmd/swagger/commands/generate/server.go:88 +0x94
github.com/go-swagger/go-swagger/cmd/swagger/commands/generate.createSwagger(0xea6e40, 0xc00000a5a0, 0x8b4a01, 0x7f732f76b2b8)
/go/src/github.com/go-swagger/go-swagger/cmd/swagger/commands/generate/shared.go:175 +0x225
github.com/go-swagger/go-swagger/cmd/swagger/commands/generate.(*Server).Execute(0xc00000a5a0, 0xc0001b4a80, 0x0, 0xe, 0xc00000a5a0, 0x1)
/go/src/github.com/go-swagger/go-swagger/cmd/swagger/commands/generate/server.go:115 +0x37
github.com/jessevdk/go-flags.(*Parser).ParseArgs(0xc000185e00, 0xc00018c010, 0xe, 0xe, 0x10, 0xd54c3a, 0x2a, 0xbda6e0, 0xc0003b1ef0)
/go/pkg/mod/github.com/jessevdk/go-flags@v1.4.0/parser.go:316 +0x8c0
github.com/jessevdk/go-flags.(*Parser).Parse(...)
/go/pkg/mod/github.com/jessevdk/go-flags@v1.4.0/parser.go:186
main.main()
/go/src/github.com/go-swagger/go-swagger/cmd/swagger/swagger.go:145 +0xafc
rake aborted!
Command failed with status (2): [/repo/build-root/tools/v0.23.0/swagger_lin...]
/repo/build-root/Rakefile:195:in `block (2 levels) in <top (required)>'
/repo/build-root/Rakefile:194:in `chdir'
/repo/build-root/Rakefile:194:in `block in <top (required)>'
Tasks: TOP => install_server => build_server => gen_server => /repo/build-root/backend/server/gen/restapi/configure_stork.go
(See full trace by running task with --trace)
rake aborted!
Command failed with status (1): [cd ./build-root && GOPATH=/repo/build-root...]
/repo/Rakefile:551:in `block in <top (required)>'
Tasks: TOP => build_all_copy_in_subdir
(See full trace by running task with --trace)
rake aborted!
Command failed with status (1): [docker run -v $PWD:/repo --rm stork-builde...]
/home/thomson/devel/stork/Rakefile:544:in `block in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Tasks: TOP => docker_up => build_all_in_container
(See full trace by running task with --trace)
```
This is actually a kernel bug, details [go#35777](https://github.com/golang/go/issues/35777) and [go#37436](https://github.com/golang/go/issues/37436). This was so common that go added an actual test to detect if the kernel is buggy on not, that's why it prints this:
```
runtime: mlock of signal stack failed: 12
runtime: increase the mlock limit (ulimit -l) or
runtime: update your kernel to 5.3.15+, 5.4.2+, or 5.5+
```
This works fine when building natively, but fails in Docker containers. This ticket proposes a workaround for this problem.
It is intended to be temporary (couple months). However, at this time there is no newer kernel available for Ubuntu 20.04 (the lastest as of today) and we can't realistically expect people to compile new kernel for Stork compilation.0.9Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/320adapt deploy_demo in .gitlab-ci.yml to new model of building demo (docker_up)2020-06-16T13:22:15ZMichal Nowikowskiadapt deploy_demo in .gitlab-ci.yml to new model of building demo (docker_up)0.9Michal NowikowskiMichal Nowikowski