Release notes for version 1.0
A few words on VirtualBox
- If you are not familiar with VirtualBox, you can read the documentation and download the software from Oracle's web site.
- Once VirtualBox is installed and running, you import the .ovm distribution image using the File / Import Appliance function.
- The default network connection for the Virtual Machines is NAT. This will work well for the case of logging in and examing the VM and containers. To connect to services hosted by the VM from the outside, you'll likely want to switch the network to bridged mode. This will give the VM an IP address from your network's DHCP server and provide you with the ability to access services from a browser. Remember, if you are on a public network, the VM will be exposed to the world and we publish the password on this web site. When you complete the process below, you'll be able to see the COmanage login web page.
Initial Testing Process
A quick test of the environment includes the following steps:
- Download the COmanage-1.0.ova file (or the most recent version) from the distribution site.
- Import the image into virtual box.
- Potentially change the network setting from NAT to Bridged - see above comments on VirtualBox.
- Start the virtual machine.
- Login to the VM:
- LoginId: comanage
- password: comanage
- Create a self-signed certificate for use in the test. (See this sample output on the right)
- Fill in appropriate answers for Country and City.
- Be sure to keep track of the domain name that you put into the CN field.
- openssl req -x509 -nodes -days 365 -sha256 -newkey rsa:2048 -keyout coman.key -out coman.crt
- Copy the certificate files to the appropriate locations for the installer
- cp coman.key coman.crt /home/comanage/ssl/httpd
- cp coman.crt /home/comanage/ssl/httpd/incommon_chain.pem
- Run the configuration script: ./bin/configure.sh
- As you answer the questions, make sure that the FQDN you specify now matches the CN value used when you created the certificate. For this reason - you may just want to use IP addresses if they will be the same each time you run the virtual machine (as one might on a laptop virtual machine)
- You can safely put in fake answers to the email questions as that feature will not work as part of this simple test.
- Start comanage: ./bin/comanage.sh
- You will see the final build/configuration process.
- When this command returns, the Docker version of COmanage will be up and running.
- Verify that two containers are running via the command: docker ps
- If you enabled bridge mode described above
- Obtain the IP address of your virtual machine if you haven't done so already.
- ip addr | grep -i "inet" and look for and address from your campus network
- With a web browser, connect to: https://ip_addr/registry/
- Ignore the SSL warnings.
- You should connect to a login page. Do not expect the login function to actually work, that requires InCommon integration and this quick test does not perform any InCommon integration.
- Obtain the IP address of your virtual machine if you haven't done so already.
Full Testing Process
[comanage@Hostname]$ openssl req -x509 -nodes -days 365 -sha256 -newkey rsa:2048 -keyout coman.key -out coman.crt Generating a 1024 bit RSA private key Please note that you may want to find out your virtual machine's IP address PRIOR to getting to this point as it may be more straightforward running and connecting to the virtual machine and COmanage once the build is complete.
[comanage@Hostname]$ cp coman.key coman.crt /home/comanage/ssl/httpd [comanage@Hostname]$ cp coman.crt /home/comanage/ssl/httpd/incommon_chain.pem |
---|