Skip to main content

Efficient Steps for migrating

cloud computing gains momentum, organisations are looking for a more robust way to approach the cloud. In order to leverage the benefits of the cloud, a strong cloud strategy must be in place. Based on the approach framed by the popular research firm, The Burton Group, the following five steps define the framework for a strong cloud adoption strategy:
1. Pre-work
To start with, organisations must build an internal cloud team, which together will set the scope of the cloud project. Expectations, standards to be achieved and cloud objectives must be well defined during the initial stages of the cloud journey.
2. Business and Application Analysis
The cloud cannot be considered as plainly a technical enhancement since it has a strong impact on the various business functions. During this stage, business applications moving into the cloud are evaluated based on the costs and architectural requirements. The operational changes to be made within an organisation are also determined. The four significant components of this stage are business impact evaluation, assessment of organisational impact, cost analysis and application analysis.
3. Selecting the Cloud Service Provider
Solutions from different cloud service providers are reviewed, and the most suitable one is chosen. The migration plan is initiated, and the road map to cloud is thus made clear.
4. Building the Risk Mitigation Plan
No cloud adoption framework can be complete without the risks and challenges being included. A risk mitigation plan is drawn and the exit strategy is devised.
5. Planning for the Steady State
Once applications are moved to cloud, there needs to be a plan in place for the cloud governance and vendor management. Regular reviews of the strategy must be conducted, and the cloud team must ensure that both internal processes and personnel issues are addressed during the move.

Comments

Post a Comment

thank you for visiting :)

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
Post a Comment
Read more

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
Post a Comment
Read more

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.
Post a Comment
Read more

tag