AWS OpsWorks
Welcome to the AWS OpsWorks API Reference . This guide provides
descriptions, syntax, and usage examples about AWS OpsWorks
actions and data types, including common parameters and error
codes.
AWS OpsWorks is an application management service that provides an
integrated experience for overseeing the complete application
lifecycle. For information about this product, go to the `AWS
OpsWorks`_ details page.
SDKs and CLI
The most common way to use the AWS OpsWorks API is by using the
AWS Command Line Interface (CLI) or by using one of the AWS SDKs
to implement applications in your preferred language. For more
information, see:
Endpoints
AWS OpsWorks supports only one endpoint, opsworks.us-
east-1.amazonaws.com (HTTPS), so you must connect to that
endpoint. You can then use the API to direct AWS OpsWorks to
create stacks in any AWS Region.
Chef Version
When you call CreateStack, CloneStack, or UpdateStack we recommend
you use the ConfigurationManager parameter to specify the Chef
version, 0.9, 11.4, or 11.10. The default value is currently 11.4.
For more information, see `Chef Versions`_.
-
APIVersion = '2013-02-18'
-
DefaultRegionEndpoint = 'opsworks.us-east-1.amazonaws.com'
-
DefaultRegionName = 'us-east-1'
-
ResponseError
alias of JSONResponseError
-
ServiceName = 'OpsWorks'
-
TargetPrefix = 'OpsWorks_20130218'
-
assign_volume(volume_id, instance_id=None)
Assigns one of the stack’s registered Amazon EBS volumes to a
specified instance. The volume must first be registered with
the stack by calling RegisterVolume. For more information, see
`Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- volume_id (string) – The volume ID.
- instance_id (string) – The instance ID.
|
-
associate_elastic_ip(elastic_ip, instance_id=None)
Associates one of the stack’s registered Elastic IP addresses
with a specified instance. The address must first be
registered with the stack by calling RegisterElasticIp. For
more information, see `Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- elastic_ip (string) – The Elastic IP address.
- instance_id (string) – The instance ID.
|
-
attach_elastic_load_balancer(elastic_load_balancer_name, layer_id)
Attaches an Elastic Load Balancing load balancer to a
specified layer. For more information, see `Elastic Load
Balancing`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- elastic_load_balancer_name (string) – The Elastic Load Balancing
instance’s name.
- layer_id (string) – The ID of the layer that the Elastic Load Balancing
instance is to be attached to.
|
-
clone_stack(source_stack_id, service_role_arn, name=None, region=None, vpc_id=None, attributes=None, default_instance_profile_arn=None, default_os=None, hostname_theme=None, default_availability_zone=None, default_subnet_id=None, custom_json=None, configuration_manager=None, chef_configuration=None, use_custom_cookbooks=None, use_opsworks_security_groups=None, custom_cookbooks_source=None, default_ssh_key_name=None, clone_permissions=None, clone_app_ids=None, default_root_device_type=None)
Creates a clone of a specified stack. For more information,
see `Clone a Stack`_.
Required Permissions: To use this action, an IAM user must
have an attached policy that explicitly grants permissions.
For more information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- source_stack_id (string) – The source stack ID.
- name (string) – The cloned stack name.
- region (string) – The cloned stack AWS region, such as “us-east-1”. For
more information about AWS regions, see `Regions and Endpoints`_.
- vpc_id (string) – The ID of the VPC that the cloned stack is to be
launched into. It must be in the specified region. All instances
will be launched into this VPC, and you cannot change the ID later.
|
- If the VPC ID corresponds to a default VPC and you have specified
- either the DefaultAvailabilityZone or the DefaultSubnetId
parameter only, AWS OpsWorks infers the value of the other
parameter. If you specify neither parameter, AWS OpsWorks sets
these parameters to the first valid Availability Zone for the
specified region and the corresponding default VPC subnet ID,
respectively.
If you specify a nondefault VPC ID, note the following:
- For more information on how to use AWS OpsWorks with a VPC, see
- `Running a Stack in a VPC`_. For more information on default VPC
and EC2 Classic, see `Supported Platforms`_.
| Parameters: |
- attributes (map) – A list of stack attributes and values as key/value
pairs to be added to the cloned stack.
- service_role_arn (string) – The stack AWS Identity and Access Management
(IAM) role, which allows AWS OpsWorks to work with AWS resources on
your behalf. You must set this parameter to the Amazon Resource
Name (ARN) for an existing IAM role. If you create a stack by using
the AWS OpsWorks console, it creates the role for you. You can
obtain an existing stack’s IAM ARN programmatically by calling
DescribePermissions. For more information about IAM ARNs, see
`Using Identifiers`_.
- default_instance_profile_arn (string) – The ARN of an IAM profile that is
the default profile for all of the stack’s EC2 instances. For more
information about IAM ARNs, see `Using Identifiers`_.
- default_os (string) – The cloned stack’s default operating system, which
must be set to Amazon Linux or Ubuntu 12.04 LTS. The default
option is Amazon Linux.
- hostname_theme (string) – The stack’s host name theme, with spaces are
replaced by underscores. The theme is used to generate host names
for the stack’s instances. By default, HostnameTheme is set to
Layer_Dependent, which creates host names by appending integers
to the layer’s short name. The other themes are:
|
- Baked_Goods
- Clouds
- European_Cities
- Fruits
- Greek_Deities
- Legendary_Creatures_from_Japan
- Planets_and_Moons
- Roman_Deities
- Scottish_Islands
- US_Cities
- Wild_Cats
- To obtain a generated host name, call GetHostNameSuggestion, which
- returns a host name based on the current theme.
| Parameters: |
- default_availability_zone (string) – The cloned stack’s default
Availability Zone, which must be in the specified region. For more
information, see `Regions and Endpoints`_. If you also specify a
value for DefaultSubnetId, the subnet must be in the same zone.
For more information, see the VpcId parameter description.
- default_subnet_id (string) – The stack’s default subnet ID. All instances
will be launched into this subnet unless you specify otherwise when
you create the instance. If you also specify a value for
DefaultAvailabilityZone, the subnet must be in the same zone. For
information on default values and when this parameter is required,
see the VpcId parameter description.
- custom_json (string) – A string that contains user-defined, custom JSON.
It is used to override the corresponding default stack
configuration JSON values. The string should be in the following
format and must escape characters such as ‘”’.:
|
“{“key1”: “value1”, “key2”: “value2”,...}”
- For more information on custom JSON, see `Use Custom JSON to Modify the
- Stack Configuration JSON`_
| Parameters: |
- configuration_manager (dict) – The configuration manager. When you clone
a stack we recommend that you use the configuration manager to
specify the Chef version, 0.9, 11.4, or 11.10. The default value is
currently 11.4.
- chef_configuration (dict) – A ChefConfiguration object that specifies
whether to enable Berkshelf and the Berkshelf version on Chef 11.10
stacks. For more information, see `Create a New Stack`_.
- use_custom_cookbooks (boolean) – Whether to use custom cookbooks.
- use_opsworks_security_groups (boolean) – Whether to associate the AWS
OpsWorks built-in security groups with the stack’s layers.
|
- AWS OpsWorks provides a standard set of built-in security groups, one
- for each layer, which are associated with layers by default. With
UseOpsworksSecurityGroups you can instead provide your own custom
security groups. UseOpsworksSecurityGroups has the following
settings:
- True - AWS OpsWorks automatically associates the appropriate built-in
security group with each layer (default setting). You can associate
additional security groups with a layer after you create it but you
cannot delete the built-in security group.
- False - AWS OpsWorks does not associate built-in security groups with
layers. You must create appropriate EC2 security groups and
associate a security group with each layer that you create.
However, you can still manually associate a built-in security group
with a layer on creation; custom security groups are required only
for those layers that need custom settings.
For more information, see `Create a New Stack`_.
| Parameters: |
- custom_cookbooks_source (dict) – Contains the information required to
retrieve an app or cookbook from a repository. For more
information, see `Creating Apps`_ or `Custom Recipes and
Cookbooks`_.
- default_ssh_key_name (string) – A default SSH key for the stack instances.
You can override this value when you create or update an instance.
- clone_permissions (boolean) – Whether to clone the source stack’s
permissions.
- clone_app_ids (list) – A list of source stack app IDs to be included in
the cloned stack.
- default_root_device_type (string) – The default root device type. This
value is used by default for all instances in the cloned stack, but
you can override it when you create an instance. For more
information, see `Storage for the Root Device`_.
|
-
create_app(stack_id, name, type, shortname=None, description=None, data_sources=None, app_source=None, domains=None, enable_ssl=None, ssl_configuration=None, attributes=None)
Creates an app for a specified stack. For more information,
see `Creating Apps`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID.
- shortname (string) – The app’s short name.
- name (string) – The app name.
- description (string) – A description of the app.
- data_sources (list) – The app’s data source.
- type (string) – The app type. Each supported type is associated with a
particular layer. For example, PHP applications are associated with
a PHP layer. AWS OpsWorks deploys an application to those instances
that are members of the corresponding layer.
- app_source (dict) – A Source object that specifies the app repository.
- domains (list) – The app virtual host settings, with multiple domains
separated by commas. For example: ‘www.example.com, example.com’
- enable_ssl (boolean) – Whether to enable SSL for the app.
- ssl_configuration (dict) – An SslConfiguration object with the SSL
configuration.
- attributes (map) – One or more user-defined key/value pairs to be added
to the stack attributes.
|
-
create_deployment(stack_id, command, app_id=None, instance_ids=None, comment=None, custom_json=None)
Deploys a stack or app.
- App deployment generates a deploy event, which runs the
associated recipes and passes them a JSON stack configuration
object that includes information about the app.
- Stack deployment runs the deploy recipes but does not
raise an event.
For more information, see `Deploying Apps`_ and `Run Stack
Commands`_.
Required Permissions: To use this action, an IAM user must
have a Deploy or Manage permissions level for the stack, or an
attached policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID.
- app_id (string) – The app ID. This parameter is required for app
deployments, but not for other deployment commands.
- instance_ids (list) – The instance IDs for the deployment targets.
- command (dict) – A DeploymentCommand object that specifies the
deployment command and any associated arguments.
- comment (string) – A user-defined comment.
- custom_json (string) – A string that contains user-defined, custom JSON.
It is used to override the corresponding default stack
configuration JSON values. The string should be in the following
format and must escape characters such as ‘”’.:
|
“{“key1”: “value1”, “key2”: “value2”,...}”
- For more information on custom JSON, see `Use Custom JSON to Modify the
- Stack Configuration JSON`_.
-
create_instance(stack_id, layer_ids, instance_type, auto_scaling_type=None, hostname=None, os=None, ami_id=None, ssh_key_name=None, availability_zone=None, virtualization_type=None, subnet_id=None, architecture=None, root_device_type=None, install_updates_on_boot=None, ebs_optimized=None)
Creates an instance in a specified stack. For more
information, see `Adding an Instance to a Layer`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID.
- layer_ids (list) – An array that contains the instance layer IDs.
- instance_type (string) – The instance type. AWS OpsWorks supports all
instance types except Cluster Compute, Cluster GPU, and High Memory
Cluster. For more information, see `Instance Families and Types`_.
The parameter values that you use to specify the various types are
in the API Name column of the Available Instance Types table.
- auto_scaling_type (string) –
|
The instance auto scaling type, which has three possible values:
- AlwaysRunning: A 24/7 instance, which is not affected by auto
scaling.
- TimeBasedAutoScaling: A time-based auto scaling instance, which
is started and stopped based on a specified schedule. To specify
the schedule, call SetTimeBasedAutoScaling.
- LoadBasedAutoScaling: A load-based auto scaling instance, which
is started and stopped based on load metrics. To use load-based
auto scaling, you must enable it for the instance layer and
configure the thresholds by calling SetLoadBasedAutoScaling.
| Parameters: |
- hostname (string) – The instance host name.
- os (string) – The instance operating system, which must be set to one of
the following.
|
- Standard operating systems: Amazon Linux or Ubuntu 12.04 LTS
- Custom AMIs: Custom
- The default option is Amazon Linux. If you set this parameter to
- Custom, you must use the CreateInstance action’s AmiId parameter
to specify the custom AMI that you want to use. For more
information on the standard operating systems, see `Operating
Systems`_For more information on how to use custom AMIs with
OpsWorks, see `Using Custom AMIs`_.
| Parameters: |
- ami_id (string) – A custom AMI ID to be used to create the instance. The
AMI should be based on one of the standard AWS OpsWorks APIs:
Amazon Linux or Ubuntu 12.04 LTS. For more information, see
`Instances`_
- ssh_key_name (string) – The instance SSH key name.
- availability_zone (string) – The instance Availability Zone. For more
information, see `Regions and Endpoints`_.
- virtualization_type (string) – The instance’s virtualization type,
paravirtual or hvm.
- subnet_id (string) – The ID of the instance’s subnet. If the stack is
running in a VPC, you can use this parameter to override the
stack’s default subnet ID value and direct AWS OpsWorks to launch
the instance in a different subnet.
- architecture (string) – The instance architecture. The default option is
x86_64. Instance types do not necessarily support both
architectures. For a list of the architectures that are supported
by the different instance types, see `Instance Families and
Types`_.
- root_device_type (string) – The instance root device type. For more
information, see `Storage for the Root Device`_.
- install_updates_on_boot (boolean) – Whether to install operating system and
package updates when the instance boots. The default value is
True. To control when updates are installed, set this value to
False. You must then update your instances manually by using
CreateDeployment to run the update_dependencies stack command or
manually running yum (Amazon Linux) or apt-get (Ubuntu) on the
instances.
- ebs_optimized (boolean) – Whether to create an Amazon EBS-optimized
instance.
|
-
create_layer(stack_id, type, name, shortname, attributes=None, custom_instance_profile_arn=None, custom_security_group_ids=None, packages=None, volume_configurations=None, enable_auto_healing=None, auto_assign_elastic_ips=None, auto_assign_public_ips=None, custom_recipes=None, install_updates_on_boot=None, use_ebs_optimized_instances=None)
Creates a layer. For more information, see `How to Create a
Layer`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
- The layer type. A stack cannot have more than one built-in layer of the
- same type. It can have any number of custom layers. This parameter
must be set to one of the following:
- custom: A custom layer
- db-master: A MySQL layer
- java-app: A Java App Server layer
- rails-app: A Rails App Server layer
- lb: An HAProxy layer
- memcached: A Memcached layer
- monitoring-master: A Ganglia layer
- nodejs-app: A Node.js App Server layer
- php-app: A PHP App Server layer
- web: A Static Web Server layer
| Parameters: |
- name (string) – The layer name, which is used by the console.
- shortname (string) – The layer short name, which is used internally by AWS
OpsWorks and by Chef recipes. The short name is also used as the
name for the directory where your app files are installed. It can
have a maximum of 200 characters, which are limited to the
alphanumeric characters, ‘-‘, ‘_’, and ‘.’.
- attributes (map) – One or more user-defined key/value pairs to be added
to the stack attributes.
- custom_instance_profile_arn (string) – The ARN of an IAM profile that to
be used for the layer’s EC2 instances. For more information about
IAM ARNs, see `Using Identifiers`_.
- custom_security_group_ids (list) – An array containing the layer custom
security group IDs.
- packages (list) – An array of Package objects that describe the layer
packages.
- volume_configurations (list) – A VolumeConfigurations object that
describes the layer’s Amazon EBS volumes.
- enable_auto_healing (boolean) – Whether to disable auto healing for the
layer.
- auto_assign_elastic_ips (boolean) – Whether to automatically assign an
`Elastic IP address`_ to the layer’s instances. For more
information, see `How to Edit a Layer`_.
- auto_assign_public_ips (boolean) – For stacks that are running in a VPC,
whether to automatically assign a public IP address to the layer’s
instances. For more information, see `How to Edit a Layer`_.
- custom_recipes (dict) – A LayerCustomRecipes object that specifies the
layer custom recipes.
- install_updates_on_boot (boolean) – Whether to install operating system and
package updates when the instance boots. The default value is
True. To control when updates are installed, set this value to
False. You must then update your instances manually by using
CreateDeployment to run the update_dependencies stack command or
manually running yum (Amazon Linux) or apt-get (Ubuntu) on the
instances.
- use_ebs_optimized_instances (boolean) – Whether to use Amazon EBS-optimized
instances.
|
-
create_stack(name, region, service_role_arn, default_instance_profile_arn, vpc_id=None, attributes=None, default_os=None, hostname_theme=None, default_availability_zone=None, default_subnet_id=None, custom_json=None, configuration_manager=None, chef_configuration=None, use_custom_cookbooks=None, use_opsworks_security_groups=None, custom_cookbooks_source=None, default_ssh_key_name=None, default_root_device_type=None)
Creates a new stack. For more information, see `Create a New
Stack`_.
Required Permissions: To use this action, an IAM user must
have an attached policy that explicitly grants permissions.
For more information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- name (string) – The stack name.
- region (string) – The stack AWS region, such as “us-east-1”. For more
information about Amazon regions, see `Regions and Endpoints`_.
- vpc_id (string) – The ID of the VPC that the stack is to be launched into.
It must be in the specified region. All instances will be launched
into this VPC, and you cannot change the ID later.
|
- If the VPC ID corresponds to a default VPC and you have specified
- either the DefaultAvailabilityZone or the DefaultSubnetId
parameter only, AWS OpsWorks infers the value of the other
parameter. If you specify neither parameter, AWS OpsWorks sets
these parameters to the first valid Availability Zone for the
specified region and the corresponding default VPC subnet ID,
respectively.
If you specify a nondefault VPC ID, note the following:
- For more information on how to use AWS OpsWorks with a VPC, see
- `Running a Stack in a VPC`_. For more information on default VPC
and EC2 Classic, see `Supported Platforms`_.
| Parameters: |
- attributes (map) – One or more user-defined key/value pairs to be added
to the stack attributes.
- service_role_arn (string) – The stack AWS Identity and Access Management
(IAM) role, which allows AWS OpsWorks to work with AWS resources on
your behalf. You must set this parameter to the Amazon Resource
Name (ARN) for an existing IAM role. For more information about IAM
ARNs, see `Using Identifiers`_.
- default_instance_profile_arn (string) – The ARN of an IAM profile that is
the default profile for all of the stack’s EC2 instances. For more
information about IAM ARNs, see `Using Identifiers`_.
- default_os (string) – The stack’s default operating system, which must be
set to Amazon Linux or Ubuntu 12.04 LTS. The default option is
Amazon Linux.
- hostname_theme (string) – The stack’s host name theme, with spaces are
replaced by underscores. The theme is used to generate host names
for the stack’s instances. By default, HostnameTheme is set to
Layer_Dependent, which creates host names by appending integers
to the layer’s short name. The other themes are:
|
- Baked_Goods
- Clouds
- European_Cities
- Fruits
- Greek_Deities
- Legendary_Creatures_from_Japan
- Planets_and_Moons
- Roman_Deities
- Scottish_Islands
- US_Cities
- Wild_Cats
- To obtain a generated host name, call GetHostNameSuggestion, which
- returns a host name based on the current theme.
| Parameters: |
- default_availability_zone (string) – The stack’s default Availability
Zone, which must be in the specified region. For more information,
see `Regions and Endpoints`_. If you also specify a value for
DefaultSubnetId, the subnet must be in the same zone. For more
information, see the VpcId parameter description.
- default_subnet_id (string) – The stack’s default subnet ID. All instances
will be launched into this subnet unless you specify otherwise when
you create the instance. If you also specify a value for
DefaultAvailabilityZone, the subnet must be in that zone. For
information on default values and when this parameter is required,
see the VpcId parameter description.
- custom_json (string) – A string that contains user-defined, custom JSON.
It is used to override the corresponding default stack
configuration JSON values. The string should be in the following
format and must escape characters such as ‘”’.:
|
“{“key1”: “value1”, “key2”: “value2”,...}”
- For more information on custom JSON, see `Use Custom JSON to Modify the
- Stack Configuration JSON`_.
| Parameters: |
- configuration_manager (dict) – The configuration manager. When you clone
a stack we recommend that you use the configuration manager to
specify the Chef version, 0.9, 11.4, or 11.10. The default value is
currently 11.4.
- chef_configuration (dict) – A ChefConfiguration object that specifies
whether to enable Berkshelf and the Berkshelf version on Chef 11.10
stacks. For more information, see `Create a New Stack`_.
- use_custom_cookbooks (boolean) – Whether the stack uses custom cookbooks.
- use_opsworks_security_groups (boolean) – Whether to associate the AWS
OpsWorks built-in security groups with the stack’s layers.
|
- AWS OpsWorks provides a standard set of built-in security groups, one
- for each layer, which are associated with layers by default. With
UseOpsworksSecurityGroups you can instead provide your own custom
security groups. UseOpsworksSecurityGroups has the following
settings:
- True - AWS OpsWorks automatically associates the appropriate built-in
security group with each layer (default setting). You can associate
additional security groups with a layer after you create it but you
cannot delete the built-in security group.
- False - AWS OpsWorks does not associate built-in security groups with
layers. You must create appropriate EC2 security groups and
associate a security group with each layer that you create.
However, you can still manually associate a built-in security group
with a layer on creation; custom security groups are required only
for those layers that need custom settings.
For more information, see `Create a New Stack`_.
| Parameters: |
- custom_cookbooks_source (dict) – Contains the information required to
retrieve an app or cookbook from a repository. For more
information, see `Creating Apps`_ or `Custom Recipes and
Cookbooks`_.
- default_ssh_key_name (string) – A default SSH key for the stack instances.
You can override this value when you create or update an instance.
- default_root_device_type (string) – The default root device type. This
value is used by default for all instances in the stack, but you
can override it when you create an instance. The default option is
instance-store. For more information, see `Storage for the Root
Device`_.
|
-
create_user_profile(iam_user_arn, ssh_username=None, ssh_public_key=None, allow_self_management=None)
Creates a new user profile.
Required Permissions: To use this action, an IAM user must
have an attached policy that explicitly grants permissions.
For more information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- iam_user_arn (string) – The user’s IAM ARN.
- ssh_username (string) – The user’s SSH user name. The allowable characters
are [a-z], [A-Z], [0-9], ‘-‘, and ‘_’. If the specified name
includes other punctuation marks, AWS OpsWorks removes them. For
example, my.name will be changed to myname. If you do not
specify an SSH user name, AWS OpsWorks generates one from the IAM
user name.
- ssh_public_key (string) – The user’s public SSH key.
- allow_self_management (boolean) – Whether users can specify their own SSH
public key through the My Settings page. For more information, see
`Setting an IAM User’s Public SSH Key`_.
|
-
delete_app(app_id)
Deletes a specified app.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | app_id (string) – The app ID. |
-
delete_instance(instance_id, delete_elastic_ip=None, delete_volumes=None)
Deletes a specified instance. You must stop an instance before
you can delete it. For more information, see `Deleting
Instances`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- instance_id (string) – The instance ID.
- delete_elastic_ip (boolean) – Whether to delete the instance Elastic IP
address.
- delete_volumes (boolean) – Whether to delete the instance’s Amazon EBS
volumes.
|
-
delete_layer(layer_id)
Deletes a specified layer. You must first stop and then delete
all associated instances. For more information, see `How to
Delete a Layer`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | layer_id (string) – The layer ID. |
-
delete_stack(stack_id)
Deletes a specified stack. You must first delete all
instances, layers, and apps. For more information, see `Shut
Down a Stack`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | stack_id (string) – The stack ID. |
-
delete_user_profile(iam_user_arn)
Deletes a user profile.
Required Permissions: To use this action, an IAM user must
have an attached policy that explicitly grants permissions.
For more information on user permissions, see `Managing User
Permissions`_.
| Parameters: | iam_user_arn (string) – The user’s IAM ARN. |
-
deregister_elastic_ip(elastic_ip)
Deregisters a specified Elastic IP address. The address can
then be registered by another stack. For more information, see
`Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | elastic_ip (string) – The Elastic IP address. |
-
deregister_rds_db_instance(rds_db_instance_arn)
Deregisters an Amazon RDS instance.
| Parameters: | rds_db_instance_arn (string) – The Amazon RDS instance’s ARN. |
-
deregister_volume(volume_id)
Deregisters an Amazon EBS volume. The volume can then be
registered by another stack. For more information, see
`Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | volume_id (string) – The volume ID. |
-
describe_apps(stack_id=None, app_ids=None)
Requests a description of a specified set of apps.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- stack_id (string) – The app stack ID. If you use this parameter,
DescribeApps returns a description of the apps in the specified
stack.
- app_ids (list) – An array of app IDs for the apps to be described. If
you use this parameter, DescribeApps returns a description of the
specified apps. Otherwise, it returns a description of every app.
|
-
describe_commands(deployment_id=None, instance_id=None, command_ids=None)
Describes the results of specified commands.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- deployment_id (string) – The deployment ID. If you include this parameter,
DescribeCommands returns a description of the commands associated
with the specified deployment.
- instance_id (string) – The instance ID. If you include this parameter,
DescribeCommands returns a description of the commands associated
with the specified instance.
- command_ids (list) – An array of command IDs. If you include this
parameter, DescribeCommands returns a description of the
specified commands. Otherwise, it returns a description of every
command.
|
-
describe_deployments(stack_id=None, app_id=None, deployment_ids=None)
Requests a description of a specified set of deployments.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID. If you include this parameter,
DescribeDeployments returns a description of the commands
associated with the specified stack.
- app_id (string) – The app ID. If you include this parameter,
DescribeDeployments returns a description of the commands
associated with the specified app.
- deployment_ids (list) – An array of deployment IDs to be described. If
you include this parameter, DescribeDeployments returns a
description of the specified deployments. Otherwise, it returns a
description of every deployment.
|
-
describe_elastic_ips(instance_id=None, stack_id=None, ips=None)
Describes `Elastic IP addresses`_.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- instance_id (string) – The instance ID. If you include this parameter,
DescribeElasticIps returns a description of the Elastic IP
addresses associated with the specified instance.
- stack_id (string) – A stack ID. If you include this parameter,
DescribeElasticIps returns a description of the Elastic IP
addresses that are registered with the specified stack.
- ips (list) – An array of Elastic IP addresses to be described. If you
include this parameter, DescribeElasticIps returns a description
of the specified Elastic IP addresses. Otherwise, it returns a
description of every Elastic IP address.
|
-
describe_elastic_load_balancers(stack_id=None, layer_ids=None)
Describes a stack’s Elastic Load Balancing instances.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- stack_id (string) – A stack ID. The action describes the stack’s Elastic
Load Balancing instances.
- layer_ids (list) – A list of layer IDs. The action describes the Elastic
Load Balancing instances for the specified layers.
|
-
describe_instances(stack_id=None, layer_id=None, instance_ids=None)
Requests a description of a set of instances.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- stack_id (string) – A stack ID. If you use this parameter,
DescribeInstances returns descriptions of the instances
associated with the specified stack.
- layer_id (string) – A layer ID. If you use this parameter,
DescribeInstances returns descriptions of the instances
associated with the specified layer.
- instance_ids (list) – An array of instance IDs to be described. If you
use this parameter, DescribeInstances returns a description of
the specified instances. Otherwise, it returns a description of
every instance.
|
-
describe_layers(stack_id=None, layer_ids=None)
Requests a description of one or more layers in a specified
stack.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID.
- layer_ids (list) – An array of layer IDs that specify the layers to be
described. If you omit this parameter, DescribeLayers returns a
description of every layer in the specified stack.
|
-
describe_load_based_auto_scaling(layer_ids)
Describes load-based auto scaling configurations for specified
layers.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: | layer_ids (list) – An array of layer IDs. |
-
describe_my_user_profile()
Describes a user’s SSH information.
Required Permissions: To use this action, an IAM user must
have self-management enabled or an attached policy that
explicitly grants permissions. For more information on user
permissions, see `Managing User Permissions`_.
-
describe_permissions(iam_user_arn=None, stack_id=None)
Describes the permissions for a specified stack.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
-
describe_raid_arrays(instance_id=None, raid_array_ids=None)
Describe an instance’s RAID arrays.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- instance_id (string) – The instance ID. If you use this parameter,
DescribeRaidArrays returns descriptions of the RAID arrays
associated with the specified instance.
- raid_array_ids (list) – An array of RAID array IDs. If you use this
parameter, DescribeRaidArrays returns descriptions of the
specified arrays. Otherwise, it returns a description of every
array.
|
-
describe_rds_db_instances(stack_id, rds_db_instance_arns=None)
Describes Amazon RDS instances.
| Parameters: |
- stack_id (string) – The stack ID that the instances are registered with.
The operation returns descriptions of all registered Amazon RDS
instances.
- rds_db_instance_arns (list) – An array containing the ARNs of the
instances to be described.
|
-
describe_service_errors(stack_id=None, instance_id=None, service_error_ids=None)
Describes AWS OpsWorks service errors.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID. If you use this parameter,
DescribeServiceErrors returns descriptions of the errors
associated with the specified stack.
- instance_id (string) – The instance ID. If you use this parameter,
DescribeServiceErrors returns descriptions of the errors
associated with the specified instance.
- service_error_ids (list) – An array of service error IDs. If you use
this parameter, DescribeServiceErrors returns descriptions of the
specified errors. Otherwise, it returns a description of every
error.
|
-
describe_stack_summary(stack_id)
Describes the number of layers and apps in a specified stack,
and the number of instances in each state, such as
running_setup or online.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: | stack_id (string) – The stack ID. |
-
describe_stacks(stack_ids=None)
Requests a description of one or more stacks.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: | stack_ids (list) – An array of stack IDs that specify the stacks to be
described. If you omit this parameter, DescribeStacks returns a
description of every stack. |
-
describe_time_based_auto_scaling(instance_ids)
Describes time-based auto scaling configurations for specified
instances.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: | instance_ids (list) – An array of instance IDs. |
-
describe_user_profiles(iam_user_arns=None)
Describe specified users.
Required Permissions: To use this action, an IAM user must
have an attached policy that explicitly grants permissions.
For more information on user permissions, see `Managing User
Permissions`_.
| Parameters: | iam_user_arns (list) – An array of IAM user ARNs that identify the users
to be described. |
-
describe_volumes(instance_id=None, stack_id=None, raid_array_id=None, volume_ids=None)
Describes an instance’s Amazon EBS volumes.
You must specify at least one of the parameters.
Required Permissions: To use this action, an IAM user must
have a Show, Deploy, or Manage permissions level for the
stack, or an attached policy that explicitly grants
permissions. For more information on user permissions, see
`Managing User Permissions`_.
| Parameters: |
- instance_id (string) – The instance ID. If you use this parameter,
DescribeVolumes returns descriptions of the volumes associated
with the specified instance.
- stack_id (string) – A stack ID. The action describes the stack’s
registered Amazon EBS volumes.
- raid_array_id (string) – The RAID array ID. If you use this parameter,
DescribeVolumes returns descriptions of the volumes associated
with the specified RAID array.
- volume_ids (list) – Am array of volume IDs. If you use this parameter,
DescribeVolumes returns descriptions of the specified volumes.
Otherwise, it returns a description of every volume.
|
-
detach_elastic_load_balancer(elastic_load_balancer_name, layer_id)
Detaches a specified Elastic Load Balancing instance from its
layer.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- elastic_load_balancer_name (string) – The Elastic Load Balancing
instance’s name.
- layer_id (string) – The ID of the layer that the Elastic Load Balancing
instance is attached to.
|
-
disassociate_elastic_ip(elastic_ip)
Disassociates an Elastic IP address from its instance. The
address remains registered with the stack. For more
information, see `Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | elastic_ip (string) – The Elastic IP address. |
-
get_hostname_suggestion(layer_id)
Gets a generated host name for the specified layer, based on
the current host name theme.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | layer_id (string) – The layer ID. |
-
make_request(action, body)
-
reboot_instance(instance_id)
Reboots a specified instance. For more information, see
`Starting, Stopping, and Rebooting Instances`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | instance_id (string) – The instance ID. |
-
register_elastic_ip(elastic_ip, stack_id)
Registers an Elastic IP address with a specified stack. An
address can be registered with only one stack at a time. If
the address is already registered, you must first deregister
it by calling DeregisterElasticIp. For more information, see
`Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- elastic_ip (string) – The Elastic IP address.
- stack_id (string) – The stack ID.
|
-
register_rds_db_instance(stack_id, rds_db_instance_arn, db_user, db_password)
Registers an Amazon RDS instance with a stack.
| Parameters: |
- stack_id (string) – The stack ID.
- rds_db_instance_arn (string) – The Amazon RDS instance’s ARN.
- db_user (string) – The database’s master user name.
- db_password (string) – The database password.
|
-
register_volume(stack_id, ec_2_volume_id=None)
Registers an Amazon EBS volume with a specified stack. A
volume can be registered with only one stack at a time. If the
volume is already registered, you must first deregister it by
calling DeregisterVolume. For more information, see `Resource
Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- ec_2_volume_id (string) – The Amazon EBS volume ID.
- stack_id (string) – The stack ID.
|
-
set_load_based_auto_scaling(layer_id, enable=None, up_scaling=None, down_scaling=None)
Specify the load-based auto scaling configuration for a
specified layer. For more information, see `Managing Load with
Time-based and Load-based Instances`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- layer_id (string) – The layer ID.
- enable (boolean) – Enables load-based auto scaling for the layer.
- up_scaling (dict) – An AutoScalingThresholds object with the upscaling
threshold configuration. If the load exceeds these thresholds for a
specified amount of time, AWS OpsWorks starts a specified number of
instances.
- down_scaling (dict) – An AutoScalingThresholds object with the
downscaling threshold configuration. If the load falls below these
thresholds for a specified amount of time, AWS OpsWorks stops a
specified number of instances.
|
-
set_permission(stack_id, iam_user_arn, allow_ssh=None, allow_sudo=None, level=None)
Specifies a user’s permissions. For more information, see
`Security and Permissions`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID.
- iam_user_arn (string) – The user’s IAM ARN.
- allow_ssh (boolean) – The user is allowed to use SSH to communicate with
the instance.
- allow_sudo (boolean) – The user is allowed to use sudo to elevate
privileges.
- level (string) – The user’s permission level, which must be set to one of
the following strings. You cannot set your own permissions level.
|
- deny
- show
- deploy
- manage
- iam_only
- For more information on the permissions associated with these levels,
- see `Managing User Permissions`_
-
set_time_based_auto_scaling(instance_id, auto_scaling_schedule=None)
Specify the time-based auto scaling configuration for a
specified instance. For more information, see `Managing Load
with Time-based and Load-based Instances`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- instance_id (string) – The instance ID.
- auto_scaling_schedule (dict) – An AutoScalingSchedule with the
instance schedule.
|
-
start_instance(instance_id)
Starts a specified instance. For more information, see
`Starting, Stopping, and Rebooting Instances`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | instance_id (string) – The instance ID. |
-
start_stack(stack_id)
Starts a stack’s instances.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | stack_id (string) – The stack ID. |
-
stop_instance(instance_id)
Stops a specified instance. When you stop a standard instance,
the data disappears and must be reinstalled when you restart
the instance. You can stop an Amazon EBS-backed instance
without losing data. For more information, see `Starting,
Stopping, and Rebooting Instances`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | instance_id (string) – The instance ID. |
-
stop_stack(stack_id)
Stops a specified stack.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | stack_id (string) – The stack ID. |
-
unassign_volume(volume_id)
Unassigns an assigned Amazon EBS volume. The volume remains
registered with the stack. For more information, see `Resource
Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: | volume_id (string) – The volume ID. |
-
update_app(app_id, name=None, description=None, data_sources=None, type=None, app_source=None, domains=None, enable_ssl=None, ssl_configuration=None, attributes=None)
Updates a specified app.
Required Permissions: To use this action, an IAM user must
have a Deploy or Manage permissions level for the stack, or an
attached policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- app_id (string) – The app ID.
- name (string) – The app name.
- description (string) – A description of the app.
- data_sources (list) – The app’s data sources.
- type (string) – The app type.
- app_source (dict) – A Source object that specifies the app repository.
- domains (list) – The app’s virtual host settings, with multiple domains
separated by commas. For example: ‘www.example.com, example.com’
- enable_ssl (boolean) – Whether SSL is enabled for the app.
- ssl_configuration (dict) – An SslConfiguration object with the SSL
configuration.
- attributes (map) – One or more user-defined key/value pairs to be added
to the stack attributes.
|
-
update_elastic_ip(elastic_ip, name=None)
Updates a registered Elastic IP address’s name. For more
information, see `Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- elastic_ip (string) – The address.
- name (string) – The new name.
|
-
update_instance(instance_id, layer_ids=None, instance_type=None, auto_scaling_type=None, hostname=None, os=None, ami_id=None, ssh_key_name=None, architecture=None, install_updates_on_boot=None, ebs_optimized=None)
Updates a specified instance.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- instance_id (string) – The instance ID.
- layer_ids (list) – The instance’s layer IDs.
- instance_type (string) – The instance type. AWS OpsWorks supports all
instance types except Cluster Compute, Cluster GPU, and High Memory
Cluster. For more information, see `Instance Families and Types`_.
The parameter values that you use to specify the various types are
in the API Name column of the Available Instance Types table.
- auto_scaling_type (string) –
|
The instance’s auto scaling type, which has three possible values:
- AlwaysRunning: A 24/7 instance, which is not affected by auto
scaling.
- TimeBasedAutoScaling: A time-based auto scaling instance, which
is started and stopped based on a specified schedule.
- LoadBasedAutoScaling: A load-based auto scaling instance, which
is started and stopped based on load metrics.
| Parameters: |
- hostname (string) – The instance host name.
- os (string) – The instance operating system, which must be set to one of
the following.
|
- Standard operating systems: Amazon Linux or Ubuntu 12.04 LTS
- Custom AMIs: Custom
- The default option is Amazon Linux. If you set this parameter to
- Custom, you must use the CreateInstance action’s AmiId parameter
to specify the custom AMI that you want to use. For more
information on the standard operating systems, see `Operating
Systems`_For more information on how to use custom AMIs with
OpsWorks, see `Using Custom AMIs`_.
| Parameters: |
- ami_id (string) – A custom AMI ID to be used to create the instance. The
AMI should be based on one of the standard AWS OpsWorks APIs:
Amazon Linux or Ubuntu 12.04 LTS. For more information, see
`Instances`_
- ssh_key_name (string) – The instance SSH key name.
- architecture (string) – The instance architecture. Instance types do not
necessarily support both architectures. For a list of the
architectures that are supported by the different instance types,
see `Instance Families and Types`_.
- install_updates_on_boot (boolean) – Whether to install operating system and
package updates when the instance boots. The default value is
True. To control when updates are installed, set this value to
False. You must then update your instances manually by using
CreateDeployment to run the update_dependencies stack command or
manually running yum (Amazon Linux) or apt-get (Ubuntu) on the
instances.
- ebs_optimized (boolean) – Whether this is an Amazon EBS-optimized instance.
|
-
update_layer(layer_id, name=None, shortname=None, attributes=None, custom_instance_profile_arn=None, custom_security_group_ids=None, packages=None, volume_configurations=None, enable_auto_healing=None, auto_assign_elastic_ips=None, auto_assign_public_ips=None, custom_recipes=None, install_updates_on_boot=None, use_ebs_optimized_instances=None)
Updates a specified layer.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- layer_id (string) – The layer ID.
- name (string) – The layer name, which is used by the console.
- shortname (string) – The layer short name, which is used internally by AWS
OpsWorksand by Chef. The short name is also used as the name for
the directory where your app files are installed. It can have a
maximum of 200 characters and must be in the following format:
/A[a-z0-9-_.]+Z/.
- attributes (map) – One or more user-defined key/value pairs to be added
to the stack attributes.
- custom_instance_profile_arn (string) – The ARN of an IAM profile to be
used for all of the layer’s EC2 instances. For more information
about IAM ARNs, see `Using Identifiers`_.
- custom_security_group_ids (list) – An array containing the layer’s
custom security group IDs.
- packages (list) – An array of Package objects that describe the
layer’s packages.
- volume_configurations (list) – A VolumeConfigurations object that
describes the layer’s Amazon EBS volumes.
- enable_auto_healing (boolean) – Whether to disable auto healing for the
layer.
- auto_assign_elastic_ips (boolean) – Whether to automatically assign an
`Elastic IP address`_ to the layer’s instances. For more
information, see `How to Edit a Layer`_.
- auto_assign_public_ips (boolean) – For stacks that are running in a VPC,
whether to automatically assign a public IP address to the layer’s
instances. For more information, see `How to Edit a Layer`_.
- custom_recipes (dict) – A LayerCustomRecipes object that specifies the
layer’s custom recipes.
- install_updates_on_boot (boolean) – Whether to install operating system and
package updates when the instance boots. The default value is
True. To control when updates are installed, set this value to
False. You must then update your instances manually by using
CreateDeployment to run the update_dependencies stack command or
manually running yum (Amazon Linux) or apt-get (Ubuntu) on the
instances.
- use_ebs_optimized_instances (boolean) – Whether to use Amazon EBS-optimized
instances.
|
-
update_my_user_profile(ssh_public_key=None)
Updates a user’s SSH public key.
Required Permissions: To use this action, an IAM user must
have self-management enabled or an attached policy that
explicitly grants permissions. For more information on user
permissions, see `Managing User Permissions`_.
| Parameters: | ssh_public_key (string) – The user’s SSH public key. |
-
update_rds_db_instance(rds_db_instance_arn, db_user=None, db_password=None)
Updates an Amazon RDS instance.
| Parameters: |
- rds_db_instance_arn (string) – The Amazon RDS instance’s ARN.
- db_user (string) – The master user name.
- db_password (string) – The database password.
|
-
update_stack(stack_id, name=None, attributes=None, service_role_arn=None, default_instance_profile_arn=None, default_os=None, hostname_theme=None, default_availability_zone=None, default_subnet_id=None, custom_json=None, configuration_manager=None, chef_configuration=None, use_custom_cookbooks=None, custom_cookbooks_source=None, default_ssh_key_name=None, default_root_device_type=None, use_opsworks_security_groups=None)
Updates a specified stack.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- stack_id (string) – The stack ID.
- name (string) – The stack’s new name.
- attributes (map) – One or more user-defined key/value pairs to be added
to the stack attributes.
- service_role_arn (string) – The stack AWS Identity and Access Management
(IAM) role, which allows AWS OpsWorks to work with AWS resources on
your behalf. You must set this parameter to the Amazon Resource
Name (ARN) for an existing IAM role. For more information about IAM
ARNs, see `Using Identifiers`_.
- default_instance_profile_arn (string) – The ARN of an IAM profile that is
the default profile for all of the stack’s EC2 instances. For more
information about IAM ARNs, see `Using Identifiers`_.
- default_os (string) – The stack’s default operating system, which must be
set to Amazon Linux or Ubuntu 12.04 LTS. The default option is
Amazon Linux.
- hostname_theme (string) – The stack’s new host name theme, with spaces are
replaced by underscores. The theme is used to generate host names
for the stack’s instances. By default, HostnameTheme is set to
Layer_Dependent, which creates host names by appending integers
to the layer’s short name. The other themes are:
|
- Baked_Goods
- Clouds
- European_Cities
- Fruits
- Greek_Deities
- Legendary_Creatures_from_Japan
- Planets_and_Moons
- Roman_Deities
- Scottish_Islands
- US_Cities
- Wild_Cats
- To obtain a generated host name, call GetHostNameSuggestion, which
- returns a host name based on the current theme.
| Parameters: |
- default_availability_zone (string) – The stack’s default Availability
Zone, which must be in the specified region. For more information,
see `Regions and Endpoints`_. If you also specify a value for
DefaultSubnetId, the subnet must be in the same zone. For more
information, see CreateStack.
- default_subnet_id (string) – The stack’s default subnet ID. All instances
will be launched into this subnet unless you specify otherwise when
you create the instance. If you also specify a value for
DefaultAvailabilityZone, the subnet must be in that zone. For
more information, see CreateStack.
- custom_json (string) – A string that contains user-defined, custom JSON.
It is used to override the corresponding default stack
configuration JSON values. The string should be in the following
format and must escape characters such as ‘”’.:
|
“{“key1”: “value1”, “key2”: “value2”,...}”
- For more information on custom JSON, see `Use Custom JSON to Modify the
- Stack Configuration JSON`_.
| Parameters: |
- configuration_manager (dict) – The configuration manager. When you clone
a stack we recommend that you use the configuration manager to
specify the Chef version, 0.9, 11.4, or 11.10. The default value is
currently 11.4.
- chef_configuration (dict) – A ChefConfiguration object that specifies
whether to enable Berkshelf and the Berkshelf version on Chef 11.10
stacks. For more information, see `Create a New Stack`_.
- use_custom_cookbooks (boolean) – Whether the stack uses custom cookbooks.
- custom_cookbooks_source (dict) – Contains the information required to
retrieve an app or cookbook from a repository. For more
information, see `Creating Apps`_ or `Custom Recipes and
Cookbooks`_.
- default_ssh_key_name (string) – A default SSH key for the stack instances.
You can override this value when you create or update an instance.
- default_root_device_type (string) – The default root device type. This
value is used by default for all instances in the stack, but you
can override it when you create an instance. For more information,
see `Storage for the Root Device`_.
- use_opsworks_security_groups (boolean) – Whether to associate the AWS
OpsWorks built-in security groups with the stack’s layers.
|
- AWS OpsWorks provides a standard set of built-in security groups, one
- for each layer, which are associated with layers by default.
UseOpsworksSecurityGroups allows you to instead provide your own
custom security groups. UseOpsworksSecurityGroups has the
following settings:
- True - AWS OpsWorks automatically associates the appropriate built-in
security group with each layer (default setting). You can associate
additional security groups with a layer after you create it but you
cannot delete the built-in security group.
- False - AWS OpsWorks does not associate built-in security groups with
layers. You must create appropriate EC2 security groups and
associate a security group with each layer that you create.
However, you can still manually associate a built-in security group
with a layer on creation; custom security groups are required only
for those layers that need custom settings.
For more information, see `Create a New Stack`_.
-
update_user_profile(iam_user_arn, ssh_username=None, ssh_public_key=None, allow_self_management=None)
Updates a specified user profile.
Required Permissions: To use this action, an IAM user must
have an attached policy that explicitly grants permissions.
For more information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- iam_user_arn (string) – The user IAM ARN.
- ssh_username (string) – The user’s SSH user name. The allowable characters
are [a-z], [A-Z], [0-9], ‘-‘, and ‘_’. If the specified name
includes other punctuation marks, AWS OpsWorks removes them. For
example, my.name will be changed to myname. If you do not
specify an SSH user name, AWS OpsWorks generates one from the IAM
user name.
- ssh_public_key (string) – The user’s new SSH public key.
- allow_self_management (boolean) – Whether users can specify their own SSH
public key through the My Settings page. For more information, see
`Managing User Permissions`_.
|
-
update_volume(volume_id, name=None, mount_point=None)
Updates an Amazon EBS volume’s name or mount point. For more
information, see `Resource Management`_.
Required Permissions: To use this action, an IAM user must
have a Manage permissions level for the stack, or an attached
policy that explicitly grants permissions. For more
information on user permissions, see `Managing User
Permissions`_.
| Parameters: |
- volume_id (string) – The volume ID.
- name (string) – The new name.
- mount_point (string) – The new mount point.
|


Visual Perception of the road lanes/boundaries includes to implement artificial vision techniques in order to extract the road lines in an image that came from a camera.
My purpose with this thesis is to develop a solution that complements a great ROS software architecture with Visual Perception of road lanes algorithms.


{{ sign_inout }}
{{ title }}
{{ body }}
AddressBooker
is a little hack by Brad Fitzpatrick<EMAIL_ADDRESS>It comes with
no warranty of any kind
.


Applications are full, but you can still add yourself to the waitlist. We'll also add you to the newsletter so you hear about future events.
We are committed to creating a harassment-free experience for all attendees.
Read about our Code of Conduct policies here.


Clover EFI
r%CLOVERREVISION% (%CLOVERSHA1%)
Developers:
%DEVELOP%
Source code credits to:
%CREDITS%
Package credits to:
%PKGDEV%
Supports Fat32, HFS+, APFS, ExFAT.
Copyright © %CPRYEAR%


{% extends "base.html" %} {% block content %}
OpenCourse is currently unavailable.
The site is down temporarily for routine maintenance and upgrades. Please check back in a few minutes.


Webpack help’s to not worry about to vendor prefixes for support in modern browsers.
Everything you do, will be real time in any browser with the same Wi-fi.
Use DRY development with sass or scss.
You only need to type 2 commands in your terminal
1- npm run watch: for real time development
2- npm run production: for css and js production.
npm install (using npm and node)
yarn install (using yarn and node)
Download at github.com


3:15 pm Decided to have a solo trip, explore the possibilities of 5-MeO-DIPT in a personal, uninterrupted setting. Took one geltab that contained between 18-20 milligrams of Foxy. Now waiting for it to take effect. Took a shower, cleaned up a bit, drank some iced chai tea and bumbled about.
3:55 pm – Starting to feel a few twinges...nothing big. Playing the Legend of Zelda on n64…having a little trouble concentrating.
4:11 pm – Definitely starting to feel it, gonna lay down and watch rat race (the newer version). This should be interesting.
4:23 pm – Ran to the store for some more supplies, milk, etc.
4:42 pm – Made it back, and only just in time. The beginnings of a foxy trip in a pharmacy is pretty daunting.
4:46 pm - There are lovely color distortions among the waves of psychedelic color/sensation pulses. I can SEE waves of synthetic distortion.
4:49 pm – The onset of foxy feel good waves and grinning fool-dom! Joy!
4:58 pm – All within a couple of minutes, full onset of trip…breathing walls, peripheral color distortion and tracers…foxy energetic rushes…auditory distortion too…about to do a whipit….check back in ;)
5:02 pm - Foxy adopts and lengthens the dissasociative affects of Nitrous. The waves of “waaa” are stretched, lengthened and deepened.
5:20 pm - Oh my lord…just looked at clock. Only 18 minutes since last at this computer. Foxy definitely distorts time perception whew…fingers snaking into keyboard. Trying to describe body high…almost like too much ecstacy or body energy…feeling of expanding soul…my skin is stretched too tight for my being. Maybe that’s why people don’t like the body load…feeling of constriction.
5:42 – Feels as if my heart is connected fundamentally to the music…no foxy trips without music…I couldn’t even imagine it.
5:56 pm – I can see how some of us talk about “self” and “one” and “Center” so much…I am here…with the proper music, drugs and atmosphere, I feel completely at one with myself. Most joyous feeling in the world...something akin to the purest feelings of joy when I was a child (christmas mornings, camping trips, etc)
6:04 pm I wonder if other people’s headspaces are like this…sex and music inextricably intertwined…I’ve found that I can play with audio…with enough focus, I can choose and distort sound in my own head. That is the high of psychedelics to me…I am the mistress of my own universe for one day. I control shadow, light, sound and thought from the center of my being. It’s never this good in real life. Heh…now to get there without drugs. Must listen to the Orbital remix of “Perfect Drug” when sober…I don’t remember it being this synthy/distorted/wavy
..or maybe orbital is just that good.
6:12 pm - I take it back…there is a connection with nature through this drug. Must try mushrooms…see how much more organic it gets. Silence is lovely…I turned off the music…the sounds of the world are strangely rhythmical and purposeful. Sunset is going to be awesome.
6:39 pm – Peaking now maybe…everything very deep and far away…much meaning assigned to the faintest perceptible motion or sound. Personal connection to the movement and every sound around me, very sacred hue cast upon the entire world.
6:56 pm - Just had one of THE ONES.  YOW.
Attempting to sing on hallucinogens is definitely interesting. I wish I had a tape recorder. WHEE…I have no idea what this sounds like. Sounds pretty strange on my end, what with the auditory distortion and all.
7:36 pm - Went and talked to my roommate…dunno if he knows that I know that he knows that uh…yeah…I'm not currently residing in this dimension. I totally just recreated a scene from the wizard of oz…where she opens the door to Technicolor and *WHOOSH*! the cutesy 50’s music changes. Except the scene was my back deck, and the music was Orbital's “Bladerunner”. The sunset is beginning…its fargin awesome. The shades of light and dark are much more pronounced on foxy, creating the illusion of deepened color. I really do feel like Dorothy in the Wizard of Oz...everything is in electric technicolor.
7:41 I feel like the most sensitive membrane of skin…any sound or movement or sight vibrates along my entire being most pleasantly.
7:48: Just had an intense spiritual moment…I stared at the world outside and was presented by what (I swear to god sounds so silly but fuck ill say it) looked like a symbol…symmetrical, curving and somehow very meaningful…it just floated out of the trees and hung suspended midair for a moment and then…I pulled away and it dissipated…I was left with an overwhelming feeling of awe. Wow…I certainly hope this makes sense someday. But for just a moment, I vibrated with it, lived in its space and was the symbol with my mind and body…and then it just floated away. I got to keep it, though. Forever burned on my eyes. A lady bug just flew in and landed on my finger. Is the world saying hello?
8:25 pm - Still definitely tripping, although I seem to be past the peak, feeling utterly drained psychically, psychologically. My brain has been thoroughly probed and explored.
8:56 pm well, I’m on the hind end of a uniquely satisfying trip. I’m back, for the most part…cant say whether I’m in one piece or not ;) I am, however, enjoying some very fine strawberry shortcake ice cream and wishing that my baby were here. I may even be up for going out later…the night is still young! I must look completely haggard, tho..after this much goings on in my head, I can imagine what my body looks like. We’ll see later. Heh.
6:42 a.m Morning after. Stayed up quite late, sizzling in a pile of overexposed quivering psychedelic goo. I had to battle some small pesky demons in the wee hours of the morning. The extra sensitivity foxy lends one's eyes and ears is not friendly when one is desperately trying to sleep. I wooed myself to Neverland with thoughts of warmth and love and the next day to be had. The only thing I truly dislike about foxy is its tenacity on the comedown…it will NOT let me sleep. But I think I eventually got a good two or three hours in. The ravens woke me with a very colorful conference outside on my back deck…’twas quite fun to watch. A night of therapeutic self exploration well accented with foxy.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Reid Burke
Left arrow or swipe left to continue!
Upstage is a library for making web presentations built on YUI.
Slides are plain old HTML.
Upstage can be used with deck.js themes.
Build on YUI's rock-solid architecture.
index.html
and the build
directory to another directory.The Upstage core provides the architecture for the presentation. Make it useful by plugging in some of these:
UpstageKeyboard: Keyboard navigation.
UpstageGesture: Gesture navigation.
UpstageBlanker: Blank the screen.
UpstagePermalink: Permalinks to each slide.


|
tiffdither − convert a greyscale image to bilevel using dithering |
|
tiffdither [ options ] input.tif output.tif |
|
tiffdither converts a single channel 8-bit greyscale image to a bilevel image using Floyd-Steinberg error propagation with thresholding. |
|
−c |
Specify the compression to use for data written to the output file: none for no compression, packbits for PackBits compression, lzw for Lempel-Ziv & Welch compression, zip for Deflate compression, g3 for CCITT Group 3 (T.4) compression, and g4 for CCITT Group 4 (T.6) compression. By default tiffdither will compress data according to the value of the Compression tag found in the source file. |
|
The CCITT Group 3 and Group 4 compression algorithms can only be used with bilevel data. Group 3 compression can be specified together with several T.4-specific options: 1d for 1-dimensional encoding, 2d for 2-dimensional encoding, and fill to force each encoded scanline to be zero-filled so that the terminating EOL code lies on a byte boundary. Group 3-specific options are specified by appending a ‘‘:’’-separated list to the ‘‘g3’’ option; e.g. −c g3:2d:fill to get 2D-encoded data with byte-aligned EOL codes. LZW compression can be specified together with a predictor value. A predictor value of 2 causes each scanline of the output image to undergo horizontal differencing before it is encoded; a value of 1 forces each scanline to be encoded without differencing. LZW-specific options are specified by appending a ‘‘:’’-separated list to the ‘‘lzw’’ option; e.g. −c lzw:2 for LZW compression with horizontal differencing. |
|
−f |
Specify the bit fill order to use in writing output data. By default, tiffdither will create a new file with the same fill order as the original. Specifying −f lsb2msb will force data to be written with the FillOrder tag set to LSB2MSB , while −f msb2lsb will force data to be written with the Fill- Order tag set to MSB2LSB . |
|||
|
−t |
Set the threshold value for dithering. By default the threshold value is 128. |
|
The dither algorithm is taken from the tiffmedian(1) program (written by Paul Heckbert). |
|
pal2rgb(1), fax2tiff(1), tiffinfo(1), tiffcp(1), tiff2bw(1), libtiff(3TIFF) Libtiff library home page: http://www.remotesensing.org/libtiff/ |


call psb_abort(icontxt)
This subroutine aborts computation on the parallel virtual machine.
- Type:
- Asynchronous.
- On Entry
-
- icontxt
- the communication context identifying the virtual
parallel machine.
Scope: global.
Type: required.
Intent: in.
Specified as: an integer variable.


AMAZING PEOPLE ARE MAKING AMAZING DESIGNS IN A FUN ENVIRONMENT
When you work with us, you are part of a team of committed
collaborators. All aspects of our software development process are
integrated, interactive
and agile.
Our approach unifies design, development and product management to create exceptional products.
We start each project understanding your business goals, the user's needs and the product requirements
Then we help translate them into effective and elegant solutions.
Before we sign a contract or write a line of code our team will spend the necessary time needed to understand your production vision
The outcome of this scoping is proposal or high level statement of
work
based on your requirements, we can provide acomplete
offering or just the pieces you need
Our design practice offers a full range of services including a brand strategy, interaction and visual design and user experience testing.Throughout your project, our designers create and implement visual design and workflows, solicit user feedback and work with you to make sure what gets built is what is needed.
All engineers are fluent in the latest enterprise, mobile and web development technologies. They collaborate with your team to write and improve test-drive code on a daily basis, using proven practices such as test-driven development and pair programming.
Planning and development is iterative. Because we are constantly coding and testing, the products we build are always ready to go live.This iterative process allows for changes as business requirements evolve.
Blank
Ontario Security
Pyramid
Games
Website
Form
Burned logo
Giraffe Restaurant


The ux-virtual-scroll
component is designed to allow you to display a list of many thousands of items without
any noticeable performance degradation.
This virtual scroll component is similar to the infinite scroll directive but will be much more performant with large datasets. One limitation of the virtual scroll component is that each cell must be the same height.
The component supports both a "Load More" button and paging on scroll which can be styled using the *uxVirtualScrollLoadButton
structural directive. The loading indicator can also be defined using the *uxVirtualScrollLoading
structural directive.
For accessibility, ensure that you apply an appropriate role to the ux-virtual-scroll
element and its
children. In this example, role="list"
and role="listitem"
are used respectively. On the
cells, specify aria-posinset
to indicate the position of the item in the overall collection, and
aria-setsize
to specify the total number of items if known (use the value -1
otherwise).
Finally, the example shows use of
LiveAnnouncer
to announce the
start and end of the loading period.
The following attributes can be used to customize the component:
.complete()
function should be called on the observable to prevent the component from trying to load any additional items. If you want to reset the list
simply create a new subject instance and the list will remove all current items and request the first page of data.
true
the next page of data will be requested when the scrollbar nears the end of the list. If false
a "Load More"
button will be displayed at the end of the list allowing the user to request additional items by clicking it.
The following code can be used to create the example above:


A channel to discuss trading. For useful links and more info click the pinned messages to the right.
100 messages
Before 05-Dec-19 12:00 AM
Caglio07-Aug-19 02:02 PM
0.5 easily
bu we started from 0.5
so dead cat bounce
wouldnt be dead cat bounce
Sherdogz07-Aug-19 02:02 PM
What up with pirate... Lucky i didnt buy much
Caglio07-Aug-19 02:02 PM
if we get back on price we had
so 0.40
altcoinist07-Aug-19 02:02 PM
I don't think so 0.70-0.75
Caglio07-Aug-19 02:02 PM
well only shittiest thing than komodo
are komodo eco system coins
here u lost only 900%
ther eu lost even more
Sherdogz07-Aug-19 02:03 PM
Caglio07-Aug-19 02:03 PM
but buy more now
its bargain
you paid 6.5$ before to go to 0
now you will pay only 80 cents
totally worth it
Markus07-Aug-19 02:04 PM
only shit thing is anywhere u can buy kmd with fiat kinda take 2 years to verify transactions
thats why i hate to buy alts with fiat
so i always buy btc then alts
Caglio07-Aug-19 02:04 PM
maybe the reasons is noone knows about this shitcoin ?
And why is that ?
maybe cos of the worst marketing ever ?
hm ?
CHMEX07-Aug-19 02:05 PM
Btc dominance close to 70%
Markus07-Aug-19 02:05 PM
all alts getting rekt so kmd is no different
altcoinist07-Aug-19 02:05 PM
Btc dominance close to 70%
CHMEX07-Aug-19 02:05 PM
Maybe it nees another 20 points up
Markus07-Aug-19 02:05 PM
Eth is soon making a new lower low since 2017
ultimate rekt
CHMEX07-Aug-19 02:05 PM
@altcoinist bot?
altcoinist07-Aug-19 02:06 PM
no
Markus07-Aug-19 02:06 PM
would be fun to see btc dominance 80-90%
alts market cap would be like nothing
xD
coingirl8707-Aug-19 02:07 PM
What differences kmd to tezos or lisk? Both have a very good performance in altcoin bear market...how you explain it?
altcoinist07-Aug-19 02:07 PM
tezos got listed on coinbase
Acura07-Aug-19 02:08 PM
These questions...
Caglio07-Aug-19 02:08 PM
Why did tezos got listen on coinbase
Is it possible due better marketing ?
 You guys tell me all the time ..."bear market" "all alts dump" but these 2 coins not fall...i only want to know why and you fucked me up(edited)
Caglio07-Aug-19 02:11 PM
then btc goes down, guess whose fault it is
btcs
Btc goes sideways
this time its santas fault for kmd dying
Kill the Santa
Kmd hits milestone of 2500sats
BUY BAGS 5% SAFE EARN
Yes please, put the home on a bank loan and invest in KMD
new rebrand comes
this time we even have a support via e mail
Buddz199307-Aug-19 02:12 PM
LOL
Caglio I still didn't get if your trolling or being serious
Caglio07-Aug-19 02:12 PM
Ideas by nature did a good job, their main man got paid by supernet dividends
He spents 2 week in Aruba
Buddz199307-Aug-19 02:13 PM
both I guess(edited)
Caglio07-Aug-19 02:13 PM
Meanwhile I stop coming online cos I can only get over wi fi
And I dont have a home anymore
actionslacks07-Aug-19 02:13 PM
another beautiful morning in kmd land
Caglio07-Aug-19 02:13 PM
I am living in a tent, stealing wi fi from a local store
Whose fault is it now ?
Boogieman ?
PHBA206107-Aug-19 02:13 PM
on consensus level, I believe both Tezos & Lisk have DPoS , instead of PoW
Buddz199307-Aug-19 02:13 PM
I'ts yours for investing too much
Caglio07-Aug-19 02:13 PM
Not seeing exit signs ?
Buddz199307-Aug-19 02:13 PM
Caglio07-Aug-19 02:13 PM
Ofc its mine ( :
I agree on that
But lets buy now
Superb chance
We cannot go lower
Buddz199307-Aug-19 02:14 PM
but we can
Caglio07-Aug-19 02:14 PM
I think that too
But most people here dont
Buddz199307-Aug-19 02:14 PM
we are bellow 90 cents
if we close like that on the daily
support is broken
I haven't seen Komodo ranking 71 in a while
Lisk and ARK also have DPOS
Caglio07-Aug-19 02:16 PM
I really think we shall invest more in this coin
Cos its osmething world need
Also invest as much as you can in ecosystem projects


AP Top International News at 7:01 a.m. EST
UK's Labour promises radical change if it wins election
Pope in Thailand calls for action to protect women, children
Hong Kong campus drama persists as city gears for elections
China demands Trump veto bills on Hong Kong
Victims' lawyer: Prince Andrew must talk to US prosecutors
Survey: About 1 in 4 Europeans hold anti-Semitic beliefs
Activists: Iran conservationists get prison time amid unrest
British Airways says flights disrupted by ‘technical issue'
The Latest: Spanish ship rescues 73 migrants
Ex-Scottish leader Alex Salmond denies sex assault charges
Copyright 2019 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.


The Bio Roll can be installed during the frontend installation step of your cluster (refer to section 1.2 of the Rocks usersguide). If this method is chosen, then the Bio Roll is added to a frontend installation in exactly the same manner as the required OS Roll. Specifically, after the OS Roll is added, the installer will once again ask if you have a Roll (see below). Select 'Yes' and insert the Bio Roll.
The Bio Roll can also be added to running frontend. Here's the procedure for an x86_64 cluster (for an i386 cluster, substitute x86_64 with i386).
# cd /tmp # wget http://www.rocksclusters.org/ftp-site/pub/rocks/extras/4.2/x86_64/bio-4.2-0.x86_64.disk1.iso # mount -o loop bio-4.2-0.x86_64.disk1.iso /mnt/cdrom # cd /home/install # rocks-dist --install copyroll # umount /mnt/cdrom # rocks-dist dist # kroll bio > /tmp/bio-install.sh # sh /tmp/bio-install.sh |
Now install your compute nodes (or re-install your compute nodes if you added the roll to a running system).


Assignment 1 by Daniel Renteria
AME 220 Fall 2015
swing
easeInQuad
easeOutQuad
easeInOutQuad
easeInCubic
easeOutCubic
easeInOutCubic
easeInQuart
easeOutQuart
easeInOutQuart
easeInQuint
easeOutQuint
easeInOutQuint
easeInSine
easeOutSine
easeInOutSine
easeInExpo
easeOutExpo
easeInOutExpo
easeInCirc
easeOutCirc
easeInOutCirc
easeInElastic
easeOutElastic
easeInOutElastic
easeInBack
easeOutBack
easeInOutBack
easeInBounce
easeOutBounce


Your team code is NOT WORKING. Share with your friends or join their team below.
Already signed up? Sign in here!


Hello World! Today is my day, even if it's just a incubation project. No, it is a Team. Love the world, Humble & Respect & Trust Coming is coming


GenICam feature: Enumeration entry. More...
Public Member Functions | |
| PvResult | GetValue (int64_t &aValue) const |
| Get the enumeration entry's value. More... | |
| PvResult | GetName (PvString &aName) const |
| Get the enumeration entry's name. More... | |
| PvResult | GetToolTip (PvString &aToolTip) const |
| Get a short description of the enum entry. More... | |
| PvResult | GetDescription (PvString &aDescription) const |
| Get a longer description of the enum entry. More... | |
| PvResult | GetVisibility (PvGenVisibility &aVisibility) const |
| Get the enumeration entry's current visibility level. More... | |
| PvResult | GetDisplayName (PvString &aDisplayName) const |
| Get the enum entry's display name. More... | |
| PvResult | GetNameSpace (PvGenNameSpace &aNameSpace) const |
| Get the enum enty's name space. More... | |
| PvResult | IsVisible (PvGenVisibility aVisibility, bool &aVisible) const |
| Test if the enumeration entry is above a specific visibilty level. More... | |
| PvResult | IsAvailable (bool &aAvailable) const |
| Test if the enumeration entry is currently available. More... | |
| bool | IsVisible (PvGenVisibility aVisibility) const |
| Test if the parameter is visible at the specified visibilty level. More... | |
| bool | IsAvailable () const |
| Test if the enumeration entry is currently available. More... | |
Protected Member Functions | |
| PvGenEnumEntry () | |
| Constructor. | |
| virtual | ~PvGenEnumEntry () |
| Destructor. | |
GenICam feature: Enumeration entry.
To use PvGenEnumEntry, see PvGenEnum.
Get a longer description of the enum entry.
| [out] | aDescription | A longer description of the enum entry. |
Get the enum entry's display name.
| [out] | aDisplayName | The enum entry's display name; a name that can be used to identify an enum entry in a user-interface context instead of GetName. |
Get the enumeration entry's name.
| [out] | aName | The enumeration entry's name |
| PvResult PvGenEnumEntry::GetNameSpace | ( | PvGenNameSpace & | aNameSpace | ) | const |
Get the enum enty's name space.
| [out] | aNameSpace | The enum entry's name space. |
Get a short description of the enum entry.
| [out] | aToolTip | A short description of the enum entry. |
| PvResult PvGenEnumEntry::GetValue | ( | int64_t & | aValue | ) | const |
Get the enumeration entry's value.
| [out] | aValue | The enumeration entry's value. |
| PvResult PvGenEnumEntry::GetVisibility | ( | PvGenVisibility & | aVisibility | ) | const |
Get the enumeration entry's current visibility level.
See PvGenParameter::GetVisibility.
| [out] | aVisibility | See PvGenParameter::GetVisibility. |
| PvResult PvGenEnumEntry::IsAvailable | ( | bool & | aAvailable | ) | const |
Test if the enumeration entry is currently available.
See PvGenParameter::IsAvailable.
| [out] | aAvailable | See PvGenParameter::IsAvailable. |
| bool PvGenEnumEntry::IsAvailable | ( | ) | const |
Test if the enumeration entry is currently available.
| PvResult PvGenEnumEntry::IsVisible | ( | PvGenVisibility | aCurrentVisibility, |
| bool & | aVisible | ||
| ) | const |
Test if the enumeration entry is above a specific visibilty level.
See PvGenParameter::IsVisible.
| [in] | aCurrentVisibility | See PvGenParameter::IsVisible. |
| [out] | aVisible | See PvGenParameter::IsVisible. |
| bool PvGenEnumEntry::IsVisible | ( | PvGenVisibility | aCurrentVisibility | ) | const |
Test if the parameter is visible at the specified visibilty level.
| [in] | aCurrentVisibility | See PvGenParameter::IsVisible. |
Copyright (c) 2002-2015 Pleora Technologies Inc.
www.pleora.com


Business Process and Workflow Analysis
In this section we will look at information, documents, people, roles, and business rules and their importance in process analysis. We will learn how to understand the different business processes involved and how to perform workflow analysis on these processes. Also, attention will be given to rolling out change initiatives within an organization and the possible hurdles and issues that may be encountered.


§412:1-101 Purpose. This chapter shall be liberally construed and applied to promote its underlying purposes and policies, which are as follows:
(1) To simplify, clarify, and modernize the laws concerning the regulation, organization, management, and activities of financial institutions in this State; and
(2) To provide a comprehensive set of laws applicable to financial institutions. [L 1993, c 350, pt of §1]


{{#markdown}} For information on JavaScript-powered drop-down menus, [consult the Foundation documentation](http://foundation.zurb.com/sites/docs/dropdown-menu.html). {{/markdown}}


To see the documentation click here To see previous example (JQuery AJAX) click here To see the source files of this example click here


Proposed Feedback
Students are expected to learn the subject swiftly as the contents are in conjunction with the syllabus of form 5 English, and also, able to answer 80% of the questions provided during evaluation correctly within 30 minutes.
Students are expected to learn the subject swiftly as the contents are in conjunction with the syllabus of form 5 English, and also, able to answer 80% of the questions provided during evaluation correctly within 30 minutes.


Children's literature is for readers and listeners up to about age 12. It is often illustrated. The term is used in senses that sometimes exclude young-adult fiction, comic books, or other genres. Books specifically for children existed at least several hundred years ago.


--- title: HTML5 video without JavaScript excerpt: 'Mozilla''s reply on using HTML5 video without using JavaScript: http://tinyurl.com/l9c772 2009-06-23' date: '2009-06-23 18:28:57 +0200' date_gmt: '2009-06-23 16:28:57 +0200' categories: - Webdev ---
Mozilla's reply on using HTML5 video without using JavaScript: http://tinyurl.com/l9c772 2009-06-23


Portugal team trains before travelling to Luxembourg
by TPN/LusaPortugal’s national football team is training on Friday in the Algarve, before travelling to Luxembourg, where they are to play their last UEFA EURO2020 qualifier on Sunday.
Hours after beating Lithuania (6-0) at the Algarve Stadium on Thursday, Portugal was training at the hotel where they are expected to spare the starters from Thursday's triumph and then travel to Luxembourg.
With a Group B encounter to play, Ukraine, who have already qualified, lead with 19 points, five more than Portugal and six more than Serbia.
In their final matchday, Portugal plays against Luxembourg, while Serbia host Ukraine, having to win or wait until Serbs do not win to secure second place and qualification.