Eu vou palestrar no Teched Australia 2011

Oi pessoal

Gostaria de compartilhar com voces que estarei palestrando em duas sessoes no Teched Australia 2011. Para quem esta aqui na Australia, conto a presenca la.

SCVMM 2012: Deployment, Planning, Upgrade

This session provides a scenario rich detailed walk through of VMM 2012 deployment, planning, and upgrade scenarios. Come and learn how to best plan your next

VMM rollout SCVMM 2012 Fabric Lifecycle:
Networking and Storage This session provides a scenario rich detailed walk through of new and more robust networking and storage features in VMM 2012. In this session you will learn how to discover, configure, and provision networking and storage fabric for use with the private cloud

O Tech.Ed Australia 2011 vai ser em  Gold Coast, Australia, de 30 de Agosto a 2 de Setembro. Mais informacoes http://australia.msteched.com/

 

Dynamic Data Center: Toolkit to create a private or public cloud based on Microsoft’s Hyper-V and System Center

 

To make it easier for hosting providers to create Dynamic Data Centers, Microsoft is providing a set of documents and code samples that will serve as guidelines and best practices.

The set of documents provided is as follows:

• Bare-metal provisioning of Windows Server 2008 to host virtual environments
• Provisioning a virtual environment (using Hyper-V). This document outlines:
  • Configurations to deploy a virtual infrastructure based on Windows Server 2008 Hyper-V.
  • Configuring the Active Directory® service to make it easier to create a multi-tenant environment.
  • Securing the environment.
  • Managing the virtual environment using System Center Virtual Machine Manager.
  • Best practices to configure and use Virtual Machine Manager.
  • Capacity planning.
• Installing and configuring System Center to manage your virtual environment
• Leveraging System Center Data Protection Manager to back up/restore the virtual environments in a delegated administration model
• Configure System Center Configuration Manager to:
  • Perform updates on demand.
  • Track inventory.
  • Push out standard configurations and software.
• Configure System Center Operations Manager to monitor and alert individual end customers based on policies

In addition to these documents, Microsoft released a Silverlight™-based test portal for ContosoHosting.com. This portal includes a control panel that enables end customers to:

• Provision and manage Hyper-V–based clients.
• Perform file/folder-level backups and restores.
• Monitor important counters and receive alerts.
• Install updates during a configurable time window.
• Monitor events.

Along with the sample application, there is a source code for Windows® Communication Foundation (WCF) services and Windows Powershell™ scripts to perform all operations to provision and manage the System Center Server Management Suite Enterprise and Windows Server 2008

For more info : http://archive.msdn.microsoft.com/ddc

 

 

Hyper-V R2 cluster: Maximo numero de VM’s por nó

Planeje recursos o suficiente para permitir que um pelo menos 1(um) nó seja reservado para failover, o que significa que ele permanecerá ocioso até que outro nó receba o failover para ele. (nó passivo)

Minha recomendacao : reserve 2 nós como passivos. Não há uma taxa ou um multiplicador de nós reservados recomendados para nós ativos. A única exigência específica é que o número total de nós em um cluster não pode exceder o máximo de 16.

Vários fatores podem afetar o número real de máquinas virtuais que podem ser executadas ao mesmo tempo em um nó, como:

• Uma quantidade de memória física sendo usada por cada máquina virtual.
• Largura de banda de armazenamento e rede.
• Número de eixos de disco, o que afeta o desempenho de E/S do disco

Note que a alta desidade de VM’ em um cluster Hyper-V R2 requer uma capacidade alta de IO capability no Storage. Este sim pode ser o fator limitante.

Numero de Nós no Cluster	Media de VM’s por nó	Max # VMs no Cluster
2 Nodes (1 active + 1 failover)	384	384
3 Nodes (2 active + 1 failover)	384	768
4 Nodes (3 active + 1 failover)	333	1000
5 Nodes (4 active + 1 failover)	250	1000
6 Nodes (5 active + 1 failover)	200	1000
7 Nodes (6 active + 1 failover)	166	1000
8 Nodes (7 active + 1 failover)	142	1000
9 Nodes (8 active + 1 failover)	125	1000
10 Nodes (9 active + 1 failover)	111	1000
11 Nodes (10 active + 1 failover)	100	1000
12 Nodes (11 active + 1 failover)	90	1000
13 Nodes (12 active + 1 failover)	83	1000
14 Nodes (13 active + 1 failover)	76	1000
15 Nodes (14 active + 1 failover)	71	1000
16 Nodes (15 active + 1 failover)	66	1000

Embora a