Overview
Key Concepts
General
- Index
- Favorites
- User Getting Started
- General
- User Key Concepts
- Search
- User Testing and Debugging
- User Interface
Account
- Index
- Add a Group to an Organization
- Add a New Azure Cloud
- Add a New Cloud
- Add a User To a Group
- Add a User
- Add a User to a Team
- Azure Setup
- Azure
- Catalogs
- Clouds
- Cost Management
- Create a Team in an Organization
- Delete a Platform
- Deploy an Organization
- Deployment Approval Process
- Enable Access to an Assembly for a User on a Team
- Environment Profiles
- How Cost Tracking and Reporting Works
- Import and Export Catalog
- Account
- Manage OneOps User Accounts
- Notifications
- OneOps Policy Management
- Organization Summary
- Provide Only Necessary Privileges to Accounts
- Reports Summary
- Restrict Access with Teams
- Secrets Proxy
- Security Groups
- Shutdown a Cloud
- View a Reports Summary
- View, Add, or Edit Environment Profiles
- View an Organization Summary
- View Assembly and Organization Consumption with Reports
Design
- Index
- Add a Platform to a Design
- Add a Variable
- Add ELK Stack to an Application
- Add or Delete a Security Group to Open or Close an Additional Port
- Add a Team to an Assembly
- Apache HTTP Server Component
- Apache HTTP Server Pack
- Apache Tomcat Pack
- Artifact Component
- Attachments
- Variables Override Prevention
- Certificate Component
- Chocolatey Package Component
- Components
- Compute Component
- Create Assemblies to Design Applications
- Create Environment Dependency with Environment Profiles
- Daemon Component
- Design Best Practices
- Download Component
- Edit a Platform
- Enable https for a Service (LB Certs)
- File Component
- Filebeat Component
- Firewall Component
- Fully Qualified Domain Name FQDN
- Hostname Component
- Design
- Java Component
- Job Component
- Keystore Component
- Load Balancer Component
- Library Component
- Load/Extract
- Logstash Component
- Manage Assemblies
- DotNet Framework Component
- Microsoft IIS Pack
- IIS Website Component
- Microsoft SQL Server Pack
- Naming Conventions
- NuGet Package Component
- Objectstore Component
- Operating System Component
- Packs
- Platform Links
- Platforms
- Ports by Platform
- Propagation
- Security Group Component
- Secrets Client Component
- Sensuclient Component
- Set Up Multiple Ports/Protocols in Load Balancer
- Share Component
- SSH Keys Component
- Storage Component
- Telegraf Component
- Upgrade an Application Version in an Environment
- User Component
- Variables
- View Design Releases
- Volume Component
- Watching an Assembly
- Website Component
Transition
- Index
- Add CNAME in Azure DNS
- Add CNAME
- Add or Edit Primary and Secondary Clouds
- Add or Reduce Capacity
- Availability Modes
- Configure ECV Check URL on OneOps
- Create an Environment
- Delete an Environment
- Deploy Application after Design Changes
- Deploy an Application for the First Time
- Deploy Application With Database
- Deploy an Environment
- Deploy Multiple Clouds in Parallel
- Deploy and Provision an Application and Environment for the First Time
- Edit an Environment
- Email Notification Relay
- Environment Releases
- Environment
- Transition
- Remove an Unused Cloud from an Environment
- Rollback Code
- Set Variable Cloud Scaling Percentage
- Transition Best Practices
- Transition
- View Deployment Status
Operation
- Index
- Assess the Health of Applications, Platforms and Clouds
- Auto Repair
- Auto Replace
- Auto Scale
- Computes in Operation
- Control Environment
- Enable Platform to Auto Replace Unhealthy Components
- Ensure that Alerts for Production Environment are Sent to NOC
- Find a Platform VIP Name
- Grep or Search Text in Files on Computes
- Operation
- Navigation to Monitors
- Monitors
- Operations
- Operations Summary
- Set Up a Custom Action
- Take a Node out of Traffic (ECV Disable)
- Update or Upgrade New OneOps Code
Apache HTTP Server Pack
The Apache pack provides the user with the ability to use the Apache HTTP Server as a platform in their assembly.
The main components involved are:
- the website component for the actual content
- the Apache HTTP Server component for the server configuration
- the compute component
Examples
Simple Website
Running a website with Apache HTTP server can be implemented with a few simple steps:
- Create a platform with the apache pack.
- Inspect and optionally configure the apache component of the platform.
- Configure the website component
- Use the attachments tab:
- Provide a Source URL that points at an archive file with the contents of your website
- The Destination Path determines the temporary location of the archive.
- Use Execute Command to configure how to extract the archive file.
- The content is downloaded with root ownership and 600 permissions.
- Add commands to ensure the webserver user (typically
apache) can access the files withchownandchmod. 5 Configure the Run on Events to determine, when the content should be downloaded. Recommended values are After Add, After Replace, After Update, On Demand. 6.Commit the design changes and proceed with deployment as usual.
Apache HTTP Server does not automatically restart if you make additional changes & deployments after the initial deployment. Ensure to restart the webserver in operations to load any content changes.
Enable HTTPS
There are two options for configuring HTTPS. Options 1 terminates SSL at the load balancer and the traffic is only encrypted to the load balancer and is clear text from load balancer to web server.
The more advanced Option 2 encrypts the traffic all the way to the web server and its configuration follows below.
General tips about SSL certificate usage can be found in the certificate component documentation.
After configuring the Apache HTTP Server platform you need to obtain a valid certificate with the following characteristics:
- Include Private Key: Enabled
- Include Root Chain: Enabled
- Chain Order: End-entity first
- Format: Base64 (OpenSSL)
- Password: create a password
- Change the the Listen Port on the website component to 443 and enable SSL.
- Turn Enable TLSv1 the configuration of the apache component off and remove 80 from the Listen Ports.
- Add the certificate details in design to use the same certificate for all environment, or in transition for each environment separate as desired.
- Add a lb-certificate and certificate component and configure the certificate. 6.Commit the design changes and proceed with deployment as usual.
