OpenStack - session 1

Here are couple of good videos to start with:

- OpenStack 101 from Rackspace. 6 mins
   a quick introduction about Openstack. Worth watching if you are not familiar of OpenStack.

- Introduction to OpenStack from Sandy Walsh Nov 2012 32 mins
   Good history overview and concept overview.

- OpenStack Grizzly Architecture 101 from Ken Pepple Apr 2013(Summit) 43 mins
  a good explanation of the architecture of Grizzly release of OpenStack.

- OpenStack Grizzly Dashboard Demo from Mark Collier 2013 7 mins
 COO of OpenStack Foundation 

- OpenStack 101 from Joshua Mckenty Oct 2012 43 mins
  has anology between linux kernel and openstack. quite interesting. advocate guys not download from openstack directly, and should try some distributions from other companies. kind of advertisement. ;)

You can find a good writing about the Grizzly architecture from Ken Pepple:

http://www.solinea.com/2013/06/15/openstack-grizzly-architecture-revisited/

- writen in Python
- deamon/service using WSGI Paste
- Dashboard is a Django app

1, Identity (Keystone) <-> AWS IAM
    includes back-end of identity, catalog, token, policy 
2, Dashboard (Horizon) Django app <-> AWS deployment/Management services like CloudWatch/CloundFormation
3, Object Storage (Swift), object basically is files <-> AWS S3
    not FTP server, not mount as file share, not file server.
    should be accessed (via API or HTTP) through swift-proxy
    account / container implemented on SQLlite;
    object store implemented on disk;
    swift-proxy is the deamon
4, Image service (Glance) <-> no 
    glance-api is the deamon
    upload/download images(VM images), query/assign meta-data to images;
    glance-registry stores only meta-data about images, not images itself;
    actual images have plugable backend to support the images storage, 
    usually via swift(as actual image repository)
    misc: caching images, pre-fetching images;
5, Compute (Nova)
    initiates most of the orchestration activities;
    policy - quota checks;
    nova-compute orchestrate hypervisor;(is a worker deamon that creates and terminates virtual machine instances via hypervisor's API)
   <<openstack is not hypervisor, it's not virtualization, it's a framework to control virtualization>>
   support VMware(VMware API), Hyper-V, KVM(libvirt), Xen(Xen API).
   all below interactions are via queue services(messages)
   nova-api -> nova-scheduler -> nova-compute (->glance-api) -> nova-conductor
   nova-scheduler determine which nova compute server to use;
   nova-compute retrieve image, talk to hypervisor to create the instance;
   nova-conductor mediate the access to database for nova;
   database stores the all of the state of your current running cloud;
   queue can be implemented with different technologies; 
   nova-consoleauth provides console service;
6, Block Storage(Cinder)
   moved out from Nova;
   Cinder-Volume; interacts with a variety of storage providers;
   Cinder-scheduler;
7, networking (quantum)
   allows to create layer2 or layer3 networks;
   plugins & agents from different providers;