vmware-archive / chaperone

Chaperone

Chaperone is an Automation toolkit rooted in DevOps principals for deploying and configuring a Software Defined Data Center (SDDC) based Hybrid Cloud Management platform. It is intended to expedite and standardize "typical" deployments and configuration of VMware solutions including vSphere/vCenter, NSX, VIO, vRA, vRO, vROps, vRLI, vRB and others as the toolkit grows.

Chaperone is a work in progress. We will continue to add new functionality and products to the Chaperone base.

Chaperone Overview

Current Standard Configurations Supported

The ansible playbooks are used to configure and deploy several standard platforms. The following are under active development, but are considered fairly complete:

• Chaperone for VIO (Open Stack Integration)
• Chaperone for CNA (Cloud Native Application Platform)
• Chaperone for CMP (Hybrid Cloud Management Platform)

Experimental Configurations

The following are under active development

• Chaperone for NSX
• Chaperone for VxRails
• Chaperone for kubernetes
• Chaperone for IOT platforms

Setup and Run Chaperone

There are guides for setting up and running the Chaperone tools against an appropriate SDDC environment.

Development

Read the developer guide if you are interested in the development process of Chaperone

Chaperone Sub-components

Chaperone is built from lots of smaller pieces with a glue of UI and Ansible Playbooks.

The following is a current list of sub-projects:

• chaperone-ui
• ansible-playbooks-chaperone
• ansible-modules-extras-gpl3
• ansible-module-chaperone
• nsxansible.git
• nsxraml.git
• ansible-role-jenkins
• ansible-role-haproxy
• ansible-role-ansible
• ansible-role-assets
• ansible-role-autodeploy
• ansible-role-chaperone
• ansible-role-dnsmasq
• ansible-role-docker
• ansible-role-govc
• ansible-role-iptables
• ansible-role-kibana
• ansible-role-kubernetes-master
• ansible-role-kubernetes-node
• ansible-role-elasticsearch
• ansible-role-liota
• ansible-role-logstash-server
• ansible-role-net
• ansible-role-nfs
• ansible-role-nsx
• ansible-role-ovftool
• ansible-role-photon
• ansible-role-pip
• ansible-role-registrator
• ansible-role-repo
• ansible-role-sshkeys
• ansible-role-sudo
• ansible-role-vcenter
• ansible-role-vcsa
• ansible-role-vio
• ansible-role-vrops
• ansible-role-vra
• ansible-role-vrli
• ansible-role-vrb
• ansible-role-vrpt
• docker-chaperone
• docker-collectd
• docker-elasticsearch
• docker-graphite-api
• docker-jenkins
• docker-kibana
• docker-logstash-server
• docker-vrpt
• ViaSat/ansible-vsphere.git
• tomhite/ansible-xml
• tomhite/ansible-role-apache.git
• tomhite/ansible-role-collectd
• tomhite/ansible-role-consul
• tomhite/ansible-role-graphite-api
• ajsalminen/ansible-role-hosts.git
• weareinteractive/ansible-nginx.git
• weareinteractive/ansible-openssl
• weareinteractive/ansible-htpasswd.git
• Meta
  • link to PRs
  • link to Issues

License and Copyright

Copyright 2016 VMware, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Author Information

Initially created in 2015 by Tom Hite / VMware.

chaperone's Issues

Chaperone UI missing Apache

Testcase:
When executing site.yml and not using chaperone as a router, router.yml and ui.yml host must be set to the same host or Apache server is not available to ui. This causes the ui play to fail when trying to configure apache settings.

Error msg:
Destination directory /etc/apache2/sites-available does not exists

Remove "does_vm_exist" from manifest

due to change in vmware-archive/ansible-module-chaperone#3

Was removal of these modules necessary

From commit 717bc7f from @jdatx

• vcenter_datacenter
• add_nfs_datastore
• vio_create_network
• vio_add_ad_user
• os_create_user
• os_create_project
• does_vm_exist

Ansible 2.0 requires refactoring of several modules [PLACEHOLDER]

We knew this was coming, it's here now.

Process to set up new development environment is incorrect

The setup.md document is missing the usage of base.yml which calls the sshkeys role to set up key-based SSH access from the development server to the deployment server. The document also states that the new keys created are name id_rsa but are actually now called ansible_role_test_key.

Apache role broken

Fails with the below message

failed: [chaperone-ui.corp.local] (item=[u'apache_packages']) => {
"failed": true,
"invocation": {
"module_args": {
"allow_unauthenticated": false,
"autoremove": false,
"cache_valid_time": 0,
"deb": null,
"default_release": null,
"dpkg_options": "force-confdef,force-confold",
"force": false,
"install_recommends": null,
"name": [
"apache_packages"
],
"only_upgrade": false,
"package": [
"apache_packages"
],
"purge": false,
"state": "present",
"update_cache": false,
"upgrade": null
},
"module_name": "apt"
},
"item": [
"apache_packages"
],
"msg": "No package matching 'apache_packages' is available"

Removal of vcenter is preventing certain tasks in the vcenter role

The following modules were pulled from the manifest and therefore the associated tasks are failing:

• vcenter_add_nfs_ds: vcenter/tasks/storage.yml --> Add NFS datastore to OOB ESX hosts, Add NFS datastore to IB ESX hosts, Remove NFS datastore from OOB ESX hosts, Remove NFS datastore from IB ESX hosts
• vcenter_datacenter: vcenter/tasks/create_datacenter.yml via templates/create_datacenter.yml.j2--> Create Datacenter, vcenter/tasks/destroy_datacenter.yml via templates/destroy_datacenter.yml.j2 --> Destroy Datacenter
• vcenter_addhost: vcenter/tasks/esxhosts.yml --> Add ESX hosts to OOB cluster, Add ESX hosts to IB cluster, Remove ESX hosts from OOB cluster, Remove ESX hosts from IB cluster

The commit that removed these modules should be reverted OR if they were meant to be removed the new modules/updated tasks need to be committed after successful testing.

build-squid.eng.vmware.com not found

Hello, I might be missing something, however when attempting to follow the instructions and deploy chaperone-ui I'm hitting an issue downloading the depot files. They are referencing "build-squid.eng.vmware.com" which isn't resolvable.

TASK [assets : get depot file stats] *******************************************
ok: [chaperone-ui.lab.vrandom.com]

TASK [assets : pull depot files for future downloads (may take many minutes)] **
fatal: [chaperone-ui.lab.vrandom.com]: FAILED! => {"changed": false, "dest": "/var/www/html/downloads/VMware-ESXi-6.0.0-2494585-depot.zip", "failed": true, "msg": "Request failed", "response": "Request failed: <urlopen error [Errno -2] Name or service not known>", "state": "absent", "status_code": -1, "url": "http://build-squid.eng.vmware.com/build/mts/release/bora-2494585/publish/VMware-ESXi-6.0.0-2494585-depot.zip"}

RUNNING HANDLER [iptables : restart ufw] ***************************************

PLAY RECAP *********************************************************************
chaperone-ui.lab.vrandom.com : ok=54 changed=13 unreachable=0 failed=1

Thanks in advance

Alex

DNS resolution:
vmware@dev01:~/chaperone/ansible/playbooks/chaperone-ui$ dig build-squid.eng.vmware.com

; <<>> DiG 9.9.5-3ubuntu0.4-Ubuntu <<>> build-squid.eng.vmware.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1757
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;build-squid.eng.vmware.com. IN A

;; AUTHORITY SECTION:
eng.vmware.com. 573 IN SOA ns1-sjc31.engx.vmware.com. si-admin.vmware.com. 2015122310 3600 900 2419200 900

;; Query time: 4 msec
;; SERVER: 10.30.20.20#53(10.30.20.20)
;; WHEN: Thu Jan 14 18:16:53 GMT 2016
;; MSG SIZE rcvd: 115