Testing and Deployment: Quality Is King - Deploying and Managing a Cloud Infrastructure - page 300

FIGURE 10.4 Network bottlenecks identified and removed

Organizational and
FTP/SFTP
LAN

ISP

Cloud service

Office LAN

ISP

Dedicated FTP/SFTP
LAN

Step 3: Document deployment concerns. Not all concerns can be resolved during the
architecting and design stage. Concerns still outstanding should be put down as part of the
deployment documentation. There are usually three types of concerns: security, manage-
ment, and standards.
Security concerns include legal issues with the retention and location of data, regulatory
compliance and data governance (integrity and classification), and data auditing.
Infrastructure management concerns usually include virtual machine management,
VLANs, VM migration, application compatibility for cloud-to-cloud migration, and
VM multitenancy.
Concerns related to standards include open vs. proprietary cloud service provider APIs and
technology, which again points to compatibility and migration. This also suggests risks in
terms of vendor lock-in, and organizations have to make a decision whether compromising
openness and compatibility is a small giveaway.
Step 4: Design the deployment scheme. During the design of the deployment scheme,
several things need to be considered. The most important issue to be considered is the level
of control and access that an organization wishes to maintain over its cloud deployment.
The level of administration—i.e., infrastructure level, platform level, or both—is also an
important issue.