[Go-essp-tech] About Gateway Installation...
Estanislao Gonzalez
estanislao.gonzalez at zmaw.de
Fri Aug 6 02:04:42 MDT 2010
Hi Eric & Gavin,
I totally agree with this idea and since Neil is still waiting for some
certs I can only send after I've installed the Gateway here (the test
machine is almost done) I suggest we move forward.
I have altered both the gway and globus install scripts so I can use
them for the second machine. There are a lot of small things that are
just difficult to pinpoint and thus take time. The installer has become
a massive thing (2000 lines for the gway and 1400 lines for the globus),
so it's normal there are a couple of corners that need to be rounded. In
any case I'll provide you both with the modified versions once I can
test them and assure they work as intended.
What it's worthed mentioning now, is that every single node installed
with the installer is running MyProxy 4.2, as the newer 4.8 is not being
installed. Moving to the new version at the node caused a little
trouble, but I cannot tell if this will be the case for anyone. Check
the version by running $GLOBUS_LOCATION/bin/myproxy-info -V
Regarding your list Eric (and the numbering you've used) I'd like to
comment a little about the current stand of the situation:
1) Mailing list
This is great. I wonder why neither Gavin nor I (probably quite a lot of
others too) had no info about it. I think this information should be
shared. (should we send a monthly mailinglist list within GO-ESSP? Does
it make any sense?)
2) Jira
The idea is great, but e.g. I saw that a bug I wanted to commit was
already committed by someone else, and it even appears to be solved by
now, which would be great. The thing is, I still has no access to the
corrected code (just the binaries) as the Gateway ESG-CET 1.1.0 version
that I can download still has the Liquibase lowercase problem which
inhibit me from installing it here. This forces me to re-solve the
problem manually and lowers the usage of Jira (at least for the
"consumer" like me). Not to forget mentioning there are almost 500
major+ issues open.
3) Communication via email -mailing lists
In my opinion this is working great. I'm just wondering if there are
more mailingslist I should be subscribed to...
4) Documentation
This should be the cornerstone of everything. Before an Installer is
provided the complete documentation should be accessible. IMHO the
installer should speed the installation, not hide it. I'm still finding
info bits spread all over the net...
5) Access to releases and snapshots
This would solve the problem of what to do if a release has a blocking
bug like the Liquibase one.
6) Maintain the installer and tools
I totally agree on that. The responsibility of the installer should be
on the hands of those developing the application it's being installed.
If not the'll grow apart.
We all want to help in the development of the Gateway. I'm more than
happy to be able to contribute my findings. I just think we need a
better infrastructure to support this, and Eric summary just seems the
right path to take.
I wish you all well,
Estani
Gavin M. Bell wrote:
> Eric,
>
> I am glad that you agree with my idea that you folks at NCAR should
> take over the burden of installation over since you have yet to open
> up the gateway source code to the community to be able to help with
> installation issues. The globus script is a shared script used by
> both the data node install and the gateway install scripts. We can
> choose to fork that off or work collaboratively on that since it is
> part of the process and overall system for which we have mutual vested
> interest in. Contact me so we can discuss that further.
>
> As the create of these scripts, I'd be happy to field general
> questions you may have.
>
> The script is licensed as open source, so I would expect that status
> to be respected, (header maintained, etc) though NCAR will be the
> custodian.
>
> Thanks Eric and everyone.
>
> On 8/5/10 11:41 AM, Eric Nienhouse wrote:
>> Hi Gavin, All,
>>
>> Thanks for raising this question.
>>
>> I believe Gateway support for installation, update and maintenance is
>> best suited to the NCAR team. Historically this task has been shared by
>> PCMDI, NCAR and more recently JPL/NOAA. This arrangement has led to
>> some confusion amongst Gateway administrators regarding points of
>> contact, where documentation resides, etc. It has also made deployment
>> coordination difficult as certain tools, such as the gateway
>> installation/update scripts, are not tightly coordinated with gateway
>> release versions.
>>
>> In order to simplify the gateway installations, improve quality and
>> receive valuable feedback from this process I propose the NCAR team take
>> on the majority of "front line" Gateway deployment support. In general
>> this would include:
>>
>> 1) Maintain and respond to questions and issues via a gateway specific
>> email list: esg-gateway-dev at earthsystemgrid.org
>> 2) Maintain and respond to an issue tracking system and encourage the
>> gateway community to log issues. (Jira)
>> 3) Communicate important software releases, time-lines and milestones
>> via community email lists.
>> 4) Document gateway installation and update steps, identify best
>> practices, support FAQs, etc.
>> 5) Provide access to quality controlled release versions and nightly
>> development snapshots.
>>
>> I also believe it is in the best interest of all that the Gateway team
>> also take on maintaining the gateway installation script. Gavin has
>> been the developer and maintainer of this useful tool up to this point
>> which has been great. However, I feel this, too, is best supported the
>> gateway team due to the dependencies upon gateway software versions and
>> deployment configuration. So, I also propose the Gateway team:
>>
>> 6) Develop and maintain the gateway installation tools and scripts.
>>
>> Many of our community members have already contributed to these
>> efforts. It is my hope that this would continue to be a collaborative
>> process benefiting the community in general, but with a clear,
>> centralized point of contact for these efforts.
>>
>> Please let me know if you agree this is a reasonable plan moving forward.
>>
>> Thanks,
>>
>> -Eric
>>
>> Gavin M. Bell wrote:
>>
>>> Gentle People,
>>>
>>> I would like to bring up the topic of Gateway installations.
>>>
>>> Is there a plan going forward from NCAR to facilitate / support the
>>> installation of gateways to those that want / have them?
>>>
>>> --
>>> Gavin M. Bell
>>> Lawrence Livermore National Labs
>>> --
>>>
>>> "Never mistake a clear view for a short distance."
>>> -Paul Saffo
>>>
>>> (GPG Key - http://*rainbow.llnl.gov/dist/keys/gavin.asc)
>>>
>>> A796 CE39 9C31 68A4 52A7 1F6B 66B7 B250 21D5 6D3E
>>>
>>>
>>
>>
>
> --
> Gavin M. Bell
> Lawrence Livermore National Labs
> --
>
> "Never mistake a clear view for a short distance."
> -Paul Saffo
>
> (GPG Key - http://rainbow.llnl.gov/dist/keys/gavin.asc)
>
> A796 CE39 9C31 68A4 52A7 1F6B 66B7 B250 21D5 6D3E
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
>
--
Estanislao Gonzalez
Max-Planck-Institut für Meteorologie (MPI-M)
Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre
Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany
Phone: +49 (40) 46 00 94-126
E-Mail: estanislao.gonzalez at zmaw.de
More information about the GO-ESSP-TECH
mailing list