SUSE Cloud 8 CLM Overview Input Model and Configuration Processor - - PowerPoint PPT Presentation
SUSE Cloud 8 CLM Overview Input Model and Configuration Processor Configuration Processing Flow Key Build Artifacts Ansible Playbooks Ardana release Configuration file templates Generated Customer Examples Service Edit Definitions
config/ definition/ info/
Configuration Processor
Examples Ardana Service Definitions Configuration file templates Site Specific Copy & Edit Links Persisted State Ansible Variables Ansible Playbooks html/ Build Artifacts
Ardana
release
Customer Edit Generated
Key
2
3
File Provides details of address_info.yml IP address assignments on each network. firewall_info.yml All ports that are open on each network by the firewall configuration. Can be used if you want to configure an additional firewall in front of the API network, for example. net_info.yml IP addresses assigned to services. route_info.yml Routes that need to be configured between networks. server_info.yml How servers have been allocated, including their network configuration. Allows details of a server to be found from its ID. service_info.yml Details of where components of each service are deployed. control_plane_topoloy.yml Details the structure of the cloud from the perspective of each control-plane. network_topology.yml Details the structure of the cloud from the perspective of each network address. region_topoloy.yml Details the structure of the cloud from the perspective of each region. service_topology.yml Details the structure of the cloud from the perspective of each service. private_data_metadata_<co ntrol-plan name>.yml Details the secrets that are generated by the configuration processor. The names of the secrets, the service(s) that use each secret and a list of the clusters on which the service that consumes the secret is deployed. password_change.yml Details the secrets that have been changed by the configuration processor. The information for each secret is the same as for private_data_metadata.yml explain.txt An explanation of the decisions the configuration processor has made when allocating servers and networks. CloudDiagram.txt A pictorial representation of the cloud. In addition to producing all of the data needed to deploy and configure the cloud, the configuration processor also creates a number of information files that provide details of the resulting configuration. These files can be found in ~/openstack/my_cloud/info after the first configuration processor run. This directory is also rebuilt each time the Configuration Processor is run.
4
5
Services
Networks
Servers - Have a role which defines:
Control Planes
6
Cloud Architecture: Which services are included? Where do they run? What are the regions? Networks: How does each service connect to the network? How is traffic routed between networks? Servers: What are the server “types” in the cloud? How should local storage be used? How do network interfaces map to networks? Physical Constraints: Which networks are connected to each group of servers? How are servers grouped for availability?
7 Keystone Nova Glance Cinder hed2 hed4 PV1 PV2 PV3 Volume Group root log crash Swift Neutron Swift hed1
3xCore Controller
Monasca Logging hed2 bond0 PV1 PV2 PV3 Volume Group root log Cass DB Ceilometer hed1
3xMML
MariaDB hed2 bond0 PV1 PV2 PV3 Volume Group root maria rmq RabbitMQ hed1
3xMariaDB/RMQ
compute hed2 hed3 bond0 PV1 PV2 PV3 vg1 root log nova hed1
NxCompute PXE MGMT Provider VLANs GUEST INTERNAL API EXTERNAL API EXTERNAL VM
vg2 hed3 bond0 PV4
8
Cloud Control Plane Service Component Interface Model Server Role Disk Model Server NIC Mapping Network Group Server Group Network Firewall Rules Configuration Data NIC Device Type NIC Device Family Memory Model CPU Model Regions
Cloud Architecture Servers Networking Physical Constraints Cloud Knowledge
Service
9
Cloud Control Plane Service Interface Model
Service Endpoints are attached to Networks in a Network Group Networks in a group may be tagged as being significant for a service. A Network is part of a Network Group. Control Planes run one or more Services. A Cloud consists of one or more Control Planes.
Server Role
Control Planes use servers with particular roles to run different sets of services.
Disk Model
The Role of a server determines which Disk Model is used to configure its local storage
Server
Servers have a Role which defines how they will be used in the cloud. The Role of a server determines which Interface Model is used to configure its network interfaces. Network Groups may define routes to
Network Groups.
NIC Mapping
An interface model maps network groups to specific sets of (bonded) ports. Servers can be linked to a NIC Mapping that enumerates network ports. The NIC Mapping provides the mapping of physical interfaces.
Can be configured by customer Defined by Cloud 8
Network Group Server Group
Servers can be in a Server Group. Networks can be used by servers in one or more Server Groups. Networks within a Network Group route to each other. Control Planes use servers and networks from one or more server groups.
Network
Server Groups can form a hierarchy
Firewall Rules
Firewall rules are applied to one or more network groups.