Currently I am of the assumption that Postgres-XL can be installed on Linux/Unix machines. But is there a way to install Postgres-XL on a Windows Server Machine?
If Yes, any help or resource would be really helpful.
Thanks
Postgres-XL does not currently compile in Windows. IIRC, this was due to the the threading that the Global Transaction Manager uses. It probably would not be difficult to buidl the other components- the Coordinator and Datanode. In any event, some testing should be done if tried. Feel free to send me a message if you are interested in helping test it if we do a Windows build.
Related
Suggest a solution if such exists.
There are 20 empty baremetal servers. Me need to go to the ipmi and manually connect the image file to start the installation OS.
Question: are there any solutions to automate this process?
Since you tag this question with "OpenStack", you must have heard of Ironic.
If the thought of installing OpenStack to automatically install servers frightens you, look up Cobbler. It was used by now defunct products Helion OpenStack and SUSE OpenStack Cloud to set up clouds.
Ubuntu uses MAAS for this purpose.
This is not a complete list.
I am planning to implement some Jenkins driven tests of one GUI application which is available for Windows (Windows 7) and Linux (CentOS7) operating systems. to run these GUI tests, I was recommended to use Sikuli. By looking at the available versions, I came to the two following sites:
SikuliX (http://sikulix.com)
SikuliX2 (https://github.com/RaiMan/SikuliX2)
Does someone have some experience with one of the two applications? Can I safely move to SikuliX2?
Moreover, as a constraint, the Linux tests should be running on a docker.
Thanks in advance for your feedback.
Pretty much, I am needing to know if I need to run it on a server or can it be run from my desktop? I would hate to think I would run a 24 hour load test from my desktop and tie up my machine, but is that how it goes? Or can I run it from a server (virtual or other?)?
Sorry for the ambiguity, but I do not know much about the infrastructure needed to run this. I tried researching it but all I can find is how to run a load test, not the physical requirements. I also read something about team systems.
Thank you in advance.
The requirements are in MSDN, here. And yes, you can run it on your desktop. As you will see from the link, your requirements are driven by the number of virtual users you want to add to the load. How resource intensive your tests are also plays into this.
You should be able to find what you need on MSDN. Read though it and set things up and run the test. Post a more specific question here on StackOverflow if you run into problems.
I need to build a small cluster for my research. It's pretty humble and I'd like to build a cluster just with my other 3 laptops at home.
I'm writing in C++. My codes in MPI framework are ready. I can simulate them using visual studio 2010 and they're fine. Now I want to see the real thing.
I want to do it free (I'm a student). I have ubuntu installed and I wonder:
if I could build a cluster using ubuntu. I couldn't find a clear answer to that on the net.
if not, is there a free linux distro that I can use at building cluster?
I also wonder if I have to install ubuntu, or the linux distro on the host machine to all other laptops. Will any other linux distribution (like openSUSE) work with the one at the host machine? Or do all of them have to be same linux distro?
Thank you all.
In principle, any linux distro will work with the cluster, and also in principle, they can all be different distros. In practice, it'll be a enormously easier with everything the same, and if you get a distribution which already has a lot of your tools set up for you, it'll go much more quickly.
To get started, something like the Bootable Cluster CD should be fairly easy -- I've not used it myself yet, but know some who have. It'll let you boot up a small cluster without overwriting anything on the host computer, which lets you get started very easily. Other distributions of software for clusters include Rocks and Oscar. A technical discussion on building a cluster can be found here.
I also liked PelicanHPC when I used it a few years back. I was more successful getting it to work that with Rocks, but it is much less popular.
http://pareto.uab.es/mcreel/PelicanHPC/
Just to get a cluster up and running is actually not very difficult for the situation you're describing. Getting everything installed and configured just how you want it though can be quite challenging. Good luck!
Our production machines are running on debian etch. Now, they finally released lenny, the day will come we need to upgrade these systems. How can I do this with minimal risk? Are there any premises, preparations of fall-back scenarios and do I need a plan B in case something goes wrong? Besides the binary packages handled by the debian installer there are a couple of compiled applications running on the machines.
Personally I wouldn't upgrade any OS on an important server. OS upgrades always have the potential for subtle bugs, whether it's Windows, Linux or anything else. Debian has got better than it used to be in this regard; dist-upgrade doesn't hose the machine nearly as often as it used to back in the day. But for production machines there is no point in risking it.
Set up new servers with a fresh OS and application deployment and swap them in as needs arise. There is no need to hurry to replace Etch companywide in one go. It will be supported with security updates for a while yet.
Having just gone through that transition for some dev boxes, I wanted to point out that you'll probably want to recompile any custom libraries that you'll be linking against. Lenny uses GCC 4.3, whereas Etch uses 4.1. The output from either compiler isn't very compatible with the other. You may need to install the gcc-4.1 package to do things like compile custom kernel modules.
If you're using 3rd party tools that have a plugin interface, you may have challenges there. I've been having troubles getting Matlab plugins (mex files) to work.
I'd suggest starting with a test system. After hammering it for a while and verifying that everything's working, switch it to be a production box.
Most people don't update production servers for exactly this reason - if it's working correctly, you wouldn't update unless you had a compelling reason.
Assuming you have a dev box built similarly to the production machine, you can simulate the update on the dev box.