How to Install the MetroAE Container
The MetroAE Container will be dynamically built on the users machine starting v5.
MetroAE Version 5.0.0 is now available
We are pleased to announce the GA of the latest feature update to
MetroAE v4.5.0 is Now Available
We are pleased to announce the GA of the latest feature update to
Essential Information about MetroAE Features v4.3
MetroAE v4.3 is officially available! It is available in both container and GitHub
Everything You Need To Know About MetroAE Config
With the release of MetroAE v4.1 comes MetroAE Config, the newest tool in
Essential Information about MetroAE Features v4.1
MetroAE v4.1 is officially available! MetroAE is now comprised of MetroAE Deploy, which
Essential Information about MetroAE Features v4.0
MetroAE v4.0 is officially here! It is available in both container and GitHub
Docker CE
In my testing of the new MetroAE Croxley container deployment on CentOS 7,
Upgrading From 1.1.0 to 1.1.2 version
1.1.0 and 1.1.1 versions of the MetroÆ Docker container were built with a
Using passwords with special chars
If you have passwords that break the yaml format. i.e. beginning with !
Don’t forget to setup passwordless ssh to existing nodes – especially for Docker
We’ve recently provided support for a Nuage Networks VSP upgrade scenario in which
vsc_health: Get output of ‘show version’ failed: unable to open shell
We recently saw a user encounter this error when running vsc_health prior to
Q&A: Command to launch the Docker MetroAE Container
Question In the GitHub repo the DOCKER.md refers to the metroae command being
Validate KVM environment on hypervisor
Here are some tools to validate that KVM is healthy on your hypervisor.
Can’t find id_rsa.pub error
We recently had a report of the following error during vsd-predeploy: TASK [vsd-predeploy
Unable to open shell error: take 2
Have you seen this error? unable to open shell. Please see: https://docs.ansible.com/ansible /network_debug_troubleshooting.html#unable-to-open-shell
Public key for .rpm is not installed
As part of the installation of VRS on Linux compute blades, MetroAE follows
fallocate: Operation not supported
The VSP Install Guide makes a best-practice recommendation to use the fallocate command on a
Accessing MetroÆ behind a firewall
You can download MetroÆ from github.com as a zip file. It is just
Error: Permission denied waiting for SSH when VSD not installed using MetroAE
MetroAE does not require that you have used it to install when you
Can’t use jinja2 in deployment files
We recently saw a problem where a user was having trouble doing an
Invalid data failure: What is required input data?
We recently had a user stumble over input data validation. In MetroAE v3,
Not enough memory on KVM
Our lab machines tend to have small memory sizes. When we do our
libvirt Error reading QCOW2: Permission denied
We faced a scenario in our lab that may be of interest to
Recovery from check-node-running fails if VM is running but node not reachable
MetroAE tests to see if a node is already running before it tries
{{ dns_domain }} in build_vars conversion and clearing corrupted inventory
Jinja2 substitution in deployment files is not currently supported. Many build_vars files included
‘IPAddress’ object has no attribute ‘netmask_bits’ in build_vars conversion
If when running the convert_build_vars_to_deployment.py script, you get the following error: AttributeError: ‘IPAddress’
Docker CE
In my testing of the new MetroAE Croxley container deployment on CentOS 7,
TLS for VSC Connections to Forwarding Plane
By default, MetroAE will establish TLS OpenFlow channels from the VSCs to the
Unable to open shell error
We sometimes see an issue when running an install with MetroAE that results
yum update error on VSD: Timeout on http://nuage-public-mirror
A common problem we hear from the field is an error when MetroAE
Setup error: network unreachable for pip
We recently saw a user experiencing an error running the MetroAE setup script:
Converting from build_vars.yml to deployments for Croxley
With the introduction of Croxley, MetroÆ supports a new, schema-validated method of user
vsd_health error on JMS: http instead of https
Recently, a MetroAE user reported seeing the following error when running vsd_health: TASK
