Five main points of best practice in hybrid cloud Model Management

For enterprises with a hybrid cloud model for authentication, the implementation must be planned so that it can be managed as accurately as the existing private cloud. Below, we give a way to manage a mixed cloud, assuming it teams follow the corporate ITIL best practices.

No matter how carefully you choose public cloud services and how well you match your private cloud design, differences are inevitable. The greater the difference between two clouds, the more difficult it is to manage the two clouds as a single entity. You will also get the biggest gains from your existing hybrid cloud management strategy and best practices as much as possible.

The hybrid cloud management strategy should involve the following areas:

Configuration。 It teams must refine the best practices for creating, modifying, uncertain, and implementing cloud installations. Version-controlled development libraries and certified production images will make the configuration more efficient and secure. Wherever you are, the configuration should be created either in the public cloud or in a private cloud. But this is no longer a problem, the library system should clearly refine which cloud is associated with the image.

Change control. Although almost all businesses are mostly ITIL best practices, change control seems to be overlooked in many public cloud implementations. Many small IT departments see DevOps as a way to quickly implement changes from development to production. Although start-up software, a service firm, agrees with this flexibility, companies consider it a dangerous shortcut that hinders the adoption of a hybrid cloud model. As companies agree on the use of mixed cloud models, they need developers to introduce change control principles into rollback plan submission changes. Patch management needs to be completed in a specific number of days for a vulnerability alert release.

Security。 Mixed cloud security includes data encryption, access control policies, firewalls, and network rule execution in transport and hibernation. The Enterprise Risk Management Department should promote the implementation of the same or similar strategy across departments. If possible, it is better to extend a single sign-on method, such as Security Declaration Markup Language (SAML) or Lightweight Directory Access Protocol (LDAP). Key encryption is the only known and mandatory for enterprise it.

Fault monitoring. For a while, we heard cloud authorities say that device failure monitoring is not mandatory in the public cloud, and that the resilience of resource provisioning masks the failure of the infrastructure, thus easing the burden of strict fault monitoring. But with the recent High-profile infrastructure, the service (IaaS) outage, it's not that easy. Failure and performance alerts need to be sent to the core manager (MOM) in the manager. If the public cloud has an e-business function that is directly facing the customer, and a geographically distributed user experience Performance Monitor, it is necessary to ensure uptime.

Budget control. The elasticity of the cloud is a double-edged sword of budget control. As the IT staff is not paying attention, leave an extra instance open until he sees the monthly IaaS example Bill will understand. Unused resource alerts and alert instructions will be issued when IaaS or platform-service (PaaS) costs exceed critical values to assist you in maintaining budget control over the entire cloud resource.

Ultimately, cloud technology will evolve to allow businesses to simply expand private cloud management systems to effectively control the separate parts of the public cloud, while network links bind the two clouds. Enterprise It is most likely to need to merge at least some public cloud management systems to feed back to mom. Occurs when you use a feature such as content distribution network or large data, which does not exist in your private cloud.

Businesses will need to stitch up these new cloud systems and their existing centralized management systems to be able to use a single help desk and achieve total cost of ownership (TCO). IT managers have integrated management systems over the years; however, the cloud is a disruptive technology because it once again adjusts its management system.

The presence of mixed cloud applications signals that cloud technology is mature enough for the enterprise IT department to allow them to extend their sensitivity to a multi-tenant, mixed cloud environment. But the "DevOps Cloud Cowboy" period will fade the sunset as the enterprise IT department closes down data based on enterprise-class management best practices.

(Responsible editor: The good of the Legacy)