Teams need to move fast, every action which results in wait time must be minimized to zero. Teams need to move flexible, context changes must be easy adoptable by the team and the system they realize. Using Azure for their Environment and ALM needs helps them fulfill this need.
2. |
€19,34
per month
Calculation example
Laptop costs about €85,00 per month
220
Hour per
month
Development
machine
active
40%150 GB
data storage
1 Gb
data traffic
Large VM
4 x 1,6 GHz CPU
7 GB RAM
€7,83
per month
€59,18
per month
Setup
Costs
0 hour
8 hour
Azure for Team | Maart 2014 6
3. |
More business value
with fast and flexible
teams.
Azure usages scenario’s for software development teams.
3Azure for Team | Maart 2014
6. |
Cloud Value for teams
LOWER COST LESS RISK FASTER VALUE
Self
provisioning
test and
development
infrastructure
Minimize
your
upfront
investment
and work
pay for
what you
use, free
DC
capacity
Azure for Team | Maart 2014 5
7. |
Cloud fundamentals
Private Community Public
Deployment
Models
Infrastructure
as a
Service
Platform
as a
Service
Software
as a
Service
Service
Models
Anywhere
Access
Rapid
Elasticity
Metered
Services
Self-Service
On-demand
Resource Pooling
Cloud
Principles
Azure for Team | Maart 2014 7
8. |
BACKLOG
RELEASE
Team activities in the Cloud
8Azure for Team | Maart 2014
Plan
Develop
Operate
Team member Env.
Build and Test Infra
Agile Planning
Monitor
Test and
Production Env.
ALM Tools
10. |
Team environments.
Environments used by team members to
plan, prepare, specify and execute development work.
agile in onboarding team members with pre-installed
and configured environments.
Azure for Team | Maart 2014
19. |
Benefits.
From a single core to
eight cores, from less
than 1 Gb to 56 Gb
in less than 5 minutes
Flexible power
Different development
environments for
different project types.
Multiple
environments
Create golden images
and standardize the
developer desktop for
outsourced work.
Standardize
work
Use the same IDE and
code from anywhere
on any device
Access from
anywhere
Reuse environments by
other team members
and teams.
Share
environments
Setup complex multi-
server environments
for development.
Complex
environments
24. |
Virtual Network
24Azure for Team | Maart 2014
Extending your infrastructure
Side to Side:
• On-premises datacenter
Point-to-Side:
• Individual computers behind
corporate firewall.
• Remote workers
25. |
Considerations ...
Network setup
Azure VMs have a warm-up time
Remote Desktop Connection is used
25Azure for Team | Maart 2014
26. |
Tips Azure VM’s…
26Azure for Team | Maart 2014
VM‘s are Server OS‘s configure to Workstation.
Different size VMs have different data transfer speeds –
use large or x-large VMs for Dev VMs
Always create an Affinity Group to locate both storage
and VM together in the same data center
Automate, Use PowerShell for Creation, Start and Stop
scheduling.
Use your MSDN benefit
27. |
Tips Collaboration …
27Azure for Team | Maart 2014
Use OneDrive or Windows Azure Blob Storage to save files
in the Cloud
Use OneNote for content sharing
Visual Studio Online to store your Source Code and Agile
planning in the Cloud
28. |
BACKLOG
RELEASE
Development and Test Environments
28Azure for Team | Maart 2014
Plan
Develop
Operate
Team member Workspace.
Build and Test Infra
Agile Planning
Monitor
Test and
Production Env.
ALM Tools
30. |
Development and Test Environments
Environments where systems run on.
Development, Test, Acceptance, …
Flexible and fast enabling of clean environments for ...
Azure for Team | Maart 2014
31. | 31Azure for Team | Maart 2014
Virtualized Test Infrastructure
A default
infrastructure for
validation of a
complete system
architecture
Host A
All
Application
Server Roles
Host A
All
Application
Server Roles
Web Server Web Server
High availability — For environments above 1,000 users, two
servers utilizing SQL Server clustering, mirroring, or AlwaysOn
is recommended. AlwaysOn requires SQL Server 2012.
All SharePoint Databases
34. |
Project Subscription
Per project.
- Base Images repository for environments.
- Scripts for creating environments
Development
Test
Acceptance
Production
Base images
43. |
EA Subscription
Project
43
A subscription per environment.
- cost separation
- security separation
Development
Subscription
Test
Subscription
Acceptance
Subscription
Production
Subscription
Azure for Team | Maart 2014
44. |
Separate Repository subscription
- Well maintained, managed
- Versioned
Golden image
repository
PowerShell scripts
repository
Repository subscription
Azure for Team | Maart 2014
46. |
Tips...
Subscription Administration.
Environment Creation Validation tests
Manual (Remote Desktop)
Automated (PowerShell)
Stop environments
Measure
Infrastructure as code
Versioning PowerShell Scripts
Use a branching structure
46Azure for Team | Maart 2014
47. |
Infrastructure as Code
47Azure for Team | Maart 2014
Windows
PowerShell
Desired State
Configuration
Configuration IISWebsite
{
Node Server1, Server2
{
WindowsFeature IIS
{
Ensure = “Present”
Name = “Web-Server”
}
WindowsFeature ASP
{
Ensure = “Present”
Name = “Web-Asp-Net45”
}
}
}
51. | 51Azure for Team | Maart 2014
Build Infrastructure
Build
agents, controller
.
52. | 52Azure for Team | Maart 2014
Requirements, Bug and Test case
management
Central store for
project artifacts.
53. | 53Azure for Team | Maart 2014
Load Test Rig
Load
agents, controller
and monitoring
server.
54. |
ALM Infra Hosted on IaaS
Customized Processes
• Different Workflow
• Special reporting
Specialized Builds
• SDK’s
• Multiple builds
Custom environments
- Hybrid deployment
environment scenarios
- Multi platform testing
Azure for Team | Maart 2014
55. |
SaaS PaaS IaaS On Premise
Cloud first Strategy
Azure for Team | Maart 2014 55
63. |
Project Subscription
Per project.
- Base Images repository for environments.
- Scripts for creating environments
- Visual Studio License
Development
Test
Acceptance
Production
Base images