Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add followers to AWS Cluster demo #32

Merged
merged 1 commit into from
Mar 12, 2019
Merged

Add followers to AWS Cluster demo #32

merged 1 commit into from
Mar 12, 2019

Conversation

micahlee
Copy link
Contributor

@micahlee micahlee commented Mar 8, 2019

This PR updates the AWS Cluster demo to add AWS instances for followers and a script to optionally configure them.

Connected to #33

@micahlee micahlee self-assigned this Mar 11, 2019

mkdir -p $SEED_DIR

# Create Standby Seed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment should read Create Follower Seed.

-o "StrictHostKeyChecking no" \
core@$MASTER_1_PUBLIC /bin/bash << EOF
docker exec conjur-appliance bash -c " \
evoke seed follower "$LB_FOLLOWER_DNS" "$LB_DNS" > "/opt/conjur/backup/$filename"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you include $LB_DNS here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last I checked on it, it was still not crystal clear what is the correct way to setup certificates and domain names for an autofailover cluster to work with load balancers. So I was explicit about what the master address should be for the follower to avoid any issues while preparing the PCF demo video.

It's possible that it's not necessary. I can create an issue to investigate removing it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#35


create_follower_seed "follower-seed.tar"

configure_followers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In some other projects, we adhere to Google shell guidelines that state to create a main function at the top of the file and call it at the bottom so that it's easy to find the program start. I know the way you did this is more consistent with the other files in this repo so maybe it's better to follow the established standard here but thought it was worth raising.

Copy link
Contributor Author

@micahlee micahlee Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, I did not know about this! I'm not going to change it now because I would need to run through it all again to make sure I didn't break anything. I will create an issue to refactor this according to these guidelines next time I'm in here. Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#34

@micahlee
Copy link
Contributor Author

Thanks @jtuttle! I fixed the typo and added follow up issues for the others. Let me know what you think!

@jtuttle jtuttle merged commit 99be56f into master Mar 12, 2019
@jtuttle jtuttle deleted the aws-cluster-followers branch March 12, 2019 17:51
jvanderhoof pushed a commit that referenced this pull request Sep 9, 2022
Quickstart Flow Automation in Actions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants