Hey everybody! As you might have noticed an extra banned has showed up on this site from veeam. Since they have decided to sponsor this blog (thank you very much all! Would not have happened without all of you!) I’ll periodically share some news from them with all of you.
They are doing a big give away if you register on there site, one of them being a surface tablet, which you all know is brilliant!
Veeam is now featuring monthly prize drawings with some very exciting prizes.
Entering is easy—just one entry is all that’s required for a chance to win every month until August 2013.
Among the prizes, there are Microsoft Surface tablets, Apple iPads, and FREE passes to TechEd 2013 and VMworld 2013!
Find out more about Veeam’s big giveaway.
Welcome back to the fourth post in this series! Today we will have a look at what Microsoft recommends as a “private cloud design” and what I will make of it. Whilst my own solution is based of the reference architecture, it is quite different indeed!
An important thing to know is that, whilst I am using the private cloud as a reference, I am skipping most of the steps in designing a private cloud. If that is why you are here, please read the links at the end of the article and skim through my own content. A private cloud is much more process driven than just building a virtual infrastructure…
The architecture of it all…
So imagine for a minute that you have unlimited funds to build this lab of yours… You’d want redundancy on all levels and separation of each network where possible! Unfortunately we don’t have that luxury and, as you saw me hinting at in the previous article, our own design will be more limited but still quite capable!
From the networking perspective I will not have a fully redundant network, after all, this is but a lab environment! Thanks to Server 2012 I will be able to use bonding on my NIC’s and use LACP to improve the performance on that part.
As I mentioned in the previous article a Synology DS1218+ will be used for iSCSI provisioning. This device has 2 NICs on-board which can be bonded in to one 2 Gbps interface giving me a decent throughput and making the disks the most limiting factor in the storage design.
Domain controllers and extra infrastructure
Server 2012 completely supports running domain controllers virtualized and has no need to actually have a reachable DC when booting… That being said I need a remote access machine to power on the hosts (I have no need for them running 24/7) and a possible System Center VMM 2012 box (although server 2012 is not supported until SP1 :( ).
Undecided on if I am to install those boxes separately or as a virtual machine…
Which amounts to…
Something like this pretty picture!
Microsoft Private Cloud Solutions Repository (en-US)
Private Cloud Reference Model:
Exchange 2013 has been signed off and is now RTM! Hoozaaa!!
From the Exchange team blog:
Today we reached an important milestone in the development of the new Exchange.
Moments ago, the Exchange engineering team signed off on the Release to Manufacturing (RTM) build. This milestone means the coding and testing phase of the project is complete and we are now focused on releasing the new Exchange via multiple distribution channels to our business customers. General availability is planned for the first quarter of 2013.
We have a number of programs that provide business customers with early access so they can begin testing, piloting and adopting Exchange within their organizations:
- We will begin rolling out new capabilities to Office 365 Enterprise customers in our next service updates, starting in November through general availability.
- Volume Licensing customers with Software Assurance will be able to download Exchange Server 2013 through the Volume Licensing Service Center by mid-November. These products will be available on the Volume Licensing price list on December 1.