Changes between Version 63 and Version 64 of CloudPlugin
- Timestamp:
- Sep 14, 2016, 9:33:59 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CloudPlugin
v63 v64 11 11 * Execute commands (e.g., deployments) to ec2 instances based on environment or role. 12 12 13 [[Image(instance-grid.png )]]13 [[Image(instance-grid.png, border=2)]] 14 14 15 15 There are additional features and quite possibly more to come, but the focus is on orchestrating between AWS and Chef inclusive of managing ec2 instances based on environment or role. … … 205 205 The {{{crud_view}}}, {{{crud_new}}}, {{{crud_edit}}}, and {{{grid_columns}}} options are lists of field names in the order to be displayed in their respective views. "crud" stands for "create, read, update, delete". An asterisk ({{{*}}}) appended to a field name (only applicable for {{{crud_new}}} and {{{crud_edit}}}) indicates that the field should be read-only in that view. All fields in the {{{crud_new}}} and {{{crud_edit}}} views will be used to set or update the chef resource item. 206 206 207 [[Image(instance-new.png )]]207 [[Image(instance-new.png, border=2)]] 208 208 209 209 The {{{grid_sort}}} and {{{grid_asc}}} are for default sorting in the grid view. … … 244 244 Actions such as launching or bootstrapping an ec2 instance or deploying code to an environment can take a variably long time - usually longer than the default Apache timeouts (e.g., {{{FcgidIOTimeout}}}). Instead of wrestling with Apache timeout configurations, this plugin executes each of these actions in a separate, spawned process (an orphaned daemon) that survives Apache timeouts and restarts. Surviving Apache restarts is also helpful when Trac itself is chef-managed and may be restarted by the {{{chef-client}}} upon config changes. Creating a new ec2 instance, executing remote commands, etc. now brings up a new 'Progress' page that tracks the spawned process' progress: 245 245 246 [[Image(progress.png )]]246 [[Image(progress.png, border=2)]] 247 247 248 248 For launching ec2 instances, as the instance id and public DNS become known, they're presented. The progress view is also used for other (potentially) long-lived actions such as deployments and audits where the list of nodes is shown with the same progress icons and time durations.