Mirantis fuel puppet execution sequence and understanding of the entire project code execution process

Stage execution sequence stage {'zero ':}-> stage {'first' :}-> stage {'openstack-custom-repo ':} -> stage {'netconfig' :}-> stage {'corosync _ setup' :}-> stage {'openstack-Firewall ':} -> stage ['main'] 1. Class {'in in _ deployment ': Stage => 'zero'} First, execute begin_deployment2, class {": openstack :: logging ": running: openstack: logging. PP (involving rsyslog: Server. PP: openstack: logrotate. PP-> anacron module) 3. 'openstack-M m-repo' exist in these three files. 4. Class {"l23network: hosts_file": Stage => 'netconfig ', nodes => $ nodes_hash} class {'l23network': use_ovs => $ use_quantum, stage => 'netconfig'} class {'osnailyfacter: network_setup ': stage => 'netconfig'} class {'openstack: keepalive': Stage => 'netconfig', 5. Class {': cluster ': stage => 'corosync _ setup', class {'virtual _ ip': Stage => 'corosync _ setup6, class {'openstack: Firewall ': stage => 'openstack-Firewall', 7. Class {'corosync: commitorder': Stage => 'main '}

In the glance module of puppet, regristry. PP and API. PP are called by/openstack/manifests/glance. pp.
 

 
Glance. PP is composed/Openstack/manifests/controller. PP call
 

 
Controller. PP is called by/osnailyfacter/manifests/cluster_simple.pp cluster_ha.pp cluster_ha_full.pp (either of the three options)
 

 
Cluster_simple.pp, cluster_ha.pp, or cluster_ha_full.pp are called by the main site. PP according to the fuel_settings parameter.
 

 
/Openstack/manifests/controller. PP:
 

 
Install database (MySQL)-> keystone-> glance-> Nova-> cinder controller-> ceilometer-> horizon
 

Fuel_settings parameters are automatically generated when you select them on the web interface.

I understand it myself, and it may be wrong in some places.