Title: Re: [Oscar-devel] Configurator values -> ODA
With the recent fixes by
Erich, this is now confirmed to be working.
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of Bernard LiSent: Sat 01/07/2006 18:25To:
[EMAIL PROTECTED]; oscar-devel@lists.sourceforge.netSubject:
Title: Re: [Oscar-devel] Configurator values -> ODA
Hi Erich:
I just tried a fresh install
with FC5 x86, and the issue is still present. Here's the content of
/etc/gmetad.conf:gridname ""data_source
"" fc5-x86.ocg.org
The relevant bits from
/etc/gmond.con
Hi Bernard,
I fixed one thing and then tried calling
cd $OSCAR_HOME/packages/ganglia
env OSCAR_PACKAGE_HOME=`pwd` scripts/edit_ganglia_conf --gmetad --verbose
while the ODA table Packages_conf was empty. /etc/gmetad.conf looked good
afterwards. But I didn't try a clean fresh install.
We can o
Hi Wesley,
I'd propose to do it in some steps:
1. add the table (doesn't hurt)
2. prepare routines for reading/writing values from/to database (given opkg,
context)
3. prepare a routine to parse the configurator.values and feed the database
with them (doesn't hurt, yet, as it leaves the old t
So this approach sounds good to me, but there are a few things that I want to
know before I dive into this thing simply because I don't have enough time
here this summer to be able to address all these issues:
Would this still work for the current GUI or are there going to be some major
changes
On Wednesday 14 June 2006 14:33, Wesley Bland wrote:
> Continuing the discussion about Configurator:
>
> What is your idea about moving the configurator stuff to the ODA? I'm not
> opposed to the idea as it would probably make things simpler for me, but the
> problem that I run into is that I o
Hi Wesley,
a few weeks ago we were discussing how (and when) to move the configurator
data from dispersed files inside the packages/ directory into the OSCAR
database. That would make your life much easier because you'd just need a
method to enter the correct configuration variable names into the
Le Jeudi 8 Juin 2006 15:54, Bernard Li a écrit :
> Hi Wesley:
>
> You won't be modifying the behaviour of the GUI Configurator though,
> right?
>
> i.e. it will still use HTML as opposed to XML
Yes because in the worst case (if we do not want to maintain both the XML
files and the HTML files for
,
Bernard
> -Original Message-
> From: Ted Powell [mailto:[EMAIL PROTECTED] On Behalf
> Of Ted Powell
> Sent: Thursday, June 08, 2006 15:23
> To: Bernard Li
> Cc: Wesley Bland; oscar-devel@lists.sourceforge.net
> Subject: Re: [Oscar-devel] Configurator schema
>
> On
On Thu, Jun 08, 2006 at 12:54:47PM -0700, Bernard Li wrote:
> Hi Wesley:
>
> You won't be modifying the behaviour of the GUI Configurator though,
> right?
>
> i.e. it will still use HTML as opposed to XML
The GUI Configurator I'm (sort of) familiar with is the one at:
trunk/lib/OSCAR/Config
Hi Wesley:
You won't be modifying the behaviour of the GUI Configurator though,
right?
i.e. it will still use HTML as opposed to XML
Cheers,
Bernard
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Wesley Bland
> Sent: Thursday, June 08, 2006
Yes. The problem is the same for both. The automated install is basically
just a scripted version of the normal command line install.
Wesley
On Thursday 08 June 2006 2:02 pm, Michael Edwards wrote:
> Is the html vs xml a problem for the automated installs also?
>
> On 6/8/06, Wesley Bland <[EM
Is the html vs xml a problem for the automated installs also?
On 6/8/06, Wesley Bland <[EMAIL PROTECTED]> wrote:
> The probelm with using lynx is that I can't control the input and output in
> the way that I need, and I really do need the automation as that is the whole
> premise of my work.
>
> W
The probelm with using lynx is that I can't control the input and output in
the way that I need, and I really do need the automation as that is the whole
premise of my work.
Wesley
On Thursday 08 June 2006 1:21 pm, Bernard Li wrote:
> Hi Wesley:
>
> First of all welcome (but I think I have alre
Hi Wesley:
First of all welcome (but I think I have already said that in the conference
call before) and I'm glad that you're getting us involved in your summer
project.
Anyways, I have been meaning to contact you regarding your work. About your
problems with parsing the HTML - how about just
I guess my big question after looking at your wiki is "Why reinvent
functionality that works beter in the GUI?". I understand the need
for automated installs and the need for some sort of CLI interface,
but I am not really understanding the need for a fully featured text
mode installer which has s
Sorry about that, here's the URL:
https://svn.oscar.openclustergroup.org/trac/oscar/wiki/DevelDocs
My stuff is under Command Line Interface.
Wesley
On Thursday 08 June 2006 12:07 pm, Ted Powell wrote:
> On Thu, Jun 08, 2006 at 09:02:36AM -0400, Wesley Bland wrote:
> > [...]
> > Please send me an
On Thu, Jun 08, 2006 at 09:02:36AM -0400, Wesley Bland wrote:
> [...]
> Please send me any input you have and keep an eye on the wiki page to keep up
> with progress on the CLI.
On Thu, Jun 08, 2006 at 11:06:27AM -0400, Wesley Bland wrote:
> [...]
> would do). Feel free to take a look at the wiki
You're right. I'll admit that I am by no means an HTML expert and that many
of the things I described here can probably be done as long as you are
looking for output for an HTML browser. My problem is that I'm not trying to
use the HTML code as a browser would, but instead parse it to display
On Thu, Jun 08, 2006 at 09:02:36AM -0400, Wesley Bland wrote:
> As you may have seen this summer I'm working on making a CLI for the OSCAR
> Installer. As I have moved into the configurator step (Step 2), I have run
> into a major problem. HTML is very difficult to parse into a command line
>
20 matches
Mail list logo
