No need to create entities when testing with a test cloud account. The scripts will create them for you. Hybrid's with a core account has to have the entities created though. This is done automatically if the core account is set up for rackspace monitoring.
I use raxmon with cloud10 to work with the monitoring api. I have the ~/.raxrc file set up for it. The username and apikey was set up from the account page.
| ############################################### | |
| # Set up tripleo-quickstart test environment | |
| ############################################### | |
| # Download the quickstart script | |
| git clone https://github.com/openstack/tripleo-quickstart | |
| cd tripleo-quickstart | |
| # Install some deps not done with the installer | |
| yum -y install tmux |
To keep things simple, I'm using my local fedora 29 install with libvirt. We will also use virtualbmc to act as an ipmi interface to allow stonith with pcs. For a quicker install, I'm just using a cloud image of Centos7 with a manual configdrive iso for each vm. We will use a couple of VMs for the cluster and a 3rd for the iscsi server. I have recently found myself dealing with OSP13 which uses PCS and ISCSI, so it will be a refresher for me as well as its been a few years.
Yes we could script and/or ansible all of this shit out, but this is a learning exercise.
| mv-*: macvlan bridge int | |
| br-*: linux bridge | |
| veth*1<->veth*2: veth pair | |
| bondX.YYY: vlan interface | |
| ######################################## | |
| # Newer machinectl config Before Install | |
| # Based on looking over an AIO install | |
| ######################################## |
| enp66s0f1 -> | |
| enp3s0f1 -> bond0 -> bond0.281 -> br-ipmi | |
| -> bond0.282 -> br-mgmt | |
| enp66s0f0 -> | |
| enp3s0f0 -> bond1 -> bond1.284 -> br-vxlan | |
| -> bond1.283 -> br-storage | |
| -> bond1.276 -> br-ironic -> (veth pair for ironic neutron flat network) | |
| -> bond1.1500 -> br-lbaas -> (veth pair for octavia neutron flat network) |
| ######################################################### | |
| # Current layout(moving away from the octavia weirdness) | |
| ######################################################### | |
| eth1 -> bond0(interface) -> br-vlan(host ip) -> (vlans defined in neutron unrelated to the base interfaces set up by support) | |
| -> bond0.EEE -> br-vxlan -> [ lxc veth6-0 -> lxc veth6-1 -> LXC Container ] | |
| -> bond0.AAA -> br-ironic -> [ lxc veth1-0 -> lxc veth1-1 -> LXC Container ] | |
| -> veth2-0 -> veth2-1 -> [ Neutron controlled bridge -> neutron AAA vlan int -> VM and/or neutron namespace ] | |
| -> bond0.BBB -> br-lbaas -> [ lxc veth3-0 -> lxc veth3-1 -> LXC Container ] | |
| -> veth4-0 -> veth4-1 -> [ Neutron controlled bridge -> neutron BBB vlan int -> VM and/or neutron namespace ] | |
| -> bond0.CCC -> br-mgmt -> [ lxc veth4-0 -> lxc veth4-1 -> LXC Container ] |
| # rpc-on-ironic network notes. | |
| # Generate the networks for your cluster. | |
| The ./scripts/gen-onironic-nets.py generates a yaml var file to use for the network setup. | |
| The vxlan ids at the top of each section is randomly generated. The vxlan_group for | |
| multicast traffic is also randomly generated. Here is what it looks like: | |
| vxlan_group: 239.51.50.107 |
| Still have some bugs to work out. Took two runs to complete. The Success's with times dumped below with the full runs below that. | |
| ############################################ | |
| # List of play times from build logs below | |
| ############################################ | |
| [Success]: Script bootstrap-ansible.sh completed without issue in 111.88s. | |
| [Success]: Script gen_user_secrets.yml completed without issue in 0.22s. | |
| [Success]: Play setup-hosts.yml completed without issue in 645.35s | |
| [Success]: Play unbound-install.yml completed without issue in 9.68s |
| ################################################ | |
| # Build out a new AIO environment for testing | |
| ################################################ | |
| (These steps are only used for testing the playbooks in an AIO environment. Can throw away after) | |
| (The customer's environment that we are initially testing on should already be in place) | |
| - Created an OnMetal IO v1 in IAD via the interface. | |