/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
--
Gao,Yan y...@suse.com
Senior Software Engineer
SUSE LINUX Products GmbH
It turned out to be a bug in pengine. Fixed and requested:
https://github.com/ClusterLabs/pacemaker/pull/595
Regards,
Yan
On 30/09/2014 19:55, Gao,Yan wrote:
Hi Youssef,
I tried promote and it worked for my simple configuration.
Which version are you running? Is it possible to collect
From: Gao,Yan y...@suse.com
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] symmetrical ordering flaw for multi-state
resources
Message-ID: 5425524b.9010...@suse.com
Content-Type: text/plain; charset=windows-1252
Hi Youssef
/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
--
Gao,Yan y...@suse.com
Senior Software Engineer
SUSE LINUX Products GmbH
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http
On 06/06/14 13:21, Gao,Yan wrote:
On 01/29/14 13:44, Andrew Beekhof wrote:
On 28 Jan 2014, at 10:11 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote:
Hi all,
Just discovered, that when I add resource to a middle of
(running) group, it is added to the end.
I mean, if I update following
@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE
://bugs.clusterlabs.org
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started
Hi,
On 09/18/13 17:54, Lars Marowsky-Bree wrote:
On 2013-09-18T17:53:16, Gao,Yan y...@suse.com wrote:
actions-limit is a good name. (One of the three hard problems in
computer science! ;-)
(If we need it more fine grained at any point in the future, we can
always add class/provider/type/op
On 09/17/13 15:53, Lars Marowsky-Bree wrote:
On 2013-09-16T18:19:55, Gao,Yan y...@suse.com wrote:
1. Global property: operations-limit, operations-limit-migrate (alias
for migration-threshold)
How about to keep it migration-limit, and name the new property
the current DC if
unset?
Probably it's the only feasible way for now.
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman
resource secret Journal set password xx
/bin/sh: cibsecret: command not found
I use pacemaker 1.1.9.
If there is no cibsecret command, what is the right way to store
passwords in the configuration?
You have to configure it --with-cibsecrets when building.
Regards,
Gao,Yan
--
Gao,Yan y
Hi,
Was pacemaker built --with-acl? Is acls listed in the output of
cibadmin -!?
Regards,
Gao,Yan
On 07/08/13 17:57, emmanuel segura wrote:
Hi
I did
Thanks
2013/7/8 Dejan Muhamedagic deja...@fastmail.fm
mailto:deja...@fastmail.fm
Hi,
On Mon, Jul 08, 2013 at 12:52
way is:
./ConfigureMe configure [options]
Regards,
Gao,Yan
Configure flags for RedHat Linux: --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --mandir=/usr/share/man --disable-rpath
Usage: ./ConfigureMe
{configure|make|install|dist|distcheck|package|flags|bootstrap} [--xxx=yyy
way is:
./ConfigureMe configure [options]
Regards,
Gao,Yan
thanks I did it but now
./ConfigureMe configure --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --mandir=/usr/share/man --disable-rpath
Configure flags for RedHat Linux: --prefix=/usr --sysconfdir=/etc
--localstatedir
On 02/05/13 16:29, Andrew Beekhof wrote:
On Fri, Feb 1, 2013 at 3:37 PM, Gao,Yan y...@suse.com wrote:
Hi Andrew,
On 01/31/13 14:35, Andrew Beekhof wrote:
On 24/01/2013, at 3:36 AM, David Vossel dvos...@redhat.com wrote:
- Original Message -
From: Yan Gao y...@suse.com
remote monitoring
Hi,
Here's the code for supporting nagios plugins in lrmd:
https://github.com/gao-yan/pacemaker/commits/nagios
A new resource class nagios is introduced.
Actions:
- probe: A resource defined for a resource container is not probed.
(We
can also add a condition in pengine
for supporting nagios plugins in lrmd:
https://github.com/gao-yan/pacemaker/commits/nagios
A new resource class nagios is introduced.
Actions:
- probe: A resource defined for a resource container is not probed.
(We
can also add a condition in pengine to just avoid probing a nagios
class
the probe action invokes --version for the
plugin, which can cover the cases of NOT_INSTALLED and
INSUFFICIENT_PRIV. If the invocation succeeds, returns NOT_RUNNING to
crmd. I think this should make sense, right?
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE
Hi,
Here's the code for supporting nagios plugins in lrmd:
https://github.com/gao-yan/pacemaker/commits/nagios
A new resource class nagios is introduced.
Actions:
- probe: A resource defined for a resource container is not probed. (We
can also add a condition in pengine to just avoid probing
: heartbeat-devel
Requires: heartbeat
%endif
And:
./ConfigureMe configure
make
will do that.
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http
pacemaker-1.1.8.
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http
for stop op defaults to restart-container:
https://github.com/gao-yan/pacemaker/commits/container
And yes, internally, failed stop operations are ignored so that the
container can be restarted, given that there's a mandatory order.
But really I'd not want to make oh let's just skip stop
On 12/12/12 15:38, Gao,Yan wrote:
On 12/12/12 11:14, Gao,Yan wrote:
On 12/12/12 01:53, David Vossel wrote:
- Original Message -
From: Yan Gao y...@suse.com
To: pacemaker@oss.clusterlabs.org
Sent: Tuesday, December 11, 2012 1:23:03 AM
Subject: Re: [Pacemaker] Enable remote monitoring
On 12/12/12 01:53, David Vossel wrote:
- Original Message -
From: Yan Gao y...@suse.com
To: pacemaker@oss.clusterlabs.org
Sent: Tuesday, December 11, 2012 1:23:03 AM
Subject: Re: [Pacemaker] Enable remote monitoring
Hi,
Here's the latest code:
https://github.com/gao-yan/pacemaker
On 12/12/12 11:14, Gao,Yan wrote:
On 12/12/12 01:53, David Vossel wrote:
- Original Message -
From: Yan Gao y...@suse.com
To: pacemaker@oss.clusterlabs.org
Sent: Tuesday, December 11, 2012 1:23:03 AM
Subject: Re: [Pacemaker] Enable remote monitoring
Hi,
Here's the latest code
Hi,
Here's the latest code:
https://github.com/gao-yan/pacemaker/commit/4d58026c2171c42385c85162a0656c44b37fa7e8
Now:
- container-type:
* black - ordering, colocating
* white - ordering
Both them are not probed so far.
- on-fail defaults restart-container for most actions,
except
it. Of course if needed, we can introduce a probe
meta attribute for primitive, and:
black implies - ordering, colocated, probe=false
white implies - ordering, probe=false
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE
it too. Here comes the drafted code:
https://github.com/gao-yan/pacemaker/commit/4f7b80baa42f3801c1fb8186aef076877f34dfea
It works in my simple test. Although failures of resources hasn't
counted against container's migration-threshold yet, it shows you the
basic idea. I'd appreciate if you can
now.
I like it too. Here comes the drafted code:
https://github.com/gao-yan/pacemaker/commit/4f7b80baa42f3801c1fb8186aef076877f34dfea
It works in my simple test. Although failures of resources hasn't
counted against container's migration-threshold yet, it shows you the
basic idea. I'd
On 12/07/12 10:14, Andrew Beekhof wrote:
On Fri, Dec 7, 2012 at 12:46 PM, Gao,Yan y...@suse.com wrote:
what about:
container-type=(black | white)
black: colocate with the vm
white: potentially other colocation or location constraints
Or just:
contained=(true| false)
Detaults
On 12/07/12 10:50, Andrew Beekhof wrote:
On Fri, Dec 7, 2012 at 1:44 PM, Gao,Yan y...@suse.com wrote:
On 12/07/12 10:14, Andrew Beekhof wrote:
On Fri, Dec 7, 2012 at 12:46 PM, Gao,Yan y...@suse.com wrote:
what about:
container-type=(black | white)
black: colocate with the vm
white
container:start - resource:start internally should applies for most
cases, and it would simplify the configuration of the white container.
Regards,
Gao,Yan
Colocation is less clear, I think the default is no but David has suggested
an additional meta attribute to turn it on.
--
Gao,Yan y
On 12/07/12 12:09, Andrew Beekhof wrote:
On Fri, Dec 7, 2012 at 3:00 PM, Gao,Yan y...@suse.com wrote:
On 12/07/12 07:38, Andrew Beekhof wrote:
On 06/12/2012, at 10:42 PM, Lars Marowsky-Bree l...@suse.com wrote:
On 2012-12-06T22:25:40, Andrew Beekhof and...@beekhof.net wrote:
But any
Hi,
This is the first step - the support of restart-origin for order
constraint along with the test cases:
https://github.com/gao-yan/pacemaker/commits/restart-origin
It looks straight-forward to me. Hope I didn't miss anything ;-)
If restart-origin=true combines with kind=Optional, it just
for order
constraint along with the test cases:
https://github.com/gao-yan/pacemaker/commits/restart-origin
It looks straight-forward to me. Hope I didn't miss anything ;-)
I had made some in-line comments for you in git-hub. It looks like you are
on the right track.
Thanks!
I'm just
On 12/06/12 04:52, David Vossel wrote:
Hi,
This is the first step - the support of restart-origin for order
constraint along with the test cases:
https://github.com/gao-yan/pacemaker/commits/restart-origin
It looks straight-forward to me. Hope I didn't miss anything ;-)
I had made some
Hi Andrew,
Thanks for the comments!
On 12/06/12 09:44, Andrew Beekhof wrote:
On 05/12/2012, at 11:27 PM, Gao,Yan y...@suse.com wrote:
Hi,
This is the first step - the support of restart-origin for order
constraint along with the test cases:
https://github.com/gao-yan/pacemaker/commits
On 12/04/12 18:21, Lars Marowsky-Bree wrote:
On 2012-12-04T12:45:05, Gao,Yan y...@suse.com wrote:
(Ohhh. Did we just find a use for a negative score here? ;-) Just
throwing that out there. It'd fit the model we have so far, is all I'm
saying.)
Perhaps to name another kind for order
on it yet. :-)
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http
-origin=true
resource_set id=vm-and-rscs sequential=true
resource_ref id=vm/
resource_ref id=nagios-foo/
resource_ref id=nagios-bar/
/resource_set
/rsc_order
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE
Hi Andrew,
On 11/08/12 13:09, Andrew Beekhof wrote:
On Tue, Nov 6, 2012 at 10:30 PM, Gao,Yan y...@suse.com wrote:
Hi,
Currently, we can manage VMs via the VM agents. But the services running
within VMs are not very easy to be monitored. If we could use
nagios/icinga probes from the host
and appreciated.
Thanks,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting
On 03/27/12 13:56, Andrew Beekhof wrote:
On Tue, Mar 27, 2012 at 2:40 PM, Gao,Yan y...@suse.com wrote:
On 03/27/12 10:33, Andrew Beekhof wrote:
On Tue, Mar 27, 2012 at 2:34 AM, Jiaju Zhang jjzh...@suse.de wrote:
On Mon, 2012-03-26 at 11:50 +0900, Yuichi Seino wrote:
Hi Jiaju,
I have
,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started
number.
Regards
Gao,Yan
Sincerely,
Jiaju
2012年3月27日11:33 Andrew Beekhof and...@beekhof.net:
On Tue, Mar 27, 2012 at 2:34 AM, Jiaju Zhang jjzh...@suse.de wrote:
On Mon, 2012-03-26 at 11:50 +0900, Yuichi Seino wrote:
Hi Jiaju,
I have a question about booth.
I would like to know
Hi Florian,
On 02/24/12 16:00, Florian Haas wrote:
On 02/24/12 02:53, Andrew Beekhof wrote:
We're about to lock in the syntax for cluster tickets (used for
multi-ste clusters).
The syntax rules are at:
https://github.com/gao-yan/pacemaker/commit/9e492f6231df2d8dd548f111a2490f02822b29ea
Hi,
The code for referencing resource templates in resource sets has been
done and merged upstream for some time. The following link is the
complete documentation of Resource templates including the new feature:
https://github.com/gao-yan/pacemaker/commit/18a85d341ee6213004b1ad95a7f9e16c4c336a4c
Hi Yuusuke,
You may want to fork pacemaker repository, commit the fix and send a
pull request, or probably you want me do that for you?
Regards,
Gao,Yan
On 02/20/12 15:21, Yuusuke Iida wrote:
Hi, Yan
Thank you for comment.
If a patch does not have a problem, I want a repository to update
On 02/09/12 15:38, Gao,Yan wrote:
On 02/09/12 13:08, Andrew Beekhof wrote:
On Thu, Feb 9, 2012 at 1:21 AM, Florian Haas flor...@hastexo.com wrote:
On Wed, Feb 8, 2012 at 3:09 PM, Dan Frincu df.clus...@gmail.com wrote:
I've reviewed both files and made some minor additions and fixed a
couple
-$ticket -v `date +%s`
crm_attribute $options -t tickets /dev/null 21
rc=$?
exit $rc
I send a patch to refer to a value definitely.
The patch makes sense. Thanks!
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE
the docs in the asciidoc way.
Regards,
Gao,Yan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http
Hi Dan,
On 02/08/12 22:09, Dan Frincu wrote:
Hi,
On Wed, Feb 8, 2012 at 1:11 PM, Gao,Yan y...@suse.com wrote:
Hi,
The feature Utilization and Placement Strategy has been provided for
quite some time. But it still missing a documentation. (Florian reminded
us, thanks a lot
On 01/05/12 13:23, Larry Brigman wrote:
On Wed, Jan 4, 2012 at 8:50 PM, Gao,Yan y...@suse.com
mailto:y...@suse.com wrote:
[root@sweng0096 ~]# crm configure property enable-acl=true
[root@sweng0096 ~]# crm
crm(live)#
role monitor \
read xpath:/cib
crm
read id=monitor-read xpath=/cib/
/acl_role
acl_user id=nvs
role_ref id=monitor/
/acl_user
acl_user id=acm
role_ref id=monitor/
/acl_user
/acls
/configuration
...
/cib
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE
On 12/13/11 04:25, Andrew Beekhof wrote:
On Mon, Dec 12, 2011 at 9:20 PM, Gao,Yan y...@suse.com wrote:
On 12/12/11 17:52, Florian Haas wrote:
On Mon, Dec 12, 2011 at 10:36 AM, Gao,Yan y...@suse.com wrote:
On 12/12/11 17:16, Florian Haas wrote:
On Mon, Dec 12, 2011 at 10:04 AM, Gao,Yan y
failed
resource would not consume the capacity of the node.
Regards,
Gaoyan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo
On 12/12/11 15:55, Gao,Yan wrote:
Hi,
As some people have noticed, we've provided a new feature Resource
templates since pacemaker-1.1.6. I made a document about it which is
meant to be included into Pacemaker_Explained. I borrowed the
materials from Tanja Roth , Thomas Schraitle
On 12/12/11 17:16, Florian Haas wrote:
On Mon, Dec 12, 2011 at 10:04 AM, Gao,Yan y...@suse.com wrote:
On 12/12/11 15:55, Gao,Yan wrote:
Hi,
As some people have noticed, we've provided a new feature Resource
templates since pacemaker-1.1.6. I made a document about it which is
meant
On 12/12/11 17:52, Florian Haas wrote:
On Mon, Dec 12, 2011 at 10:36 AM, Gao,Yan y...@suse.com wrote:
On 12/12/11 17:16, Florian Haas wrote:
On Mon, Dec 12, 2011 at 10:04 AM, Gao,Yan y...@suse.com wrote:
On 12/12/11 15:55, Gao,Yan wrote:
Hi,
As some people have noticed, we've provided a new
somewhere?)
You can retrieve the latest source tarball from:
http://hg.clusterlabs.org/pacemaker/pygui/archive/tip.tar.bz2
and the attached spec file should help.
Regards,
Gaoyan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
#
# spec file for package pacemaker-mgmt
Hi Yuusuke,
On 10/20/11 20:43, Yuusuke Iida wrote:
Hi, Yan
(2011/09/26 17:46), Gao,Yan wrote:
A glance to the transition. After grpPostgreSQLDB3 was assigned to act1,
grpPostgreSQLDB1 was chosen to be processed, and it was assigned to act2
(because it had no preference between act2
first rather than grpPostgreSQLDB1. Though the problem is:
Basing on what policy, we could choose grpPostgreSQLDB2 to process
earlier than grpPostgreSQLDB1? Given the processing order was decided
before assigning them all, i.e before assigning grpPostgreSQLDB3.
Regards,
Gaoyan
--
Gao,Yan y
On 08/24/11 17:38, Vladislav Bogdanov wrote:
23.08.2011 12:19, Gao,Yan wrote:
[snip]
When allocating every resource, we compare the capacity of the nodes.
The node has more remaining capacity is preferred. This would be quite
clear if we only define one kind of capacity. While if we define
.)
3. The resource has higher score on the preferred node gets allocated first.
Regards,
Gaoyan
--
Gao,Yan y...@suse.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org
On 07/15/11 14:09, Andrew Beekhof wrote:
On Fri, Jul 15, 2011 at 3:16 PM, Gao,Yan y...@novell.com wrote:
On 07/15/11 10:55, Andrew Beekhof wrote:
On Thu, Jul 14, 2011 at 4:28 PM, Gao,Yan y...@novell.com wrote:
Hi,
Sorry for the delay. I've been thinking about it...
On 07/14/11 12:21, Andrew
On 07/15/11 10:55, Andrew Beekhof wrote:
On Thu, Jul 14, 2011 at 4:28 PM, Gao,Yan y...@novell.com wrote:
Hi,
Sorry for the delay. I've been thinking about it...
On 07/14/11 12:21, Andrew Beekhof wrote:
This loop looks wrong
+ for(gIter2 = resource1-rsc_cons; gIter2 != NULL; gIter2
::pacemaker:Dummy): Started sby1
Resource Group: grp3
rsc3 (ocf::pacemaker:Dummy): Started sby1
As for this, will not it be right like primitive resource to be dispersed
transition?
I attach hb_report when a problem happened.
Best Regards,
Yuusuke
--
Gao,Yan y...@suse.com
Software
On 07/05/11 12:34, Andrew Beekhof wrote:
On Thu, Jun 2, 2011 at 4:59 PM, Gao,Yan y...@novell.com wrote:
On 06/01/11 18:51, Yuusuke IIDA wrote:
Hi, Yan
An answer becomes slow, and really I'm sorry.
(2011/05/13 15:06), Gao,Yan wrote:
I understand that you think the improvement for the non
On 06/21/11 13:07, Andrew Beekhof wrote:
On Tue, May 31, 2011 at 6:58 PM, Gao,Yan y...@novell.com wrote:
On 05/31/11 04:13, Andrew Beekhof wrote:
On Mon, May 30, 2011 at 2:23 PM, Gao,Yan y...@novell.com wrote:
On 05/30/11 17:31, Andrew Beekhof wrote:
It used to be in crm_config.h but I had
On 06/01/11 18:51, Yuusuke IIDA wrote:
Hi, Yan
An answer becomes slow, and really I'm sorry.
(2011/05/13 15:06), Gao,Yan wrote:
I understand that you think the improvement for the non-default
placement strategy makes sense to the default too. Though the
default is somewhat intended
On 05/31/11 04:13, Andrew Beekhof wrote:
On Mon, May 30, 2011 at 2:23 PM, Gao,Yan y...@novell.com wrote:
On 05/30/11 17:31, Andrew Beekhof wrote:
It used to be in crm_config.h but I had to remove it because it
interfered with multilib (not that I've ever seen anyone make use
of it? I don't seem to find one.
Regards,
Yan
--
Gao,Yan y...@novell.com
Software Engineer
China Server Team, SUSE.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http
of resources allocated to a node. That might be a choice.
Regards,
Yan
--
Gao,Yan y...@novell.com
Software Engineer
China Server Team, SUSE.
javascript:void(0);
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman
in cluster_state.
That would not even affect the schema.
Other replies and issues below:
On 05/12/11 19:47, Lars Marowsky-Bree wrote:
On 2011-04-29T03:33:00, Gao,Yan y...@novell.com wrote:
Yes; a ticket section, just like that.
All right. How about the schema:
element name=configuration
. Before pacemaker 1.1 is merged with devel , please adopt:
http://hg.clusterlabs.org/pacemaker/pygui/archive/efff2a4588e5.tar.bz2
Regards,
Yan
--
Gao,Yan y...@novell.com
Software Engineer
China Server Team, OPS Engineering, Novell, Inc.
___
Pacemaker
simplistic
active/passive overlay.)
Does that make sense, or am I creating more confusion than answers? ;-)
Definitely makes a lot of sense:-)
Regards,
Yan
--
Gao,Yan y...@novell.com
Software Engineer
China Server Team, OPS Engineering, Novell, Inc
76 matches
Mail list logo
