Difference between revisions of "Main Page"

From stoney cloud
Jump to: navigation, search
[unchecked revision][quality revision]
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<div style="float:left; width:67%">
 
<div style="float:left; width:67%">
 
The stoney cloud wiki acts as a collection of all aspects of a high availability cloud infrastructure. It is roughly divided into the following sections:
 
The stoney cloud wiki acts as a collection of all aspects of a high availability cloud infrastructure. It is roughly divided into the following sections:
* '''[[:Category:Infrastructure|Infrastructure]]''': The basis of the whole ecosystem.
+
* [[:Category:Infrastructure|Infrastructure]]: The basis of the whole ecosystem (Build Server, Binary Package Server, Mirror Server, Puppet Server, Operating System).
* '''[[:Category:stoney cloud|stoney cloud]]''': The actual cloud with an easy to use multi-tenant web based interface.
+
* [[:Category:stoney cloud|stoney cloud]]: An expandable multi-tenant web based Open Source Cloud management solution with service providers as it's target audience.
* '''[[:Category:Self-Service Modules|Self-Service Modules]]''': Modules that expand the functionality of the stoney cloud.
+
* [[:Category:Self-Service Modules|Self-Service Modules]]: Modules that expand the initial stoney cloud functionality.
 
<br />
 
<br />
 
</div>
 
</div>
Line 14: Line 14:
 
* [[stoney cloud: Dual-Node Installation]]
 
* [[stoney cloud: Dual-Node Installation]]
 
* [[stoney cloud: Multi-Node Installation]]
 
* [[stoney cloud: Multi-Node Installation]]
 +
* [[stoney cloud: Resetting your Test-Environment]]
 
* [[stoney cloud: Upgrade]]
 
* [[stoney cloud: Upgrade]]
 
</div>
 
</div>
Line 22: Line 23:
 
== Infrastructure ==
 
== Infrastructure ==
 
The stoney cloud builds upon the [http://www.gentoo.org/ Gentoo] Linux Distribution and is dependent on infrastructure projects like:
 
The stoney cloud builds upon the [http://www.gentoo.org/ Gentoo] Linux Distribution and is dependent on infrastructure projects like:
* Build Server
+
* [[Build Server]]
* Binary Package Server
+
* [[Binary Package Server]]
* Mirror Server
+
* [[Mirror Server]]
* Puppet Server
+
* [[Puppet Server]]
 
While this infrastructure will serve stoney cloud in many ways, it may also be used to build cloud independent systems. We want you to be able to deploy desktops or more specialized gear using the same stack the infrastructure projects use to build services and manage machines for the cloud.
 
While this infrastructure will serve stoney cloud in many ways, it may also be used to build cloud independent systems. We want you to be able to deploy desktops or more specialized gear using the same stack the infrastructure projects use to build services and manage machines for the cloud.
  
Line 35: Line 36:
 
<div style="float:left; width:34%;">
 
<div style="float:left; width:34%;">
 
== stoney cloud ==
 
== stoney cloud ==
The stoney cloud is an expandable multi-tenant web based Open Source Cloud management solution with service providers as it's target audience.
+
The main framework called [[:Category:stoney core|stoney core]] is responsible for shared functionality.
 +
* The basic installation and configuration of the initial stoney cloud components (OpenLDAP server, Apache web server, GlusterFS, ...).
 +
* Reseller, customer and user management.
 +
* Roles and rights management.
 +
* Billing functionality.
 +
* Searching functionality.
 +
* A consistent look and feel between modules.
 +
* Internationalization.
  
* [[:Category:stoney core|stoney core]]: Main framework responsible for shared functionality:
+
This functionality is accessible via:
** [[:Category:REST_API|REST API]], which serves as a data and business logic abstraction layer and uses JSON as the primary data interchange format.
+
* A [[:Category:REST_API|REST API]], which serves as the data and business logic abstraction layer and uses JSON as the primary data interchange format.
** User management, rights and roles.
+
** A consistent look and feel between modules.
+
** Internationalization.
+
  
*[[:Category:stoney conductor|stoney conductor]]: Responsible for:
+
This [[:Category:REST_API|REST API]] is currenty accessible via:
** Storage allocation
+
* A '''c'''ommand '''l'''ine '''i'''nterface.
** Network configuration
+
* An Ajax based web interface.
** Virtual machine profiles
+
* Any scripting language which supports a REST API and JSON.
** Virtual machine templates
+
** Virtual machines
+
** Virtual machine snapshots
+
** Virtual machine full backups
+
 
</div>
 
</div>
  
 
<div style="float:right; width:33%">
 
<div style="float:right; width:33%">
 
== Self-Service Modules ==
 
== Self-Service Modules ==
=== Existing ===
+
The [[:Category:Self-Service Modules|Self-Service Modules]] expand the initial stoney cloud functionality. Some examples:
 +
* [[:Category:stoney conductor|stoney conductor]]: A cloud and virtual machine management tool (storage, network, cpu, memory, virtual machines, backups, snapshots, ...).
 +
* [[:Category:stoney vm|stoney vm]]: A simplified sub set of the [[:Category:stoney conductor|stoney conductor]] functionality (start, stop, access a virtual machine).
 
* [[:Category:stoney backup|stoney backup]]: An on-line backup service for desktops, servers and virtual machines.
 
* [[:Category:stoney backup|stoney backup]]: An on-line backup service for desktops, servers and virtual machines.
 
=== Work in progress ===
 
* [[:Category:stoney vm|stoney vm]]: A simplified sub set of the [[:Category:stoney conductor|stoney conductor]] functionality.
 
 
* [[:Category:stoney mail|stoney mail]]: A mail service with optional collaboration functionality (based on Open-Xchange).
 
* [[:Category:stoney mail|stoney mail]]: A mail service with optional collaboration functionality (based on Open-Xchange).
 
=== Planned ===
 
 
* [[:Category:stoney monitor|stoney monitor]]: Monitoring (with Zabbix).
 
* [[:Category:stoney monitor|stoney monitor]]: Monitoring (with Zabbix).
 
* [[:Category:stoney orchestra|stoney orchestra]]: Configuration Management (with Puppet).
 
* [[:Category:stoney orchestra|stoney orchestra]]: Configuration Management (with Puppet).
* [[:Category:stoney box|stoney box]]: An on-line storage service (will support WebDAV via HTTPS and SFTP, later CIFS as well).
+
* [[:Category:stoney box|stoney box]]: An on-line storage service (Webbrowser access via HTTPS, WebDAV via HTTPS and synchronisation to multiple devices).
 
* [[:Category:stoney web|stoney web]]: Web & Database hosting service (based on Apache and MariaDB).
 
* [[:Category:stoney web|stoney web]]: Web & Database hosting service (based on Apache and MariaDB).
 
</div>
 
</div>

Latest revision as of 11:50, 12 February 2015

The stoney cloud wiki acts as a collection of all aspects of a high availability cloud infrastructure. It is roughly divided into the following sections:

  • Infrastructure: The basis of the whole ecosystem (Build Server, Binary Package Server, Mirror Server, Puppet Server, Operating System).
  • stoney cloud: An expandable multi-tenant web based Open Source Cloud management solution with service providers as it's target audience.
  • Self-Service Modules: Modules that expand the initial stoney cloud functionality.


Quick Links

Infrastructure

The stoney cloud builds upon the Gentoo Linux Distribution and is dependent on infrastructure projects like:

While this infrastructure will serve stoney cloud in many ways, it may also be used to build cloud independent systems. We want you to be able to deploy desktops or more specialized gear using the same stack the infrastructure projects use to build services and manage machines for the cloud.

Currently some requirements and proposals have been imported from the RaBe Wiki and are being fleshed out and merged into this wiki proper.

stoney cloud Wiki Write Access

If you would like write access to the stoney cloud Wiki, please send us a request.

stoney cloud

The main framework called stoney core is responsible for shared functionality.

  • The basic installation and configuration of the initial stoney cloud components (OpenLDAP server, Apache web server, GlusterFS, ...).
  • Reseller, customer and user management.
  • Roles and rights management.
  • Billing functionality.
  • Searching functionality.
  • A consistent look and feel between modules.
  • Internationalization.

This functionality is accessible via:

  • A REST API, which serves as the data and business logic abstraction layer and uses JSON as the primary data interchange format.

This REST API is currenty accessible via:

  • A command line interface.
  • An Ajax based web interface.
  • Any scripting language which supports a REST API and JSON.

Self-Service Modules

The Self-Service Modules expand the initial stoney cloud functionality. Some examples:

  • stoney conductor: A cloud and virtual machine management tool (storage, network, cpu, memory, virtual machines, backups, snapshots, ...).
  • stoney vm: A simplified sub set of the stoney conductor functionality (start, stop, access a virtual machine).
  • stoney backup: An on-line backup service for desktops, servers and virtual machines.
  • stoney mail: A mail service with optional collaboration functionality (based on Open-Xchange).
  • stoney monitor: Monitoring (with Zabbix).
  • stoney orchestra: Configuration Management (with Puppet).
  • stoney box: An on-line storage service (Webbrowser access via HTTPS, WebDAV via HTTPS and synchronisation to multiple devices).
  • stoney web: Web & Database hosting service (based on Apache and MariaDB).