Configserver Setup Script Output

 [root@localhost ~]# aeolus-configserver-setup

 This script will help you configure Apache as a proxy for a Config Server.
 Typically this is only useful if you are not familiar with Apache
 configurations and modules, specifically with mod_proxy, mod_auth_basic, and
 mod_ssl.
 
 Also, this configuration tool assumes that you are not currently running Apache
 for any purposes on this server.  This configuration tool will create a Named
 Virtual Host for *:443.  If this server is currently using Apache to serve
 secure pages on port 443, then this tool should not be used.
 
 
 Do you wish to continue [y/N]:  y
 
 
 Please provide the web application URL where the Config Server is currently
 running on this server.  If the Config Server was installed from an RPM, then
 this will typically be:
 
   http://localhost:4567/
 
 The provided URL should be a fully qualified URL, providing the scheme,
 hostname, and port:  http://HOSTNAME:PORT/
 
 
 Enter the application URL [http://localhost:4567/]: 
 Root context: /
 App URL: http://localhost:4567/
 Conductor Auth Key: 206251912458234717300511
 Conductor Auth Secret: NUkrZIZIVGWmzfE1oPDdtDdohiPfYGyGGba06WaaMM8vQNry
 \n\n*** You need to add this config server information to a ***
 *** provider account in conductor.                      ***
 running: echo | /usr/bin/puppet --modulepath /usr/share/aeolus-configserver/configure/puppet/modules --external_nodes /tmp/tmp.RFE8RDtzj8 --node_terminus exec
 notice: /Stage[main]/Configserver/Service[configserver]/ensure: ensure changed 'stopped' to 'running'
 notice: /Stage[main]/Apache::Ssl/Exec[config-iptables-for-443]/returns: executed successfully
 notice: /Stage[main]/Apache::Ssl/File[vhost-443-addl]/ensure: created
 notice: /Stage[main]/Apache::Ssl/Exec[pk-gen]/returns: executed successfully
 notice: /Stage[main]/Apache::Ssl/Exec[sign-request]/returns: executed successfully
 notice: /Stage[main]/Apache::Ssl/Exec[cert]/returns: executed successfully
 notice: /Stage[main]/Apache::Ssl/File[vhost-443]/ensure: created
 notice: /Stage[main]/Apache::Base/Exec[graceful-apache]: Triggered 'refresh' from 3 events
 notice: /Stage[main]/Configserver/File[/var/lib/aeolus-configserver/configs/]/ensure: created
 notice: /Stage[main]/Configserver/File[/var/lib/aeolus-configserver/configs/oauth/]/ensure: created
 notice: /Stage[main]/Configserver/File[/var/lib/aeolus-configserver/configs/oauth/206251912458234717300511]/ensure: defined content as '{md5}8d4bc196bc7d7285ff13497b070068f0'
 notice: Finished catalog run in 2.46 seconds

Understanding the setup script

There are a few of points to make about the Configserver setup script. The script prompts you for two pieces of information: Do you wish to continue [y/N] and Enter the application URL [http://localhost:4567/].

The first prompt, Do you wish to continue [y/N], is confirming whether you understand that the setup script will attempt to configure a Virtual Host in Apache for :443 and use Apache as a proxy for the Configserver. This configuration makes Apache listen on port 443 on ALL network interfaces. In the case outlined in these instructions, it is always OK to answer “y” to this question. In an advanced configuration, you may want to run the Configserver alongside other services that use Apache as a proxy. In these cases, you should not use this setup script, and should instead configure Apache manually.

The second prompt, Enter the application URL [http://localhost:4567/], is asking where the Configserver service is running. In the case outlined in these instructions, it is always acceptable to simply hit the key. This will accept the default value of http://localhost:4567. NB: this indicates how Apache will contact the Configserver, not how users and external services (such as Aeolus Conductor) will contact the Configserver.