(outline) |
(bring everything up one level) |
||
| Line 4: | Line 4: | ||
'''Fedora Cloud SIG''' | |||
= Our Goals = | |||
(mission) | (mission) | ||
= Quick Links = | |||
- ec2 | - ec2 | ||
- docs | - docs | ||
- participate (below) | - participate (below) | ||
= What Do We Mean by "Cloud"? = | |||
(this should probably be a short paragraph and a link for more) | (this should probably be a short paragraph and a link for more) | ||
= Areas of Activity = | |||
== Fedora in the Cloud == | |||
''Cloud guest images and cloud guest issues.'' | ''Cloud guest images and cloud guest issues.'' | ||
| Line 29: | Line 29: | ||
Constituents: anyone interested in development and production use of Fedora as a server platform | Constituents: anyone interested in development and production use of Fedora as a server platform | ||
== The Cloud on Fedora == | |||
''Cloud platforms packaged for and running on Fedora.'' | ''Cloud platforms packaged for and running on Fedora.'' | ||
| Line 39: | Line 39: | ||
Constituents: upstream cloud infrastructure projects, downstream distros using Fedora, Fedora as tech preview, Fedora as testbed, Fedora as part of real infrastructure (ovirt-node). Special note for EPEL. | Constituents: upstream cloud infrastructure projects, downstream distros using Fedora, Fedora as tech preview, Fedora as testbed, Fedora as part of real infrastructure (ovirt-node). Special note for EPEL. | ||
== The Cloud ''for'' Fedora == | |||
''The Fedora Project as a user of cloud technologies.'' | ''The Fedora Project as a user of cloud technologies.'' | ||
| Line 49: | Line 49: | ||
Constituents: Fedora contributors | Constituents: Fedora contributors | ||
== Fedora as Cloud End-Point == | |||
''Desktop and mobile devices running Fedora connect to cloud services.'' | ''Desktop and mobile devices running Fedora connect to cloud services.'' | ||
| Line 59: | Line 59: | ||
Constituents: users of Fedora as a desktop or mobile operating system. Special note for privacy and data-control concerns. | Constituents: users of Fedora as a desktop or mobile operating system. Special note for privacy and data-control concerns. | ||
= Participating in the Cloud SIG = | |||
(nothing fancy required to join... ways of participating below...) | (nothing fancy required to join... ways of participating below...) | ||
== Mailing List == | |||
== IRC == | |||
== Virtual Meetings == | |||
== Conferences == | |||
Revision as of 13:09, 16 October 2012
This is a draft for an updated Cloud SIG web site. Please see the current page at Cloud SIG, which has actual useful information.
Fedora Cloud SIG
Our Goals
(mission)
Quick Links
- ec2 - docs - participate (below)
What Do We Mean by "Cloud"?
(this should probably be a short paragraph and a link for more)
Areas of Activity
Fedora in the Cloud
Cloud guest images and cloud guest issues.
- ec2 images - other public cloud providers - images for private or hybrid clouds
Constituents: anyone interested in development and production use of Fedora as a server platform
The Cloud on Fedora
Cloud platforms packaged for and running on Fedora.
- openstack / eucalyptus / cloudstack / opennebula - openshift origin - owncloud / sparkleshare
Constituents: upstream cloud infrastructure projects, downstream distros using Fedora, Fedora as tech preview, Fedora as testbed, Fedora as part of real infrastructure (ovirt-node). Special note for EPEL.
The Cloud for Fedora
The Fedora Project as a user of cloud technologies.
- Fedora Infrastructure private cloud - connections with openshift? - other ways we can use cloud tech to benefit Fedora development
Constituents: Fedora contributors
Fedora as Cloud End-Point
Desktop and mobile devices running Fedora connect to cloud services.
- connecting with cloud accounts - software-as-a-service for fedora users - possible service offerings
Constituents: users of Fedora as a desktop or mobile operating system. Special note for privacy and data-control concerns.
Participating in the Cloud SIG
(nothing fancy required to join... ways of participating below...)
Mailing List
IRC
Virtual Meetings
Conferences
(note packaging and documentation as activities...)