LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  April 2014

QSERV-L April 2014

Subject:

Re: qserv work in FY2015

From:

Jacek Becla <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Fri, 18 Apr 2014 12:24:38 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (78 lines)

Andy

I consider installing/deployment/starting/stopping services
part of administration (which is on top already)

Partitioning is part of data loading.

And yes, both will rely on CSS backend, that is why
I explicitly mentioned it in the "main focus" bullets.


The list on the web is what we will be expected to deliver
for R5.1 (8/31/2015), but we need to think about bigger
picture, some things are not explicitly mentioned, and
some tasks in more distance future need a lot of thinking.
For example, obviously the system need to be robust
(the closer to commissioning the more robust, but we
can't ignore robustness even now). I also worry a lot
about managing replicas, and rebalancing after failure.

So, we will likely add to that list, even though some
things are not explicitly mentioned, or are not needed
by 8/31/2015, just so we make our life easier after
8/31/2015....

thanks,
Jacek



On 04/18/2014 12:08 PM, Salnikov, Andrei A. wrote:
> Hi Jacek,
>
> should we start doing something (or at least thinking) on
> deployment? Things like installing, starting/stopping,
> partitioning whole shebang across the cluster need to be
> figured out at some point. Or is it covered by CSS
> backend?
>
> Cheers,
> Andy
>
>
> Jacek Becla wrote on 2014-04-18:
>> FYI, I created a page for capturing FY2015 work:
>>
>> https://dev.lsstcorp.org/trac/wiki/db/Qserv/FY2015
>>
>> I believe it is going to be discussed at the meeting
>> in Seattle next week.
>>
>> The way I see it: our main focus will be
>>    - administration (create/drop db/table, abort query)
>>    - data loading
>>    - CSS backend for administration and data loading
>>    - shared scans
>>    - better syntax support
>> If anyone has any quick comments you want to add,
>> please go ahead, via trac or email.
>>
>> thanks,
>> Jacek
>>
>> ########################################################################
>> Use REPLY-ALL to reply to list
>>
>> To unsubscribe from the QSERV-L list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
>
>
>

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use