|
37 | 37 | <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> |
38 | 38 |
|
39 | 39 | - [Who Uses CloudStack?](#who-uses-cloudstack) |
40 | | -- [Demo](#demo) |
| 40 | +- [Quick Start / Try It Now](#quick-start--try-it-now) |
41 | 41 | - [Getting Started](#getting-started) |
42 | 42 | - [Getting Source Repository](#getting-source-repository) |
43 | 43 | - [Documentation](#documentation) |
44 | 44 | - [News and Events](#news-and-events) |
45 | 45 | - [Getting Involved and Contributing](#getting-involved-and-contributing) |
| 46 | +- [Project Status](#project-status) |
46 | 47 | - [Reporting Security Vulnerabilities](#reporting-security-vulnerabilities) |
47 | 48 | - [License](#license) |
48 | 49 | - [Notice of Cryptographic Software](#notice-of-cryptographic-software) |
|
53 | 54 |
|
54 | 55 | Apache CloudStack empowers organizations to build and manage highly available, scalable, and secure private, public, and hybrid clouds with unparalleled ease. Transform your infrastructure into a flexible, on-demand service with CloudStack's comprehensive IaaS platform. |
55 | 56 |
|
56 | | -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). |
| 57 | +### Key Features |
| 58 | + |
| 59 | +* **Multi-hypervisor Support**: Manage VMs across VMware vSphere, KVM, XenServer, and Hyper-V from a single pane of glass. |
| 60 | +* **Network-as-a-Service (NaaS)**: Automate virtual networking, load balancing, and firewall services. |
| 61 | +* **Rich API & UI**: Programmatically control your cloud with a robust RESTful API and intuitive web interface. |
| 62 | +* **Storage Management**: Flexible storage options including primary and secondary storage, snapshots, and disaster recovery. |
| 63 | +* **User & Account Management**: Robust multi-tenancy with granular access control for users and accounts. |
| 64 | +* **Resource Accounting & Usage**: Track resource consumption for billing and capacity planning. |
| 65 | + |
| 66 | +### Ecosystem & Integrations |
| 67 | + |
| 68 | +CloudStack integrates seamlessly with your existing infrastructure and tools: |
| 69 | + |
| 70 | +* **Authentication**: LDAP, Active Directory, SAML 2.0. |
| 71 | +* **Storage**: S3-compatible object storage, Ceph, GlusterFS, SolidFire, Dell EMC, NetApp. |
| 72 | +* **Networking**: Juniper, Cisco, F5, NetScaler, OpenDaylight, Tungsten Fabric. |
| 73 | +* **Monitoring & Logging**: Prometheus, Grafana, ELK Stack, Splunk. |
| 74 | +* **Configuration Management**: Ansible, Terraform, Chef, Puppet. |
57 | 75 |
|
58 | 76 | CloudStack currently supports the most popular hypervisors: |
59 | 77 | VMware vSphere, KVM, XenServer, XenProject and Hyper-V as well as |
@@ -144,33 +162,19 @@ via GitHub pull requests. |
144 | 162 |
|
145 | 163 | ## Getting Involved and Contributing |
146 | 164 |
|
147 | | -Interested in helping out with Apache CloudStack? Great! We welcome |
148 | | -participation from anybody willing to work [The Apache Way](https://theapacheway.com) and make a |
149 | | -contribution. Note that you do not have to be a developer in order to contribute |
150 | | -to Apache CloudStack. We need folks to help with documentation, translation, |
151 | | -promotion etc. See our contribution [page](https://cloudstack.apache.org/contribute.html). |
152 | | - |
153 | | -If you are a frequent contributors, you can request to be added as collaborators |
154 | | -(see https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub) |
155 | | -to our GitHub repos. This allows you to use project GitHub with ability to report |
156 | | -issue with tags, and be assigned to issues and PRs. This is done via the .asf.yaml |
157 | | -file in this repo. |
158 | | -You may do so by sharing your GitHub users ID or raise a GitHub issue. |
159 | | - |
160 | | -If you're interested in learning more or participating in the Apache CloudStack |
161 | | -project, the mailing lists are the best way to do that. While the project has |
162 | | -several communications channels, the [mailing lists](https://cloudstack.apache.org/mailing-lists.html) are the most active and the |
163 | | -official channels for making decisions about the project itself. |
164 | | -
|
165 | | -Mailing lists: |
166 | | -- [Development Mailing List](mailto:[email protected]) |
167 | | -- [Users Mailing List](mailto:[email protected]) |
168 | | -- [Commits Mailing List](mailto:[email protected]) |
169 | | -- [Issues Mailing List](mailto:[email protected]) |
170 | | -- [Marketing Mailing List](mailto:[email protected]) |
171 | | -
|
172 | | -Report and/or check bugs on [GitHub](https://github.com/apache/cloudstack/issues) and check our |
173 | | -developer [page](https://cloudstack.apache.org/developers.html) for contributing code. |
| 165 | +We welcome contributions from everyone! Here's how you can get started: |
| 166 | +
|
| 167 | +* **How to Contribute**: Read our [CONTRIBUTING.md](CONTRIBUTING.md) guide for details on code, documentation, and translation contributions. |
| 168 | +* **Mailing Lists**: Join the conversation on our mailing lists. This is where decisions are made. |
| 169 | + * [[email protected]](mailto:[email protected]) - For development discussions. |
| 170 | + * [[email protected]](mailto:[email protected]) - For general usage questions. |
| 171 | + * [[email protected]](mailto:[email protected]) - For issue tracking notifications. |
| 172 | +* **Report Issues**: Found a bug? Report it on [GitHub Issues](https://github.com/apache/cloudstack/issues). |
| 173 | +* **Good First Issues**: New to the project? Check out issues labeled ["good first issue"](https://github.com/apache/cloudstack/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). |
| 174 | +
|
| 175 | +## Project Status |
| 176 | +
|
| 177 | +Apache CloudStack is a mature, actively developed project with a vibrant community. We follow a regular release cadence, typically delivering major feature releases every 6 months, with maintenance releases in between. This ensures a balance of innovation and stability for production environments. |
174 | 178 |
|
175 | 179 | ## Reporting Security Vulnerabilities |
176 | 180 |
|
|
0 commit comments