Chapter 6. Deploy the edge without storage

Procedure

1. Log in to the undercloud as the stack user.

2. Source the stackrc file:

   [stack@director ~]$ source ~/stackrc

3. Generate an environment file ~/dcn0/dcn0-images-env.yaml[d]:

   sudo[e] openstack tripleo container image prepare \
   -e containers.yaml \
   --output-env-file ~/dcn0/dcn0-images-env.yaml

4. Generate a roles file for the edge location. Generate roles for the edge location using roles appropriate for your environment:

   (undercloud)$ openstack overcloud roles \
    generate Compute \
    -o /home/stack/dcn0/dcn0_roles.yaml

5. If you are using ML2/OVS for networking overlay, you must edit the Compute role include the NeutronDhcpAgent and NeutronMetadataAgent services:

   1. Create a role file for the Compute role:

      openstack overcloud roles \
      generate Compute \
      -o /home/stack/dcn0/dcn0_roles.yaml

   2. Edit the /home/stack/dcn0/dcn0_roles.yaml file to include the NeutronDhcpAgent and NeutronMetadataAgent services:

      ...
          - OS::TripleO::Services::MySQLClient
          - OS::TripleO::Services::NeutronBgpVpnBagpipe
      +   - OS::TripleO::Services::NeutronDhcpAgent
      +   - OS::TripleO::Services::NeutronMetadataAgent
          - OS::TripleO::Services::NeutronLinuxbridgeAgent
          - OS::TripleO::Services::NeutronVppAgent
          - OS::TripleO::Services::NovaAZConfig
          - OS::TripleO::Services::NovaCompute
      ...

      For more information, see Preparing for a routed provider network.

6. Provision networks for the overcloud. This command takes a definition file for overcloud networks as input. You must use the output file in your command to deploy the overcloud:

   (undercloud)$ openstack overcloud network provision \
   --output /home/stack/dcn0/overcloud-networks-deployed.yaml \
   /home/stack/dcn0/network_data.yaml

   Important

   If your network_data.yaml template includes additional networks which were not included when you provisioned networks for the central location, then you must re-run the network provisioning command on the central location:

   (undercloud)$ openstack overcloud network provision \
   --output /home/stack/central/overcloud-networks-deployed.yaml \
   /home/stack/central/network_data.yaml

7. Provision bare metal instances. This command takes a definition file for bare metal nodes as input. You must use the output file in your command to deploy the overcloud:

   (undercloud)$ openstack overcloud node provision \
   --stack dcn0 \
   --network-config \
   -o /home/stack/dcn0/deployed_metal.yaml \
   ~/overcloud-baremetal-deploy.yaml

8. Configure the naming conventions for your site in the site-name.yaml environment file.

   parameter_defaults:
       NovaComputeAvailabilityZone: dcn0
       ControllerExtraConfig:
           nova::availability_zone::default_schedule_zone: dcn0
       NovaCrossAZAttach: false

9. Deploy the stack for the dcn0 edge site:

   openstack overcloud deploy \
   --deployed-server \
   --stack dcn0 \
   --templates /usr/share/openstack-tripleo-heat-templates/ \
   -r /home/stack/dcn0/dcn0_roles.yaml \
   -n /home/stack/network_data.yaml \
   -e /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml \
   -e /usr/share/openstack-tripleo-heat-templates/environments/nova-az-config.yaml \
   -e /home/stack/overcloud-deploy/central/central-export.yaml \
   -e /home/stack/dcn0/overcloud-networks-deployed.yaml \
   -e /home/stack/dcn0/overcloud-vip-deployed.yaml \
   -e /home/stack/dcn0/deployed_metal.yaml

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the stackrc credentials file:

   $ source ~/stackrc

3. Include the NovaImageTypeExcludeList parameter in one of your custom environment files:

   parameter_defaults:
     NovaImageTypeExcludeList:
           - raw

4. Include the environment file that contains the NovaImageTypeExcludeList parameter in the overcloud deployment command, along with any other environment files relevant to your deployment:

   openstack overcloud deploy --templates \
   -n network_data.yaml \
   -r roles_data.yaml \
   -e <environment_files> \
   -e <new_environment_file>