cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From seb...@apache.org
Subject [7/7] cloudstack-www git commit: First commit to initialize site
Date Mon, 11 May 2015 17:25:46 GMT
First commit to initialize site


Project: http://git-wip-us.apache.org/repos/asf/cloudstack-www/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-www/commit/a5f9cf52
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-www/tree/a5f9cf52
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-www/diff/a5f9cf52

Branch: refs/heads/master
Commit: a5f9cf523223a24f903eb81cfa8906689b67e78d
Parents: 
Author: Sebastien Goasguen <runseb@gmail.com>
Authored: Mon May 11 19:25:23 2015 +0200
Committer: Sebastien Goasguen <runseb@gmail.com>
Committed: Mon May 11 19:25:23 2015 +0200

----------------------------------------------------------------------
 Gemfile                                         |   14 +
 Gemfile.lock                                    |  129 +
 LICENSE                                         |  179 +
 README.md                                       |    2 +
 config.rb                                       |   76 +
 source/about.markdown                           |   40 +
 source/archives.markdown                        |   30 +
 source/bylaws.markdown                          |  385 +
 source/cloudstack-faq.markdown                  |   58 +
 source/contribute.markdown                      |   33 +
 source/developers.markdown                      |  185 +
 source/downloads.markdown                       |  197 +
 source/features.markdown                        |  187 +
 source/fonts/glyphicons-halflings-regular.eot   |  Bin 0 -> 14079 bytes
 source/fonts/glyphicons-halflings-regular.svg   |  228 +
 source/fonts/glyphicons-halflings-regular.ttf   |  Bin 0 -> 29512 bytes
 source/fonts/glyphicons-halflings-regular.woff  |  Bin 0 -> 16448 bytes
 source/history.markdown                         |   28 +
 .../images/banner-apache-4.0.0-incubating.png   |  Bin 0 -> 56939 bytes
 source/images/cloudmonkey-fp-sm.png             |  Bin 0 -> 44624 bytes
 source/images/cloudmonkey-fp.png                |  Bin 0 -> 40902 bytes
 source/images/cloudstack-oss-architecture.png   |  Bin 0 -> 69366 bytes
 source/images/cs-front-page.png                 |  Bin 0 -> 197097 bytes
 source/images/feed-icon-14x14.png               |  Bin 0 -> 689 bytes
 source/images/glyphicons-halflings-white.png    |  Bin 0 -> 8777 bytes
 source/images/glyphicons-halflings.png          |  Bin 0 -> 12799 bytes
 source/images/logo-sm.png                       |  Bin 0 -> 8700 bytes
 source/images/monkey-144.png                    |  Bin 0 -> 10584 bytes
 source/images/monkey.png                        |  Bin 0 -> 30274 bytes
 source/images/new-logo-sm.png                   |  Bin 0 -> 14576 bytes
 source/images/title_logo.png                    |  Bin 0 -> 12266 bytes
 source/index.html.erb                           |  233 +
 source/javascripts/bootstrap.js                 | 2039 +++++
 source/javascripts/bootstrap.min.js             |    7 +
 source/layouts/layout.erb                       |  141 +
 source/layouts/layout.erb.orig                  |   19 +
 source/mailing-lists.markdown                   |   67 +
 source/security.markdown                        |   72 +
 source/software.markdown                        |   44 +
 source/stylesheets/all.css                      |  173 +
 source/stylesheets/bootstrap-responsive.css     | 1058 +++
 source/stylesheets/bootstrap-responsive.min.css |    9 +
 source/stylesheets/bootstrap.css                | 7445 ++++++++++++++++++
 source/stylesheets/bootstrap.min.css            |  841 ++
 source/stylesheets/bootswatch.min.css           |    1 +
 source/stylesheets/font-awesome.css             |  303 +
 source/survey.markdown                          |   23 +
 source/trademark-guidelines.markdown            |  150 +
 source/users.markdown                           |  233 +
 source/videos.markdown                          |   27 +
 source/who.markdown                             |  221 +
 51 files changed, 14877 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/Gemfile
----------------------------------------------------------------------
diff --git a/Gemfile b/Gemfile
new file mode 100644
index 0000000..44eaa38
--- /dev/null
+++ b/Gemfile
@@ -0,0 +1,14 @@
+# If you do not have OpenSSL installed, update
+# the following line to use "http://" instead
+source 'https://rubygems.org'
+
+gem "middleman", "~>3.3.10"
+
+# Live-reloading plugin
+gem "middleman-livereload", "~> 3.1.0"
+
+# For faster file watcher updates on Windows:
+gem "wdm", "~> 0.1.0", :platforms => [:mswin, :mingw]
+
+# Windows does not come with time zone data
+gem "tzinfo-data", platforms: [:mswin, :mingw]

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/Gemfile.lock
----------------------------------------------------------------------
diff --git a/Gemfile.lock b/Gemfile.lock
new file mode 100644
index 0000000..777829d
--- /dev/null
+++ b/Gemfile.lock
@@ -0,0 +1,129 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (4.1.10)
+      i18n (~> 0.6, >= 0.6.9)
+      json (~> 1.7, >= 1.7.7)
+      minitest (~> 5.1)
+      thread_safe (~> 0.1)
+      tzinfo (~> 1.1)
+    celluloid (0.16.0)
+      timers (~> 4.0.0)
+    chunky_png (1.3.4)
+    coffee-script (2.3.0)
+      coffee-script-source
+      execjs
+    coffee-script-source (1.9.1)
+    compass (1.0.3)
+      chunky_png (~> 1.2)
+      compass-core (~> 1.0.2)
+      compass-import-once (~> 1.0.5)
+      rb-fsevent (>= 0.9.3)
+      rb-inotify (>= 0.9)
+      sass (>= 3.3.13, < 3.5)
+    compass-core (1.0.3)
+      multi_json (~> 1.0)
+      sass (>= 3.3.0, < 3.5)
+    compass-import-once (1.0.5)
+      sass (>= 3.2, < 3.5)
+    em-websocket (0.5.1)
+      eventmachine (>= 0.12.9)
+      http_parser.rb (~> 0.6.0)
+    erubis (2.7.0)
+    eventmachine (1.0.7)
+    execjs (2.4.0)
+    ffi (1.9.8)
+    haml (4.0.6)
+      tilt
+    hike (1.2.3)
+    hitimes (1.2.2)
+    hooks (0.4.0)
+      uber (~> 0.0.4)
+    http_parser.rb (0.6.0)
+    i18n (0.7.0)
+    json (1.8.2)
+    kramdown (1.6.0)
+    listen (2.10.0)
+      celluloid (~> 0.16.0)
+      rb-fsevent (>= 0.9.3)
+      rb-inotify (>= 0.9)
+    middleman (3.3.10)
+      coffee-script (~> 2.2)
+      compass (>= 1.0.0, < 2.0.0)
+      compass-import-once (= 1.0.5)
+      execjs (~> 2.0)
+      haml (>= 4.0.5)
+      kramdown (~> 1.2)
+      middleman-core (= 3.3.10)
+      middleman-sprockets (>= 3.1.2)
+      sass (>= 3.4.0, < 4.0)
+      uglifier (~> 2.5)
+    middleman-core (3.3.10)
+      activesupport (~> 4.1.0)
+      bundler (~> 1.1)
+      erubis
+      hooks (~> 0.3)
+      i18n (~> 0.7.0)
+      listen (>= 2.7.9, < 3.0)
+      padrino-helpers (~> 0.12.3)
+      rack (>= 1.4.5, < 2.0)
+      rack-test (~> 0.6.2)
+      thor (>= 0.15.2, < 2.0)
+      tilt (~> 1.4.1, < 2.0)
+    middleman-livereload (3.1.1)
+      em-websocket (>= 0.2.0)
+      middleman-core (>= 3.0.2)
+      multi_json (~> 1.0)
+      rack-livereload
+    middleman-sprockets (3.4.2)
+      middleman-core (>= 3.3)
+      sprockets (~> 2.12.1)
+      sprockets-helpers (~> 1.1.0)
+      sprockets-sass (~> 1.3.0)
+    minitest (5.5.1)
+    multi_json (1.11.0)
+    padrino-helpers (0.12.5)
+      i18n (~> 0.6, >= 0.6.7)
+      padrino-support (= 0.12.5)
+      tilt (~> 1.4.1)
+    padrino-support (0.12.5)
+      activesupport (>= 3.1)
+    rack (1.6.0)
+    rack-livereload (0.3.15)
+      rack
+    rack-test (0.6.3)
+      rack (>= 1.0)
+    rb-fsevent (0.9.4)
+    rb-inotify (0.9.5)
+      ffi (>= 0.5.0)
+    sass (3.4.13)
+    sprockets (2.12.3)
+      hike (~> 1.2)
+      multi_json (~> 1.0)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    sprockets-helpers (1.1.0)
+      sprockets (~> 2.0)
+    sprockets-sass (1.3.1)
+      sprockets (~> 2.0)
+      tilt (~> 1.1)
+    thor (0.19.1)
+    thread_safe (0.3.5)
+    tilt (1.4.1)
+    timers (4.0.1)
+      hitimes
+    tzinfo (1.2.2)
+      thread_safe (~> 0.1)
+    uber (0.0.13)
+    uglifier (2.7.1)
+      execjs (>= 0.3.0)
+      json (>= 1.8.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  middleman (~> 3.3.10)
+  middleman-livereload (~> 3.1.0)
+  tzinfo-data
+  wdm (~> 0.1.0)

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/LICENSE
----------------------------------------------------------------------
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..20092be
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,179 @@
+Copyright (c) 2013 The Apache Software Foundation
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..bbbb623
--- /dev/null
+++ b/README.md
@@ -0,0 +1,2 @@
+Source of Apache CloudStack Web site
+====================================

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/config.rb
----------------------------------------------------------------------
diff --git a/config.rb b/config.rb
new file mode 100644
index 0000000..058fd8b
--- /dev/null
+++ b/config.rb
@@ -0,0 +1,76 @@
+###
+# Compass
+###
+
+# Change Compass configuration
+# compass_config do |config|
+#   config.output_style = :compact
+# end
+
+###
+# Page options, layouts, aliases and proxies
+###
+
+# Per-page layout changes:
+#
+# With no layout
+# page "/path/to/file.html", :layout => false
+#
+# With alternative layout
+# page "/path/to/file.html", :layout => :otherlayout
+#
+# A path which all have the same layout
+# with_layout :admin do
+#   page "/admin/*"
+# end
+
+# Proxy pages (https://middlemanapp.com/advanced/dynamic_pages/)
+# proxy "/this-page-has-no-template.html", "/template-file.html", :locals => {
+#  :which_fake_page => "Rendering a fake page with a local variable" }
+
+###
+# Helpers
+###
+
+# Automatic image dimensions on image_tag helper
+# activate :automatic_image_sizes
+
+# Reload the browser automatically whenever files change
+# configure :development do
+#   activate :livereload
+# end
+
+# Methods defined in the helpers block are available in templates
+# helpers do
+#   def some_helper
+#     "Helping"
+#   end
+# end
+
+set :css_dir, 'stylesheets'
+
+set :js_dir, 'javascripts'
+
+set :images_dir, 'images'
+
+# Define markdown engine
+
+set :markdown_engine, :kramdown
+
+# Build-specific configuration
+configure :build do
+  # For example, change the Compass output style for deployment
+  # activate :minify_css
+
+  # Minify Javascript on build
+  # activate :minify_javascript
+
+  # Enable cache buster
+  # activate :asset_hash
+
+  # Use relative URLs
+  # activate :relative_assets
+
+  # Or use a different image path
+  # set :http_prefix, "/Content/images/"
+end

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/about.markdown
----------------------------------------------------------------------
diff --git a/source/about.markdown b/source/about.markdown
new file mode 100644
index 0000000..e5d893c
--- /dev/null
+++ b/source/about.markdown
@@ -0,0 +1,40 @@
+---
+title: About CloudStack
+---
+
+<div class="row">
+	<div class="col-lg-12">
+		<div class="page-header">
+			<h1 id="indicators">Apache CloudStack: About</h1>
+		</div>
+
+	</div>
+</div>
+
+# What is Apache CloudStack?
+
+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? 
+
+# Features and Functionality
+
+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:
+
+- Works with hosts running XenServer/XCP, KVM, Hyper-V, and/or VMware ESXi with vSphere
+- Provides a friendly Web-based UI for managing the cloud
+- Provides a native [API](/docs/api/)
+- May provide an Amazon S3/EC2 compatible API (optional)
+- Manages storage for instances running on the hypervisors (primary storage) as well as templates, snapshots, and ISO images (secondary storage)
+- Orchestrates network services from the data link layer (L2) to some application layer (L7) services, such as DHCP, NAT, firewall, VPN, and so on
+- Accounting of network, compute, and storage resources
+- Multi-tenancy/account separation
+- User management
+
+In short, organizations can use Apache CloudStack to deploy a full-featured public or private IaaS cloud.
+
+# People of Apache CloudStack
+
+Apache projects are managed by a [Project Management Committee](http://www.apache.org/dev/pmc.html#what-is-a-pmc) (PMC), and much of the work is done by the project's [committers](http://www.apache.org/dev/committers.html). 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](http://theapacheway.com).
+
+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](/who.html)*.

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/archives.markdown
----------------------------------------------------------------------
diff --git a/source/archives.markdown b/source/archives.markdown
new file mode 100644
index 0000000..83840b8
--- /dev/null
+++ b/source/archives.markdown
@@ -0,0 +1,30 @@
+---
+title: Archives
+---
+
+<h2 id="indicators">Archived Releases</h2>
+
+* [apache-cloudstack-4.4.0.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.4.0/apache-cloudstack-4.4.0-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.4.0/apache-cloudstack-4.4.0-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.4.0/apache-cloudstack-4.4.0-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.4.0/apache-cloudstack-4.4.0-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.3.1.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.3.1/apache-cloudstack-4.3.1-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.3.1/apache-cloudstack-4.3.1-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.3.1/apache-cloudstack-4.3.1-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.3.1/apache-cloudstack-4.3.1-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.3.0.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.3.0/apache-cloudstack-4.3.0-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.3.0/apache-cloudstack-4.3.0-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.3.0/apache-cloudstack-4.3.0-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.3.0/apache-cloudstack-4.3.0-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.2.1.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.2.1/apache-cloudstack-4.2.1-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.2.1/apache-cloudstack-4.2.1-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.2.1/apache-cloudstack-4.2.1-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.2.1/apache-cloudstack-4.2.1-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.2.0.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.2.0/apache-cloudstack-4.2.0-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.2.0/apache-cloudstack-4.2.0-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.2.0/apache-cloudstack-4.2.0-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.2.0/apache-cloudstack-4.2.0-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.1.1.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.1.1/apache-cloudstack-4.1.1-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.1.1/apache-cloudstack-4.1.1-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.1.1/apache-cloudstack-4.1.1-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.1.1/apache-cloudstack-4.1.1-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.1.0.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.1.0/apache-cloudstack-4.1.0-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.1.0/apache-cloudstack-4.1.0-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.1.0/apache-cloudstack-4.1.0-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.1.0/apache-cloudstack-4.1.0-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.0.2.src.tar.bz2](http://archive.apache.org/dist/cloudstack/releases/4.0.2/apache-cloudstack-4.0.2-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/cloudstack/releases/4.0.2/apache-cloudstack-4.0.2-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/cloudstack/releases/4.0.2/apache-cloudstack-4.0.2-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/cloudstack/releases/4.0.2/apache-cloudstack-4.0.2-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.0.1-incubating.src.tar.bz2](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.1-incubating/apache-cloudstack-4.0.1-incubating-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.1-incubating/apache-cloudstack-4.0.1-incubating-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.1-incubating/apache-cloudstack-4.0.1-incubating-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.1-incubating/apache-cloudstack-4.0.1-incubating-src.tar.bz2.sha) ]
+* [apache-cloudstack-4.0.0-incubating.src.tar.bz2](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2) [ [PGP](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc) ][ [MD5](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5) ][ [SHA512](http://archive.apache.org/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha) ]
+
+<h3>CloudMonkey release archives</h3>
+
+* [apache-cloudstack-cloudmonkey-5.3.0](http://archive.apache.org/dist/cloudstack/releases/cloudmonkey-5.3.0/)
+* [apache-cloudstack-cloudmonkey-5.2.0](http://archive.apache.org/dist/cloudstack/releases/cloudmonkey-5.2.0/)
+* [apache-cloudstack-cloudmonkey-5.1.0](http://archive.apache.org/dist/cloudstack/releases/cloudmonkey-5.1.0/)
+* [apache-cloudstack-cloudmonkey-5.0.0](http://archive.apache.org/dist/cloudstack/releases/cloudmonkey-5.0.0/)
+
+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.
+
+- [Binaries for Red Hat Enterprise Linux 6.2 and CentOS 6.2](http://sourceforge.net/projects/cloudstack/files/CloudStack%20Acton/3.0.2/CloudStack-oss-3.0.2-1-rhel6.2.tar.gz/download)
+- [Binaries for Ubuntu 10.04 LTS](http://sourceforge.net/projects/cloudstack/files/CloudStack%20Acton/3.0.2/CloudStack-oss-3.0.2-1-ubuntu10.04.tar.gz/download)

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/bylaws.markdown
----------------------------------------------------------------------
diff --git a/source/bylaws.markdown b/source/bylaws.markdown
new file mode 100644
index 0000000..74c680b
--- /dev/null
+++ b/source/bylaws.markdown
@@ -0,0 +1,385 @@
+---
+title: Apache CloudStack Project Bylaws
+---
+
+<div class="row">
+
+<div class="col-lg-12">
+
+<div class="page-header">
+
+<h1 id="indicators">Apache CloudStack: Project Bylaws</h1>
+
+</div>
+
+</div>
+
+</div>
+
+# 1. Introduction
+
+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.
+
+# 2. Roles and Responsibilities
+
+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.
+
+# 3. Decision Making
+
+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:
+
+* A request is made that includes the required information for the PMC to make 
+a decision.
+* A PMC member reviews the request and provides an initial acknowledgement 
+response to the requester.
+* If no PMC member raises a concern after 72 hours, the requester can assume 
+approval.
+
+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.

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/cloudstack-faq.markdown
----------------------------------------------------------------------
diff --git a/source/cloudstack-faq.markdown b/source/cloudstack-faq.markdown
new file mode 100644
index 0000000..d8e9ae4
--- /dev/null
+++ b/source/cloudstack-faq.markdown
@@ -0,0 +1,58 @@
+---
+title: Apache CloudStack FAQ
+---
+
+<div class="row">
+
+<div class="col-lg-12">
+
+<div class="page-header">
+
+<h1 id="indicators">Apache CloudStack: FAQ</h1>
+
+</div>
+
+</div>
+
+</div>
+
+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](/mailing-lists.html). 
+
+- [What is Apache CloudStack?](/cloudstack-faq.html#what)
+- [Can I create my own private templates?](/cloudstack-faq.html#private)
+- [How are users, accounts, and domains handled in CloudStack?](/cloudstack-faq.html#users)
+
+### What is Apache CloudStack?
+
+<a name="what"> </a>
+
+Apache CloudStack is a complete software suite for creating Infrastructure as a Service (IaaS) clouds. Target environments include service providers and enterprises.
+
+- The Apache CloudStack platform enables service providers to set up an on-demand, elastic cloud computing service. It enables a utility computing service by allowing service providers to offer self-service virtual machine instances, storage volumes, and networking configurations over the Internet.
+- The Apache CloudStack platform enables enterprises to set up a private cloud for use by their own employees. The current generation of virtualization infrastructure targets enterprise IT departments who manage virtual machines the same way they would manage physical machines. The Apache CloudStack platform, on the other hand, enables self-service of virtual machines by users outside of the IT department. 
+- As an open source IaaS, Apache CloudStack is available to individuals and organizations that wish to study and implement an IaaS for personal, educational, and/or production use.
+
+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.
+
+### Can I create my own private templates?
+
+<a name="private"> </a>
+
+Yes. Every template has a privacy level associated with it. Privacy levels include:</a>
+
+- **Public**: The template is available to all users in the zone.
+- **Private**: The template is available only to its owner. A user can make her private templates available to specific users.
+
+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.)
+
+### How are users, accounts, and domains handled in CloudStack?
+
+<a name="users"> </a>
+
+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.

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/contribute.markdown
----------------------------------------------------------------------
diff --git a/source/contribute.markdown b/source/contribute.markdown
new file mode 100644
index 0000000..eb79007
--- /dev/null
+++ b/source/contribute.markdown
@@ -0,0 +1,33 @@
+---
+title: Apache CloudStack: Getting Involved
+---
+
+<div class="row">
+
+<div class="col-lg-12">
+
+<div class="page-header">
+
+<h1 id="indicators">Apache CloudStack: Getting Involved</h1>
+
+</div>
+
+</div>
+
+</div>
+
+Interested in helping out with Apache CloudStack? Great! We welcome participation from anybody willing to work [The Apache Way](http://theapacheway.com/) 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 &ndash; join us on the Marketing list and we'll help you get started](/mailing-lists.html)!
+
+Developers, of course, are also welcome. See the [Developer Resources](/developers.html) page!
+
+If you just want to report a bug, that's easily done in our [Jira bug tracking tool](https://issues.apache.org/jira/browse/CLOUDSTACK).
+
+## Where To Ask For Help
+
+Need some help getting started? Feel free to ask on the [mailing list](/mailing-lists.html) or find us on one of the following IRC channels on irc.freenode.net:
+
+* \#cloudstack - General Apache CloudStack conversation and end user support 
+* \#cloudstack-dev - Development discussions 
+* \#cloudstack-meeting - Weekly and ad-hoc meeting room for the Apache CloudStack community

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/developers.markdown
----------------------------------------------------------------------
diff --git a/source/developers.markdown b/source/developers.markdown
new file mode 100644
index 0000000..29e0d0e
--- /dev/null
+++ b/source/developers.markdown
@@ -0,0 +1,185 @@
+---
+title: Developer Resources for Apache CloudStack
+---
+
+<div class="row">
+
+<div class="col-lg-12">
+
+<div class="page-header">
+
+<h1 id="indicators">Developer Resources for Apache CloudStack</h1>
+
+</div>
+
+</div>
+
+</div>
+
+<div class="row">
+
+<div class="col-lg-8">
+
+<h2>Contributing as a Non-Committer</h2>
+
+<p>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.</p>
+
+<p>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 <a href="http://reviews.apache.org/">Review Board</a>, but it's a piece of cake from start to finish.</p>
+
+<h3> Assumptions </h3>
+
+<p>For the purpose of this post, we'll assume that you already have a system with <a href="http://git-scm.com/">Git</a> 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 <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License 2.0</a>.</p>
+
+<p>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.</p>
+
+<p>If you want to add a feature, you should bring it up for discussion on the <a href="mailto:dev@cloudstack.apache.org">dev@cloudstack.apache.org</a> 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 <a href="/mailing-lists.html">here</a>.</p>
+
+<p>In short, communication is a vital part of making a contribution to an Apache project.</p>
+
+<h3> Getting Started </h3>
+
+<p>First, lets make sure that you've added your name and email to your `~/.gitconfig`:</p>
+
+<pre>
+$ git config --global user.name "Your Name"
+$ git config --global user.email you@domain.com
+</pre>
+
+<p>You'll grab the CloudStack source with git:</p>
+
+<pre>
+$ git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git
+</pre>
+
+<p>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!)</p>
+
+<pre>
+$ git checkout -b mybranch
+</pre>
+
+<p>This does two things: One, it creates the branch <em>mybranch</em> and two, it changes your working branch to <em>mybranch</em>. Running `git branch` will show you which branch you're working on, with an asterisk next to the active branch, like so:</p>
+
+<pre>
+[user@localhost cloudstack]$ git branch
+  master
+  * mybranch
+  </pre>
+
+<p>Make whatever changes you're going to make, be sure to use <code>git add</code> to stage the changes, and then you're going to commit the changes to your working branch:</p>
+
+<pre>git commit -m "Insert a meaningful summary of changes here."</pre>
+
+<p>Finally, you're going to create a patch to upload to <a href="http://reviews.apache.org/">Review Board</a>:</p>
+
+<pre>git format-patch master --stdout > ~/patch-name.patch</pre>
+
+<h3>Using Review Board</h3>
+
+<p>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 <em>strong preference</em> is that patches be submitted through Review Board. Don't worry, it's a very easy tool to use.</p>
+
+<p>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 <a href="https://reviews.apache.org/r/new/">New Review Request</a> and select the repository (<strong>cloudstack-git</strong>) and upload the patch (diff) created with git.</p>
+
+<p>Click <strong>Create Review Request</strong> and then fill out the information required. Specifically:</p>
+
+<ol>
+<li>Summary</li>
+<li>Groups (choose cloudstack)</li>
+<li>People (only use if you need specific committers to review changes)</li>
+<li>Description</li>
+<li>Testing Done</li>
+</ol>
+
+<p>The <strong>Summary</strong> 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.")</p>
+
+<p>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 ).</p>
+
+<p>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.</p>
+
+<p>Once you're sure everything is OK, go ahead and submit the patch. But that's <em>not</em> the end of the process. The work isn't done until the patch is committed!</p>
+
+<h3> Review </h3>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>If the patch is accepted and committed, you have one last task (don't worry, it's minor and kind of satisfying).</p>
+
+<p>Go back to Review Board, click <strong>My Dashboard</strong> and then <strong>Outgoing Reviews</strong>. Go to your submission, you should see a "Ship it!" message from the reviewer. Click the <strong>Close</strong> button and choose <strong>Submitted</strong>. The status has now changed from <em>pending</em> to <em>submitted</em>.</p>
+
+<p>That's it &ndash; you've helped make Apache CloudStack a better project. Thanks!</p>
+
+<h3>Screencast</h3>
+
+<p>If you are new to git you might want to watch this screencast:</p>
+
+<iframe width="560" height="315" src="//www.youtube.com/embed/3c5JIW4onGk?list=PLb899uhkHRoZCRE00h_9CRgUSiHEgFDbC" frameborder="0" allowfullscreen></iframe>
+
+<h3>Further Reading</h3>
+
+<p>You might want to peruse the <a href="http://www.apache.org/foundation/getinvolved.html">Get Involved</a> page on Apache.org, and the <a href="http://commons.apache.org/patches.html">On Contributing Patches</a> 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).</p>
+
+</div>
+
+<div class="col-lg-4">
+
+
+<div class="list-group">
+
+<div class="list-group-item active">Resources</div>
+
+<a href="https://issues.apache.org/jira/browse/CLOUDSTACK" class="list-group-item">Jira</a>
+
+<a href="https://reviews.apache.org/dashboard/" class="list-group-item">Reviewboard</a>
+
+<a href="https://builds.apache.org/view/A-D/view/Cloudstack/" class="list-group-item">ASF Jenkins</a>
+
+<a href="http://jenkins.buildacloud.org/" class="list-group-item">CloudStack Jenkins</a>
+
+<a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+101" class="list-group-item">CloudStack Development 101</a>
+
+<a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment" class="list-group-item">Setting up a Dev Environment</a>
+
+<a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Coding+conventions" class="list-group-item">Code Conventions</a>
+
+<a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Testing" class="list-group-item">Testing CloudStack</a>
+
+</div>
+
+
+
+<div class="panel panel-success">
+
+<div class="panel-heading">
+                
+<h3 class="panel-title">Git Repositories</h3>
+              
+</div>
+              
+<div class="panel-body">
+                
+<p>The git repositories are hosted on Apache infrastructure, and can be found here:</p>
+
+<ul>
+<li>Apache CloudStack <a href="https://git-wip-us.apache.org/repos/asf/cloudstack.git">https://git-wip-us.apache.org/repos/asf/cloudstack.git</a></li>
+<li>Apache CloudStack CloudMonkey <a href="https://git-wip-us.apache.org/repos/asf/cloudstack-cloudmonkey.git">https://git-wip-us.apache.org/repos/asf/cloudstack-cloudmonkey.git</a></li>
+</ul>
+
+<p>To get the most recent source for Apache CloudStack, use:</p>
+
+<pre>
+git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git
+</pre>
+
+<p>Similarly, clone the cloudstack-cloudmonkey repository to get access to the most recent source for CloudMonkey.</p>
+
+<p>For projects related to Apache CloudStack, see the <a href="https://github.com/cloudstack-extras">CloudStack-extras repositories on GitHub</a>.</p>
+              
+</div>
+            
+</div>
+
+
+</div>
+
+</div>

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/downloads.markdown
----------------------------------------------------------------------
diff --git a/source/downloads.markdown b/source/downloads.markdown
new file mode 100644
index 0000000..3782ce4
--- /dev/null
+++ b/source/downloads.markdown
@@ -0,0 +1,197 @@
+---
+title: Apache CloudStack Downloads
+---
+
+<div class="row">
+
+<div class="col-lg-12">
+
+<div class="page-header">
+
+<h1 id="indicators">Apache CloudStack: Downloads</h1>
+
+</div>
+
+</div>
+
+</div>
+
+<div class="bs-example">
+
+<div class="row">
+
+<div class="col-lg-6">
+
+<h2>Latest CloudStack Release</h2>
+
+<h4>Source Release</h4>
+
+<p>Apache CloudStack's most current release is 4.4.2.
+</p>
+
+<p>
+<a href="http://www.apache.org/dyn/closer.cgi/cloudstack/releases/4.4.2/apache-cloudstack-4.4.2-src.tar.bz2"><button type="button" class="btn btn-primary btn-lg">Get the 4.4.2 Source!</button></a>
+
+<a href="http://www.apache.org/dist/cloudstack/KEYS"><button type="button" class="btn btn-info btn-xs">KEYS</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/4.4.2/apache-cloudstack-4.4.2-src.tar.bz2.asc"><button type="button" class="btn btn-info btn-xs">PGP</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/4.4.2/apache-cloudstack-4.4.2-src.tar.bz2.md5"><button type="button" class="btn btn-info btn-xs">MD5</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/4.4.2/apache-cloudstack-4.4.2-src.tar.bz2.sha"><button type="button" class="btn btn-info btn-xs">SHA</button></a>
+
+</p>
+
+<p>
+<a href="http://www.apache.org/dyn/closer.cgi/cloudstack/releases/4.3.2/apache-cloudstack-4.3.2-src.tar.bz2"><button type="button" class="btn btn-primary btn-lg">Get the 4.3.2 Source!</button></a>
+
+<a href="http://www.apache.org/dist/cloudstack/KEYS"><button type="button" class="btn btn-info btn-xs">KEYS</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/4.3.2/apache-cloudstack-4.3.2-src.tar.bz2.asc"><button type="button" class="btn btn-info btn-xs">PGP</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/4.3.2/apache-cloudstack-4.3.2-src.tar.bz2.md5"><button type="button" class="btn btn-info btn-xs">MD5</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/4.3.2/apache-cloudstack-4.3.2-src.tar.bz2.sha"><button type="button" class="btn btn-info btn-xs">SHA</button></a>
+
+</p>
+
+<h4>Packages</h4>
+
+<p>For easier installation or upgrades, the official source code release has been supplemented by community members who have chosen to provide package repositories.</p>
+
+<ul>
+<li>DEB package repository: <a href="http://cloudstack.apt-get.eu/ubuntu">http://cloudstack.apt-get.eu/ubuntu</a></li>
+<li>RPM package repository: <a href="http://cloudstack.apt-get.eu/rhel/">http://cloudstack.apt-get.eu/rhel/</a></li>
+<li>CloudStack packages by ShapeBlue: <a href="http://shapeblue.com/packages/">http://shapeblue.com/packages</a></li>
+</ul>
+
+<p>Instructions for using these community provided repositories can be found in the <a href="http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.4/installation.html#configure-package-repository">Configure Package Repository</a> section of the Installation Guide.</p>
+
+
+<h4>Release Notes for CloudStack 4.4.2</h4>
+
+<p>Full release notes can be found in the <a href="http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.2/">Version 4.4.2 Release Notes</a> document.</p>
+
+<p>Instructions for building from source and installing Apache CloudStack can be found in the <a href="http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.4/">Installation Guide</a>.</p>
+
+<p>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 <a href="http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.2/">Release Notes</a>.</p>
+
+
+<h4>Release Notes for CloudStack 4.3.2</h4>
+
+<p>Full release notes can be found in the <a href="http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3.2/">Version 4.3.2 Release Notes</a> document.</p>
+
+<p>Instructions for building from source and installing Apache CloudStack can be found in the <a href="http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.3/">Installation Guide</a>.</p>
+
+<p>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 <a href="http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.3.2/">Release Notes</a>.</p>
+
+
+</div>
+
+<div class="col-lg-6">
+
+<div class="panel panel-default">
+
+<div class="panel-heading">
+
+<h3 class="panel-title">Verifying Downloads</h3>
+
+</div>
+              
+<div class="panel-body">
+
+<p>
+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
+<a href="https://dist.apache.org/repos/dist/release/cloudstack/KEYS">KEYS</a> 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:
+</p>
+<pre>
+    % pgpk -a KEYS
+    % pgpv apache-cloudstack-X.X.X-src.tar.bz2.asc
+</pre>
+<p>or</p>
+<pre>
+    % pgp -ka KEYS
+    % pgp apache-cloudstack-X.X.X-src.tar.bz2.asc
+</pre>
+<p>or</p>
+<pre>
+    % gpg --import KEYS
+    % gpg --verify apache-cloudstack-X.X.X-src.tar.bz2.asc
+</pre>
+<p>
+Additionally, you can verify the MD5 or SHA512 signatures on the files.
+</p>
+
+</div>
+
+</div>
+
+</div>
+
+</div>
+
+</div>
+                
+
+
+
+<a name="cloudmonkey"></a>
+
+<div class="row">
+
+<div class="col-lg-12">
+
+<div class="page-header">
+
+<h2 id="indicators">Latest CloudMonkey Release</h2>
+
+</div>
+
+</div>
+
+</div>
+
+Apache CloudStack's CloudMonkey tool is a CLI and shell environment designed for interacting with CloudStack-based clouds.
+
+#### Source Release
+
+CloudMonkey's most current release is 5.3.1.
+
+<p>
+<a href="http://www.apache.org/dyn/closer.cgi/cloudstack/releases/cloudmonkey-5.3.1/apache-cloudstack-cloudmonkey-5.3.1-src.tar.bz2"><button type="button" class="btn btn-primary btn-lg">Get the 5.3.1 Source!</button></a>
+
+<a href="http://www.apache.org/dist/cloudstack/KEYS"><button type="button" class="btn btn-info btn-xs">KEYS</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/cloudmonkey-5.3.1/apache-cloudstack-cloudmonkey-5.3.1-src.tar.bz2.asc"><button type="button" class="btn btn-info btn-xs">PGP</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/cloudmonkey-5.3.1/apache-cloudstack-cloudmonkey-5.3.1-src.tar.bz2.md5"><button type="button" class="btn btn-info btn-xs">MD5</button></a>
+<a href="http://www.apache.org/dist/cloudstack/releases/cloudmonkey-5.3.1/apache-cloudstack-cloudmonkey-5.3.1-src.tar.bz2.sha"><button type="button" class="btn btn-info btn-xs">SHA</button></a>
+
+</p>
+
+Instructions for building and installing from source can be found in the included [README.md](https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=blob_plain;f=README.md) file.
+
+#### PyPi Package
+
+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](https://pypi.python.org/pypi/cloudmonkey/).
+
+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
+
+
+<a name="archives"></a>
+
+<div class="row">
+
+<div class="col-lg-12">
+
+<div class="page-header">
+
+<h2 id="indicators">Archived Releases</h2>
+
+You can find links to older releases of Apache CloudStack on the <a href="archives.html">archives page</a>.

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/features.markdown
----------------------------------------------------------------------
diff --git a/source/features.markdown b/source/features.markdown
new file mode 100644
index 0000000..e187cf6
--- /dev/null
+++ b/source/features.markdown
@@ -0,0 +1,187 @@
+---
+title: Apache CloudStack Features
+---
+
+##<i class="icon-cloud"></i> Apache CloudStack Features
+
+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](/cloudstack/mailing-lists.html), and consider [filing a feature request in our bug tracker](https://issues.apache.org/jira/browse/CLOUDSTACK). 
+
+<table id="features" style="width: 100%;" border="1" cellpadding="2" cellspacing="2">
+<tbody>
+<tr>
+<td class="head-left">
+<h2><strong>Feature</strong></h2>
+</td>
+<td class="head-right">
+<h2><strong>Description</strong></h2>
+</td>
+</tr>
+<tr>
+<td><strong>Rich Management User Interface</strong></td>
+<td>CloudStack provides a feature-rich out-of-the-box <strong>user interface</strong> implemented on top of the CloudStack <strong>API</strong> 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.</td>
+</tr>
+<tr>
+<td><strong>Brand-able Self Service User Interface</strong></td>
+<td>Our out-of-the-box <strong>user interface</strong> was built using standard HTML and CSS with jQuery as our standard JavaScript library. It can be <strong>easily customized</strong> and branded to mirror your company’s existing look and feel.</td>
+</tr>
+<tr>
+<td><strong><strong>Secure AJAX Console Access</strong></strong></td>
+<td>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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Powerful <strong>API</strong></strong></td>
+<td style="width: 518px;">Easily build, integrate, and use applications built on top of the CloudStack <strong>API</strong>. The CloudStack API is well-documented and extensible. CloudStack also includes support for the Amazon EC2 and S3 APIs.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>Secure Single Sign On</strong></strong></td>
+<td style="width: 518px;">Aggregate and integrate your existing applications with our management <strong>user interface</strong> via our secure single sign-on for a better user experience.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>Multi-role Support</strong></strong></td>
+<td style="width: 518px;">Three distinct account roles for <strong>user interface</strong> and <strong>API</strong> access are supported out-of-the-box:
+<ul>
+<li><strong>Admin:</strong> can manage both the virtual and physical resources of the cloud</li>
+<li><strong>Domain-Admin:</strong> can manage only the virtual resources owned by the accounts within their domain</li>
+<li><strong>User:</strong> can manage their own virtual resources</li>
+</ul>
+</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>On Demand Virtual Data center Hosting</strong></td>
+<td style="width: 518px;">Provides users with virtually unlimited amount of computing resources – on demand, as required and billed by actual usage.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>Dynamic Workload Management</strong></strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Broad network Virtualization Capabilities</strong></td>
+<td style="width: 518px;">Support for embedded software-based network management as well as <strong>VLAN</strong>. Our Direct Attached IP enables you to integrate with a virtual network architecture that best fits your needs.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>MPLS</strong> Support in the Cloud</strong></td>
+<td style="width: 518px;">CloudStack allows you to dedicate an entire <strong>VLAN</strong> to a specific account for <strong>MPLS</strong> support between network nodes.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Secure Cloud Deployments</strong></td>
+<td style="width: 518px;">Ensures that all memory, CPU, network, and storage resources are both available and isolated from one user account to another within the cloud.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>Hypervisor Agnostic</strong></strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Easy Template Creation Process</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Rich Template and ISO Management</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Domains and Delegated Administration</strong></td>
+<td style="width: 518px;">The support for domains allows you to segregate your cloud resources and delegate the management of these domains to other administrators.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Snapshot Management</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Comprehensive Service Management</strong></td>
+<td style="width: 518px;">Administrators can define, meter, deploy, and manage multiple service and disk offerings within the cloud.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>VM Sync and High Availability</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Resource Over Provisioning and Limits</strong></td>
+<td style="width: 518px;">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.
+<p>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).</p>
+</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Usage Metering</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Alerts and Notifications</strong></td>
+<td style="width: 518px;">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 <strong>API</strong> and/or via email using SMTP.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Virtual Routers, Firewalls and Load Balancers</strong></td>
+<td style="width: 518px;">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</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Multiple Storage Solutions</strong></td>
+<td style="width: 518px;">CloudStack supports many storage solutions with&nbsp; iSCSI and NFS being preferred, but anything that can have multiple nodes mount it simultaneously will work.&nbsp; 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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Storage Tiering</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Block Storage Volumes</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Wide Range Guest VM OS Support</strong></td>
+<td style="width: 518px;">Depending on the configured hypervisor, CloudStack supports a wide range of guest operating system including Windows®, Linux®, and various versions of BSD®.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Event/Audit Logs</strong></td>
+<td style="width: 518px;">All user interactions via the CloudStack UI or <strong>API</strong> 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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>User Data Support</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Guest OS Preferences</strong></td>
+<td style="width: 518px;">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.”</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Host Maintenance with Live Migration</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Flexible Adapter Framework</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Random Password for Guest OS</strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>OpenStack Swift Integration for Secondary Storage&nbsp;</strong></td>
+<td style="width: 518px;">Secondary storage (templates and VM snapshots) can be stored in OpenStack Swift as an alternative to NFS.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Projects</strong></td>
+<td style="width: 518px;">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.&nbsp;</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong>Clustered LVM Support</strong></td>
+<td style="width: 518px;">CloudStack can utilize clustered Logical Volume Manager (LVM) storage configurations starting with version 3.0.&nbsp;</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>NetScaler Support</strong></strong></td>
+<td style="width: 518px;"><strong></strong>CloudStack supports MPX, VPX &amp; SDX devices. Users can set up Layer-4 load balancing rules. Supported protocols: HTTP, TCP &amp; UDP; Algorithms: least loaded and round robin; Persistent sessions: source IP based, cookie based.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>Network As a Service<br data-mce-bogus="1" /></strong></strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>LDAP Integration<br data-mce-bogus="1" /></strong></strong></td>
+<td style="width: 518px;">CloudStack supports LDAP authentication as a built-in optional AUTH adapter</td>
+</tr>
+<tr>
+<td style="width: 200px; text-align: left;"><strong><strong>Notification &amp; Capacity Thresholds<br data-mce-bogus="1" /></strong></strong></td>
+<td style="width: 518px;">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.</td>
+</tr>
+</tbody>
+</table>
+

http://git-wip-us.apache.org/repos/asf/cloudstack-www/blob/a5f9cf52/source/fonts/glyphicons-halflings-regular.eot
----------------------------------------------------------------------
diff --git a/source/fonts/glyphicons-halflings-regular.eot b/source/fonts/glyphicons-halflings-regular.eot
new file mode 100644
index 0000000..87eaa43
Binary files /dev/null and b/source/fonts/glyphicons-halflings-regular.eot differ


Mime
View raw message