We recently saw a problem where a user was having trouble doing an install via ./metroae install_everything. The problem: metroae was completing without doing anything. In the output, every component type displayed a message like this: [WARNING]: Could not match supplied host pattern, ignoring: vstats PLAY
We recently had a user stumble over input data validation. In MetroAE v3, all input data in your deployments folder is schema validated. This means that every file in your deployment must conform to the schema. This includes required data. In the case under discussion,
Our lab machines tend to have small memory sizes. When we do our testing, we often ‘cheat’ by allocating less RAM for Nuage VMs that we spin up on hypervisors. This is *Not* acceptable in a production environment, but can be useful in a PoC
We faced a scenario in our lab that may be of interest to some of you. We re-purposed an old bare-metal server running CentOS 7.3 as a hypervisor/target server for a MetroÆ test. On our first attempt to install a VSD, we ran out of
MetroAE tests to see if a node is already running before it tries to instantiate it. For example, if a VSD is up and running, we will skip the vsd-predeploy step, saving you time. One of the conditions that can cause the check-node-running task to
Jinja2 substitution in deployment files is not currently supported. Many build_vars files included “{{ dns_domain }}” tags. In the v3.0.0 convert_build_vars_to_deployment script, it carried these substitutions into the deployment files and thus corrupted them. This is fixed in v3.0.1 to perform the substitution beforehand. If
If when running the convert_build_vars_to_deployment.py script, you get the following error: AttributeError: ‘IPAddress’ object has no attribute ‘netmask_bits’ This is likely because the Python “netaddr” package is old on your system. The package can be upgraded using: $ pip install –upgrade netaddr You can check
In my testing of the new MetroAE Croxley container deployment on CentOS 7, I have found the following installation instructions for Docker CE to be accurate and reliable: https://docs.docker.com/install/linux/docker-ce/centos/ Docker Community Edition (CE) is ideal for individual developers and small teams looking to get started
By default, MetroAE will establish TLS OpenFlow channels from the VSCs to the forwarding-plane components, VRS and NSGv. TLS is required for NSGV/VNS, but not for VRS/VCS. In order to turn off TLS for your data-center VCS deployment, you would edit the following parameter in common.yml in
