en:
  vagrant_openstack:
    already_created: |-
      The server is already created.
    already_suspended: |-
      The server is already suspended
    deleting_server: |-
      Deleting server...
    finding_flavor: |-
      Finding flavor for server...
    finding_image: |-
      Finding image for server...
    finding_networks: |-
      Finding network(s) for server...
    launching_server: |-
      Launching a server with the following settings...
    not_created: |-
      The server hasn't been created yet. Run `vagrant up` first.
    ready: |-
      The server is ready!
    stopping_server: |-
      Stopping server...
    starting_server: |-
      Starting server...
    timeout: |-
      Timeout!
    trying_authentication: |-
      Trying authentication...
    rsync_folder: |-
      Rsyncing folder: %{hostpath} => %{guestpath}
    waiting_for_build: |-
      Waiting for the server to be built...
    waiting_for_ssh: |-
      Waiting for SSH to become available...
    waiting_stop: |-
      Waiting for the server to stop...
    warn_networks: |-
      Warning! The Openstack provider doesn't support any of the Vagrant
      high-level network configurations (`config.vm.network`). They
      will be silently ignored.

    config:
      password_required: |-
        A password is required.
      username_required: |-
        A username is required.
      invalid_uri: |-
        The value for %{key} is not a valid URI: %{uri}
      metadata_must_be_hash: |-
        Metadata must be a hash.
      keypair_name_required: |-
        A keypair name is required.

    errors:
      default: |-
        %{message}
      authentication_required: |-
        Authentication token is missing or no longer valid.
      create_bad_state: |-
        While creating the server, it transitioned to an unexpected
        state: '%{state}', instead of properly booting. Run `vagrant status`
        to find out what can be done about this state, or `vagrant destroy`
        if you want to start over.
      no_matching_flavor: |-
        No matching flavor was found! Please check your flavor setting
        to make sure you have a valid flavor chosen.
      no_matching_image: |-
        No matching image was found! Please check your image setting to
        make sure you have a valid image chosen.
      sync_method_error: |-
        Value '%{sync_method_value}' is not allowed for 'sync_method' configuration parameter. Valid values are 'rsync' and 'none'
      rsync_error: |-
        There was an error when attemping to rsync a share folder.
        Please inspect the error message below for more info.

        Host path: %{hostpath}
        Guest path: %{guestpath}
        Error: %{stderr}
      ssh_unavailble: |-
        SSH server anavailable on instance %{host}. You should maybe increase the timeout value which currently is %{timeout} second(s).

    states:
      short_active: |-
        active
      long_active: |-
        The server is up and running. Run `vagrant ssh` to access it.
      short_build: |-
        building
      long_build: |-
        The server is currently being built. You must wait for this to
        complete before you can access it. You can delete the server, however,
        by running `vagrant destroy`.
      short_error: |-
        error
      long_error: |-
        The server is in an erroneous state. Contact your OpenStack administrator
        or destroy the machine with `vagrant destroy`.
      short_hard_reboot: |-
        hard reboot
      long_hard_reboot: |-
        The server is hard rebooting. This is equivalent to pulling the power plug
        on a physical server, plugging it back in, and rebooting it.
      short_password: |-
        password reset
      long_password: |-
        The password is being reset on the server.
      short_reboot: |-
        reboot
      long_reboot: |-
        The server is in a soft reboot state. A reboot command was passed to the operating system.
      short_rebuild: |-
        rebuild
      long_rebuild: |-
        The server is currently being rebuilt from an image.
      short_rescue: |-
        rescue
      long_rescue: |-
        The server is in rescue mode.
      short_resize: |-
        resize
      long_resize: |-
         Server is performing the differential copy of data that changed during
         its initial copy. Server is down for this stage.
      short_revert_resize: |-
        revert resize
      long_revert_resize: |-
        The resize or migration of a server failed for some reason. The destination
        server is being cleaned up and the original source server is restarting.
      short_shutoff: |-
        shutoff
      long_shutoff: |-
        The virtual machine (VM) was powered down by the user, but not through the
        OpenStack Compute API. For example, the user issued a shutdown -h command
        from within the server instance. If the OpenStack Compute manager detects
        that the VM was powered down, it transitions the server instance to the
        SHUTOFF status. If you use the OpenStack Compute API to restart the instance,
        the instance might be deleted first, depending on the value in the
        shutdown_terminate database field on the Instance model.
      short_suspended: |-
        suspended
      long_suspended: |-
        The server is suspended, either by request or necessity. This status appears
        for only the following hypervisors: XenServer/XCP, KVM, and ESXi.
      short_unknown: |-
        unknown
      long_unknown: |-
        The state of the server is unknown. Contact your cloud provider.
      short_verify_resize: |-
        verify resize
      long_verifiy_resize: |-
        System is awaiting confirmation that the server is operational after a move or resize.
      short_not_created: |-
        not created
      long_not_created: |-
        The server is not created. Run `vagrant up` to create it.

    client:
      looking_for_available_endpoints: |-
        Looking for available endpoints...
      multiple_endpoint: |-
        %{size} endpoints are available for service '%{type}' but only the first one will be used
      authentication: |-
        Authentication on project %{project} with user %{user}