This is a template for deploying a Single Windows server running DNN on IIS, ASP .Net 4.5 and with FTP enabled.

This deployment configures IIS with ASP .Net 4.5 and sets up a DNN site with the provided domain. It also creates a FTP site.

• A Heat provider that supports Rackspace::Cloud::WinServer.
• An OpenStack username, password, and tenant id.
• python-heatclient >= v0.2.8:

pip install python-heatclient

We recommend installing the client within a Python virtual environment.

Here is an example of how to deploy this template using the python-heatclient:

heat --os-username <OS-USERNAME> --os-password <OS-PASSWORD> --os-tenant-id \
  <TENANT-ID> --os-auth-url https://identity.api.rackspacecloud.com/v2.0/ \
  stack-create aspdotnet -f dnn-app-single.yaml \
  -P server_hostname=my-site -P domain=example.org -P ftp_username=ftp_user

• For UK customers, use https://lon.identity.api.rackspacecloud.com/v2.0/ as the --os-auth-url.

Optionally, set environmental variables to avoid needing to provide these values every time a call is made:

export OS_USERNAME=<USERNAME>
export OS_PASSWORD=<PASSWORD>
export OS_TENANT_ID=<TENANT-ID>
export OS_AUTH_URL=<AUTH-URL>

Parameters can be replaced with your own values when standing up a stack. Use the -P flag to specify a custom parameter.

• server_hostname: Hostname to set for the server (Default: DNN)
• image: Operating System to use (Default: Windows Server 2008 R2 SP1)
• flavor: Server size for your deployment (Default: 4 GB Performance)

Once a stack comes online, use heat output-list to see all available outputs. Use heat output-show <OUTPUT NAME> to get the value fo a specific output.

• server_ip: Public IP of the Windows server.
• admin_password: Administrator password for logging into the Windows Server.

If you are new to DNN, the DNN Community has great ressources to get you started including a well maintained Wiki. DNN provides Professional Services and Training, and DNN Extensions are available through the DNN Store.

To login, use the IP address of the server or point an A record to your server's IP. The domain you provided has also been used to set the host file on the server. Therefore you can open an RDP session to the server, open the domain in the web browser and pursue the last step of the DNN site activation.

Once you have the server's IP or the domain name open in the web browser, you must complete the Account information form and the Website information form. The Database Information section MUST remain unchanged because it has been configured in the connection string in the Web.config, and the database has been set to use the application pool identity.

DNN is open source under the MIT Licence.

The Administrator password is included in the passwords/secrets section of this deployment. Use that password and the instructions found here to login and begin managing DNN.

The FTP password is included in the passwords/secrets section of this deployment. You may use Filezilla FTP Client or Cyberduck with the FTP credential to upload your application.

This setup was built through a Powershell Script. Once the deployment is up, the script will not be run again, so it is safe to change settings and configurations on your server and within DNN.

There are substantial changes still happening within the OpenStack Heat project. Template contribution guidelines will be drafted in the near future.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.