Difference between revisions of "Plan/Discovery One/BootCamp"
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | = Boot Camp = |
| + | |||
| + | For the last couple of weeks we have been talking about how to hand over hosting and maintenance of Activities.sugarlabs.org. In order to transfer the necessary knowledge to the Students at Rochester Institute of Technology, I am putting together a 'Deploying and Maintaining a Scalable and Reliable Web Service' bootcamp. | ||
| + | |||
| + | The format is series of 5 talks and hands on session in which students learn about systems in general while using activites.sugarlabs.org as a case study. | ||
| + | |||
| + | The High level question is, "What do I wish I knew when I started working on ALSO." | ||
| + | |||
| + | == Session 0 Systems == | ||
Deploying and maintaining a scalable and reliable web service. | Deploying and maintaining a scalable and reliable web service. | ||
| Line 41: | Line 49: | ||
* addons.sugarlabs.org | * addons.sugarlabs.org | ||
| + | Lab - Gathering our tools. | ||
| − | == Stage 1 | + | == Stage 1 Basic Web Site Technologies == |
1. installing aslo | 1. installing aslo | ||
| Line 49: | Line 58: | ||
* configuration | * configuration | ||
| − | hands on- | + | hands on - Installing ASLO |
----------------- | ----------------- | ||
| − | == Stage 2 | + | == Stage 2 Caching == |
more memory | more memory | ||
| Line 58: | Line 67: | ||
squid | squid | ||
| − | hands on - | + | hands on - monitoring and benchmarking effects of memcached |
-------------- | -------------- | ||
| − | == Stage 3 Load balancing | + | == Stage 3 Load balancing == |
multiple databases | multiple databases | ||
| Line 69: | Line 78: | ||
---------------- | ---------------- | ||
| − | == Stage 4 Reliability | + | == Stage 4 Reliability == |
redundency | redundency | ||
failover | failover | ||
| − | hands on - setting up proxy, web node, and | + | hands on - setting up proxy, web node, and database failover. |
| + | |||
| + | and last but not least | ||
| + | backup | ||
| + | monitoring - munin | ||
| + | profiling - analytics | ||
---------------- | ---------------- | ||
| − | |||
| − | |||
Latest revision as of 15:50, 9 March 2010
Boot Camp
For the last couple of weeks we have been talking about how to hand over hosting and maintenance of Activities.sugarlabs.org. In order to transfer the necessary knowledge to the Students at Rochester Institute of Technology, I am putting together a 'Deploying and Maintaining a Scalable and Reliable Web Service' bootcamp.
The format is series of 5 talks and hands on session in which students learn about systems in general while using activites.sugarlabs.org as a case study.
The High level question is, "What do I wish I knew when I started working on ALSO."
Session 0 Systems
Deploying and maintaining a scalable and reliable web service.
1. Learning objectives
- What is ASLO?
- What is a system?
- What is scalablity?
- What is reliablity?
2. What is a System?
3. Why build a System?
4. Why are systems hard?
5. Critial thinking
- What is the problem being solved?
- What approach is being used?
- What benchmarks are being performed?
- What conclusions can be drawn?
- What are the next steps?
6. Parts of a web service.
- Model - database.
- View - html pages delivered to users
- Controller - web site code.
7. Activities.sugarlabs.org overview
8. What is the problem.
- Distribute activities
- Community of Users
- Community of developer
9. What is the approach.
- Links on a wiki
- Roll your own
- Build on existing open source project
- addons.sugarlabs.org
Lab - Gathering our tools.
Stage 1 Basic Web Site Technologies
1. installing aslo
- code - php.
- database - mysql.
- configuration
hands on - Installing ASLO
Stage 2 Caching
more memory memcached squid
hands on - monitoring and benchmarking effects of memcached
Stage 3 Load balancing
multiple databases multiple web servers
hands on - setting up slave server and multiple web nodes
Stage 4 Reliability
redundency failover
hands on - setting up proxy, web node, and database failover.
and last but not least backup monitoring - munin profiling - analytics