Open Stack

Hi Elizabeth,

Sorry for not replying earlier, Monday was a holiday over here.

First thing: Thursday 9am (my time) sounds perfect. I have another
meeting at 10 am, but I think we can get you up and running in less than
that.

As for the installation (isntall.sh), you actually got most of it right.
The schema that the application is asking for is actually the name of
the schema that was used in the 'CREATE DATABASE' command. If you were
following the installation steps, then 'zanata' is the right schema name.

I can take a look at the log messages (you can send them over email or
pastebin, or something :) ) and could have answers for you before our chat.

About the security updates, it might not make any difference to you guys
because you run on Ubuntu. Because our production instances run on RHEL,
the jboss package gets automatically patched with each new EAP version.
In your case, Jboss patches would involve downloading the latest version
and installing Zanata from scratch (no data loss as the DB would remain
the same).

Once we manage to get Wildfly deployment going, there might be other
options, such as using the wildfly packages on Ubuntu, but we can cross
that bridge when we get there.

Regards,

Carlos.

Carlos A. Munoz
Software Engineering Supervisor
Engineering - Internationalization
Red Hat

On 06/06/2014 08:49 AM, Elizabeth K. Joseph wrote:
> On Mon, Jun 2, 2014 at 7:19 PM, Carlos Munoz <camunoz at redhat.com> wrote:
>> I will send you the puppet files directly in another email.
> 
> Thanks again for these, browsing through them has answered a few of my
> questions about configuration, I'll look deeper next week.
> 
>> On the JBoss front, I suggest then you go with the server zip that we
>> provide in the downloads section. It already provides all the necessary
>> changes needed to run zanata,
> 
> So I gave this a spin, and I think the instructions are missing some
> key points, ie following http://zanata.org/download/ it says:
> 
> "Create a database schema for Zanata. NOTE: Ensure that the default
> collation is UTF-8."
> 
> I have no idea what schema to use, so I went here for some ideas:
> https://github.com/zanata/zanata-server/wiki/Installation-Guide
> 
> Note that $ZANATA_DB_PASS isn't exported along with others, so that
> may be worth mentioning in case someone is following the database
> setup blindly ;)
> 
> Once I ran the database commands properly, I was still puzzled by
> "database schema" prompt during install.sh
> 
> elizabeth at zanata-demo:~/zanata-server/bin/zanata-installer$ ./install.sh
> Please select the Zanata version you wish to install:
> [1] 3.3.2
> 1
> Database Host:
> localhost
> Database port:
> 3306
> Database schema:
> zanata ...I know this is wrong, what does it want here?
> Database Username:
> zanata
> Database Password:
> not-my-real-password
> Downloading http://sourceforge.net/projects/zanata/files/webapp/zanata-war-3.3.2.war/download
> This might take a few minutes.
> null
> elizabeth at zanata-demo:~/zanata-server/bin/zanata-installer$
> 
> Ultimately, this doesn't work (because of database schema is wrong?).
> I tried launching jboss manually anyway to see if errors could help me
> out, and there are definitely zanata mysql errors but it's too much
> for me to intelligently debug and localhost:8080/zanata doesn't exist,
> as expected.
> 
> I have mysql-server libmysql-java openjdk-7-jdk packages installed on
> Ubuntu 14.04 so going by listed dependencies, it doesn't look like
> that's an issue.
> 
>> with the downside of not getting all the
>> security updates.
> 
> Is this due to the server zip not being updated with each version of
> Zanata, or because it's using JBoss AS rather than EAP? I guess my
> question is, will we run into the security issue if we insist upon
> using AS rather than EAP due to our licensing concerns?
> 
>> Deployment on the most current version of JBoss AS (WildFly 8.1) is
>> something we are currently looking at for future versions, but it's just
>> not ready at the moment.
>>
>> Lets schedule that IRC so we can answer some of your questions. We are
>> in UTC+10 timezone.
> 
> Looks like I can do Monday-Wednesday at 23:00 UTC (your Tuesday-Thursday at 9AM)
> 
> http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140609T23
> 
> I can also do an hour or two later Monday or Tuesday.
> 
> Happy to chat about any of the above issues I ran into then, so no rush.
>