Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Utilize AssetCache checking and Mist-CLI to utilize Content Caching natively #241

Open
tranziq opened this issue Oct 2, 2024 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@tranziq
Copy link

tranziq commented Oct 2, 2024

By using assetcachelocatorutil you can verify if a content cache is available and reachable.

in the Braindate at JNUC, it was mentioned that Mist CLI can utilize Content caching with a flag

-Brent David

@ofirgalcon
Copy link

sounds like a good idea

@Macjutsu Macjutsu added the enhancement New feature or request label Oct 10, 2024
@Macjutsu Macjutsu added this to the v5.x.x milestone Oct 10, 2024
@dnikles
Copy link

dnikles commented Oct 10, 2024

FYI, here's info on how to use the caching server with mist-cli

Currently (outside of super) we use something like this with a hard coded caching server address to determine wether or not to call mist-cli with the caching option, as it will fail if it is called with a caching server that is unreachable

ping -c 1 $cachingserver
reachable=$?
if [ $reachable == "0" ]
	then
		echo "caching server is reachable"
		jamf policy -event sequoia-caching-server		
	else
		echo "caching server is unreachable"
		jamf policy -event sequoia-no-caching
fi

If parsing the output from assetcachelocator, that data might be under .results."current user"."saved servers"."shared caching"[] then .healthy, .hostport, and .rank to help determine the best choice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants