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

Workflow to setup Windows Domain with DC and hosts #168

Merged
merged 35 commits into from
Aug 29, 2024

Conversation

zjleblanc
Copy link
Contributor

@zjleblanc zjleblanc commented Aug 12, 2024

This change includes a workflow to provide users a small Windows domain with a domain controller and two windows hosts. The added workflow leverages pre-existing job templates from the cloud and windows content:

  • Create an AWS Keypair
  • Create a VPC
  • Create VMs (domain controller, domain computers)
  • Create Domain
  • Join Domain
windows_domain_workflow

@zjleblanc zjleblanc closed this Aug 19, 2024
@zjleblanc zjleblanc reopened this Aug 19, 2024
@zjleblanc
Copy link
Contributor Author

Latest success - running E2E after @jce-redhat consolidation to common
Screenshot 2024-08-22 at 10 31 52 AM

Copy link
Collaborator

@jce-redhat jce-redhat left a comment

Choose a reason for hiding this comment

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

minor comments, testing the workflow was successful

gather_facts: false

tasks:
- name: Wait 600 seconds for target connection to become reachable/usable
Copy link
Collaborator

Choose a reason for hiding this comment

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

cosmetic: task says 600 seconds but default value in the task is 300

Comment on lines +10 to +11
delay: "{{ wait_for_delay_sec | default(0) }}"
sleep: "{{ wait_for_sleep_sec | default(1) }}"
Copy link
Collaborator

Choose a reason for hiding this comment

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

if you know the initial connection after building the systems will take a while, you might want to increase the delay default to what you think the minimum time would be. i'd suggest also increasing the sleep default to 5 or 10 just to reduce the connection load on the system.

## Suggested Usage

**Setup Active Directory Domain** - One-click domain setup, infrastructure included.
Copy link
Collaborator

Choose a reason for hiding this comment

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

what is meant by "infrastructure included?"

type: multiplechoice
variable: create_vm_aws_region
required: true
default: us-east-2
Copy link
Collaborator

Choose a reason for hiding this comment

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

in other surveys i don't think we set a default for AWS region, but i like the idea so i'll put in an issue to do so.

Copy link
Collaborator

@jce-redhat jce-redhat left a comment

Choose a reason for hiding this comment

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

looks good, we'll just have to remember to remove the known issues section once the intermittent connectivity issue gets resolved.

@jce-redhat jce-redhat merged commit 8a99b66 into ansible:main Aug 29, 2024
1 check passed
This pull request was closed.
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.

4 participants