OBSOLETE Juniper vMX deployment

[Quali-Community]

OBSOLETE Juniper vMX deployment

THIS VERSION IS OBSOLETE AND IS KEPT ONLY FOR REFERENCE. SEARCH FOR "VMX" IN THIS COMMUNITY AND USE THE NEWER VERSION.

This is a modified version of the first generation JunOS shell that can be used with vMX virtual router on vSphere.

It handles both deployment and use of the virtual router.

The Juniper JunOS Router model is selected as the deployment target of a vSphere app for the vMX controller (VCP). This is dragged into the blueprint canvas and connected with ordinary connectors. During Setup, the resource driver automatically deploys and connects additional vSphere apps for the vMX cards (VFP) and moves the connectors to individual VFP VMs. A connector can also be added after Setup, going directly to an interface under some VFP.

VCP and VFP templates on vSphere and corresponding apps must be provided.

Point-to-point and VLAN service connections are fully supported.

See the readme on GitHub for full details.

Repository

README.md

Name Juniper-JunOS-Shell Owner ericrqs Type 1st Gen Shell Category Networking Min. Compatible CloudShell Version 8.0

Juniper JunOS Shell This Shell supports all Juniper networking devices that run JunOS operating system. A CloudShell Shell implements integration of a device model, application or other technology with CloudShell. A Shell consists of a data-model that defines how the device and its properties are modeled in CloudShell along with an automation that enables interaction with the device via CloudShell. This networking shell provides connectivity and management capabilities such as power management, save and restore configruations, structure autoload functionality and upgrade firmware, etc. This shell is forked from Quali's official JunOS first generation shell. vMX is added to a blueprint by dragging a single app and drawing connectors to it. The added function connect_child_resources in the deployed app resource driver (Generic Juniper JunOS Driver Version3) will be called by Setup and will automatically add vMX card apps to the reservation, deploy them, and rearrange the connectors so that blueprint devices with connectors to the vMX will instead be connected to ports under deployed cards. The JunOS driver is capable of autoloading the vMX as if it were a standard JunOS router. Router and Firewall families changed to type ResourceType="Application" so model "Juniper JunOS Router" can be used for vMX and "Juniper JunOS Firewall" for vSRX Added "Juniper JunOS Router" attributes that will be used during vMX deployment Number of VFP Cards VFP Card App Name Prefix Management IP Extra Config Commands Family "VNF Card", model "vMX VFP Card" No attributes Family "Port", model "vMX Port" with attributes: Requested vNIC Name (e.g. "4" representing "Network adapter 4" in vSphere) vMX Port Address (e.g. ge-0/0/5 MAC Address Function connect_child_resources for deploying the multi-VM vMX added to driver Generic Juniper JunOS Driver Version3

* Updated Weekly

* Repository, release and asset info is updated weekly. * Please allow 30-60 seconds for manual update changes to take effect.

* Update Now

---

 Eric Rosenquist 07/13/2017 04:54 PM

·  1738  ·