Imagine you’re asked to build a modern financial application—let’s call it FlowTrack—whose purpose is to give customers a unified view of all their finances across every bank they use. On the surface, the idea feels straightforward: you need to retrieve account lists, fetch balances, collect recent transactions, and help customers see their complete financial picture. But the moment you begin exploring how to connect to real banks, the technical landscape quickly becomes far more challenging than you expect.
| -- Position settings, modify if you find the mouse is at incorrect position when you press the hotkey. | |
| screenMirroringIconX = 215 -- position in px of icon from right of screen | |
| visionProOptionY = 125 -- position in px of icon from top of screen | |
| -- Hotkey settings, default is cmd+opt+ctrl+m | |
| connectHotkey = "m" | |
| connectHotkeyModifiers = { 'command', 'option', 'control' } | |
| hs.hotkey.bind(connectHotkeyModifiers, connectHotkey, function() | |
| -- only execute if the primary screen is the Built-in Retina Display |
| #!/usr/bin/env bash | |
| API_KEY='' | |
| API_BASE='https://genai-proxy.sys.tas.vmtanzu.com/v1' | |
| MODEL="text-embedding-ada-002"# this is actually vicuna 1.5 7b on my TAS | |
| TEMPERATURE=0 | |
| MAX_TOKENS=1024 | |
| function chat_with_model() { | |
| local prompt=$1 | |
| # Construct the request body | |
| local request_body=$(jq -n \ |
| while read newline | |
| do | |
| new=$(date -d "$(echo "$newline" | sed -E 's/-([0-9][0-9])\.([0-9][0-9])\./ \1:\2:/')" '+%s') | |
| if [ "$old" ] && (( $new - $old > 20)) | |
| then | |
| printf "%4i seconds gap before %s" "$((new - old))" "$newline" | |
| fi | |
| old=$new | |
| done <check_liveness.log |
Welcome! This is a series of quick guides to setting up dev/test/lab environment with Tanzu Kubernetes Grid and/or with VMware Telco Cloud Automation.
This isn't a replacement for the official documentation but rather is a curated, streamlined set of "how tos" from several locations based on my experiences.
Audience: anyone in the BOSH ecosystem, whether you work on something open-source or proprietary
"BOSH Links" is a feature which simplifies how data is shared between BOSH-deployed jobs that need to collaborate with one another (e.g. a web server and its backing database). Like many BOSH things, the whole "BOSH Links" thing can seem counter-intuitive at first, and it may not be clear why things are the way they are. This note hopes to show some of the powerful benefits of BOSH Links, and provide examples and explanations that make things more intuitive.
| apiVersion: v1 | |
| kind: ServiceAccount | |
| metadata: | |
| name: calico-node-cleanup | |
| namespace: kube-system | |
| --- | |
| kind: ClusterRole | |
| apiVersion: rbac.authorization.k8s.io/v1 | |
| metadata: | |
| name: calico-node-cleanup |
- Shows you how to use Istio 1.4.0 - 1.4.2 on Kubernetes 1.14+ with a modicum of runtime security for your workloads.
- Specifically it installs Istio with CNI support, and allows the use of restrictive PodSecurityPolicies for your workloads. Istio 1.4.3 fixes this issue. However, this may still be useful due to a need to add a PSP privileged role to the Istio helm charts!
- It is designed for VMware PKS, but doesn't require it ... (just change the CNI bin dir and excluded namespaces in
values-cni.yml, also swap the ClusterRolepks-privilegedandpks-restrictedmentioned throughout these files with your own PSP roles). - It doesn't fix the need for Istio itself to run as root, but that should be fixed in a future Istio release as it's already fixed in trunk.
- Update I've also included a workaround for the CNI race condition bug in Istio CNI if you're using a DaemonSet-based CNI. See istio/istio#14327
| sudo sed -i "s/AZ_NAME_FOR_AVAILABILITY_SETS = 'Availability Sets'.freeze/AZ_NAME_FOR_AVAILABILITY_SETS = 'null'.freeze/" /home/tempest-web/tempest/web/app/models/persistence/models/azure/azure_availability_zone.rb | |
| sudo service tempest-web restart |
| nodes-network.json | |
| { | |
| "description": "Configurable Nodes Network IP Block", | |
| "name": "network-profile_nodes-ip-block", | |
| "parameters": { | |
| "node_ip_block_ids": [ | |
| "2250dc43-63c8-4bb8-b8cf-c6e12ccfb7de", "3d577e5c-dcaf-4921-9458-d12b0e1318e6" | |
| ], | |
| "node_routable":true, | |
| "node_subnet_prefix":20 |