Proto commits in googlecloudrobotics/core

These 33 commits are when the Protocol Buffers files have changed:

2023-07-03

Extend the monitoring of the relay to also track the backend timing. (#166) This lets us observe the overall duration, the backend duration and as a delta (overall-backend) the overhead. Especially the overhead is hopefully useful to spot infrastructure issues on the relay side.

The documentation is generated from this commit.

2023-01-10

Remove Java code and build system. Java was only used by the old token vendor. Now that the token vendor is re-written in golang we can remove the tooling for Java. Change-Id: I013cabb666c10463b4ba7e9610673ea054a546e0 GitOrigin-RevId: b159794df4ced7e596a43dce38f0bb8211ded642

2022-11-17

removed dead protos Change-Id: I167f144e1830fa85efcc5fe033a8c114e0da601f GitOrigin-RevId: 3a3e644c894890853cc00be9b0c85732f14dbfa5

2022-11-03

update go compiler and proto dependencies also update indirect dependency json-iterator as the previous would fail (segfault) with go 1.18+ Change-Id: I935f31772e9689c80c4a1f872cf21860598184e4 GitOrigin-RevId: a4cb86dc57a9792d47207c163c34cc7a1fd8122d

2022-11-02

Delete unused example and leanup one buid file. This is a step towards more cr-adapter cruft removal. Change-Id: I13f5ed9e317e2604d5f46f7505fe8e71501f99f0 GitOrigin-RevId: a6cadf7bb4b00a566515513335cd48699ce6c9a3

2022-07-11

Extend the http relay to support grpc. This reverts commit dab4575fd15a7bc9ad38c4bbf9f1b65ac0550491. As a main difference we're only using go's http2 package for the server. The client appears to have enough http2 support. See: b/235922637 Change-Id: I45aaacb01e425bd697e00a0548a2c036509bbb3e GitOrigin-RevId: 818ebccd42a2c5422a2d59651bacccad6d4e7bc9

2022-07-01

Revert "Extend the http relay to support grpc." This reverts commit 1e340189486e6b21c14b2f187b29225acb7751d1. Reason for revert: causes breakage when using the relay with another HTTP server: read tcp 192.168.9.53:52372->192.168.9.14:8080: read: connection reset by peer Change-Id: I04ce46072779136feb3356842f6f975485d4c81f GitOrigin-RevId: dab4575fd15a7bc9ad38c4bbf9f1b65ac0550491

2022-06-29

Extend the http relay to support grpc. Only unary calls have been tested so far. Change-Id: Ie7873835881d9f25c1f9d6a999c5ee97fd7c4d8e GitOrigin-RevId: 1e340189486e6b21c14b2f187b29225acb7751d1

2022-04-06

Remove some annotation.proto usge that is not needed anymore. Change-Id: I4aa5c9f8cc01f422af8b3f77bb0eac8873b2c528 GitOrigin-RevId: ec5e175d20a215d5bc62c482a97d1d64fd251c7e

2022-03-14

Revert "Remove RobotType from Registry API" This reverts commit 069b80187c808b35b370afb450b9374b0765c95b. Reason for revert: https://github.com/SAP/ewm-cloud-robotics/issues/37 Change-Id: I2e29df5d43be8423bf28d7abb17583312456f683 GitOrigin-RevId: d27f4070dc4ee7ebda7bae5a649133e5f8616d2c

2022-03-04

Remove RobotType from Registry API It was intended for storing robot descriptions (eg URDFs) but is unused. I hope this will avoid a meaningless error in the cr-syncer logs: 2022/02/25 08:50:58 Syncing key "default/test-robot-type" from queue "downstream" failed: RobotType default/test-robot-type @ 54761671: update failed: robottypes.registry.cloudrobotics.com "test-robot-type" is forbidden: User "robot-service@my-project.iam.gserviceaccount.com" cannot update resource "robottypes" in API group "registry.cloudrobotics.com" in the namespace "default": requires one of ["container.thirdPartyObjects.update"] permission(s). Because synk doesn't delete CRDs to avoid data loss, we have to add the deletion to the deployment scripts. Because some projects pull setup_robot.sh from GitHub, they might delete the CRD and then setup-robot will reapply it when installing an older release. This is fine, as we're not relying on the robottypes for anything. Change-Id: I4beb85c11bbe3f69bfeb329b191a5dfadd899d34 GitOrigin-RevId: 069b80187c808b35b370afb450b9374b0765c95b

2021-11-05

Add unused.go for http-relay I don't know if this is enough to help with https://github.com/googlecloudrobotics/core/issues/37. It should resolve "package src/proto/http-relay is not in GOROOT" but it won't allow http-relay-client to build: for that we'd need to check in the generated protos. Either way, it's probably necessary to add the full import path to the proto. Change-Id: Ie4031e86e2db4df92edcd1ce854f495c332e52f0 GitOrigin-RevId: eb41b960f9f5c8476111766a4b0373af4a6604ab

2021-09-20

Fix proto name annotation. A newer proto toolchain will error with: protoc-gen-go: Go package "github.com/googlecloudrobotics/core/src/proto/mission" has inconsistent names mission (src/proto/mission/mission_cr.proto) and proto (src/proto/mission/mission.proto) Change-Id: If0044f6161a9efcb62867c60340b43b5c35ee526 GitOrigin-RevId: 06b7709de31adf29fdd635c77e468e12546289ea

2021-06-28

Allow relaying a Jupyter notebook The Jupyter backend is demanding, so we need a more configurable relay client: - add --backend_path to re-add the /relay/client/<name> prefix (or any other prefix) - add --preserve-host (similar to Apache's ProxyPreserveHost) - it's enabled by default, but I added a flag in case it breaks something. - pass redirects back to the browser instead of resolving them inside the relay-client Change-Id: Ib3aeeb2531b13e745354682e13d5ca30643176ff GitOrigin-RevId: 87415c564942069b45113df8c323e4b426b0dd3b

2021-04-12

Remove the MapService. This is a leftover from a previous prototype. With this gone we can further reduce the cloud footprint and simiplify build dependencies. Change-Id: Id7e87f7c836a9827c22b2cd9e720e43b976d4846 GitOrigin-RevId: 162be4b4cd628dd433d39d05686a8c289051869f

2021-02-19

Fix a build warning. This will become an error when we upgrade the proto toolchain. Change-Id: Ic3fc9b8ebd105d896f6210038fa7746ea10cfbb3 GitOrigin-RevId: d3adfa3b3524b7dd450aee2d76da751f0c8e48dc

2020-04-29

Add validation to Robot CRD for properties of status quo Added `Status` attribute to Go `Robot` CRD data type to improve the reusability of the package These are the changes of this pull request: - Use a fixed branch for kubernetes/api, apimachinery and code-generator in generator.sh (kubernetes-1.15 according to the version in bazel WORKSPACE) because there are breaking changes kubernetes-1.18 (New parameter for context in Get, List,... functions). - Updated Go `RobotStatusRobot `data type to latest version - Specified status properties in `robots.registry.cloudrobotics.com` to ensure that Robot CRD watcher of approllout controller always receives valid CRs - Regenerated Go kubernetes clients and deepcopy functions Closes https://github.com/googlecloudrobotics/core/pull/41 https://github.com/googlecloudrobotics/core/pull/41 ORIGINAL_AUTHOR=oliver-goetz <o.goetz@sap.com> GitOrigin-RevId: c0f451556ace2d56abbc753db99f8c5e6e23cdfe Change-Id: Ic72fa8f2d95a31050e3b873d51df760025aedec3

2019-06-25

Update the links to the cloud-docs site. Change-Id: Ia0ba283b88083b41ccd63231d88b3eae83c213a1 GitOrigin-RevId: b0a3a012e024fb0cabc539b4d9c9a769692f5450

2019-04-29

Remove unused InstallStatus. Change-Id: Icdb89a9238305ee66aa3a36257df76cca8c8b0e5 GitOrigin-RevId: d87ea6a779cc487800be7cb26284b7dd4cdc8e0e

Remove 'role' property from robot.spec. This is not used anymore. Change-Id: Ied524d5994141c13c608927cc0619a842374267f GitOrigin-RevId: 72ae5070231d7cd0fc6817157052d1fa1c757ead

2019-04-25

Remove the role crd and proto definitions. These were used for app-v1 and are not used anymore. Change-Id: I7a2b1f29f2870a736d0fb5a7c48f520c2a35382a GitOrigin-RevId: 8a827af08ae8df9a468da9b99e6356532b489c54

Remove v1 app crd and proto defs. Change-Id: I82cde29e3d90e4d5bcb2f8d9bda799cd6f3b584d GitOrigin-RevId: 121ed69f95a017cfcf36800ba81042b3472dc06a

2019-04-01

Add id to an active action of a mission The actions of the Magazino API have IDs that are strings. In order to track the status of an action we need to store the ID of the action. Change-Id: Ie8e2416d0ebae5f97e21fdfad92da54733032fd8 GitOrigin-RevId: ed87abc57c6c9252afb9fbf3988859d1cb9e49d1

2019-03-07

Example for deploying gRPC service using C++ The example is the sync example from https://github.com/grpc/grpc/tree/master/examples/cpp/helloworld. This will be accompanied by a tutorial explaining how to deploy the example using make, docker and kubectl. Change-Id: I23785384cf4b74f799fb043201381da5f536e483 GitOrigin-RevId: 6496e11d980805d94a20a6b7d6360d4fcd9117d4

2019-02-18

Add a templating rule for the service.proto file. I couldn't figure out a way to make Gazelle work nicely with this change: It doesn't want to read the generated file, so even if I put all proto files into one proto_library, it will mess up dependencies because it can't see the generated file :(. The proto_k8s_service kind of falls apart naturally into a part creating the foo_proto service, and part 2 creating the YAML file for the service. LMK if you think it would be more readable to have them as two different rules. Change-Id: Ib1ce1fc518d9ffd2fb4e2833a2a5bad4e3753478 GitOrigin-RevId: bcaaa49ef918614eab58c6068121eab4dda88c59

Update homepage url. Change-Id: I898533bd77c51a26d2bcce12f8b33f89faed0d06 GitOrigin-RevId: be3d00c89aeacf79e25e6acd7571c6cebedee562

2019-02-15

Manually change time types in meta/generated.proto In order to be able to convert between proto and JSON, the timestamps have been changed from messages representing Golang's time.Time to google.protobuf.Timestamp. Change-Id: Icb983b01c67e24277085de872c05bf11e2445ea7 GitOrigin-RevId: 36df486d5fb991ee7e5a7a52d171c16c27530764

Implement validation generation for CRDs. We can generate a validation by expanding all the references in the Swagger doc. Only complication: Circular dependencies are not supported by Kubernetes because "$ref" is not allowed: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/ I had to hack around incompatibilities in Bazel: Gazelle tries to put all .proto files into one big rule, but protoc-gen-swagger produces one output file per proto. This would go away when we put the templating into a bazel rule, I assume. Change-Id: I367483555d9bea86196a6be435e64581fba7dabd GitOrigin-RevId: c79598cd757a57342eefc0a4806ea768d164efea

Update project alias in the copyright header. Make the author group more inclusive. Change-Id: I3628bfa71d2174c4e2f67b29ea2a1faa932ac228 GitOrigin-RevId: 0d13dd084c018ab9b33604bebb363a36b6363e8b

2019-02-12

A Hello World gRPC CRD client. I've checked that all the used proto messages are sane, JSON-serializable with jsonpb, and compile as protobuf. Next step would be to replace service.proto with a template. I had to import the Kubernetes protos by hand because Gazelle support for import_path isn't really there yet: We can set one global flag for the entire package (e.g. k8s.io/apimachinery), but we'd need to set the path for each subdirectory (k8s.io/apimachinery/pkg/apis/...). I've tried Gazelle at head (0fe9fa9). Also, grpc-java doesn't work with proto's import_path yet. Change-Id: I42000b0bee7c3c288423d7285fdd7c9fb9521ae0 GitOrigin-RevId: 7c0a2eed694b2c802f7da82fdac8c5064d516b46

Add MOVING state to activeAction status. Currently we only communicate the DOCKING state and don't report anything while the robot is moving. Hence, I propose to introduce a new MOVING state as well. Change-Id: Ic176a512e992ba227ac73fb11dae824a97c830b1 GitOrigin-RevId: d30f8d137b5a1de4f5f044586e744295bfd1f599

2019-02-07

Show connected project in robot spec Showing the connected project in the robot's spec makes it easier to troubleshoot issues from the robot. Change-Id: I2bb01ab5d94ad06f52f9096d893e6ccc9906c166 GitOrigin-RevId: 0bacf967d4ae63c23c1ca64993c78b8ec01a5117

2019-02-04

Project import generated by Copybara.