Camera-node

All software needed for a camera node in an environment. Includes pieces for both capture and delivery as well as proxy node that handles centralized processing of video, upload, and queuing in case of slow or down connectivity.

Proxy

Flask service that receives data from all other camera nodes and feeds and internal queue and that sends data to honeycomb and optionally processes videos to pull out frames that are also sent to honeycomb.

Capture

Service that runs on nodes that have cameras. Captures video clips in short segments and sends them to their internal queue where workers send the to the proxy.

Workers

Celery service that performs tasks from the internal queue. Capture work is processed and sent to the proxy, unless it is a the proxy-node in which case it forwards the work to another task. Video segments are processes and sent to honeycomb. Processing includes tagging etc. Once uploaded the next set of processing happens, key frames are extracted at those are sent to honeycomb as child datapoint objects of the video.

If running on more capable hardware the keyframes could be evaluated for things like pose detection or object tracking. This is not planned yet but isn't out of scope specifically.

Radio-Monitor

A python service that connects to a network of DWM1001 modules over BLE to collect data. That data is queued to be sent to honeycomb. It is expected that this service runs on the proxy node.

CUWB-Stream

Leverages fluentd to move Ciholas sensor data to S3

Before deploying the service, update the Ciholas network config as follows:

	IP	Port	Interface
Config	239.255.76.67	7671	<>
Input	239.255.76.67	7667	<>
Output	0.0.0.0	32222	<>

PS: In order to resolve an issue with the anchors disconnecting and not reconnecting, you may need to set the interface IPs of the Config and Input rows to the ethernet device's IP (Use ifconfig)

Build and push cuwb service

make build-cuwb-stream

Deploy streaming service to k8

# Install envsubtr, on MacOS install through the gettext pkg
brew install gettext
brew link --force gettext 

# Create a config and secrets file with S3 and AWS ENV keys
kubectl apply -f ./k8s/kube-logging.yml
kubectl apply -f ./private/aws-s3-write-auth-config.yml
kubectl apply -f ./private/aws-s3-write-auth-secret.yml
kubectl apply -f ./k8s/fluentd.yml
kubectl apply -f ./k8s/fluentd-s3-config.yml
kubectl apply -f ./k8s/fluentd-s3.yml

TIMEZONE=US/Pacific envsubst < ./k8s/fluentd-s3-scheduler.yml | kubectl apply -f -

kubectl apply -f ./k8s/cuwb-service.yml

Test CUWB Steaming logger

See the cdp_player README

CDP Player

You can use the Makefile to build or run the cdp-player. You can also work with cdp-player directly.

Build

make build-cdp-player REPO_NAME=<<Ciholas PPA Repository Name>>

Run

make run-cdp-player REPO_NAME=<<Ciholas PPA Repository Name>>

Setup cluster with Docker Hub robot

First login and then copy creds into the cluster:

docker login
# Provide username and PAT (personal access token)

kubectl create secret generic regcred --from-file=.dockerconfigjson=/home/wildflowertech/.docker/config.json --type=kubernetes.io/dockerconfigjson

Logz + Fluentd Experiment

kubectl create namespace monitoring

kubectl create secret generic logzio-logs-secret \
    --from-literal=logzio-log-shipping-token='<<REDACTED>>' \
    --from-literal=logzio-log-listener='https://listener.logz.io:8071' \
    -n monitoring

# fluentd-general-config.yml contains the CLASSROOM_ENVIRONMENT env var
kubectl apply -f ./private/fluentd-general-config.yml
kubectl apply -f ./k8s/fluentd-general-config.yml -f ./k8s/fluentd-general-monitoring.yml

Metadata

Release files for wf-camera-utils 1.0.28

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for wf-camera-utils 1.0.28
File	Size	Uploaded	Provenance
wf-camera-utils-1.0.28.tar.gz	14.6 kB	Nov 29, 2022	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for wf-camera-utils 1.0.28
File	Interpreter	ABI	Platform	Reset
wf_camera_utils-1.0.28-py3-none-any.whl 16.3 kB Nov 29, 2022 Without provenance	Python 3	none	any	Details

Total release size: 30.9 kB

Release files / wf-camera-utils-1.0.28.tar.gz

Download URL	wf-camera-utils-1.0.28.tar.gz
Size	14.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`b920a2bb6b0ae24d3036ad93192b2c3ebf971854b77c4da681752cabc3bb2ae5`
BLAKE2b-256 checksum How to use checksums	`17d7128f32df67de3fe008da8c2496b6efb02e879f98c8b5332f63679c742452`
Upload date	Nov 29, 2022
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`poetry/1.2.1 CPython/3.10.2 Darwin/21.6.0`

Release files / wf_camera_utils-1.0.28-py3-none-any.whl

Download URL	wf_camera_utils-1.0.28-py3-none-any.whl
Size	16.3 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`cf8fddb77b39f2967922e34d6423dd9e4961922a3682715cae97332656dddd73`
BLAKE2b-256 checksum How to use checksums	`96738b9a8a1c089b35075eb1546fa7ffdc7d72429ea101ceb940d4a947b3e33a`
Upload date	Nov 29, 2022
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`poetry/1.2.1 CPython/3.10.2 Darwin/21.6.0`

Security for wf-camera-utils 1.0.28

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.