summaryrefslogtreecommitdiffstats
path: root/mcp/reclass/classes/cluster/mcp-pike-odl-ha/infra/init.yml
blob: 419c059476e8cd1d2668d6169f6284d18ba32bb1 (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14

##############################################################################
# Copyright (c) 2018 Mirantis Inc., Enea AB and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Apache License, Version 2.0
# which accompanies this distribution, and is available at
# http://www.apache.org/licenses/LICENSE-2.0
##############################################################################
---
classes:
  - cluster.mcp-pike-common-ha.infra
  - cluster.mcp-pike-odl-ha.openstack
parameters:
  _param:
    cluster_name: mcp-pike-odl-ha
s='-o StrictHostKeyChecking=no' ``` In this configuration file, connection details should be filled in. In case more nodes within the cluster are needed, add lines as necessary to the workers group within the `hosts` file. ### Usage In order to use the script, download or clone [this repository] (https://gerrit.opnfv.org/gerrit/vswitchperf) to the root of what will be the master node. Navigate to its contents and execute the following command as regular user (this will prevent errors throughout configuration and deployment) on whichever machine you wish to use as the master node (this host will be the one running kubectl): ``` ansible-playbook k8sclustermanagement.yml -i hosts –tags “deploy” ``` You can verify the installation by running: ``` kubectl get nodes ``` And verifying the readiness of the nodes. More information may be obtained with `kubectl describe nodes` if needed. To clear the cluster, execute the following command ``` ansible-playbook k8sclustermanagement.yml -i hosts_garr –tags “clear” ``` To deploy only CNI plugins ``` ansible-playbook k8sclustermanagement.yml -i hosts_garr –tags “cni” ``` ### Debugging In case a step goes wrong within the installation, ansible should display a message, however, there's also files to debug if the installation had something to do within k8s. In the case of the master node, we should be able to find a `log_init.txt` with necessary logs. On worker nodes, the relevant file is `node_joined.txt`.