• 设为首页
  • 点击收藏
  • 手机版
    手机扫一扫访问
    迪恩网络手机版
  • 关注官方公众号
    微信扫一扫关注
    迪恩网络公众号

openebs/maya: Manage Container Attached Storage (CAS) - Data Engines in Kubernet ...

原作者: [db:作者] 来自: 网络 收藏 邀请

开源软件名称(OpenSource Name):

openebs/maya

开源软件地址(OpenSource Url):

https://github.com/openebs/maya

开源编程语言(OpenSource Language):

Go 97.0%

开源软件介绍(OpenSource Introduction):

Build Status Go Report codecov License FOSSA Status CII Best Practices

Overview

OpenEBS control plane components like provisioners and operators were hosted in this repository.

As the OpenEBS community started to add new engines, the engine specific control plane components have been moved to their respective repositories.

This repository mainly contains code required for running the legacy cStor and Jiva pools and volumes like:

  • m-apiserver - used for provisoining the legacy cStor and Jiva pools and volumes.
    • mayactl - packaged along with m-apiserver for fetching the legacy cStor and Jiva volume status.
  • admission-server - used for validating Jiva and cStor pool and volume requests.
  • m-upgrade - used for upgrading the legacy Jiva volumes, cStor pools and volumes.
  • cstor-pool-mgmt and cstor-volume-mgmt - used for managing the legacy cStor pool and volumes.

With OpenEBS 3.0, all of the above legacy components are deprecated and users are requested to migrate towards using:

  • CStor CSI Driver
  • Jiva CSI Driver

The steps to migrate are provided here: https://github.com/openebs/upgrade.

v2.12.x is the last active branch on this repository, that will be used to mainly resolve any security vulnerability or kubernetes compatibility issues found on production setups using the legacy provisioners. New features will be developed only cStor and Jiva CSI drivers.

Install

Please refer to our documentation at OpenEBS Documentation.

Release

Prior to creating a release tag on this repository on v2.12.x branch with the required fixes, ensure that:

  • the dependent data engine repositories and provisioner are tagged.
  • update the versionDetails.go to include the supported upgrade path.

Once the code is merged, use the following sequence to release a new version for the legacy components:

Note: The github release workflows are setup to push the tag to the dependent repositories. In the above case, if a release tag is created on v2.12.x branch of linux-utils, then it will trigger the releases down to velero-plugin repo.

Once the tags are generated update the helm charts and YAMLs at:

Contributing

We are looking at further refactoring this repository by moving the common packages from this repository into a new common repository. If you are interested in helping with the refactoring efforts, please reach out to the OpenEBS Community.

For details on setting up the development environment and fixing the code, head over to the CONTRIBUTING.md.

Community

OpenEBS welcomes your feedback and contributions in any form possible.

License

FOSSA Status




鲜花

握手

雷人

路过

鸡蛋
该文章已有0人参与评论

请发表评论

全部评论

专题导读
热门推荐
阅读排行榜

扫描微信二维码

查看手机版网站

随时了解更新最新资讯

139-2527-9053

在线客服(服务时间 9:00~18:00)

在线QQ客服
地址:深圳市南山区西丽大学城创智工业园
电邮:jeky_zhao#qq.com
移动电话:139-2527-9053

Powered by 互联科技 X3.4© 2001-2213 极客世界.|Sitemap