Skip to main content

Understanding the Best Practices

Some of the best practices of cloud implementation are as follows:
Best Practice #1
Choose the right cloud service provider
With the checklist outlined in the first section of this chapter, making the right vendor choice becomes easy for any organisation. Assess their availability, performance and security measures well before you start working with them, and focus on crafting a foolproof SLA.
Best Practice #2
Adopt a phased-in approach
While moving to the cloud, organisations literally share their right of control over their data with the cloud vendors. While this may be a difficult decision to make, using the phased-in approach can reduce the mental stress caused due to physical relocation of data. In this approach, the organisation moves data to the cloud only in parts rather than putting the whole thing into the cloud.
Best Practice #3
Leverage the goodness of the cloud with creativity
Cloud offers an unprecedented level of flexibility and scalability to enterprises. IT managers and administrators must leverage the power of cloud creatively to derive the best benefits from the cloud investment.
Best Practice #4
Audit to ensure better security in the cloud
Regular assessment of problems, compliance of policies set earlier and identification of required upgrades must be performed to ensure the highest level of security for the cloud system. Audit tools are available to perform these functions and the right ones must be adopted by the organisation.
Best Practice #5
Keep data closer to lower latency and costs
Placing data as close as possible to the compute and processing resource reduces latency. Additionally, this practice also reduces the cost of shipping data as organisations pay for the bandwidth used in the cloud.

Comments

Popular posts from this blog

Special Permissions in linux

The setuid permission on an executable file means that the command will run as the user owning the file, not as the user that ran the command. One example is the passwd command: [student@desktopX ~]$ ls -l /usr/bin/passwd -rw s r-xr-x. 1 root root 35504 Jul 16 2010 /usr/bin/passwd In a long listing, you can spot the setuid permissions by a lowercase s where you would normally expect the x (owner execute permissions) to be. If the owner does not have execute permissions, this will be replaced by an uppercase S . The special permission setgid on a directory means that files created in the directory will inherit their group ownership from the directory, rather than inheriting it from the creating user. This is commonly used on group collaborative directories to automatically change a file from the default private group to the shared group, or if files in a directory should be

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the

RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version

import tweepy /usr/lib/python2.7/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!   RequestsDependencyWarning) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/dist-packages/tweepy/__init__.py", line 14, in <module>     from tweepy.api import API   File "/usr/local/lib/python2.7/dist-packages/tweepy/api.py", line 12, in <module>     from tweepy.binder import bind_api   File "/usr/local/lib/python2.7/dist-packages/tweepy/binder.py", line 11, in <module>     import requests   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 97, in <module>     from . import utils   File "/usr/lib/python2.7/dist-packages/requests/utils.py", line 26, in <module>     from ._internal_utils import to_native_string   File "/usr/lib/python2.

tag