你好

第42节 RFC: 对 horizon 工程和代码细节上部分改进策略


❤️💕💕记录sealosopen in new window开源项目的学习过程。k8s,docker和云原生的学习open in new window。Myblog:http://nsddd.topopen in new window

[TOC]

horizon 目前存在的问题

  • Makefile 功能太单一，可扩展性弱，不支持交叉编译和容器编译，不支持其他扩展能力
  • 并没有对日志做出很好的处理
  • 没有对版权做很好的处理
  • 没有一个完美的 CICD 流程
  • 没有一套合适的错误码设计方案
  • 虽然有 Swagger 但是并没有生成 API 文档
  • 没有优雅的 tag、branch、release，以及 commit 规范

Makefile 设计

makefile 设计是工程设计很大的一个模块，将其抽出基本的子模块，各司其职。

  • 支持交叉编译(arm, amd)
  • 支持 docker 二进制编译
  • 并行编译

The current project has the following shortcomings:

  • [ ] The Makefile has too simple functionality, weak extensibility, does not support cross-compilation and container compilation, and does not support other extension capabilities.
  • [ ] There is no good handling of logs (can be encapsulated with zap).
  • [ ] There is no good handling of copyright.
  • [ ] There is no perfect CICD process.
  • [ ] The robot setting is unreasonable.
  • [ ] There is no suitable error code design solution.
  • [ ] Although there is Swagger, API documentation is not generated.
  • [ ] There is no elegant tag, branch, release, and commit specification.
  • [ ] The documentation is not elegant enough.
  • [ ] Unit coverage should be used, embedded in actions and Makefiles

END 链接