I'm a research student and I want to build a windows cluster at home with my laptops to test my parallel codes.
The problem is I'm using Windows 7 Home Premium, not a server edition.
I'm using Visual Studio 2010 Ultimate and I installed Microsoft HPC Packs with SP1 and able to simulate MPI codes at my localhost without a problem. Now I want to see the real application.
I have 3 other laptops at home and windows 7 starter is installed on them. They don't have visual studio installed because I have only 1 license from the university.
So is there any way to build a windows cluster with these configurations??
No, a Windows cluster will only work with Windows Server Enterprise or above.
To simulate this a good way is to host Windows Server operating systems on virtual machines. A good resource for this is here.
You do need Windows Server licenses to do this, however -- if you have an MSDN subscription you may find that you can get development licenses under that.
I've done it in HyperV a number of times. You'll need to create a domain controller (using Server STD or Enterprise) as well as N nodes that run Server HPC edition (a lightweight/simplified server edition). Easiest thing to setup would be to create a single HPC (VM) that contains your DC, DNS, DHCP, and HPC Head Node/WCF Broker. Then, you can add a few compute nodes (also VMs) (2 or 3 is good enough for testing) using the HPC server edition and be all set.
Related
The Background
Today I was reflecting on the pain install/OS testing. As we approach a new release of our windows software, we have to verify:
That it installs without issue
That it runs, given a reasonable fulfillment of dependencies
That our assumptions as to what is available on an "updated" machine are correct
On a range of architectures (32/64 bit, etc)
On a range of operating system versions (Windows XP, Windows Vista, 7, 8, etc.)
Our sad (but usual and cost effective) approach is to spin up some old boxes here on site. We either try to stuff an OS install into a VM system, or are forced to wipe the box and do a native install just to get to a "clean" install of the app. Depending on the functional approach, reverting snapshots may or may not be available.
The Idea
I realized that Windows Azure was making it very easy to spin up virtual machines these days and "pay for what you use". Mostly this appears to be focused on web hosting (Windows Server 2008 and Windows Server 8 are the only windows variants available in the "VM OS Selection" dialog). See this page for an overview.
But what if I could spin up other kinds of Windows OS images purely for testing?
I have an MSDN subscription, and access to a set of OSes that we should support. Couldn't I push these up somehow and have snapshottable, on-demand test hosts?
The Questions
Is this feasible right now with Windows Azure? (I can do this for Server 2008 and Server 8 now, it would seem...can i do this with other OS images?)
If so, how? (Can i upload a .vhd to storage in some manner as to have it show in the "my images" section?)
If not, is there a good alternative? (I get the sense you could do this with Amazon EC2? Am I barking up the wrong tree? Is this better to try and do onsite with VM software entirely?)
In the best case, I want "fresh" (recently patched) images for a set of supported Windows OSes that I can spin up on demand, pay for what I use, and then shut down again. Does this exist?
Thanks for your time and consideration...
P.S. Not entirely sure if this should be here or on serverfault...please advise.
1.Is this feasible right now with Windows Azure? (I can do this for Server 2008 and Server 8 now, it would seem...can i do this with other
OS images?)
The Windows Server is 2012, not 8. But anyway. So no. The currently supported Windows family OS'es are:
* Windows Server 2008 SP2 x64,
* Windows Server 2008 R2,
* Windows Server 2012
Note that all of them are just the 64bit versions! Frankly, I don't think Windows client OS'es will ever be supported (like XP, 7, 8)
2.If so, how? (Can i upload a .vhd to storage in some manner as to have it show in the "my images" section?)
No. so no way.
3.If not, is there a good alternative? (I get the sense you could do this with Amazon EC2? Am I barking up the wrong tree? Is this better
to try and do onsite with VM software entirely?)
Can't answer this question completely, but a quick search says that currently in Amazon EC2 you can run:
Amazon EC2 running Microsoft Windows Server® (available in 2003 R2,
2008 or 2008 R2 editions)
So far with Windows OSes.
In summary: Only Server Windows OS can be run in an Azure and Amazon.
A hint: you can't install Hyper-V on Windows server in either Azure nor Amazon (you can't virtualize what is already virtualized).
I am trying to find a solution for installing Visual Studio 2010 (VMWARE) and connecting to it remotely so that both i can use the pc and the receiver can monitor what i am doing.
There seems to be so many different solutions for VMWARE and i am little of which will work.
It would be ideal if it was free of charge, i notice the "VMWARE PLAYER" is - but i think is only to run virtual machines???
If anybody has had any success of running VMWARE with visual studio 2010 i would look to hear your comments or any advice
Thanks
EDIT
TO clarify, i am looking to run visual studio 2010 in VM.
In order to run VS2010 in VM you will need:
VMWare Server 2.0
Licenced operating system
VS2010
Follow those steps:
Install VMWare server on the physical host
Create a new virtual machine
Install operating system on your virtual machine
Install VS2010 + any other software you need for development
Connect your VM to internet so it can be connected to from internet (open necessary firewall ports)
On a side note: why do you want the receiver to have access to your development environment in the first place? Won't it suffice to give him access to your deliverables only? If you are developing a web site - publish it and give him access. For desktop apps give him the link to a site where you can dump your nightly builds...
I agree with Jakub, but you could also use ESXi on a system do the same thing and have for a few trade shows I would do the following
1) VMware ESXi, use 4.01 located at VMware vSPhere Hypervisor ESXi
2) Use Microsoft Windows 2008, you can be granted a 60 day license for testing.
3) Install Microsoft VS2010 (in my case it was Microsoft VS2008, its all our group uses.
The only issues I have found are when installing Visual Studio 2008, the OS detection might cause a few issues. VS2010 should be able to correctly detect the OS you are using.
The other testing bed the developers I support use are based around the same thing, but use Xen for the hypervisor. We have found on long haul networks using tunnels, VMware ESXi's remote console sessions can be crazy and produced odd graphical draws and even latency.
Good luck with Visual Studio 2010. And I hope your teams work out.
I recently switched to a MacBook Pro for my development machine (for many reasons). I want to setup a Virtual Machine for ASP.NET, IIS, and Visual Studio 2010 development. I also have need to do some development work with SharePoint 2010.
What I am wondering is if I should use Windows 7 (64 bit) or Windows Server 2008 (64 bit) as the OS for my development virtual machine. I don't really need most of the services running in Server 2008 so I felt that Windows 7 would probably run faster in the VM environment however I am fairly new to SharePoint 2010 so I am not sure if Windows 7 (64 bit) can be used as a development environment for it.
Thanks for any input.
much easier is to install SharePoint 2010 on Win Server than on Windows 7 - on Windows 7 you need to install SharePoint manually (extract installation files, install prerequisites, install additional patches etc). Here is a link how to do it: http://bit.ly/aDCzvS
Services will not make a difference. Look at all the stuff you need for Sharepoint - this is not a low capacity environment. So, 00mb will not make a difference. Between SQL Server, Sharepoint server and Visual Studio I would say you ASK for about 6-8gb anyway ;)
I do not think it makes a difference now. Sharepoint 2010 was explicitly optimized for being installable on Win 7 - and this is a fully supported development model (contrary to 2007 where you basically were at the end of a bad line as developer). Win 7 should be good. That said, you can tune Windows server to be as good as Win 7 UI wise (for development work and playing music in the background).
I would go with Windows 7 for the time being - and possibly install Sharepoint on a separate Win 2008 when needed. THe main problem here is that Sharepoint is heavy in mem useage, and I woud hate carrying it around all the other time.
A MacBook Pro may be a bad choice for that - make sure you have at least 8gb memory for real sharepoint development work.
I work with people that use SharePoint in a VM on a Mac and their life is much harder. Among other things copying and pasting code between the guest and host machine doesn't work, and they're forced to dedicate one monitor to the VM. You should really consider Boot Camp and Windows 7.
Boot Camp + Windows 7 should get you:
Ability to use multiple monitors (Visual Studio's multi-monitor support is really wonderful)
Ability to hibernate (which you wouldn't necessarily get in Boot Camp + Server 2008 R2)
Use of all of your memory (SharePoint 2010 is a memory hog, running in a VM won't help the situation)
Fewer inconveniences like copy and paste problems
If for whatever reason Boot Camp isn't an option I'd go with Windows 7 in a VM. One of the big pros over Server 2008 is it has all of the features that you need already enabled. It ends up being a lot of work to debug why something isn't working in Server 2008 R2 only to find some obscure feature or service wasn't installed or activated out of the box.
As the release date for the public beta of SharePoint 2010 is coming closer and closer, I'm wondering how to set up a developer machine for it. I've heard that for developing on SharePoint a 64 bit system is needed and that Microsoft advises to use Windows 7 64 bit and install SharePoint 2010 on it.
I think that won't be an option for me as I only have one computer here at work and I don't like to install SharePoint on the same machine that I use for my normal office work (email stuff, writing concept papers, ...).
Am I right that I only have two other options? Using Server 2008 as a desktop operating system and install SharePoint 2010 on a virtual machine or using Windows 7 64 and use VMWare to host the SharePoitn 2010.
So I'm wondering if there are any other options and which one you chose? What experiences have you already made?
If you decide to install 2010 on your Vista/Windows 7 machine, make sure you have at least 4GB of RAM (I'd personally want at least 6, if not 8), and follow the instructions from MSDN: "Setting Up the Development Environment for SharePoint Server"
Yes, you are right there are only three options:
Install SharePoint onto the OS natively (new for 2010 and aimed at developers)
Install SharePoint into a VM you run on your machine
Get a second machine and install SharePoint on it.
In addition you will need Visual Studio 2010 for the developer experience to be complete.
I would highly recommend trying the install native route as it will provide a great development experience and will run fairly light. Also at worst you can have two batch files, one of which starts and the other stops the services so there will be zero impact except disk.
I am doing some SP2010 development at the moment. I have:
Windows Server 2008 R2 Standard with Sharepoint 2010 and Visual Studio 2010 installed, running on Hyper-V. I just connect to it via Remote Desktop. Works a treat. I do all my dev in the VS2010 instance running on the VM, leaving my physical work computer free for everything else. I back up my work using TFS, so if I mess up the Sharepoint install (somehow), I can just roll back to a previous snapshot.
hope that helps. :D
Sharepoint 2010 development takes a lot of hardware resources. You can't use Hyper-V on Windows 7 but if you have the Enterprise version of the OS, you can build and boot directly from VHD, taking normal advantage of hardware resources. To learn how, you can visit this post: http://rambletech.wordpress.com/2011/09/19/boot-windows-7-directly-from-virtual-hard-disk-image/
HTH.
What are the best practices in setting up a new instance of TFS 2008 Workgroup edition?
Specifically, the constraints are as follows:
Must install on an existing Windows Server 2008 64 bit
TFS application layer is 32 bit only
Should I install SQL Server 2008, Sharepoint and the app layer in a virtual instance of Windows Server 2008 or 2003(I am already running Hyper-V) or split the layers with a database on the host OS and the app layer in a virtual machine?
Edit: Apparently, splitting the layers is not recommended
This is my recipe for installing TFS 2008 SP1.
There is no domain controller in this scenario, we are only a couple of users. If I was to do it again, I would consider changing our environement to use a active directory domain.
Host Server running Windows Server 2008 with 8GB RAM and quad processor
Fresh install of Windows Server 2008 32bit in a VM under Hyper-V
Install Application Server role with IIS
Install SQL Server 2008 Standard edition
Use a user account for Reporting Services and Analysis Services
Create a slipstreamed image of TFS 2008 with SP1 and install TFS
Install VSTS 2008
Install Team System Explorer
Install VSTS 2008 SP1
Install TFS Web Access Power tool
After installing everything, reports were not generated. Found this forum post that helped resolve the problem.
Open p://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx
Run the webservice (see above link for details), it will take a little while, the tfsWarehouse will be rebuilt
It is very important to do things in order, download the installation guide and follow it to the letter. I forgot to install the Team System Explorer until after installing SP1 and ventured into all sorts of problems. Installing SP1 once more fixed that.
One critical thing you has to keep in mind about TFS, is that it likes to have the machine all to it self. So if you have to create a separate instance on Hyper-V do it using the proven Windows Server 2003 platform with SQL Server 2005.
I am sure Microsoft has done a great job getting it to work under Windows Server 2008 and SQL Server 2008, however you don't get any additional features with this newer install and it is currently unproven in the wild.
So my recommendation is to stick with what is known until the next release of TFS comes out.
Also splitting the layers is definitely not recommended, especially in the workgroup edition where you will only be allowed to have 5 licensed users. Those 5 users will never exceed the server's needs. Also my recommendation is to not update Sharepoint if you don't need to. In my environment, we don't really use Sharepoint all that much, so I left it alone. Sharepoint is usually, in my experience, where most of the problems come from with TFS.
I just upgraded our team to TFS 2008, from TFS 2005. The hardest part was upgrading SharePoint 2.0 to 3.0, so I would make sure to do that first, if you have not already installed TFS 2008. We had a couple of other difficulties, but they were all either related to the SharePoint upgrade, or to the fact that we were using an aftermarket Policy package - Scrum for TeamSystem. We are on SQL Server 2005, so I cannot address SQL Server 2008. As for splitting the layers, we did not do this either, as we are running on Windows Server 2003 and everything ran under the host OS.
Splitting the layers is only needed for more than 450 users.
I would also recommend having the Build Server on a completely seperate machine. Building is very file system intensive. SQL Server performs best when it has complete control of a file system - so having build and TFS on the same machine may create performance issues while builds are executing.
Perhaps this can be alleviated with proper tuning and seperate physical drives - but I'd think in the long run it would be a lot simpler to just either use some old hardware - or spin up a small virtual machine on a seperate host for your builds