Difference between revisions of "TryStack"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<!-- ## page was renamed from [[FreeCloud]] --> | <!-- ## page was renamed from [[FreeCloud]] --> | ||
| + | |||
| + | <pre><nowiki>#!wiki caution | ||
| + | '''This page is out of date''' | ||
| + | |||
| + | !FreeCloud has been renamed to TryStack and many of the details have changed. You can find more current information on www.trystack.org | ||
| + | </nowiki></pre> | ||
| + | |||
| + | |||
= What is [[FreeCloud]] = | = What is [[FreeCloud]] = | ||
Revision as of 16:43, 15 February 2012
#!wiki caution '''This page is out of date''' !FreeCloud has been renamed to TryStack and many of the details have changed. You can find more current information on www.trystack.org
What is FreeCloud
FreeCloud is a public deployment of OpenStack that highlights a set of common reference architectures and enables users to try out the OpenStack APIs for managing cloud computing resources.
The project is designed to be a public sandbox for individuals and companies interested in the following:
- Writing software that calls or extends the OpenStack API
- Understanding best practices around deploying OpenStack on a variety of reference architectures
The project also serves as a unique place for the OpenStack development and deployment community to:
- Identify problems with packaging and deployment
- Gain experience administering an OpenStack cloud on a variety of heterogeneous hypervisors and network topologies
- Documenting differences in behaviour, functionality and performance between different reference architectures
<<TableOfContents()>>
Details
Users of FreeCloud can launch instances in one of the FreeCloud zones. Each zone is a reference architecture that highlights different hypervisors and configuration settings. The instances last one week, at which point they are destroyed; therefore FreeCloud is not meant for permanent storage or compute resources, but rather as a test-bed for OpenStack enthusiasts and developers to experiment with the OpenStack API.
Proposed Terms of Service
We want to provide the following unique terms of service for FreeCloud users:
- All users have an allotment of 1GB of RAM resources
- Users can allocate any number of instances they wish, with the cumulative RAM of all instances not to exceed 1GB
- Instances have different expiry times, based on the instance's RAM size and CPU count:
- * 256MB / 1 CPU -- 72 hour expiry time
- * 512MB / 1 CPU -- 48 hour expiry time
- * 1024MB / 1 CPU -- 24 hour expiry time
- * 1024MB / 2 CPU -- 12 hour expiry time
The Code
The code that runs FreeCloud is a collection of deployment scripts/modules and scripts that automatically purge instances after a certain amount of time. This code lives at https://launchpad.net/freecloud. Feel free to check out that code and contribute any code you feel would be helpful.
OpenDevOps
For operators, FreeCloud is the place of OpenDevOps Community. OpenSource Community is a collaboration of coding. OpenDevOps Community is a collaboration of operation. We can share know-how for effective operations, experiences and troubleshooting burden. All technical information,which includes server architecture, development tools and management tool will be Apache2 License. FreeCloud-Admins (https://launchpad.net/~freecloud-admins ) has responsibility for operating FreeCloud. We are happy to see you joining FreeCloud admins. We have a weekly meeting, so please join us.
IRC freenode.net #freecloud
Team meeting Tuesday: * EDT 7:00pm * PDT 4:00pm * JST 8:00 am (Wednesday)
Etherpad http://etherpad.openstack.org/freecloud
Contribution for OpenStack Communities
Reference architectures : We define some reference architectures which is ensured by real operation on FreeCloud Deployment tools : cobbler and puppet based deployment tools enables admins to install OpenStack clusters just a inserting Disk to management servers. Operational tools: We provide tools to help daily operation.
Milestone
MileStone of FreeCloud is based on OpenStack milestone. After the major release we start each version's FreeCloud. First primary target is FreeCloud Diablo. We open the FreeCloud Diablo on next design summit.
Service Level Agreement
TBD Basically, it is no warranty (Eg Apache2 Licence.) User can not host some private data. User can not use illegal action (SPAM or something like that)
How to use FreeCloud
TBD
[Plan]
some questionnaire and agreement for SLA needed -> You can use the cloud for a week.
Implementation of FreeCloud
Architecture
Deployment tools
- Deploy master server iso (TBD)
- Deploy agent image (TBD)
- Cobber (TBD Cobber configuration must be linked here) - Puppet https://github.com/puppetlabs/puppetlabs-openstack
Services
nova,glance,keystone,dash-board,clanavi
Public cloud
Configurations
- OS : Ubuntu
- Hypervisor : XEN
- DB : MySQL
troubles in setup
Private cloud
Configurations
- OS Cent OS
- Hypervisor: KVM Server
- DB PostgreSQL
