-
Notifications
You must be signed in to change notification settings - Fork 17
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
Document albatross over tls #155
Conversation
TLS.md
Outdated
16 unikernels on two CPUs. | ||
|
||
``` | ||
albatross-provision-request add_policy user 16 --mem 1024 --cpu 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
albatross-provision-request add_policy user 16 --mem 1024 --cpu 0 | |
albatross-provision-request add_policy user 16 --mem 1024 --cpu 0 --cpu 1 |
In the text, there's two CPUs
-- that should be reflected in the command.
Also I'm wondering whether we need a slight excursion what these cpu
arguments are meaning / what they're used for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, thanks. Indeed I was confused by the --cpu <n>
option at first I thought <n>
was the total number of CPUs allowed, instead of the core ID. I'll make the doc more precise on that matter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added a commit to make the doc consistent and replaced two CPUs
by CPU IDs 0 and 1
. It still not very clear what that means as I'm not familiar with the option, so don't hesitate to add something if you want !
Thanks for writing this up. I added some minor comments. |
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
thanks! :) |
CHANGES: This is a breaking release since the binaries to be installed have been revised and merged. The `albatross-client-local` is now `albatross-client [--socket]`, `albatross-provision-ca` is now `albatross-client sign` or `albatross-client generate`. The `albatross-client-remote` is now `albatross-client certificate`. The `albatross-client-bistro` is now `albatross-client <command> --destination <host> --ca ca.pem --ca-key ca.pem --server-ca cacert.pem`. And finally, `albatross-tls-inetd` is now `albatross-tls-endpoint --inetd`. - Document TLS usage (robur-coop/albatross#155, robur-coop/albatross#156 @TheLortex @hannesm) - Improve TLS experience by providing more reasonable error messages and apply more checks before establishing a TLS session (robur-coop/albatross#157 @hannesm @reynir) - Slim down binaries: - remove albatross-stat-client binary (robur-coop/albatross#161 @hannesm) - move X509 parts out of Albatross_cli (robur-coop/albatross#158 @reynir) - merge albatross-tls-inetd with albatross-tls-endpoint (robur-coop/albatross#160 @hannesm) - merge albatross-client-inspect-dump into albatross-client (robur-coop/albatross#161 @hannesm) - merge albatross-provision-ca and albatross-provision-request into albatross-client (robur-coop/albatross#159 @reynir @hannesm) - merge albatross-client-remote and albatross-client-bistro and albatross-client-local into albatross-client (robur-coop/albatross#162 @hannesm) - Check solo5 ABI tender version, allow multiple solo5 tenders to exist (named as solo5-{s,h}vt.<ABI> (robur-coop/albatross#163 @hannesm) - Improve documentation and manpages (robur-coop/albatross#164 @hannesm)
Here is a document I synthesized from my experiments.
It might help for the "document" part of #149