Added reverse proxy for glance-api
Added reverse proxy for glance_registry
reverse proxy for cinder
Added reverse proxy for nova api
Added reverse proxy for nova-ec2 api
Added reverse proxy for neutron
Enable CORS header for radosgw

This patch add CORS header for radosgw.

This is depend on patch jiocloud/puppet-ceph#6
Changed the endpoints to use jiocloud.com domain

SSL need the urls to have the domain names match to the domain name in the
certificate. The easiest option here (which works on all environments including
production) is to change the endpoints to the names in jiocloud.com domain and
make appropriate cnames which points lb.<servicename>.service.consul to
appropritate <servicename>.jiocloud.com.

In this case, all we need to do is to create self signed certificate for test
systems and CA signed certificate for prod/staging without any other changes.

So this patch making below changes.

* Add cnames in dnsmasq to all endpoints to <service name>.jiocloud.com.
  * I have taken the names we used in previous implementation (like compute for
nova, volume for cinder etc.)
* Change the endpoint to the new names.
* Used the same name on all internal/public/admin urls
  * All the requests including internal requests should use the urls from load
    balancer which was not true because we were using
    real.<servicename>.service.consul for internal and admin endpoints
  * The public access to the APIs will be through NATed IPs (to public IPs)
    in which case even though it use same names, internal servers will be
    resolving it to internal names (using dnsmasq cnames) and external clients will
    be using public IPs from public dns servers
* Other option is to use a different name for internal/admin urls (in jiocloud.com domain iteself
  something like compute-internal.jiocloud.com).
* Changed dns/entry.pp to use dns_resolve from orchestration_utils instead of
  dns_a because dns_a was failing the execution if the address is not resolvable
  which was causing the entire deployment stuck there.
Use keystone_public_address to create openrc
Added ssl to openstack components

This patch:

* jiocloud-ssl-certs package is installing expired packages as of now, so adding
  self signed certificate and distribute it through puppet until repackaged with
  right certificate
* Trust installed self signed certificate
* Enable SSL on hiera data
* Moved apache class parameters to hiera from rjil::apache
* Changed Puppetfile to use jiocloud/puppet-openstack_extras as it need to be
  patched.
Made appropriate changes to fix tests and other issues

* Some tests were hardcoded for http, fixed them
* Added contrail keystone_protocol hiera data to be https
* added hiera data specific to rjil::tempest to work with https
Changed puppetfile to use Harish's repo for testing the changes
Set of arrangements to fix ssl problems

* splitted ssl cert installation and trusting it as we will have to trust the
  certificate on all nodes which need to call any openstack apis
* Just put trust_selfsigned_cert code in rjil::base, it is not required to
  trust the cert on some set of servers like st nodes, etcd , but st node is not
  there in virtual node scenario and etcd is the only one left, so I put it as
  part of rjil::base, it may be changed as and when required.
* Changed some consul service definition to handle http calls with ssl
* Included port for radosgw tests as including ssl change the default port to
  443
* Fixed spec tests
Changed Puppetfile to use jiocloud/puppet-ceph module
Merge pull request #277 from hkumarmk/combined_patch_for_api_apache_frontend

Combined patch for api apache frontend