Planning is an important first step in building a cloud computing solution. When planning, you need to create a complete document of the current datacenter assets and running processes, you need to describe the relationships between existing devices in the datacenter, and consider how to deploy future new devices.
Because of the complexity of the environment, the enterprise assigns different people to maintain different data in the datacenter. You need to understand the interaction between all the different roles and data center devices, and responsibilities overlap between roles. Top decision-makers in an enterprise need to participate in the process and make decisions.
Data Center full asset information
The
data Center includes a large number of servers and devices that first need to collect information about the hardware assets and the relationships between those assets. The relationship between assets is important for planning. Here's an example of the relationship between a server and a network:
through a logically defined IP address the server must define a network interface in the operating system to define the IP address server must have a physical NIC to support the network interface defined in the operating system with specific properties such as MAC address, Used to connect the NIC through physical links and other devices in the datacenter must be connected to a port on the switch and the switch also has its own relationship, such as which module the port belongs to, and the connection between the switches. The above asset information needs to be collected. Figure 5-9 shows an example of a datacenter:
Figure 5-9 Data Center Paradigm
to draw business data streams
After the device logic is documented, it is important to correctly understand the process of configuring these devices in order to determine which parts of the automation deployment can be implemented. It is also important to understand the use of equipment in business functions. Based on this information, we can basically determine the infrastructure of the data center, such as routers, switches, database servers, and load balancers, these devices have fewer changes and are configured in a special way, so it is not appropriate to use automated deployments. The application server usually uses the same hardware and changes frequently, and it is more appropriate to use automated deployments based on the information analysis we collect. The following figure is an example of a business data flow:
Figure 5-10 Data flow for a data center paradigm
After the
automated deployment, you can deploy a server from bare metal to an operating system deployment to an application deployment without human intervention, and then be able to add this new application server to the application server cluster and start providing services externally. Understanding the manual deployment process
After documenting the current structure and usage of the datacenter device, document the IT process that manages the data center. This allows the device to be sorted into a list of steps from arrival to entry into the data center. This list includes manual steps such as shelves and power calls, and automated steps that can be integrated into an automated management platform. The deployment process is typically across organizational roles and should be combined with existing automation technologies to form a complete solution.
with this documentation, you can understand that the parts of a data center can be managed using automation. Each organization has a unique set of steps to implement automated management, and each step has different requirements, so this automated management platform is not a static solution to all problems. For each user's different environment, different processes, we need to customize the cloud computing platform. In order to meet the needs of different users. Organizational Structure
automated deployment involves a number of complex steps, including physical infrastructure, operating systems, network infrastructure, application deployment, monitoring, project management, and coordination with other departments. General day-to-day server deployments do not need to be coordinated with other departments, unless there are organizational, security, or other reasons.
in many organizations, many parts of the architecture are considered critical to the business. For example, the network Architecture Department needs service-level agreements that meet network availability and change management and security issues. And cloud computing platforms often need to change the IT culture, and to better use the platform, you need to integrate every department in your organization. Standardized
Many organizations ' IT environments are heterogeneous, which complicates the implementation of cloud computing platforms. The best way to do this is to use a standard hardware configuration for data center devices that minimize hardware types. For example, for the application server layer, using a unified hardware platform can reduce the amount of manual configuration for each server. and current automated process integration
Many organizations have used automated deployments at different levels of the IT infrastructure, such as starting servers, software subcontracting, system management software, and custom scripts to run day-to-day tasks. But these automation technologies are aimed at a certain subsystem or local, in the process of deploying the whole system or need a lot of human intervention to complete. The cloud computing platform does not completely replace the existing technologies, but relies on these automated technologies and processes to achieve a higher level of overall automation management.
