Documentation Cloud Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Replaced content with "{{header|docs}} {{Docs_beat_open}} Category:Docs Project Category:Draft documentation Category:Documentation beats")
Line 1: Line 1:
 
{{header|docs}}
 
{{header|docs}}
{{Documentation_closed_beat|Release Notes}}
 
 
 
== Aeolus Conductor ==
 
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
 
The Aeolus Conductor is a web UI and tools to create and manage cloud instances across a wide variety of cloud types, all from the same UI.  More information about the UI and what is supported is available at the [http://aeolusproject.org Aeolus home page].
 
 
 
== Condor Cloud ==
 
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
 
Condor Cloud is an Infrastructure as a Service (IaaS) cloud implementation.  It allows you to create as many VMs from an image or images as you wish, distributing them across a pool of configured hosts.  The user interface is the Deltacloud API (http://deltacloud.org).  The backend is implemented using Condor (http://www.cs.wisc.edu/condor/) which in turn starts VMs using libvirt and KVM.
 
 
 
== HekaFS ==
 
 
HekaFS 0.7 enhances the feature set of GlusterFS with multi-tenancy, security, and management features.
 
 
HekaFS deployment requires knowledge of how to set up OpenSSL keys and certificates to facilitate authentication at both the management and I/O levels.
 
 
Network and storage encryption are both optional, and incur a significant performance penalty if used.
 
 
Quota/billing support is under active development within GlusterFS, and will not be available for this release of HekaFS.
 
 
Enhanced local file distribution/replication and wide-area replication are planned as eventual features of HekaFS, but are not in this release.
 
 
 
== Matahari ==
 
 
Fedora 16 features Matahari, a collection of APIs accessible over remote and local interfaces for system monitoring and management.  Matahari APIs are served via a collection of Agents.  Matahari also includes a framework for adding new Agents and APIs.
 
 
The available agents are:
 
* '''''Host''''' - An agent for viewing and controlling hosts
 
* '''''Networking''''' - An agent for viewing and controlling network devices
 
* '''''Services''''' - An agent for viewing and controlling system services
 
 
 
== pacemaker-cloud ==
 
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
 
Pacemaker-Cloud provides high availability for application services inside virtual machines on a single node.  This feature provides a shell for creating virtual machine images, associating resources with the virtual machines, and combining these images into a deployable.  A deployable can then be launched and monitored for high availability.  If virtual machines or applications fail, these components will be restarted reducing MTTR (mean time to repair) improving availability over manual operator restart.
 
 
Fedora ''guest virtual machines using systemd'' are currently non-functional until the following bugzilla is merged into rawhide: See [https://bugzilla.redhat.com/show_bug.cgi?id=702621 systemd defect 702621] discussion.
 
 
  
 +
{{Docs_beat_open}}
  
 
[[Category:Docs Project]]
 
[[Category:Docs Project]]
 
[[Category:Draft documentation]]
 
[[Category:Draft documentation]]
 
[[Category:Documentation beats]]
 
[[Category:Documentation beats]]

Revision as of 15:24, 15 January 2012

DocsProject Header docTeam1.png


Note.png
Beat is open
This beat is now ready to have Fedora 24 content added by the beat writer