[VOTE] Release Apache Mesos 1.7.2 (rc1)

2019-02-19 Thread Gastón Kleiman
Hi all, Please vote on releasing the following candidate as Apache Mesos 1.7.2. 1.7.2 includes a number of bug fixes since 1.7.1; the CHANGELOG for the release is available at: https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.7.2-rc1

Re: [VOTE] Release Apache Mesos 1.6.2 (rc1)

2019-02-19 Thread Vinod Kone
Found a flaky test

[VOTE] Release Apache Mesos 1.6.2 (rc1)

2019-02-19 Thread Greg Mann
Hi all, Please vote on releasing the following candidate as Apache Mesos 1.6.2. 1.6.2 includes a number of bug fixes since 1.6.1; the CHANGELOG for the release is available at: https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.6.2-rc1

[API Working Group] Meeting today cancelled

2019-02-19 Thread Greg Mann
Hi all, We don't have any agenda items for the API working group meeting today, so I'm cancelling it. The next meeting will be held on March 5 at 11am PST, feel free to add items to the agenda here !

Failed accept: connection error: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca

2019-02-19 Thread Marc Roos
I keep getting unknown ca messages from the mesos-master after setting these in the environment. Are there specific settings for a browser client? The custom ca is installed on the server with update-ca-trust. LIBPROCESS_SSL_CA_FILE="/etc/pki/ca-trust/source/cust-ca.crt"

RE: ssl mesos-executor not using /etc/default/mesos

2019-02-19 Thread Marc Roos
Hi James, with your info on that the excutor runs inside the container, I need to provision the container environment with the certificate and key I guess before it starts the ssl connection. How can I do this? -Original Message- Sent: 18 February 2019 18:49 To: user Subject: Re: