Pulsar installation on Windows...

I'm having trouble getting to square one with a Windows deployment of pulsar. I'm working towards a cloud-based (AWS cloud formation, auto-scaling, ideally) windows instance that can act as a worker for a CloudMan galaxy cluster to carry out mass-spec conversion utilities which must run on windows.

I'm following the published installation docs, using virtualenv and pip. I'm using EPD Python corresponding to 2.7.11 on a clean, new (virtual) 64-bit Windows 7 installation.

Install with pip in the virtual environment seems to go fine. Pulsar-config with no arguments runs without any errors, but app.yaml is essentially empty, with just "---" in it. server.ini is created too - this looks correct, although I'm worried that there are so many things in there I don't plan to use. Should I comment out most of it?

There is no runable pulsar.exe, but I do see pulsar-main.exe and pulsar-run.exe. Pulsar-main.exe doesn't seem to accept the --url argument (referenced later in the docs) so I guess pulsar-run.exe is the Windows executable for pulsar.

The galaxy.utils import is problematic, since my Windows/EPD python has no module "grp" (for Linux groups). I wrapped this in a try/except ImportError block with a pass on exception to proceed.

Both pulsar-run and pulsar-check generate the following error when I run them:

File "c:\users\nathan\pulsar\venv\lib\site-packages\pulsar\client\transport\standard.py", line 49, in execute
raise PulsarClientTransportError(transport_message=exc.reason)
pulsar.client.exceptions.PulsarClientTransportError: Unknown transport error (transport message: [Errno 10061] No connection could be made because the target machine actively refused it)
- Does this mean I have to stand up a Galaxy instance to check/test the pulsar install, or is there something else going on?
- Why is app.yaml empty?
- Is anyone else currently doing this in production?

Thanks,
- n

Start with the published installation docs, then inspect the pulsar-config output, app.yaml, and server.ini generated on Windows. Trace the failure reported from pulsar/client/transport/standard.py and the galaxy.utils import issue, and compare pulsar-main.exe, pulsar-run.exe, and pulsar-check behavior. Done means the Windows installation path and connection requirements are documented or the reproducible installation defects are identified.

Written by the indexing model from the issue text.