Bloomberg Clustered Private Cloud distribution
The cloud consists of head nodes (OpenStack controller services, Ceph Mons, etc.) and work nodes (hypervisors).
Each head node runs all of the core services in a highly-available manner. Each work node runs the relevant services (nova-compute, Ceph OSDs, etc.).
The following instructions will get chef-bcpc up and running on your local machine for development and testing purposes.
NOTE: It is likely possible to build an environment with 16GB of RAM or less if one is willing to make slight modifications to the virtual topology and/or change some of the build settings and overrides. However, we've opted to spec the minimum requirements slightly more aggressively and target hosts with 32GB RAM or more to provide the best out-of-the-box experience.
virtual/topology/topology.ymlfor the topology you will build and make changes as required, e.g. assign more or less RAM based on your topology and your build environment. Other topologies exist in the same directory.
topology.overrides.yml, respectively, and make changes to them instead.
Create a Python virtual environment (virtualenv) and activate it
python3 -mvenv venv source venv/bin/activate pip install PyYaml ansible netaddr pyOpenSSL pycryptodome
To create a virtualbox build (the default):
make generate-chef-databags make create all
To create a libvirt build:
sudo apt-get install build-essential libvirt-dev qemu-utils vagrant plugin install vagrant-libvirt vagrant-mutate vagrant box add bento/ubuntu-18.04 --box-version 202005.21.0 --provider virtualbox vagrant mutate bento/ubuntu-18.04 libvirt export VAGRANT_DEFAULT_PROVIDER=libvirt VAGRANT_VAGRANTFILE=Vagrantfile.libvirt make generate-chef-databags make create all
You may also want to change cpu model from
chef_environment: name: virtual override_attributes: bcpc: nova: cpu_config: cpu_mode: custom cpu_model: kvm64
To revert to the default virtualbox provider, as far as the build is concerned, you can just remove the mutated libvirt box and then unset VAGRANTDEFAULTPROVIDER and VAGRANT_VAGRANTFILE environment variables. However since you must also make sure that the different hypervisors don't both try to control the CPU virtualisation facilities, it is best to remove the mutated box and then simply reboot your development host (assuming no scripts reset the VAGRANT variables).
This would look something like this:
$ rm -rf ~/.vagrant.d/boxes/bento-VAGRANTSLASH-ubuntu-18.04/202005.21.0/libvirt/ $ sudo reboot
Currently, most development is done by a team at Bloomberg L.P. but we would like to build a community around this project. PRs and issues are welcomed. If you are interested in joining the team at Bloomberg L.P. please see available opportunities at the Bloomberg L.P. careers site.
This project is licensed under the Apache 2.0 License - see the LICENSE.txt file for details.
chef-bcpc is built with the following open source software:
Thanks to all of these communities for producing this software!