Kickstart your career with best deals on top training courses NY10 Click to Copy

Search

Impact On IT Service Management From Cloud Computing

In IT Service Management, the ITIL V3 philosophy stresses that “IT is the business.” This is truly realized for providers offering cloud computing services. There are a number of considerations that affect Service Management processes when moving to a cloud services model. Service Desk These traditional ITIL Service Support processes are tightly linked. In the cloud computing model, high expectations of availability are part of the model’s selling point, so rapid restoration of service becomes critical through the use of these processes and the Service Desk that performs them. Change management In addition, Change Management work flow activities can sometimes be done best by the Service Delivery Architects. They are the ones who determine the rules used by the automation tools rather than by the Service Management team, who traditionally performed those tasks now being done by the automation tools. Configuration and Asset Management With the Cloud service model’s standardized infrastructure and specialized tool sets, configuration is typically much simpler than that of an enterprise environment, with its extensive variety of hardware and software that must be orchestrated together. Many service-specific tools provide configuration capability for that service, thus reducing the amount of manual coordination requiredwhen compared to the Enterprise IT model. Asset management is related to configuration management and, in a cloud service, has both a virtual component (e.g. tracking virtual resources) and a dynamic component (i.e., assets can change every hour) to its management process.  Configuration Management needs to address a consumer view, (i.e., what assets belong to the service being consumed), a service view, (since assets equal revenue), and an enterprise view, (showing the business status of all cloud services being offered.) Service Level Management With a cloud environment, a single SLM process can exist, but separate SLAs and Service Level Packages should be defined, monitored, and managed for each service. The monitoring components for SLA related performance data will require tools that do not just rely on knowledge of the infrastructure, given the unpredictability of which cloud infrastructure components will actually be used. Instead, monitoring service performance and availability for ensuring SLA compliance must be done from the perspective of the user not from the perspective of the infrastructure. Availability, Capacity, Continuity, and Security The cloud environment’s “Provider-Consumer” model breaks the link between IT continuity and the customer’s business continuity. The Cloud service provider must offer to its customers a warranty of service continuity and make it part of the SLA that comprises the Service Level Packages offered by the service provider. With a cloud service provider, the hardware and software environments are much more uniform and more easily managed. With the provider’s more homogeneous infrastructure offering a much more stable environment, the risks from a change to production are significantly reduced. With reduced risk, Cloud service providers can deliver modifications to services much faster and hence their agility becomes a part of the business model and a distinguishing capability in the market. It also implies that the Release and Deployment Management (RDM) process is often replaced by a different paradigm. In the cloud model, scalability of capacity and performance is a core offering provided by cloud service providers and their SLAs should reflect this. To accomplish this real-time scalability requires two things on the part of the service provider. For cloud services, availability is vital; much of the availability must be architected into the service. Where once the technical developers of a service could ignore the availability issues of their applications, leaving that to the job of the IT organization, cloud service availability is a key factor to its commercial success and hence must be built-in by the service developers and service architects working with the IT organization. With a combination of tools and resiliency built into the design and implementation of the service itself, the responsibility for availability must be shifted into the development lifecycle long before a service goes into production.
Rated 4.0/5 based on 20 customer reviews

Impact On IT Service Management From Cloud Computing

495
Impact On IT Service Management From Cloud Computing

In IT Service Management, the ITIL V3 philosophy stresses that “IT is the business.” This is truly realized for providers offering cloud computing services. There are a number of considerations that affect Service Management processes when moving to a cloud services model.

Service Desk

These traditional ITIL Service Support processes are tightly linked. In the cloud computing model, high expectations of availability are part of the model’s selling point, so rapid restoration of service becomes critical through the use of these processes and the Service Desk that performs them.

Change management

In addition, Change Management work flow activities can sometimes be done best by the Service Delivery Architects. They are the ones who determine the rules used by the automation tools rather than by the Service Management team, who traditionally performed those tasks now being done by the automation tools.

Configuration and Asset Management

With the Cloud service model’s standardized infrastructure and specialized tool sets, configuration is typically much simpler than that of an enterprise environment, with its extensive variety of hardware and software that must be orchestrated together. Many service-specific tools provide configuration capability for that service, thus reducing the amount of manual coordination requiredwhen compared to the Enterprise IT model.

Asset management is related to configuration management and, in a cloud service, has both a virtual component (e.g. tracking virtual resources) and a dynamic component (i.e., assets can change every hour) to its management process.  Configuration Management needs to address a consumer view, (i.e., what assets belong to the service being consumed), a service view, (since assets equal revenue), and an enterprise view, (showing the business status of all cloud services being offered.)

Service Level Management

With a cloud environment, a single SLM process can exist, but separate SLAs and Service Level Packages should be defined, monitored, and managed for each service. The monitoring components for SLA related performance data will require tools that do not just rely on knowledge of the infrastructure, given the unpredictability of which cloud infrastructure components will actually be used. Instead, monitoring service performance and availability for ensuring SLA compliance must be done from the perspective of the user not from the perspective of the infrastructure.

Availability, Capacity, Continuity, and Security

The cloud environment’s “Provider-Consumer” model breaks the link between IT continuity and the customer’s business continuity. The Cloud service provider must offer to its customers a warranty of service continuity and make it part of the SLA that comprises the Service Level Packages offered by the service provider.

With a cloud service provider, the hardware and software environments are much more uniform and more easily managed. With the provider’s more homogeneous infrastructure offering a much more stable environment, the risks from a change to production are significantly reduced. With reduced risk, Cloud service providers can deliver modifications to services much faster and hence their agility becomes a part of the business model and a distinguishing capability in the market. It also implies that the Release and Deployment Management (RDM) process is often replaced by a different paradigm.

In the cloud model, scalability of capacity and performance is a core offering provided by cloud service providers and their SLAs should reflect this. To accomplish this real-time scalability requires two things on the part of the service provider.

For cloud services, availability is vital; much of the availability must be architected into the service. Where once the technical developers of a service could ignore the availability issues of their applications, leaving that to the job of the IT organization, cloud service availability is a key factor to its commercial success and hence must be built-in by the service developers and service architects working with the IT organization. With a combination of tools and resiliency built into the design and implementation of the service itself, the responsibility for availability must be shifted into the development lifecycle long before a service goes into production.

KnowledgeHut

KnowledgeHut Editor

Author

KnowledgeHut is a fast growing Management Consulting and Training firm that is a source of Intelligent Information support for businesses and professionals across the globe.


Website : http://www.knowledgehut.com/

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Delivering Messages Made Easy With Azure Service Bus

Integrating two different systems is often complicated and comes up with lots of challenges with respect to the availability of both systems, processing speed, scaling and many more. Amongst many recommendations for designing and developing applications for the cloud, enabling asynchronous communication between multiple services plays a vital role in achieving the reliability, scalability and the efficiency of the system.What are Message Queues?Message Queues is the solution to the challenges faced during Integration in distributed systems. It is an efficient way of enabling asynchronous communications between different software services.Following are three most important benefits Queuing solution comes with:1. Decoupling: Messaging queues provide a persistent storage and asynchronous communication and thus the availability of one service does not impact the another. They are eligible to work in a disconnected fashion.2. High reliability: Messaging queues use transactions to manage the message and help to roll back the transaction to recover the message, In case of a failure.3. Granular Scalability – Messaging queues helps to achieve granular scalability where the producer or consumer can scale on their own choice without even impacting the other.Azure Service Bus – A managed Queuing system on Azure CloudAzure Service bus is a highly scalable service that helps to achieve asynchronous messaging and exchanging data among decoupled systems. Moreover, since it is a Platform as a Service (PaaS) offering from Microsoft, thus, you don’t have to manage the Infrastructure and configuration. Azure cloud manages all this for you.Among all others, the most important feature of Azure Service Bus queue is that it guarantees messages to be delivered in FIFO order, which many other queuing solutions fail to provide, even Azure Storage Queues. This makes service bus the most suitable choice than any other Message Queues, though not the only choice. However, Other features to include high availability, auditing, Geo redundancy etc.Azure Service Bus has 3 offerings:1. Queues2. Topics and Subscriptions3. Relays1. Service Bus Queues:The queue is an optimum choice when we are implementing one-directional messaging and, we want to ensure that only one consumer can fetch the message. This is generally used when both the producer and the consumer are not online at the same point in time. All the messages sent by the producer are stored in the queue until consumed by the consumer or gets expired. Also, each message in the queue is identified by a unique Message-ID.Queues come with the assumption that the message needs to be consumed by only one service. However, in practical scenarios, one message might need to be delivered to multiple consumers on some business decisions or need to be broadcasted. To meet those requirements Service bus does have a different offering, Topics.2. Topics and Subscriptions:Topics also provide one-directional communication. However, it works on the publish-subscribe principle where the same message can be consumed by more than one consumer. A single topic may have multiple subscriptions associated with it. A Subscription is somewhat like Queue. When the topic receives the message, it delivers it to all the relevant subscriptions or distributes based on the subscription filters.3. Relays:Unlike Queues and Topics, Relays provides more sort of bi-directional communication. Relays do not support brokered messaging i.e. they don’t store any messages instead simply passes the message from one service to the other. Therefore, both the publisher and subscriber need to be active at the same point in time in case of relays. Relays are automatically created and deleted in a service bus namespace i.e. they need not be created beforehand and deleted post use by services.Azure Service Bus ArchitectureThe Azure Service Bus architecture is depicted in the figure below:Some Important Limits and QuotasLimit/Quota NameValueQueue/topic size1,2,3,4,or 5 GBIf partitioning is enabled -80 GBNumber of concurrent connectionsNet Messaging:1,000AMQP: 5,000Number of topics/queues per service namespace10,000Number of partitioned topics/queues per service namespaceBasic and standard Tiers- 100Premium- 1,000 {per messaging unit]Message size for a queue/topicKsubscription entityMaximum message size: 256 KB[Standard tier} I 1 MB (Premier tier).Number of subscriptions per topic2,0002,000Advanced Features of Azure Service BusAzure Service Bus also has some advanced features that can help you to solve most complex messaging problems. The key features are listed below:1. Dead LetteringService bus provides dead letter subqueue to store messages that could not be delivered or processed. Dead letter queues can be used to move expired or poisoned messages from the parent queue. Those messages then can be retrieved for further investigations. Dead letter queues need not be created manually but are automatically created with the queue.2. TransactionsService bus provides transactions to group multiple operations together into one execution scope. This ensures that all the operations within a group either succeed or fail together.3. Duplicate detectionEnabling Duplicate detection helps to identify duplicate messages added on the basis of the unique message id. The duplicate message could be added by an application on restart of unexpected failure or exception scenarios not handled. Such messages need not be handled manually by the application because the service bus automatically handles those messages.4. Batch processingBatch processing feature of Azure service bus helps to add and retrieve messages in batch instead of one by one message. This extends help to the systems that have to process bulk messages.5. SessionsSometimes the messages are bigger in size say more than 1 MB (maximum message size capacity of queues). Sessions help in such scenarios by sending the message in parts and allowing the processing of the same only when all the parts are received at the consumer end.SummaryMicrosoft’s PaaS offering, Azure Service Bus is really helpful in developing and implementing highly scalable services without even care about infrastructure. It provides asynchronous communication and ensures greater reliability.Azure also lets you select from different options in service bus - for brokered and one directional message we have Queues and Topics and for non-persistent and bi-directional messages we have Relays.
Rated 4.0/5 based on 2 customer reviews
5487
Delivering Messages Made Easy With Azure Service B...

Integrating two different systems is often complic... Read More

How To Configure Jenkins With BITBUCKET - Cloud Computing

PURPOSE:This article will provide you a complete detailed knowledge of configuring Jenkins with Bitbucket repository which will help in automating the deployment process and will help to set the path for the interaction of Jenkins continuous integration tool with bitbucket repository.INTRODUCTION:As a part of the continuous integration and deployment process, it is a requirement that the code repository should have an interaction with the build automation and continuous integration tool. In this article, we are working with bitbucket and Jenkins to achieve the same, but this could be similar to the other tools that are available in the market. Let’s see the steps to integrate a Bitbucket with the Jenkins.Ways for Enabling Jenkins with Bitbucket:STEP 1: Login to your Jenkins and then select Manage Jenkins->Plugin Manager and on the tab available select the option bitbucket plugin and click on install without restart. In my case, this is installed already hence it’s showing under the Installed section.Step 2: Once the installation is done, configure a sample project and in build triggers section during the creation of a new project select build when a change is pushed to bitbucket and click apply and save to enable trigger Jenkins with bitbucket:Step 3: Now, visit Bitbucket URL: https://bitbucket.org/ and create your own repository, if you haven’t created yet else visit your own bitbucket repository for the purpose of this course. I have LearnShareKnowledge as the repository-Step 4: Click on the clone and copy the repository URL which you want to configure with Jenkins from bitbucket:Step 5: Go back to Jenkins and click on the project which you have to create and click on configure under the Source Code Management section, select the repository type which you have in your bitbucket repository. In my case, it is git and paste the URL by removing git clone to connect Jenkins with bitbucket. Click on save to reflect the changes:Step 6: Select the credentials if it is not a public repository for configuring the credentials, you can click the Add button on credentials section and proceed with username and password under global credentials domain and click Add.Step 7: Now, again visit the bitbucket repository which you want to configure. For that, click on settings under that repository:Step 8: Under settings, click on webhooks highlighted in the picture:Step 9: Click on add webhook and give the title to that webhook and paste the URL of Jenkins which you have configured with bitbucket and then select active and repository push and save the changes. If you want to make this more secure, then you can verify this with SSL certificate but in my case,  I used a secure key which provides a security to this setup:Now with the Jenkins setup for Bitbucket, we are ready to test the complete configuration. As soon as you do commit to the repository, you will be having an automated build triggered initiating a job inside the Jenkins project which you have configured with the repository.
Rated 4.0/5 based on 3 customer reviews
How To Configure Jenkins With BITBUCKET - Cloud Co...

PURPOSE:This article will provide you a complete d... Read More

Team Collaboration: The Benefits Of Using Cloud Tools

According to Forbes Insights: Collaboration in the Cloud,the ability to mingle across geographical parameters, time zones, or even organizational borders is becoming an ever more critical foundation of success. The cloud has reached a place where it has become an integral part of our everyday work-lives. Based on its affordability and colossal effectiveness, modern entrepreneurs are using cloud services to build and run their small businesses, while working with people from different parts of the globe. In fact, collaborative work based on cloud technology has already proved its competency in bringing your most diverse teams together. By working together on on-site and off-site documents alike, cloud collaboration tools allow your team members to ingress, edit and even share files outside of the company firewall. Thanks to the growing practices of BYOD (Bring Your Own Device) and remote employment, cloud tools are fast becoming permanent features of the contemporary workplace. Modern-day workforce wants to move and communicate easily between various devices and cloud collaboration helps them to do that. Perks Of The Cloud Despite the increasing trend of cloud collaboration to amplify business productivity, many small businesses are yet to understand its benefits. According to the report published by Endurance International Group, many entrepreneurial ventures fail to take advantage of the significant advances in cloud collaboration technology and are also “unfamiliar with some of the most advantageous online tools.” The study also found that even though one-third of the respondents had heard of the term, they were unsure of what cloud computing actually meant. While 11 percent of the group said they rely on cloud collaboration for their business functioning,  67 percent of people admitted to not having invested in the technology yet. As a business person, if you too are thinking of investing in cloud tools for collaboration, here are the five basic benefits of the practice for start-ups and their teams. Easy Deployment & Maintenance SaaS (software as a service) collaborative solutions, often requiring little more than a license activation to get you up and running, are easy to install and maintain – with no unnecessary software downloads or costly, time-consuming hardware installations. Often by simply entering an email address, you can test a cloud-based collaboration product with a free trial. By taking advantage of free trials, you can be more confident when it comes time to purchase. Cost Effective Many of the cloud collaboration perks are linked to its cost-effectiveness. Unlike the age-old, on premise software, you don’t have to invest in pricey infrastructure with cloud-based collaborative tools. They also eradicate the need for expensive customization and heavy IT involvement. Following the pay-as-you-go model, cloud collaboration is indeed a cost effective solution for tech-businesses. The computer billing method, under this utility, only requires you to pay for procured, rather than actual computer resources. This means, instead of paying for an entire infrastructure in the case of in-house IT department, you only have to pay for the services used in a given month. Since cloud-based collaboration allows employees to work from remote locations, you can actually cut off office overheads, making it especially beneficial for entrepreneurial ventures that usually have a strict work budget. After subtracting the upfront and extensive capital expense, you can also mitigate project risk by using cloud technology to your advantage. Everything is web-based, which means no time-consuming installation, system configuration or maintenance involved either. Thus, as a part of tech-service industry, you don’t have to bother about constant updates or server upkeep. Boosts The Project Management Process The ability to connect people to share information when it’s most needed is one of the key advantages of cloud collaboration tools. Besides, it helps businesses streamline the documentation process by keeping all project related files within the same workspace, allowing them to manage everything in a single domain; the cloud. With these collaborative project management tools, you can retain archived versions of all your information and update them in real time. Additionally, your team members can add tasks and comments to each file, providing you with a detailed audit trail of all project related interactions. You can even create and manage task lists, making your overall project management much faster and simpler. According to a 2014 Software Advice study, thousands of interviewed buyers, shopping for the right project management tool, revealed that around 46% of small business consumers were using manual methods like email, pens, papers and Excel. But companies that have a cloud-based deployment preference voted for cloud solutions over on-site disposal. And the biggest chunk, around 98% of them looked for project management as one of the integrated services in their cloud collaboration tools. The challenging aspect of projecting across various stand-alone platforms makes the reason behind such preferences quite obvious. Nonetheless, the key is to find a collaborative tool that helps you create and manage milestones and goals seamlessly to keep your project on track. Syncing Files & Data By hosting the on-going project documents, shareable records, presentations and more in the cloud, your files are automatically synced and available from any of your devices. Without any additional action required to access the file, a presentation can be uploaded from your work computer and further presented from your tablet at home. You can also easily share documents with your co-workers without the need to remain in the same office. Greater Scalability Cloud based technologies are famously known for their flexibility and scalability. Using a cloud-based collaboration tool, you can start small and add on the resources as the demand increases. It is often the case for start-ups that the number of participants and the volume of contributions increase rapidly in-between projects. Under cloud collaboration, it becomes easier to cater to such growing demands without adding much cost. The most important benefit of cloud tools is they allow you to scale for users, workload and adoption. You can, therefore, accommodate the growth seamlessly. Without making any infrastructure investment, you only have to pay for additional storage and users as you need them. Additionally, you can manage peaks in demand by automatically allocating managing team performance and capacity when facing data-intensive periods. This helps you achieve greater organizational agility. In Conclusion The outlook of cloud collaboration is such that it serves companies and the mobile workforce with multiple locations and allows remote workers to access information seamlessly across devices, helping them to become more productive at work. Upon understanding the real benefits of cloud collaboration, you will also realise that its goal is to provide a natural working experience with your team members, even when that’s not the case.      
Rated 4.0/5 based on 20 customer reviews
Team Collaboration: The Benefits Of Using Cloud To...

According to Forbes Insights: Collaboration in the... Read More

other Blogs