diff --git a/README.md b/README.md deleted file mode 100644 index 7bce8947345..00000000000 --- a/README.md +++ /dev/null @@ -1,15 +0,0 @@ -# Apache CloudStack - - - -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. - -## Website - -This is a WIP to use github pages to host the CloudStack website -Make pull request to this gh-pages branch and it will build http://apache.github.io/cloudstack diff --git a/about.html b/about.html deleted file mode 100644 index 457266ac00b..00000000000 --- a/about.html +++ /dev/null @@ -1,179 +0,0 @@ - - -
-Apache CloudStack is a top-level project of the Apache Software Foundation (ASF). The project develops open source software for deploying public and private Infrastructure-as-a-Service (IaaS) clouds.
- -CloudStack provides an open and flexible cloud orchestration platform to deliver reliable and scalable private and public clouds. What's that mean, exactly?
- -Apache CloudStack is a Java-based project that provides a management server and agents (if needed) for hypervisor hosts so that you can run an IaaS cloud. Some, but not all, of the features and functionality provided by CloudStack:
- -In short, organizations can use Apache CloudStack to deploy a full-featured public or private IaaS cloud.
- -Apache projects are managed by a Project Management Committee (PMC), and much of the work is done by the project's committers. Note that committer status is not limited to developers, but is conferred to individuals who have made sustained contributions of high quality, and have shown a committment to mentoring other contributors and following The Apache Way.
- -The current Vice President of Apache CloudStack and chair of the PMC is Hugo Trippaers, a full list of PMC members and contributors is available on the page Who We Are.
- - - - -Releases of CloudStack as a Citrix project prior to the project's acceptance into the incubator can be found on SourceForge.net:
- -Please note the releases listed below are NOT Apache project releases. These links are being provided to the user community, as a convenience only.
- - - - - - -1.1. This document defines the bylaws under which the Apache CloudStack project -operates. It defines the roles and responsibilities of the project, who may -vote, how voting works, how conflicts are resolved and specifies the rules for -specific project actions.
- -1.2. CloudStack is a project of the Apache Software Foundation. The foundation -holds the trademark on the name "CloudStack" and copyright on Apache code -including the code in the CloudStack codebase. The foundation FAQ explains the -operation and background of the foundation.
- -1.3. CloudStack operates under a set of principles known collectively as the -"Apache Way". Those principles are: Transparency, consensus, non-affiliation, -respect for fellow developers, and meritocracy, in no specific order.
- -Apache projects define a set of roles with associated rights and -responsibilities. These roles govern what tasks an individual may perform -within the project. The roles are defined in the following sections:
- -2.1. Users
- -The most important participants in the project are people who use our software. -Users can contribute to the Apache projects by providing feedback to developers -in the form of bug reports and feature suggestions. As well, users can -participate in the Apache community by helping other users on mailing lists and -user support forums. Users who participate in the project through any mechanism -are considered to be Contributors.
- -2.2. Contributors
- -Contributors are all of the volunteers who are contributing time, code, -documentation, or resources to the CloudStack Project. Contributions are not -just code, but can be any combination of documentation, testing, user support, -code, code reviews, bug reporting, community organizing, project marketing, or -numerous other activities that help promote and improve the Apache CloudStack -project and community.
- -A Contributor that makes sustained, welcome contributions to the project may be -invited to become a Committer by the PMC. The invitation will be at the -discretion of a supporting PMC member.
- -2.3. Committers
- -The project's Committers are responsible for the project's technical -management. Committers have access to all project source control repositories. -Committers may cast binding votes on any technical discussion regarding the -project (or any sub-project).
- -2.3.1. Committer access is by invitation only and must be approved by a lazy -consensus of the active PMC members.
- -2.3.2. All Apache Committers are required to have a signed Individual -Contributor License Agreement (ICLA) on file with the Apache Software -Foundation. There is a Committer FAQ which provides more details on the -requirements for Committers at Apache.
- -2.3.3. A Committer who makes a sustained contribution to the project may be -invited by the PMC to become a member of the PMC, after approval of the PMC.
- -2.4. Project Management Committee
- -The Project Management Committee (PMC) for Apache CloudStack is responsible to -the board and the ASF for the management and oversight of the Apache CloudStack -codebase.
- -2.4.1. The responsibilities of the PMC include:
- -2.4.1.1. Fostering, supporting and growing the project's community.
- -2.4.1.2. Deciding what is distributed as products of the Apache CloudStack -project. In particular all releases must be approved by the PMC.
- -2.4.1.3. Maintaining the project's shared resources, including the codebase -repository, mailing lists, websites.
- -2.4.1.4. Speaking on behalf of the project.
- -2.4.1.5. Resolving license disputes regarding products of the project.
- -2.4.1.6. Nominating new PMC members and committers.
- -2.4.1.7. Maintaining these bylaws and other guidelines of the project.
- -2.4.1.8. Managing and protecting the project's trademarks and brand.
- -2.4.2. Membership of the PMC is by invitation only and must be approved by a -lazy consensus of active PMC members.
- -2.4.3. A PMC member is considered "emeritus" by their own declaration. An -emeritus member may request reinstatement to the PMC. Such reinstatement is -subject to lazy consensus of the active PMC members.
- -2.4.4. "Active PMC members" are all non-emeritus PMC members.
- -2.4.4. The chair of the PMC is appointed by the ASF board. The chair is an -office holder of the Apache Software Foundation (Vice President, Apache -CloudStack) and has primary responsibility to the board for the management of -the projects within the scope of the CloudStack PMC. The chair reports to the -board quarterly on developments within the CloudStack project. The chair must -be an active PMC member.
- -2.4.5. If the current chair of the PMC resigns, or the term of the current -chair expires, the PMC will attempt to reach consensus on a new chair through -discussion, confirming that consensus via a vote to recommend a new chair using -a lazy 2/3 majority voting method. In the case that consensus is not achieved, -the PMC will vote for a chair using Single Transferable Vote (STV) voting. Due -to the fact that the discussions are about specific individuals, this vote -would be held on the cloudstack-private mailing list. The decision must be -ratified by the Apache board.
- -2.4.6. The role of PMC chair will have a one year term. The intention of this -term is to allow for a rotation of the role amongst the PMC members. This -intention does not prohibit the PMC from selecting the same chair to serve -consecutive terms.
- -This section defines how voting is performed, the types of approvals, and which -types of decision require which type of approval.
- -3.1. Voting
- -3.1.1. Decisions regarding the project are made by votes on the primary project -development mailing list (dev@cloudstack.apache.org). Where necessary, PMC -voting may take place on the private CloudStack PMC mailing list. Votes are -clearly indicated by subject line starting with [VOTE]. Votes may contain -multiple items for approval and these should be clearly separated. Voting is -carried out by replying to the vote mail.
- -3.1.2. Voting may take four flavors:
- -3.1.2.1. +1 "Yes," "Agree," or "the action should be performed." In general, -this vote also indicates a willingness on the behalf of the voter in "making it -happen"
- -3.1.2.2. +0 This vote indicates a willingness for the action under -consideration to go ahead. The voter, however will not be able to help.
- -3.1.2.3. -0 This vote indicates that the voter does not, in general, agree -with the proposed action but is not concerned enough to prevent the action -going ahead.
- -3.1.2.4. -1 This is a negative vote. On issues where consensus is required, -this vote counts as a veto if binding. All vetoes must contain an explanation -of why the veto is appropriate. Vetoes with no explanation are void. It may -also be appropriate for a -1 vote to include an alternative course of action.
- -3.1.3. All participants in the CloudStack project are encouraged to show their -agreement with or against a particular action by voting. For technical -decisions, only the votes of active committers are binding. Non-binding votes -are still useful for those with binding votes to understand the perception of -an action in the wider CloudStack community. For PMC decisions, only the votes -of PMC members are binding.
- -3.1.4. Voting can also be applied to changes made to the CloudStack codebase. -These typically take the form of a veto (-1) in reply to the commit message -sent when the commit is made.
- -3.1.5. Non-binding -1 votes are not considered to be vetos for any decision.
- -3.2. Approvals
- -There are three types of approvals that can be sought. Section 3.4 describes -actions and types of approvals needed for each action.
- -3.2.1. Lazy Consensus - Lazy consensus requires 3 binding +1 votes and no -binding -1 votes.
- -3.2.2. Lazy Majority - A lazy majority vote requires 3 binding +1 votes and -more binding +1 votes than binding -1 votes.
- -3.2.3. Lazy 2/3 Majority - Lazy 2/3 majority votes requires at least 3 binding -votes and twice as many binding +1 votes as binding -1 votes.
- -3.3. Vetoes
- -3.3.1. Vetoes are only possible in a lazy consensus vote.
- -3.3.2. A valid, binding veto cannot be overruled. If a veto is cast, it must be -accompanied by a valid reason explaining the reasons for the veto. The validity -of a veto, if challenged, can be confirmed by anyone who has a binding vote. -This does not necessarily signify agreement with the veto - merely that the -veto is valid.
- -3.3.3. If you disagree with a valid veto, you must lobby the person casting the -veto to withdraw their veto. If a veto is not withdrawn, any action that has -been vetoed must be reversed in a timely manner.
- -3.4. Actions
- -This section describes the various actions which are undertaken within the -project, the roles that have the right to start a vote on the action, the -corresponding approval required for that action and those who have binding -votes over the action.
- -3.4.1. Technical Decisions
- -A technical decision is any decision that involves changes to the source code -that we distribute in our official releases.
- -Technical decisions should normally be made by the entire community using -discussion-lead consensus gathering, and not through formal voting.
- -Technical decisions must be made on the project development mailing list.
- -During the consensus gathering process, technical decisions may be vetoed by -any Committer with a valid reason.
- -If a formal vote is started for a technical decision, the vote will be held as -a lazy consensus of active committers.
- -Any user, contributor, committer, or PMC member can initiate a technical -decision making process.
- -3.4.2. Non-Technical Decisions
- -A non-technical decisions is any decision that does not involve changes to the -source code that we distribute in our official releases (excluding questions of -trademark usage).
- -Non-technical decisions should normally be made by the entire community using -discussion-lead consensus-building, and not through formal voting.
- -Non-technical decisions can be made on whichever project mailing list is most -appropriate.
- -Non-technical decisions cannot be vetoed, but if there is strong opposition -a formal vote can be used to resolve the dispute.
- -If a formal vote is started for a non-technical decision, the vote will be held -as a lazy 2/3 majority of active committers.
- -Any user, contributor, committer, or PMC member can initiate a non-technical -decision making process.
- -3.4.3. Release Plan
- -Defines the timetable and work items for a release. The plan also nominates a -Release Manager.
- -A lazy majority of active committers is required for approval.
- -Any active committer or PMC member may call a vote. The vote must occur on the -project development mailing list.
- -3.4.4. Product Release
- -When a release of one of the project's products is ready, a vote is required to -accept the release as an official release of the project.
- -Lazy Majority of active PMC members is required for approval.
- -Any active committer or PMC member may call a vote. The vote must occur on the -project development mailing list.
- -3.4.5. Adoption of New Codebase
- -When the codebase for an existing, released product is to be replaced with an -alternative codebase. If such a vote fails to gain approval, the existing code -base will continue.
- -This also covers the creation of new sub-projects within the project.
- -Lazy 2/3 majority of active PMC members.
- -Any active committer or PMC member may call a vote. The vote must occur on the -project development mailing list.
- -3.4.6. New Committer
- -When a new committer is proposed for the project.
- -Lazy consensus of active PMC members.
- -Any active PMC member may call a vote. The vote must occur on the PMC private -mailing list.
- -3.4.7. New PMC Member
- -When a committer is proposed for the PMC.
- -Lazy consensus of active PMC members.
- -Any active PMC member may call a vote. The vote must occur on the PMC private -mailing list.
- -3.4.8. Committer Removal
- -When removal of commit privileges is sought. Note: Such actions will also be -referred to the ASF board by the PMC chair
- -Lazy 2/3 majority of active PMC members (excluding the committer in question if -a member of the PMC).
- -Any active PMC member may call a vote. The vote must occur on the PMC private -mailing list.
- -3.4.9. PMC Member Removal
- -When removal of a PMC member is sought. Note: Such actions will also be -referred to the ASF board by the PMC chair.
- -Lazy 2/3 majority of active PMC members (excluding the member in question)
- -Any active PMC member may call a vote. The vote must occur on the PMC private -mailing list.
- -3.4.10. Modifying Bylaws
- -Modifying this document.
- -Lazy majority of active PMC members
- -Any active committer or PMC member may call a vote. The vote must occur on the -project development mailing list.
- -3.4.11. Trademark Usage Approvals
- -Our project maintains a formal Trademark Usage Guidelines document, which -serves as a additive reference to the Apache Software Foundation's trademark -policies. The Apache CloudStack PMC has had approval authority delegated to it -for requests from third parties to use our trademarks. It is the PMC's -responsibility to provide these approvals, and to ensure that any requests -are in compliance with both the project and the foundation's trademark -usage policies.
- -The CloudStack Trademark Guidelines specify how a requestor is expected to -request permission for usage of the trademarks.
- -The process of approval will typically be as follows:
- -In situations where a concern is raised, the PMC member is expected inform the -requster that there is some discussion that needs to be had prior to approval -from the PMC. This notice serves to end the assumed approval after 72 hours.
- -After raising a concern, the PMC member in question is required to forward the -concern to private@cloudstack.apache.org, explaining the issue that they have -with the request. The use of private@cloudstack.apache.org for discussing the -request is to allow the PMC to deliberate without confusing the requester, and -to ensure that a formal approval or denial is clear at the end of the -discusion.
- -The PMC will then attempt to achieve consensus on how the request for approval -will be answered. The requester may be asked for more information to help the -PMC make a decision, may be asked to make a change to the proposal in order to -gain approval, or may have their request be denied.
- -If consensus is not achieved within the PMC by discussion, then a formal VOTE -can be called as a Lazy 2/3 majority of voting PMC members.
- -Votes related to trademark usage approvals may be performed on the -private@cloudstack.apache.org mailing list.
- -3.5. Voting Timeframes
- -Formal votes are open for a period of at least 72 hours to allow all active -voters time to consider the vote.
- - - - -This page is for Frequently Asked Questions (FAQ) having to do with Apache CloudStack as a project and its use.
- -Have a question that's not answered here? You might want to ask on the CloudStack users mailing list.
- -Apache CloudStack is a complete software suite for creating Infrastructure as a Service (IaaS) clouds. Target environments include service providers and enterprises.
- -The CloudStack platform includes the Management Server and extensions to industry-standard hypervisor software (e.g. XenServer, vSphere, KVM) installed on Hosts running in the cloud. The Management Server is deployed on a farm of management servers. The administrator provisions resources (Hosts, storage devices, IP addresses, etc.) into the Management Server and the Management Server manages those resources. The Management server presents web interfaces to end users and administrators that enable them to take actions on some or all of their instances in the IaaS cloud.
- -Yes. Every template has a privacy level associated with it. Privacy levels include:</a>
- -Administrators and end users can add templates to the system. Users can see the template owner when viewing the template.
- -(Templates define the base OS image that will be used when a guest is first booted. For example, a template might be a 64-bit version of CentOS 5.3.)
- -Apache CloudStack users are assigned accounts. An account is typically a customer of the service provider or a department in a large organization. Accounts are the unit of isolation in the cloud. Accounts are grouped by domains. Domains usually contain accounts that have some logical relationship to each other and a set of delegated administrators with some authority over the domain and its subdomains. For example, a service provider with several resellers could create a domain for each reseller.
- -Multiple users can exist in an account. Users are like aliases in the account. Users in the same account are not isolated from each other. Most installations need not surface the notion of users; they just have one user per account.
- - - - -title: Apache CloudStack: Getting Involved -—
- -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, and having someone with snazzy Web design skills would not be a bad thing! Want to give a talk about Apache CloudStack, or even organize a CloudStack event? We're all ears – join us on the Marketing list and we'll help you get started!
- -Developers, of course, are also welcome. See the Developer Resources page!
- -If you just want to report a bug, that's easily done in our Jira bug tracking tool.
- -Need some help getting started? Feel free to ask on the mailing list or find us on one of the following IRC channels on irc.freenode.net:
- -If you're a committer on an Apache project, it means that you can commit directly to the project's repository. For instance, with Apache CloudStack committers are allowed to directly push commits into the git repository.
- -Non-committers, however, have to submit patches for review. Don't worry, it's not an onerous process at all. The first time you submit a patch, it will take a minute or two to create an account on Review Board, but it's a piece of cake from start to finish.
- -For the purpose of this post, we'll assume that you already have a system with Git and have found a bug to fix or have a feature that you'd like to submit, and you're willing to contribute that code or documentation under the Apache License 2.0.
- -Further, if you're fixing a bug we'll assume that you've either filed a bug report or are submitting a fix for a known bug. If you find a bug and would like to fix it, that's awesome! Please be sure to file the bug too, though.
- -If you want to add a feature, you should bring it up for discussion on the dev@cloudstack.apache.org mailing list before implementing it. This ensures that it meshes with the plans that other contributors have for Apache CloudStack, and that you're not doing redundant work. Other developers may also have ideas for the feature or suggestions that will help you land the feature without having to re-do the work. More information about our mailing lists can be found here.
- -In short, communication is a vital part of making a contribution to an Apache project.
- -First, lets make sure that you've added your name and email to your `~/.gitconfig`:
- --$ git config --global user.name "Your Name" -$ git config --global user.email you@domain.com -- -
You'll grab the CloudStack source with git:
- --$ git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git -- -
If you already have the source, make sure you're working with the most recent version. Do a `git pull` if you cloned the source more than a few hours ago. (Apache CloudStack development can move pretty fast!)
- --$ git checkout -b mybranch -- -
This does two things: One, it creates the branch mybranch and two, it changes your working branch to mybranch. Running `git branch` will show you which branch you're working on, with an asterisk next to the active branch, like so:
- --[user@localhost cloudstack]$ git branch - master - * mybranch -- -
Make whatever changes you're going to make, be sure to use git add to stage the changes, and then you're going to commit the changes to your working branch:
git commit -m "Insert a meaningful summary of changes here."- -
Finally, you're going to create a patch to upload to Review Board:
- -git format-patch master --stdout > ~/patch-name.patch- -
Review Board is the main method of sending patches to the Apache CloudStack project. That's not to say that a patch sent directly to the mailing list will be ignored, but the strong preference is that patches be submitted through Review Board. Don't worry, it's a very easy tool to use.
- -If you haven't already, create an account with Review Board. Registering only requires an email address, first name, and last name. After you're registered, head to New Review Request and select the repository (cloudstack-git) and upload the patch (diff) created with git.
- -Click Create Review Request and then fill out the information required. Specifically:
- -The Summary will be the subject that's sent to the cloudstack-dev mailing list. So if your summary is "fixed feature foo" the subject of the mail sent to the list will be "Review Request: fixed feature foo". Try to be descriptive with the Summary. If you're submitting a patch for a bug, please be sure to include the bug number in the summary. (Like "Bugfix CS-15942: Fixing problem with redundant routers.")
- -The description should be a full description of what you've done. Please be specific, and include enough information that any reviewer will be able to look at your patch without asking for follow-up information. You need to include the bug ID that your patch relates to as well (ex: CLOUDSTACK-XXX ).
- -If you're submitting a patch that modifies code, adds features, etc. you should test before submitting. Please be sure to describe your tests here.
- -Once you're sure everything is OK, go ahead and submit the patch. But that's not the end of the process. The work isn't done until the patch is committed!
- -Once you've submitted your patch, you should receive a response within a few days. If you receive no response within a week, please ping the cloudstack-dev mailing list. One of the features of Review Board is that shows all of the requests and when they were posted, and the committers know that they should be responsible for reviewing patches in a timely fashion.
- -When your patch is reviewed, it may be accepted as-is or you may be asked to make changes. If you're asked to make changes, please work with the committer to see the patch through to acceptance.
- -If the patch is accepted and committed, you have one last task (don't worry, it's minor and kind of satisfying).
- -Go back to Review Board, click My Dashboard and then Outgoing Reviews. Go to your submission, you should see a "Ship it!" message from the reviewer. Click the Close button and choose Submitted. The status has now changed from pending to submitted.
- -That's it – you've helped make Apache CloudStack a better project. Thanks!
- -If you are new to git you might want to watch this screencast:
- - - -You might want to peruse the Get Involved page on Apache.org, and the On Contributing Patches doc as well. Note that some of that does not apply to Apache CloudStack, as we're using git rather than Subversion. But do respect the original style of the CloudStack code, and ensure that you're using spaces rather than tabs, and your patches have Unix line endings (LF) rather than Windows-type line endings (CRLF).
- -The git repositories are hosted on Apache infrastructure, and can be found here:
- -To get the most recent source for Apache CloudStack, use:
- --git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git -- -
Similarly, clone the cloudstack-cloudmonkey repository to get access to the most recent source for CloudMonkey.
- -For projects related to Apache CloudStack, see the CloudStack-extras repositories on GitHub.
- -Apache CloudStack's most current release is 4.5.1. -
- - - - - - -For easier installation or upgrades, the official source code release has been supplemented by community members who have chosen to provide package repositories.
- -Instructions for using these community provided repositories can be found in the Configure Package Repository section of the Installation Guide.
- -Full release notes can be found in the Version 4.5.1 Release Notes document.
- -Instructions for building from source and installing Apache CloudStack can be found in the Installation Guide.
- -Instructions for building from source and upgrading from a previous version of CloudStack to Apache CloudStack 4.5.1 can be found in the upgrade section of the Release Notes.
- - -Full release notes can be found in the Version 4.4.2 Release Notes document.
- -Instructions for building from source and installing Apache CloudStack can be found in the Installation Guide.
- -Instructions for building from source and upgrading from a previous version of CloudStack to Apache CloudStack 4.4.2 can be found in the upgrade section of the Release Notes.
- - -Full release notes can be found in the Version 4.3.2 Release Notes document.
- -Instructions for building from source and installing Apache CloudStack can be found in the Installation Guide.
- -Instructions for building from source and upgrading from a previous version of CloudStack to Apache CloudStack 4.3.2 can be found in the upgrade section of the Release Notes.
- - --It's essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. -The PGP signatures can be verified using PGP or GPG. First download the -KEYS as well as the asc -signature file for the relevant distribution. Make sure you get these files from the -main distribution directory, rather than from a mirror. Then verify the signatures using: -
-- % pgpk -a KEYS - % pgpv apache-cloudstack-X.X.X-src.tar.bz2.asc --
or
-- % pgp -ka KEYS - % pgp apache-cloudstack-X.X.X-src.tar.bz2.asc --
or
-- % gpg --import KEYS - % gpg --verify apache-cloudstack-X.X.X-src.tar.bz2.asc --
-Additionally, you can verify the MD5 or SHA512 signatures on the files. -
- -Apache CloudStack's CloudMonkey tool is a CLI and shell environment designed for interacting with CloudStack-based clouds.
- -CloudMonkey's most current release is 5.3.1.
- - - -Instructions for building and installing from source can be found in the included README.md file.
- -For easier installation or upgrades, the official source code release has been supplemented by community members who have pushed the python package to the Python Package Index.
- -For installing the package from pypi, use:
- -$ pip install cloudmonkey
-
-
-To upgrade:
- -$ pip install --upgrade cloudmonkey
-
-
-Though a clean upgrade is recommended:
- -$ pip uninstall cloudmonkey
-$ pip install cloudmonkey
-
-
-
-
-As a mature and turnkey Infrastructure-as-a-Service (IaaS) platform, Apache CloudStack has a comprehensive set of features. This is an extensive, but not exhaustive, set of features.
- -Have a feature request? We'd invite you to bring it up on the mailing list, and consider filing a feature request in our bug tracker.
- -
-Feature- |
-
-Description- |
-
| Rich Management User Interface | -CloudStack provides a feature-rich out-of-the-box user interface implemented on top of the CloudStack API to manage the cloud infrastructure. It is a fully AJAX based solution compatible with most of the latest internet browsers and can also be easily integrated with your existing portal. | -
| Brand-able Self Service User Interface | -Our out-of-the-box user interface was built using standard HTML and CSS with jQuery as our standard JavaScript library. It can be easily customized and branded to mirror your company’s existing look and feel. | -
| Secure AJAX Console Access | -A VNC AJAX client that allows users to access their virtual machine using any of the latest internet browsers without the need of any external add-on such as a JRE, ActiveX, or Flash. | -
| Powerful API | -Easily build, integrate, and use applications built on top of the CloudStack API. The CloudStack API is well-documented and extensible. CloudStack also includes support for the Amazon EC2 and S3 APIs. | -
| Secure Single Sign On | -Aggregate and integrate your existing applications with our management user interface via our secure single sign-on for a better user experience. | -
| Multi-role Support | -Three distinct account roles for user interface and API access are supported out-of-the-box:
-
|
-
| On Demand Virtual Data center Hosting | -Provides users with virtually unlimited amount of computing resources – on demand, as required and billed by actual usage. | -
| Dynamic Workload Management | -Completely automates the distribution of compute, network, and storage resource across the physical infrastructure while adhering to defined policies on load balancing, data security, and compliance. | -
| Broad network Virtualization Capabilities | -Support for embedded software-based network management as well as VLAN. Our Direct Attached IP enables you to integrate with a virtual network architecture that best fits your needs. | -
| MPLS Support in the Cloud | -CloudStack allows you to dedicate an entire VLAN to a specific account for MPLS support between network nodes. | -
| Secure Cloud Deployments | -Ensures that all memory, CPU, network, and storage resources are both available and isolated from one user account to another within the cloud. | -
| Hypervisor Agnostic | -CloudStack provides you with the flexibility to allow you to integrate with the major hypervisors in the market today including VMware, KVM, Citrix XenServer, and Citrix Xen Cloud Platform. | -
| Easy Template Creation Process | -The CloudStack User Interface allows you to easily create pre-defined templates for efficient virtual machine deployments. Templates can be created by attaching a guest OS ISO to a blank VM or directly from existing VMs in the cloud. | -
| Rich Template and ISO Management | -Both users and administrators will be able to upload and manage their OS templates and ISO images from within the cloud. A few management features include the ability to allow others to use the templates/ISOs either on a global public level or on a per-account basis, and to allow the management of templates across multiple zones. CloudStack will ensure that templates are automatically copied to the appropriate storage servers. | -
| Domains and Delegated Administration | -The support for domains allows you to segregate your cloud resources and delegate the management of these domains to other administrators. | -
| Snapshot Management | -To help mitigate data loss and a way of disaster recovery, users are given the capability of either taking ad hoc snapshots of their disk volumes or setting up a comprehensive schedule for taking periodic snapshots of their data. Users can set limits to the number of snapshots taken to creating new data disk volumes from existing snapshots. | -
| Comprehensive Service Management | -Administrators can define, meter, deploy, and manage multiple service and disk offerings within the cloud. | -
| VM Sync and High Availability | -Our custom VM Sync technology constantly monitors and maintains the state of all virtual machines within the cloud from notifications of individual VM status to the ability to automatically ensure that the VM remains running. | -
| Resource Over Provisioning and Limits | -By leveraging existing hypervisor, storage, and network technologies, you can configure the cloud to allow over provisioning of physical resources to optimize the allocation of your virtual machines.
- CloudStack also provides administrators the capability of limiting virtual resources (such as the number of VMs that an account can create to the number of public IP addresses an account can own). - |
-
| Usage Metering | -Be able to deliver real-time visibility, produce historical usage reports, and create billing invoices by integrating with metering data generated by the CloudStack Usage Engine. | -
| Alerts and Notifications | -With built-in cloud system monitoring processes, you will be able to receive up-to-the-minute alerts such as reaching a certain physical resource threshold or detecting machine failures through the CloudStack API and/or via email using SMTP. | -
| Virtual Routers, Firewalls and Load Balancers | -CloudStack supports integration with both software and hardware firewalls and load balancers to provide additional security and scalability to a user’s cloud environment. Including F5 and Netscaler | -
| Multiple Storage Solutions | -CloudStack supports many storage solutions with iSCSI and NFS being preferred, but anything that can have multiple nodes mount it simultaneously will work. This gives you the ultimate freedom in deciding your storage servers from using commodity hardware to integrating with enterprise-grade solutions such as Dell EqualLogic or NetApp. | -
| Storage Tiering | -As part of the CloudStack’s ability to integrate with multiple storage solutions, you will also be able to target specific storage servers to be used for VM deployments. This can be extremely beneficial when you have storage servers built with commodity hardware to support non disk intensive applications and dedicate fast and robust hardware for disk intensive applications such as databases. | -
| Block Storage Volumes | -CloudStack supports the creation of block storage volumes of arbitrary size on both network attached storage (NAS) or local disk that can be attached and detached to and from your virtual machine. | -
| Wide Range Guest VM OS Support | -Depending on the configured hypervisor, CloudStack supports a wide range of guest operating system including Windows®, Linux®, and various versions of BSD®. | -
| Event/Audit Logs | -All user interactions via the CloudStack UI or API are recorded as events. Each event will indicate the type, severity level, description, owner of the resource, the user that initiated the action, and when the event occurred. | -
| User Data Support | -CloudStack supports the notion of allowing a user to submit any type of binary user data when deploying a new virtual machine. This gives you the flexibility of giving each virtual machine created from the same OS template its own identity in the cloud. | -
| Guest OS Preferences | -To take advantage of today’s hardware and OS licensing models, CloudStack allows administrators to identify physical hosts to “prefer” specific operating systems. For example this means that whenever possible, your Windows based operating systems will be instantiated on all hosts that have been identified as Windows “preferred.” | -
| Host Maintenance with Live Migration | -Upgrades and hardware maintenance can be achieved on the cloud with no downtime for guest VMs. CloudStack will live-migrate any VMs from hosts that have been targeted for maintenance to prevent any disruption of service. | -
| Flexible Adapter Framework | -The CloudStack was built from the ground up to support integration with a variety of hypervisors, storage, network, and authentication solutions. Due to this flexibility, we have created an Adapter Framework that will easily allow you to further customize the cloud to suit your business needs. | -
| Random Password for Guest OS | -You can further enhance your guest OS templates to include our custom random password feature that will automatically generate a unique password upon the creation of a VM. This will allow your customers to securely log in and change their password. Both Windows and Linux based OS platforms are currently supported. | -
| OpenStack Swift Integration for Secondary Storage | -Secondary storage (templates and VM snapshots) can be stored in OpenStack Swift as an alternative to NFS. | -
| Projects | -Allow users to collaborate and share resources within a defined group or "project". When a user creates an a project all usage under the project is attributed to the account who becomes the project owner. | -
| Clustered LVM Support | -CloudStack can utilize clustered Logical Volume Manager (LVM) storage configurations starting with version 3.0. | -
| NetScaler Support | -CloudStack supports MPX, VPX & SDX devices. Users can set up Layer-4 load balancing rules. Supported protocols: HTTP, TCP & UDP; Algorithms: least loaded and round robin; Persistent sessions: source IP based, cookie based. | -
| Network As a Service |
-Admin can compose network offerings with different network behaviors. For example, a basic network offering with CloudStack Virtual Router offering network services and a high-performance network offering with physical devices such as NetScaler and Juniper SRX. Users can select the network offering of choice while deploying a VM and also migrate VMs from one network offering to another. | -
| LDAP Integration |
-CloudStack supports LDAP authentication as a built-in optional AUTH adapter | -
| Notification & Capacity Thresholds |
-Admin can set notification threshold to receive an alert when resource pool crosses the notification threshold. Capacity threshold prevents CloudStack from allocating further resources to that pool. | -
The CloudStack project began as a project of a start-up known as VMOps in 2008. The company eventually changed its name to Cloud.com, and it released much of the source to CloudStack in May 2010 under the GNU General Public License version 3 (GPLv3).
- -Cloud.com was purchased in July 2011 by Citrix, and the remainder of CloudStack's code was released (again, under the GPLv3) in August 2011. Citrix released CloudStack 3.0 in early 2012.
- -In April 2012, Citrix re-licensed CloudStack under the Apache Software License 2.0 (ASLv2) and submitted CloudStack to the Apache Incubator. It was accepted into the Incubator on April 16th, 2012.
- -After getting its infrastructure and community processes in place, CloudStack made its first major release (4.0.0-incubating) from the Apache Incubator on November 6th, 2012. The first minor release (4.0.1-incubating) came out on February 12, 2013.
- -Apache CloudStack graduated from the Incubator on March 20, 2013, and the announcement was released on March 25, 2013.
- - - - - -Open Source Cloud Computing™
- -
-
- -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, KVM, XenServer, Xen Cloud Platform (XCP) and Hyper-V. -
- --Users can manage their cloud with an easy to use Web interface, command line tools, and/or a full-featured RESTful API. In addition, CloudStack provides an API that's compatible with AWS EC2 and S3 for organizations that wish to deploy hybrid clouds. -
- - - -- Learn more about getting involved with Apache CloudStack on the Contributing to Apache CloudStack page, or go straight to our Developer Resources page. -
-- In 2015, five CloudStack Days events will be held across the globe. Each one-day event will feature morning plenary sessions, afternoon breakout sessions in user and developer tracks and a hackathon. Learn more at: -
- --
- View videos from the CloudStack Collaboration Conference Europe 2014 -
- -- -
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. "If it didn't happen on a mailing list, it didn't happen."
- -The project currently has several lists:
- -The preferred language to use on the lists above is English. To support the global nature of the CloudStack user community, we also have the following regionally specific user lists:
- -If you want to subscribe to list, send an email to listname-subscribe@cloudstack.apache.org:
- -Decided you're getting too much mail? To unsubscribe from one of the lists, send an email to listname-unsubscribe@cloudstack.apache.org from the same email you subscribed with.
- -Please do not send emails to the list asking for someone to unsubscribe you.
- -We expect all participants on the mailing list to treat one another professionally and politely.
- - - - -The Apache CloudStack project understands that as a core infrastructure project, the application security of Apache CloudStack is of critical importance to the community and users.
- -The PMC has decided to create a "Security Team" for CloudStack. The Security Team's charter is to manage the response to vulnerabilities reported with Apache CloudStack. This includes communication with the report, issue verification, issue correction, public communication creation, and vendor coordination. The Security Team may ask assistance from other community members to help verify or correct a reported issue.
- -Members of the PMC are eligible to join the security team, but lurking is discouraged.
- -Community members engaged by the Security Team are expected to hold the issue in confidence until public announcement of the vulnerability. This protects the users of the software and gives reasonable time for the response process to be implemented. Further information can be found on the ASF's How it Works page.
- -The CloudStack security team works closely with, and under the direction of, the ASF security team.
- -If you've found an issue that you believe is a security vulnerability in a released version of CloudStack, please report it to security@cloudstack.apache.org with details about the vulnerability, how it might be exploited, and any additional information that might be useful.
- -Upon notification, the ACS security team will initiate the security response procedure. If the issue is validated, the team generally takes 2-4 weeks from notification to public announcement of the vulnerability. During this time, the team will communicate with you as they proceed through the response procedure, and ask that the issue not be announced before an agreed-upon date.
- -The security team asks that you please do not create publicly-viewable JIRA tickets related to the issue. If validated, a JIRA ticket with the security flag set will be created for tracking the issue in a non-public manner.
- -title: Apache CloudStack: Open Source Cloud Computing -—
- -
-Apache CloudStack is open source software that forms the foundation for infrastructure clouds. Data center operators can quickly and easily build cloud services within their existing infrastructure to offer on-demand, elastic cloud services. Enterprises can use CloudStack to take on hybrid workloads, making it easier to manage legacy workloads while spinning up workloads that take advantage of the cloud model.
CloudStack users can take full advantage of cloud computing to deliver higher efficiency, limitless scale and faster deployment of new services and systems to the end-user. CloudStack allows user to coordinate virtualized servers, networking and network storage to provide infrastructure-as-a-service (IaaS) just like hosting providers – but on their own hardware.
- -CloudStack is an open source cloud operating system which delivers public cloud computing similar to Amazon EC2 but using your own hardware. CloudStack provides orchestration of your virtualized resources into one homogeneous environment where you can delegate the creation to users of the virtual machines using the self-service CloudStack portal.
- -CloudStack provides powerful features for enabling a secure multi-tenant cloud computing environment. With one click virtual servers can be deployed from a pre-defined template. Virtualized instances can be shutdown, paused and restarted via the web interface, the command line or by calling the extensive CloudStack API.
- -CloudStack can be used for multiple purposes:
- -All these capabilities are a result of years of development and collaboration by the Cloudstack development team with cloud computing users to deploy some of the largest, most scalable private and public cloud computing environments in the world.
- -For a full list of features, see our feature list.
- -You can get started with CloudStack immediately. See our downloads page for source code and convenience binaries.
- - - - -Apache CloudStack, CloudStack, the CloudStack word design, the Apache -CloudStack word design, the cloud monkey logo, either separately or in -combination are hereinafter referred to as "CloudStack Trademarks" and -are trademarks or registered trademarks of the Apache Software -Foundation. Excepting the provisions outlined below you may not use the -CloudStack trademarks or any confusingly similar mark as a trademark for -your product, to imply endorsement by the project, or use the CloudStack -trademarks in any other manner that might cause confusion in the -marketplace.
- -Trademark law dictates that owners must police their marks or risk the -loss of the marks.
- -The Apache Software Foundation has an established trademark policy -(http://www.apache.org/foundation/marks) -that when in conflict should be considered the canonical standard (with one -exception noted below).
- -However, the Apache Software Foundation has given the responsibility for -brand management to the project's Project Management Committee. Thus -this document should be taken as additive to the Apache Software -Foundation's trademark guideline. Nothing contained herein provides an -exception to those guidelines (again, with one exception below).
- -Exception: The Apache CloudStack PMC is the contact point for all requests -related to the use of the CloudStack Trademarks. In places where the Apache -Software Foundation's formal trademark usage documentation and policies specify -trademarks@apache.org, requesters should use press@cloudstack.apache.org or -private@cloudstack.apache.org. In places where the Apache Software -Foundation's policies specify that explicit approval must come from the VP -Brand Management, requesters will be given authoritative approval from a -representative of the Apache CloudStack PMC instead. The Apache Software -Foundation has delegated approval authority to the Apache CloudStack PMC, -specifically related to the CloudStack Trademarks.
- -The word 'CloudStack' is a registered trademark, -and should use the '®' symbol. In places where that symbol is not -reasonably used it is acceptable to use '(R)' as an alternative.
- -The CloudStack word design, the Apache CloudStack word design, the -'Apache CloudStack' wordmark and the -cloud monkey logo are all trademarks and should not appear without the -'™' symbol being present.
- -The Apache CloudStack logo with the "TM" symbol present may be -downloaded here:
- -Apache CloudStack committers may, without prior approval, use the -CloudStack Trademarks to promote exhibits or sessions at events with the -aim to promote Apache CloudStack, though the general adherence to the -ASF's trademark guidelines is still required.
- -Sponsoring events can provide good visibility for the project, however -it frequently requires funds that the project does not have access to. -Many outside organizations wish to provide this type of visibility.
- -The following is required:
- -The following is required:
- -Local area user events are encouraged.
- -Creating non-software goods (e.g.: stickers, event give-aways, etc…) to help -promote the Apache CloudStack project is encouraged. However, there are some -requirements that must be met prior to producing the goods. Additionally, -goods bearing any of the CloudStack marks may not be sold without explicit -written permission.
- -The following is required:
- -No additional guidelines are required above and beyond the -Third Party Domain Name Branding Policy. -In general:
- --- - - - -you may not use Apache marks such as "ApacheFoo" or "Foo" in your own -domain names if that use would be likely to confuse a relevant consumer -about the source of software or services provided through your domain -with products or services provided by the Apache Foo project or the -Apache Software Foundation as a whole. You should apply the -"likelihood of confusion" test described in our -formal Trademark Policy, and -please realize that the use of Apache marks in third party domain -names is generally not "nominative fair use."
-
The following organisations are known users of 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, organisations who have used Cloudstack to build their own private clouds, and systems integrators that offer CloudStack related services.
- -Are you using CloudStack ?
- -If you are using CloudStack in your organisation and your company isn’t listed here, please complete our brief adoption survey. We’re happy to keep your company name anonymous if you require.
- -Noticed Something wrong ?
- -If you noticed something wrong with your entry here (or if you’d like us to remove it), please complete our adoption survey. We will use the information you give us in this survey to update the contents of this page
- -Looking for more info on Apache CloudStack? We've collected a number of videos that explore and explain Apache CloudStack.
- -A short introduction to Apache CloudStack, and some of the people who help create it.
- - - -Chiradeep Vittal discusses Apache CloudStack's architecture at a CloudStack Developer On-Ramp. The first of two videos.
- - - -Alex Huang talks about CloudStack architecture at a CloudStack Developer On-Ramp. This is the second of two videos.
- - - - - - - -This page includes all of the Apache CloudStack Project Management Committee (PMC) members and committers, and their ASF usernames.
- -** Alex Huang ** (ahuang)
- -** Alex Karasulu ** (akarasulu)
- -** Alena Prokharchyk ** (alena1108)
- -** Animesh ** (animesh)
- -** Chip Childers ** (chipchilders)
- -** Chiradeep Vittal ** (chiradeep)
- -** Daan ** (dahn)
- -** Ian Duffy ** (duffy)
- -** Disheng Su ** (edison)
- -** Giles Sirett ** (giles)
- -** Go Chiba ** (gochiba)
- -** Matt Richard Hogstrom ** (hogstrom)
- -** Hugo Trippaers ** (hugo)
- -** Ilya Musayev ** (ilya)
- -** John Burwell ** (jburwell)
- -** Jim Jagielski ** (jim)
- -** John Kinsella ** (jlk)
- -** Joe Brockmeier ** (jzb)
- -** David Nalley ** (ke4qqq)
- -** Kevin Kluge ** (kluge)
- -** Marcus Sorensen ** (mlsorensen)
- -** Mohammad Nour El-Din ** (mnour)
- -** Mark R. Hinkle ** (mrhinkle)
- -** Mike Tutkowski ** (mtutkowski)
- -** Noah Slater ** (nslater)
- -** Olivier Lamy ** (olamy)
- -** Pierre-Luc Dion ** (pdion891)
- -** Rajani Karuturi ** (rajani)
- -** Sebastien Goasguen ** (sebgoa)
- -** Prasanna ** (tsp)
- -** Wido den Hollander ** (widodh)
- -** William Chan ** (willchan)
- -** Ahmad Emneina ** (ahmad)
- -** Amogh Vasekar ** (amoghvk)
- -** Anthony Xu ** (anthonyxu)
- -** Abhinandan Prateek ** (aprateek)
- -** Brian Federle ** (bfederle)
- -** Rohit Yadav ** (bhaisaab)
- -** Brett Porter ** (brett)
- -** Clayton Weise ** (claytonweise)
- -** Chris Suich ** (csuich2)
- -** Darren Shepherd ** (darren)
- -** Dave Cahill ** (dcahill)
- -** Demetrius Tsitrelis ** (demetriust)
- -** Devdeep Singh ** (devdeep)
- -** Wilder Rodrigues ** (ekho)
- -** Erik Weber ** (erikw)
- -** Xin Zhang ** (frankzhang)
- -** Gavin Lee ** (gavinlee)
- -** Girish Prabhakar Shilamkar ** (girish)
- -** Gaurav Nandkumar Aradhye ** (guarav)
- -** Harikrishna Patnala ** (harikrishna)
- -** Toshiaki Hatano ** (haeena)
- -** Geoff Higginbottom ** (higster)
- -** Isaac Chiang ** (isaacchiang)
- -** Jayapal ** (jayapal)
- -** Jason Bausewein ** (jbausewein)
- -** Jessica Wang ** (jessicawang)
- -** Jessica Tomechak ** (jtomechak)
- -** Karen Vuong ** (karenv)
- -** Hiroaki Kawai ** (kawai)
- -** Kelcey Damage ** (kdamage)
- -** Kelven Yang ** (kelveny)
- -** Kirk Kosinski ** (kirk)
- -** Kishan ** (kishan)
- -** Laszlo Hornyak ** (kocka)
- -** Koushik Das ** (koushik)
- -** Likitha Shetty ** (likithas)
- -** Min Chen ** (mchen)
- -** Mice Xia ** (mice)
- -** Bruno Demion ** (milamber)
- -** Murali Mohan Reddy ** (muralireddy)
- -** Nitin ** (nitin)
- -** Noa Resare ** (noa)
- -** Nux ** (nux)
- -** Olga Smola ** (olgasmola)
- -** Paul Angus ** (paul_a)
- -** Phong Nguyen ** (pnguyen)
- -** Prachi Damle ** (prachidamle)
- -** Pranav Saxena ** (pranavs)
- -** Pierre-Yves Rischard ** (pyr)
- -** Radhika Nair ** (radhika)
- -** Rajesh Battala ** (rajeshbattala)
- -** Remi Bergsma ** (remi)
- -** Rene Moser ** (resmo)
- -** Sailaja Mada ** (sailajamada)
- -** Saksham Srivastava ** (saksham)
- -** Sangeetha Hariharan ** (sangeethah)
- -** Sanjay Tripathi ** (sanjaytripathi)
- -** Sanjeev Neelarapu ** (sanjeev)
- -** Santhosh ** (santhoshedukulla)
- -** Sateesh Chodapuneedi ** (sateesh)
- -** Sonny Heng Chhen ** (schhen)
- -** Sam Robertson ** (slriv)
- -** Funs Kessen ** (snuf)
- -** Sowmya Krishnan ** (sowmya)
- -** Sudhap ** (sudhap)
- -** Venkata Swamy ** (swamy)
- -** Will Stevens ** (swill)
- -** Srikanteswararao Talluri ** (talluri)
- -** Anh Tu Nguyen ** (tuna)
- -** Vijayendra Bhamidipati ** (vijayendrabvs)
- -** Wei Zhou ** (weizhou)
- -** Sheng Yang ** (yasker)
- -** Yoshikazu Nojima ** (ynojima)
- - - - -