Skip to main content

SPOT Framework

The SPOT framework of cloud governance enables easy understanding of how cloud governance can be established in an organisation.

SPOT stands for-

S- Stakeholders and Scope

Like the SOA governance, cloud governance also demands stakeholder and decision authority enablement. For instance, who is held accountable for the deployment of cloud? Who makes decisions on the procurement of cloud solutions? The cloud governance committee must be formed with the participation of employees from different departments such as IT, compliance, legal, audit, the particular line of business and risk management.

P-Policies and Processes

The “Policies and Process” part of the framework refers to defining and mapping of each governance policy and process to its respective dimension in the cloud governance lifecycle management. Legal contracts, SLA management, architectural processes and fault alerts are some of the processes established through this component of the SPOT framework.

O – Organisations

Cloud governance is an expense and a massive task for any organisation. Determining the different bodies that can undertake various responsibilities of cloud governance is an easier approach to achieving better results. This includes:
The Executive Team that takes care of the end-to-end operations of the cloud.
The Operations Team takes responsibility of all routine cloud activities with special attention to resource management.
The Cloud Working Group is in charge of all activities such as cloud pilot and R&D established before the adoption of cloud.
The Consumer Stakeholder Board is responsible for all activities needed to steer the cloud adoption process. Examples include pricing, accounting and so on.

T – Technologies and Tools

The field of cloud governance has a vast range of proven techniques and tools that must be deployed during various stages of the governance lifecycle. Some of the common tools used by enterprises are cloud contract tools, cloud management and monitoring tools and cloud services portfolio.

Comments

Post a Comment

thank you for visiting :)

Popular posts from this blog

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

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

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

tag