ce9793c0be
This PR enhances the existing CLVM implementation which was based on the deprecated CLVM technology which was based on corosync/pacemaker. With RHEL 7 having reached EOL, CLVM seems to be broken. CLVM supports RAW volumes on LVM , where as CLVM_NG support QCOW2 on LVM. Further details: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Modernized+CLVM%3A+Enhancements+and+CLVM_NG+support NOTE: On testing - it was identified that incremental snapshots for clvm-ng do not work as expected. As of now it's been removed from scope. So, CLVM and CLVM_NG would only support full snapshots. * add support for proper cleanup of snapshots and prevent vol snapshot of running vm * remove snap vol restriction for sunning vms * refactor clvm code * add support for live migration * add support for migrating lvm lock * clvm deletion called explicitly * made necessary changes to allow migration of lock and deletion of detached volumes * fix create vol from snap and attach * add support to revert snapshot for clvm * add support to revert snapshot for clvm * make zero fill configurable * make setting non-dynamic & fix test * fix locking at vol/vm creation * fix revert snapshot format type and handle revert snapshot functionality for clvm * 1. Create clvmlockmanager and move common code \n 2. handle attaching volumes to stopped VMs \n 3. Handle lock transfer when VM is started on another host * add license * remove command/answer classes from sonar coverage check * add support for new gen clvm with template (qcow2) backing * Add support for clvm_ng - which allows qcow2 on block storage , linked clones, etc * fix test and use physical size + 50% of virtual size for backing file, while virtual size + pe for disk * migrate clvm volumes as full clone and allow migration from clvm to nfs * fix clvm_ng to nfs migration, and handle overhead calc * support live migration from clvm_ng to nfs and vice-versa * add support to migrate to and from clvm to nfs * fix creation of volume on destination host during migration to clvm/clvm-ng * support live vm migration between clvm -> clvm-ng (vice-versa), nfs -> clvm (vice-versa) and nfs->clvm-ng (vice-versa) * add unit tests for clvm/clvm_ng operations * Add support for incremental volume snapshots for clvm_ng * prevent snapshot backup for incremental clvm_ng snaps, fix build failure, add unit tests * fix lockhost on creation of volumes from snap and fix bitmap issue when migrating a vol with incremental snap * restrict pre and post migration commands to only kvm hosts where vm has CLVM/CLVM-NG volumes * evist lock tracking - use lvs command to get lock host than DB * add test for pre/post migration * Create a CLVM storage adaptor * update existing clvm get stats method * fix precommit check failure * Apply suggestions from code review Co-authored-by: Suresh Kumar Anaparti <sureshkumar.anaparti@gmail.com> * Apply suggestions from code review Co-authored-by: Suresh Kumar Anaparti <sureshkumar.anaparti@gmail.com> * improve lock host retrieval logic and quicker retrival using db host as first check point and then fanning out * add proper support for resizing of clvm_ng which calculated PE correctly for qcow2 metadata * fallback to full snapshots for clvm-ng - incremental not supported in 4.23 * expunge volume detail of lock host on vm expunge * if vmmigration with volume is done to the same clvm volume group, then dont do data transfer, just lock transfer and vm * add clvm pools with deterministic uuid , so as to prevent adding the same pool twic * added a small improvement to factor in a senario when lv is inactive on all hosts, could happen in storage outage issue * address comment - extract common code for endpoint identification if clvm pool type * Address comments - add early return guard to reduce indentation * minor improvement - when migrating vm with volumes, if there's a failures, change the clvm vols to exclusive on source from shared, and on success, change dest vol to exclusive only for cross-pool migration * cleanup unused code and tests for incremental snaps for clvmng and other cleanups * allow storage browser to list lv in clvm, fix clvm shrink, overprovisioning factor isnt used for clvm pools - so set it to 1 and prevented display of provisioning type for clvm * no need to have locktransfercommand to execute in sequence * increase lv cmd timeouts to consider cluster load --------- Co-authored-by: Pearl Dsilva <pearl1954@gmail.com> Co-authored-by: Suresh Kumar Anaparti <sureshkumar.anaparti@gmail.com> |
||
|---|---|---|
| .github | ||
| agent | ||
| api | ||
| build | ||
| client | ||
| cloud-cli | ||
| core | ||
| debian | ||
| deps | ||
| developer | ||
| engine | ||
| extensions | ||
| framework | ||
| packaging | ||
| plugins | ||
| python | ||
| quickcloud | ||
| scripts | ||
| server | ||
| services | ||
| setup | ||
| systemvm | ||
| test | ||
| tools | ||
| ui | ||
| usage | ||
| utils | ||
| vmware-base | ||
| .asf.yaml | ||
| .codespellrc | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .java-version | ||
| .markdownlintignore | ||
| .pre-commit-config.yaml | ||
| .python-version | ||
| CHANGES.md | ||
| CONTRIBUTING.md | ||
| INSTALL.md | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE | ||
| LICENSE.header | ||
| NOTICE | ||
| PRE_COMMIT.md | ||
| PULL_REQUEST_TEMPLATE.md | ||
| PendingReleaseNotes | ||
| README.md | ||
| pom.xml | ||
| requirements-dev.txt | ||
| requirements.txt | ||
README.md
Apache CloudStack
- Who Uses CloudStack?
- Demo
- Getting Started
- Getting Source Repository
- Documentation
- News and Events
- Getting Involved and Contributing
- Reporting Security Vulnerabilities
- License
- Notice of Cryptographic Software
- Star History
- Contributors
Apache CloudStack is open source software designed to deploy and manage large networks of virtual machines, as a highly available, highly scalable Infrastructure as a Service (IaaS) cloud computing platform. CloudStack is used by a number of service providers to offer public cloud services, and by many companies to provide an on-premises (private) cloud offering, or as part of a hybrid cloud solution.
CloudStack is a turnkey solution that includes the entire "stack" of features most organizations want with an IaaS cloud: compute orchestration, Network-as-a-Service, user and account management, a full and open native API, resource accounting, and a first-class User Interface (UI).
CloudStack currently supports the most popular hypervisors: VMware vSphere, KVM, XenServer, XenProject and Hyper-V as well as OVM and LXC containers.
Users can manage their cloud with an easy to use Web interface, command line tools, and/or a full-featured query based API.
For more information on Apache CloudStack, please visit the website
Who Uses CloudStack?
-
There are more than 150 known organizations using Apache CloudStack (or a commercial distribution of CloudStack). Our users include many major service providers running CloudStack to offer public cloud services, product vendors who incorporate or integrate with CloudStack in their own products, organizations who have used CloudStack to build their own private clouds, and systems integrators that offer CloudStack related services.
-
See our case studies highlighting successful deployments of Apache CloudStack.
-
See the up-to-date list of current users.
-
If you are using CloudStack in your organization and your company is not listed above, please complete our brief adoption survey. We're happy to keep your company name anonymous if you require.
Demo
See the project user-interface QA website that runs CloudStack against simulator hypervisor: https://qa.cloudstack.cloud/simulator/ (admin:password)
Getting Started
- Download a released version
- Build from source with the instructions in the INSTALL.md file.
Getting Source Repository
Apache CloudStack project uses Git. The official Git repository is at:
https://gitbox.apache.org/repos/asf/cloudstack.git
And a mirror is hosted on GitHub:
https://github.com/apache/cloudstack
The GitHub mirror is strictly read only and provides convenience to users and developers to explore the code and for the community to accept contributions via GitHub pull requests.
Documentation
- Project Documentation
- Release notes
- Developer wiki
- Design documents
- API documentation
- How to contribute
News and Events
Getting Involved and Contributing
Interested in helping out with Apache CloudStack? Great! We welcome participation from anybody willing to work The Apache Way and make a contribution. Note that you do not have to be a developer in order to contribute to Apache CloudStack. We need folks to help with documentation, translation, promotion etc. See our contribution page.
If you are a frequent contributors, you can request to be added as collaborators (see https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub) to our GitHub repos. This allows you to use project GitHub with ability to report issue with tags, and be assigned to issues and PRs. This is done via the .asf.yaml file in this repo. You may do so by sharing your GitHub users ID or raise a GitHub issue.
If you're interested in learning more or participating in the Apache CloudStack project, the mailing lists are the best way to do that. While the project has several communications channels, the mailing lists are the most active and the official channels for making decisions about the project itself.
Mailing lists:
- Development Mailing List
- Users Mailing List
- Commits Mailing List
- Issues Mailing List
- Marketing Mailing List
Report and/or check bugs on GitHub and check our developer page for contributing code.
Reporting Security Vulnerabilities
If you've found an issue that you believe is a security vulnerability in a
released version of CloudStack, please report it to security@apache.org with
details about the vulnerability, how it might be exploited, and any additional
information that might be useful.
For more details, please visit our security page.
License
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Please see the LICENSE file included in the root directory of the source tree for extended license details.
Notice of Cryptographic Software
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See The Wassenaar Arrangement for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included cryptographic software:
- CloudStack makes use of JaSypt cryptographic libraries.
- CloudStack requires a MySQL-compatible database (MariaDB or MySQL), and uses native database encryption functionality.
- CloudStack makes use of the Bouncy Castle general-purpose encryption library.
- CloudStack can optionally interact with and control OpenSwan-based VPNs.
- CloudStack has a dependency on and makes use of JSch - a java SSH2 implementation.