text:
CloudControl Documentation
Documentation News
Created by Jereme Conley, last modified on Mar 20, 2020
MCP 2.0
Cloud Servers MCP 2.0
Introduction to Cloud Server Snapshots
Provides an overview of the Cloud Server Snapshot feature available in some MCP 2.0 locations. To identify if this feature is currently available in a particular MCP 2.0 location, see How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location.
Cloud Server Snapshots provides a hypervisor-enabled backup solution that shares many of the characteristics of traditional VM snapshots. Cloud Server Snapshots provides the user the benefits of a backup solution which can be enabled without loading any software agents into a Cloud Server, and at the same time provides the ability to instantly restore to a known-good previous state of a Cloud Server in circumstances such as the need to recover quickly from a failed change. Cloud Server Snapshots is a feature that can be enabled for a given Cloud Server. Once the feature is enabled, the system takes periodic "snapshots" of the Cloud Server. Each snapshot is a copy of a Cloud Server's hardware and storage state at a given point in time. Cloud Server Snapshots include the current state of all components of the Cloud Server, including server hardware configuration elements (Number of CPU, CPU Speed, RAM, Network Adapters, Storage Controllers, etc.) as well as the state of all local storage disks.
There are two types of Snapshots:
System Generated Snapshot - The system takes a daily "system-generated" snapshot periodically during a pre-determined window. The pre-determined window is chosen by the user when the Cloud Server Snapshot is enabled. When provisioning the service, users will choose an available window from a pool of windows made available on a first-come / first-served basis. Users cannot delete the system generated snapshots. The retention of System Generated Snapshots is based on the Snapshot Plan. See the Cloud Server Snapshot Plans section below for more details
Manual Snapshots (User Initiated) - Manual snapshots allow users to take a snapshot of a Cloud Server outside the time of their weekly window. For example, a user preparing for a maintenance event on a Cloud Server might take a manual snapshot prior to the maintenance to have a copy of the server state. Users can request a manual snapshot at any time but can only have a single snapshot in progress at any one time for each Cloud Server. Unlike system-generated Snapshots, manual Snapshots can be deleted. Manual Snapshots are automatically deleted by the system after 14 days. See How to Take a Manual Cloud Server Snapshot and How to View and Manage Snapshots for a Cloud Server
Once a Snapshot is created, the snapshot is stored for a given period of time (which varies depending on the snapshot "service plan" and the type of snapshot - see Cloud Server Snapshot Plans section below). So long as the Snapshot is stored, users can create new Cloud Server(s) from those Cloud Server Snapshots. The new server or servers have the same hardware configuration and storage state as the historical snapshot, giving users the ability to "roll back" to a previous state, for example back to a time before a failure or fault occurred.
Cloud Server Snapshots are useful for a variety of use cases such as:
Creating a snapshot for "rollback" or protection prior to initiating maintenance or making major changes to a server.
Recovering to a historical state after corruption of a server
Review of historical states to recover lost files or to identify server state
These are simply a subset of potential ways the system can be used. There are too many potential use cases and variables to provide "best practices" around all the options, but it is helpful to provide a sample use case to get a better feel of how the Cloud Snapshot functions tie together.
User initiates a Manual Snapshot per How to Take a Manual Cloud Server Snapshot
User can identify Snapshot is in progress as described in How to Take a Manual Cloud Server Snapshot
User ensures Manual Snapshot successfully completed by checking the snapshot list per How to View and Manage Snapshots for a Cloud Server
This step is important since it is possible for a Manual Snapshot to fail!
User performs the upgrade or change to the server.
User tests new application and determines something is not working correctly
User creates a new Snapshot Preview Server from the Manual Snapshot created prior to the event per How to Create a Snapshot Preview Server from a Local Snapshot
User may then choose to:
Access the newly created server via Console and identify the information/configurations from the server prior to the event
Copy information or configurations from the newly created Snapshot Preview server back to the server which was modified in order to correct information.
Note this may involve re-IP'ing and reconnecting NICs such that the servers can communicate without an IP conflict
Alternately, the user may choose to power down or disconnect the NICs on the original server and begin using the Snapshot Preview server to replace the original, since it represents the same state as prior to the change. In this case:
User would want to migrate the Snapshot Preview server to Normal per How to Migrate a "Snapshot Preview" Server to a Normal Cloud Server.
User may want to re-enable add-on services on the new server.
User may want to maintain the "original" server for troubleshooting to determine what may have caused the upgrade to fail.
For additional redundancy, you can enable Snapshot Replication and the system will replicate System Snapshots to an available secondary location within the same Geographic Location.
In the event of a Data Center failure, you can restore Snapshots to the secondary location from the Replicated Snapshot
Cloud Server Snapshot Plans
We currently offer three Cloud Server Snapshot plans: One Month, Three Month, and Twelve Month. All three Snapshot plans offer the same Cloud Server Snapshot features:
Servers will have a Daily "System" snapshot taken during a user-specified UTC window
Users can choose from a pool of available UTC windows, broken into 12 two-hour times during the day.
Note that some daily UTC windows may be identified as "OVERLAPS_WITH_MAINTENANCE". This means that time overlaps with one of our Operational maintenance windows on a particular day of the week. The System does not block a snapshot from occurring during this timeframe, however, if Operations is performing hypervisor or snapshot maintenance in the location during the selected time, the System snapshot may be unsuccessful on that particular day. Such failed system snapshots are visible as described in How to View and Manage Snapshots for a Cloud Server.
In order for the System to determine whether a System snapshot failed:
CloudControl checks once an hour for the list of all snapshots, including System ones
If CloudControl does not identify a System snapshot within 12 hours of the scheduled window, it inserts a failed record with a 31-day expiry time
However, we have seen some cases where the underlying infrastructure takes more than 12 hours to complete the scheduled snapshot, in that case, the system will show both the failed record and the successful one with the same Snapshot start time.
Users can take Manual Snapshots "on-demand" in addition to scheduled System snapshots
For details, see the Manual Snapshots section below
Users can choose to have their System Snapshots replicated to another location (where available)
For details, see the Snapshot Replication section below
Users can define local OS-level scripts that run before and after the vSphere snapshot used during the snapshot process
For details, see the Pre and Post Snapshot Scripts Feature section below.
Users can create a new Cloud Server from a Snapshot at any time
For details, see the Using Cloud Server Snapshots to Create a New Cloud Server section below
Users can restore files or directories from a Local Snapshot directly onto the protected server
For details, see the Performing a File or Directory Restore from a Cloud Server Snapshot section below
The difference between the plans relates to the retention period for these system snapshots. Each plan offers a different retention period:
System Snapshot Retention Period
Retention Notes
ONE_MONTH One Month: 7d-4w
Daily - 7 days
Weekly - 31 Days
Every 7 Days, one daily Snapshot will be "promoted" to a weekly Snapshot with a 31 day retention period.
THREE_MONTH Three Month: 14d-12w
Daily - 14 Days
TWELVE_MONTH Twelve Month: 31d-12w-12m
Monthly - 365 days
Every 7 days, one daily snapshot will be "promoted" to a weekly Snapshot with a 90 Day retention Period,
Every 30 days, one weekly snapshot will be "promoted" to a monthly Snapshot with 365 Day retention period.
Details on Previously Available Plans
Prior to October 24, 2019, the system offered Essentials and Advanced Cloud Server Snapshot plans. For details on these plans and the end-of-sale details, see October 2019 Changes to Cloud Server Snapshot Plans.
Enabling the Cloud Server Snapshot feature
The Cloud Server Snapshot feature is not available in all locations. To identify if it is available in a given location, and to see system constraints around the service, see How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location.
Where available, users can enable the service as described in How to Enable Cloud Server Snapshots on a Server. A few notes on this:
All Snapshot Window times are listed in UTC, so the local time may change with daylight savings time, where applicable. For example, if the Server is located in the NA9 location which follows US-Eastern Time Zone and you pick the 02:00 UTC window, the Snapshot may be taken at either 9:00 PM or 10:00 PM local time depending on whether the location is currently following daylight savings time. The UI will show this conversion based on the current daylight savings time status.
There is a maximum number of total servers that can be assigned to each window in a given location. When all of these "slots" are used, the system will not allow additional servers to choose that window. Slots may become available again in the future if a Cloud Server using the slot disables the feature or if the infrastructure is expanded to provide additional slots. The UI will display the current number of available slots as described in How to Enable Cloud Server Snapshots on a Server in order to allow you to ensure there are enough slots to support multiple servers for which you want to share the same window.
The initial System Generated snapshot taken after a Cloud Server is enabled can be a long-running process taking hours (especially if the amount of local storage is large). This is true only of the initial System snapshot - after the initial System snapshot is taken, any future Manual or System snapshots are much quicker as the system only needs to identify changes since the previous snapshot. This means that even if you choose to Create Initial Snapshot immediately as described in How to Enable Cloud Server Snapshots on a Server, this initial Manual Snapshot will also be a long-running process and you will be prevented from performing a number of Server actions while a Manual Snapshot is in progress, as detailed in the Restrictions While Snapshots are Taking Place section below.
There is a limitation on the maximum amount of storage that can be attached to a Cloud Server in order to enable the Cloud Server Snapshot feature. For more information see Maximum Total Snapshot Storage on How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
Some Server Configurations Not Supported or Are Not Fully Restored
Some Cloud Server hardware configurations are incompatible with the Cloud Server Snapshot Service. For example, Cloud Servers with ISO files attached to CD-ROM cannot be enabled for Snapshots. Similarly, although Snapshot enablement of servers with "empty" SATA Controllers without ISO or Local Drives is allowed, users should be aware that when creating a "Snapshot Preview" server as described in How to Create a Snapshot Preview Server from a Local Snapshot, the SATA controller will not appear as part of the Snapshot Preview server.
For complete details on all unusual configurations, see preconditions in How to Enable Cloud Server Snapshots on a Server
Users can switch between Snapshot plans. For instructions on switching plans, see How to View and Manage Snapshots for a Cloud Server.
Snapshot Replication Feature
Snapshot Replication allows you to replicate System Snapshots to a secondary site in the same Geographic Region. Only System-Generated Snapshots can be replicated (not Manual Snapshots). Replication is not available in all Snapshot locations. To identify if it is available and to which locations replications can be made, see How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location.
Once Snapshot Replication has been enabled on a Cloud Server, It can take anywhere from 30 minutes to several hours for the Snapshots to be replicated to the secondary location. Replicated system snapshots are retained for the same retention time as Primary (Source) snapshots. In the secondary location, you will incur "Replicated Snapshot Hours" based on your Snapshot plan once replication is enabled.
Snapshots are replicated asynchronously to the replicated location. Once the snapshot is replicated, you will be able to create Snapshot Preview servers in the secondary location using the Replicated Snapshots. However, there are some differences in the process when creating a Snapshot Preview Server from a Replicated Snapshot:
You will need to specify a unique VLAN to which to connect each NIC on the Server. This means that the secondary location must have the same number of available VLANs as the Network Domain of the Source server.
If a Disk speed is not available in the replicated location, the Disk Speed will automatically be changed to the default Disk Speed for that Data Center Location, which in currently always the Standard Disk Speed.
For details, see:
How to Manage Snapshot Replication on a Cloud Server
How to Create a Snapshot Preview Server from a Replicated Snapshot
Pre and Post Snapshot Scripts Feature
The Pre and Post Snapshots feature can help ensure your snapshots can be used to create a usable server. At a technical level, taking a Cloud Server Snapshot is a two-step process:
The System first uses VMWare's native Virtual Machine Snapshot capability to take a local snapshot of the server. This process usually lasts a few seconds.
The system then offloads a "copy" of that Virtual Machine Snapshot to the external snapshot infrastructure where it is stored. This is a longer-running process, especially on the initial Snapshot.
Cloud Server Snapshots can be created either while a server is running or in a stopped state. However, the Virtual Machine Snapshot performed in step #1 is taken with the Quiesce and Memory settings set to OFF, so there are no actions taken within the Guest OS to prepare for the Virtual Machine Snapshot if the server is running. To address this limitation, the system supports the ability to configure the system to run a local script on the Cloud Server prior to taking the Virtual Machine Snapshot and to run another local script and immediately after the Virtual Machine Snapshot has been taken. Users can opt to run a Pre-Snapshot Script, a Post-Snapshot script, or both a Pre and Post Snapshot script.
Once this feature is enabled, the system will attempt to run these scripts on all Snapshots (Manual and System) for that Cloud Server. Pre and/or Post Snapshot scripts can be enabled when a Cloud Server is initially enabled for Snapshots or added on to an existing Snapshot-enabled Cloud Server. Users are required to provide Server credentials, file/path name for the script to be run, along with additional parameters when enabling this feature. Note there are limitations on supported OS and VMware Tools must be installed and running in order to use the feature. For details, see:
How to Set Pre and Post Snapshot Scripts on a Cloud Server
Manual Snapshot Feature
The Manual Snapshot function allows users to take a snapshot at any time outside the time of their weekly window as described in How to Take a Manual Cloud Server Snapshot.
The maximum number of Manual snapshots that can be stored on can be identified as described in How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location. Users at the limit can delete a manual snapshot at any time in order to have the ability to generate a new Manual Snapshot
NOTE: As of October 8, 2019, the limit is 5 Manual Snapshots per server in all locations.
Manual Snapshots are automatically deleted by the system after the Manual Snapshot Retention period is listed in the Data Center Specifications section of the Data Center Dashboard. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location.
NOTE: As of October 8, 2019, the retention period is 14 days in all locations.
Cloud Server System Snapshot Archiving
System Snapshot Archival In Process of Being Rolled Out
We are in the process of rolling out the archival of system snapshots as described below. It is expected that most locations with Cloud Server Snapshots will eventually have archiving enabled. Announcements will be made on the status page before archiving is enabled, but users should be aware that even if a location currently does not show archiving is in place, it may be added later.
In data centers where Snapshot Archiving has been enabled after a System Snapshot has been successfully taken it will be moved from local Snapshot storage infrastructure to Archived Storage infrastructure after a certain number of days. Manual Snapshots are not archived. The time between the successful completion of the System Snapshot and when it is moved to Archived Storage can vary by Data Center. You can identify whether snapshot archival is currently being used and the specific archival policy by looking at the Data Center Specifications section of the Data Center Dashboard as described in How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location. Specifically, see the sections "Snapshot Archive Enabled" (True or False) and "Snapshot Retention Before Archive (Days)". If replication is enabled in a location, the replication policy applies to all System Snapshots stored in that location - including if that location is used as a Replication Target location by a server in another data center location.
You can identify if a System Snapshot is currently archived when viewing the list of Snapshots. The Snapshot tab of the Server dashboard will display the Archive Status of each Snapshot, indicating whether it is archived, available locally or is in the process of being downloaded from the archive.
For more details, see Navigating the Server Dashboard
Creating a Snapshot Preview Server from a Snapshot that currently resides on Archived Storage will take significantly longer than creating one from a Snapshot that is not archived as the process requires an extra step where the Snapshot is first copied ("rehydrated") from the Archival Storage infrastructure to local Snapshot storage infrastructure before a Snapshot Preview Server can be created. The timeframe to rehydrate a Snapshot depends on a number of factors, including the size of the snapshot, connectivity to the archival storage, and overall load on the Snapshot infrastructure. Be sure to allow for this extra time if you plan to create a Snapshot Preview Server from an archived Snapshot. Once successfully rehydrated from the archival storage, a Snapshot will reside on the local storage for up to 24 hours. It is important to note that only one archived Snapshot can be brought back to local storage (re-hydrated) at a time for a given Cloud Server.
File or Directory Restore operations do not require the rehydration step but may also take longer if restoring from an archived System Snapshot. See How to Restore a File or Directory from a Cloud Server Snapshot to the Cloud Server.
Snapshot Long-Term Snapshot Retention Feature
Many organizations have a need to retain backups for an extended period of time to meet compliance requirements, in some cases for up to 7 years. Snapshot Long-Term Retention is an add-on feature of Cloud Server Snapshot Service that allows users to specify that they want to keep a System Snapshot for a longer period than what is allowed under the Snapshot Service Plans (i.e. longer than 1 year). This feature provides a solution for Cloud Server Snapshots which is not tied to proprietary vendor formats. Long-Term Retention Images are stored using standard vSphere datastores, meaning that if the underlying technology of Cloud Server Snapshots is changed, Long-term Retention Images will not be "stuck" in a legacy vendor format.
For more information on Long-Term Snapshot Replication, see Introduction to Cloud Server Snapshot Long-Term Retention Images
Application-Specific Considerations when Configuring Snapshot Service
Since there is no guarantee write state of the server at the time of snapshot, some applications such as databases and Active Directory servers will need additional configuration in order to ensure a restorable state based on the snapshot. Here are overview of the approach to address common scenarios:
Using Windows Server Backup to Protect Active Directory (AD) with the Cloud Server Snapshot Feature
Using Volume Shadow Copy Service (VSS) to Protect SQL Server with the Cloud Server Snapshot Feature
Using FLUSH TABLES WITH READ LOCK to Protect MySQL databases with the Cloud Server Snapshots Feature
Viewing and Understanding Cloud Server Snapshots
Once enabled, you can view the Cloud Server Snapshots associated with a server as described in How to View and Manage Snapshots for a Cloud Server. The View Snapshots function allows you to view the detailed configuration of the Cloud Server at the time the snapshot was taken, as well as Snapshots that have been replicated to a secondary location.
Cloud Server Snapshot Consistency Levels
VMWare Tools Required for Some Consistency Levels
Note that the "consistency level" provided by the Cloud Server Snapshot service varies depending on:
Whether VMware Tools is installed and Running
Operating System capabilities
When a Cloud Server Snapshot is taken, it is possible that the system, at that moment, is making changes to files on the disk at the time of the snapshot. It's also possible that the application is in the middle of a thread or transaction where it is making changes across multiple files or transactions. To avoid problems when creating a Snapshot Preview server from a snapshot, you want some level of "consistency" in the snapshot - avoiding complications where the file state is "incomplete".
The Cloud Snapshot Service supports multiple levels of consistency depending on the server and application configuration:
INCONSISTENT - Inconsistent means the disk state is not guaranteed to be consistent on any level. This level occurs when neither VMware Tools nor Open VM Tools is running on the Cloud Server at the time of the snapshot. This includes times when the server is in a stopped state since Tools isn't running. The system requires VMware Tools or Open VM Tools to be running in order to have visibility into the Operating System, which is needed to identify or ensure any information about consistency.
CRASH_CONSISTENT - Crash Consistent means the system was able to confirm that all the data captured on the local disks is representative of the state of the storage as of the start time of the snapshot. This means the OS will boot but application data cannot be guaranteed. This level can be provided when Open VM Tools is running on the Cloud Server at the time of the snapshot or the server is running an out-of-date version of VMware Tools. This is currently the highest level of guaranteed consistency supported with servers running Open VM Tools.
FILE_SYSTEM_CONSISTENT - This indicates the file system state is consistent as of the start time of the snapshot, meaning that any writes to specific files are complete. The level can be provided when VMware Tools is up-to-date and the OS does not support application consistency.
APP_CONSISTENT - This value is returned for some LINUX OS variants but effectively means the same thing as FILE_SYSTEM_CONSISTENT
VSS_CONSISTENT (NOT YET AVAILABLE)- With a VSS_CONSISTENT snapshot, you can ensure some level of application consistency for applications taking advantage of Microsoft's Volume Shadow Copy Service as the service ensures the application is in a consistent state when the snapshot is taken. Note that VSS_CONSISTENT is not a guarantee of full application consistency. It merely indicates the snapshot was consistent with the Microsoft's Volume Shadow Copy Service
Support for VSS Consistent Snapshots is not yet available but is expected to be added in the future. It will require a special software agent that interfaces with the Cloud Server Snapshot service.
Snapshot Index State
When a Snapshot is initiated (whether Manual or System), the Snapshot will be indexed based on the state of the snapshot. In order for a snapshot to be used for a file or directory restore operation, the Index State must be Valid. There are 3 possible index states:
Valid – This indicates that indexing has completed successfully, and the Snapshot can be used for File or Directory restores
Note: If the Index State is Valid, the Index State icon will be black . Hovering your mouse over the icon will indicate that the state is Valid.
Incomplete – This indicates that the indexing has not yet completed. You cannot use a Snapshot in this state for a File or Directory restore at this time.
Note: The system automatically sets the index state of Snapshots to this value during the Snapshot process. It may take some time to update, depending on the size and complexity of the file and directory structure
Note: If the Index State is Incomplete, the Index State icon will be gray . Hovering your mouse over the icon will indicate whether the state is Incomplete or Invalid
Invalid – Snapshots cannot be used for file or directory restores. This could be because of any of the following reasons:
Indexing has failed
The Operating System could be unsupported
The file system on the Operating System could be unsupported
Note: If the Index State is Invalid, the Index State icon will be red . Hovering your mouse over the icon will indicate that the state is Invalid.
The index state of a Snapshot can be viewed in the Snapshot tab of the Server Dashboard. See Navigating the Server Dashboard
Using Cloud Server Snapshots to Create a New Cloud Server
The purpose of having Cloud Server Snapshots is to either get access to the data from a historical snapshot or to create a replica of the server based on a historical snapshot. This section explains how to create a replica of the server. You can also restore a directory onto the protected server as described in the next section Performing a File or Directory Restore from a Cloud Server Snapshot.
Creating a new Cloud Server from a Snapshot involves two phases: Creating a Snapshot Preview Server and Migration of a Snapshot Preview Server to Production Disk Speeds. Details on each phase are described below.
Creating a Snapshot Preview Server
The first step in the process is to create a "Snapshot Preview" server. The process differs slightly depending on whether you are creating a server from a "local" snapshot in the same data center as the original server or whether you are creating it from a "replicated" snapshot in a different data center. When using a local snapshot, the Snapshot Preview server is created on the same NIC VLANs as the original server. When using a replicated Snapshot, you must define the VLANs for each NIC.
For complete details, see:
How to Create a Snapshot Preview Server from a Local Snapshot
In either case, this function allows you to bring up a new server that matches the state of the server represented by the start time of a successful snapshot. The goal is to allow you to quickly assess the snapshot to ensure it contains the data and server state you are looking for as well as to gain quick access to data and potentially replace the original server in production using this newly created server. Note that this process will take longer if Archive is enabled for the Location and the Snapshot chosen resides are Archive Storage (see Snapshot Archiving section above)
A "Snapshot Preview" server has the same virtual CPU and RAM performance as the original server and runs on a physical ESXi host in the production infrastructure. However, the "local storage" (i.e. disks) for a Snapshot Preview server is not running on the production storage infrastructure. Instead, it is running on disks presented by the snapshot service itself. Snapshot Preview Servers are indicated by the Snapshot Preview Server icon. You can hover your mouse over the icon to see that the Server is in Snapshot Preview mode:
Performance and Restrictions of Snapshot Preview Servers
While in Snapshot Preview mode, the server has some performance limitations and some other restrictions:
Since the disk is being presented by the snapshot infrastructure and mounted to the ESX hypervisor via NFS, the server will not achieve the I/O performance indicated associated with the "disk speed" of the local storage. To achieve normal performance, you need to initiate a "migration" to the normal storage infrastructure as described in the next step.
The "Snapshot Preview" server is tied to a specific physical ESXi host. If that physical ESXi host fails, the Snapshot Preview server state will be lost and will not immediately restart on another host as described in What Happens When the Physical Server Hosting my Cloud Server Crashes.
The following server actions are prohibited while the Cloud Server is in Snapshot Preview mode:
Modifications to Storage Controllers or Disks, including:
Add/Remove/Expand Local Disk
Add/Remove SCSI Controller
Change Disk Speed
Change the IOPS value on a variable IOPS disk speed disk
Remove ISO/FLP
Create Server Anti-Affinity Rule using Server
Enabling other CloudControl Services such as Cloud Server Snapshots, Monitoring, or Backup
This also includes a prohibition on creating a Security Group or DRS Consistency Group with a server while it is in "Snapshot Preview" state
Given those limitations (particularly the first two issues), the recommended best practice is to verify that the server represents a snapshot state you are looking for, make any necessary changes to it, and then to migrate the Snapshot Preview server to NORMAL as soon as possible. Users must initiate migration of "Snapshot Preview" Servers to at the Production Disk Speeds as described in the next section within two hours after creation. After two hours, the system will initiate the migration automatically.
Potential Configuration Issues with Snapshot Preview Servers
There are some minor caveats and potential Guest OS configuration issues with Snapshot Preview Server:
When creating a Snapshot Preview from a Local Snapshot, the Snapshot Preview server is provisioned to the same VLANs as the original server. Therefore, it likely has many (if not all) of the same IP addresses as the original server. That means there is a high likelihood of IP conflict if the original server is running. We recommend creating Snapshot Preview Servers with the NICs in a disconnected state and connecting them only after you are sure it will not cause a problem.
For more details on "connected" and "disconnected" NICs, see Introduction to Cloud Server NICs in MCP 2.0
The system will prevent you from creating a Snapshot Preview server if any of the IP addresses from the time of the snapshot are "exclusively reserved". You will need to unreserve the IPs in order to create a Snapshot Preview server as described in How to Unreserve an IPv4 or IPv6 Address.
On UNIX-based Operating Systems, failing to preserve the MAC address means the resulting server will require configuration changes as described in Enabling Network Connectivity to a Snapshot Preview Server using RHEL, CentOS, or Oracle if MAC Addresses Have Changed. However, keeping the MAC Addresses has the potential to cause a MAC address conflict when both the original Server and the Snapshot Preview server are powered on with their NICs connected, so Users should be aware of this possibility and similarly use the disconnected NIC option as described above. See How to Create a Snapshot Preview Server from a Local Snapshot and Introduction to IP Addressing in MCP 2.0 for more details.
Any CD-ROM devices attached to the original Cloud Server as of the time of the snapshot are not restored on the Snapshot Preview server.
Servers with disks on IDE controller will have a new boot order. See Addressing Boot Order Issues with a Snapshot Preview Server with an IDE Disk
If the Cloud Server was using Cloud Backup at the time of the snapshot, the backup agent will still be installed and potentially running on the Snapshot Preview server even though it's not enabled for backups. We recommend disabling the agent so as not to result in the backup agent processing backup requests.
Although Snapshot enablement of servers with "empty" SATA Controllers without ISO or Local Drives is allowed, users should be aware that when creating a "Snapshot Preview", the SATA controller will not appear as part of the Snapshot Preview server.
Migration of a Snapshot Preview Server to Production Disk Speeds
The second step in the process migrates the server's local storage onto the production disk infrastructure. This converts the server to a "normal" Cloud Server free of any performance limitations or restrictions. This is a potentially long-running process depending on the size of the local storage, as the process is the equivalent of initiating a "disk speed" change on all of the local disks attached to the Cloud Server. During this migration, the server will continue to run in the state it was in at the time of the migration. However:
All CloudControl server changes are prohibited during the migration (i.e. the server is in a "Pending Change" state).
This includes the ability to start or stop the server, so ensure you have the server in the desired state prior to migration
However, OS-level and application-level changes can continue to be made while in this state. The prohibition applies only to CloudControl changes to the server.
Until migration is complete, the performance restrictions of a Snapshot Preview continue to apply:
Since at least some disk is being presented by the snapshot infrastructure and mounted to the ESX hypervisor via NFS, the server will not achieve the I/O performance indicated associated with the "disk speed" of the local storage until the migration is complete.
The "Snapshot Preview" server is still tied to a specific physical ESXi host and if that host fails, the Snapshot Preview server will be lost and will not restart on another host.
The server continues to incur normal usage charges except local storage which continues to be reported as Standard Disk Speed under Storage Hours
Once migration is complete, the server acts as a Normal Cloud Server and there are no restrictions on usage or changes. However, remember that the new server is not enabled with services such as Cloud Server Snapshots, Monitoring, etc. so you may want to enable those services on the new server if required.
Migration from a Snapshot Preview to a "Normal" server can be done in one of two ways:
Users can initiate the migration, see How to Migrate a "Snapshot Preview" Server to a Normal Cloud Server
If the server has been in Snapshot Preview for more than two hours, the System will initiate the migration automatically.
System Will Make Three System Initiated Migration Attempts
If the System initiated migration fails, the System will retry the migration. If the migration fails after 3 retries, the System will stop trying to migrate the Server. The Server will remain in Snapshot Preview status but will be returned to a Normal state. At this point the User can either:
Initiate the Migration Manually, see How to Migrate a "Snapshot Preview" Server to a Normal Cloud Server or
Delete the Snapshot Preview Server, see How to Delete a Cloud Server
Performing a File or Directory Restore from a Cloud Server Snapshot
Another feature of Cloud Server Snapshots is the ability for a user to specify a file or file directory from a historical snapshot and have that particular file or directory copied or "restored" back onto the Cloud Server associated with the snapshot. This ability is useful when a single file or directory needs to be restored instead of creating an entirely new Server using Snapshot Preview.
The system will restore the specified file or directory from a source location on the Snapshot to a target location on the parent Cloud Server.
There are several preconditions that must be met in order to successfully perform a File or Directory restore. For a full list of preconditions, as well as instructions on how to use this function, see How to Restore a File or Directory from a Cloud Server Snapshot to the Cloud Server
Note that you cannot perform a File or Directory Restore from a Replicated Snapshot.
Cloud Server Snapshots and Usage Reporting
Enabling Cloud Server Snapshots on a server will cause the server to incur a new (Snapshot Plan) Snapshot Service Hours where (Snapshot Plan) represents either the Snapshot plan was enabled for the Cloud Server. If Snapshot Replication is enabled for a Server, additional usage will appear under (Snapshot Plan) Replicated Snapshot Hours beginning from the time Replication was enabled on the Server. In all cases, the usage charges are based on the aggregate size of all of the local disks attached to the Cloud Server. The charges apply to the total size of the disks, not the amount of local storage actually used by the Operating System becausethe stored snapshot includes the exact state of all local disks (even if unformatted) and any Disks that are replicated to a secondary location.
All Snapshot Service Hours usage is incurred immediately upon service enablement before any snapshots are taken or stored and usage will stop when the service is disabled. Note that disabling Snapshot Replication can take anywhere from 2 to 4 hours andusage will continue to be incurred until Replication is fully disabled. The "(Snapshot Plan) Snapshot Service Hours" and "(Snapshot Plan) Snapshot Hours usage charges are in addition to the normal Economy/Standard/High-Performance usage charges for local disks that are described in Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds.
When a "Snapshot Preview" Cloud Server that is newly created from a Snapshot (Local or Replicated) as described in How to Create a Snapshot Preview Server from a Local Snapshot, the server incurs all local disks as Standard Disk Speed rates ("Storage Hours") while it is in Snapshot Preview mode. Local disks incur normal disk speed usage only after the server is migrated to a "Normal" server as described in How to Migrate a "Snapshot Preview" Server to a Normal Cloud Server.
For more information on Snapshot usage elements, please refer to the Cloud Server Snapshots section of Introduction to Usage Reporting
From a reporting perspective, details of Snapshot Usage (and Replicated Snapshot usage) are contained in the Snapshot Usage report as described in How to Generate a Snapshot Usage Report
Additional Details on Cloud Server Snapshot Service
Restrictions While Snapshots are Taking Place
While snapshots are in progress, you cannot modify any existing disks on the Cloud Server. Therefore:
When taking a Manual Snapshot, the system will prevent you from removing disks, changing disk speeds, and expanding disks until the Manual Snapshot is finished.
If you take these actions while a System Snapshot is occurring:
Attempting to removing a disk or change a disk speed on the Server will fail
Attempting to expand a disk on the Server will cause the System Snapshot to fail
Unfortunately, the system does not provide a real-time view into when a system snapshot is occurring, so the best practice is to avoid such actions during your system window and schedule your system window when such actions are unlikely to occur.
Notes about Snapshot Preview Servers
Remember a Snapshot Preview server is a completely separate Cloud Server from the original server on which the snapshot was created. Changes made on this server are not reflected on the original Cloud Server or vice-versa.
The new server does not have the same services associated with it, so it is not enabled for Monitoring, Backup, Cloud Server Snapshots, or any other services. These will have to be enabled on the new server once it is migrated out of Snapshot Preview as described below.
Snapshot Preview servers incur normal usage for all usage elements, meaning they are "billable" as new servers with the one exception that all local disk is reported as Standard Disk Speed under Storage Hours. For more details, see the Cloud Server Snapshots and Usage Reporting section above
Any Priced Software that was associated with the Cloud Server at the time of the snapshot is inherited by the Snapshot Preview and will incur usage accordingly. For more details on Priced Software, see Introduction to Cloud ("Priced") Software
You can create multiple Snapshot Preview servers from the same Snapshot, and the Snapshot remains available even after the server is migrated to "Normal" as described below.
You can have a maximum of 10 Snapshot Preview servers deployed at one time in a given Data Center.
New Features by Release
Cloud Backup - Introduction
Introducing the New Red Hat Update Infrastructure
Introduction to the Compute Menu
Introduction to the UI
server-mcp2-0
intro-mcp-2-0


text:
//
// Copyright (C) 2005 Andras Varga
// Copyright (C) 2008 Alfonso Ariza
//
// This program is free software; you can redistribute it and/or
// modify it under the terms of the GNU General Public License
// as published by the Free Software Foundation; either version 2
// of the License, or (at your option) any later version.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.
//

#ifndef NS2_MOTION_MOBILITY_H
#define NS2_MOTION_MOBILITY_H

#include "INETDefs.h"

#include "LineSegmentsMobilityBase.h"

/**
 * @brief Uses the ns2 motion native file format. See NED file for more info.
 *
 * @ingroup mobility
 * @author Alfonso Ariza
 */

class Ns2MotionMobility;

/**
 * Represents a ns2 motion file's contents.
 */
class INET_API Ns2MotionFile
{
  public:
    typedef std::vector<double> Line;
    double initial[3];
  protected:
    friend class Ns2MotionMobility;
    typedef std::vector<Line> LineList;
    LineList lines;
};

class INET_API Ns2MotionMobility : public LineSegmentsMobilityBase
{
  protected:
    // state
    unsigned int vecpos;
    Ns2MotionFile *ns2File;
    int nodeId;
    double scrollX;
    double scrollY;

  protected:
    void parseFile(const char *filename);

    /** @brief Initializes mobility model parameters.*/
    virtual void initialize(int stage);

    /** @brief Initializes the position according to the mobility model. */
    virtual void initializePosition();

    /** @brief Overridden from LineSegmentsMobilityBase.*/
    virtual void setTargetPosition();

    /** @brief Overridden from LineSegmentsMobilityBase.*/
    virtual void move();

  public:
    Ns2MotionMobility();

    virtual ~Ns2MotionMobility();
};

#endif

redpajama_set_name: RedPajamaGithub


Experience has suggested that academic scientists can be as 'guilty' as the popular press in generating a 'moral panic' causing mass anxiety and hysteria. Take for example the media reporting of the new variant Creuztfeld-Jacob disease, a very rare yet important cause of dementia (Fitzpatrick, 1996).
How dementia is represented in the media is a good surrogate market of how the issue can be represented in certain segments of the culture of a society (Zeilig, 2014).
According to George, Whitehouse and Ballenger (2011), the concept of dementia, a term which they attribute to Celsus in the first century A.D. — has long carried "social implications for those so diagnosed and has been associated with reduced civilian and legal competence, as well as with entitlement to support and protection.
A range of emotionally charged metaphors about dementia pervades the popular imagination, and these are found in newspaper accounts, political speeches, and in both documentary and feature films. The 'G8 dementia' summit allowed many of these recurrent motifs to resurface unchallenged.
I've been intrigued how the G8 Dementia Summit was covered in the English-speaking media on the web. So I did a Google search for "G8 dementia", on the UK Google site. It only came up with languages in English article, and I included the top 75 search results.
I excluded some search results. I excluded webpages consisting of only videos. Flickr photos or Pinterest boards. I decided to exclude articles less than 100 words long.
The aim of this piece of work was to complete a preliminary exploration of how the #G8dementia summit was reported on the internet in the English language.
The literature in this field is very small, and no study to my knowledge has ever been undertaken for the actual reporting of the G8 dementia summit which was unprecedented.
For the text analysis, done online using this tool, I excluded the author names, titles, location of authorship of the article (e.g. London). also excluded the endings, invariably, "Read more" "You may also like", "You can read more about" and list of other 'links' to look at. I excluded duplicates. Finally, one article which was largely a compilation of tweets was excluded.
Unsurprisingly, the word "dementia" featured 955 times, but encouragingly "people" featured 280 times. I found this quite gratifying as I have just published a book on the rôle of the person and the environment for living well with dementia – though the vast majority of articles did not have wellbeing as their main thrust.
I think the problem in English policy is revealed in the finding that "research" appears 334 times, and yet "wellbeing" is there fewer than eight times. The facts that "data" is used thirty times, with "collaboration" 28 times, hint at the overall drive towards data sharing for the development of cross-country trials and personalised medicine.
There seems to be a greater need for "funding" somewhere, a word used 66 times. There's clearly an "international" focus, a word used 103 times.
The word "carers" was only used thirty times – a bit of a knee in the groin for the caring community?
The term "social care" is used 14 times across the 75 articles, but this is dwarfed by the use of the term "innovation" used 37 times. "Innovation" is of course a key meme of Big Pharma, as demonstrated by this infographic by Eli Lilly, a prominent company in dementia neuropharmacology.
The ideological bias towards the medical model for dementia is reflected in the frequency of the word "disease" or "diseases", totalling 203; "treatment" or "treatments", totalling 91; and "cure" or "cures", totalling 72.
There's clearly a bias towards Alzheimer's disease, in that "Alzheimer" was used 145 times, with the word "vascular" used only six times. Strikingly, no other forms of dementia were mentioned. There are probably about a hundred known forms of diagnoses comprising the dementias, including some very common ones such as "frontotemporal" or "diffuse Lewy Body".
Various authors, including Kate Swaffer who lives with a dementia herself, have often remarked on this bias known in the literature as "Alzheimerisation" (Swaffer, 2012).
"Cameron" is mentioned 60 times, and "Hunt" is mentioned 24 times. "Hughes", as in Jeremy Hughes, CEO of the Alzheimer's Society, is only mentioned 5 times.
It's also interesting to see which other conditions are mentioned alongside dementia in these 75 articles. Only three were, in fact: these are "cancer" (45 times), HIV (25 times) and AIDS (29 times); treating HIV and AIDS as distinct, which is of course is not necessary to do, and there may have been no intention on the part of the journalists to use these words specifically in their narratives.
Thankfully, the usual dramatic terms were not used often.
"It also called on the World Health Organization to identify dementia as "an increasing threat to global health" and to help countries adapt to the dementia timebomb.
The terms "bomb" or "bombs" were only used four times, and encouraging one of these was complaining about in a passage complaining about military metaphors.
The danger of flooding has long been associated with dementia. A 1982 U.K. report was entitled: "The rising tide: Developing services for mental illness in old age" (Arie and Jolley, 1983).
Note Hunt's 'wordie' contains 'heartache', 'threats', 'battle', 'dreading', 'stigma' and 'fight', but also includes 'diagnosis', 'people' and 'research'.
It is indeed fascinating the on-running theme of promoting dementia research in the absence of a context of wellbeing.
David Cameron's 'Wordie' is quite tame.
But the consequences for this media messaging are potentially quite profound.
There is a sample bias introduced with how Google orders its ranking.
Page ranking is not only calculated on the basis of traffic, but also in terms of degree of linkage with other websites.
It is possible that higher ranking articles, particularly online versions of newspaper articles, have a common root such as the Press Association, leading to a lack of independence amongst authors in their coverage of the Summit.
Encouragingly though the frequency of words such as 'timebomb' and 'flood' were not as much as one might have feared, from the (albeit small) literature in this field.
If you assume that the 75 articles form a representative cohort of copy on the G8 dementia summit, the picture presented has a clear emphasis on a magic pharmacological bullet for dementia. The copy represents not a balanced debate, on behalf of all stakeholders, but reads like a business case to invest more in neuropharmacological-based research into dementia.
Arie, T., & Jolley, D. (1983). The rising tide. British Medical Journal, 286, 325–326.
Fitzpatrick, M. (1996) Creutzfeldt-Jakob disease and bovine spongiform encephalopathy, BMJ, 312, 1037.3.
George, D.R., Whitehouse, P.J., Ballenger, J. (2011) The evolving classification of dementia: placing the DSM-V in a meaningful historical and cultural context and pondering the future of "Alzheimer's", Cult Med Psychiatry. 2011 Sep;35(3):417-35.
Swaffer, K. (2012) Dementia, denial, old age and dying, blogpost here.
Whitehouse, P.J. (2014) The end of Alzheimer's disease-From biochemical pharmacology to ecopsychosociology: A personal perspective. Biochem Pharmacol. 2014 Apr 15;88(4):677-681. doi: 10.1016/j.bcp.2013.11.017.
Zeilig H. (2014) Dementia as a cultural metaphor, Gerontologist, 54(2), pp. 258-67.


NEMOX GELATO PRO 6K CREA IS A PROFESSIONAL GELATO, ICE CREAM & SORBET MAKER. It is the most compact fully automatic table-top unit. Made in Italy. 120V/60Hz/1 Phase - 800W, AUTOMATIC program and storage, Air cooling.Electronic Speed Control, Inverter. Gravity drain. Gas R404. S/S case and paddle. Optional removable bowl.
These automatic programs, as well as ensuring the best results, make the machine completely autonomous, leaving the operator free to focus on other tasks.
• The compact size allows you to place PRO 6K CREA in every professional kitchen.
• Easy cleaning through the drain valve.
• Blade is stainless steel AISI 304 with adjustable scrapers.
The professional ice cream machine Gelato Pro 6K CREAships by truck on a pallet. The shipping cost will be added to the order amount upon determination.


Charlie Brown Coloring Pages Keralapscgov is part of great design ideas. Charlie Brown Coloring Pages Keralapscgov was created by combining fantastic ideas, interesting arrangements, and follow the current trends in the field of that make you more inspired and give artistic touches. We'd be honored if you can apply some or all of these design in your wedding. believe me, brilliant ideas would be perfect if it can be applied in real and make the people around you amazed!
Charlie Brown Coloring Pages Keralapscgov was posted in December 20, 2018 at 9:39 pm. Charlie Brown Coloring Pages Keralapscgov has viewed by 31 users. Click it and download the Charlie Brown Coloring Pages Keralapscgov.
Coloring Pages, Christmas Coloring Pages Charlie Brown was posted December 20, 2018 at 2:04 am by Verpa coloring pages . More over Christmas Coloring Pages Charlie Brown has viewed by 2430 visitor.
Coloring Pages, Merry Christmas Charlie Brown Coloring Pages was posted December 20, 2018 at 2:39 pm by Verpa coloring pages . More over Merry Christmas Charlie Brown Coloring Pages has viewed by 4921 visitor.
Coloring Pages, Free Printable Charlie Brown Christmas Coloring Pages was posted December 20, 2018 at 2:17 pm by Verpa coloring pages . More over Free Printable Charlie Brown Christmas Coloring Pages has viewed by 13731 visitor.
Coloring Pages, Printable Charlie Brown Christmas Coloring Pages was posted December 20, 2018 at 6:29 am by Verpa coloring pages . More over Printable Charlie Brown Christmas Coloring Pages has viewed by 3354 visitor.


text:
Q: if list contains variable change it to item once d = input("fill in:")
d = d.lower()
y = ['a', 'b', 'c']
if d in y:
  for x in y:
    d = d.replace(x, "d")
    print(d)
else:
  print("false")

If the user fills in a, b, or c it is supposed to print out d, if not a,b,c it is supposed to say "false". In this case the program returns 3 times, how do I fix this?

A:   for x in y:
    d = d.replace(x, "d")
    print(d)

You specifically told the program to print (not "return") three times.
If you don't want three lines printed, then move the print statement outside of the loop.

redpajama_set_name: RedPajamaStackExchange


The IQS5000B2 is a great starter kit for users who want the highest possible resolution recording with fantastic features available in AHD, with expansion up to 4 AHD cameras and 2 IP cameras this system gives crystal clear images in 5MP (2.5 X higher than 1080P). simple plug and play installation and fully featured Apps and software for remote viewing and control. This system uses AHD technology to deliver crystal clear images at 5MP recording at 12FPS and is backward compatible with other CCTV technologies. The system is designed to be plug and play and is supplied with 18 metre of cable and power supply per camera.
The System includes 2 X IQC5000B compact bullet style camera with a 3.6mm prefocused megapixel lens you get a 78º wide angle crystal clear view and the single high powered IR illuminator allows viewing in complete darkness up to 30 metres. The camera includes a 3 axis bracket for wall or ceiling mount with a solid and robust modern design this camera ticks a lot of boxes.


Will Torrent trained under Heston Blumenthal at the age of 16, won Young Chef of the Year in 2009 and has worked with top chefs such as Brian Turner and Gary Rhodes, as well as for Claridges, The Dorchester, The Lanesborough and The Fat Duck. He has appeared on the BBC's Sweet Baby James with James Martin and Ready Steady Cook. He is a patisserie consultant to Waitrose and he recently collaborated with Waitrose, Heston Blumenthal and Royal Chef Mark Flanagan to create the Diamond Jubilee Picnic Hampers. He has been profiled by The Guardian and in December he appeared on Jamie Oliver's Channel 4 show Jamie & Jimmy's Food Fight Club.
You can earn a 5% commission by selling Patisserie at Home: Step-By-Step Recipes to Help You Master the Art of French Pastry on your website. It's easy to get started - we will give you example code. After you're set-up, your website can earn you money while you work, play or even sleep! You should start right now!


text:
Classic Car Tyres
Free Shipping 2
Toyota Camry Tyres
Toyota Camry Vista Liftback
The V10 generation of Toyota Camry fitted 165-13, we recommend the 165 HR 13 Michelin XAS FF and for a low profile alternative in the size 185/70 - 13, we recommend the 185/70R13 PIRELLI CINTURATO CN36.
The V20 and V30 generations of Camry featured a few different wheel sizes based on the engine in the particular model.
165 R 14 was fit to the SV30 model for a full profile tyre option. For this size we recommend the 165 HR 14 PIRELLI CINTURATO CA67.
185/70 R 13 was fit to the CV20 and SV20 models of the Camry.
185/70 R 14 was fit to the SV21, SV25, VZV20, SV30, CV30, SV32, SV33, and SV35 models of the Camry. For this we recommend the 185/70 VR 14 PIRELLI CINTURATO CN36.
195/60 R 15 was fit to the SV21, SV32 SV33, SV35, VZV30, VZV31 VZV32, and VZV33 models on 15" wheels. For this size we recommend the 195/60 VR 15 Michelin Pilot Primacy 3.
Toyota Camry Inner Tubes:
We recommend the Michelin 13D Offset Valve Inner Tube for the size 165 - 13.
We recommend the Michelin 13E Offset Valve Inner Tube for the size 185/70 - 13.
We recommend the Michelin 14E Offset Valve Inner Tube for the size 165 - 14
We recommend the Michelin 14F Offset Valve Inner Tube for the size 185/70 - 14.
It is worth noting an inner tube should not be fitted into the later Toyota Camry with 195/60R15 tyres. Inner tubes should not be fitted into a 60 profile tyre.
Toyota Camry Recommended Tyres
165 R 13 Dunlop SP Sport Aquajet
Starting at $248.64 $207.20
185/70 VR 13 PIRELLI CINTURATO CN36
165 HR 14 PIRELLI CINTURATO CA67
195/60 VR 15 Michelin Pilot Primacy 3
Michelin 13D Offset Valve Inner Tube
Starting at $21.84 $18.20
Michelin 13E Offset Valve Inner Tube
Michelin 14F Offset Valve Inner Tube
Other Options for Toyota Camry Tyres
165 HR 14 Michelin XAS
165 HR 13 Michelin XAS FF
185/70 R 14 Michelin XAS
185/70 R 13 Michelin XDX
185/70 HR 13 Avon CR6ZZ
165 X 14 Vredestein Classic
185/70R13 Dunlop SP Sport AquaJet
195/60 SR 15 B.F.Goodrich Radial T/A
165 TR 14 Barum
Starting at $102.48 $85.40
Set of 4 165 HR14 PIRELLI CINTURATO CA67
Set of 5 165 R 14 PIRELLI CINTURATO CA67
Starting at $1,006.32 $838.60
Set of 4 185/70 R13 PIRELLI CINTURATO CN36
Set of 5 185/70 R 13 PIRELLI CINTURATO CN36
History of the Toyota Camry
The Toyota Camry moniker originated with the Toyota Celica Camry, a variant of the Celica introduced in January 1980 exclusively in Japan through Toyota Corolla Store dealerships. The Celica Camry was a forerunner of the Camrys that debuted just two years later, the V10 generation of Camry. The V10 Camry was introduced to the Japanese market on March 24, 1982, alongside a twinned product named the Toyota Vista, which was effectively a rebadged Camry offered in different dealership locations. The V10 was designed with two distinct characteristics in mind. Fuel efficiency (after the 1973 Oil Crisis) and exports, particularly to the United States Sales in the United States began in March 1983, and by 1985, they had sold 128,000 vehicles, launching the Camry's massive success in the United States.
Aside from estate variants, which were Toyota's first estate vehicle, the V20 Camry/Vista generation featured the same four-door saloon configuration. These were released in Japan in August 1986, Australia in February 1987, and the United States in May 1988. All Camry and Vista engines now received fuel injection, while the Camry Saloon models got a sportier look with lower and broader body proportions.
The Holden Apollo, another rebadged Camry that was sold in Australia beginning in 1989, was the result of the UAAI, or United Australian Automobile Industries, a joint venture between Toyota Australia and General Motors-Holden. Minor trim modifications on the Apollo included a revised grille, tail lights, and other minor tweaks. The V30 Camry retained the four-door saloon design while also offering a hardtop saloon in a distinct style. Vista-branded variants with different designs were also available. The V30 was only offered in Japan, whereas the Camry XV10 was available elsewhere, with modest differences in trim at the front and back.

redpajama_set_name: RedPajamaCommonCrawl


Conducting her first 35-piece film score she composed & orchestrated.
Above and below is Crystal BlackCreek Carlisle conducting her 35-piece orchestral score at Martin Sound dubbing stage for her final score at UCLA Extension Filmscoring Program completed recently.
Conducting her first 35-piece orchestration to film at a dubbing session.


text:
Investment Criteria Overview
Industrial Chemicals, Products & Distribution
Consumer Foods, Products & Home Services
Professional Information Services
The path to successful investments begins with our consumer expertise
Akoya has identified a Consumer Food sector strategy that capitalizes on key societal trends and select product categories that are well positioned relative to these key trends. We have chosen to focus on product categories that meet the following criteria:
The product category benefits from several of the key societal trends
The category size is sufficiently large (>$500 MM) to provide growth opportunities
The market share structure of the category represents an attractive scenario with the #1 brand share at The selected company or business is not marketing intensive, but rather focuses primarily on private label and/or foodservice business
Company gross margins are 40-50%, or can reach that range within 1 year
Existing capacity is sufficient to support at least two to three years of growth
Target Segments for Consumer Foods
Frozen/Refrigerated
Natural/Better For You
Akoya is focusing on the Consumer Products sector comprising of over $500 Billion of annual sales in the US. A consumer products company develops, manufactures and markets products through the following channels – Specialty Retailers, Wholesale Clubs, Food & Drug, Mass Merchants, ecommerce/online retailers, B2b or B2C Distributors and Independent Dealers. We seek companies that fall within one or more of the following categories.
Unique products, technology or defensible market positions
Quality products, recognizable brands, established channels of distribution
Under-performing business requiring strategic realignment, new talent or additional capital
Steady cash flow but lacking sufficient funds to reach full potential
Companies run by owner/operators that wish to diversify holdings; remain with the business with partial ownership
Target Segments for Consumer Products
Housewares & Home Improvement Products
Home, School, & Office Products
Sports & Recreational Products
Target Segments for Home Services
Essential Home Services including residential HVAC, waterproofing, and plumbing services.
Exterior & Interior Home Finishing including residential siding, roofing, windows, doors, solar energy, bathroom and kitchen remodeling
Sector Leaders
Lou Nieto
Managing Director, Consumer Foods Sector Leader
Denny Chandler
Managing Director, Consumer Products Sector Leader
Steve DeZara
Managing Director, Home Services
lnieto@akoyacapital.com
Lou became affiliated with Akoya Capital in 2010 and serves as its Consumer Foods Sector Leader.
Having spent over 28 years in the industry, Lou has deep domain expertise and executive leadership capability in consumer foods; including, marketing and brand management, strategy, distribution, private label, ethnic, and dairy, and in implementation and change management.
Lou has had large company sales, marketing, and branding experiences at both Quaker Oats Company and Kraft Foods, Inc followed by executive-level experiences as EVP, Marketing, Sales & Distribution for Mission Foods, Group President of Dean Foods Company, President/CEO of Federated Group and, most recently as President of Consumer Foods for ConAgra.
Lou currently serves on the Boards of Ryder Systems, Inc., Auto Zone our portfolio company Eddy Packing Company and Fresh and Ready Foods. Lou is also President of Nieto Advisory, LLC. He has a BA from the University of Chicago and an MBA from Harvard University.
dchandler@akoyacapital.com
Denny Chandler joined Akoya in 2014 and is our Sector Leader for Consumer Products. He has a 30-year track record of leading consumer products businesses successfully through transition; and, building market share and profits in challenging competitive circumstances. His experience spans globally and includes private equity, turnarounds, restructurings, strategic realignments, M&A and start-ups.
Before joining Akoya Denny led privately held Identity Group Holdings through a financial restructuring and successful turnaround as its CEO and member of the Board of Directors.
Prior experience includes a successful fifteen-year career at ACCO Brands. As President and Chief Operating Officer from 2005 through 2008, he was a key member of the executive team that successfully led the spin-off of ACCO from Fortune Brands, ACCO's merger with General Binding Co. and its ultimate transition to a NYSE publicly listed company.
Before ACCO Brands, Denny held several executive level positions including Division President at Bell + Howell, VP Brand Marketing for Walt Disney Consumer Products and VP & General Manager at Wilson Sporting Goods.
Denny earned an MBA from the Kellogg School of Management at Northwestern University and a degree in marketing from Indiana University. He currently serves on the Board of Directors of Akoya's portfolio company Indigo Signworks and on the board of Fiber Mark and SED International.
sdezara@akoyacapital.com
Steve brings over 30 years of innovative and data-driven business leadership, and a passion for problem-solving related to sales, operations, and growth of businesses. As a thought-leader within the Home Services industry, Steve, throughout his career, always leveraged new and existing technologies to grow revenue, and utilized relevant data to create meaningful business solutions. He has driven profitable growth in both large, publicly traded companies, and small entrepreneurial businesses.
Steve has held numerous operating roles including as CEO of Luna Flooring for over 15 years, and then as CEO of Luna Brands after leading a successful merger with Empire Today. During his tenure as CEO of Luna, Steve grew the business at 25% CAGR. He has also led a geographic expansion strategy that resulted in a 50% at home flooring market share within 24 months of opening new markets. Most recently, Steve has started and built two successful Home Services companies. He acquired Galaxie Home in 2012 and grew that company over the course of six years before pivoting to his current role in AI technology.
Steve currently operates as the CEO and founding partner of Think Unlimited, helping Home Services companies grow revenue through data-driven AI lead allocation and scoring software as well as drip campaign services.
Steve is a Board Director of Empire Today and Board Director for the past 25 years for the BBB.
Companies in this sector
Indigo Signworks
Investment date
Indigo, based in Fargo, ND is a market-leading manufacturer of custom-made exterior and interior signage, offering a wide suite of services, including design, manufacturing, installation, and maintenance to a diverse customer base.
Fresh Ready Foods
Fresh & Ready, headquartered in Chicago, Illinois, is a leading manufacturer and distributor of high quality sandwiches, box lunches, salads and baked goods and producer of "gourmet" fresh-prepared, grab-n-go sandwiches, wraps, salads and side dishes.
Eddy Packing Company, headquartered in Yoakum, Texas, is a broadly diversified, premier processor of beef, pork and poultry products. The company offers a complete line of fully cooked, marinated, cured, fresh and frozen meat products, such as smoked sausage, fajita meat, pulled beef/pork/chicken, ribs, pork chops/loins, chicken breast, brisket and other meat products. In addition to owning one of the largest branded meat portfolios in its region, Eddy offers private label products to major retailers and foodservice distributors nationally.
Download the Akoya Summary Overview
© 2021 Akoya Capital All Rights Reserved
Website Design by MVP Marketing + Design


text:
The Cashmere Valley Bank Secret Sound
Morning Bull Pen
Random Acts of Bullness
Subscribe to 92.9 on YouTube
#1 FOR NEW COUNTRY IN YAKIMA
Shows and DJs
The Morning Bull Pen
Brian Stephenson
Got Our App?
Listen to The Bull on Alexa
Road and pass reports
The Bull Mobile
The Morning Bull PenThe Morning Bull Pen
Everything You Need to Know About the 2019 CMA Awards
Michael Loccisano, Getty Images
The 2019 CMA Awards are right around the corner, and the details of Country Music's Biggest Night are starting to take shape. Taste of Country is putting together all of the information you need to know about the 53rd annual CMA Awards in one handy guide.
The show features award presentations in some of the most important categories, all-star performances, special collaborations and epic moments from your favorite country stars. The CMA Awards are generally considered the most prestigious awards in the genre. This year's broadcast will feature a Who's Who of contemporary country music, as well as some living legends.
Read on to find out everything we know about the 2019 CMA Awards:
The Date and Time:
The 2019 CMA Awards will take place on Nov. 13 and broadcast live on ABC beginning at 8PM ET.
The 53rd annual CMA Awards will air live from the Bridgestone Arena in Nashville.
The Hosts:
Carrie Underwood and Brad Paisley have co-hosted the CMA Awards for the past 11 years, but she is returning without him in 2019. Reba McEntire and Dolly Parton are set to join Underwood as special guest co-hosts this year as part of an emphasis on the women of country music.
The Nominees:
The Country Music Association revealed the nominees for the 2019 CMA Awards on Aug. 28. Some of country music's biggest stars will compete for honors including Song of the Year, Single of the Year and Album of the Year, culminating in the night's biggest award, Entertainer of the Year. Garth Brooks, Eric Church, Chris Stapleton, Carrie Underwood and Keith Urban are all nominated for Entertainer of the Year in 2019.
The Country Music Association announced Eric Church, Luke Combs, Miranda Lambert, Reba McEntire, Maren Morris, Dolly Parton with For King & Country and Zach Williams, Pink and Chris Stapleton, Carrie Underwood and Keith Urban as the first round of performers for the 53rd annual CMA Awards on Oct. 23.
Additionally Blake Shelton and Garth Brooks will perform and Shelton will perform solo. Kacey Musgraves and Willie Nelson will share the stage and you can expect massive all-female collaborations led by Kelsea Ballerini and Carrie Underwood. Ballerini's group of younger artists will perform "Girl Crush" while Underwood's group is set to sing a medley of female country hits.
Dierks Bentley will lead a collaborative tribute to Kris Kristofferson, singing "Me and Bobby McGee." Brooks & Dunn, Dan + Shay and Thomas Rhett are three more of the 18 announced performances.
There are 23 announced presenters for the 2019 CMA Awards, including Reese Witherspoon, Vince Gill, Jimmie Allen, Martina McBride and Trisha Yearwood.
How the Winners Are Chosen:
The Country Music Association has its over 7,000 industry professional members vote in three rounds to determine the nominees and winners in the annual CMA Awards.
Remember: The best way to watch the 2019 CMAs is on TV, with ToC on your phone!
No Brad? No Problem! Carrie's Got This:
Carrie Underwood's Best CMA Awards Looks of All Time:
Source: Everything You Need to Know About the 2019 CMA Awards
Categories: Featured, News
Heard on 92.9
Phishing Scam Looking for Victims in Yakima
No Fox TV Because of Dish? Here's the Quick Fix
Yakima Arboretum Fundraiser at Ummelina Spa in February
Former Sheriff Brian Winter Dies Saturday
2020 92.9 The Bull is part of the Taste Of Country Network, Townsquare Media, Inc. All rights reserved.


Discover the very unique character of a community where French is the mother tongue of most of its 3000 inhabitants. Meet the locals, proud of their cultural heritage and willing to share with you their joie de vivre and traditions through many cultural activities, festivals or events. Taste their authentic cuisine, enjoy a typical Acadian dish or some delightful freshly caught seafood. Let's cast off!


text:
Find a Veterans Service Officer
ND Department of Veterans Affairs
Education (SAA)
State Heroes
VSO Tools
Commissioner's Challenge on Suicide Prevention
Benefit Types
Burial and Memorial
Veterans Appreciation
Women and Minority Veterans
Other Assistance
TRICARE Health Insurance Changes 2021
VA Extends Fargo VA HBOT Demonstration Program
988 to be New National Suicide Prevention Number
VA releases 2020 National Veteran Suicide Prevention Annual Report
VA has new options for Veterans to pay their VA Medical Care Copayments
Fargo VA Health Care System approved as priority for future VA Fisher House construction
Three (3) more conditions added to AGENT ORANGE presumptive conditions list
ND Department of Veterans Affairs Main Phone Line Down
North Dakota Women Veterans
This website requires JavaScript be turned on for full functionality.
Benefit Category: State
ND Veterans Affairs Resources
The ND VA developed a Women Veteran's Registry card as a tool to register woman veterans into our data base. Some ideas that are in development are; conferences, membership to the association, newsletters, and committees. We would benefit from your input into the possibilities. Please take a few minutes to print, complete, and mail this card. (78kb pdf)
The Women in the Military Survey was developed to collect statistical information for the State of North Dakota. Please print, complete, and mail this survey. (68kb pdf)
Center for Women Veterans
The role of the VA Center for Women Veterans is to monitor and coordinate VA's administration of health care and benefits services, and programs for women Veterans. Serve as an advocate for a cultural transformation (both within VA and in the general public) in recognizing the service and contributions of women Veterans and women in the military. And to raise awareness of the responsibility to treat women Veterans with dignity and respect.
Women Veterans Call Center
Calling all women who served in the United States Military. Do you know your Veteran status? Do you have a Veteran ID card? Do you receive any benefits from the VA, like the GI Bill? Do you receive health care benefits from VA? If you do not know the answers to these questions Department of Veterans Affairs (VA) established a call center just for you.
The Women Veterans Call Center (WVCC) answers questions and responds to concerns from women Veterans, their families, and caregivers across the nation about VA services and resources. The call is free, and you can call as often as you like until you have the answers to your questions. The hours of operation are Monday through Friday 8:00 a.m. to 10:00 p.m. ET and Saturday, 8:00 a.m. to 6:30 p.m. ET.
UniteUS Center for Women Veterans
Here's What We Do:
INFORM. Monitor and coordinate VA's administration of health care and benefits services, and programs for women Veterans.
ADVOCATE. Serve as an advocate for a cultural transformation (both within VA and in the general public) in recognizing the service and contributions of women Veterans and women in the military. Raise awareness of the responsibility to treat women Veterans with dignity and respect.
CONNECT. We help women Veterans connect to the people and resources that can help them when they need it most.
We hope this community serves as an opportunity for women Veterans across the country to come together, learn about benefits and resources, and connect with each other. We look forward to our continued collaborations and exploring ways in which to maximize our Women Veterans' UniteUS experience.
Grace After Fire
Grace After Fire is a resource solely for women veterans to support their need to connect with each other and share yet remain anonymous. These women can reach out to others who have experienced the same concerns of re-entry, alcoholism, drug addiction or prescription addiction due to chronic pain, Post Traumatic Stress Disorder (PTSD), incidents of service time rape, depression, unwarranted anger, or Traumatic Brain Injury (TBI) due to war time trauma.
Phone: 877-490-5797 (Toll Free)
Website: http://www.graceafterfire.org/
National Association of State Women Veteran Coordinators
The purpose of this organization is to exchange ideas, information and training to facilitate reciprocal service for women veterans and to secure uniformity, equality and effectiveness in providing these services to women veterans; furthermore, identify issues of concern to the women veterans community, and develop recommendations to address these concerns through legislative, programmatic, and outreach activities.
The National Women's Health Information Center
The Office on Women's Health (OWH) was established in 1991 within the U.S. Department of Health and Human Services. Its Vision is to ensure that "All Women and Girls are Healthier and Have a Better Sense of Well Being." Its mission is to "provide leadership to promote health equity for women and girls through sex/gender-specific approaches." The strategy OWH uses to achieve its mission and vision is through the development of innovative programs, by educating health professionals, and motivating behavior change in consumers through the dissemination of health information.
200 Independence Avenue, SW Room 712E
Women in Military Service For America Memorial
Mission: "Let the generations know that the women in uniform also guaranteed their freedom". - Anne S. (Sosh) Brehm 1LT, USA NC, World War II
Women In Military Service For America Memorial Foundation
Dept. 560
FAX: 703-931-4208 • E-mail: hq@womensmemorial.org
Related Resource(s)
ND Women Veterans Newsletter (January 2015) (467.0 KB pdf)
Woman Veteran Registry Card (151.0 KB pdf)
Women in the Military Survey (203.0 KB pdf)
News about North Dakota Women Veterans
Remarkable Women Veterans in American History
by Hans Petersen, VA Staff Writer
VA celebrates Women's History Month with a look at some fascinating women Veterans and their remarkable achievements.
Discharge Requests
Most Veteran's benefits require that applicants provide a copy of their Form DD 214 or discharge record, which is evidence of their veteran status. This is an important document and must be safeguarded. In the State of North Dakota separation documents are considered confidential and privileged NDCC 37-18-11 (13). National Guard members may receive a NGB22 and/or NGB23 upon obtaining 20 years of satisfactory service (20 year letter).
Through the ND Department of Veterans Affairs website you are able to link to other websites which are not under the control of the ND Department of Veterans Affairs. We have no control over the nature, content, or availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views, products, or services expressed within them.
Copyright © 2021 North Dakota Office of Veterans Affairs
Download Adobe Reader to view and print PDF files.


This selection of images comes from Iconic Australian Houses: An Exhibition by Karen McCartney on show at the National Archives until 13 March 2017.
Please attribute all images to photographer.
The Dingle House, architect Enrico Taglietti.
The Audette House, architect Peter Muller.
The Rosenburg House, architect Neville Gruzman.
The Buhrich House II, architect Hugh Buhrich.
The Lobster Bay House, architect Ian McKay.
The Collins House, architect Ian Collins.
The Palm House, architect Richard Leplastrier.
The Marie Short/Murcutt House, architect Glenn Murcutt.
The Gottlieb House, Wood Marsh architects.
The Kew House, architect Sean Godsell.
The Grounds House, architect Roy Grounds.
The Butterfly House, architect Peter McIntyre.
The Phillip Island House, architect Barrie Marshall.
The Hildebrand House, Robinson Chen architects.
The Wardle House, architect John Wardle.
The D House, Donovan Hill architects.
The Gartner House, architect Gabriel Poole.
The Mooloomba House, Andresen and O'Gorman architects.


text:
Trudeau to offer formal apology in Commons for fate of Jewish refugee ship MS St. Louis
Prime Minister Justin Trudeau will deliver another official apology in the House of Commons, this time over the fate of the MS St. Louis.
In 1939, Canada turned away 907 German Jews seeking asylum; 254 later lost their lives in the Holocaust
CBC News · Posted: May 08, 2018 8:50 PM ET | Last Updated: October 30, 2018
Jewish refugees aboard the MS St. Louis attempt to communicate with friends and relatives in Cuba, who were permitted to approach the docked vessel in small boats, June 3, 1939. (United States Holocaust Memorial Museum/National Archives and Records)
"When Canada denied asylum to the 907 German Jews on board the MS St. Louis, we failed not only those passengers, but also their descendants and community," Trudeau said in a statement, which doesn't say when he plans to deliver the apology.
The prime minister said that while an apology can't change Canada's history or bring back those who lost their lives, acknowledging the result of the decision to turn away the MS St. Louis — the deaths of 254 people in the Holocaust — is key to learning from the past.
"It is our collective responsibility to acknowledge this difficult truth, learn from this story, and continue to fight against anti-Semitism every day, as we give meaning to the solemn vow: 'Never again,'" Trudeau said. "I look forward to offering this apology on the floor of the House."
The Prime Minister said in a Toronto synagogue on Tuesday evening that he would apologize on the floor of the Commons for the turning back of the ship in 1939 1:01
Trudeau has previously sought to atone for wrongs committed by governments of the past with official apologies in the House of Commons.
Since the last election, Trudeau has personally apologized to gay men and women targeted for their sexuality, he apologized for Canada's 1914 decision to turn away the Komagata Maru ship that was carrying 376, mostly Sikh, migrants, and he exonerated six Tsilhqot'in chiefs who were hanged in 1864 for their role in the killing of six white colonists.
Prime Minister Justin Trudeau hugs a drummer after delivering a statement of exoneration on behalf of the government of Canada to the Tsilhqot'in Nation and the descendants of six Tsilhqot'in chiefs. (Sean Kilpatrick/Canadian Press)
The prime minister also apologized to survivors of the Indian residential school system in Newfoundland and Labrador, people who were left out of the initial apology delivered by former prime minister Stephen Harper in 2008 because those schools weren't federally run.
The prime minister's father, Pierre Elliott Trudeau, spurned these sorts of official apologies, saying: "I do not think the purpose of a government is to right the past. It cannot rewrite history. It is our purpose to be just in our time."
It was Conservative Brian Mulroney who bucked the trend in 1988, when he apologized for the internment of Japanese-Canadians (former U.S. President Ronald Reagan the same year signed a similar apology to Japanese-Americans who were interned).
Stephen Harper followed suit in 2006 with an apology for the head tax that unfairly penalized Chinese immigrants from 1885 to 1923. The apology to Indian residential schools followed two years later.
Though panned by some critics as "virtue-signalling" and gesture politics, apologies often mean a lot to the people to whom they're directed.
Ship of Fate exhibit tells dark chapter of Canadian history
Liberals working on apology for 1939 decision to refuse ship of Jewish refugees
In 1939, the MS St. Louis left Germany carrying 907 Jewish passengers fleeing persecution from the Nazi regime. The ship was turned away from Cuba and the United States before a group of Canadians tried to convince then-prime minister Mackenzie King's government to let it dock in Halifax.
'None is too many'
The Canadian government heeded anti-Semitic sentiment by severely restricting Jewish immigration in this era. From 1933 to 1945, only about 5,000 Jewish refugees were accepted because of what Trudeau called Tuesday "our discriminatory, 'none is too many' immigration policy" in place at the time.
Thus, when the government refused to let MS St. Louis passengers disembark, the ship returned to Europe.
About half the passengers were taken in by the U.K., the Netherlands, France and Belgium. About 500 of them ended up back in Germany, where 254 were killed in concentration and internment camps.
In a statement, the Friends of Simon Wiesenthal Centre applauded Trudeau's announcement as a "meaningful step" toward acknowledging the shameful chapter.
"While an apology can never change the past, it can awaken the national conscience to ensure such grave mistakes are never repeated in the future," centre president Avi Benlolo said.
The announcement took place during a gala in Toronto to mark 30 years of the March of the Living, an event that teaches about the horrors of the Second World War while honouring Holocaust survivors .
The CEO of the Centre for Israel and Jewish Affairs (CIJA), a group that promotes Jewish interests in Canada, welcomed Trudeau's announcement.
"We applaud the Prime Minister for committing to formally apologize in the House of Commons for the St. Louis incident — a shameful example of Canada's 'none is too many' policy toward Jewish refugees fleeing Nazi persecution," said Shimon Koffler Fogel.
"Canada is extraordinary not only because we strive to uphold the highest ideals, but also because we have the courage to address moments in our history when we failed to do so. A formal apology will be a powerful statement to Holocaust survivors and their families, including St. Louis passengers who live in Canada today."
With files from the CBC's John Paul Tasker, Evan Dyer and the Canadian Press
Libeskind memorial to Jews rejected in Halifax unveiled
'We are truly sorry': Trudeau exonerates Tsilhqot'in chiefs hanged in 1864


text:
Q: Besides being symmetric, when will a matrix have ONLY real eigenvalues? I realize that when a matrix is symmetric, then it must have all real eigenvalues. However, I am doing research on matrices for my own pleasure and I cannot find a mathematical proof or explanation when a matrix will have all real eigenvalues except for when it is symmetric. I am dealing with matrices such as A below and I want to know what is it about A and its characteristic polynomial that gives it real eigenvalues (0, 0, -2)? Similarly, what is it about matrix B that gives it only one real eigenvalue (0) and the other two complex?

A: There are so-called $\mathcal{PT}$-symmetric matrices which may have purely real eigenvalues. A square matrix $M$ is called $\mathcal{PT}$-symmetric iff it satisfies the property:
$$
[\mathcal{PT},M] = 0 \Leftrightarrow \mathcal{P}M = M^*\mathcal{P}
$$
where $\mathcal{T}\equiv*$ is the complex conjugation operator and $\mathcal{P}$ is a matrix satisfying  $[\mathcal{P},\mathcal{T}]=0$ (implying that $\mathcal{P}$ is a real matrix) and $\mathcal{P}^2=1$, $\mathcal{T}^2=1$ $\Rightarrow (\mathcal{PT})^2=1$. Since $\mathcal{P}$ is an involution, its eigenvalues are $\pm1$ and one may find a basis such that $\mathcal{P}=\mathrm{diag}(1,1,1,1,...,-1,-1,-1)$. A $\mathcal{PT}$-symmetric matrix is said to have 'unbroken' $\mathcal{PT}$ symmetry iff any eigenvector of $M$ is also an eigenvector of $\mathcal{PT}$.
Claim:
If $M$ has unbroken $\mathcal{PT}$ symmetry, this implies that $M$ has real eigenvalues.
Proof: First note that the eigenvalues of $\mathcal{PT}$ are non-zero since the combination is an involution: $\mathcal{PT} u = \mu u \Rightarrow \mathcal{PT}^2 u = u = \mu^*\mu u  \Rightarrow |\mu|=1$.
Now let $Mv = \lambda v \Rightarrow \mathcal{PT}Mv = \mathcal{PT} \lambda v$. Thus since the combination $\mathcal{PT}$ is an anti-linear operator and $M$ commutes with $\mathcal{PT}$: $\mathcal{PT} M v = \lambda^*\mathcal{PT}v\Rightarrow \lambda \mu = \lambda^*\mu$. Since we've shown that $\mu\neq0$, this implies $\lambda^* = \lambda$. QED
More on $\mathcal{PT}$-symmetry and related concepts in this article: http://arxiv.org/abs/1212.1861
The English in there isn't perfect but the content looks good.

A: Another approach is  to construct a triangular matrix with pre-determined diagonal entries; they will be the eigenvalues, and the matrix is not symmetric.

A: Do you know of  companion matrices? See the Wikipedia link here:
http://en.wikipedia.org/wiki/Companion_matrix
They are made-to-order matrices which will have the polynomial you want as its characteristic polynomial. They are far from symmetric matrices. Now start with a polynomial having your favorite real numbers as its roots, and construct the Companion matrix for that polynomial.

A: Here is one example of sufficient conditions.

A: I do not understand what is the OP's question. Yet, I think that the interesting question is : if I randomly choose a large square matrix, then should I wait for a long time before getting a matrix whose all eigenvalues are real? The answer is: yes, a very long time.
Let $N_n$ be the number of real roots of a random polynomial (its coefficients are iid and follow the same law)  of degree $n$. In this paper (one of the authors is Van Vu who wrote papers with Terrific Tao...),
https://arxiv.org/pdf/1402.4628.pdf
we find this beautiful result
$\textbf{Theorem}$. For any random variable $\xi$ with mean $0$ and variance $1$ and bounded $(2 +\epsilon)$-moment, one has
$E(N_n)=2/π\log n+O(1)$ where $O(1)$ depends on $\xi$.
$\textbf{Remark}$.  Generally, the standard deviation of $N_n$ is in $O(\sqrt{\log(n)})$.
Thus, the probability when $n$ is large that $N_n=n$ is $\approx 0$. For example, if $n=10$ and the coefficients are uniformly random in $[[-100,100]]$, then $10^5$ tests give $0$ such matrix!!

A: A necessary and sufficient condition for a matrix$~A$ to have only real eigenvalues (that is, not have any non-real complex eigenvalues) is the existence of a polynomial $P$ that splits into linear factors over the real numbers and such that $P[A]=0$. If such a polynomial exists at all, one can take the characteristic polynomial for$~A$ (but not necessarily the minimal polynomial) as$~P$. This gives a trivially valid, but fairly hard to check condition. Without using eigenvectors, it is actually not so obvious why the characteristic polynomial of a symmetric matrix should always allow such a factorisation. But I don't think one can do much better to completely characterise the case of real-only eigenvalues.


text:
Jonathon Calvin Simmons (Houston, Texas, 14 de septiembre de 1989) es un baloncestista estadounidense que actualmente pertenece a la plantilla de los Shanxi Loongs de la CBA china. Con 1,98 metros de estatura, juega en la posición de escolta.

Trayectoria deportiva

Universidad
Tras jugar dos años en sendos junior college de la NJCAA, fue transferido en 2011 a los Cougars de la Universidad de Houston, donde jugó una temporada en la que promedió 14,7 puntos y 5,0 rebotes por partido. En abril de 2012 anunció su intención de entrar en el draft de la NBA, renunciando a su último año universitario.

Estadísticas

Profesional
Tras no ser elegido en el Draft de la NBA de 2012, fue elegido en la primera ronda de la temporada inaugural de la American Basketball League, una liga semiprofesional en la que jugó con los Sugar Land Legends, promediando unos sorprendentes 36,5 puntos por partido.

Al año siguiente fichó por los Austin Toros de la NBA D-League, donde en su primera temporada promedió 9,8 puntos y 4,5 rebotes por partido. En 2014 renovó con el equipo con su nueva denominación, los Austin Spurs, promediando en su segunda temporada 15,2 puntos, 4,3 rebotes y 3,7 asistencias, resultando elegido en el tercer mejor quinteto defensivo de la NBA Development League.

Tras varias subidas y bajadas, finalmente, en la temporada 15-16 consiguió hacerse un hueco en el banquillo de los Spurs. Durante la temporada siguiente, pasó a ser un fijo en la rotación para Gregg Popovich, llegando a disputar 78 encuentros de temporada regular, y 15 de playoffs. Al término de la temporada, la franquicia le ofreció una oferta cualificada, pero Simmons la rechazó para convertirse en agente libre.

El 15 de julio de 2017, Simmons firma su primer gran contrato como profesional, por tres años y $20 millones, con los Orlando Magic. El 9 de diciembre de 2017, anotó 29 tantos en la derrota frente Atlanta Hawks por 117–110. El 6 de febrero de 2018, consiguió 22 puntos en el tercer cuarto, para finalizar con 34, en la victoria frente a los Cleveland Cavaliers por 116–98. El 14 de marzo de 2018, en la victoria frente Milwaukee Bucks (126–117), registró la anotación más alta de su carrera con 35 tantos.

A mediados de temporada, el 7 de febrero de 2019, fue traspasado a Philadelphia 76ers a cambio de Markelle Fultz.

El 21 de junio de 2019, Simmons es traspasado, junto a los derechos del draft de Admiral Schofield, a los Washington Wizards. Pero el 7 de julio de 2019, los Wizards cortan a Simmons.

El 25 de febrero de 2020, Jonathon vuelve a la D-League al fichar por los Santa Cruz Warriors.

El 7 de octubre de 2020 decide fichar por los Liaoning Flying Leopards de la Chinese Basketball Association (CBA).

El 15 de diciembre de 2021 firma con los Shanxi Loongs también de la Chinese Basketball Association.

Estadísticas de su carrera en la NBA

Temporada regular

Playoffs

Vida personal
Jonathon es hijo de Michael Sean y LaTonya Simmons, y tiene un hermano pequeño (Joi) y otras dos hermanas.

Simmons es padre de cuatro niñas. Las tres primeras (Jaeda, Journey y Jordynn) las tuvo con su novia del instituto, Courtney Holt, y la última (Brielle) con Briana Monique Mouttet, con quien sale desde 2012.

Referencias

Enlaces externos

 Ficha en basketball-reference (NBD-L)
Houston bio
NBA D-League profile
Jonathan Simmons' Personal over Physical Growth
2015 NBA Summer League profile

Baloncestistas de Texas
Baloncestistas de la NBA
Baloncestistas de los Houston Cougars
Baloncestistas de los San Antonio Spurs
Baloncestistas de los Austin Spurs
Baloncestistas de los Orlando Magic
Baloncestistas de los Philadelphia 76ers
Baloncestistas de los Santa Cruz Warriors
Baloncestistas de los Liaoning Dinosaurs
Nacidos en Houston

redpajama_set_name: RedPajamaWikipedia


Have you ever heard of the "Bulletin of the Atomic Scientists"? It's a group of really smart men and women that observe world events and guesstimate how close the world is to an apocalyptic event of any description. Their easy to understand "... to twelve" format currently has the apocalypse represented as 2.5 minutes to twelve. A scary thought.
Uncertainty in the world is good for few things, but gaming is an exception. Survival games thrive and have become a genre of itself. Judgment: Apocalypse Survival Simulation rides this wave of popularity and it does it so well that you'd almost forget it's an Early Access title. In fact, I honestly felt I was playing a full game until the game told me that I was not.
Judgement liberally mixes settlement building with role-playing, exploration and top down shooting. Combined, these elements make for a fascinating survival experience. You start out with a small group of survivors trying to get by in a world that has been invaded by demons. All sorts of horrors are trying to cut your game short and the only way to stay alive is to rally other survivors to your cause. With them, you must build, grow, fight and craft your way out of the mess your survivors are in and eliminate the demon threat.
Survival means paying attention to all sorts of things. You'll need to create a defensible base, feed your survivors and supply them with weapons and armor. If you are to survive, equipment, farming buildings will need to be developed and improved through research and crafting. There is a whole set of rituals to deal with the new demonic reality as well, some of which can be ignored, others offering an important lifeline.
And that's just the stuff you'll be in charge of at home. There is a whole world outside too. You'll need to guide expeditionary forces to scavenge a substantial world map. Your brave men and women will come back with much needed resources, often wounded from fighting the demons protecting whatever they find in the field. If they are not scrounging for supplies, they're rescuing other survivors that will join your team and increase your chances of survival. But you can't just bring every stray home - the busier your base gets, the more likely it is to be discovered by roving demons.
There is a real sense of urgency and every minute of the game feels like it matters. Each minute is one more to gear up and prepare the fight against the waves of demon attackers that are looking to destroy your base. Where the expeditions feel like you're playing a top-down shooter, the home defense missions could be seen a bit like a high stakes tower defense game. Increasingly strong waves of demons descend upon your base and your defensive prowess will be tested to the max every time. A more developed base increases your chances to come out on top and you'll continuously be working towards that end.
Judgment appeals to the imagination. There is a definite sense of hopelessness during the early stages of the game. As you grow stronger, this changes into hope but very, very slowly and that is how it should be. The Early Access version appears to have almost all of the tech trees and base building options that do not involve the story line. At some point you're asked to start figuring out a way to get rid of the demons altogether and this is where the Early Access version stops you in your tracks. You don't need to take this route though. There is a seemingly endless supply of demons and you can keep going to your heart's content.