Architecture of a cloud hosting service using python technologies: django, ansible and celery
summary
A self‑hosted managed web service is running a Django web panel that 200 users and 400 websites use to request VMs, domains and TLS; requests enqueue Celery/Redis tasks that run Ansible playbooks against hosts so Django panel triggers Ansible playbooks via Celery and installs users, SSH keys and packages. VM provisioning uses a VM API and evolves from VMware to Xen to enable migrated from VMware to Xen for live migration with DRBD/pacemaker HA. Monitoring uses statsd/collectd and Graphite and logging via ELK and certificates via Let's Encrypt and SSHFP/DNSSEC.
AI-written summary · about
chapters (13)
- 0:00Start
- 13:52ANSIBLE PLAYBOOK
- 14:18ANSIBLE ROLE
- 15:00ANSIBLE HANDLER
- 16:15AUTHORISATION (LDAPISH BASED)
- 18:47IP REGISTER API
- 22:01CENTRAL INVENTORY
- 22:16API COMMUNICATION TYPES
- 22:29ASYNC TASKS
- 25:47VM ARCHITECTURE (1)
- 26:08VM ARCHITECTURE (3)
- 31:16SECURITY
- 34:12METRICS AND LOGGING
related talks
42mBuilding a hosting platform with Python
48mDeploying web applications to the cloud with Python
43mHosting and DevOps for Django
42mBuilding a hosting platform with Python
50mBest Practices for Python in the Cloud
48mDeploying web applications to the cloud with Python
30mDeploying scalable Django application on AWS
23mDevOps with Python