[OPEN-ILS-GENERAL] I Need Help With Hostname

K. D. kd.8 at icloud.com
Wed Mar 6 19:09:55 EST 2013


I downloaded the client.  



On Mar 6, 2013, at 11:07 AM, open-ils-general-request at list.georgialibraries.org wrote:

> Send Open-ils-general mailing list submissions to
>    open-ils-general at list.georgialibraries.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://libmail.georgialibraries.org/mailman/listinfo/open-ils-general
> or, via email, send a message with subject or body 'help' to
>    open-ils-general-request at list.georgialibraries.org
> 
> You can reach the person managing the list at
>    open-ils-general-owner at list.georgialibraries.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Open-ils-general digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: I Need Help With Hostname (Tara Robertson)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 6 Mar 2013 09:07:08 -0800
> From: Tara Robertson <information.detective at gmail.com>
> Subject: Re: [OPEN-ILS-GENERAL] I Need Help With Hostname
> To: Evergreen Discussion Group
>    <open-ils-general at list.georgialibraries.org>
> Message-ID:
>    <CALPJNUkxyY3-jqo+KULTsuVD+8XikBt9sqbKap3JQ+vJT2349A at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi,
> 
> I'm still unclear if you downloaded Evergreen and created you own
> installation of Evergreen. This would've taken a little while, or if you
> downloaded the client, this would've taken about a minute.
> 
> Can you clarify if you set up an Evergreen server, or if you just
> downloaded the client?
> 
> Thanks,
> Tara
> 
> On Wed, Mar 6, 2013 at 8:54 AM, K. D. <kd.8 at icloud.com> wrote:
> 
>> Hello Jason, Tara and all:
>> 
>> I installed the 2.3 version of evergreen software.  What client version or
>> server works with this latest?
>> 
>> Assuming I want to host this locally, what are the steps to host it
>> locally?
>> 
>> As always, thank you for your assistance.
>> 
>> 
>> On Feb 27, 2013, at 10:55 AM,
>> open-ils-general-request at list.georgialibraries.org wrote:
>> 
>>> Send Open-ils-general mailing list submissions to
>>>   open-ils-general at list.georgialibraries.org
>>> 
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>   http://libmail.georgialibraries.org/mailman/listinfo/open-ils-general
>>> or, via email, send a message with subject or body 'help' to
>>>   open-ils-general-request at list.georgialibraries.org
>>> 
>>> You can reach the person managing the list at
>>>   open-ils-general-owner at list.georgialibraries.org
>>> 
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Open-ils-general digest..."
>>> 
>>> 
>>> Today's Topics:
>>> 
>>>  1. Re: [OPEN-ILS-DEV] Evergreen & Software Performance Analysis
>>>     (Tim Spindler)
>>>  2. Re: I Need Help With Hostname (Tara Robertson)
>>>  3. Re: [OPEN-ILS-DEV] Evergreen & Software Performance Analysis
>>>     (Mike Rylander)
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> 
>>> Message: 1
>>> Date: Wed, 27 Feb 2013 11:45:27 -0500
>>> From: Tim Spindler <tjspindler at gmail.com>
>>> Subject: Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen & Software
>>>   Performance Analysis
>>> To: Evergreen Discussion Group
>>>   <open-ils-general at list.georgialibraries.org>
>>> Cc: Evergreen Development Discussion List
>>>   <open-ils-dev at list.georgialibraries.org>
>>> Message-ID:
>>>   <CAMAokjPDptvu4ssy+f=7cPBJihVKHzizB-6-YDqOOB6_ke89iw at mail.gmail.com>
>>> Content-Type: text/plain; charset="iso-8859-1"
>>> 
>>> Kathy,
>>> 
>>> Are do you want some information like workflows that seem slow?  For
>>> instance, just got a report from a library about specific steps they are
>>> doing to catalogiing where certain individual processes are slow.
>>> 
>>> Tim
>>> 
>>> On Wed, Feb 27, 2013 at 11:37 AM, Kathy Lussier <klussier at masslnc.org
>>> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> It was brought to my attention that everyone who may have some input for
>>>> this discussion may not have an Evergreen wiki account. In that case,
>>>> please feel free to send an e-mail (to the list, not directly to me)
>>>> identifying any performance issues you believe should be addressed
>> through
>>>> a performance evaluation. I'll be happy to add them to the wiki.
>>>> 
>>>> What I'm looking for is:
>>>> 
>>>> 1. Any specific paint points you see in performance.
>>>> 2. Any specific questions you think a performance evaluation should
>> answer.
>>>> 3. Any ideas you might already have regarding causes of performance
>>>> problems. In reading through the logs from the "future of the staff
>> client"
>>>> meeting, I noticed several people said they thought it was important to
>>>> bring these ideas together before reaching out to a consultant, and I
>> agree
>>>> that this is an important first step in the process.
>>>> 
>>>> I posted just a few of our local issues at
>> http://www.evergreen-ils.org/dokuwiki/doku.php?id=dev:testing:performance_issues
>>>> :
>>>> 
>>>> STAFF CLIENT:
>>>> 
>>>> Memory leaks - is there an inherent problem with the technology used in
>>>> the staff client (xulrunner, Dojo) that is the source of the memory leak
>>>> problem and other performance problems?
>>>> Slow retrieval of patron records
>>>> 
>>>> MESSAGING (OPENSRF):
>>>> Staff client batch operations (e.g. updates/deletes from copy buckets)
>>>> 
>>>> DATABASE:
>>>> Catalog search - is there a way to optimize searching in the catalog so
>>>> that users get faster results and are able to start re-implementing
>> things
>>>> like search.relevance_adjustment to provide boosts to relevance ranking?
>>>> 
>>>> I'm quite sure there are far more pain points out there, so please don't
>>>> feel shy about contributing to the list!
>>>> 
>>>> 
>>>> Kathy
>>>> 
>>>> 
>>>> 
>>>> Kathy Lussier
>>>> Project Coordinator
>>>> Massachusetts Library Network Cooperative(508)
>> 343-0128klussier at masslnc.org
>>>> Twitter: http://www.twitter.com/kmlussier
>>>> 
>>>> On 2/25/2013 11:44 AM, Kathy Lussier wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> Having heard no objections to proceeding with finding somebody to do a
>>>> software performance analysis, I have created a page on the wiki at
>> http://www.open-ils.org/dokuwiki/doku.php?id=dev:testing:performance_issueswherewe can identify the pain points that need further evaluation and add
>>>> any questions that we hope a performance analysis might be able to
>> answer.
>>>> 
>>>> I have started the list off with some basic issues/questions that have
>>>> come up in our own systems. During the future of the staff client
>> meeting,
>>>> Dan Scott had mentioned that there might be three points of
>> attack:client,
>>>> opensrf, database.  I thought dividing the list into those three areas
>>>> might be a good way to start.
>>>> 
>>>> I'm hoping that all the knowledgeable sys admins out there who have a
>>>> stronger understanding of the system architecture than I do can build
>> this
>>>> list into something that might be a good starting point for any
>> performance
>>>> evaluation, whether it's done by a third party or by somebody in the
>>>> Evergreen community. By identifying the questions we hope a performance
>>>> evaluation might answer, we are also identifying what our expectations
>> are
>>>> before we enter the process. I would want to be clear on our
>> expectations
>>>> before formally talking to any third party so that we can be fully
>> informed
>>>> about whether an evaluation could meet those expectations.
>>>> 
>>>> Kathy
>>>> 
>>>> 
>>>> Kathy Lussier
>>>> Project Coordinator
>>>> Massachusetts Library Network Cooperative(508)
>> 343-0128klussier at masslnc.org
>>>> Twitter: http://www.twitter.com/kmlussier
>>>> 
>>>> On 2/20/2013 2:26 PM, Mike Rylander wrote:
>>>> 
>>>> On Wed, Feb 20, 2013 at 2:10 PM, Kathy Lussier <klussier at masslnc.org
>>> wrote:
>>>> 
>>>>> Hi all,
>>>>> 
>>>>> I wasn't sure if I should add this to the QA discussion, but it seemed
>>>>> worthy of its own thread.
>>>>> 
>>>>> During the "future of the staff client" meeting, I advocated for
>> bringing
>>>>> in a consultant to do a software performance analysis for Evergreen to
>> help
>>>>> us identify where the critical bottlenecks are in the system in the
>> hopes
>>>>> that we could then identify the areas that need to be worked on to
>> improve
>>>>> performance. At the time, I didn't have any concrete suggestions on
>> finding
>>>>> a consultant who could take on this project, but I have since done some
>>>>> more investigation and have a couple of leads, the most promising of
>> which
>>>>> is an individual local to Massachusetts who previously worked for many
>>>>> years at Stratus Technologies where he was involved in all levels of
>>>>> performance analysis. He now teaches graduate-level courses on
>> performance
>>>>> evaluation and also does contract work.
>>>>> 
>>>>> Now that I actually have concrete leads, I would like to get the ball
>>>>> rolling, provided there is support from the larger community. I'm not
>> quite
>>>>> sure how this might fit in with ESI's planned QA efforts or with the
>>>>> possibility of bringing in a firm like OmniTI as Dan suggested, but my
>>>>> reading into these QA e-mails is that the focus would be on testing new
>>>>> commits.
>>>> 
>>>> I want to clarify something that Dan seems to have assumed incorrectly:
>>>> that anything ESI does is mutually exclusive with bringing in outside
>>>> expertise.  Nobody has any grounds to stop such an effort, and it would
>>>> be ridiculous to argue otherwise, words put into my mouth
>> notwithstanding.
>>>> The initial focus of an ESI effort will be what exists today, through
>>>> infrastructure, so that what exists tomorrow can then be tested.
>>>> 
>>>> As for how it would fit in, ESI would absorb and internalize any advice
>>>> or direction, just like any other community member, and work within the
>>>> community to incorporate that.
>>>> 
>>>> So, why have ESI involved at all?  Besides the fact that we create a
>>>> significant portion of the code, and that it benefits us as much as
>> anyone
>>>> to have a more stable Evergreen, there is a need for ongoing, active
>>>> leadership in QA.  The fact is that it has not materialized yet, so
>> we're
>>>> looking for a way to make that a maintainable proposition for the
>>>> community's benefit.  That means ongoing, deep integration with both
>>>> developer and user communities.  And that is not something that we can
>>>> expect from OmniTI or any other organization that is not plugged into
>> those
>>>> communities.  Could some other organization step into that role, and
>>>> provide years of ongoing QA support?  Perhaps so, but ESI exists today
>> and
>>>> has the Evergreen expertise needed to avoid long (and costly) ramp-up
>> time.
>>>> 
>>>> The point is this, though, ESI will encourage any effort to improve
>>>> Evergreen, and is willing and able to work in the community, as we
>> always
>>>> do, to further those efforts.
>>>> 
>>>> Thanks, Kathy!
>>>> 
>>>> --
>>>> Mike Rylander
>>>> | Director of Research and Development
>>>> | Equinox Software, Inc. / Your Library's Guide to Open Source
>>>> | phone:  1-877-OPEN-ILS (673-6457)
>>>> | email:  miker at esilibrary.com
>>>> | web:  http://www.esilibrary.com
>>> 
>>> 
>>> --
>>> Tim Spindler
>>> tjspindler at gmail.com
>>> 
>>> *P**   Go Green - **Save a tree! Please don't print this e-mail unless
>> it's
>>> really necessary.*
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: <
>> http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20130227/11e6bce2/attachment-0001.htm
>>> 
>>> 
>>> ------------------------------
>>> 
>>> Message: 2
>>> Date: Wed, 27 Feb 2013 08:50:28 -0800
>>> From: Tara Robertson <information.detective at gmail.com>
>>> Subject: Re: [OPEN-ILS-GENERAL] I Need Help With Hostname
>>> To: Evergreen Discussion Group
>>>   <open-ils-general at list.georgialibraries.org>
>>> Message-ID:
>>>   <CALPJNUkfz3s=H9OjPJkWpHyxWYgPkE6ZhDfnmW1_3g1gsyxPWw at mail.gmail.com>
>>> Content-Type: text/plain; charset="iso-8859-1"
>>> 
>>> Hi,
>>> 
>>> My hunch also is that you might have just downloaded the client. There
>> are
>>> some community Evergreen servers:
>> http://www.open-ils.org/dokuwiki/doku.php?id=community_servers#community_demo_serversCan
>>> you connect to any of them from your computer?
>>> 
>>> Cheers,
>>> Tara
>>> 
>>> On Wed, Feb 27, 2013 at 8:07 AM, Jason Stephenson <jstephenson at mvlc.org
>>> wrote:
>>> 
>>>> Quoting "K. D." <kd.8 at icloud.com>:
>>>> 
>>>> Hi Steve Wills and Alexey Lazar:
>>>>> 
>>>>> I installed the software on Windows 7.  Command HOSTNAME does not tell
>> me
>>>>> anything.  I am currently using local host.  I do appreciate your
>> support.
>>>> You need a server to connect to. It sounds like you have downloaded the
>>>> client. The client by itself is useless without a server.
>>>> 
>>>> 
>>>> --
>>>> Jason Stephenson
>>>> Assistant Director for Technology Services
>>>> Merrimack Valley Library Consortium
>>>> Chief Bug Wrangler, Evergreen ILS
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: <
>> http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20130227/ba69c699/attachment-0001.htm
>>> 
>>> 
>>> ------------------------------
>>> 
>>> Message: 3
>>> Date: Wed, 27 Feb 2013 11:55:01 -0500
>>> From: Mike Rylander <mrylander at gmail.com>
>>> Subject: Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen & Software
>>>   Performance Analysis
>>> To: Evergreen Discussion Group
>>>   <open-ils-general at list.georgialibraries.org>
>>> Cc: Evergreen Development Discussion List
>>>   <open-ils-dev at list.georgialibraries.org>
>>> Message-ID:
>>>   <CAO8ar=njaCv0zcffhH_oZjR9nMFnU5xT-mVmBgF2rnsr=-uW_g at mail.gmail.com>
>>> Content-Type: text/plain; charset="iso-8859-1"
>>> 
>>> Thanks, Kathy, this is great!  I've filled in some info that ESI has
>>> gathered and experiments toward resolution we've performed.  We'll work
>> to
>>> keep this up to date with any progress we make.
>>> 
>>> --miker
>>> 
>>> 
>>> 
>>> On Wed, Feb 27, 2013 at 11:37 AM, Kathy Lussier <klussier at masslnc.org
>>> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> It was brought to my attention that everyone who may have some input for
>>>> this discussion may not have an Evergreen wiki account. In that case,
>>>> please feel free to send an e-mail (to the list, not directly to me)
>>>> identifying any performance issues you believe should be addressed
>> through
>>>> a performance evaluation. I'll be happy to add them to the wiki.
>>>> 
>>>> What I'm looking for is:
>>>> 
>>>> 1. Any specific paint points you see in performance.
>>>> 2. Any specific questions you think a performance evaluation should
>> answer.
>>>> 3. Any ideas you might already have regarding causes of performance
>>>> problems. In reading through the logs from the "future of the staff
>> client"
>>>> meeting, I noticed several people said they thought it was important to
>>>> bring these ideas together before reaching out to a consultant, and I
>> agree
>>>> that this is an important first step in the process.
>>>> 
>>>> I posted just a few of our local issues at
>> http://www.evergreen-ils.org/dokuwiki/doku.php?id=dev:testing:performance_issues
>>>> :
>>>> 
>>>> STAFF CLIENT:
>>>> 
>>>> Memory leaks - is there an inherent problem with the technology used in
>>>> the staff client (xulrunner, Dojo) that is the source of the memory leak
>>>> problem and other performance problems?
>>>> Slow retrieval of patron records
>>>> 
>>>> MESSAGING (OPENSRF):
>>>> Staff client batch operations (e.g. updates/deletes from copy buckets)
>>>> 
>>>> DATABASE:
>>>> Catalog search - is there a way to optimize searching in the catalog so
>>>> that users get faster results and are able to start re-implementing
>> things
>>>> like search.relevance_adjustment to provide boosts to relevance ranking?
>>>> 
>>>> I'm quite sure there are far more pain points out there, so please don't
>>>> feel shy about contributing to the list!
>>>> 
>>>> 
>>>> Kathy
>>>> 
>>>> 
>>>> 
>>>> Kathy Lussier
>>>> Project Coordinator
>>>> Massachusetts Library Network Cooperative(508)
>> 343-0128klussier at masslnc.org
>>>> Twitter: http://www.twitter.com/kmlussier
>>>> 
>>>> On 2/25/2013 11:44 AM, Kathy Lussier wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> Having heard no objections to proceeding with finding somebody to do a
>>>> software performance analysis, I have created a page on the wiki at
>> http://www.open-ils.org/dokuwiki/doku.php?id=dev:testing:performance_issueswherewe can identify the pain points that need further evaluation and add
>>>> any questions that we hope a performance analysis might be able to
>> answer.
>>>> 
>>>> I have started the list off with some basic issues/questions that have
>>>> come up in our own systems. During the future of the staff client
>> meeting,
>>>> Dan Scott had mentioned that there might be three points of
>> attack:client,
>>>> opensrf, database.  I thought dividing the list into those three areas
>>>> might be a good way to start.
>>>> 
>>>> I'm hoping that all the knowledgeable sys admins out there who have a
>>>> stronger understanding of the system architecture than I do can build
>> this
>>>> list into something that might be a good starting point for any
>> performance
>>>> evaluation, whether it's done by a third party or by somebody in the
>>>> Evergreen community. By identifying the questions we hope a performance
>>>> evaluation might answer, we are also identifying what our expectations
>> are
>>>> before we enter the process. I would want to be clear on our
>> expectations
>>>> before formally talking to any third party so that we can be fully
>> informed
>>>> about whether an evaluation could meet those expectations.
>>>> 
>>>> Kathy
>>>> 
>>>> 
>>>> Kathy Lussier
>>>> Project Coordinator
>>>> Massachusetts Library Network Cooperative(508)
>> 343-0128klussier at masslnc.org
>>>> Twitter: http://www.twitter.com/kmlussier
>>>> 
>>>> On 2/20/2013 2:26 PM, Mike Rylander wrote:
>>>> 
>>>> On Wed, Feb 20, 2013 at 2:10 PM, Kathy Lussier <klussier at masslnc.org
>>> wrote:
>>>> 
>>>>> Hi all,
>>>>> 
>>>>> I wasn't sure if I should add this to the QA discussion, but it seemed
>>>>> worthy of its own thread.
>>>>> 
>>>>> During the "future of the staff client" meeting, I advocated for
>> bringing
>>>>> in a consultant to do a software performance analysis for Evergreen to
>> help
>>>>> us identify where the critical bottlenecks are in the system in the
>> hopes
>>>>> that we could then identify the areas that need to be worked on to
>> improve
>>>>> performance. At the time, I didn't have any concrete suggestions on
>> finding
>>>>> a consultant who could take on this project, but I have since done some
>>>>> more investigation and have a couple of leads, the most promising of
>> which
>>>>> is an individual local to Massachusetts who previously worked for many
>>>>> years at Stratus Technologies where he was involved in all levels of
>>>>> performance analysis. He now teaches graduate-level courses on
>> performance
>>>>> evaluation and also does contract work.
>>>>> 
>>>>> Now that I actually have concrete leads, I would like to get the ball
>>>>> rolling, provided there is support from the larger community. I'm not
>> quite
>>>>> sure how this might fit in with ESI's planned QA efforts or with the
>>>>> possibility of bringing in a firm like OmniTI as Dan suggested, but my
>>>>> reading into these QA e-mails is that the focus would be on testing new
>>>>> commits.
>>>> 
>>>> I want to clarify something that Dan seems to have assumed incorrectly:
>>>> that anything ESI does is mutually exclusive with bringing in outside
>>>> expertise.  Nobody has any grounds to stop such an effort, and it would
>>>> be ridiculous to argue otherwise, words put into my mouth
>> notwithstanding.
>>>> The initial focus of an ESI effort will be what exists today, through
>>>> infrastructure, so that what exists tomorrow can then be tested.
>>>> 
>>>> As for how it would fit in, ESI would absorb and internalize any advice
>>>> or direction, just like any other community member, and work within the
>>>> community to incorporate that.
>>>> 
>>>> So, why have ESI involved at all?  Besides the fact that we create a
>>>> significant portion of the code, and that it benefits us as much as
>> anyone
>>>> to have a more stable Evergreen, there is a need for ongoing, active
>>>> leadership in QA.  The fact is that it has not materialized yet, so
>> we're
>>>> looking for a way to make that a maintainable proposition for the
>>>> community's benefit.  That means ongoing, deep integration with both
>>>> developer and user communities.  And that is not something that we can
>>>> expect from OmniTI or any other organization that is not plugged into
>> those
>>>> communities.  Could some other organization step into that role, and
>>>> provide years of ongoing QA support?  Perhaps so, but ESI exists today
>> and
>>>> has the Evergreen expertise needed to avoid long (and costly) ramp-up
>> time.
>>>> 
>>>> The point is this, though, ESI will encourage any effort to improve
>>>> Evergreen, and is willing and able to work in the community, as we
>> always
>>>> do, to further those efforts.
>>>> 
>>>> Thanks, Kathy!
>>>> 
>>>> --
>>>> Mike Rylander
>>>> | Director of Research and Development
>>>> | Equinox Software, Inc. / Your Library's Guide to Open Source
>>>> | phone:  1-877-OPEN-ILS (673-6457)
>>>> | email:  miker at esilibrary.com
>>>> | web:  http://www.esilibrary.com
>>> 
>>> 
>>> --
>>> Mike Rylander
>>> | Director of Research and Development
>>> | Equinox Software, Inc. / Your Library's Guide to Open Source
>>> | phone:  1-877-OPEN-ILS (673-6457)
>>> | email:  miker at esilibrary.com
>>> | web:  http://www.esilibrary.com
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: <
>> http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20130227/55f12b53/attachment.htm
>>> 
>>> 
>>> End of Open-ils-general Digest, Vol 80, Issue 45
>>> ************************************************
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20130306/a616e002/attachment.htm>
> 
> End of Open-ils-general Digest, Vol 81, Issue 8
> ***********************************************


More information about the Open-ils-general mailing list