We’ve recently provided support for a Nuage Networks VSP upgrade scenario in which the existing Nuage components had been installed months back. The customer had a 3-VSD cluster, a pair of VSCs, and a 3-ES cluster. Metro is designed to support exactly this scenario. One item that caused premature failures
The VSP Install Guide makes a best-practice recommendation to use the fallocate command on a Linux hypervisor when copying the qcow2 image file. fallocate will tell the file system on the hypervisor to pre-allocate disk space for the file, preventing a potential out-of-space error as the qcow2 grows. The Install Guide recommends that we
MetroAE does not require that you have used it to install when you want to use it for upgrade or health checking. We 100% support working for this use case. There is an additional requirement for such a use case, however: You must manually copy ssh keys to the Nuage
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 or lab/test setup. Modifying the
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 space when we copied the
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 fail is if both of
A common problem we hear from the field is an error when MetroAE attempts to execute a yum update on the VSDs. This takes place during the vsd-deploy phase and results in this error text: This problem is going to prevent you from moving forward because the vsd-install script hasn’t
With the introduction of Croxley, MetroÆ supports a new, schema-validated method of user input. The implementatino is such that now each section of the old build_vars.yml file now has its own file: vsds.yml vscs.yml common.yml and so on As an aid to hep you convert from the older format to
