Have we checked the server logs to see if there are any users of these?

On Feb 25, 2014, at 3:07 PM, Nomi Harris <nlharris@lbl.gov> wrote:

Ok, thanks for checking. Sounds like ERDB is still needed. So the revised list of services that can go is:
feature_selection (fizzy)
file_type_service
genotype_phenotype
experiment
prom_service
communities_qc
regulation (regprecise)

On Feb 25, 2014, at 12:54 PM, Shane Canon <scanon@lbl.gov> wrote:


So ERDB may still be needed by translation and trees.

--Shane

root@t1:/kbase/deployments/20140214-prod/dev_container/modules# grep -i erdb */DEP*
experiment/DEPENDENCIES:erdb_service
prom_service/DEPENDENCIES:erdb_service
translation/DEPENDENCIES:erdb_service
trees/DEPENDENCIES:erdb_service

On Feb 25, 2014, at 12:09 PM, "Brettin, Thomas S." <brettin@anl.gov> wrote:

I think the list is accurate. The only exception might be ERDB service. A recursive grep might be needed for that one.

Sent from my Verizon Wireless 4G LTE DROID


Nomi Harris <nlharris@lbl.gov> wrote:

Sure. We can follow up on it during tomorrow's devel call if needed.


On Tue, Feb 25, 2014 at 11:57 AM, Shane Canon <scanon@lbl.gov> wrote:

This is very helpful.  Should we notify the devel list as well?

--Shane


On Feb 25, 2014, at 11:38 AM, Nomi Harris <nlharris@lbl.gov> wrote:

> I believe the following services are not currently supported and can be shut down (if they haven’t been already):
>
> feature_selection (fizzy)
> file_type_services
> genotype_phenotype
> experiment
> prom_service
> communities_qc
> regulation (regprecise)
> erdb_service
>
> Ccing the release team in case they have any adjustments to that list.
>
>       Nomi
>
> On Feb 24, 2014, at 5:54 PM, Shane Canon <scanon@lbl.gov> wrote:
>
>>
>> So we can retire this service?  Are there other services we can shutdown?
>>
>> Shane
>>
>> Sent from my iPhone
>>
>>> On Feb 24, 2014, at 11:56 AM, Nomi Harris <nlharris@lbl.gov> wrote:
>>>
>>> I forgot to forward this to you. Ranjan says to leave the genotype/phenotype service out of this release.
>>>  Nomi
>>>
>>> Begin forwarded message:
>>>
>>>> From: "Ranjan, Priya" <pranjan@utk.edu>
>>>> Subject: Re: Genotype/Phenotype service repo?
>>>> Date: February 18, 2014 at 2:59:58 PM PST
>>>> To: Nomi Harris <nlharris@gmail.com>
>>>>
>>>> Yes. Thanks.
>>>> Ranjan
>>>>
>>>>
>>>>> On Feb 18, 2014, at 5:40 PM, "Nomi Harris" <nlharris@gmail.com> wrote:
>>>>>
>>>>> Ok—so the release of IRIS we’re doing this week should not include Genotype/Phenotype commands, and I should remove it from the Services web page?
>>>>> Nomi
>>>>>
>>>>>> On Feb 18, 2014, at 12:03 PM, Ranjan, Priya <pranjan@utk.edu> wrote:
>>>>>>
>>>>>> Hi Nomi,
>>>>>> Both these services are obsolete and their functionality are being incorporated into gwas service.
>>>>>> I will request them to be deleted in few weeks.
>>>>>> Thanks
>>>>>> Ranjan
>>>>>>
>>>>>>
>>>>>> ________________________________________
>>>>>> From: Nomi Harris [nlharris@gmail.com]
>>>>>> Sent: Tuesday, February 18, 2014 3:00 PM
>>>>>> To: pranjan77@gmail.com; Ranjan, Priya
>>>>>> Cc: release-team@kbase.us
>>>>>> Subject: Genotype/Phenotype service repo?
>>>>>>
>>>>>> Hi Ranjan,
>>>>>> What is the correct repo for the Genotype/Phenotype service?
>>>>>> There’s a repo called genotype_phenotype, which hasn’t been updated since Sept.
>>>>>> There’s one called genotype_phenotype_api, which I think is the current repo.
>>>>>> The Master tab of the Services repo (https://docs.google.com/spreadsheet/ccc?key=0AriSbOyynCz1dDdJRHJBcGszaldlUE5KaG5yNHBRcWc&usp=sharing#gid=2) claims that the repo is called geno_pheno_service, which I guess is just wrong.
>>>>>> If genotype_phenotype_api is the live repo, then I would suggest deleting genotype_phenotype to avoid confusion.
>>>>>> Thanks,
>>>>>>  Nomi
>




_______________________________________________
Release-team mailing list
Release-team@lists.kbase.us
https://lists.kbase.us/mailman/listinfo/release-team