Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Furkan KAMACI]

Hi,

I’ll try to compile it again. For the incorrect year in NOTICE, fixing it
at next release is fine as Justin mentioned.

Kind Regards,
Furkan KAMACI

On 1 Mar 2021 Mon at 10:42 Justin Mclean  wrote:

> HI,
>
> > Also, for the incorrect year in NOTICE. Should I fix it in this
> > release (and vote for another candidate) or fix it before the next
> > release version? Thanks.
>
> Fix it in the next release is fine IMO.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Justin Mclean]

HI,

> Also, for the incorrect year in NOTICE. Should I fix it in this
> release (and vote for another candidate) or fix it before the next
> release version? Thanks.

Fix it in the next release is fine IMO.

Thanks,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Hi Furkan,

I tried to compile it in Docker for macOS with 8 GB memory and can
compile it successfully (but pretty slow).

Can you verify that the `apache-teaclave-0.2.0-rc.1-incubating/keys`
directory exists? If possible, it's recommended to compile with docker
on Linux.

Also, for the incorrect year in NOTICE. Should I fix it in this
release (and vote for another candidate) or fix it before the next
release version? Thanks.

Best,
Mingshen Sun



On Sun, Feb 28, 2021 at 3:19 PM Matt Sicker  wrote:
>
> Alright, finally finished building and running tests. All passed after
> upping the memory limits to 8 GB, thought that might be overkill.
>
> +1
>
> On Sun, 28 Feb 2021 at 16:43, Yiming Jing  wrote:
> >
> > +1 approve
> >
> > On 2021/02/26 18:26:28, Mingshen Sun  wrote:
> > > Dear community,
> > >
> > > This is a call for a vote to release Apache Teaclave (incubating)
> > > version 0.2.0. This is the second Apache release since Teaclave
> > > entered the incubator.
> > >
> > > The Apache Teaclave (incubating) community has voted and approved the
> > > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > > Rundong Zhou, Tongxin Li).
> > >
> > > Vote/result thread:
> > >   - 
> > > https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> > >
> > > The release candidate is signed with a GPG key available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > >
> > > The Git commit for this release is:
> > >   - 
> > > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> > >
> > > The release note is available in:
> > >   - https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> > >
> > > Build guide and get started instructions can be found at:
> > >   - 
> > > https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> > >
> > > The short version of building Teaclave from the source tarball:
> > >
> > > ```
> > > $ wget 
> > > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> > > $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> > > apache-teaclave-0.2.0-rc.1-incubating
> > > $ # Instructions to verify the source tar:
> > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > >
> > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> > >bash -c ". /root/.cargo/env && \
> > >  . /opt/sgxsdk/environment && \
> > >  mkdir -p build && cd build && \
> > >  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > >  make"
> > > ```
> > >
> > > The vote will be open for at least 72 hours.
> > >
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove with the reason
> > >
> > >
> > > Best,
> > >
> > > Mingshen Sun
> > > http://mssun.me
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] lxdb - proposal for Apache Incubation

[Juan Pan]

Hi,


My +1 for the suggestions and summary from Furkan KAMACI.
They are truly many IPMC concerns, I guess.
Some of the items will need you plenty of time to handle, 
I am unsure whether it is the best time for you to propose now.
But, at least I suppose you have a direction to improve.


Sincerely,
Trista



---
Email：panj...@apache.org
Juan Pan(Trista) Apache ShardingSphere


On 02/28/2021 18:51，Furkan KAMACI wrote：
Hi,

Actually you have a detailed documentation which explains which approach
you have compared to similar systems and performance metrics of following
them i.e. reducing storage 10 to the 100 times or having low latency
queries.

My advices are (some of them are same with Sheng's and Liang's ):

1) Find an experienced mentor to guide you.

2) Start to translate your documentation to English.

3) Open source your project. How can we have a comment on your project if
we cannot see anything about it?

4) Gain contributors to your project. At least you should show your
intention to have committers/contributors out of your company. Eliminate
the risk of being non-meritocratic management of the project.

5) Structure your proposal. Explain why people need this project, which
problems do current projects have and how you managed to handle them. We
should understand is it a bundle of other projects, a completely new
project, or a wrapper of other projects which eliminates the shortcomings
of them.

6) Find a suitable name for your project in order to not try to solve
trademark problems that may lose your time if you enter the incubation.

Kind Regards,
Furkan KAMACI


On Sun, Feb 28, 2021 at 1:02 PM Liang Chen  wrote:

Hi

It would be better if you could find an experienced IPMC member to help you
for preparing the proposal.
Based on Sheng Wu input, i have one more comment : can you please explain
what are the different with other similar data analysis DB?  you can
consider explaining from use cases perspective.

Regards
Liang


fp wrote
Dear Apache Incubator Community,


Please accept the following proposal for presentation and discussion:
https://github.com/lucene-cn/lxdb/wiki


LXDB is a high-performance,OLAP,full text search database.it`s base on
hbase,but replaced hfile with lucene index to support more effective
secondary indexes,it`s also base on spark sql,so that you can used sql
api
to visit data and do olap calculate. and also the lucene index is store
on
hdfs (not local disk).


In our Production System, LXDB supported 200+ clusters,some of the single
cluster is 1000+ nodes,insert 200 billion rows  per day ( 2
billion rows for total), one of the biggest single table has 200million
lucene index on LXDB.


Hadoop`s father Doug Cutting cut nutch into HBase, MapReduce (hive),
HDFS,
Lucene.We have merged these separated projects again,LXDB equals
spark sql+hbase+lucene+parquet+hdfs,it is a super database.It took me 10
years to complete these merging operations.But the purpose is no longer a
search engine, but a database.





Best regards
  yannian mu




LXDB Proposal
== Abstract ==
LXDB is a high-performance,OLAP,full text search database.


=== it`s base on hbase,but replaced hfile with lucene index to support
more effective secondary indexes.=== 
we modify hbase region server ,we  change hfile to lucene,when put
data we put  document to lucene instande of  put data to hfile
lucene index store on region server  (it is not sote in
different cluster like elstice search+hbase ,it takes to copy of data)


=== it`s base on spark sql for olap=== 
we Integrated spark and hbase together ,it`s useage like this ,
1.unpackage lxdb.tar.gz 
2.config hadoop_config path,
3.run start-all.sh to start cluster. 
lxdb can startup spark through hadoop yarn ,and then spark executor
process Embedded start hbase region server service . 


you can operate lxdb database throuth spark sql api(hive) or mysql api.
1.the sql used spark rdd+hbase scaner  to visit hbase .
2.the sql`s condition (filter or group by agg) will predicate to hbase ,
3.hbase used lucene index to filter data in region server.
all of the spark,hbase,lucene is Embedded Integrated together,it is
not  a  seperate cluster ,that is the different with solr/es +
hbase+spark Solution.


== Background ==
=== Multiple copies of data ===
Apache HBase+Elastic Search is the most popular Solution on full text
search ,but it`s weak on Online AnalyticalProcessing.
so most of the time the Production System used spark(or hive or impala or
presto) ,hbase,solr/es at the same time.Multiple copies of data are
stored
in multiple systems,multiple systems has different Api .Data consistency
is difficult to guarantee.For the above reasons we merger
spark,hbase,elastic into one project .it`s target is used one copy of
data,one cluster,one api to solve olap,kv,full text...database scenarios.


=== Merging and splitting of lucene indexes(hstore) acrocess different
machine on hdfs ===
As we all know solr/es store file in 

[Cancel] [VOTE] Retire BlueMarlin project from Incubator

[Sheng Wu]

The BlueMarlin mail link is back to active.
I am canceling this retirement vote and will keep my eyes on it.
Thank you all.

Sheng Wu 吴晟
Twitter, wusheng1108


Sheng Wu  于2021年3月1日周一 上午8:16写道：

> Agree, I am watching the mail list, it seems better now.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Uma gangumalla  于2021年3月1日周一 上午4:59写道：
>
>> I agree, there is good progress. +1 to cancel the vote.
>>
>> Regards,
>> Uma
>>
>> On Sun, Feb 28, 2021 at 11:46 AM JB Onofré  wrote:
>>
>> > Hi
>> >
>> > Just to let you know that the BlueMarlin team showed great progress
>> about
>> > the donation and overall bootstrap. I will help them with the next
>> steps.
>> >
>> > What do you think about cancel this vote for now ?
>> >
>> > Thanks
>> > Regards
>> > JB
>> >
>> > > Le 23 févr. 2021 à 08:20, Jean-Baptiste Onofré 
>> a
>> > écrit :
>> > >
>> > > Hi Reza,
>> > >
>> > > it sounds like a plan. I will start to work on the repo (to prepare
>> code
>> > > donation) tomorrow. Let's keep in touch.
>> > >
>> > > Thanks,
>> > > Regards
>> > > JB
>> > >
>> > >> On Tue, Feb 23, 2021 at 1:09 AM Reza Adibnia <
>> > reza.adib...@futurewei.com>
>> > >> wrote:
>> > >>
>> > >> Hi JB,
>> > >>
>> > >> I guess Xun and I are now part of the d...@bluemarlin.apach.org
>> mailing
>> > >> list.  I will CC d...@bluemarlin.apach.org from now on.
>> > >>
>> > >> The existing code repository of blue-marlin project is
>> > >> https://github.com/Futurewei-io/blue-marlin
>> > >>
>> > >> I can help you with the migration. I will create a new branch called
>> > >> apache-migration from master and make the following changes.
>> > >>
>> > >> - check license (JB will do)
>> > >> - add ASF headers in all files (Reza will do)
>> > >> - add DISCLAIMER, LICENSE and NOTICE files (JB will do)
>> > >> - eventually rename packages/artifacts to org.apache.bluemarlin (Reza
>> > will
>> > >> do)
>> > >> - prepare a source artifact containing all and named with
>> > >> version-incubator (I don't know about this one)
>> > >>
>> > >> After it is done, you can go and check it.  I will start with
>> renaming
>> > >> packages and if you send me the ASF header I can fix the files as
>> well.
>> > >>
>> > >> Best,
>> > >>
>> > >> Reza.
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> -Original Message-
>> > >> From: Xun Hu 
>> > >> Sent: Sunday, February 21, 2021 10:20 PM
>> > >> To: Reza Adibnia ; Jean-Baptiste Onofré
>> <
>> > >> jbono...@yupiik.com>
>> > >> Subject: RE: [VOTE] Retire BlueMarlin project from Incubator
>> > >>
>> > >> Hi, JB,
>> > >>
>> > >> Thanks.
>> > >>
>> > >> @Reza Adibnia, please follow up with JB on all the steps and document
>> > it.
>> > >>
>> > >> Regards,
>> > >> -xun
>> > >>
>> > >>
>> > >> -Original Message-
>> > >> From: Jean-Baptiste Onofre 
>> > >> Sent: Sunday, February 21, 2021 10:16 PM
>> > >> To: general@incubator.apache.org
>> > >> Cc: Reza Adibnia 
>> > >> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
>> > >>
>> > >> No problem.
>> > >>
>> > >> So, if not done, please subscribe to d...@bluemarlin.apache.org
>> > > >> d...@bluemarlin.apache.org>.
>> > >>
>> > >> Then, can you please send the existing code repository details on dev
>> > >> mailing list ?
>> > >>
>> > >> Basically, the first steps is:
>> > >> - check license
>> > >> - add ASF headers in all files
>> > >> - add DISCLAIMER, LICENSE and NOTICE files
>> > >> - eventually rename packages/artifacts to org.apache.bluemarlin
>> > >> - prepare a source artifact containing all and named with
>> > version-incubator
>> > >>
>> > >> Once this is done (or meantime), we can move forward with website.
>> > >>
>> > >> Let’s move forward on dev mailing list about these actions.
>> > >>
>> > >> Thanks,
>> > >> Regards
>> > >> JB
>> > >>
>> >  Le 22 févr. 2021 à 07:12, Xun Hu  a écrit :
>> > >>>
>> > >>> Yes, please help us, we are not familiar with the process. Could you
>> > >> please work with Reza to finalize the process? We can follow it in
>> the
>> > >> future.
>> > >>>
>> > >>> Thanks,
>> > >>> -xun
>> > >>>
>> > >>>
>> > >>>
>> > >>> -Original Message-
>> > >>> From: Jean-Baptiste Onofre 
>> > >>> Sent: Sunday, February 21, 2021 10:10 PM
>> > >>> To: general@incubator.apache.org
>> > >>> Cc: Reza Adibnia 
>> > >>> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
>> > >>>
>> > >>> Hi,
>> > >>>
>> > >>> I think it’s important to keep the state on dev mailing list
>> > (publicly).
>> > >>>
>> > >>> The key think while in the incubator is to build/grow up the
>> community.
>> > >>>
>> > >>> So, let’s share the detail on the BlueMarlin dev mailing list and
>> move
>> > >> forward there.
>> > >>>
>> > >>> It’s important to give visibility to everyone.
>> > >>>
>> > >>> Thanks,
>> > >>> Regards
>> > >>> JB
>> > >>>
>> >  Le 22 févr. 2021 à 05:01, Xun Hu  a écrit :
>> > 
>> >  Hi, JB,
>> > 
>> >  Please check with Reza, we would like to work you closely to make
>> the
>> > >> donation.
>> > 
>> >  Thanks,

Re: [VOTE] Retire BlueMarlin project from Incubator

[Sheng Wu]

Agree, I am watching the mail list, it seems better now.

Sheng Wu 吴晟
Twitter, wusheng1108


Uma gangumalla  于2021年3月1日周一 上午4:59写道：

> I agree, there is good progress. +1 to cancel the vote.
>
> Regards,
> Uma
>
> On Sun, Feb 28, 2021 at 11:46 AM JB Onofré  wrote:
>
> > Hi
> >
> > Just to let you know that the BlueMarlin team showed great progress about
> > the donation and overall bootstrap. I will help them with the next steps.
> >
> > What do you think about cancel this vote for now ?
> >
> > Thanks
> > Regards
> > JB
> >
> > > Le 23 févr. 2021 à 08:20, Jean-Baptiste Onofré  a
> > écrit :
> > >
> > > Hi Reza,
> > >
> > > it sounds like a plan. I will start to work on the repo (to prepare
> code
> > > donation) tomorrow. Let's keep in touch.
> > >
> > > Thanks,
> > > Regards
> > > JB
> > >
> > >> On Tue, Feb 23, 2021 at 1:09 AM Reza Adibnia <
> > reza.adib...@futurewei.com>
> > >> wrote:
> > >>
> > >> Hi JB,
> > >>
> > >> I guess Xun and I are now part of the d...@bluemarlin.apach.org
> mailing
> > >> list.  I will CC d...@bluemarlin.apach.org from now on.
> > >>
> > >> The existing code repository of blue-marlin project is
> > >> https://github.com/Futurewei-io/blue-marlin
> > >>
> > >> I can help you with the migration. I will create a new branch called
> > >> apache-migration from master and make the following changes.
> > >>
> > >> - check license (JB will do)
> > >> - add ASF headers in all files (Reza will do)
> > >> - add DISCLAIMER, LICENSE and NOTICE files (JB will do)
> > >> - eventually rename packages/artifacts to org.apache.bluemarlin (Reza
> > will
> > >> do)
> > >> - prepare a source artifact containing all and named with
> > >> version-incubator (I don't know about this one)
> > >>
> > >> After it is done, you can go and check it.  I will start with renaming
> > >> packages and if you send me the ASF header I can fix the files as
> well.
> > >>
> > >> Best,
> > >>
> > >> Reza.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> -Original Message-
> > >> From: Xun Hu 
> > >> Sent: Sunday, February 21, 2021 10:20 PM
> > >> To: Reza Adibnia ; Jean-Baptiste Onofré <
> > >> jbono...@yupiik.com>
> > >> Subject: RE: [VOTE] Retire BlueMarlin project from Incubator
> > >>
> > >> Hi, JB,
> > >>
> > >> Thanks.
> > >>
> > >> @Reza Adibnia, please follow up with JB on all the steps and document
> > it.
> > >>
> > >> Regards,
> > >> -xun
> > >>
> > >>
> > >> -Original Message-
> > >> From: Jean-Baptiste Onofre 
> > >> Sent: Sunday, February 21, 2021 10:16 PM
> > >> To: general@incubator.apache.org
> > >> Cc: Reza Adibnia 
> > >> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
> > >>
> > >> No problem.
> > >>
> > >> So, if not done, please subscribe to d...@bluemarlin.apache.org
>  > >> d...@bluemarlin.apache.org>.
> > >>
> > >> Then, can you please send the existing code repository details on dev
> > >> mailing list ?
> > >>
> > >> Basically, the first steps is:
> > >> - check license
> > >> - add ASF headers in all files
> > >> - add DISCLAIMER, LICENSE and NOTICE files
> > >> - eventually rename packages/artifacts to org.apache.bluemarlin
> > >> - prepare a source artifact containing all and named with
> > version-incubator
> > >>
> > >> Once this is done (or meantime), we can move forward with website.
> > >>
> > >> Let’s move forward on dev mailing list about these actions.
> > >>
> > >> Thanks,
> > >> Regards
> > >> JB
> > >>
> >  Le 22 févr. 2021 à 07:12, Xun Hu  a écrit :
> > >>>
> > >>> Yes, please help us, we are not familiar with the process. Could you
> > >> please work with Reza to finalize the process? We can follow it in the
> > >> future.
> > >>>
> > >>> Thanks,
> > >>> -xun
> > >>>
> > >>>
> > >>>
> > >>> -Original Message-
> > >>> From: Jean-Baptiste Onofre 
> > >>> Sent: Sunday, February 21, 2021 10:10 PM
> > >>> To: general@incubator.apache.org
> > >>> Cc: Reza Adibnia 
> > >>> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
> > >>>
> > >>> Hi,
> > >>>
> > >>> I think it’s important to keep the state on dev mailing list
> > (publicly).
> > >>>
> > >>> The key think while in the incubator is to build/grow up the
> community.
> > >>>
> > >>> So, let’s share the detail on the BlueMarlin dev mailing list and
> move
> > >> forward there.
> > >>>
> > >>> It’s important to give visibility to everyone.
> > >>>
> > >>> Thanks,
> > >>> Regards
> > >>> JB
> > >>>
> >  Le 22 févr. 2021 à 05:01, Xun Hu  a écrit :
> > 
> >  Hi, JB,
> > 
> >  Please check with Reza, we would like to work you closely to make
> the
> > >> donation.
> > 
> >  Thanks,
> >  -xun
> > 
> > 
> >  -Original Message-
> >  From: Dave Fisher mailto:w...@apache.org>>
> >  Sent: Sunday, February 21, 2021 9:40 AM
> >  To: general@incubator.apache.org
> >  
> >  Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
> > 
> >  Hi JBO,
> > 
> >  Good luck with

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Matt Sicker]

Alright, finally finished building and running tests. All passed after
upping the memory limits to 8 GB, thought that might be overkill.

+1

On Sun, 28 Feb 2021 at 16:43, Yiming Jing  wrote:
>
> +1 approve
>
> On 2021/02/26 18:26:28, Mingshen Sun  wrote:
> > Dear community,
> >
> > This is a call for a vote to release Apache Teaclave (incubating)
> > version 0.2.0. This is the second Apache release since Teaclave
> > entered the incubator.
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > Rundong Zhou, Tongxin Li).
> >
> > Vote/result thread:
> >   - 
> > https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> >
> > The release candidate to be voted over is available at:
> >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> >
> > The release candidate is signed with a GPG key available at:
> >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> >
> > The Git commit for this release is:
> >   - 
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> >
> > The release note is available in:
> >   - https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> >
> > Build guide and get started instructions can be found at:
> >   - 
> > https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> >
> > The short version of building Teaclave from the source tarball:
> >
> > ```
> > $ wget 
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> > $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> > apache-teaclave-0.2.0-rc.1-incubating
> > $ # Instructions to verify the source tar:
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> >
> > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> >bash -c ". /root/.cargo/env && \
> >  . /opt/sgxsdk/environment && \
> >  mkdir -p build && cd build && \
> >  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> >  make"
> > ```
> >
> > The vote will be open for at least 72 hours.
> >
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> >
> >
> > Best,
> >
> > Mingshen Sun
> > http://mssun.me
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Yiming Jing]

+1 approve

On 2021/02/26 18:26:28, Mingshen Sun  wrote: 
> Dear community,
> 
> This is a call for a vote to release Apache Teaclave (incubating)
> version 0.2.0. This is the second Apache release since Teaclave
> entered the incubator.
> 
> The Apache Teaclave (incubating) community has voted and approved the
> release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> Rundong Zhou, Tongxin Li).
> 
> Vote/result thread:
>   - 
> https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> 
> The release candidate to be voted over is available at:
>   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> 
> The release candidate is signed with a GPG key available at:
>   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> 
> The Git commit for this release is:
>   - 
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> 
> The release note is available in:
>   - https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> 
> Build guide and get started instructions can be found at:
>   - 
> https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> 
> The short version of building Teaclave from the source tarball:
> 
> ```
> $ wget 
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> apache-teaclave-0.2.0-rc.1-incubating
> $ # Instructions to verify the source tar:
> https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> 
> $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
>   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
>bash -c ". /root/.cargo/env && \
>  . /opt/sgxsdk/environment && \
>  mkdir -p build && cd build && \
>  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
>  make"
> ```
> 
> The vote will be open for at least 72 hours.
> 
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove with the reason
> 
> 
> Best,
> 
> Mingshen Sun
> http://mssun.me
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Furkan KAMACI]

Hi Mingshen,

Yes, I’ve tried it on macOS.

Kind Regards,
Furkan KAMACI

On 28 Feb 2021 Sun at 23:46 Tongxin Li  wrote:

> +1
>
> On 2021/02/28 20:12:23, Pei Wang  wrote:
> > +1
> >
> > On 2021/02/26 18:26:28 Mingshen Sun wrote:
> > > Dear community,
> > >
> > > This is a call for a vote to release Apache Teaclave (incubating)
> > > version 0.2.0. This is the second Apache release since Teaclave
> > > entered the incubator.
> > >
> > > The Apache Teaclave (incubating) community has voted and approved the
> > > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > > Rundong Zhou, Tongxin Li).
> > >
> > > Vote/result thread:
> > >   -
> https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > >   -
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> > >
> > > The release candidate is signed with a GPG key available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > >
> > > The Git commit for this release is:
> > >   -
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> > >
> > > The release note is available in:
> > >   -
> https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> > >
> > > Build guide and get started instructions can be found at:
> > >   -
> https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> > >
> > > The short version of building Teaclave from the source tarball:
> > >
> > > ```
> > > $ wget
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> > > $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> > > apache-teaclave-0.2.0-rc.1-incubating
> > > $ # Instructions to verify the source tar:
> > >
> https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > >
> > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> > >bash -c ". /root/.cargo/env && \
> > >  . /opt/sgxsdk/environment && \
> > >  mkdir -p build && cd build && \
> > >  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > >  make"
> > > ```
> > >
> > > The vote will be open for at least 72 hours.
> > >
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove with the reason
> > >
> > >
> > > Best,
> > >
> > > Mingshen Sun
> > > http://mssun.me
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire BlueMarlin project from Incubator

[Uma gangumalla]

I agree, there is good progress. +1 to cancel the vote.

Regards,
Uma

On Sun, Feb 28, 2021 at 11:46 AM JB Onofré  wrote:

> Hi
>
> Just to let you know that the BlueMarlin team showed great progress about
> the donation and overall bootstrap. I will help them with the next steps.
>
> What do you think about cancel this vote for now ?
>
> Thanks
> Regards
> JB
>
> > Le 23 févr. 2021 à 08:20, Jean-Baptiste Onofré  a
> écrit :
> >
> > Hi Reza,
> >
> > it sounds like a plan. I will start to work on the repo (to prepare code
> > donation) tomorrow. Let's keep in touch.
> >
> > Thanks,
> > Regards
> > JB
> >
> >> On Tue, Feb 23, 2021 at 1:09 AM Reza Adibnia <
> reza.adib...@futurewei.com>
> >> wrote:
> >>
> >> Hi JB,
> >>
> >> I guess Xun and I are now part of the d...@bluemarlin.apach.org mailing
> >> list.  I will CC d...@bluemarlin.apach.org from now on.
> >>
> >> The existing code repository of blue-marlin project is
> >> https://github.com/Futurewei-io/blue-marlin
> >>
> >> I can help you with the migration. I will create a new branch called
> >> apache-migration from master and make the following changes.
> >>
> >> - check license (JB will do)
> >> - add ASF headers in all files (Reza will do)
> >> - add DISCLAIMER, LICENSE and NOTICE files (JB will do)
> >> - eventually rename packages/artifacts to org.apache.bluemarlin (Reza
> will
> >> do)
> >> - prepare a source artifact containing all and named with
> >> version-incubator (I don't know about this one)
> >>
> >> After it is done, you can go and check it.  I will start with renaming
> >> packages and if you send me the ASF header I can fix the files as well.
> >>
> >> Best,
> >>
> >> Reza.
> >>
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: Xun Hu 
> >> Sent: Sunday, February 21, 2021 10:20 PM
> >> To: Reza Adibnia ; Jean-Baptiste Onofré <
> >> jbono...@yupiik.com>
> >> Subject: RE: [VOTE] Retire BlueMarlin project from Incubator
> >>
> >> Hi, JB,
> >>
> >> Thanks.
> >>
> >> @Reza Adibnia, please follow up with JB on all the steps and document
> it.
> >>
> >> Regards,
> >> -xun
> >>
> >>
> >> -Original Message-
> >> From: Jean-Baptiste Onofre 
> >> Sent: Sunday, February 21, 2021 10:16 PM
> >> To: general@incubator.apache.org
> >> Cc: Reza Adibnia 
> >> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
> >>
> >> No problem.
> >>
> >> So, if not done, please subscribe to d...@bluemarlin.apache.org  >> d...@bluemarlin.apache.org>.
> >>
> >> Then, can you please send the existing code repository details on dev
> >> mailing list ?
> >>
> >> Basically, the first steps is:
> >> - check license
> >> - add ASF headers in all files
> >> - add DISCLAIMER, LICENSE and NOTICE files
> >> - eventually rename packages/artifacts to org.apache.bluemarlin
> >> - prepare a source artifact containing all and named with
> version-incubator
> >>
> >> Once this is done (or meantime), we can move forward with website.
> >>
> >> Let’s move forward on dev mailing list about these actions.
> >>
> >> Thanks,
> >> Regards
> >> JB
> >>
>  Le 22 févr. 2021 à 07:12, Xun Hu  a écrit :
> >>>
> >>> Yes, please help us, we are not familiar with the process. Could you
> >> please work with Reza to finalize the process? We can follow it in the
> >> future.
> >>>
> >>> Thanks,
> >>> -xun
> >>>
> >>>
> >>>
> >>> -Original Message-
> >>> From: Jean-Baptiste Onofre 
> >>> Sent: Sunday, February 21, 2021 10:10 PM
> >>> To: general@incubator.apache.org
> >>> Cc: Reza Adibnia 
> >>> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
> >>>
> >>> Hi,
> >>>
> >>> I think it’s important to keep the state on dev mailing list
> (publicly).
> >>>
> >>> The key think while in the incubator is to build/grow up the community.
> >>>
> >>> So, let’s share the detail on the BlueMarlin dev mailing list and move
> >> forward there.
> >>>
> >>> It’s important to give visibility to everyone.
> >>>
> >>> Thanks,
> >>> Regards
> >>> JB
> >>>
>  Le 22 févr. 2021 à 05:01, Xun Hu  a écrit :
> 
>  Hi, JB,
> 
>  Please check with Reza, we would like to work you closely to make the
> >> donation.
> 
>  Thanks,
>  -xun
> 
> 
>  -Original Message-
>  From: Dave Fisher mailto:w...@apache.org>>
>  Sent: Sunday, February 21, 2021 9:40 AM
>  To: general@incubator.apache.org
>  
>  Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
> 
>  Hi JBO,
> 
>  Good luck with that. I’ll hold back my vote for two weeks.
> 
>  Regards,
>  Dave
> 
>  Sent from my iPhone
> 
> > On Feb 21, 2021, at 8:55 AM, Jean-Baptiste Onofre 
> >> wrote:
> >
> > Hi,
> >
> > I kindly request a couple of weeks about moving forward with this
> >> vote. I try a new time to ping the BlueMarlin team to move forward with
> >> code donation and bootstrap the project. I have to admit that it’s super
> >> long and I have some diffic

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Tongxin Li]

+1

On 2021/02/28 20:12:23, Pei Wang  wrote: 
> +1
> 
> On 2021/02/26 18:26:28 Mingshen Sun wrote:
> > Dear community,
> > 
> > This is a call for a vote to release Apache Teaclave (incubating)
> > version 0.2.0. This is the second Apache release since Teaclave
> > entered the incubator.
> > 
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > Rundong Zhou, Tongxin Li).
> > 
> > Vote/result thread:
> >   - 
> > https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> > 
> > The release candidate to be voted over is available at:
> >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> > 
> > The release candidate is signed with a GPG key available at:
> >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > 
> > The Git commit for this release is:
> >   - 
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> > 
> > The release note is available in:
> >   - https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> > 
> > Build guide and get started instructions can be found at:
> >   - 
> > https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> > 
> > The short version of building Teaclave from the source tarball:
> > 
> > ```
> > $ wget 
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> > $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> > apache-teaclave-0.2.0-rc.1-incubating
> > $ # Instructions to verify the source tar:
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > 
> > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> >bash -c ". /root/.cargo/env && \
> >  . /opt/sgxsdk/environment && \
> >  mkdir -p build && cd build && \
> >  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> >  make"
> > ```
> > 
> > The vote will be open for at least 72 hours.
> > 
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> > 
> > 
> > Best,
> > 
> > Mingshen Sun
> > http://mssun.me
> > 
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> > 
> > 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Matt Sicker]

Alright, I'll try compiling with more resources allocated to Docker
and report back.

On Sun, 28 Feb 2021 at 14:10, Mingshen Sun  wrote:
>
> Hi Matt,
>
> For your case, I believe it is because of the memory limit
> (out-of-memory) of Docker for macOS. The Rust compiler needs more
> memory than others.
>
> Best,
> Mingshen
>
>
> On Sun, Feb 28, 2021 at 11:57 AM Matt Sicker  wrote:
> >
> > I tried building on macOS as well, and it got fairly far and ended up
> > failing at this point:
> >
> > Scanning dependencies of target sgxlib-teaclave_authentication_service
> > [ 37%] Building sgxlib-teaclave_authentication_service, enclave info
> > to 
> > /teaclave/build/intermediate/teaclave_authentication_service_enclave_info.toml
> >Compiling crc v2.0.0 
> > (https://github.com/mesalock-linux/crc-rs-sgx#86696be0)
> >Compiling teaclave_proto v0.2.0
> > (/teaclave/build/cmake_tomls/sgx_trusted_lib/services/proto)
> >Compiling integer-encoding v1.0.7
> >Compiling snap v0.2.5
> >Compiling jsonwebtoken v6.0.1
> > error: could not compile `crc`.
> >
> > Caused by:
> >   process didn't exit successfully:
> > `/teaclave/cmake/scripts/rustc_wrapper.sh --crate-name crc
> > --edition=2018 
> > /teaclave/build/cmake_tomls/sgx_trusted_lib/third_party/crates-sgx/vendor/crc/src/lib.rs
> > --error-format=json --json=diagnostic-rendered-ansi,artifacts
> > --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> > metadata=39ca99cb54d77a3c -C extra-filename=-39ca99cb54d77a3c
> > --out-dir /teaclave/build/target/trusted/debug/deps -L
> > dependency=/teaclave/build/target/trusted/debug/deps --cap-lints allow
> > --cfg test_mode` (signal: 9, SIGKILL: kill)
> > /usr/bin/ld: cannot find -lteaclave_authentication_service_enclave
> > collect2: error: ld returned 1 exit status
> > CMakeFiles/sgxlib-teaclave_authentication_service.dir/build.make:57:
> > recipe for target 'CMakeFiles/sgxlib-teaclave_authentication_service'
> > failed
> > make[2]: *** [CMakeFiles/sgxlib-teaclave_authentication_service] Error 1
> > CMakeFiles/Makefile2:301: recipe for target
> > 'CMakeFiles/sgxlib-teaclave_authentication_service.dir/all' failed
> > make[1]: *** [CMakeFiles/sgxlib-teaclave_authentication_service.dir/all] 
> > Error 2
> > Makefile:83: recipe for target 'all' failed
> > make: *** [all] Error 2
> >
> > Full build log output here:
> > https://gist.github.com/jvz/b214f28b788f6459b8e511149781e52a
> >
> > Signatures, notice, license, disclaimer all good.
> >
> > On Sun, 28 Feb 2021 at 13:37, Mingshen Sun  wrote:
> > >
> > > Thanks Furkan,
> > >
> > > I just tried to download and compile it in a clean Linux environment,
> > > and can successfully compile the code.
> > >
> > > Are you working on macOS? Because of the case-insensitive file system
> > > of macOS, Git cannot distinguish the KEYS file and keys directory.
> > > That may cause the keys directory is not checkout.
> > >
> > > I'll fix this in the next release.
> > >
> > > Best,
> > > Mingshen
> > >
> > > On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI  
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > +1 from me (I have notes below).
> > > >
> > > > I checked:
> > > >
> > > > - Incubating in name
> > > > - DISCLAIMER-WIP exists
> > > > - LICENSE is fine
> > > > - NOTICE has *incorrect* *year* which should be fixed
> > > > - No unexpected binary files
> > > > - Checked PGP signatures
> > > > - Checked checksums
> > > >
> > > > I got that error while compiling the project:
> > > >
> > > > Digest:
> > > > sha256:cb80cb3da4ddb15713ecd7ea8b6f4eab144c402644ece8116e762a19886d7ada
> > > > Status: Downloaded newer image for
> > > > teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
> > > > -- The C compiler identification is GNU 7.5.0
> > > > -- Check for working C compiler: /usr/bin/cc
> > > > -- Check for working C compiler: /usr/bin/cc -- works
> > > > -- Detecting C compiler ABI info
> > > > -- Detecting C compiler ABI info - done
> > > > -- Detecting C compile features
> > > > -- Detecting C compile features - done
> > > > -- Found Git: /usr/bin/git (found version "2.27.0")
> > > > -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version
> > > > "1.1.1")
> > > > SGX_SDK=/opt/sgxsdk
> > > > SGX_MODE=HW
> > > > RUSTUP_TOOLCHAIN=nightly-2020-04-07
> > > > DCAP=OFF
> > > > BUILD_TYPE=debug
> > > > TEACLAVE_SYMLINKS=/tmp/teaclave_symlinks.Dvayr2ejnVKi
> > > > -- == /teaclave/build/environment GENERATED ==
> > > > -- Configuring done
> > > > -- Generating done
> > > > -- Build files have been written to: /teaclave/build
> > > > Scanning dependencies of target prep
> > > > cp: cannot stat '/teaclave/keys/dcap_server_cert.pem': Not a directory
> > > > CMakeFiles/prep.dir/build.make:57: recipe for target 'CMakeFiles/prep'
> > > > failed
> > > > make[2]: *** [CMakeFiles/prep] Error 1
> > > > CMakeFiles/Makefile2:819: recipe for target 'CMakeFiles/prep.dir/all' 
> > > > failed
> > > > make[1]: *** [CMakeFiles/prep.dir/all] Error 2
> > > > Makefile:83: recip

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Pei Wang]

+1

On 2021/02/26 18:26:28 Mingshen Sun wrote:
> Dear community,
> 
> This is a call for a vote to release Apache Teaclave (incubating)
> version 0.2.0. This is the second Apache release since Teaclave
> entered the incubator.
> 
> The Apache Teaclave (incubating) community has voted and approved the
> release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> Rundong Zhou, Tongxin Li).
> 
> Vote/result thread:
>   - 
> https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> 
> The release candidate to be voted over is available at:
>   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> 
> The release candidate is signed with a GPG key available at:
>   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> 
> The Git commit for this release is:
>   - 
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> 
> The release note is available in:
>   - https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> 
> Build guide and get started instructions can be found at:
>   - 
> https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> 
> The short version of building Teaclave from the source tarball:
> 
> ```
> $ wget 
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> apache-teaclave-0.2.0-rc.1-incubating
> $ # Instructions to verify the source tar:
> https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> 
> $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
>   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
>bash -c ". /root/.cargo/env && \
>  . /opt/sgxsdk/environment && \
>  mkdir -p build && cd build && \
>  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
>  make"
> ```
> 
> The vote will be open for at least 72 hours.
> 
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove with the reason
> 
> 
> Best,
> 
> Mingshen Sun
> http://mssun.me
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Rundong Zhou]

+1

Regards,
Rundong

On 2021/02/28 20:09:39, Mingshen Sun  wrote: 
> Hi Matt,
> 
> For your case, I believe it is because of the memory limit
> (out-of-memory) of Docker for macOS. The Rust compiler needs more
> memory than others.
> 
> Best,
> Mingshen
> 
> 
> On Sun, Feb 28, 2021 at 11:57 AM Matt Sicker  wrote:
> >
> > I tried building on macOS as well, and it got fairly far and ended up
> > failing at this point:
> >
> > Scanning dependencies of target sgxlib-teaclave_authentication_service
> > [ 37%] Building sgxlib-teaclave_authentication_service, enclave info
> > to 
> > /teaclave/build/intermediate/teaclave_authentication_service_enclave_info.toml
> >Compiling crc v2.0.0 
> > (https://github.com/mesalock-linux/crc-rs-sgx#86696be0)
> >Compiling teaclave_proto v0.2.0
> > (/teaclave/build/cmake_tomls/sgx_trusted_lib/services/proto)
> >Compiling integer-encoding v1.0.7
> >Compiling snap v0.2.5
> >Compiling jsonwebtoken v6.0.1
> > error: could not compile `crc`.
> >
> > Caused by:
> >   process didn't exit successfully:
> > `/teaclave/cmake/scripts/rustc_wrapper.sh --crate-name crc
> > --edition=2018 
> > /teaclave/build/cmake_tomls/sgx_trusted_lib/third_party/crates-sgx/vendor/crc/src/lib.rs
> > --error-format=json --json=diagnostic-rendered-ansi,artifacts
> > --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> > metadata=39ca99cb54d77a3c -C extra-filename=-39ca99cb54d77a3c
> > --out-dir /teaclave/build/target/trusted/debug/deps -L
> > dependency=/teaclave/build/target/trusted/debug/deps --cap-lints allow
> > --cfg test_mode` (signal: 9, SIGKILL: kill)
> > /usr/bin/ld: cannot find -lteaclave_authentication_service_enclave
> > collect2: error: ld returned 1 exit status
> > CMakeFiles/sgxlib-teaclave_authentication_service.dir/build.make:57:
> > recipe for target 'CMakeFiles/sgxlib-teaclave_authentication_service'
> > failed
> > make[2]: *** [CMakeFiles/sgxlib-teaclave_authentication_service] Error 1
> > CMakeFiles/Makefile2:301: recipe for target
> > 'CMakeFiles/sgxlib-teaclave_authentication_service.dir/all' failed
> > make[1]: *** [CMakeFiles/sgxlib-teaclave_authentication_service.dir/all] 
> > Error 2
> > Makefile:83: recipe for target 'all' failed
> > make: *** [all] Error 2
> >
> > Full build log output here:
> > https://gist.github.com/jvz/b214f28b788f6459b8e511149781e52a
> >
> > Signatures, notice, license, disclaimer all good.
> >
> > On Sun, 28 Feb 2021 at 13:37, Mingshen Sun  wrote:
> > >
> > > Thanks Furkan,
> > >
> > > I just tried to download and compile it in a clean Linux environment,
> > > and can successfully compile the code.
> > >
> > > Are you working on macOS? Because of the case-insensitive file system
> > > of macOS, Git cannot distinguish the KEYS file and keys directory.
> > > That may cause the keys directory is not checkout.
> > >
> > > I'll fix this in the next release.
> > >
> > > Best,
> > > Mingshen
> > >
> > > On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI  
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > +1 from me (I have notes below).
> > > >
> > > > I checked:
> > > >
> > > > - Incubating in name
> > > > - DISCLAIMER-WIP exists
> > > > - LICENSE is fine
> > > > - NOTICE has *incorrect* *year* which should be fixed
> > > > - No unexpected binary files
> > > > - Checked PGP signatures
> > > > - Checked checksums
> > > >
> > > > I got that error while compiling the project:
> > > >
> > > > Digest:
> > > > sha256:cb80cb3da4ddb15713ecd7ea8b6f4eab144c402644ece8116e762a19886d7ada
> > > > Status: Downloaded newer image for
> > > > teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
> > > > -- The C compiler identification is GNU 7.5.0
> > > > -- Check for working C compiler: /usr/bin/cc
> > > > -- Check for working C compiler: /usr/bin/cc -- works
> > > > -- Detecting C compiler ABI info
> > > > -- Detecting C compiler ABI info - done
> > > > -- Detecting C compile features
> > > > -- Detecting C compile features - done
> > > > -- Found Git: /usr/bin/git (found version "2.27.0")
> > > > -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version
> > > > "1.1.1")
> > > > SGX_SDK=/opt/sgxsdk
> > > > SGX_MODE=HW
> > > > RUSTUP_TOOLCHAIN=nightly-2020-04-07
> > > > DCAP=OFF
> > > > BUILD_TYPE=debug
> > > > TEACLAVE_SYMLINKS=/tmp/teaclave_symlinks.Dvayr2ejnVKi
> > > > -- == /teaclave/build/environment GENERATED ==
> > > > -- Configuring done
> > > > -- Generating done
> > > > -- Build files have been written to: /teaclave/build
> > > > Scanning dependencies of target prep
> > > > cp: cannot stat '/teaclave/keys/dcap_server_cert.pem': Not a directory
> > > > CMakeFiles/prep.dir/build.make:57: recipe for target 'CMakeFiles/prep'
> > > > failed
> > > > make[2]: *** [CMakeFiles/prep] Error 1
> > > > CMakeFiles/Makefile2:819: recipe for target 'CMakeFiles/prep.dir/all' 
> > > > failed
> > > > make[1]: *** [CMakeFiles/prep.dir/all] Error 2
> > > > Makefile:83: recipe for target 'all' failed
> > > > make: *** [all] Error 2
> > > >
>

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Hi Matt,

For your case, I believe it is because of the memory limit
(out-of-memory) of Docker for macOS. The Rust compiler needs more
memory than others.

Best,
Mingshen


On Sun, Feb 28, 2021 at 11:57 AM Matt Sicker  wrote:
>
> I tried building on macOS as well, and it got fairly far and ended up
> failing at this point:
>
> Scanning dependencies of target sgxlib-teaclave_authentication_service
> [ 37%] Building sgxlib-teaclave_authentication_service, enclave info
> to 
> /teaclave/build/intermediate/teaclave_authentication_service_enclave_info.toml
>Compiling crc v2.0.0 
> (https://github.com/mesalock-linux/crc-rs-sgx#86696be0)
>Compiling teaclave_proto v0.2.0
> (/teaclave/build/cmake_tomls/sgx_trusted_lib/services/proto)
>Compiling integer-encoding v1.0.7
>Compiling snap v0.2.5
>Compiling jsonwebtoken v6.0.1
> error: could not compile `crc`.
>
> Caused by:
>   process didn't exit successfully:
> `/teaclave/cmake/scripts/rustc_wrapper.sh --crate-name crc
> --edition=2018 
> /teaclave/build/cmake_tomls/sgx_trusted_lib/third_party/crates-sgx/vendor/crc/src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts
> --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> metadata=39ca99cb54d77a3c -C extra-filename=-39ca99cb54d77a3c
> --out-dir /teaclave/build/target/trusted/debug/deps -L
> dependency=/teaclave/build/target/trusted/debug/deps --cap-lints allow
> --cfg test_mode` (signal: 9, SIGKILL: kill)
> /usr/bin/ld: cannot find -lteaclave_authentication_service_enclave
> collect2: error: ld returned 1 exit status
> CMakeFiles/sgxlib-teaclave_authentication_service.dir/build.make:57:
> recipe for target 'CMakeFiles/sgxlib-teaclave_authentication_service'
> failed
> make[2]: *** [CMakeFiles/sgxlib-teaclave_authentication_service] Error 1
> CMakeFiles/Makefile2:301: recipe for target
> 'CMakeFiles/sgxlib-teaclave_authentication_service.dir/all' failed
> make[1]: *** [CMakeFiles/sgxlib-teaclave_authentication_service.dir/all] 
> Error 2
> Makefile:83: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Full build log output here:
> https://gist.github.com/jvz/b214f28b788f6459b8e511149781e52a
>
> Signatures, notice, license, disclaimer all good.
>
> On Sun, 28 Feb 2021 at 13:37, Mingshen Sun  wrote:
> >
> > Thanks Furkan,
> >
> > I just tried to download and compile it in a clean Linux environment,
> > and can successfully compile the code.
> >
> > Are you working on macOS? Because of the case-insensitive file system
> > of macOS, Git cannot distinguish the KEYS file and keys directory.
> > That may cause the keys directory is not checkout.
> >
> > I'll fix this in the next release.
> >
> > Best,
> > Mingshen
> >
> > On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI  
> > wrote:
> > >
> > > Hi,
> > >
> > > +1 from me (I have notes below).
> > >
> > > I checked:
> > >
> > > - Incubating in name
> > > - DISCLAIMER-WIP exists
> > > - LICENSE is fine
> > > - NOTICE has *incorrect* *year* which should be fixed
> > > - No unexpected binary files
> > > - Checked PGP signatures
> > > - Checked checksums
> > >
> > > I got that error while compiling the project:
> > >
> > > Digest:
> > > sha256:cb80cb3da4ddb15713ecd7ea8b6f4eab144c402644ece8116e762a19886d7ada
> > > Status: Downloaded newer image for
> > > teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
> > > -- The C compiler identification is GNU 7.5.0
> > > -- Check for working C compiler: /usr/bin/cc
> > > -- Check for working C compiler: /usr/bin/cc -- works
> > > -- Detecting C compiler ABI info
> > > -- Detecting C compiler ABI info - done
> > > -- Detecting C compile features
> > > -- Detecting C compile features - done
> > > -- Found Git: /usr/bin/git (found version "2.27.0")
> > > -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version
> > > "1.1.1")
> > > SGX_SDK=/opt/sgxsdk
> > > SGX_MODE=HW
> > > RUSTUP_TOOLCHAIN=nightly-2020-04-07
> > > DCAP=OFF
> > > BUILD_TYPE=debug
> > > TEACLAVE_SYMLINKS=/tmp/teaclave_symlinks.Dvayr2ejnVKi
> > > -- == /teaclave/build/environment GENERATED ==
> > > -- Configuring done
> > > -- Generating done
> > > -- Build files have been written to: /teaclave/build
> > > Scanning dependencies of target prep
> > > cp: cannot stat '/teaclave/keys/dcap_server_cert.pem': Not a directory
> > > CMakeFiles/prep.dir/build.make:57: recipe for target 'CMakeFiles/prep'
> > > failed
> > > make[2]: *** [CMakeFiles/prep] Error 1
> > > CMakeFiles/Makefile2:819: recipe for target 'CMakeFiles/prep.dir/all' 
> > > failed
> > > make[1]: *** [CMakeFiles/prep.dir/all] Error 2
> > > Makefile:83: recipe for target 'all' failed
> > > make: *** [all] Error 2
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > On Fri, Feb 26, 2021 at 10:42 PM Yu Ding  wrote:
> > >
> > > > +1 approve
> > > >
> > > > On 2021/02/26 18:26:28, Mingshen Sun  wrote:
> > > > > Dear community,
> > > > >
> > > > > This is a call for a vote to release Apache Teaclave (incubating)
> > > > > version 0.2.0.

Re: [VOTE] Retire BlueMarlin project from Incubator

[Dave Fisher]

I agree.

I’m now -1.

Good luck.

Sent from my iPhone

> On Feb 28, 2021, at 11:46 AM, JB Onofré  wrote:
> 
> Hi
> 
> Just to let you know that the BlueMarlin team showed great progress about the 
> donation and overall bootstrap. I will help them with the next steps. 
> 
> What do you think about cancel this vote for now ?
> 
> Thanks 
> Regards 
> JB
> 
>> Le 23 févr. 2021 à 08:20, Jean-Baptiste Onofré  a écrit 
>> :
>> 
>> Hi Reza,
>> 
>> it sounds like a plan. I will start to work on the repo (to prepare code
>> donation) tomorrow. Let's keep in touch.
>> 
>> Thanks,
>> Regards
>> JB
>> 
>>> On Tue, Feb 23, 2021 at 1:09 AM Reza Adibnia 
>>> wrote:
>>> 
>>> Hi JB,
>>> 
>>> I guess Xun and I are now part of the d...@bluemarlin.apach.org mailing
>>> list.  I will CC d...@bluemarlin.apach.org from now on.
>>> 
>>> The existing code repository of blue-marlin project is
>>> https://github.com/Futurewei-io/blue-marlin
>>> 
>>> I can help you with the migration. I will create a new branch called
>>> apache-migration from master and make the following changes.
>>> 
>>> - check license (JB will do)
>>> - add ASF headers in all files (Reza will do)
>>> - add DISCLAIMER, LICENSE and NOTICE files (JB will do)
>>> - eventually rename packages/artifacts to org.apache.bluemarlin (Reza will
>>> do)
>>> - prepare a source artifact containing all and named with
>>> version-incubator (I don't know about this one)
>>> 
>>> After it is done, you can go and check it.  I will start with renaming
>>> packages and if you send me the ASF header I can fix the files as well.
>>> 
>>> Best,
>>> 
>>> Reza.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> -Original Message-
>>> From: Xun Hu 
>>> Sent: Sunday, February 21, 2021 10:20 PM
>>> To: Reza Adibnia ; Jean-Baptiste Onofré <
>>> jbono...@yupiik.com>
>>> Subject: RE: [VOTE] Retire BlueMarlin project from Incubator
>>> 
>>> Hi, JB,
>>> 
>>> Thanks.
>>> 
>>> @Reza Adibnia, please follow up with JB on all the steps and document it.
>>> 
>>> Regards,
>>> -xun
>>> 
>>> 
>>> -Original Message-
>>> From: Jean-Baptiste Onofre 
>>> Sent: Sunday, February 21, 2021 10:16 PM
>>> To: general@incubator.apache.org
>>> Cc: Reza Adibnia 
>>> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
>>> 
>>> No problem.
>>> 
>>> So, if not done, please subscribe to d...@bluemarlin.apache.org >> d...@bluemarlin.apache.org>.
>>> 
>>> Then, can you please send the existing code repository details on dev
>>> mailing list ?
>>> 
>>> Basically, the first steps is:
>>> - check license
>>> - add ASF headers in all files
>>> - add DISCLAIMER, LICENSE and NOTICE files
>>> - eventually rename packages/artifacts to org.apache.bluemarlin
>>> - prepare a source artifact containing all and named with version-incubator
>>> 
>>> Once this is done (or meantime), we can move forward with website.
>>> 
>>> Let’s move forward on dev mailing list about these actions.
>>> 
>>> Thanks,
>>> Regards
>>> JB
>>> 
>> Le 22 févr. 2021 à 07:12, Xun Hu  a écrit :
> 
> Yes, please help us, we are not familiar with the process. Could you
>>> please work with Reza to finalize the process? We can follow it in the
>>> future.
 
 Thanks,
 -xun
 
 
 
 -Original Message-
 From: Jean-Baptiste Onofre 
 Sent: Sunday, February 21, 2021 10:10 PM
 To: general@incubator.apache.org
 Cc: Reza Adibnia 
 Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
 
 Hi,
 
 I think it’s important to keep the state on dev mailing list (publicly).
 
 The key think while in the incubator is to build/grow up the community.
 
 So, let’s share the detail on the BlueMarlin dev mailing list and move
>>> forward there.
 
 It’s important to give visibility to everyone.
 
 Thanks,
 Regards
 JB
 
> Le 22 févr. 2021 à 05:01, Xun Hu  a écrit :
> 
> Hi, JB,
> 
> Please check with Reza, we would like to work you closely to make the
>>> donation.
> 
> Thanks,
> -xun
> 
> 
> -Original Message-
> From: Dave Fisher mailto:w...@apache.org>>
> Sent: Sunday, February 21, 2021 9:40 AM
> To: general@incubator.apache.org
> 
> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
> 
> Hi JBO,
> 
> Good luck with that. I’ll hold back my vote for two weeks.
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On Feb 21, 2021, at 8:55 AM, Jean-Baptiste Onofre 
>>> wrote:
>> 
>> Hi,
>> 
>> I kindly request a couple of weeks about moving forward with this
>>> vote. I try a new time to ping the BlueMarlin team to move forward with
>>> code donation and bootstrap the project. I have to admit that it’s super
>>> long and I have some difficulty to interact with the team, but I would like
>>> to give a last chance.
>> 
>> Thanks !
>> Regards
>> JB
>> 
>>> Le 

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Matt Sicker]

I tried building on macOS as well, and it got fairly far and ended up
failing at this point:

Scanning dependencies of target sgxlib-teaclave_authentication_service
[ 37%] Building sgxlib-teaclave_authentication_service, enclave info
to 
/teaclave/build/intermediate/teaclave_authentication_service_enclave_info.toml
   Compiling crc v2.0.0 (https://github.com/mesalock-linux/crc-rs-sgx#86696be0)
   Compiling teaclave_proto v0.2.0
(/teaclave/build/cmake_tomls/sgx_trusted_lib/services/proto)
   Compiling integer-encoding v1.0.7
   Compiling snap v0.2.5
   Compiling jsonwebtoken v6.0.1
error: could not compile `crc`.

Caused by:
  process didn't exit successfully:
`/teaclave/cmake/scripts/rustc_wrapper.sh --crate-name crc
--edition=2018 
/teaclave/build/cmake_tomls/sgx_trusted_lib/third_party/crates-sgx/vendor/crc/src/lib.rs
--error-format=json --json=diagnostic-rendered-ansi,artifacts
--crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
metadata=39ca99cb54d77a3c -C extra-filename=-39ca99cb54d77a3c
--out-dir /teaclave/build/target/trusted/debug/deps -L
dependency=/teaclave/build/target/trusted/debug/deps --cap-lints allow
--cfg test_mode` (signal: 9, SIGKILL: kill)
/usr/bin/ld: cannot find -lteaclave_authentication_service_enclave
collect2: error: ld returned 1 exit status
CMakeFiles/sgxlib-teaclave_authentication_service.dir/build.make:57:
recipe for target 'CMakeFiles/sgxlib-teaclave_authentication_service'
failed
make[2]: *** [CMakeFiles/sgxlib-teaclave_authentication_service] Error 1
CMakeFiles/Makefile2:301: recipe for target
'CMakeFiles/sgxlib-teaclave_authentication_service.dir/all' failed
make[1]: *** [CMakeFiles/sgxlib-teaclave_authentication_service.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

Full build log output here:
https://gist.github.com/jvz/b214f28b788f6459b8e511149781e52a

Signatures, notice, license, disclaimer all good.

On Sun, 28 Feb 2021 at 13:37, Mingshen Sun  wrote:
>
> Thanks Furkan,
>
> I just tried to download and compile it in a clean Linux environment,
> and can successfully compile the code.
>
> Are you working on macOS? Because of the case-insensitive file system
> of macOS, Git cannot distinguish the KEYS file and keys directory.
> That may cause the keys directory is not checkout.
>
> I'll fix this in the next release.
>
> Best,
> Mingshen
>
> On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI  wrote:
> >
> > Hi,
> >
> > +1 from me (I have notes below).
> >
> > I checked:
> >
> > - Incubating in name
> > - DISCLAIMER-WIP exists
> > - LICENSE is fine
> > - NOTICE has *incorrect* *year* which should be fixed
> > - No unexpected binary files
> > - Checked PGP signatures
> > - Checked checksums
> >
> > I got that error while compiling the project:
> >
> > Digest:
> > sha256:cb80cb3da4ddb15713ecd7ea8b6f4eab144c402644ece8116e762a19886d7ada
> > Status: Downloaded newer image for
> > teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
> > -- The C compiler identification is GNU 7.5.0
> > -- Check for working C compiler: /usr/bin/cc
> > -- Check for working C compiler: /usr/bin/cc -- works
> > -- Detecting C compiler ABI info
> > -- Detecting C compiler ABI info - done
> > -- Detecting C compile features
> > -- Detecting C compile features - done
> > -- Found Git: /usr/bin/git (found version "2.27.0")
> > -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version
> > "1.1.1")
> > SGX_SDK=/opt/sgxsdk
> > SGX_MODE=HW
> > RUSTUP_TOOLCHAIN=nightly-2020-04-07
> > DCAP=OFF
> > BUILD_TYPE=debug
> > TEACLAVE_SYMLINKS=/tmp/teaclave_symlinks.Dvayr2ejnVKi
> > -- == /teaclave/build/environment GENERATED ==
> > -- Configuring done
> > -- Generating done
> > -- Build files have been written to: /teaclave/build
> > Scanning dependencies of target prep
> > cp: cannot stat '/teaclave/keys/dcap_server_cert.pem': Not a directory
> > CMakeFiles/prep.dir/build.make:57: recipe for target 'CMakeFiles/prep'
> > failed
> > make[2]: *** [CMakeFiles/prep] Error 1
> > CMakeFiles/Makefile2:819: recipe for target 'CMakeFiles/prep.dir/all' failed
> > make[1]: *** [CMakeFiles/prep.dir/all] Error 2
> > Makefile:83: recipe for target 'all' failed
> > make: *** [all] Error 2
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Fri, Feb 26, 2021 at 10:42 PM Yu Ding  wrote:
> >
> > > +1 approve
> > >
> > > On 2021/02/26 18:26:28, Mingshen Sun  wrote:
> > > > Dear community,
> > > >
> > > > This is a call for a vote to release Apache Teaclave (incubating)
> > > > version 0.2.0. This is the second Apache release since Teaclave
> > > > entered the incubator.
> > > >
> > > > The Apache Teaclave (incubating) community has voted and approved the
> > > > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > > > Rundong Zhou, Tongxin Li).
> > > >
> > > > Vote/result thread:
> > > >   -
> > > https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> > > >
> > > > The relea

Re: [VOTE] Retire BlueMarlin project from Incubator

[JB Onofré]

Hi

Just to let you know that the BlueMarlin team showed great progress about the 
donation and overall bootstrap. I will help them with the next steps. 

What do you think about cancel this vote for now ?

Thanks 
Regards 
JB

> Le 23 févr. 2021 à 08:20, Jean-Baptiste Onofré  a écrit :
> 
> Hi Reza,
> 
> it sounds like a plan. I will start to work on the repo (to prepare code
> donation) tomorrow. Let's keep in touch.
> 
> Thanks,
> Regards
> JB
> 
>> On Tue, Feb 23, 2021 at 1:09 AM Reza Adibnia 
>> wrote:
>> 
>> Hi JB,
>> 
>> I guess Xun and I are now part of the d...@bluemarlin.apach.org mailing
>> list.  I will CC d...@bluemarlin.apach.org from now on.
>> 
>> The existing code repository of blue-marlin project is
>> https://github.com/Futurewei-io/blue-marlin
>> 
>> I can help you with the migration. I will create a new branch called
>> apache-migration from master and make the following changes.
>> 
>> - check license (JB will do)
>> - add ASF headers in all files (Reza will do)
>> - add DISCLAIMER, LICENSE and NOTICE files (JB will do)
>> - eventually rename packages/artifacts to org.apache.bluemarlin (Reza will
>> do)
>> - prepare a source artifact containing all and named with
>> version-incubator (I don't know about this one)
>> 
>> After it is done, you can go and check it.  I will start with renaming
>> packages and if you send me the ASF header I can fix the files as well.
>> 
>> Best,
>> 
>> Reza.
>> 
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Xun Hu 
>> Sent: Sunday, February 21, 2021 10:20 PM
>> To: Reza Adibnia ; Jean-Baptiste Onofré <
>> jbono...@yupiik.com>
>> Subject: RE: [VOTE] Retire BlueMarlin project from Incubator
>> 
>> Hi, JB,
>> 
>> Thanks.
>> 
>> @Reza Adibnia, please follow up with JB on all the steps and document it.
>> 
>> Regards,
>> -xun
>> 
>> 
>> -Original Message-
>> From: Jean-Baptiste Onofre 
>> Sent: Sunday, February 21, 2021 10:16 PM
>> To: general@incubator.apache.org
>> Cc: Reza Adibnia 
>> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
>> 
>> No problem.
>> 
>> So, if not done, please subscribe to d...@bluemarlin.apache.org > d...@bluemarlin.apache.org>.
>> 
>> Then, can you please send the existing code repository details on dev
>> mailing list ?
>> 
>> Basically, the first steps is:
>> - check license
>> - add ASF headers in all files
>> - add DISCLAIMER, LICENSE and NOTICE files
>> - eventually rename packages/artifacts to org.apache.bluemarlin
>> - prepare a source artifact containing all and named with version-incubator
>> 
>> Once this is done (or meantime), we can move forward with website.
>> 
>> Let’s move forward on dev mailing list about these actions.
>> 
>> Thanks,
>> Regards
>> JB
>> 
 Le 22 févr. 2021 à 07:12, Xun Hu  a écrit :
>>> 
>>> Yes, please help us, we are not familiar with the process. Could you
>> please work with Reza to finalize the process? We can follow it in the
>> future.
>>> 
>>> Thanks,
>>> -xun
>>> 
>>> 
>>> 
>>> -Original Message-
>>> From: Jean-Baptiste Onofre 
>>> Sent: Sunday, February 21, 2021 10:10 PM
>>> To: general@incubator.apache.org
>>> Cc: Reza Adibnia 
>>> Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
>>> 
>>> Hi,
>>> 
>>> I think it’s important to keep the state on dev mailing list (publicly).
>>> 
>>> The key think while in the incubator is to build/grow up the community.
>>> 
>>> So, let’s share the detail on the BlueMarlin dev mailing list and move
>> forward there.
>>> 
>>> It’s important to give visibility to everyone.
>>> 
>>> Thanks,
>>> Regards
>>> JB
>>> 
 Le 22 févr. 2021 à 05:01, Xun Hu  a écrit :
 
 Hi, JB,
 
 Please check with Reza, we would like to work you closely to make the
>> donation.
 
 Thanks,
 -xun
 
 
 -Original Message-
 From: Dave Fisher mailto:w...@apache.org>>
 Sent: Sunday, February 21, 2021 9:40 AM
 To: general@incubator.apache.org
 
 Subject: Re: [VOTE] Retire BlueMarlin project from Incubator
 
 Hi JBO,
 
 Good luck with that. I’ll hold back my vote for two weeks.
 
 Regards,
 Dave
 
 Sent from my iPhone
 
> On Feb 21, 2021, at 8:55 AM, Jean-Baptiste Onofre 
>> wrote:
> 
> Hi,
> 
> I kindly request a couple of weeks about moving forward with this
>> vote. I try a new time to ping the BlueMarlin team to move forward with
>> code donation and bootstrap the project. I have to admit that it’s super
>> long and I have some difficulty to interact with the team, but I would like
>> to give a last chance.
> 
> Thanks !
> Regards
> JB
> 
>> Le 21 févr. 2021 à 14:32, Sheng Wu  a
>> écrit :
>> 
>> Hi IPMC
>> 
>> This is an official vote for retiring the BlueMarlin from the
>> incubator.
>> We had several discussion about this
>> - general@incubator,
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fl

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Thanks Furkan,

I just tried to download and compile it in a clean Linux environment,
and can successfully compile the code.

Are you working on macOS? Because of the case-insensitive file system
of macOS, Git cannot distinguish the KEYS file and keys directory.
That may cause the keys directory is not checkout.

I'll fix this in the next release.

Best,
Mingshen

On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI  wrote:
>
> Hi,
>
> +1 from me (I have notes below).
>
> I checked:
>
> - Incubating in name
> - DISCLAIMER-WIP exists
> - LICENSE is fine
> - NOTICE has *incorrect* *year* which should be fixed
> - No unexpected binary files
> - Checked PGP signatures
> - Checked checksums
>
> I got that error while compiling the project:
>
> Digest:
> sha256:cb80cb3da4ddb15713ecd7ea8b6f4eab144c402644ece8116e762a19886d7ada
> Status: Downloaded newer image for
> teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
> -- The C compiler identification is GNU 7.5.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Found Git: /usr/bin/git (found version "2.27.0")
> -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version
> "1.1.1")
> SGX_SDK=/opt/sgxsdk
> SGX_MODE=HW
> RUSTUP_TOOLCHAIN=nightly-2020-04-07
> DCAP=OFF
> BUILD_TYPE=debug
> TEACLAVE_SYMLINKS=/tmp/teaclave_symlinks.Dvayr2ejnVKi
> -- == /teaclave/build/environment GENERATED ==
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /teaclave/build
> Scanning dependencies of target prep
> cp: cannot stat '/teaclave/keys/dcap_server_cert.pem': Not a directory
> CMakeFiles/prep.dir/build.make:57: recipe for target 'CMakeFiles/prep'
> failed
> make[2]: *** [CMakeFiles/prep] Error 1
> CMakeFiles/Makefile2:819: recipe for target 'CMakeFiles/prep.dir/all' failed
> make[1]: *** [CMakeFiles/prep.dir/all] Error 2
> Makefile:83: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Kind Regards,
> Furkan KAMACI
>
> On Fri, Feb 26, 2021 at 10:42 PM Yu Ding  wrote:
>
> > +1 approve
> >
> > On 2021/02/26 18:26:28, Mingshen Sun  wrote:
> > > Dear community,
> > >
> > > This is a call for a vote to release Apache Teaclave (incubating)
> > > version 0.2.0. This is the second Apache release since Teaclave
> > > entered the incubator.
> > >
> > > The Apache Teaclave (incubating) community has voted and approved the
> > > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > > Rundong Zhou, Tongxin Li).
> > >
> > > Vote/result thread:
> > >   -
> > https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > >   -
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> > >
> > > The release candidate is signed with a GPG key available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > >
> > > The Git commit for this release is:
> > >   -
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> > >
> > > The release note is available in:
> > >   -
> > https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> > >
> > > Build guide and get started instructions can be found at:
> > >   -
> > https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> > >
> > > The short version of building Teaclave from the source tarball:
> > >
> > > ```
> > > $ wget
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> > > $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> > > apache-teaclave-0.2.0-rc.1-incubating
> > > $ # Instructions to verify the source tar:
> > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > >
> > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> > >bash -c ". /root/.cargo/env && \
> > >  . /opt/sgxsdk/environment && \
> > >  mkdir -p build && cd build && \
> > >  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > >  make"
> > > ```
> > >
> > > The vote will be open for at least 72 hours.
> > >
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove with the reason
> > >
> > >
> > > Best,
> > >
> > > Mingshen Sun
> > > http://mssun.me
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: 

Re: Re: [Proposal] lxdb - proposal for Apache Incubation

[f...@lucene.cn]

Hi  Ming Wen

I am quit sorry, i make a reformat.

Here is my project info.


Dear Apache Incubator Community,

Please accept the following proposal for presentation and discussion:
https://github.com/lucene-cn/lxdb/wiki

LXDB is a high-performance,OLAP,full text search database.it`s base on 
hbase,but replaced hfile with lucene index to support more effective secondary 
indexes,it`s also base on spark sql,so that you can used sql api to visit data 
and do olap calculate. and also the lucene index is store on hdfs (not local 
disk).

In our Production System, LXDB supported 200+ clusters,some of the single 
cluster is 1000+ nodes,insert 200 billion rows  per day ( 2 billion rows 
for total), one of the biggest single table has 200million lucene index on LXDB.

Hadoop`s father Doug Cutting cut nutch into HBase, MapReduce (hive), HDFS, 
Lucene.We have merged these separated projects again,LXDB equals spark 
sql+hbase+lucene+parquet+hdfs,it is a super database.It took me 10 years to 
complete these merging operations.But the purpose is no longer a search engine, 
but a database.


Best regards
  yannian mu


LXDB Proposal
== Abstract ==
LXDB is a high-performance,OLAP,full text search database.

=== it`s base on hbase,but replaced hfile with lucene index to support more 
effective secondary indexes.===
we modify hbase region server ,we  change hfile to lucene,when put data we put  
document to lucene instande of  put data to hfile
lucene index store on region server  (it is not sote in different cluster like 
elstice search+hbase ,it takes to copy of data)

=== it`s base on spark sql for olap===
we Integrated spark and hbase together ,it`s useage like this ,
1.unpackage lxdb.tar.gz
2.config hadoop_config path,
3.run start-all.sh to start cluster.
lxdb can startup spark through hadoop yarn ,and then spark executor process 
Embedded start hbase region server service .

you can operate lxdb database throuth spark sql api(hive) or mysql api.
1.the sql used spark rdd+hbase scaner  to visit hbase .
2.the sql`s condition (filter or group by agg) will predicate to hbase ,
3.hbase used lucene index to filter data in region server.
all of the spark,hbase,lucene is Embedded Integrated together,it is not  a  
seperate cluster ,that is the different with solr/es + hbase+spark Solution.

== Background ==
=== Multiple copies of data ===
Apache HBase+Elastic Search is the most popular Solution on full text search 
,but it`s weak on Online AnalyticalProcessing.
so most of the time the Production System used spark(or hive or impala or 
presto) ,hbase,solr/es at the same time.Multiple copies of data are stored in 
multiple systems,multiple systems has different Api .Data consistency is 
difficult to guarantee.For the above reasons we merger spark,hbase,elastic into 
one project .it`s target is used one copy of data,one cluster,one api to solve 
olap,kv,full text...database scenarios.

=== Merging and splitting of lucene indexes(hstore) acrocess different machine 
on hdfs ===
As we all know solr/es store file in local fileSystem,it`s shard num must be a 
fix num,but if we store index on hdfs,the index can split able like hbase 
hstore,it can split or merge acorss machine nodes ,this is very usefull for 
distribute database ,it depend malloc how much resource on a table,most of time 
the records of a table is different by time by time so the num of shards always 
need adjust,if index store local it can`t split acroces throw different machine 
,but lucene index store on hdfs it`s can do it.
whether the number of pieces can be flexibly adjusted, whether it has the 
ability of elastic scaling, in a distributed database is particularly important

=== solved Insufficient of  secondary indexes ===
some people use hbase secondary index like Phoenix prjoect. but those programme 
base on the hbase rowkey has a lot of redundancy,He can't create too many 
indexes,Data inflation rate is too high,so used lucene index instand of 
secondary is the best chooses.

=== we add an lucene index for spark olap===
Most of OLAP systems has violent scanning problems and Poor timeliness of data 
like hive,spark sql,impala or some of the mpp database.
1.They used violent scans to calculate the data.but another choice is add index 
to the big data.some of the time using index can greatly improve the 
performance of the original brute force scanning. i think  that just like the 
traditional database, indexing technology can greatly improve the performance 
of the speed database.
2.Another problem of thoses database or system, Most of them are an offline 
system or batch system,lxdb `s target is realtime append ,realtime kv update 
just like hbase.

==future==
=== lucene on parquet ===
recenetly i will change lucene  tim,tip(invert index) ,dvd,dvm files to  like 
parquet or orc format.
To solve the performance problem of traversing Lucene index.To solve the 
problem that opening Lucene file needs to load files such as tip into memory, 

Re: Re: [Proposal] lxdb - proposal for Apache Incubation

[Ming Wen]

Hi, fp,
Your email is hard to read.
Please change to a normal mail client first.
Back to your proposal, the key concern is not technology, but IPMC can not
evaluate a project when we can see anything.

Thanks,
Ming Wen, Apache APISIX PMC Chair
Twitter: _WenMing


f...@lucene.cn  于2021年2月28日周日 下午9:02写道：

> Hi Furkan Kamaci
>
>
> Thank you for your proposal, I will start to improve and prepare
>
>
>
>
> 1.Find an experienced mentor to guide you.
>
>
>
>  todo
>
>
>
> 2.Start to translate your documentation to English.
>
>
>
> 3.Open source your project. How can we have a comment on your project if
>
>
>
> we cannot see anything about it?
>
>
>
>
>
>
>
>  give me some time,I discussed with my team, my English is too poor.
>
>
>
>
>
>
>
> 4) Gain contributors to your project. At least you should show your
>
>
>
> intention to have committers/contributors out of your company. Eliminate
>
>
>
> the risk of being non-meritocratic management of the project.
>
>
>
>
>
>
>
> That's what I have to do
>
>
>
>
>
>
>
> 5) Structure your proposal. Explain why people need this project, which
>
>
>
> problems do current projects have and how you managed to handle them. We
>
>
>
> should understand is it a bundle of other projects, a completely new
>
>
>
> project, or a wrapper of other projects which eliminates the shortcomings
>
>
>
> of them.
>
>
>
> 6) Find a suitable name for your project in order to not try to solve
>
>
>
> trademark problems that may lose your time if you enter the incubation.
>
>
>
>
>
>
>
> ok i thike a new name ,for example like hydrogen sql
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> f...@lucene.cn  yannian mu
>
>
>
>
>
>
>
> From: Furkan KAMACI
>
>
>
> Date: 2021-02-28 18:51
>
>
>
> To: general
>
>
>
> Subject: Re: [Proposal] lxdb - proposal for Apache Incubation
>
>
>
> Hi,
>
>
>
>
>
>
>
> Actually you have a detailed documentation which explains which approach
>
>
>
> you have compared to similar systems and performance metrics of following
>
>
>
> them i.e. reducing storage 10 to the 100 times or having low latency
>
>
>
> queries.
>
>
>
>
>
>
>
> My advices are (some of them are same with Sheng's and Liang's ):
>
>
>
>
>
>
>
> 1) Find an experienced mentor to guide you.
>
>
>
>
>
>
>
> 2) Start to translate your documentation to English.
>
>
>
>
>
>
>
> 3) Open source your project. How can we have a comment on your project if
>
>
>
> we cannot see anything about it?
>
>
>
>
>
>
>
> 4) Gain contributors to your project. At least you should show your
>
>
>
> intention to have committers/contributors out of your company. Eliminate
>
>
>
> the risk of being non-meritocratic management of the project.
>
>
>
>
>
>
>
> 5) Structure your proposal. Explain why people need this project, which
>
>
>
> problems do current projects have and how you managed to handle them. We
>
>
>
> should understand is it a bundle of other projects, a completely new
>
>
>
> project, or a wrapper of other projects which eliminates the shortcomings
>
>
>
> of them.
>
>
>
>
>
>
>
> 6) Find a suitable name for your project in order to not try to solve
>
>
>
> trademark problems that may lose your time if you enter the incubation.
>
>
>
>
>
>
>
> Kind Regards,
>
>
>
> Furkan KAMACI
>
>
>
>
>
>
>
>
>
>
>
> On Sun, Feb 28, 2021 at 1:02 PM Liang Chen 
> wrote:
>
>
>
>
>
>
>
> > Hi
>
>
>
> >
>
>
>
> > It would be better if you could find an experienced IPMC member to help
> you
>
>
>
> > for preparing the proposal.
>
>
>
> > Based on Sheng Wu input, i have one more comment : can you please explain
>
>
>
> > what are the different with other similar data analysis DB?  you can
>
>
>
> > consider explaining from use cases perspective.
>
>
>
> >
>
>
>
> > Regards
>
>
>
> > Liang
>
>
>
> >
>
>
>
> >
>
>
>
> > fp wrote
>
>
>
> > > Dear Apache Incubator Community,
>
>
>
> > >
>
>
>
> > >
>
>
>
> > > Please accept the following proposal for presentation and discussion:
>
>
>
> > > https://github.com/lucene-cn/lxdb/wiki
>
>
>
> > >
>
>
>
> > >
>
>
>
> > > LXDB is a high-performance,OLAP,full text search database.it`s base on
>
>
>
> > > hbase,but replaced hfile with lucene index to support more effective
>
>
>
> > > secondary indexes,it`s also base on spark sql,so that you can used sql
>
>
>
> > api
>
>
>
> > > to visit data and do olap calculate. and also the lucene index is store
>
>
>
> > on
>
>
>
> > > hdfs (not local disk).
>
>
>
> > >
>
>
>
> > >
>
>
>
> > > In our Production System, LXDB supported 200+ clusters,some of the
> single
>
>
>
> > > cluster is 1000+ nodes,insert 200 billion rows  per day ( 2
>
>
>
> > > billion rows for total), one of the biggest single table has 200million
>
>
>
> > > lucene index on LXDB.
>
>
>
> > >
>
>
>
> > >
>
>
>
> > > Hadoop`s father Doug Cutting cut nutch into HBase, MapReduce (hive),
>
>
>
> > HDFS,
>
>
>
> > > Lucene.We have merged these separated projects again,LXDB equals
>
>
>
> > > spark sql+hbase+lucene+parquet+hdfs,it is a super database.It took me
> 10
>
>
>
> > > years to complete the

Re: Re: [Proposal] lxdb - proposal for Apache Incubation

[f...@lucene.cn]

Hi Furkan Kamaci


Thank you for your proposal, I will start to improve and prepare




1.Find an experienced mentor to guide you.



     todo



2.Start to translate your documentation to English.



3.Open source your project. How can we have a comment on your project if



we cannot see anything about it?







     give me some time,I discussed with my team, my English is too poor.







4) Gain contributors to your project. At least you should show your



intention to have committers/contributors out of your company. Eliminate



the risk of being non-meritocratic management of the project.







That's what I have to do







5) Structure your proposal. Explain why people need this project, which



problems do current projects have and how you managed to handle them. We



should understand is it a bundle of other projects, a completely new



project, or a wrapper of other projects which eliminates the shortcomings



of them.



6) Find a suitable name for your project in order to not try to solve



trademark problems that may lose your time if you enter the incubation.







ok i thike a new name ,for example like hydrogen sql 















f...@lucene.cn  yannian mu



 



From: Furkan KAMACI



Date: 2021-02-28 18:51



To: general



Subject: Re: [Proposal] lxdb - proposal for Apache Incubation



Hi,



 



Actually you have a detailed documentation which explains which approach



you have compared to similar systems and performance metrics of following



them i.e. reducing storage 10 to the 100 times or having low latency



queries.



 



My advices are (some of them are same with Sheng's and Liang's ):



 



1) Find an experienced mentor to guide you.



 



2) Start to translate your documentation to English.



 



3) Open source your project. How can we have a comment on your project if



we cannot see anything about it?



 



4) Gain contributors to your project. At least you should show your



intention to have committers/contributors out of your company. Eliminate



the risk of being non-meritocratic management of the project.



 



5) Structure your proposal. Explain why people need this project, which



problems do current projects have and how you managed to handle them. We



should understand is it a bundle of other projects, a completely new



project, or a wrapper of other projects which eliminates the shortcomings



of them.



 



6) Find a suitable name for your project in order to not try to solve



trademark problems that may lose your time if you enter the incubation.



 



Kind Regards,



Furkan KAMACI



 



 



On Sun, Feb 28, 2021 at 1:02 PM Liang Chen  wrote:



 



> Hi



>



> It would be better if you could find an experienced IPMC member to help you



> for preparing the proposal.



> Based on Sheng Wu input, i have one more comment : can you please explain



> what are the different with other similar data analysis DB?  you can



> consider explaining from use cases perspective.



>



> Regards



> Liang



>



>



> fp wrote



> > Dear Apache Incubator Community,



> >



> >



> > Please accept the following proposal for presentation and discussion:



> > https://github.com/lucene-cn/lxdb/wiki



> >



> >



> > LXDB is a high-performance,OLAP,full text search database.it`s base on



> > hbase,but replaced hfile with lucene index to support more effective



> > secondary indexes,it`s also base on spark sql,so that you can used sql



> api



> > to visit data and do olap calculate. and also the lucene index is store



> on



> > hdfs (not local disk).



> >



> >



> > In our Production System, LXDB supported 200+ clusters,some of the single



> > cluster is 1000+ nodes,insert 200 billion rows  per day ( 2



> > billion rows for total), one of the biggest single table has 200million



> > lucene index on LXDB.



> >



> >



> > Hadoop`s father Doug Cutting cut nutch into HBase, MapReduce (hive),



> HDFS,



> > Lucene.We have merged these separated projects again,LXDB equals



> > spark sql+hbase+lucene+parquet+hdfs,it is a super database.It took me 10



> > years to complete these merging operations.But the purpose is no longer a



> > search engine, but a database.



> >



> >



> >



> >



> >



> > Best regards



> >   yannian mu



> >



> >



> >



> >



> > LXDB Proposal



> > == Abstract ==



> > LXDB is a high-performance,OLAP,full text search database.



> >



> >



> > === it`s base on hbase,but replaced hfile with lucene index to support



> > more effective secondary indexes.=== 



> > we modify hbase region server ,we  change hfile to lucene,when put



> > data we put  document to lucene instande of  put data to hfile



> > lucene index store on region server  (it is not sote in



> > different cluster like elstice search+hbase ,it takes to copy of data)



> >



> >



> > === it`s base on spark sql for olap=== 



> > we Integrated spark and hba

Re: Re: [Proposal] lxdb - proposal for Apache Incubation

[f...@lucene.cn]

Hi Liang Chen

Thank you very much for your busy time to answer my question
My reply is as follows.

==

1:It would be better if you could find an experienced IPMC member to help you

for preparing the proposal.

>I am trying to find those PMC who are willing to help me,After all, it was a 
>very heavy job


2:Based on Sheng Wu input, i have one more comment : can you please explain  
what are the different with other similar data analysis DB?  you can  consider 
explaining from use cases perspective.

Different from analytic db


>I'm not particularly familiar with analyticdb, so I just looked up some 
>information through the search engine. If there is any misunderstanding, 
>please criticize and correct me
>Most of the time they are really similar,Analyticdb is a very excellent 
>database, but its technical principles can hardly be found on the Internet. 
>From my personal point of view, they may have the following differences
#1) Analyticdb is a cloud native data warehouse in the full sense,This is also 
the feature they added to the new edition, which supports the separation of 
storage and computing, and the time-sharing flexibility of resources on demand. 
The same piece of data can start different computing resources at different 
computing nodes according to different computing 

However, lxdb is not a real cloud native database. Although we store the Lucene 
index on HDFS, we can only separate the storage from computing. At present, 
when the Lucene itself is opened for the first time, the index information such 
as tip must be preloaded into memory, which leads to the persistent opening of 
Lucene in the resident process, Therefore, lxdb has not been able to separate 
computing from computing, that is, it has not been able to distribute computing 
resources to different processes according to different queries. This has 
always been a pity of lxdb, so I have been trying these years

At present, cloud native database has great market potential, and we are 
willing to try it,And I know that it's not difficult to change Lucene like 
this, or it's less difficult than integrating spark, HBase and Lucene together. 

(大多时候两者非常相似,但目前Analyticdb 
是一个完全意义上的云原生数据仓库,我注意到他们最近加入的这个特性,支持存储于计算分离,资源按需分时弹性,同一份数据可以根据不同的计算在不同的计算节点启动不同的计算资源)
(但是lxdb还不是一个真正意义上的云原生数据库,虽然我们将lucene索引存放在了hdfs之上,但这只能做到存储与计算分离,目前由于lucene本身第一次打开的时候必须将tip等索引信息预加载到内存里,导致了lucene必须在常驻进程中持久化的打开,因此lxdb还做不到计算与计算分离,也就是还不能根据不同的查询,将计算资源分散到不同的进程中去,这一直是lxdb的一个遗憾,所以这些年我一直在不断的修改lucene索引,准备将其倒排表,正排都统一成parquet这类云原生的格式来解决这个问题,这样既能提高倒排查询的性能,又能解决所以需要预先加载的问题)
(目前来看云原生数据库有非常大的市场潜力,我们也愿意在这方面进行尝试,而且我知道,将lucene这样改动起来并不难,或者说难度小于将spark,hbase,lucene集成在一起的难度)

#2)Analyticdb can't be built by itself, it can only run on the cloud platform 
provided by it,Must be purchased with the underlying cloud environment, which 
sometimes gives users more restrictions. Lxdb is based on Hadoop platform. As 
long as users have Hadoop environment, lxdb can directly start services through 
yard, which is suitable for private deployment and deployment on the cloud, and 
it doesn't limit any manufacturers. It is relatively open

#3)I feel that it is more like a batch engine,It is more like a scene of 
centralized import and batch query,At least his cloud native model should be 
like this,Or I didn't find the user manual for real-time import
, while lxdb is a real-time engine with low data latency,Relatively speaking, 
it is easier for batch engine to realize cloud native, while it is more 
difficult for real-time millisecond delay engine to realize the separation of 
storage and computing. It needs a snapshot mechanism to record the data change 
at a certain time, so as to realize the separation of computing and computing 
between different nodes


#4 According to the official documents, see specifications and restrictions, 
the best configuration is C32. The number of nodes supported by C32 is less 
than 128, and the storage capacity is 1PB. In the production environment, lxdb 
has 904 nodes, 50pb disk capacity, and 70% storage utilization,Of course, it 
can be inaccurate and unfair to adb.

(AnalyticDB不能自己搭建,只能运行在其提供的云平台之上,必须伴随底层云环境一同购买,这有时会给用户比较多的限制.而lxdb则是基于hadoop平台的,只要用户有hadoop环境,lxdb则可以直接通过yarn启动服务,即适合私有化部署也适合在云上的部署,也不限制任何的厂商,相对来说比较开放.)
(我感觉其更像是一个批处理引擎,更像是一次集中导入,之后批量查询的场景,起码他的云原生模式应该是这样的,或者我也没找到实时导入的使用手册,而lxdb则是一个实时的引擎,数据延迟很低,相对来说批处理引擎实现云原生更容易,而实时毫秒级延迟的引擎实现存储于计算分离比较难,需要有快照机制,记录某一时刻的数据变化,才能实现计算与计算的在不同节点之间的分离)
从官方提供的文档逆向反推,see 
详细规格与限制说明来看,最好的配置C32支持的节点数在128一下,存储容量在1PB,而lxdb在生产环境目前真实的节点数904台,磁盘容量50PB,存储使用率70%,当然这有可能对adb来说不准确,也不公平,仅供参考


Different from carbondata and clickhouse
When carbondata appeared in 2015, it was a product that shocked me very much. 
Adding a layer of index to big data is what I have been doing all these years. 
I didn't expect that there would be a team in this world with the same idea as 
me,They are all based on Hadoop, and even the startup is based on spark on yarn

Everyone is based on spark, and its core is the underlying data structure o

Re: [Proposal] lxdb - proposal for Apache Incubation

[Furkan KAMACI]

Hi,

Actually you have a detailed documentation which explains which approach
you have compared to similar systems and performance metrics of following
them i.e. reducing storage 10 to the 100 times or having low latency
queries.

My advices are (some of them are same with Sheng's and Liang's ):

1) Find an experienced mentor to guide you.

2) Start to translate your documentation to English.

3) Open source your project. How can we have a comment on your project if
we cannot see anything about it?

4) Gain contributors to your project. At least you should show your
intention to have committers/contributors out of your company. Eliminate
the risk of being non-meritocratic management of the project.

5) Structure your proposal. Explain why people need this project, which
problems do current projects have and how you managed to handle them. We
should understand is it a bundle of other projects, a completely new
project, or a wrapper of other projects which eliminates the shortcomings
of them.

6) Find a suitable name for your project in order to not try to solve
trademark problems that may lose your time if you enter the incubation.

Kind Regards,
Furkan KAMACI


On Sun, Feb 28, 2021 at 1:02 PM Liang Chen  wrote:

> Hi
>
> It would be better if you could find an experienced IPMC member to help you
> for preparing the proposal.
> Based on Sheng Wu input, i have one more comment : can you please explain
> what are the different with other similar data analysis DB?  you can
> consider explaining from use cases perspective.
>
> Regards
> Liang
>
>
> fp wrote
> > Dear Apache Incubator Community,
> >
> >
> > Please accept the following proposal for presentation and discussion:
> > https://github.com/lucene-cn/lxdb/wiki
> >
> >
> > LXDB is a high-performance,OLAP,full text search database.it`s base on
> > hbase,but replaced hfile with lucene index to support more effective
> > secondary indexes,it`s also base on spark sql,so that you can used sql
> api
> > to visit data and do olap calculate. and also the lucene index is store
> on
> > hdfs (not local disk).
> >
> >
> > In our Production System, LXDB supported 200+ clusters,some of the single
> > cluster is 1000+ nodes,insert 200 billion rows  per day ( 2
> > billion rows for total), one of the biggest single table has 200million
> > lucene index on LXDB.
> >
> >
> > Hadoop`s father Doug Cutting cut nutch into HBase, MapReduce (hive),
> HDFS,
> > Lucene.We have merged these separated projects again,LXDB equals
> > spark sql+hbase+lucene+parquet+hdfs,it is a super database.It took me 10
> > years to complete these merging operations.But the purpose is no longer a
> > search engine, but a database.
> >
> >
> >
> >
> >
> > Best regards
> >   yannian mu
> >
> >
> >
> >
> > LXDB Proposal
> > == Abstract ==
> > LXDB is a high-performance,OLAP,full text search database.
> >
> >
> > === it`s base on hbase,but replaced hfile with lucene index to support
> > more effective secondary indexes.=== 
> > we modify hbase region server ,we  change hfile to lucene,when put
> > data we put  document to lucene instande of  put data to hfile
> > lucene index store on region server  (it is not sote in
> > different cluster like elstice search+hbase ,it takes to copy of data)
> >
> >
> > === it`s base on spark sql for olap=== 
> > we Integrated spark and hbase together ,it`s useage like this ,
> > 1.unpackage lxdb.tar.gz 
> > 2.config hadoop_config path,
> > 3.run start-all.sh to start cluster. 
> > lxdb can startup spark through hadoop yarn ,and then spark executor
> > process Embedded start hbase region server service . 
> >
> >
> > you can operate lxdb database throuth spark sql api(hive) or mysql api.
> > 1.the sql used spark rdd+hbase scaner  to visit hbase .
> > 2.the sql`s condition (filter or group by agg) will predicate to hbase ,
> > 3.hbase used lucene index to filter data in region server.
> > all of the spark,hbase,lucene is Embedded Integrated together,it is
> > not  a  seperate cluster ,that is the different with solr/es +
> > hbase+spark Solution.
> >
> >
> > == Background ==
> > === Multiple copies of data ===
> > Apache HBase+Elastic Search is the most popular Solution on full text
> > search ,but it`s weak on Online AnalyticalProcessing.
> > so most of the time the Production System used spark(or hive or impala or
> > presto) ,hbase,solr/es at the same time.Multiple copies of data are
> stored
> > in multiple systems,multiple systems has different Api .Data consistency
> > is difficult to guarantee.For the above reasons we merger
> > spark,hbase,elastic into one project .it`s target is used one copy of
> > data,one cluster,one api to solve olap,kv,full text...database scenarios.
> >
> >
> > === Merging and splitting of lucene indexes(hstore) acrocess different
> > machine on hdfs ===
> > As we all know solr/es store file in local fileSystem,it`s shard num must
> > be a fix num,but if we store index on hdfs,the index can split able like
> > hbase hstore,it can split

Re: [Proposal] lxdb - proposal for Apache Incubation

[Liang Chen]

Hi

It would be better if you could find an experienced IPMC member to help you
for preparing the proposal.
Based on Sheng Wu input, i have one more comment : can you please explain
what are the different with other similar data analysis DB?  you can
consider explaining from use cases perspective.

Regards
Liang


fp wrote
> Dear Apache Incubator Community,
> 
> 
> Please accept the following proposal for presentation and discussion:
> https://github.com/lucene-cn/lxdb/wiki
> 
> 
> LXDB is a high-performance,OLAP,full text search database.it`s base on
> hbase,but replaced hfile with lucene index to support more effective
> secondary indexes,it`s also base on spark sql,so that you can used sql api
> to visit data and do olap calculate. and also the lucene index is store on
> hdfs (not local disk).
> 
> 
> In our Production System, LXDB supported 200+ clusters,some of the single
> cluster is 1000+ nodes,insert 200 billion rows  per day ( 2
> billion rows for total), one of the biggest single table has 200million
> lucene index on LXDB.
> 
> 
> Hadoop`s father Doug Cutting cut nutch into HBase, MapReduce (hive), HDFS,
> Lucene.We have merged these separated projects again,LXDB equals
> spark sql+hbase+lucene+parquet+hdfs,it is a super database.It took me 10
> years to complete these merging operations.But the purpose is no longer a
> search engine, but a database.
> 
> 
> 
> 
> 
> Best regards
>   yannian mu
> 
> 
> 
> 
> LXDB Proposal
> == Abstract ==
> LXDB is a high-performance,OLAP,full text search database.
> 
> 
> === it`s base on hbase,but replaced hfile with lucene index to support
> more effective secondary indexes.=== 
> we modify hbase region server ,we  change hfile to lucene,when put
> data we put  document to lucene instande of  put data to hfile
> lucene index store on region server  (it is not sote in
> different cluster like elstice search+hbase ,it takes to copy of data)
> 
> 
> === it`s base on spark sql for olap=== 
> we Integrated spark and hbase together ,it`s useage like this ,
> 1.unpackage lxdb.tar.gz 
> 2.config hadoop_config path,
> 3.run start-all.sh to start cluster. 
> lxdb can startup spark through hadoop yarn ,and then spark executor
> process Embedded start hbase region server service . 
> 
> 
> you can operate lxdb database throuth spark sql api(hive) or mysql api.
> 1.the sql used spark rdd+hbase scaner  to visit hbase .
> 2.the sql`s condition (filter or group by agg) will predicate to hbase ,
> 3.hbase used lucene index to filter data in region server.
> all of the spark,hbase,lucene is Embedded Integrated together,it is
> not  a  seperate cluster ,that is the different with solr/es +
> hbase+spark Solution.
> 
> 
> == Background ==
> === Multiple copies of data ===
> Apache HBase+Elastic Search is the most popular Solution on full text
> search ,but it`s weak on Online AnalyticalProcessing.
> so most of the time the Production System used spark(or hive or impala or
> presto) ,hbase,solr/es at the same time.Multiple copies of data are stored
> in multiple systems,multiple systems has different Api .Data consistency
> is difficult to guarantee.For the above reasons we merger
> spark,hbase,elastic into one project .it`s target is used one copy of
> data,one cluster,one api to solve olap,kv,full text...database scenarios.
> 
> 
> === Merging and splitting of lucene indexes(hstore) acrocess different
> machine on hdfs ===
> As we all know solr/es store file in local fileSystem,it`s shard num must
> be a fix num,but if we store index on hdfs,the index can split able like
> hbase hstore,it can split or merge acorss machine nodes ,this is very
> usefull for distribute database ,it depend malloc how much resource on a
> table,most of time the records of a table is different by time by time so
> the num of shards always need adjust,if index store local it can`t split
> acroces throw different machine ,but lucene index store on hdfs it`s can
> do it.
> whether the number of pieces can be flexibly adjusted, whether it has the
> ability of elastic scaling, in a distributed database is particularly
> important
> 
> 
> 
> === solved Insufficient of  secondary indexes ===
> some people use hbase secondary index like Phoenix prjoect. but those
> programme base on the hbase rowkey has a lot of redundancy,He can't create
> too many indexes,Data inflation rate is too high,so used lucene index
> instand of secondary is the best chooses. 
> 
> 
> === we add an lucene index for spark olap=== 
> Most of OLAP systems has violent scanning problems and Poor timeliness of
> data like hive,spark sql,impala or some of the mpp database.
> 1.They used violent scans to calculate the data.but another choice is add
> index to the big data.some of the time using index can greatly improve the
> performance of the original brute force scanning. i think  that just
> like the traditional database, indexing technology can greatly improve the
> performance of the speed database.
> 2.Another problem of thoses