OK after that I saw it did assign an ip as the remoteIp however as such
since it did not work I understand now that basically what needs to happen
is that the Router needs to hold an ip and forward all ports much like
ec2's system would i.e. with its public and private ips
Will try and lookup how to do that
On Tuesday, March 18, 2014 4:23:00 PM UTC-7, Aatxe Urrutia wrote:
>
> ok digging into Code I believe I see why
>
>
> This is hard coded to 10.x and 192.x networks, it is an assumption that
> these networks are meant to be private only
>
>
> code is
>
> public function determineServerIps($client, $server)
> {
> $addr = $server->nic[0]->ipaddress;
> if (strpos($addr, "10.") === 0 || strpos($addr, "192.168") ===
> 0)
> $localIp = $addr;
> else
> $remoteIp = $addr;
>
> if ($server->publicip)
> $remoteIp = $server->publicip;
>
> return array(
> 'localIp' => $localIp,
> 'remoteIp' => $remoteIp
>
>
>
> Which makes sense however in our case we really didn't want to use public
> ip ranges in the private ( behind firewall space) its ok just have to
> design it a little more again might do a hack on my side as well
>
> On Tuesday, March 4, 2014 1:45:39 PM UTC-8, Aatxe Urrutia wrote:
>>
>> Hello I have an issue with scalr communication and cloudstack, I can
>> bring up vm's fine i imported then via scalr and it saved them as snapshot
>> when I start the farm it brings the vms up but then says 'Cloudstack
>> handler failed: Argument missing: ipAddressId'
>>
>>
>> I have a setup in aws as well and what I notice that is apparently
>> different is that my local scalr - cloudstack implementation brings up vm's
>> with one network interface, so would this error come from a lack of a
>> "public interface"?
>>
>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
