Introduction to Windows Azure IaaS
•Descargar como PPTX, PDF•
1 recomendación•538 vistas
Windows Azure now offers a new feature currently in customer preview called Virtual Machines & Virtual Networks. This new functionality provides Windows Azure with an IaaS platform for you to deploy your own virtual machines. In Windows Azure IaaS you can easily deploy and run Windows Server and Linux virtual machines in Windows Azure. This session explains the Virtual Machine storage architecture and demonstrates how to provision and customize virtual machine in Windows Azure and how to securely connect them to on-premises IT infrastructure with Windows Azure VPN’s.
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (12)
Similar a Introduction to Windows Azure IaaS
Similar a Introduction to Windows Azure IaaS (20)
Más de Alexander Feschenko
Introduction to Windows Azure IaaS
- 3. VM Role (PaaS) Virtual Machine (IaaS) Хранилище Непостоянное Постоянное, легко расширяемое VHD создается удаленно и загружается VHD можно создать как удаленно так и на Развертывание в хранилище портале Internal точки доступа открыты по умолчанию, контролируются файрволлом на операционных Сетевое Internal/Input точки доступа системах. взаимодействие настраиваются в конфигурации Input точки доступа контролируются через портал, конфигурацию или сторонними скриптами. Развертывание приложений, Приложения, которым необходимо постоянное Основной сценарий требующих длительной или ручной хранилище для успешного функционирования в применения установки условиях Windows Azure
- 13. Значение по Тип диска Поддерживается умолчанию Диск с ReadOnly and ReadWrite операционной ReadWrite системой None, ReadOnly and Диск с данными None ReadWrite
- 14. # Data VM Size CPU Cores Memory Bandwidth Disks Extra Small Shared 768 MB 5 (Mbps) 1 Small 1 1.75 GB 100 (Mbps) 2 Medium 2 3.5 GB 200 (Mbps) 4 Large 4 7 GB 400 (Mbps) 8 Extra Large 8 14 GB 800 (Mbps) 16
- 15. Образы и диски хранятся в Windows Azure Blob Storage Данные реплицируются в 3-х местах Все существующие клиенты работают Windows Azure Storage
- 18. No SLA SLA 99.95%
- 31. ContosoVNet (10.0.0.0/8) Cloud Service1 FrontEndSubnet (10.0.0.0/16) 80 Load IIS Virtual Machines Balancer Direct Access via VNET Cloud Service 2 SQLSubnet (10.1.0.0/16) SQL Mirror
- 32. 10.1.2.0/24 10.1.3.0/24 10.2.2.0/24 10.2.3.0/24
- 33. Виртуальная сеть Windows Azure Отзывы и поддержка vnetfeedback@microsoft.com http://social.msdn.microsoft.com/Forums/en- US/WAVirtualMachinesVirtualNetwork Windows Azure поддерживает
Notas del editor
- Welcome and speaker’s introductionSet expectations that the session is going to be about identity and access control for applications targeting the Windows Azure platform, as opposed to the services themselves (SQL Azure, Windows Azure management calls, etc.)
- Most of the things I mentioned apply to SOAP web services as well. The WIF wizard works in the same way, ACS can handle the appropriate protocols, and so on. There are some obvious differences, both in expressive power (services can give higher guarantees thanks to the use of more advanced cryptography) and requirements (redirects are not necessary, but the requirements on the client capabilities are more stringent).It is noteworthy that at the moment Silverlight does not have the full capabilities you’d find in WCF based clients on desktop and backend applications, however most of the scenarios can be addressed in the same way with some custom code (see the Silverlight exercises in the identity developer training kit).The REST scenario is not supported out of the box for WIF. The REST protocols are so simple that you can handle those yourself,. However if you want to leverage the handily claims model and config-based authentication mechanisms there are custom extensions to WIF you can leverage.There are various mobile (and not only) scenarios in which you want to call a service, but the identity you want to authenticate is available only via redirect (i.e. browser based) protocols. There’s still work to be done there, but for early thinking about how to tackle the scenario you can refer to the windows phone 7 sample on acs.codeplex.com
- Most of the things I mentioned apply to SOAP web services as well. The WIF wizard works in the same way, ACS can handle the appropriate protocols, and so on. There are some obvious differences, both in expressive power (services can give higher guarantees thanks to the use of more advanced cryptography) and requirements (redirects are not necessary, but the requirements on the client capabilities are more stringent).It is noteworthy that at the moment Silverlight does not have the full capabilities you’d find in WCF based clients on desktop and backend applications, however most of the scenarios can be addressed in the same way with some custom code (see the Silverlight exercises in the identity developer training kit).The REST scenario is not supported out of the box for WIF. The REST protocols are so simple that you can handle those yourself,. However if you want to leverage the handily claims model and config-based authentication mechanisms there are custom extensions to WIF you can leverage.There are various mobile (and not only) scenarios in which you want to call a service, but the identity you want to authenticate is available only via redirect (i.e. browser based) protocols. There’s still work to be done there, but for early thinking about how to tackle the scenario you can refer to the windows phone 7 sample on acs.codeplex.com
- Most of the things I mentioned apply to SOAP web services as well. The WIF wizard works in the same way, ACS can handle the appropriate protocols, and so on. There are some obvious differences, both in expressive power (services can give higher guarantees thanks to the use of more advanced cryptography) and requirements (redirects are not necessary, but the requirements on the client capabilities are more stringent).It is noteworthy that at the moment Silverlight does not have the full capabilities you’d find in WCF based clients on desktop and backend applications, however most of the scenarios can be addressed in the same way with some custom code (see the Silverlight exercises in the identity developer training kit).The REST scenario is not supported out of the box for WIF. The REST protocols are so simple that you can handle those yourself,. However if you want to leverage the handily claims model and config-based authentication mechanisms there are custom extensions to WIF you can leverage.There are various mobile (and not only) scenarios in which you want to call a service, but the identity you want to authenticate is available only via redirect (i.e. browser based) protocols. There’s still work to be done there, but for early thinking about how to tackle the scenario you can refer to the windows phone 7 sample on acs.codeplex.com
- Most of the things I mentioned apply to SOAP web services as well. The WIF wizard works in the same way, ACS can handle the appropriate protocols, and so on. There are some obvious differences, both in expressive power (services can give higher guarantees thanks to the use of more advanced cryptography) and requirements (redirects are not necessary, but the requirements on the client capabilities are more stringent).It is noteworthy that at the moment Silverlight does not have the full capabilities you’d find in WCF based clients on desktop and backend applications, however most of the scenarios can be addressed in the same way with some custom code (see the Silverlight exercises in the identity developer training kit).The REST scenario is not supported out of the box for WIF. The REST protocols are so simple that you can handle those yourself,. However if you want to leverage the handily claims model and config-based authentication mechanisms there are custom extensions to WIF you can leverage.There are various mobile (and not only) scenarios in which you want to call a service, but the identity you want to authenticate is available only via redirect (i.e. browser based) protocols. There’s still work to be done there, but for early thinking about how to tackle the scenario you can refer to the windows phone 7 sample on acs.codeplex.com
- Most of the things I mentioned apply to SOAP web services as well. The WIF wizard works in the same way, ACS can handle the appropriate protocols, and so on. There are some obvious differences, both in expressive power (services can give higher guarantees thanks to the use of more advanced cryptography) and requirements (redirects are not necessary, but the requirements on the client capabilities are more stringent).It is noteworthy that at the moment Silverlight does not have the full capabilities you’d find in WCF based clients on desktop and backend applications, however most of the scenarios can be addressed in the same way with some custom code (see the Silverlight exercises in the identity developer training kit).The REST scenario is not supported out of the box for WIF. The REST protocols are so simple that you can handle those yourself,. However if you want to leverage the handily claims model and config-based authentication mechanisms there are custom extensions to WIF you can leverage.There are various mobile (and not only) scenarios in which you want to call a service, but the identity you want to authenticate is available only via redirect (i.e. browser based) protocols. There’s still work to be done there, but for early thinking about how to tackle the scenario you can refer to the windows phone 7 sample on acs.codeplex.com
- Let’s think for a moment about claims based identity in itself and at the tools we can use to implement it; we will re-introduce cloud-specific considerations later
- Let’s think for a moment about claims based identity in itself and at the tools we can use to implement it; we will re-introduce cloud-specific considerations later
- Let’s think for a moment about claims based identity in itself and at the tools we can use to implement it; we will re-introduce cloud-specific considerations later
- Let’s think for a moment about claims based identity in itself and at the tools we can use to implement it; we will re-introduce cloud-specific considerations later
- Let’s think for a moment about claims based identity in itself and at the tools we can use to implement it; we will re-introduce cloud-specific considerations later