However, regarding the names, we have the DB is named as cms_dbs3_prodcaf* that is following the same naming schema we are using for all the DBS' DBs. I did not put 01 because this is the only one caf we have and we will have.
-----Original Message-----
From: Stefano Belforte [mailto:stefano.belforte@cern.ch]
Sent: Thursday, February 20, 2014 12:52 AM
To: Eric W Vaandering; Yuyi Guo
Subject: Re: caf_analysis_01
I think Yuyi meant:
with next scheduled cmsweb release content of DBS2/caf_analysis_01
will be availabl in DBS3 as an additional instance with name ... caf01 ?
[I alredy have a name here in Crab2 code, if OK with you I will look it up
and please use same, so I do not have to change release for this] 2. We will
not allow adding to it 3. Datasets created from parents in caf01 will be written to
phys03 like everything else from users
At least that is my understanding and what I think we want and costs little to
nothing.
@yuyi there is no use case for adding other "caf" data anymore.
Stefano
On 02/20/2014 01:13 AM, Eric W Vaandering wrote:
I don't see a problem with adding CAF to phys01/phys02, or phys03. For
the former two, we'd have to check that the dataset names are
orthogonal. For phys03 I think there is little risk of that and one could do a
DBS3->DBS3 migration dataset by dataset. I assume that's what you are
proposing?
On Feb 19, 2014, at 5:08 PM, Yuyi Guo <yuyi@fnal.gov mailto:yuyi@fnal.gov>
wrote:
Hi, Eric:
Migration for caf_analysis_01 is done. In order to be available from
DBS, we need to have another CMSWEB deployment. Is it OK we wait for the
February release to add it in?
I assume that this will be a read only DBS3 instance as the phys01/02.
I have been thinking about caf instance. Is it OK that new caf data
for DBS3 will go directly to
phys03 instead of creating a new caf03?
Thanks,
Yuyi
Stefano Belforte - I.N.F.N. tel : +39 040 375-6261 (fax: 375-6258)
Area di Ricerca - Padriciano 99 tel mobile: +39 328 010 7327
34012 TRIESTE TS - Italy AIM: stefanobelforte
Yes, Stefano. You understood me right.
However, regarding the names, we have the DB is named as cms_dbs3_prodcaf* that is following the same naming schema we are using for all the DBS' DBs. I did not put 01 because this is the only one caf we have and we will have.
So the instance name will be https://cmsweb.cern.ch/dbs/prod/caf/*. Caf will only on cmsweb. So no int/caf or dev/caf.
Ciao, Yuyi