You can't perform this operation as non-sudoer user. Please, re-login or configure sudo access for this user.
Check the verion of HDF components 3.0.0
| Terminology | |
| Write-Ahead Logging | |
| https://www.xuchao.org/docs/postgresql/wal.html | |
| Archi View & Use cases | |
| https://www.slideshare.net/hortonworks/hortonworks-data-in-motion-series-part-4 | |
| http://bryanbende.com/development/2016/08/17/apache-nifi-1-0-0-authorization-and-multi-tenancy | |
| Performance Tuning |
| Conclusion, | |
| Zookeeper need at least 2 instances to function as cluster coordinator. | |
| When start a new publisher, we need to specify the publish-brokers, | |
| • if all publish-brokers are down but there’s other broker(s) in same replica is up and zookeeper is in function, then the published message will be cached somewhere and re-published when one of the publish-brokers is up | |
| • if all publish-brokers are down and zookeeper is not in function, then we can’t publish | |
| For an existing function publisher, when we bring down some of publish-brokers, | |
| • If all publish-brokers are down and we need to switch to other alive brokers , we need to count on zookeeper |
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
| #!/usr/bin/env python | |
| # | |
| # Example 1: All blocks in list.txt, one CIDR per line | |
| # cat list.txt | cidr.py | |
| # | |
| # Example 2: Echo CIDR blocks to stdout | |
| # echo 1.2.3.0/25 1.2.3.128/25 | cidr.py | |
| import sys | |
| from netaddr import * |
| AWSTemplateFormatVersion: '2010-09-09' | |
| # ------------------------------------------------------------# | |
| # Metadata | |
| # ------------------------------------------------------------# | |
| Metadata: | |
| AWS::CloudFormation::Interface: | |
| ParameterGroups: | |
| - Label: | |
| default: "Kinesis Data Firehose Configuration" | |
| Parameters: |
| #!/bin/bash | |
| # MacOS 11 Big Sur | |
| # Homebrew 3.3.9 | |
| # bind: stable 9.16.24 | |
| # Local caching NS server | |
| # 1) INSTALL BIND |
This document outlines the steps to set up a one tunnel IPSec Site to site VPN on AWS and a VM on another cloud provider (Packet) running Strongswan.
(References:
https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html
(This can be any cloud provider. It does not have to be Packet)