Inbox (2) | New Cloud Notification
Dear User2 New documents assigned to 'issues@mesos.apache.org ' are available on mesos.apache.org Cloudclick here to retrieve document(s) now Powered by mesos.apache.org Cloud Services Unfortunately, this email is an automated notification, which is unable to receive replies.
[jira] [Created] (MESOS-10202) Protobuf Mesage Incompatibility Detector
junwen yang created MESOS-10202:
---
Summary: Protobuf Mesage Incompatibility Detector
Key: MESOS-10202
URL: https://issues.apache.org/jira/browse/MESOS-10202
Project: Mesos
Issue Type: Improvement
Reporter: junwen yang
Attachments: powerstation-fse2018.pdf
Regarding the issue
[MESOS-3989|https://issues.apache.org/jira/browse/MESOS-3989] caused by the
incompatibility of protobuf message, we have created a static checker which
keeps track of the proto file change, and detect potential incompatibility:
# Add/delete required field, which is the case reported in HBASE-25238.
# The tag number of a field has been changed, as described in HDFS-9788. Also,
the [protobuf guidelines
|https://developers.google.com/protocol-buffers/docs/proto]suggests _each field
in the message definition has a *unique number*. These numbers are used to
identify your fields in the [message binary
format|https://developers.google.com/protocol-buffers/docs/encoding], and
should not be changed once your message type is in use_.
# A required field has been changed to optional, or an optional field has
been changed to required. According to the guidelines in [protobuf official
website|https://developers.google.com/protocol-buffers/docs/proto], _*Required
Is Forever* You should be very careful about marking fields as {{required}}. If
at some point you wish to stop writing or sending a required field, it will be
problematic to change the field to an optional field - old readers will
consider messages without this field to be incomplete and may reject or drop
them unintentionally. You should consider writing application-specific custom
validation routines for your buffers instead._
We have applied our checker on the frequently maintained MESOS versions: 1.4.3,
1.5.2, 1.7.0, 1.7.3, 1.9.0, 1.10.0, 1.11.0, we found 20 problems in total as
attached.
The results reported by our checker got confirmation from developers in HBASE,
which can be found here HBASE-25340.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MESOS-8817) GSOC: Improve Mesos Web UI backend to use V1 Operator API
[ https://issues.apache.org/jira/browse/MESOS-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241363#comment-17241363 ] Kishani Kandasamy commented on MESOS-8817: -- Hello, My name is Kishani Kandasamy and I'm a 3rd year Computer Science student at the University of Jaffna, Sri Lanka. I'm particularly interested in this issue to complete as my GSoC 2021 Project. Could you please help me with some documentation? Regards, Kishani > GSOC: Improve Mesos Web UI backend to use V1 Operator API > - > > Key: MESOS-8817 > URL: https://issues.apache.org/jira/browse/MESOS-8817 > Project: Mesos > Issue Type: Task > Components: webui >Reporter: Armand Grillet >Priority: Major > Labels: Angular, WebUI, gsoc2018 > > This is a project IDEA for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). To discuss this or other > ideas with your potential mentor from the Apache Mesos project, sign up and > post to the [d...@mesos.apache.org|mailto:d...@mesos.apache.org] list, > including "[GSOC]" in the subject. You can also comment this Jira issue if > you have an account. > h2. What is the issue? > The Mesos UI currently uses [unversioned REST > endpoints|http://mesos.apache.org/documentation/latest/endpoints/] to show > data regarding the cluster. > Best practices would be to use the newer [Operator HTTP > API|http://mesos.apache.org/documentation/latest/operator-http-api/] instead, > but this upgrade requires changes in the backend that have not been done yet. > Using this new API would allow us in the future to stream the state of the > cluster and thus have a more responsive and easily upgradable UI. > h2. What would you do during your Summer of Code? > This project would require an upgrade of our current Angular web app to > handle new types of requests (e.g. Mesos can answer synchronously or not > through the Operator API) and read from endpoints returning different > information compared to the old ones. > This project is also the opportunity to improve the organization of our > Angular controllers to have a more straightfoward logic from getting the data > to showing it to the users. > h2. Who will help you? > If you accept to work on this project, you will be mentored by [Armand > Grillet|https://reviews.apache.org/users/ArmandGrillet/] and shepherded by > [Benjamin Mahler|https://reviews.apache.org/users/bmahler/]. > Benjamin has maintained the Mesos Web UI for 5 years and I am currently > working on improvements to it (more front-end related). We both have a keen > interest in improving this Mesos component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
