Seeds on different VMs at DAS-4 do not find each other

[ovedanner]

When running the Pumpkin framework for the Web Services and Cloud-based Systems course and trying to deploy different seeds on different VMs, the different seeds can not really find each other. We tried to run the 'tweetinject' and 'filter' seed on one VM and the 'collector' seed on another VM. The first VM did manage to find a 'collector' seed, but on a different IP address (maybe an IP address of another group).
The image below shows the output from running ./run_pumpkin.sh on the first VM

The image below shows the output from running ./run_pumpkin.sh on the second VM

After this, there is no more output, the program just keeps running

[recap]

it can take up to 60sec for the info to propagate. To eliminate
possibilities of interference you can rename your seeds. This can be done in
2 steps
1 rename the .py file example filter.py to filter08.py
2 open the file filter08.py and replace filter to filter08 in lines
##"object_name": "filter",
to
##"object_name": "filter08",

and
class filter(PmkSeed.Seed):
to
class filter08(PmkSeed.Seed):

do this to all 3 files

REg.

On 29 April 2014 15:47, ovedanner notifications@github.com wrote:

When running the Pumpkin framework for the Web Services and Cloud-based
Systems course and trying to deploy different seeds on different VMs, the
different seeds can not really find each other. We tried to run the
'tweetinject' and 'filter' seed on one VM and the 'collector' seed on
another VM. The first VM did manage to find a 'collector' seed, but on a
different IP address (maybe an IP address of another group).
The image below shows the output from running ./run_pumpkin.sh on the
first VM
[image: tweetinject_filter_seeds_error]https://cloud.githubusercontent.com/assets/3994385/2829567/952a508c-cfa4-11e3-9eeb-5c991538893e.png
The image below shows the output from running ./run_pumpkin.sh on the
second VM
[image: collector_seed_error]https://cloud.githubusercontent.com/assets/3994385/2829575/b581270c-cfa4-11e3-9473-8dac404c9567.png
After this, there is no more output, the program just keeps running

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

REg.