Skip to content

Latest commit

 

History

History
31 lines (22 loc) · 1.7 KB

EurekaAsgard.md

File metadata and controls

31 lines (22 loc) · 1.7 KB
Raw

Eureka/Asgard Integration

If Asgard knows about Eureka it will enhance many of the pages with Eureka information. The link above goes into more specific of how the integratin works. The following steps are to enable that integregation in a way that is compatible with the rest of this tutorial.

Build/Bake

If you don't have the eureka--frontend ELB's DNS Name handy, go back to Asgard and find it. Make sure to use that DNS name below instead of just copying like you have in previous steps.

EUREKA_ELB=*ELB DNS NAME from Step 14*
cd ~/zerotocloud
./gradlew :asgard:bake

To ensure that the EUREKA_ELB var is set on future attempts, it is recommended to add an export to the .bash_profile on the jumphost.

Deploy

  1. From Asgard, go to Cluster | Clusters.
  2. Find the Asgard cluster, and select it. The path should look like /us-west-2/cluster/show/asgard.
  3. There should be a "Create Next Group" box on the right. This is where the next ASG is staged.
  4. Select AMI Image Id, select most recently built.
  5. Click "Create Next Group asgard-v000". A task page will come up to show the progress of calls to Amazon.
  6. Return to the Asgard Cluster page, there is a link at the top and bottom of the page.
  7. Click the "Disable" button in the first ASG.
  8. Reload the Asgard UI.
  9. When visiting a Cluster page, you will now see a Eureka column and a "Wait for Eureka health check pass" checkbox for new clusters.

FYI, this can not be done as a Rolling Push, since Asgard will disable creation of new instances while killing itself.