Removing renamed build.sh

This commit is contained in:
desrod 2018-04-20 14:13:25 -04:00
parent f4c4371801
commit 10b8331f21

283
build.sh
View File

@ -1,283 +0,0 @@
#!/bin/bash
required_bins=( ip jq sudo uuid )
check_bins() {
# Append any needed binaries we need to check for, to our list
if [[ $1 ]]; then
required_bins+=("$1")
fi
for binary in "${required_bins[@]}"; do
if ! [ -x "$(command -v "$binary")" ]; then
printf "Error: Necessary program '%s' is not installed. Please fix, aborting now.\n\n" "$binary" >&2
exit 1
fi
done
}
# Initialize some vars we'll reuse later in the build, bootstrap
init_variables() {
# This is the user who 'maas' uses when commissioning nodes
virsh_user="ubuntu"
maas_profile="admin"
maas_pass="openstack"
# This is the user whose keys get imported into maas by default
launchpad_user="setuid"
maas_system_ip="$(hostname -I | awk '{print $1}')"
maas_bridge_ip="$(ip addr show virbr0 | awk '/inet/ {print $2}' | cut -d/ -f1)"
maas_endpoint="http://$maas_bridge_ip:5240/MAAS"
# This is the proxy that MAAS itself uses (the "internal" MAAS proxy)
maas_local_proxy="http://$maas_bridge_ip:8000"
maas_upstream_dns="1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4"
# This is an upstream, peer proxy that MAAS may need to talk to (tinyproxy in this case)
# maas_upstream_proxy="http://$maas_system_ip:8888"
virsh_chassis="qemu+ssh://${virsh_user}@${maas_system_ip}/system"
maas_packages=(maas maas-cli maas-proxy maas-dhcp maas-dns maas-rack-controller maas-region-api maas-common)
pg_packages=(postgresql-9.5 postgresql-client postgresql-client-common postgresql-common)
}
remove_maas() {
# Drop the MAAS db ("maasdb"), so we don't risk reusing it
sudo -u postgres psql -c "select pg_terminate_backend(pid) from pg_stat_activity where datname='maasdb'"
sudo -u postgres psql -c "drop database maasdb"
# Remove everything, start clean and clear from the top
sudo DEBIAN_FRONTEND=noninteractive apt-get -y remove --purge "${maas_packages[@]}" "${pg_packages[@]}" && \
sudo apt-get -fuy autoremove
# Yes, they're removed but we want them PURGED, so this becomes idempotent
for package in "${maas_packages[@]}" "${pg_packages[@]}"; do
sudo dpkg -P "$package"
done
}
install_maas() {
# This is separate from the removal, so we can handle them atomically
# sudo apt -fuy --reinstall install maas maas-cli jq tinyproxy htop vim-common
sudo apt -fuy --reinstall install "${maas_packages[@]}" "${pg_packages[@]}"
}
purge_admin_user() {
read -r -d '' purgeadmin <<EOF
with deleted_user as (delete from auth_user where username = '$maas_profile' returning id),
deleted_token as (delete from piston3_token where user_id = (select id from deleted_user)),
deleted_ssh_id as (delete from maasserver_sshkey where user_id = (select id from deleted_user)),
deleted_userprofile as (delete from maasserver_userprofile where user_id = (select id from deleted_user))
delete from piston3_consumer where user_id = (select id from deleted_user);
EOF
sudo -u postgres psql -c "$purgeadmin" maasdb
}
build_maas() {
# maas_endpoint=$(maas list | awk '{print $2}')
# Create the initial 'admin' user of MAAS, purge first!
purge_admin_user
sudo maas createadmin --username "$maas_profile" --password "$maas_pass" --email "$maas_profile"@"$maas_pass" --ssh-import lp:"$launchpad_user"
maas_api_key="$(sudo maas-region apikey --username=$maas_profile | tee ~/.maas-api.key)"
# Fetch the MAAS API key, store to a file for later reuse, also set this var to that value
maas login "$maas_profile" "$maas_endpoint" "$maas_api_key"
maas_system_id="$(maas $maas_profile nodes read hostname="$HOSTNAME" | jq -r '.[].interface_set[0].system_id')"
# Inject the maas SSH key
maas_ssh_key=$(cat ~/.ssh/maas_rsa.pub)
maas $maas_profile sshkeys create "key=$maas_ssh_key"
# Update settings to match our needs
maas $maas_profile maas set-config name=network_discovery value=disabled
maas $maas_profile maas set-config name=active_discovery_interval value=0
maas $maas_profile maas set-config name=kernel_opts value="console=ttyS0,115200 console=tty0,115200 elevator=cfq intel_iommu=on iommu=pt debug nosplash scsi_mod.use_blk_mq=1 dm_mod.use_blk_mq=1 enable_mtrr_cleanup mtrr_spare_reg_nr=1 systemd.log_level=debug"
maas $maas_profile maas set-config name=maas_name value=us-east
maas $maas_profile maas set-config name=upstream_dns value="$maas_upstream_dns"
maas $maas_profile maas set-config name=enable_analytics value=false
maas $maas_profile maas set-config name=enable_http_proxy value=true
maas $maas_profile maas set-config name=enable_third_party_drivers value=false
maas $maas_profile ipranges create type=dynamic start_ip=192.168.100.100 end_ip=192.168.100.200 comment='This is the reserved range for MAAS nodes'
sleep 4
maas $maas_profile vlan update fabric-1 0 dhcp_on=True primary_rack="$maas_system_id"
# This is needed, because it points to localhost by default and will fail to
# commission/deploy in this state
sudo maas-rack config --region-url "http://$maas_bridge_ip:5240/MAAS/" && sudo service maas-rackd restart
}
bootstrap_maas() {
# Import the base images; this can take some time
echo "Importing boot images, please be patient, this may take some time..."
maas $maas_profile boot-resources import
until [ "$(maas $maas_profile boot-resources is-importing)" = false ]; do sleep 3; done;
# Add a chassis with nodes we want to build against
maas $maas_profile machines add-chassis chassis_type=virsh prefix_filter=maas-node hostname="$virsh_chassis"
# This is necessary to allow MAAS to quiesce the imported chassis
echo "Pausing while chassis is imported..."
sleep 10
# Commission those nodes (requires that image import step has completed)
maas "$maas_profile" machines accept-all
# Grab the first node in the chassis and commission it
# maas_node=$(maas $maas_profile machines read | jq -r '.[0].system_id')
# maas "$maas_profile" machine commission -d "$maas_node"
# Acquire all images marked "Ready"
maas "$maas_profile" machines allocate
# Deploy the node you just commissioned and acquired
# maas "$maas_profile" machine deploy $maas_node
}
# These are for juju, adding a cloud matching the customer/reproducer we need
add_cloud() {
rand_uuid=$(uuid -F siv)
cloud_name="$1"
maas_api_key=$(cat ~/.maas-api.key)
cat > clouds-"$rand_uuid".yaml <<EOF
clouds:
$cloud_name:
type: maas
auth-types: [ oauth1 ]
description: MAAS cloud for $cloud_name
# endpoint: ${maas_endpoint:0:-8}
endpoint: $maas_endpoint
EOF
cat > credentials-"$rand_uuid".yaml <<EOF
credentials:
$cloud_name:
$cloud_name-auth:
auth-type: oauth1
maas-oauth: $maas_api_key
EOF
cat > config-"$rand_uuid".yaml <<EOF
automatically-retry-hooks: true
default-series: xenial
http-proxy: $maas_local_proxy
https-proxy: $maas_local_proxy
apt-http-proxy: $maas_local_proxy
apt-https-proxy: $maas_local_proxy
EOF
echo "Adding cloud............: $cloud_name"
juju add-cloud --replace "$cloud_name" clouds-"$rand_uuid".yaml
echo "Adding credentials for..: $cloud_name"
juju add-credential --replace "$cloud_name" -f credentials-"$rand_uuid".yaml
echo "Details for cloud.......: $cloud_name..."
juju clouds --format json | jq --arg cloud "$cloud_name" '.[$cloud]'
juju bootstrap "$cloud_name" --debug --config=config-"$rand_uuid".yaml
# Since we created ephemeral files, let's wipe them out. Comment if you want to keep them around
if [[ $? = 0 ]]; then
rm -f clouds-"$rand_uuid".yaml credentials-"$rand_uuid".yaml config-"$rand_uuid".yaml
fi
}
# Let's get rid of that cloud and clean up after ourselves
destroy_cloud() {
cloud_name="$1"
juju clouds --format json | jq --arg cloud "$cloud_name" '.[$cloud]'
juju remove-cloud "$cloud_name"
}
show_help() {
echo "
-a <cloud_name> Do EVERYTHING (maas, juju cloud, juju bootstrap)
-b Build out and bootstrap a new MAAS
-c <cloud_name> Add a new cloud + credentials
-i Just install the dependencies and exit
-j <name> Bootstrap the Juju controller called <name>
-n Create MAAS kvm nodes (to be imported into chassis)
-r Remove the entire MAAS server + dependencies
-t <cloud_name> Tear down the cloud named <cloud_name>
"
}
if [ $# -eq 0 ]; then
printf "%s needs options to function correctly. Valid options are:" "$0"
show_help
exit 0
fi
init_variables
while getopts ":a:bc:ij:nt:r" opt; do
case $opt in
a )
check_bins
remove_maas
install_maas
build_maas
bootstrap_maas
add_cloud "$OPTARG"
;;
b )
echo "Building out a new MAAS server"
# install_maas
install_maas
build_maas
bootstrap_maas
exit 0
;;
c )
check_bins maas
init_variables
add_cloud "$OPTARG"
;;
i )
echo "Installing MAAS and PostgreSQL dependencies"
install_maas
exit 0
;;
j )
echo "Bootstrapping Juju controller $OPTARG"
add_cloud "$OPTARG"
exit 0
;;
r )
remove_maas
exit 0
;;
t )
destroy_cloud "$OPTARG"
exit 0
;;
\? )
printf "Unrecognized option: -%s. Valid options are:" "$OPTARG" >&2
show_help
exit 1
;;
: )
printf "Option -%s needs an argument.\n" "$OPTARG" >&2
show_help
echo ""
exit 1
;;
esac
done