On 07/28/2011 02:27 PM, Justin Clift wrote:
On 27/07/2011, at 1:35 AM, Mark McLoughlin wrote:
>> This tends to trip people up: aeolus-configure sets up a Deltacloud server
>> with the Mock driver on the port 3002.
>> However, our tests look for the mock dc instance on 3001, which means that to
>> run the tests, one must start another Mock Deltacloud server.
Quickly trying out Mock in the 0.3.0 RHEL 6.1 release rpms, and it's broken
"out of the box". :(
Both /etc/init.d/deltacloud-core and /etc/init.d/deltacloud-mock are set to
use port 3002. The core one starts first, so the mock one silently fails.
(!). Changing the port number to 3005 for mock in the mock startup script,
then adjusting the port through the Conductor UI (mock provider account) lets
So, is the -core startup script wrong, or the -mock startup one? If the -mock
one is wrong, we'll need to move the mock port from 3002 anyway.
I checked this on my Fedora setup and I have both -core and -mock init
scripts there. They're both using 3002, but according to chkconfig
deltacloud-core doen't get started automatically.
In addition to that, I have deltacloud-ec2-us-east-1 and
deltacloud-ec2-us-west-1 scripts, each with their own unique port.
This is what I think is going on: Conductor uses separate deltacloud
daemons for mock, ec2-east and ec2-west locations. These get in when the
user installs the RPMs and runs aeolus-configure.
Deltacloud-core comes with the deltacloud-core RPM (a package Conductor
depends on) and happens to use the same port as our mock by default.
When we install Conductor, aeolus-configure makes sure the vanilla
deltacloud-core is stopped and we set up our own services.
I think it's unfortunate that both mock and the vanilla core use the
same port, but it shouldn't matter unless the user wants to start a
separate core instance manually. In that case, they can change the ports
Anyway, the latest release of Deltacloud supports connecting to multiple
providers on a single deltacloud instance listening on a single port.
After we start using that, we can use the vanilla deltacloud-core script
and it will work for all the providers we want to connect to.
I'm not terribly familiar with this topic, however. Can someone from the
aeolus-configure team elaborate?
Regards and best wishes,
Aeolus Community Manager
aeolus-devel mailing list