-
Notifications
You must be signed in to change notification settings - Fork 18
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
record start timestamp and provide via info (fixes #168) #169
Conversation
@@ -644,7 +645,8 @@ let unikernel_info = | |||
(required ~label:"net-name" utf8_string) | |||
(optional ~label:"bridge-name" utf8_string) | |||
(optional ~label:"mac" mac_addr))))) | |||
-@ (optional ~label:"arguments"(my_explicit 2 (sequence_of utf8_string)))) | |||
@ (optional ~label:"arguments"(my_explicit 2 (sequence_of utf8_string))) | |||
-@ (optional ~label:"started" (my_explicit 3 generalized_time))) |
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.
since this is optional, old servers will be able to communicate with new clients. new servers will emit that and may make old clients fail...
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 think that is acceptable. It is usually easier to upgrade the client than the server.
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.
maybe, but then we may have no control over the client installations when we upgrade the server. I added the bit needed in 2aef890.
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.
Thanks!
…ernel_info2 and receive an old_unikernel_info)
Now, certainly a new client will request the new unikernel_info command, and an old server may just fail to understand the meaning. This is fine, as written in vmm_asn, it may be worth to work on a For now, I'd merge this PR; for albatross 3 we can rethink the command negotiation mechanism. |
CHANGES: * BUGFIX install tls_endpoint as systemd service (not only as example), fix typo (robur-coop/albatross#183 @PizieDust) * BUGFIX albatross-influx: use "cow_faults" (fixed typo in robur-coop/albatross#182) as unsigned integer (b9695dd9c267f5e59f18154a632adba0481f9d72, @hannesm) * BUGFIX albatross-influx: avoid empty measurement (robur-coop/albatross#182 @hannesm) * BUGFIX tls-endpoint: don't fail if a bad client connects (robur-coop/albatross#180 @hannesm) * FEATURE tls-endpoint: add syslog support (esp. useful for inetd) (robur-coop/albatross#185 @hannesm) * FEATURE Update to FreeBSD 14 (robur-coop/albatross#172, @hannesm) * BUGFIX update command: make usable with local client (robur-coop/albatross#184, @reynir) * BUGFIX update command: handle HTTP not found explicitly (fixes robur-coop/albatross#147, robur-coop/albatross#171 @hannesm) * FEATURE Albatross: record start timestamp via info (fixes robur-coop/albatross#168, robur-coop/albatross#169 @hannesm) * BUGFIX Albatross: store timestamp as generalized time instead of utc time (robur-coop/albatross#167 @hannesm @reynir, adjusted by robur-coop/albatross#181 for backwards compatibility @PizieDust) * BUGFIX FreeBSD: restart services when they terminate (@hannesm, 64f28fbd88504ec33d6bfde5211684e0ba1bc193) * BUGFIX packaging: install albatross-client as albatross-client (@hannesm, 23acb8b3edbe0153e1bd24a1736b80e73a27e33f) * update nix inputs (robur-coop/albatross#175, robur-coop/albatross#179 @Julow) * use ohex instead of hex (robur-coop/albatross#174 @hannesm) * fix README (robur-coop/albatross#177 @PizieDust, 2a1c3d898b586946ce7c4f3171ea5eb856f4ade8, 107c235eb94e83d6a077c42ee8b527c207af4ba7)
CHANGES: * BUGFIX install tls_endpoint as systemd service (not only as example), fix typo (robur-coop/albatross#183 @PizieDust) * BUGFIX albatross-influx: use "cow_faults" (fixed typo in robur-coop/albatross#182) as unsigned integer (b9695dd9c267f5e59f18154a632adba0481f9d72, @hannesm) * BUGFIX albatross-influx: avoid empty measurement (robur-coop/albatross#182 @hannesm) * BUGFIX tls-endpoint: don't fail if a bad client connects (robur-coop/albatross#180 @hannesm) * FEATURE tls-endpoint: add syslog support (esp. useful for inetd) (robur-coop/albatross#185 @hannesm) * FEATURE Update to FreeBSD 14 (robur-coop/albatross#172, @hannesm) * BUGFIX update command: make usable with local client (robur-coop/albatross#184, @reynir) * BUGFIX update command: handle HTTP not found explicitly (fixes robur-coop/albatross#147, robur-coop/albatross#171 @hannesm) * FEATURE Albatross: record start timestamp via info (fixes robur-coop/albatross#168, robur-coop/albatross#169 @hannesm) * BUGFIX Albatross: store timestamp as generalized time instead of utc time (robur-coop/albatross#167 @hannesm @reynir, adjusted by robur-coop/albatross#181 for backwards compatibility @PizieDust) * BUGFIX FreeBSD: restart services when they terminate (@hannesm, 64f28fbd88504ec33d6bfde5211684e0ba1bc193) * BUGFIX packaging: install albatross-client as albatross-client (@hannesm, 23acb8b3edbe0153e1bd24a1736b80e73a27e33f) * update nix inputs (robur-coop/albatross#175, robur-coop/albatross#179 @Julow) * use ohex instead of hex (robur-coop/albatross#174 @hannesm) * fix README (robur-coop/albatross#177 @PizieDust, 2a1c3d898b586946ce7c4f3171ea5eb856f4ade8, 107c235eb94e83d6a077c42ee8b527c207af4ba7)
//cc @reynir