[Spce-user] Amazon issues

Andreas Granig agranig at sipwise.com
Fri May 27 15:59:18 EDT 2011


One thing I've just noticed, probably someone with good AWS experience
can help out here:

Looks like our AMI ami-84cdfbf0 is only available in Region eu-west-1,
because that's the Region I used to create the AMI. Any idea how I can
"migrate" this AMI to other regions? It's built from an EBS also located
in eu-west-1, and I'd like to avoid to re-create the EBS from scratch in
every Region just to build the AMI out of it.

Ideas?

Andreas

On 05/27/2011 04:11 PM, Andreas Granig wrote:
> Hi Claude,
> 
> Actually I've managed to create a public AMI for the SPCE v2.2, and my
> tests were successful so far (sip-to-sip, pstn peering in/out with
> registration and authentication, voicebox, rewrite rules etc).
> 
> Could you probably give it a try and provide some feedback?
> 
> The AMI is ami-84cdfbf0 and works with a t1.micro also. Keep
> kernel/ramdisk as default, and you'll need a Security Group allowing the
> following ports: 22/tcp, 443/tcp, 1443/tcp, 2443/tcp (only if you need
> access to the soap interfce), 5060/udp, 30000-40000/udp.
> 
> Once booted, in /etc/ngcp-config/config.yml change networking->eaddress
> to the address assigned to eth0 (check with "ifconfig eth0"), and
> networking->aaddress to the Elastic IP you assign to the instance. If
> running on a t1.micro instance, also change database->bufferpoolsize to
> 64M. When done, execute "ngcpcfg apply".
> 
> Hope this helps,
> Andreas
> 
> On 05/25/2011 02:55 AM, Claude Hayn wrote:
>>
>> Hello,
>>
>> We've been attempting to install version 2.2 on the Amazon cloud with mixed
>> success.  We completed the installation, but are failing to get the UIs
>> available for the administrator or end-users.  We did the upgrade today to
>> the 2.2 release from v2.2-rc1.
>>
>> During the installation of v2.2-rc1 and subsequent upgrade to v2.2
>> installation we received these errors:
>>
>> Errors were encountered while processing:
>>  collectd
>>  ngcp-check-tools
>>  ngcp-services-ce
>>  ngcp-ngcp-ce
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>>
>> root at domU-1222-361-39-500-CD-A0:~# passwd cdrexport
>> passwd: user 'cdrexport' does not exist
>>
>>
>> dkms: running auto installation service for kernel 2.6.32-5-xen-amd64:
>>       ngcp-mediaproxy-ng (1.3.5)...failed.
>> dkms: WARNING: linux headers are missing, which may explain the above
>> failures.
>>       please install the linux-headers-2.6.32-5-xen-amd64 package to fix
>> this.
>> run-parts: executing /etc/kernel/postinst.d/initramfs-tools
>> 2.6.32-5-xen-amd64 /boot/vmlinuz-2.6.32-5-xen-amd64
>> Setting up firmware-linux-free (2.6.32-34squeeze1) ...
>> Setting up linux-libc-dev (2.6.32-34squeeze1) ...
>> Bad owner for maybe chown UNKNOWN './ngrep-sip.conf'
>> Bad group for maybe chgrp UNKNOWN './ngrep-sip.conf'
>> [master bf7c851] committing changes in /etc after apt run
>>  4 files changed, 26 insertions(+), 14 deletions(-)
>>
>>
>> I'm extremely interested in any suggestions. 
>>
>> I read in Spce-user Digest, Vol 6, Issue 20 that Andreas is planning an
>> Amazon How To (hopefully soon).
>>
>> I would certainly welcome this.
>>
>> Thank you,
>>
>> Claude
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20110527/bb0c9b96/attachment-0001.asc>


More information about the Spce-user mailing list