devtest_seed

1. Create and start your seed VM. This script invokes diskimage-builder with suitable paths and options to create and start a VM that contains an all-in-one OpenStack cloud with the baremetal driver enabled, and preconfigures it for a development environment. Note that the seed has minimal variation in it’s configuration: the goal is to bootstrap with a known-solid config.

   cd $TRIPLEO_ROOT/tripleo-image-elements/elements/seed-stack-config
   # Sets:
   # - bm node arch
   # - bm power manager
   # - ssh power host
   # - ssh power key
   # - ssh power user
   TMP=`mktemp`
   jq -s '.[1] as $config |(.[0].nova.baremetal |= (.virtual_power.user=$config["ssh-user"]|.virtual_power.ssh_host=$config["host-ip"]|.virtual_power.ssh_key=$config["ssh-key"]|.arch=$config.arch|.power_manager=$config.power_manager))| .[0]' config.json $TE_DATAFILE > $TMP
   mv $TMP config.json
   
   
   cd $TRIPLEO_ROOT
       boot-seed-vm -a $NODE_ARCH $NODE_DIST neutron-dhcp-agent 2>&1 | \
           tee $TRIPLEO_ROOT/dib-seed.log

   boot-seed-vm will start a VM and copy your SSH pub key into the VM so that you can log into it with ‘ssh stack@192.0.2.1‘.

   The IP address of the VM is printed out at the end of boot-seed-vm, or you can query the testenv json which is updated by boot-seed-vm:

   SEED_IP=$(OS_CONFIG_FILES=$TE_DATAFILE os-apply-config --key seed-ip --type netaddress)

2. Add a route to the baremetal bridge via the seed node (we do this so that your host is isolated from the networking of the test environment.

   # These are not persistent, if you reboot, re-run them.
   ROUTE_DEV=$(OS_CONFIG_FILES=$TE_DATAFILE os-apply-config --key seed-route-dev --type netdevice --key-default virbr0)
   sudo ip route del 192.0.2.0/24 dev $ROUTE_DEV || true
   sudo ip route add 192.0.2.0/24 dev $ROUTE_DEV via $SEED_IP

3. Mask the seed API endpoint out of your proxy settings

   export no_proxy=$no_proxy,192.0.2.1

4. If you downloaded a pre-built seed image you will need to log into it and customise the configuration within it. See footnote [1].)

5. Setup a prompt clue so you can tell what cloud you have configured. (Do this once).

   source $TRIPLEO_ROOT/tripleo-incubator/cloudprompt

6. Source the client configuration for the seed cloud.

   source $TRIPLEO_ROOT/tripleo-incubator/seedrc

7. Perform setup of your seed cloud.

   wait_for 30 10 ping -c 1 192.0.2.1
   ssh-keyscan -t rsa 192.0.2.1 >>~/.ssh/known_hosts
   init-keystone -p unset unset 192.0.2.1 admin@example.com root@192.0.2.1
   setup-endpoints 192.0.2.1 --glance-password unset --heat-password unset --neutron-password unset --nova-password unset
   keystone role-create --name heat_stack_user
   
   echo "Waiting for nova to initialise..."
   wait_for 30 10 nova list
   user-config
   
   setup-neutron 192.0.2.2 192.0.2.3 192.0.2.0/24 192.0.2.1 192.0.2.1 ctlplane

8. Register “bare metal” nodes with nova and setup Nova baremetal flavors. When using VMs Nova will PXE boot them as though they use physical hardware. If you want to create the VM yourself see footnote [2] for details on its requirements. If you want to use real baremetal see footnote [3] for details.

   SEED_MACS=$(OS_CONFIG_FILES=$TE_DATAFILE os-apply-config --key node-macs --type raw | awk '{ print $1 }')
   SEED_PM_IPS=$(OS_CONFIG_FILES=$TE_DATAFILE os-apply-config --key node-pm-ips --type raw --key-default '' | awk '{ print $1 }')
   SEED_PM_USERS=$(OS_CONFIG_FILES=$TE_DATAFILE os-apply-config --key node-pm-users --type raw --key-default '' | awk '{ print $1 }')
   SEED_PM_PASSWORDS=$(OS_CONFIG_FILES=$TE_DATAFILE os-apply-config --key node-pm-passwords --type raw --key-default '' | awk '{ print $1 }')
   NODE_ARCH=$(os-apply-config -m $TE_DATAFILE --key arch --type raw)
   setup-baremetal $NODE_CPU $NODE_MEM $NODE_DISK $NODE_ARCH "$SEED_MACS" seed "$SEED_PM_IPS" "$SEED_PM_USERS" "$SEED_PM_PASSWORDS"

   If you need to collect the MAC address separately, see scripts/get-vm-mac.

Footnotes

[1]

Customize a downloaded seed image. If you downloaded your seed VM image, you may need to configure it. Setup a network proxy, if you have one (e.g. 192.168.2.1 port 8080) # Run within the image! echo << EOF >> ~/.profile export no_proxy=192.0.2.1 export http_proxy=http://192.168.2.1:8080/ EOF Add an ~/.ssh/authorized_keys file. The image rejects password authentication for security, so you will need to ssh out from the VM console. Even if you don’t copy your authorized_keys in, you will still need to ensure that /home/stack/.ssh/authorized_keys on your seed node has some kind of public SSH key in it, or the openstack configuration scripts will error. You can log into the console using the username ‘stack’ password ‘stack’.

[2]

Requirements for the “baremetal node” VMs If you don’t use create-nodes, but want to create your own VMs, here are some suggestions for what they should look like. each VM should have 1 NIC eth0 should be on brbm record the MAC addresses for the NIC of each VM. give each VM no less than 2GB of disk, and ideally give them more than NODE_DISK, which defaults to 20GB 1GB RAM is probably enough (512MB is not enough to run an all-in-one OpenStack), and 768M isn’t enough to do repeated deploys with. if using KVM, specify that you will install the virtual machine via PXE. This will avoid KVM prompting for a disk image or installation media.

[3]

Notes when using real bare metal If you want to use real bare metal see the following. When calling setup-baremetal you can set the MAC, IP address, user, and password parameters which should all be space delemited lists that correspond to the MAC addresses and power management commands your real baremetal machines require. See scripts/setup-baremetal for details. If you see over-mtu packets getting dropped when iscsi data is copied over the control plane you may need to increase the MTU on your brbm interfaces. Symptoms that this might be the cause include: iscsid: log shows repeated connection failed errors (and reconnects) dmesg shows: openvswitch: vnet1: dropped over-mtu packet: 1502 > 1500