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 Ansible Variables Configuration Processor Ardana Copy & Edit Links Site Specific Persisted State info/ html/ config/ definition/ 2

Configuration Processor Information Files 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. 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 Details the secrets that are generated by the configuration processor. The names of the secrets, the service(s) that use ntrol-plan name>.yml 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. 3

How do we map this to Ansible? 4

Input Model Key concepts Services - Attach to networks - Connect to other services (defined by Cloud 8) Networks - Route to other networks - Connect to specific servers - Can be tagged for specific usage by Neutron Servers - Have a role which defines: - Usage - Storage and network interfaces configuration Control Planes - Define sets of services hosted on specific groups of servers - Provide load balancers for their services 5

Main Areas of the Model 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? 6

Flexible Cloud Deployment – Expanded Controller Setup EXTERNAL VM EXTERNAL API INTERNAL API GUEST Provider VLANs MGMT PXE bond0 bond0 bond0 bond0 hed1 hed2 hed3 hed4 hed1 hed2 hed1 hed2 hed1 hed2 hed3 Keystone Swift Monasca Ceilometer MariaDB RabbitMQ compute Nova Neutron Logging Glance Swift Cinder root log crash root log Cass DB root maria rmq root log nova Volume Group Volume Group Volume Group vg1 vg2 PV1 PV2 PV3 PV1 PV2 PV3 PV4 PV1 PV2 PV3 PV1 PV2 PV3 3xCore Controller 3xMML 3xMariaDB/RMQ NxCompute 7

Main Areas of the Model Firewall Service Rules Regions Service Component Network Configuration Group Data Server Group Network Control Cloud Plane NIC Device Family Server Server Role NIC NIC Device Type Mapping Cloud Architecture Servers Disk Memory CPU Networking Interface Model Model Model Model Physical Constraints Cloud Knowledge 8

Cloud Model Service Endpoints are attached to Networks in a Network Group Networks in a group may be tagged as being significant for a Network service. Service Group A Network is Control Planes part of a run one or Network more Services. Network Groups may Group. define routes to Control Planes use A Cloud other servers and networks consists of one or Networks can be used Network Groups. from one or more more Control Planes. by servers in one or Control server groups. Cloud more Server Groups. Server Network Plane Group Servers can be Server in a Server Group. Groups can Networks within form a a Network Firewall Control Planes hierarchy Group route to Rules use servers with Server each other. Servers can be linked to a particular roles to run NIC Mapping that different sets of services. Firewall rules are enumerates network ports. Servers have a Role applied to one or which defines how more network groups. they will be used in the cloud. NIC The NIC Mapping Mapping provides the The Role of a server mapping of physical determines which interfaces. An interface model Can be Disk Model is used to The Role of a server determines maps network groups Server configured by configure its local which Interface Model is used to to specific sets of storage Role configure its network interfaces. customer (bonded) ports. Disk Defined by Model Interface Cloud 8 Model 9