openebs-enterprise | underlying OpenEBS project
kandi X-RAY | openebs-enterprise Summary
kandi X-RAY | openebs-enterprise Summary
openebs-enterprise is a Shell library typically used in Framework applications. openebs-enterprise has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
The OpenEBS Enterprise Edition is a hardened version of the CNCF project OpenEBS. The Enterprise Edition is intended for enterprises that require a supported platform - all enterprise customers of MayaData receive the Enterprise Edition as well as the other capabilities offered by MayaData.
The OpenEBS Enterprise Edition is a hardened version of the CNCF project OpenEBS. The Enterprise Edition is intended for enterprises that require a supported platform - all enterprise customers of MayaData receive the Enterprise Edition as well as the other capabilities offered by MayaData.
Support
Quality
Security
License
Reuse
Support
openebs-enterprise has a low active ecosystem.
It has 26 star(s) with 1 fork(s). There are 6 watchers for this library.
It had no major release in the last 6 months.
openebs-enterprise has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of openebs-enterprise is current.
Quality
openebs-enterprise has no bugs reported.
Security
openebs-enterprise has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
openebs-enterprise does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
openebs-enterprise releases are not available. You will need to build from source code and install.
Installation instructions are available. Examples and code snippets are not available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of openebs-enterprise
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of openebs-enterprise
openebs-enterprise Key Features
No Key Features are available at this moment for openebs-enterprise.
openebs-enterprise Examples and Code Snippets
No Code Snippets are available at this moment for openebs-enterprise.
Community Discussions
No Community Discussions are available at this moment for openebs-enterprise.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install openebs-enterprise
The process for building OpenEBS Community images are as follows:.
Each OpenEBS Repository will have either Travis or GitHub Action that runs component or repo level tests and pushes the tagged images to image-registry.
Nightly (OpenEBS.ci E2e pipelines) builds are executed for the changes pushed to master. The E2e tests are maintained under https://github.com/openebs/e2e-tests. Nightly builds are executed on Packet Infrastructure, triggered via GitLab. GitLab machine is hosted by MayaData.
A minor release is done every month. A release branch is created from the master. Release candidate images are built and pushed to image-registry using the corresponding Repository CI scripts.
Release pipelines are triggered manually on Release Candidate builds. The Release pipelines are executed on Native K8s, OpenShift and Konvoy clusters hosted by MayaData.
OpenEBS Release Checklist comprises of: Successful execution of Release pipelines on Release tagged images. (RC and final release tag) Upgrade Testing (RC and final release tag) Director (staging) (with RC2) GitLab (openebs.ci) cluster is upgraded (with final release tag)
The process for building OpenEBS Enterprise Edition images are as follows:.
Each OpenEBS Repository will have either Travis or GitHub Action that runs component or repo level tests and pushes images to the enterprise image-registry. The images will be pushed to mayadata docker hub. Example: hub.docker.com/mayadata-io/cstor-ee. The image metadata within the docker images will indicate labels pointing to enterprise.
The automation will be setup on the enteprise release branches. Enterprise images are created, by creating via GitHub release on the enterprise branch.
Each OpenEBS Repository will have either Travis or GitHub Action that runs component or repo level tests and pushes the tagged images to image-registry.
Nightly (OpenEBS.ci E2e pipelines) builds are executed for the changes pushed to master. The E2e tests are maintained under https://github.com/openebs/e2e-tests. Nightly builds are executed on Packet Infrastructure, triggered via GitLab. GitLab machine is hosted by MayaData.
A minor release is done every month. A release branch is created from the master. Release candidate images are built and pushed to image-registry using the corresponding Repository CI scripts.
Release pipelines are triggered manually on Release Candidate builds. The Release pipelines are executed on Native K8s, OpenShift and Konvoy clusters hosted by MayaData.
OpenEBS Release Checklist comprises of: Successful execution of Release pipelines on Release tagged images. (RC and final release tag) Upgrade Testing (RC and final release tag) Director (staging) (with RC2) GitLab (openebs.ci) cluster is upgraded (with final release tag)
The process for building OpenEBS Enterprise Edition images are as follows:.
Each OpenEBS Repository will have either Travis or GitHub Action that runs component or repo level tests and pushes images to the enterprise image-registry. The images will be pushed to mayadata docker hub. Example: hub.docker.com/mayadata-io/cstor-ee. The image metadata within the docker images will indicate labels pointing to enterprise.
The automation will be setup on the enteprise release branches. Enterprise images are created, by creating via GitHub release on the enterprise branch.
Support
The enterprise images are tagged as X.Y.Z-ee, the corresponding community version is X.Y.Z.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page