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
Compute Component
The compute component is of core importance and all platforms since it represents the virtual machine and operating system on which the platform runs.
You can configure the compute component as part of your platform in design phase and specific to an environment in the transition phase.
Once your assembly is deployed in an environment you can access the computes in operation.
Configuration
Besides the global configuration available for any component such as Name and Description, you can configure the following attributes:
Instance Size: The instance size determines characteristics of the virtual machine created for operation in terms of processing power, memory size, networking bandwidth and operating system. The size values use clothing sizing values of from extra small to extra large and beyond - XS, S, M, L, XL, XXL, 3XL, 4XL. Instance sizes optimized for compute performance, network performance, storage and memory are available. The generic values are mapped to cloud specific sizes.
Networking - PAT ports: Configure the Port Address Translation PAT from
internal ports (key) to external ports (value).
Networking - Require public IP: Check if a public IP is required. Setting is
used when the compute cloud service public networking type is interface or
floating.
The Cloud Services configuration displays the services required by the component and provided by the cloud. Typically compute and dns are required, while others such as mirrors or ntp are optional and can be enabled or disabled as desired.
The Compute Depends On and Depend On Compute sections contain lists of related components.
The attachments tab should not be used on computes components as attachments are not functional when associated to a compute.
The monitors tab can be used to configure compute-related monitors.
Example Use Cases
Update the Size or OS of a Compute
Changing a compute in design, like any other design change, requires you to:
- Save the change and commit the overall design.
- Pull the design to the environment.
- Deploy the environment.
If you are changing a compute configuration like size or a related setting all deployed instances have to be flagged to be replaced.
To roll out a change you need to either disable and re-enable the whole platform perform a rolling replacment.
A platform wide approach means that the application will be unavailable during the procedure.
- Change the configuration of the compute in design.
- Set the action to replace all the computes in operation.
- Disable the entire platform.
- Commit and deploy.
- Enable the platform to commit and deploy.
Alternatively you can roll the change out via replacing computes:
- Change the configuration of the compute in design.
- Set the action to replace all the computes in operation.
- Choose a step size of less than 100% for a rolling upgrade.
- Pull the design changes to the environment.
- Deploy to the environment.
