Upload
vuongkiet
View
228
Download
0
Embed Size (px)
Citation preview
Microsoft Azure Stack TP1 Single Server
POC Deployment #Azure
Dell Power Edge R710 Server for Microsoft AzureStack TP1 POC
@Jamesvandenberg
Hardware Requirements
These requirements apply to the Azure Stack POC only and might change for future releases.
Component Minimum Recommended
Compute: CPU Dual-Socket: 12 Physical Cores Dual-Socket: 16 Physical Cores
Compute: Memory 96 GB RAM 128 GB RAM
Compute: BIOS Hyper-V Enabled (with SLAT
support)
Hyper-V Enabled (with SLAT
support)
Network: NIC
Windows Server 2012 R2
Certification required for NIC; no
specialized features required
Windows Server 2012 R2
Certification required for NIC; no
specialized features required
Disk drives:
Operating System
1 OS disk with minimum of 200
GB available for system partition
(SSD or HDD)
1 OS disk with minimum of 200 GB
available for system partition (SSD
or HDD)
Disk drives: General
Azure Stack POC
Data
4 disks. Each disk provides a
minimum of 140 GB of capacity
(SSD or HDD).
4 disks. Each disk provides a
minimum of 250 GB of capacity.
HW logo
certification
Certified for Windows Server 2012
R2
Certified for Windows Server 2012
R2
Data disk drive configuration: All data drives must be of the same type (SAS or SATA) and
capacity. If SAS disk drives are used, the disk drives must be attached via a single path (no
MPIO, multi-path support is provided)
HBA configuration options: 1. (Preferred) Simple HBA 2. RAID HBA – Adapter must be
configured in “pass through” mode 3. RAID HBA – Disks should be configured as Single-Disk,
RAID-0
Supported bus and media type combinations
SATA HDD
SAS HDD
RAID HDD
RAID SSD (If the media type is unspecified/unknown*)
SATA SSD + SATA HDD
SAS SSD + SAS HDDExample HBAs: LSI 9207-8i, LSI-9300-8i, or LSI-9265-8i in
pass-through mode
Sample OEM configurations are available.
* RAID controllers without pass-through capability can’t recognize the media type. Such
controllers will mark both HDD and SSD as Unspecified. In that case, the SSD will be
used as persistent storage instead of caching devices. Therefore, you can deploy the
Microsoft Azure Stack POC on those SSDs.
Deploy Azure Stack POC
Before you deploy, prepare the Azure Stack POC machine and make sure it meets
the minimum requirements.
1. Install Windows Server 2016 Datacenter Edition Technical Preview 4 EN-US
(Full Edition).
2. Download the Azure Stack POC deployment package to a folder on your C
drive, (for example, c:\AzureStack).
Run the Microsoft Azure Stack POC.exe file.
This creates the \Microsoft Azure Stack POC\ folder containing the following items:
DeployAzureStack.ps1: Azure Stack POC installation PowerShell script
MicrosoftAzureStackPOC.vhdx: Azure Stack data package
SQLServer2014.vhdx: SQL Server VHD
WindowsServer2012R2DatacenterEval.vhd
WindowsServer2016Datacenter.vhdx: Windows Server 2016 Data Center VHD (includes
KB 3124262)
Important: You must have at least 128GB of free space on the physical boot volume.
Copy WindowsServer2016Datacenter.vhdx and call it
MicrosoftAzureStackPOCBoot.vhdx.
In File Explorer, right-click MicrosoftAzureStackPOCBoot.vhdx and click Mount.
Run the bcdboot command:
bcdboot <mounted drive letter>:\windows
Reboot the machine. It will automatically run Windows Setup as the VHD system
is prepared.
Configure the BIOS to use Local Time instead of UTC.
Verify that four drives for Azure Stack POC data:
Are visible in disk management
Are not in use
Show as Online, RAW
Verify that the host is not joined to a domain.
Log in using a local account with administrator permissions.
Verify network connectivity to Azure.com.
Important: Only one NIC is allowed during the deployment process. If you want to use a
specific NIC, you must disable all the others.
Run the PowerShell deployment script
1. Open PowerShell as an administrator.
2. In PowerShell, go to the Azure Stack folder location (\Microsoft Azure Stack POC\ if
you used the default).
3. Run the deploy command:
I’m running the script with Proxy settings.
Deployment starts and the Azure Stack POC domain name is hardcoded as azurestack.local.
1. At the Enter the password for the built-in administrator prompt, enter a password and
then confirm it. This is the password to all the virtual machines. Be sure to record this
Service Admin password.
2. At the Please login to your Azure account in the pop-up Azure authentication page,
hit any key to open the Microsoft Azure sign-in dialog box.
3. Enter the credentials for your Azure Active Directory Account. This user must be the
Global Admin in the directory tenant
4. Back in PowerShell, at the account selection confirmation prompt, enter y. This creates
two users and three applications for Azure stack in that directory tenant: an admin user
for Azure Stack, a tenant user for the TiP tests, and one application each for the Portal,
API, and Monitoring resource providers. In addition to this, the installer adds consents for
the Azure PowerShell, XPlat CLI, and Visual Studio to that Directory Tenant.
5. At the Microsoft Azure Stack POC is ready to deploy. Continue? prompt, enter y.
6. The deployment process will take a few hours, during which several automated system
reboots will occur. Signing in during deployment will automatically launch a PowerShell
window that will display deployment progress. The PowerShell window closes after
deployment completes.
7. On the Azure Stack POC machine, sign in as an AzureStack/administrator, open Server
Manager, and turn off IE Enhanced Security Configuration for both admins and users.
There are two ways to log in to the Azure Stack POC.
Log in as a service administrator
A service administrator manages resource providers, tenant offers, plans, services, quotas, and
pricing.
1. Log in to the Azure Stack POC physical machine.
2. Double-click the AzureStack.local.rdp desktop icon to open a Remote Desktop
Connection to the client virtual machine. This automatically uses the
AzureStack\AzureStackUser account that was created by the deployment script. Use the
admin password you gave in step 5 of the script process at the Enter the password for
the built-in administrator prompt.
3. On the ClientVM.AzureStack.local desktop, double-click Microsoft Azure Stack POC
Portal icon (https://portal.azurestack.local/).
4. Log in using the service administrator account.
Click on Accept
Log in as a tenant
Tenants provision, monitor, and manage services that they subscribe to, like Web Apps, storage,
and virtual machines. A service administrator can log in as a tenant to test the plans, offers, and
subscriptions that their tenants might use. If you don’t already have one, Create a tenant account
before you log in.
1. Log in to the Azure Stack physical machine.
2. Double-click the AzureStack.local.rdp desktop icon to open a Remote Desktop
Connection to the client virtual machine. This automatically uses the
AzureStack\AzureStackUser account that was created by the deployment script. Use the
admin password you gave in step 5 of the script process at the Enter the password for
the built-in administrator prompt.
3. On the ClientVM.AzureStack.local desktop, double-click Microsoft Azure Stack POC
Portal icon (https://portal.azurestack.local/).
4. Log in using a tenant account.
RDP may restrict how many users can access the physical Microsoft Azure POC host. To enable
multiple users, see Enable multiple concurrent user connections.
This is the Dell PowerEdge R710 Azure Stack Single POC Server
Now we have installed Microsoft Azure Stack on a Single Server in part 1 we are ready to
create Plans, Offers and
create a Virtual Machine on your own Azure Stack Cloud Services
First we Create a plan in Azure Stack
Sign in as a service administrator and create a plan that includes the compute, network, and
storage resource providers. This will give subscribers to the plan the ability to provision virtual
machines.
1. In an internet browser, navigate to https://portal.azurestack.local.
2. Sign into the Azure Stack Portal as a service administrator and enter your service
administrator credentials (this is the account created during step 5 of the Run the
PowerShell script section in part 1), and then click Sign in.
Service administrators can create offers and plans, and manage users.
3. To create a plan and offer that tenants can subscribe to, click New.
In the Create blade, click Tenant Offers and Plans, and then click Plan.
4. Fill in Display Name and Resource Name. The Display Name is the plan’s friendly
name. Only the admin can see the Resource Name. It’s the name that admins use to work
with the plan as an Azure Resource Manager resource.
5. Select or create a new Resource Group as a container for the plan. By default, all plans
and offers will go into a resource group called OffersAndPlans.
6. Click Offered Services, use the Shift key to multi-select all three providers (Compute
Provider, Storage Provider, and Network Provider) and then click Select.
7. Click Compute, and then click Needs Configuration.
8. In the Set Quotas blade, accept all the defaults, click OK, and then click OK
9. Do the Same with Microsoft Storage Not Configured and with Microsoft Network Not
Configured
10. Click on Create to make the Azure Stack Plan.
The New Plan “Serverbeheer” is made.
Now you have an Azure Stack Plan, you can Create an Offer for the Tenant so they can
get a Subscription.
In the following steps we Create an Offer in Microsoft Azure Stack:
11. Log in to the portal as a service administrator.
12. Click New.
13. Click Tenant Offers and Plans, then click Offer.
Fill in Display Name and Resource Name. The Display Name is the offer’s
friendly name. Only the admin can see the Resource Name. It’s the name that
admins use to work with the offer as an Azure Resource Manager resource.
Select a new or existing Resource Group.
Select your plan and Click on Create.
Click Change State, and then click Public. Plans and offers have to be made
public for tenants to get the full view when subscribing. If a plan is private and
the offer is public, tenants can get to the offer but won’t be able to see the
details of the plan. Plans and offers can be:
a. Public: Visible to tenants.
b. Private: Only visible to the service administrators. Useful while drafting the plan
or offer, or if the service administrator wants to approve every subscription.
c. Decommissioned: Closed to new subscribers. The service administrator can use
decommissioned to prevent future subscriptions, but leave current subscribers
untouched.
Here you can Change the Status to Public
Your Microsoft Azure Stack Plan and Offer are now Created.
Changes to the plan or offer are not immediately visible to the tenant. To see the changes, the
subscription state must be InSync, then the tenant must refresh the portal or login/logout.
Even after an additional subscription has been created and is InSync, you might have to
logout/login to see the new subscription in the “Subscription picker” when creating new
resources/resource groups.
Subscribe to your Azure Stack offer
First you need your Tenant Accounts from Microsoft Azure.
Create an Azure Stack Tenant Account Using the Azure Portal :
You must have an Azure subscription to use the Azure portal.
1. Log in to Azure.
2. In Microsoft Azure left navigation bar, click Active Directory.
3. In the directory list, click the directory that you want to use for Azure Stack, or create a
new one.
4. On this directory page, click Users.
5. Click Add user.
6. In the Add user wizard, in the Type of user list, choose New user in your organization.
7. In the User name box, type a name for the user.
8. In the @ box, choose the appropriate entry.
9. Click the next arrow.
10. In the User profile page of the wizard, type a First name, Last name, and Display
name.
11. In the Role list, choose User.
12. Click the next arrow.
13. On the Get temporary password page, click Create.
14. Copy the New password.
15. Log in to Microsoft Azure with the new account. Change the password when prompted.
16. Log in to https://portal.azurestack.local with the new account to see the tenant
portal.
1. In the Display Name field, type a name for your subscription.
2. Click Offer and verify that the offer you created is in the Choose an offer Click that
offer, click Select, and then click OK.
After you subscribe to an offer, wait until the subscription state is InSync. Then refresh the
portal to see which services are part of the new subscription.
Now we are able to provision a Virtual Machine :
Click on Compute
Click on Windows Server 2012 R2 Datacenter
Select your size VM
Create your Storage account.
Your Virtual Server will be ready in 10 minutes on Microsoft Azure Stack
IN YOUR OWN DATACENTER
Hope this Step by Step guide was helpful for you.
Best Reagrds,
James van den Berg
MVP SCCDM
Blog : https://mountainss.wordpress.com