Azure DevOps Implementation

About Redington
Redington (India) Limited one of the leading value-added distributors since 1993 with presence in India, Middle
East, Africa, Turkey, Sri Lanka, Bangladesh, and CIS countries over 100 leading manufacturers of Information
Technology, Telecom, Lifestyle and Consumer Electronics Products.

Redington is investing and strengthening its capability as a “Cloud Solutions Provider”, tied up with the best cloud
service providers such as AWS, Microsoft, IBM, Oracle, Fresh Desk, Sapphire and many more.

Our services include.

 One time setup and Implementation

 Security implementation
 Migration services
 DevOps Services
 Hybrid deployment (on-prem and cloud integration)
 Managed Services (Monitoring & Optimization)
 Infrastructure discovery and solutions

Customer requirement

Customer wants to deploy PHP applications on Azure virtual machine through Azure DevOps CI CD
automation for DEV, QA and Demo environments.

Assumptions:
 Azure subscription: An Azure subscription with the necessary permissions to create and manage resources.
 Source Code repository: Source code for the application is stored in GitHub.

In Scope:
Infrastructure Setup:
 Create Azure Virtual Machines with appropriate specifications.
 Select and install the required operating system.
 Configure networking, including virtual network, subnet, and security groups.
 Install and configure necessary software components, including:
- Web server
- PHP runtime environment.
Security Implementation:
 Establish firewall rules and network security group (NSG) settings.
 Configure SSL/TLS certificate for secure communication (HTTPS).
 Implement regular security updates and patches.
 Apply role-based access control (RBAC) for Azure resources.
 CI/CD Pipeline Setup:
 Connect with existing source code repository (GitHub).
 Configure one CI/CD pipeline (Including DEV, QA and Demo stage) that triggers builds and deployments on code
changes.

Deployment Strategies:
 Design and implement deployment strategies based on project requirements.
 Define and enforce security policies and best practices with respect to Azure DevOps.

Monitoring and Logging:

 Set up monitoring and logging solutions with Azure native services as per project requirements.

Out of Scope:

 Application Development: The project assumes that the application code is already developed and
tested. Application development, debugging, and bug fixes are not included in this scope.
 Third-Party Integrations: Integrations with external systems or third-party APIs.
 Database Management: Configuration, management, and scaling of databases (such as Azure SQL Database)
are not part of this scope.
 Application Design: High-level application architecture, design decisions, and choosing
technologies/frameworks are assumed to be completed outside of this project.
 Application Monitoring and Tuning: Performance tuning, optimizing application code, and handling application-
specific performance issues are considered separate tasks.
 Data Migration: If migrating data from an existing system is required, the data migration process itself is
not included in this scope.
 Testing automation will be out of scope.
 Any customization with respect to Azure boards.
 Implementation of any other service apart from services mentioned in the commercial.
 Any License procurement.
 Anything which is not mentioned in the scope of work.

Dependency:
 Azure Subscription: Access to a valid Azure subscription is required to create Azure Container Registry, and
other necessary resources.
 Application Codebase: The application's source code, properly versioned and organized in a repository, is
a fundamental dependency.
 Third-Party Integrations: If the application relies on third-party APIs or services, those integrations should
be established and already tested.
 Application Dependencies: The project should ensure that any application dependencies, libraries, or
external components are available and compatible.
 SSL Certificates and Secrets: If the application requires SSL certificates or secrets, they should be already in
place.
 Project Team Availability: The availability of project team members, including developers, and operations
personnel, is important to progress the project.
Project Success criteria:

The successful creation of a fully automated deployment pipeline in Azure DevOps, ensuring that code changes are
automatically built, tested, and deployed to the Azure VM for Dev, QA and Demo environments.

Project Risks:

• Infrastructure and VM Configuration: Improper VM cluster configuration, network policies, or security settings
can lead to deployment failures, vulnerabilities, or connectivity issues.
• Application Compatibility: The application may not be optimized or fully compatible with Kubernetes, leading
to performance bottlenecks or unexpected behavior.
• Integration and Dependency Issues: Dependencies on external services or APIs may lead to integration failures
or degraded performance.
Scope of work for Managed Services:
 Monitoring and managing pipelines, repositories, and build/release processes.

 Basic user access management and security configuration with respect to azure DevOps.

 Providing recommendations for process improvements and Azure DevOps best practices.

Support Help Desk

 Incident management

 Ticketing system

 Generate email alerts for all major incidents in the cloud infrastructure.

Server Management

 CPU, Memory, Disk Management

 OS Management

 Traffic monitoring

Network & Security Management

 VNet and Security groups management

 Encryption and key management

 OS Hardening

 Security certificate management/configuration.

Reports

 Cloud native services shall provide the exact utilization of servers and shall generate utilization reports

Quarterly:

 Consolidated component-wise availability and resource utilization.

 All relevant reports required for calculation of SLAs.

 The MIS reports shall be in-line with the SLAs and the same shall be scrutinized by Inventive.

 Reactive ticket details

 Security Recommendations
Out of scope for Managed Services:
 Setup and configuration of new Azure DevOps environment.

 Actual development of software applications or features.

 Developing custom scripts or applications.

 Application testing, including quality assurance and testing activities.

 Monitoring application performance and availability.

 In-depth training for end-users on how to use Azure DevOps.

 Managing and integrating tools other than Azure DevOps.

Commercials:

Service type Estimated Duration Cost (INR)

One-time Implementation 5 days 1,40,000

Managed Service Monthly 15000

Note:
 In case implementation time exceeds then additional charges will be applicable.
 We have considered 5 business days excluding the weekends
 1. SLA Response Time

Redington will provide managed services support to customers to ensure their environment is available and operational.
These services augment the support services offered by Microsoft. This section describes the Service Level Agreement
related to Incidents and the Managed Services offered by Redington. The Redington Service Level Agreement design
considers SLAs offered by Microsoft Cloud across the respective service fronts.

Severity
Time for Response & Resolution Description
Type

Response Time: 15 min Total loss of service or specific functionality identified as

Priority 1
Resolution Time: 4 hours having critical impact on the business

Loss or potential loss of service or functionality with

critical impact on the business. This will result in
Response Time: 30 min significant loss of revenue, customer service,
Priority 2
Resolution Time: 8 -16 hours production, corporate reputation, or financial control
(including exposure to significant security risks or new
viruses).

Response Time: 60 min Loss or potential loss of service or functionality which

Priority 3
Resolution Time: 24 – 48 hours will degrade parts of the business operations.

Response Time: 24 hours

Priority 4 No business impact, Normal service requests/guidance
Resolution Time: 36 – 72 hours

Terms and conditions

 Payment terms will be as per the milestones mentioned

below. Assessment – 50 %

Implementation - 40 %

Testing and sign off –10 %

 All requirements for Implementation would be billed on actuals for the resources
identified (travel, accommodation).
 Invoices would be raised every month in the first week for which payment has to be made.
 All services will be rendered remotely from our Chennai office.
 The above cost is exclusive of applicable taxes.
 Any additional service/configuration consumed over and above the one estimated will be billed on pro-rata
basis as per the additional services. Our scope is limited to infrastructure.