* separate SP creation
separated Service Principal creation of aks due to issues on some machines with integrated SP creation
fixed typo in README
* Update deploy-sql-big-data-aks.py
removed JSON output
* adjusted for CU5
* change back
* update to CU5
* Updated requirements for pyspark installation in CU5
* Update setup-bdc.sh
* Update setup-bdc.sh
* Revert "Update setup-bdc.sh"
This reverts commit de66fa66aa.
* Revert "Update setup-bdc.sh"
This reverts commit 22fb8c17ad.
* Update setup-bdc.sh
I'm afraid current script would clobber existing /etc/sysctl.conf configuration
AND each of the 3 changes clobbering would clobber the previous one(s), only the last "net.ipv6.conf.lo.disable_ipv6=1" would be persisted in sysctl.
No code change, just 2 lines of comments pertaining to the seemingly redundant need to mount the folders when they *already* are under the discovery folder.
running this script as sudo ./setup-k8s-prereqs.sh would hit
"./setup-k8s-prereqs.sh: 22: [: bionic: unexpected operator"
explanation : https://stackoverflow.com/a/3411105
since script is "marketed" as sh, use "=" instead of "==" which works both under sh and bash
all lines from [setup-k8s-prereqs.sh] basically require elevation, and because there's no sudo prefixing each, running the script under sudo su context makes sense.
But the setup-k8s-master.sh will do chmod for root instead of current user if run under sudo su (cf use of "id"). It should be run under regular user context I think ?
The need for root context for [setup-volumes-agent.sh] is tied to the bond command, which is linked to another PR which I'll link later.
Daniel Coelho
Ben Weissman
Nguyen AnhandNguyen Anh
Mihaela Blendea
RL_MSFT
Mike Ray
Guillaume-Fourrat
NelGson
Umachandar Jayachandran