Book Image

Building Clouds with Windows Azure Pack

By : Amit Malik
Book Image

Building Clouds with Windows Azure Pack

By: Amit Malik

Overview of this book

Windows Azure Pack is an on-premises cloud solution by Microsoft, which can be leveraged by Organizations and Services providers for building an enterprise class cloud solution. WAP provides consistent experience to Microsoft Azure, along with capabilities such as multi-tenancy, high density, self-service, automated. WAP can be leveraged to provide both IaaS & PaaS Offerings to internal and external customers. In this book, we will learn about planning and deployment of Cloud Fabric for Windows Azure Pack, Azure Pack components, VM Clouds and IaaS offerings, PaaS Offering including WebSites & Service Bus, DBaaS offerings, Automation with SMA, and extending capabilities with third party products integration and tenant experience for all services.
Table of Contents (18 chapters)
Building Clouds with Windows Azure Pack
Credits
About the Author
Acknowledgement
About the Reviewer
www.PacktPub.com
Preface
Index

Authoring DBaaS plans


Like all other Windows Azure Pack cloud services, DBaaS offerings are also assigned to tenants via Windows Azure Pack plans and add-ons. See Chapter 5, Assigning Cloud Services – Plans, Add-O s, Tenant Accounts, and Subscriptions, to learn more about the planning of plans and add-ons.

Creating plans for SQL and MySQL DBaaS

The following steps outline the requirement to create WAP plans for SQL and MySQL databases:

  1. Log into the WAP management portal and browse the new item workspace.

  2. Select Plans to start creating a plan.

  3. Enter a friendly name for the plan identification.

  4. Select SQL Servers, MySQL Servers, or both as applicable.

  5. The newly created plan will now be visible under plans workspace as not configured.

  6. Click on the plan name to start the configuration.

  7. Click on SQL and MySQL Servers to start adding groups to the plans. Enter the database server information including group, template, and other settings, such as edition display name of the tenants, maximum number of databases...