Resultados 1 a 5 de 5
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    Azure in your datacenter (on-premises) - Hardware requirements

    Hardware requirements for Azure Stack Technical Preview (POC)

    Note that these requirements only apply to the upcoming POC release, they may change for future releases.
    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
    Storage considerations
    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*)
    • SAS SSD + SAS HDD**

    * 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.
    ** For tiered storage, you must have at least 3 HDDs.
    Example HBAs: LSI 9207-8i, LSI-9300-8i, or LSI-9265-8i in pass-through mode

    While the above configuration is generic enough that many servers should fit the description, we recommend a couple of SKUs: Dell R630 and the HPE DL 360 Gen 9. Both these SKUs have been in-market for some time.
    Última edição por 5ms; 21-12-2015 às 19:26.

  2. #2
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    Azure Stack

    by Yevgeniy Sverdlik on December 21, 2015

    Hoping to exploit the edge over VMware in the enterprise data center it has due to the massive scale of its public cloud, Microsoft is preparing to launch the first preview release of Azure Stack – a private Azure cloud environment a company can stand up in its own data center that will look exactly like the public version of Azure to users and be seamlessly integrated with the public cloud.

    This is a similar angle on hybrid cloud VMware has been pursuing since 2013, when it announced its vCloud Hybrid Service that was later rebranded into vCloud Air. VMware promised a virtual extension of a customer’s on-premises VMware environment into the cloud.

    The public cloud portion of VMware’s hybrid cloud is hosted in fewer data centers than Azure, relying on smaller footprint in colocation facilities, while Microsoft spends billions of dollars on massive data centers around the world, in some cases building on its own and in other cases leasing large facilities wholesale.

    While it is working with hardware vendors to bring to market pre-integrated hardware-software packages for quick setup of private Azure clouds, Microsoft has released hardware specs for those who want to try the preview version of the Azure Stack software it expects to launch next quarter.
    Última edição por 5ms; 21-12-2015 às 19:28.

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    “The Microsoft Azure Stack gives application owners the ability to ‘write once, deploy anywhere,’ whether it be to your private cloud, a service provider’s cloud, or the public Azure cloud,” reads a post to Microsoft’s server and cloud blog. “Developers will have the broadest access to application development platforms across Windows and Linux to build, deploy and operate cloud applications using consistent tools, processes and artifacts. One Azure ecosystem across public, private and hosted clouds will allow you to participate in a unified, robust partner network for Azure clouds.”

  4. #4
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    2009 - Enterprises will self-host Windows Azure someday

    By Eric Lai
    Mar 6, 2009

    "The corporate data center at some point in time will look like a mini-cloud, partitioned by application workload," said Steven Martin, senior director for developer platform product management at Microsoft, in an interview.

    First previewed last fall, Windows Azure is Microsoft's foray into bringing Windows Server online as a cloud computing platform. Developers will be able to port or write applications using Microsoft's popular .Net tools and Web standard interfaces such as REST, SOAP and Atom, and host them on Azure.

    Azure is expected to be released later this year (2009).

    Conventional hosting entails companies buying or leasing a server from a datacenter operator and running a set number of applications off it. That can be complicated to manage, entail a lot of upfront cost, and be difficult to scale quickly on demand.

    Windows Azure enables faster setup and easier scaling, and lets users pay for usage, and helps ISVs avoids big upfront investments.

    Azure runs on Windows Server 2008 inside Microsoft's data centers. The fact that Microsoft offers both Windows Server software and the Azure service as part of its "software+services" strategy, is a plus for companies unsure about committing completely to a cloud infrastructure, Martin said, whether because they think they can run it cheaper or with more agility, or because regulations require them to do so.

    "We make it really easy for you to transition back to on-premises without having to completely rewrite your app. You control your own destiny," Martin said.

    Besides corporations, Web hosting companies may be interested in hosting Azure to make their infrastructure more nimble and efficient.
    Última edição por 5ms; 22-12-2015 às 07:12.

  5. #5
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    Azure in a can

    6 Jan 2016 at 13:32, Trevor Pott

    HPE and Microsoft have teamed up to give everyone else a right good kicking. The product of the now is the "HPE Hyper Converged 250 for Microsoft CPS Standard”. This is a very long name and so I propose instead that we shall think of it as "Azure in a can 250". Sticking to the Azure-in-a-can theme, HPE's new gizmo does exactly what it says on the tin, and it changes everything.

    The Azure in a can 250 is a 2U chassis containing 4 nodes lashed together into a hyper-converged cluster using HP's StoreVirtual software. Each node comes with 2 Xeon E5-2640 or 2680 CPUs, 128GB, 256GB or 512GB of RAM and 2 SFP+ 10GbE NICs.

    The cluster can be configured in a 4 node or a 3 node configuration. The hybrid storage configuration offers 4 x 1.2 TB SAS and 2 x 480 GB SFF SSDs for ~ 7.5 TB usable storage in the 4-node configuration and ~ 5.6 TB HA usable storage for a 3-node configuration.

    Unlike most of its hyperconverged competitors, HPE has actually listened to the SMB and mid-market customers that the Azure in a can 250 is aimed at and provided a capacity configuration as well. The capacity configuration offers 6 x 1.2 TB SAS disks for ~ 11.5 TB usable storage for 4-node systems and ~ 8.5 TB HA usable storage for a 3-node configuration.

    This is a bigger deal than any hyperconverged vendor (other than Scale Computing) has thus far been willing to admit. Obsessed with performance numbers, hyperconverged vendors have built faster and faster systems that end up priced out of reach for the mass market and ultimately are ridiculous overkill for the vast majority of workloads.

    One need only look at Scale Computing to understand how out of touch most hyperconverged vendors really are. Scale is a small startup offering a feature-limited KVM-based hyperconverged solution that doesn't even use flash drives at all. Despite this, the company has managed to win thousands of customers very quickly and build a cult-like following in the process.

    So along comes HPE, with a hyperconverged solution where the mid-market can afford the floor cost. But isn't just a hyperconverged cluster with some monitoring: it’s a proper hybrid cloud and it can scale out impressively.

    Azure made easy

    The Azure in a Can 250s come with all you need to take over the cloudy world: Windows Server 2012 R2, HPE OneView for Microsoft System Center (also known as "that thing that makes System Center almost usable"), and the Windows Azure Pack. This means that out of the box, the system is ready to deploy anything you see in the Azure marketplace. Windows VMs, Linux VMs, you name it.

    The point of this offering, however, is to enable organisations to embrace hybrid cloud computing. Yes, it's great that you can run workloads from the Azure marketplace in your own data centre, but the real value-add is supposed to be that those exact same workloads can be set up to run on Microsoft's public cloud as well. Run it in your data centre, run it in Microsoft's data centre, it's all the same code.

    The other part of this partnership sees HPE working with Microsoft to package up more applications into virtual appliance form and make them available through the Azure Marketplace. HPE is also committed to certifying an additional 5,000 staff as Azure Cloud Architects so that its services arm is ready to support this new play.

    Backup and DR are provided by Azure Backup and Azure Site Recovery. You can sign up for the services online and going through some fairly painless setup processes. Other options, such as Zerto, have been certified and Microsoft and HPE look like they're gearing up to aggressively grow the ecosystem around this partnership.

    All of this is quite positive. HPE and Microsoft had produced something that, while not quite an Infrastructure Endgame Machine (IEM), is a giant leap towards one.

    Towards a right good kicking

    The entry cost for these units is somewhere around $80k. Consider this for a moment: for under $100k you can get a 4 node hyperconverged cluster that you unbox, put on the rack, plug in and go. Not just any hyperconverged cluster, but Azure in a can.

    HPE has stolen a march on the competition. Very few major hyperconverged vendors are offering a full hybrid cloud solution out of the box. If you futz with the VMware-based ones (EVO:RAIL, Nutanix, SimpliVity, Maxta, etc.) for long enough then you can make your own hybrid cloud hyperconverged system. It is a fair amount of work to do so, requires rather a lot of expertise and – most critically – is spectacularly more expensive than what HPE is offering.

    If you're willing to go for more obscure vendors – Yottabyte or Zerostack, as two examples – you can get very similar functionality to what HPE is offering for a lower cost. What you don't get is the fully populated Azure Marketplace. That makes a big difference.

    Individually, none of the components are particularly difficult or even all that innovative. Any decent Microsoft sysadmin with enough time on their hands could buy some HP servers, install the relevant software and roll their own Azure in a Can 250. The 250 line is used for any number of converged offerings from HPE.

    The whole, however, is much more than the sum of its parts. It's a fully self-serve hybrid cloud with working (and almost easy to use) full automation and orchestration capabilities, a jam-packed marketplace and a set of mostly usable management interfaces that's ready to go as soon as you plug it in. That's pretty bloody nifty right there.

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens