This article is focused on automated large scale deployment of ZNS appliances. As such, it entails some non-trivial steps and command-line tools. It is expected that some of these steps would be adapted into SW management tools such as Ansible/Chef/Puppet/etc to fit into the operational procedures of the target IT organization.
For UI-based configuration through zCenter admin portal, please refer to the zCenter admin guide.
For automated deployment of ZNS clusters and nodes, the following major steps are required:
API-based configurator to configure zCenter
ZNS node SW installation
ZNS node configuration
FW rules for communication with users/servers/zCenter
Detailed steps:
API-based configurator to configure zCenter
If one is not yet available, create a Service-level API Key, in zCenter > Advanced Management > API Management > API Credentials, click Create Credentials, select Admin Type: Service Admin, add relevant comments in description, select all permissions, and save JSON file to a secure location
Download the configurator tool attached to this article
Note - this configurator is built to run on Centos7 operating system. Contact us for other operating systems
Usage: ./zns_cluster_node_create_811_centos.bin --scred <api_key.json> --zns_cluster_name <cluster_name> --control_channel_ip <IP_OR_FQDN> --preferred_data_path_ip <IP_OR_FQDN>
This will produce a file node_enable_key.txt with the pairing key, to be used below
ZNS node SW installation
VM Requirement: Centos 7 OS with latest yum updates. Please contact us for appropriate VM sizing
Download latest SW installer
For zCenter version 7.4.5:
for zCenter version 8.1.1: URL to be added
tar xf zns-node-install-<version>.tar.gz
cd zns-install-centos<version>
sudo ./install_zns<version>.sh
ZNS node configuration
Change to the zns-install-centos<version> directory created above
sudo ./cluster.sh enable --mcg-host=<zcenter URL> --shared-key=<Eg abcdef0123456789abcdef0123456789>
Note, if needed, to disable, use: sudo ./cluster.sh disable
Firewall rules
NOTE - The automation of these FW rules will vary depending on the FW technology used and is beyond the scope of this document
NOTE - These rules allow the ZNS appliance to communicate and establish access overlay network, which then tunnel the data channel traffic amongst users and servers. Once the below rules are in place, no further infrastructure firewall touches are required for individual access policies and connections.
NOTE - It is assumed that other basic functions such as SSH, NTP, yum, etc are already supported
Enable TCP 443 inbound to ZNS Node from any source
Enable TCP 4433 inbound to ZNS Node from zCenter
Enable TCP 443 outbound from ZNS Node to zCenter
Comments
0 comments
Please sign in to leave a comment.