Hi There

I am setting up a test install of clearwater in an AWS VPC in London 
(eu-west-2). Initially I would like to set up an All In One installation. Our 
virtual DC in AWS has a VPC containing a public part and a private part. I am 
aiming initially to set up in the public part, which allows external input. I 
have a Route53 domain set up: rmcore.net<http://rmcore.net>. I have a chef 
server and workstation set up and working in the VPC.

Initially I found no support for eu-west-2. I have been able to resolve that by 
adding appropriately to boxes.rb and fog/aws.rb. I also managed to figure out 
the necessary environment config required to add the AIO instance to a VPC. So 
far so good.

However, the installed instance doesn’t seem to be using much of the chef 
environment data when configuring the new instance:

- my domain is not being used for the home_domain (it’s still 
example.com<http://example.com>)
- the amazon public host names are being used instead of the Route53 domain I 
specified in the chef environment.
- I would prefer to be using private IPs or hostnames rather than public.

Probably I could spend more time on this and figure it all out for myself, but 
it’s taken me quite a while to get this far and I’d like to know if there is 
either

a) a resource that covers the use case I want
b) someone on here who might be able to help me with the environment config I 
need to do what I want.

Here’s my environment file:

ubuntu@chef-client:~$ cat chef/environments/clearwater.rb
name “clearwater”
description "Clearwater deployment - clearwater”
cookbook_versions "clearwater" => "= 0.1.0”
override_attributes "clearwater" => {
  "root_domain" => “rmcore.net<http://rmcore.net>”,
  "vpc" => {"vpc_id" => “vpc-xxxxxxx", "subnet_id" => “subnet-xxxxxxxx”},
  "region" => "eu-west-2”,
  "availability_zones" => ["eu-west-2b”],
  "repo_servers" => ["http://repo.cw-ngv.com/stable”],
  "number_start" => “83555000000”,
  "number_count" => 1000,
  "keypair" => “jimaws”,
  "keypair_dir" => "~/.chef/“,
  "pstn_number_count" => 0,

  # Signup key. Anyone with this key can create accounts
  # on the deployment. Set to a secure value.
  "signup_key" => “xxxxxxxxx”,

  # TURN workaround password, used by faulty WebRTC clients.
  # Anyone with this password can use the deployment to send
  # arbitrary amounts of data. Set to a secure value.
  "turn_workaround" => “xxxxxxxxx”,

  # Ellis API key. Used by internal scripts to
  # provision, update and delete user accounts without a password.
  # Set to a secure value.
  "ellis_api_key" => “xxxxxxx”,

  # Ellis cookie key. Used to prevent spoofing of Ellis cookies. Set
  # to a secure value.
  "ellis_cookie_key" => “xxxxxxxxx”,

  # SMTP credentials as supplied by your email provider.
  "smtp_server" => “localhost”,
  "smtp_username" => “”,
  "smtp_password" => “”,

  # Sender to use for password recovery emails. For some
  # SMTP servers (e.g., Amazon SES) this email address
  # must be validated or email sending will fail.
  "email_sender" => "[email protected]<mailto:[email protected]>”
}

Here’s the created shared_config:

[cw-aio]ubuntu@ec2-52-56-82-175:~$ cat /etc/clearwater/shared_config
# Deployment definitions
home_domain=example.com<http://example.com>
sprout_hostname=ec2-52-56-82-175.eu-west-2.compute.amazonaws.com<http://ec2-52-56-82-175.eu-west-2.compute.amazonaws.com>
hs_hostname=ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:8888<http://ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:8888>
hs_provisioning_hostname=ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:8889<http://ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:8889>
xdms_hostname=ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:7888<http://ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:7888>
ralf_hostname=
chronos_hostname=
cassandra_hostname=
sprout_registration_store=ec2-52-56-82-175.eu-west-2.compute.amazonaws.com<http://ec2-52-56-82-175.eu-west-2.compute.amazonaws.com>
ralf_session_store=
homestead_impu_store=ec2-52-56-82-175.eu-west-2.compute.amazonaws.com<http://ec2-52-56-82-175.eu-west-2.compute.amazonaws.com>

# Email server configuration
smtp_smarthost=127.0.0.1
smtp_username=username
smtp_password=password
[email protected]<mailto:[email protected]>

# I-CSCF/S-CSCF configuration
upstream_hostname=ec2-52-56-82-175.eu-west-2.compute.amazonaws.com<http://ec2-52-56-82-175.eu-west-2.compute.amazonaws.com>
scscf_uri="sip:scscf.ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:5054;transport=TCP”
icscf_uri="sip:icscf.ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:5052;transport=TCP”
bgcf_uri="sip:bgcf.ec2-52-56-82-175.eu-west-2.compute.amazonaws.com:5053;transport=TCP”

# Keys
signup_key=secret
turn_workaround=secret
ellis_api_key=secret
ellis_cookie_key=secret

reduce_cassandra_mem_usage=Y

Any help or advice gratefully received!

Kind regards
Jim

RedMatter Ltd
Jim Page
VP Mobile Services
+44 (0)333 150 1666
+44 (0)7870 361412
[email protected]<mailto:[email protected]>

_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to