templates.yaml

welcome: Welcome to VMAX managed by Alexa. Voice Controled Storage Domination.

what_can_i_do: Ask me about Alerts, Provisioning, Performance, or why not ask about the new VMAX Nine Fifty

alert_help: you can ask, what alerts are on my VMAX.

provisioning_help: You can simply ask me provision storage.

performance_help: Possible Questions are.
                  Give me an overview of storage group compliance.

faq_help: You can ask for help on the following topics.
          Tell me about VMAX all flash.
          Tell me about the new VMAX

array: There are {{ amount }} VMAX arrays in your environment. These are {{ array_list }}.
       Select an array by stating the last four digits of its serial number.

one_array: There is one array in your environment. Its serial number is {{ array }}

indexerror: Sorry, that index was not recognised. Would you like to try again?

alerts: There are {{ array_alert_num }} total unacknowledged alerts, including {{ server_unacknowledged }}
        server alerts, for the given VMAX. If you would like the details of these alerts, say "get alert details".

no_alerts: There are no alerts for your chosen array.

alert_details: The details of the selected alerts are as follows {{ alert_list }}.

goodbye: Goodbye Hack Attack teams and thank you for listening


vmax_intro: VMAX All Flash is architected to support the densest flash configuration possible. VMAX ALL Flash provides
            higher performance, predictable latency, increased density, reduced power with the highest reliablility
            availablity and serviceability coupled with the best data services in the industry.

vmax_device_limits: VMAX All FLash and VMAX3 support devices of up to 64TB in size.  VMAX ALL FLASH volumes can be
                    dynamically expanded, and do not use meta devices.  VMAX ALL FLASH supports up to 64K volumes.

vmax_950: VMAX Nine Fifty is the latest addition to the VMAX family.  Mazzel tov. Vmax nine fifty uses the latest intel
          processors and provides up 5 times more performance than the competition giving Unmatched Performance, PROTECTION and SECURITY.
          VMAX Nine Fifty supports all the data services you expect from VMAX giving you the protection your enterprise requires.

ndm_definition: Non Disruptive Migration is a unique feature of VMAX ALL FLASH and VMAX3 arrays that enables customers to migrate
                existing applications to the latest VMAX arrays while continiously protecting their environments with remote and local replication.
                Non Disruptive Migration NDM is truely seamless to the host environments requiring no downtime of the storage or the application making
                in VMAX to VMAX All Flash migrations a uniquely seamless activity.

snapvx_definition: SnapVX is the latest and greatest Local replication available on VMAX3 and VMAX ALL FLASH.  SnapVX is
                   incredibly space efficient with minimal performance overhead.

snap_resources: Simply creating a targetless snapshot does not consume any system resources.
                The snapshot storage usage grows as the source device is updated as we are preserving the original data.


defined_meaning: When a target is linked, the defining process scans the entire target device. The
                 defining scan changes the pointers of each track on the target to share the
                 appropriate backend data for the point-in-time snapshot, which will typically be a
                 combination of source tracks and snapshot changes.

unmount_link: Yes. The target should be unmounted before issuing either the link or
              relink command and then remounted after the operation completes. This action
              also ensures that the host operating system does not cache any file system data.
              Generally speaking you should unmount any volumes before refreshing the data from the storage
              array so that the host inode tables are refreshed too.

rescan_volumes: There is no EMC TimeFinder requirement to rescan after a link or unlink operation.
                A rescan is only required when prestenting volumes to a host for the first time or if
                new volumes were added to the Storage Group.

compliance_details: There are {{ all_sg_count }} storage groups. {{ stable_sg_count }} are stable.
                    {{ marginal_sg_count }} are marginal and {{ critical_sg_count }} are critical.
                    Additionally, {{ no_slo_count }} storage groups have no S-L-O.

found_array: Selected VMAX array {{ symm_id }}


total_usable_capacity: Your Array is currently  {{ effective_used_capacity_percent }} percent of effective capacity consumed.


no_array: VMAX array {{ symm_id }} not found

processing_jobs_details: There is {{ jobs_processing_count }} pending job for this session. It's description is
                          {{ processing_jobs_list }} and its status is {{ status }}.

no_jobs: There no pending jobs for this session

host_list: There are {{ host_count }} hosts in your environment. These are {{ host_list }}.
           Which host would you like to provision storage to? Please state the name of the host and the capacity required.

no_hosts: There are no hosts configured in your environment

provision_storage: Provisioning a {{ size }} gigabyte volume to {{ host }}.

destroy_array: Initiating self-destruct sequence, A-K-A the mother of all D-U D-L events, in five, four,
               three, two, one. Just kidding. You can't do that with VMAX.

performance_stats: Your VMAX system is running {{HostIOs}} IOs per second totaling {{HostMBs}} megabytes per second.  Cash Utilization
                   is at {{PercentCacheWP}} and your average read response time is {{ReadResponseTime}} milliseconds.