About Environments on Engine Yard Cloud

Environment is an overloaded term. Here at Engine Yard, when we refer to your "environment", we are talking about the group of instances that collectively run an application or set of applications.

An environment includes application instance(s), database instance(s), and possibly one or more utility instances. For more information about instances types, see About instances on Engine Yard Cloud.




Cluster Architecture


Referencing Environment Instances

For versions of the Engine Yard stack stable-v5.3.0.21 and stable-v4-2.0.117 and above internal hostnames for all instances in the local environment are automatically generated in /etc/hosts . This can be useful for configurations where you want to remotely access a specific instance through the Elastic IP of the application master (e.g. ssh tunnels) or if you want set a configuration to point to an instance with a specific role (e.g. ey-utility-redis).

Each type of instance has its own unique host name generation pattern:

  • Application Master: ey-app-master
  • DB Master: ey-db-master
  • Application Slaves: If there is only a single host it will be mapped to ey-app-slave. If there are multiple application slaves they will include an index number (starting at 0) based on the order in which the hosts are listed in the DNA.
  • Database Slaves: If there is only a single database slave it will be mapped to ey-db-slave. If there are multiple database slaves they will have an index number (starting at 0) based on the order in which the hosts are listed in the DNA. If a database slave also has an assigned name (e.g. backup) it will generate a corresponding hostname for that also (e.g. ey-db-slave-backup) resulting in more than one way to reference to a single replica.
  • Utility Instances: Will generate a name based on the assigned name of the instance using the pattern ey-utility-#{name}. If two utility instances share the same name an index number will be appended (starting at 0) based on the order in which the hosts are listed in the DNA.

The hosts entries will automatically be regenerated as part of the chef run for your environment. These occur when you click Apply on the dashboard, as well as when you add and remove instances from your environment.



# Application Master        ey-app-master

# Application Slaves        ey-app-slave-0        ey-app-slave-1

# Database Master         ey-db-master

# Database Replicas        ey-db-slave-brian_wilson        ey-db-slave-0        ey-db-slave-1

# Utility Instances        ey-utility-test2-0        ey-utility-test2-1        ey-utility-test1



If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.


Article is closed for comments.