Installing Spinnaker on Openstack

Configure the file and run locally on ubuntu, which is downloaded from openstack.

ubuntu@spinnaker:~$ cat vmware-cloud-openrc.sh

[2]+  Stopped                 vim vmware-cloud-openrc.sh
ubuntu@spinnaker:~$ rm vmware-cloud-openrc.sh/
rm: cannot remove ‘vmware-cloud-openrc.sh/’: Is a directory
ubuntu@spinnaker:~$ rm -r vmware-cloud-openrc.sh/
ubuntu@spinnaker:~$ ls
]  InstallHalyard.sh  minio
ubuntu@spinnaker:~$ vim vmware-cloud-openrc.sh
ubuntu@spinnaker:~$ cat vm
cat: vm: No such file or directory
ubuntu@spinnaker:~$ cat vmware-cloud-openrc.sh
#!/usr/bin/env bash

# To use an OpenStack cloud you need to authenticate against the Identity
# service named keystone, which returns a **Token** and **Service Catalog**.
# The catalog contains the endpoints for all services the user/tenant has
# access to - such as Compute, Image Service, Identity, Object Storage, Block
# Storage, and Networking (code-named nova, glance, keystone, swift,
# cinder, and neutron).
#
# *NOTE*: Using the 3 *Identity API* does not necessarily mean any other
# OpenStack API is version 3. For example, your cloud provider may implement
# Image API v1.1, Block Storage API v2, and Compute API v2.0. OS_AUTH_URL is
# only for the Identity API served through keystone.
export OS_AUTH_URL=http://10.9.80.50:5000/v3

# With the addition of Keystone we have standardized on the term **project**
# as the entity that owns the resources.
export OS_PROJECT_ID=af33d031da1743b199e6f90b75ca3d6d
export OS_PROJECT_NAME="vmware-cloud"
export OS_USER_DOMAIN_NAME="Default"
if [ -z "$OS_USER_DOMAIN_NAME" ]; then unset OS_USER_DOMAIN_NAME; fi

# unset v2.0 items in case set
unset OS_TENANT_ID
unset OS_TENANT_NAME

# In addition to the owning entity (tenant), OpenStack stores the entity
# performing the action as the **user**.
export OS_USERNAME="karthik1"

# With Keystone you pass the keystone password.
echo "Please enter your OpenStack Password for project $OS_PROJECT_NAME as user $OS_USERNAME: "
read -sr OS_PASSWORD_INPUT
export OS_PASSWORD=$OS_PASSWORD_INPUT

# If your configuration has multiple regions, we set that information here.
# OS_REGION_NAME is optional and only valid in certain environments.
export OS_REGION_NAME="us-east"
# Don't leave a blank variable, unset it if it was empty
if [ -z "$OS_REGION_NAME" ]; then unset OS_REGION_NAME; fi

export OS_INTERFACE=public
export OS_IDENTITY_API_VERSION=3

ubuntu@spinnaker:~$

Enter the openstack login password for API access:

ubuntu@spinnaker:~$ source vmware-cloud-openrc.sh
Please enter your OpenStack Password for project vmware-cloud as user karthik1:
ubuntu@spinnaker:~$

Choose an Environment as a Local Debian

The Local Debian installation means Spinnaker will be downloaded and run on the single machine Halyard is currently installed on.

The Local Debian installation is intended for smaller deployments of Spinnaker, and for clouds where the Distributed installation is not yet supported; however, since all services are on a single machine, there will be downtime when Halyard updates Spinnaker.

ubuntu@spinnaker:~$ hal config deploy edit --type localdebian
+ Get current deployment
  Success
+ Get the deployment environment
  Success
- No changes supplied.
ubuntu@spinnaker:~$

Deploy Spinnaker

Now that we’ve enabled one Cloud Provider, picked a Deployment Environment, and configured Persistent Storage, we’re ready to pick a version of Spinnaker, deploy it, and connect to it.

1. List the available versions:

ubuntu@spinnaker:~$ hal version list
+ Get current deployment
  Success
+ Get Spinnaker version
  Success
+ Get released versions
  Success
+ You are on version "", and the following are available:
 - 1.5.4 (Atypical):
   Changelog: https://gist.github.com/spinnaker-release/6b9fd632caeaefd32246074998af8498
   Published: Wed Jan 10 18:46:49 UTC 2018
   (Requires Halyard >= 0.40.0)
 - 1.6.1 (GLOW):
   Changelog: https://gist.github.com/spinnaker-release/f1cd6232151b70492ebdcbb557a209fc
   Published: Wed Apr 04 19:20:54 UTC 2018
   (Requires Halyard >= 0.41.0)
 - 1.7.6 (Ozark):
   Changelog: https://gist.github.com/spinnaker-release/5d3af465f07eaca64f4383167877897d
   Published: Tue May 29 16:26:20 UTC 2018
   (Requires Halyard >= 1.0.0)
 - 1.8.0 (Dark):
   Changelog: https://gist.github.com/spinnaker-release/9b37ca56f2bfa676a60ecbd9a9ebffbd
   Published: Fri Jun 22 17:48:29 UTC 2018
   (Requires Halyard >= 1.0.0)

ubuntu@spinnaker:~$

2. Set the version you want to use:

ubuntu@spinnaker:~$ hal config version edit --version 1.8.0
+ Get current deployment
  Success
+ Edit Spinnaker version
  Success
+ Spinnaker has been configured to update/install version "1.8.0".
  Deploy this version of Spinnaker with `hal deploy apply`.
ubuntu@spinnaker:~$

3. Deploy Spinnaker:
   sudo hal deploy apply

Exposing Spinnaker on OpenStack Network

This post focuses on a Local environment. To prevent inadvertently exposing your cloud infrastructure to the whole world, Halyard installs Spinnaker in its most locked-down form. This means all services only bind to localhost , which only accepts connections from inside the same server.

On the other hand, Distributed environment services bind to 0.0.0.0 , which allows them to receive requests from services running on different hosts. This is essential to scaling Spinnaker to large enterprise deployments as a high-availability service.

Opening Gate and Deck

We’ll specify the 0.0.0.0 host in both gate.yml and deck.yml in our default Halyard deployment with this command:

ubuntu@spinnaker:~$ echo "host: 0.0.0.0" | tee \
> ~/.hal/default/service-settings/gate.yml \
> ~/.hal/default/service-settings/deck.yml
host: 0.0.0.0
ubuntu@spinnaker:~$

Run sudo hal deploy apply to update the changes to spinnaker.

Now, You can test this out by navigating to the instance’s public IP address on port 9000 in your browser.