Chapter 3. Associating Objects with the Default Organization and Location

3.1. Creating a New Domain

For Web UI Users

Navigate to Infrastructure → Domains and click New Domain. The UI provides a set of fields where you can input details for the domain:

  • In the Domain tab:

    • Name - The domain name. In this example, this is " example.com ".
    • Description - A plain text description of the domain. For this example: ACME’s example domain.
    • DNS Capsule - The capsule to use for DNS assignments. For this example, use the Satellite Server’s Integrated Capsule.

  • In the Locations tab:

    • Select the locations that use this domain. For example, select the New York location.

  • In the Organizations tab:

    • Select the organizations that use this domain. For example, select ACME.

For CLI Users

Create the domain with the following command: 

# hammer domain create --name "example.com" \
--description "ACME's example domain" \
--dns_id 1 --locations "New York" \
--organizations "ACME"
Note

In this example, the --dns-id option uses 1, which is the ID of the Satellite Server’s Integrated Capsule.

3.2. Associating the Domain with the Default Organization

Associating the Domain with the Default Organization Using the Web UI

  1. On the Main Menu, click Infrastructure → Domains.
  2. Select the domain in the Description column.
  3. On the Locations tab, click Default_Location to add it to the Selected items list.
  4. On the Organizations tab, click Default_Organization to add it to the Selected items list.
  5. Click Submit.

Associating the Domain with the Default Organization Using Hammer ClI

  1. Associate the domain to your organization. 

    $ hammer organization add-domain --name $ORG --domain domain_name

  2. Associate the domain to your location. 

    $ hammer location add-domain --name $LOCATION --domain domain-name

3.3. Configuring the Subnet

Configuring the Subnet Using the Web UI

  1. On the Main Menu, click Infrastructure → Subnets.

  2. Click New Subnet and enter the information specific to your environment.

    1. If you use DHCP, enter the following information:

      • Name: Provisioning_Net
      • Network address: 172.17.13.0
      • Network mask: 255.255.255.0
      • Gateway Address: 172.17.13.1
      • Primary DNS Server: 172.17.13.2
      • Secondary DNS Server: Leave blank
      • IPAM: None
      • Start of IP Range: 172.17.13.100
      • End of IP Range: 172.17.13.150
      • VLAN ID: Leave blank
      • Boot Mode: DHCP

    2. If you use static IP addresses, enter the following information:

      • Name: Provisioning_Net
      • Network address: 172.17.13.0
      • Network mask: 255.255.255.0
      • Gateway Address: 172.17.13.1
      • Primary DNS Server: 172.17.13.2
      • Secondary DNS Server: Leave blank
      • IPAM: None
      • Start of IP Range: 172.17.13.100
      • End of IP Range: 172.17.13.150
      • VLAN ID: Leave blank
      • Boot Mode: Static
  3. Click Submit.
  4. Click Provisioning_Net to edit the subnet.
  5. On the Domains tab, select example.org.
  6. On the Capsules tab, change the TFTP and Discovery Proxy capsule to reflect the host name of the Satellite Server.
  7. On the Locations tab, select Default_Location under All items to associate the domain with the default location.
  8. On the Organizations tab, select Default_Organization under All items to associate the domain with the default organization.

Configuring the Subnet Using Hammer CLI

  1. Create a subnet.

    1. Create a subnet using DHCP. 

      # hammer subnet create --name Provisioning_Net \
--organizations 'RedHat' \
--locations 'RDU' \
--domain-ids 1 \
--boot-mode DHCP \
--network 172.17.13.0 \
--mask 255.255.255.0 \
--ipam None \
--dns-primary 172.17.13.1 \
--gateway 172.17.13.1 \
--from 172.17.13.100 \
--to 172.17.13.150 \
--tftp-id 1

    2. Create a subnet using static IP addresses. 

      # hammer subnet create --name Provisioning_Net \
--organizations 'RedHat' \
--locations 'RDU' \
--domain-ids 1 \
--boot-mode Static \
--network 172.17.13.0 \
--mask 255.255.255.0 \
--ipam None \
--dns-primary 172.17.13.1 \
--gateway 172.17.13.1 \
--from 172.17.13.100 \
--to 172.17.13.150 \
--tftp-id 1
      Note

      You cannot set the discovery proxy using Hammer CLI.