I get the following when running the local nodecellar-example blueprint on windows 7:
2016-07-05 13:20:59 LOG [mongod_9f278.start] INFO: MongoDB has not start
ed. waiting...
2016-07-05 13:21:02 LOG [mongod_9f278.start] INFO: [GET] http://localhos
t:28017 000
2016-07-05 13:21:02 LOG [mongod_9f278.start] INFO: MongoDB has not start
ed. waiting...
2016-07-05 13:21:05 LOG [mongod_9f278.start] INFO: [GET] http://localhos
t:28017 000
2016-07-05 13:21:05 LOG [mongod_9f278.start] INFO: MongoDB has not start
ed. waiting...
2016-07-05 13:21:08 LOG [mongod_9f278.start] INFO: [GET] http://localhos
t:28017 000
2016-07-05 13:21:09 LOG [mongod_9f278.start] INFO: MongoDB has not start
ed. waiting...
2016-07-05 13:21:10 LOG [mongod_9f278.start] ERROR: MongoDB failed to st
art. waited for a 120 seconds.
2016-07-05 13:21:10 LOG [mongod_9f278.start] INFO: Execution done (retur
n_code=1): c:\users\rivieb2\appdata\local\temp\tmp81nzbf-start-mongo.sh
2016-07-05 13:21:10 CFY [mongod_9f278.start] Task failed 'script_runner.
tasks.run'
2016-07-05 13:21:11 CFY 'install' workflow execution failed: Workflow fa
iled: Task failed 'script_runner.tasks.run'
Workflow failed: Task failed 'script_runner.tasks.run'
When launching cloudify locally, (without manager), it runs the scripts on the local machine where you are running the cloudify client, I think is not the right behaviour but is how it's working currently.
I have tried to launch nodecellar on amazon and both, mongo and node server are running on the local machine.
Running versions:
Cloudify 3.4.1
Ubuntu 14.04.4
After re-reading your example, you maybe are trying to executing the local-blueprint.yaml, in that case, of course you can't because is using bash script to configure and launch the services which is not compatible with windows 7.