juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kurt T Stam <ks...@apache.org>
Subject Re: Updating the demo site
Date Thu, 03 Oct 2019 18:16:29 GMT
Hi Alex,

I have no clue about the file permission issue. Maybe Doug will come up
with something. Please see
https://issues.apache.org/jira/browse/INFRA-19146?focusedCommentId=16943799&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16943799

I have it running successfully from my home dir on that machine. How do we
proceed from here?

--Kurt

On Tue, Sep 24, 2019 at 12:53 PM Kurt Stam <kurt.stam@gmail.com> wrote:

> File creation in /tmp/juddi-db works like a charm, not so much in
> /var/lib/tomcat9/juddi-db
>
> https://issues.apache.org/jira/browse/INFRA-19146
>
>
>
> On Sep 24, 2019, at 6:20 PM, Alex O'Ree <alexoree@apache.org> wrote:
>
> I don't care either way, but persistent storage would be nice.
>
> On Tue, Sep 24, 2019, 5:31 AM Kurt Stam <kurt.stam@gmail.com> wrote:
>
>> Thanks I see it now!
>>
>> So before, the cloud instance was used PostgreSQL. Do we really want to
>> use Derby? I will look into the permission issue as soon as I have a second
>> to follow the instructions to get sudo.
>>
>> —Kurt
>>
>> On Sep 23, 2019, at 11:53 PM, Alex O'Ree <alexoree@apache.org> wrote:
>>
>> Juddi is already installed and running on the vm from the head of the git
>> repo with tomcat 9 I believe. The problem is derby won't fire up using the
>> file system for storage. Only the in memory db would work. I think I the
>> problem is file system permissions but I am not sure how to fix it.
>>
>>
>> On Mon, Sep 23, 2019, 11:08 AM Kurt Stam <kstam@redhat.com> wrote:
>>
>>> OK I’m in after https://issues.apache.org/jira/browse/INFRA-19130
>>>
>>>
>>> So Alex should we use a PostgreSQL DB? WDYT?
>>>
>>> Also the easiest is to get started using the preconfigured juddi-tomcat
>>> from juddi-distro-3.3.6.zip
>>> <http://apache.cs.uu.nl/juddi/juddi/3.3.6/juddi-distro-3.3.6.zip>,
>>> which actually has some issues on JDK8
>>>
>>> NOTE: Picked up JDK_JAVA_OPTIONS:
>>> --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/
>>> java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
>>> OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support
>>> was removed in 8.0
>>> OpenJDK 64-Bit Server VM warning: Ignoring option PermSize; support was
>>> removed in 8.0
>>> -Djava.endorsed.dirs=/home/kstam/juddi-distro-3.3.6/juddi-tomcat-3.3.6/endorsed
>>> is not supported. Endorsed standards and standalone APIs
>>> in modular form will be supported via the concept of upgradeable modules.
>>> Error: Could not create the Java Virtual Machine.
>>> Error: A fatal exception has occurred. Program will exit.
>>>
>>> So we either use a older JDK, or we need to release jUDDI with a newer
>>> tomcat version.
>>>
>>> How do you guys want to proceed?
>>>
>>> —Kurt
>>>
>>> On Sep 22, 2019, at 2:26 PM, Kurt Stam <kstam@redhat.com> wrote:
>>>
>>> Don’t Bernie me: https://www.youtube.com/watch?v=VGTaE1cLyJA
>>>
>>> On Sep 21, 2019, at 11:41 PM, Steve Viens <sviens@gmail.com> wrote:
>>>
>>> Not Guilty! ... but good grief - I am totally guilty of negligence.  I
>>> completely forgot about this.  My apologies.
>>>
>>> Steve
>>>
>>>
>>>
>>> On Sat, Sep 21, 2019 at 4:23 PM Kurt Stam <kurt.stam@gmail.com> wrote:
>>>
>>>> Steve did it!
>>>>
>>>> On Sep 21, 2019, at 22:20, Alex O'Ree <spyhunter99@gmail.com> wrote:
>>>>
>>>> 
>>>> did anyone delete the root business? hmmm....
>>>>
>>>> On Wed, Jul 31, 2019 at 11:55 AM Steve Viens <sviens@gmail.com> wrote:
>>>>
>>>>> Awesome Alex.  I’ve been buried for past two weeks and just catching
>>>>> up with personal email and saw yours.  I’ll take a look as soon as
I can.
>>>>>
>>>>> Steve
>>>>>
>>>>> On Sat, Jul 27, 2019 at 8:47 PM Alex O'Ree <alexoree@apache.org>
>>>>> wrote:
>>>>>
>>>>>> good news, i got the demo set up and running....
>>>>>>
>>>>>> https://demo.juddi.apache.org/
>>>>>> some important paths
>>>>>> /var/log/tomcat9
>>>>>> /var/lib/tomcat9/webapps
>>>>>> /etc/tomcat9
>>>>>>
>>>>>> the original tomcat root app was moved to /opt in case we need it
in
>>>>>> the future.....
>>>>>> ssl cert is via lets encrypt, good until oct 25th
>>>>>>
>>>>>> the hard part was getting derby to fire up. it ended up at
>>>>>> /etc/tomcat9/Catalina/...
>>>>>> all other locations had file permissions issues (or maybe a security
>>>>>> manager?)
>>>>>>
>>>>>> finally the site also runs on port 80 if needed, but tls should be
>>>>>> used when possible.
>>>>>>
>>>>>> On Sat, Jul 27, 2019 at 5:23 PM Alex O'Ree <alexoree@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Steve, Kurt
>>>>>>>
>>>>>>> Please confirm that you can sign into (via ssh)
>>>>>>> demo.juddi.apache.org
>>>>>>> use your asf credentials. You'll also want to test sudoing. ASF
>>>>>>> infra uses something all opie for open time passwords for sudo.
>>>>>>> Details here:
>>>>>>> https://issues.apache.org/jira/browse/INFRA-18617?focusedCommentId=16893249&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16893249
>>>>>>>
>>>>>>> Anyhow, try to sign in and run
>>>>>>> ortpasswd
>>>>>>> use the linked website to create the one time password and paste
it
>>>>>>> in
>>>>>>> then run
>>>>>>> sudo apt update
>>>>>>> it should prompt for a open time password, again, repeat the
process
>>>>>>>
>>>>>>> On Tue, Jun 18, 2019 at 5:33 PM Steve Viens <sviens@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I’ll volunteer!  Sign me up.
>>>>>>>>
>>>>>>>> Steve
>>>>>>>>
>>>>>>>> On Tue, Jun 18, 2019 at 5:26 PM Alex O'Ree <spyhunter99@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks Kurt!
>>>>>>>>>
>>>>>>>>> Just need one more person to act as a backup
>>>>>>>>>
>>>>>>>>> On Tue, Jun 18, 2019 at 10:30 AM Kurt Stam <kurt.stam@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Alex,
>>>>>>>>>>
>>>>>>>>>> I can help.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> —Kurt
>>>>>>>>>>
>>>>>>>>>> > On Jun 15, 2019, at 4:57 PM, Alex O'Ree <alexoree@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Dear jUDDI enthusiasts,
>>>>>>>>>> >
>>>>>>>>>> > We used to have a "gear" in the redhat cloud
that hosted a demo
>>>>>>>>>> instance of juddi. I'm not too sure what happened
but i think it either
>>>>>>>>>> expired or redhat turned them all off or whatever
and migrated to something
>>>>>>>>>> else. Regardless, that instance has been dead for
a while.
>>>>>>>>>> >
>>>>>>>>>> > Moving forward, i've asked the ASF infra team
if they have a
>>>>>>>>>> solution. The answer is yes, they can fire up a VM
for this purpose. The
>>>>>>>>>> only catch is that they want to have at least 3 people
be designated as
>>>>>>>>>> maintainers of the VM.
>>>>>>>>>> >
>>>>>>>>>> > I'll certainly volunteer but i'll need 2 others
to volunteer in
>>>>>>>>>> order to move forward. I would expect that time requirement
by those
>>>>>>>>>> volunteers would be super minimal, every now and
again type of thing. It'll
>>>>>>>>>> be an ubuntu vm.
>>>>>>>>>> >
>>>>>>>>>> > Anyone out there want to help?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>> Steve Viens
>>>>>>>> sviens@gmail.com
>>>>>>>> 603-828-2397
>>>>>>>>
>>>>>>> --
>>>>> Steve Viens
>>>>> sviens@gmail.com
>>>>> 603-828-2397
>>>>>
>>>>
>>>
>>>
>>
>

Mime
View raw message